LOGIX_FLX object

The Logix_FLX object represents the physical Allen-Bradley FlexLogix processor module.

• 1794-Lxx

This object is hosted by BACKPLANE_FLX.

Add the LOGIX_FLX object to your ABCIP hierarchy

1. Select and right-click on the NEW_BACKPLANE_FLX_000 object.

2. Select Add LOGIX_FLX Connection from the shortcut menu. The New_LOGIX_FLX_000 object is created.

3. Rename the newly created object as appropriate. The LOGIX_FLX Parameters configuration view is displayed.

This configuration view has nine parameters, eight of which are configurable:

Processor Type: (not configurable) Information provided automatically by the OI Server Manager (FlexLogix).

Slot Number: A sequential number beginning with 0 (zero) assigned to each slot in a FlexLogix chassis.

• The slot number indicates where the module resides.

• The valid range is 0 - 16.

• The default value is 0.

  Reply Timeout: Time (in seconds) the Communication Driver will wait for the acknowledgement after it sends out a message. The message will be resent when time-out occurs.

• The valid range is 1 - 300.

• The default value is 15.

• Max CIP Connections: The maximum number of CIP connections that can be originated from the Communication Driver to the PLC. The number of CIP connections should be configured based on the load of messages that are sent to the device, and the hardware capabilities of the PLC processor. When multiple CIP connections are configured, the ABCIP Communication Driver distributes the number of messages across these connections to enable faster processing of the messages. For example:

  • If Max CIP Connections is configured as 1, then all messages will be polled through the single CIP Connection, one message at a time.

  • If Max CIP Connections is configured as 4 and there are 10 messages in the queue, then these 10 messages will be polled through 4 CIP Connections. 4 messages will be sent to PLC immediately, and the other 6 messages will be in queue. The next 4 messages will be sent to PLC after the first 4 messages are processed. The process will continue until all messages in the queue are processed.

  • The valid range is 1 - 31.

  • The default value is 4 (four).

    Note: For each CIP connection established, the PLC allocates certain resources to handle the connection. If too many CIP connections are established by the Communication Driver, the PLC processor allocates more resources for the CIP, which might affect the performance of other operations. For example, with 31 connections, the data updates become extremely sluggish since the PLC ran out of resources to handle the runtime logic and updating the control items. This is why it is important to configure the number of CIP Connections based on the hardware capabilities of the PLC processor.

• Optimization (For detailed information, see Logix5000 optimization mode):

  • No optimization: The server uses the most basic communication method available by using the tag name for each communication with the controller. The tag database will be uploaded from the processor to validate the tag names.

  • Optimize for read (Default): All tags are accessed by predefining messages in the controller, thus optimizing blocks of information from the controller. Initialization of this mode requires that these message blocks are built when connecting to the controller, therefore startup time will require more time. This mode is most effective with large number of tags on continuous scan.

  • Optimize for startup time: This option provides the best overall performance. All tags are accessed from the Logix processor using the device’s memory location table. If this option is checked, the ‘Auto Synchronize Tag’ option is checked automatically and cannot be unchecked.

    Note: "Optimize for Startup time" is not supported on Logix Controllers using firmware version 21 or above. For more information, see Logix5000 optimization mode.

• Optimize User Defined Data Types: The optimization for reading structures is enabled when selected (Default is unchecked). For more detailed information, see UDT optimization.

  • If selected, the server will retrieve the whole structure in one packet provided the size of the structure is 488 bytes or less.

• Tag Database Options: Three options are selectable to implement manual or automated updates of the Logix processor’s tag database. For more information, see Logix5000 online tag management.

  • Auto Load Tags on Startup (Default)

  • Auto Synchronize Tags

  • Use Persisted Tags (Default)

    Note: If the Optimization setting is selected for "Optimize for startup time", the "Auto Synchronize Tags" option is automatically selected and unchangeable (dimmed). The Communication Driver will need to synchronize physical address tags from the device.

    Important: Support for secured Logix5000 controllers will effect the way the ’Auto Synchronize Tags’ and ’Persisted Tags’ behave. For detailed information, see Access secured Logix5000-series controllers.