Logix5000 optimization mode

Operation of the ABCIP Communication Driver per device will be such that it can operate in the same multi-request service (non-optimized) mode or in optimized mode for any device. If the device and firmware support optimization, the default mode for the device will be with optimization. You will have the capability of disabling optimization even though the device and firmware may support it.

The optimization will require a tag database upload from the Logix5000-series controller (ControlLogix, CompactLogix, FlexLogix, GuardLogix, SoftLogix). The tag database contains the data types and unique references that can be used to reference the physical tags available in the controller. The tag database kept in the controller is versioned. ABCIP Communication Driver provides the option that can be used to periodically probe the controller for any version changes and to obtain the changes in the tag database.

• The ABCIP Communication Driver supports only No Optimization and Optimize for Read mode on firmware versions 21 and higher. By default Optimize for Read is selected.

• The Optimize for Startup mode will only be used to access controllers operating on firmware versions 20 and lower.

• The ABCIP Communication Driver will switch to Optimize for Read mode from Optimize for Startup if firmware version 21 or higher is detected from the controller, even if the optimization setting is set to Optimize for Startup. In this instance, the ABCIP Communication Driver will generate a warning line in the logger to alert that the Optimize for Startup mode is not supported for firmware version 21 and higher controllers.

Three selectable options are:

1. No optimization

   All tags that communicate with the Logix processor will use the tag name. The tag database will be uploaded from the controller to validate the tag names. No optimization will have the fastest startup time, but will have the slowest read performance. It will create more messages for controller communication than the other two options. The length of the tag name will affect the number of messages created.

2. Optimize for Read

   All tags that communicate with the Logix processor will require a tag database to be available as a prerequisite. This operation also generates a memory buffer inside the controller and thus requires the longest startup time among the three options.

   Despite the longer startup time, Optimize for Read provides the fastest read performance after the tag database upload operation has been completed. It will create fewer messages for controller communication.

3. Optimize for startup time

   Available only for firmware versions 20 and lower, this option provides the best overall performance among all three optimization options. All tags that communicate with the Logix processor will require a tag database to be available as a prerequisite.

   This option does not generate a memory buffer inside the controller and thus provides a faster startup time than the Optimize for read option. All tags communicating with the Logix processor will be using the physical tag address. It provides a faster read performance than the No Optimization option as multiple tags can be referenced in one request packet to the Logix processor. It will create a higher number of messages for controller communication than the Optimize for read option.

   Note: If this option is checked, the ‘Auto Synchronize Tag’ option is checked automatically and cannot be unchecked.