PYRAMID_PLC5250 Object

The PYRAMID_PLC5250 object represents the logical endpoint of the ABTCP hierarchy tree, and can be created from the New_PYRAMID_EI_000 branch of the OI Server hierarchy.

To add the PYRAMID_PLC5250 object to your ABTCP hierarchy

1. Right-click on the New_PYRAMID_EI_000 object.

2. Select Add PYRAMID_PLC5250 Object from the shortcut menu. A New_PYRAMID_PLC5250 _000 object is created.

3. Rename the newly created object as appropriate. The PYRAMID_PLC5250 parameters view is displayed.

   Note: You can add up to 1024 of each type object to the hierarchy.

4. The PLC5_TCPIP parameters view is displayed.

   

This configuration view has three configurable elements:

• Processor Type: (unconfigurable) Information provided automatically by the OI Server Manager (ControlLogix /GuardLogix /SoftLogix).

• Data block size: The number of date bytes that can be sent in a message for this hierarchy.

  • For reading blocks:
    The default value is 2000 bytes.
    The valid range is 2 to 2000.

  • For writing blocks:
    The maximum writing block is 220 bytes, and not configurable.

• Reply timeout: The time (in seconds) the OI Server will wait for the acknowledgement after it sends out a message. The message will be resent when time-out occurred.

  • The default value is 15.

  • Valid range is 1 to 300 seconds.

• Supports unsolicited ‘CLIENT’ messaging: Set this flag to true to enable the OI Server to receive unsolicited "CLIENT" data updates from the selected PLC.

  • The DAServer is enabled automatically to accept normal, "Peer-to-Peer" unsolicited data updates without this flag set to true.

  • The reason to turn on this flag is if the MSG instructions programmed inside the PLC/Host is configured with "CLIENT" as the target station, rather than a specific IP address on the network.

 

Note: The default name created from adding a hierarchy object is in the format of New_ObjectName_###, where ObjectName is the name of the object type and ### is a numeric value starting from "000" enumerated sequentially per hierarchy object. The link name for the OPC items is constructed by assembling the respective object names of the nodes along the hierarchy tree in the logical order starting from this DAServer’s PORT_TCPIP root down to the leaf. Therefore, the link name is always unique for the DAServer.

Note: In order to use the DAServer, you must activate it. See the DAServer Manager documentation for information about how to activate and deactivate the DAServer.