UPGRADE ALTERS COMMUNICATIONS CONFIGURATIONS
After upgrading, confirm and adjust the configuration of all I/O devices in your project.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
The upgrade process verifies that the functionality of your project is upgraded to version 7.x. To facilitate this, parts of your project configuration may change during the upgrade. It is therefore important to verify that a project is configured the way you want it to run before you upgrade.
In particular, memory I/O Devices defined in your project (specifying MEMORY as the port) will be configured in the upgraded project as local variables, since memory I/O Devices are no longer supported. Local variables offer the same functionality as memory I/O Devices without the need for further configuration.
However, this also means if you have I/O Devices temporarily defined as memory I/O Devices for testing or simulation, they will be incorrectly configured as local variables by the upgrade process. Verify that you configure these devices as you require them to run before upgrading to version 7.x.
|
|
|
UPGRADE ALTERS COMMUNICATIONS CONFIGURATIONS After upgrading, confirm and adjust the configuration of all I/O devices in your project. Failure to follow these instructions can result in death, serious injury, or equipment damage. |
Before attempting to configure your I/O devices for the changes caused by the upgrade process, first read the information in Configuring Local Variables and Using Memory Mode. This provides details about local variables and the other I/O Device options that replace memory I/O Devices, allowing you to select and configure your project appropriately.
Note: Alarm devices with their Protocol property set to "Alarm" are no longer used and will be removed by the Migration Tool. All Alarm Servers will now publish Alarm Properties.
The reconfiguration will take place when you run the Migration Tool. For detailed information on this tool, refer to Migration Tool.
See Also