Tech Notes

Tech Note: 120

Backing up and Restoring a Galaxy

System Platform Galaxies should be backed up so that if the Galaxy becomes corrupted, you can restore it to a working state.  The Galaxy backup file can be used to overwrite an existing, corrupted Galaxy or to re-create it as a new Galaxy.

This tech note will provide instructions on how to create a Galaxy backup file and provide the steps for restoring an existing Galaxy as well as using a Galaxy backup to create a new Galaxy.


Tech Note: 122

Cannot Select Licenses for Activation in AVEVA License Manager

It is possible to encounter a situation where you are unable to select licenses to be activated in the AVEVA Enterprise License Manager. In these cases, it may be necessary to replace the database file to correct the issue.

This tech note provides instructions to replace the License Manager database file.


Tech Note: 121

Correcting Deployment State Mismatches

Certain conditions (hardware failure of a deployed node, restoring a Galaxy from a backup, etc.) can cause the deployment state of an object in the IDE to be different from the object’s actual state.

This tech note will provide steps to correct this mismatch.


Tech Note: 119

Using $Sys$UpdateTagInfo with ABCIP OI Servers

Occasionally, making modifications to the tags in a ControlLogix/CompactLogix PLC will result in the AVEVA ABCIP OI Server having one topic that is not showing the correct information. It may appear to be good data but it is reading the wrong tag data or the tag data may have bad quality.

If you encounter this issue, you may be able to resolve it by downloading a new copy of the tag database from the PLC to the OI Server.   Toggling the $Sys$UpdateTagInfo item to “true” forces an update of the entire controller tag database.

This tech note provides two methods than can...

Tech Note: 118

Using AVEVA License Server OFFLINE Activation

AVEVA Licenses require license activation, a process whereby the authenticity of the license is verified against license records via the AVEVA License Activation Server and the license is bound to the license server from which the activation was initiated.

License activation requires communication over the Internet with the AVEVA License Activation Server. That communication can be either direct over the Internet (Online Activation) or indirect through a proxy computer (Offline Activation).

This Tech Note describes the process of activating an AVEVA license using OFFLINE activation.


Tech Note: 117

Ending AVEVA License Server Grace Period

Certain conditions can cause the AVEVA Enterprise License Server to enter a License Grace Period. The Grace Period allows the server and licenses to operate normally for fifteen days. Once the fifteen day period has expired, the License Server will no longer allow licenses to be acquired. Removing the Grace Period mode will allow the License Server to function normally again. This tech note will provide instructions for two methods that can be used to remove the Grace Period mode from a License Server.


Tech Note: 116

Adding Auto Reconnect Functionality to Device Integration Objects

When a Device Integration object gets disconnected from its data source (e.g. an AVEVA OI Server), it must be manually triggered to reconnect when the source becomes available again.  This tech note will instruct you on how to set up an auto reconnect feature and add additional diagnostic information that will indicate the number of disconnects the object has experienced since it last went on scan.