...
Parameter | Meaning | Unit / size | Default value | ||||||
---|---|---|---|---|---|---|---|---|---|
| An octet string representing the parameter Route_Path (of padded EPATH type, that is, the number of octets in each segment must be even). If this parameter is specified, the protocol messages (Get_Attribute_Single, Set_Attribute_Single, Read Tag [Fragmented] Service, Write Tag [Fragmented] Service) will be wrapped in an Unconnected Send message that is used for routing. It was not necessary to set this parameter when communicating with Micro820, MicroLogix 1100, and CompactLogix devices. When communicating with ControlLogix via the ControlLogix EtherNet/IP bridge Module (1756-EN2TR/C), it was necessary to set the parameter to 01 00, which according to protocol documentation means Port 1 (which represents the backplane) and slot 0 (where the Central Processor was located). To communicate with the processor in slot 1, the parameter had to be set to 01 01, so the general syntax for accessing a slot XX would be 01 XX. A more complicated configuration consisting of 3 segments:
so the whole Route Path string is: 01 00 12 0C 31 37 32 2E 32 35 2E 35 38 2E 31 31 01 01 (in the syntax of Rockwell OPC server it is "1,[0,2,172.25.58.11, 1], 1") | octet string | |||||||
| Setting the parameter to YES causes the protocol messages (Get_Attribute_Single, Set_Attribute_Single, Read Tag [Fragmented] Service, Write Tag [Fragmented] Service) to be wrapped in a Multiple Service Packet Service message. This parameter is used for communication optimization (wrapping several messages into one), while the size of one message (Unconnected Explicit message) does not exceed the Max Packet Size value. | YES/NO | NO | ||||||
--- Connected Message parameters --- | |||||||||
| The parameter enables the use of conected messages. Instead of Unconnected Send, a connection is created (with a Forward Open message) and then messages are sent through the created connection. | YES/NO | NO | ||||||
| The Connection Path parameter of the Forward Open message. The default value means:
| octet string | 01 00 20 02 24 01 | ||||||
| The Vendor ID parameter of the Forward Open message indicates the vendor ID (identification of the D2000 KOM process). | 0 - 65535 | 0x1234 | ||||||
| The O->T RPI parameter of the Forward Open message indicates the size of the Originator -> Target Requested Packet Interval in microseconds. | 2000000 | |||||||
| The T->O RPI parameter of the Forward Open message indicates the size of the Target -> Originator Requested Packet Interval in microseconds. | 2000000 | |||||||
--- PCCC parameters --- | |||||||||
| Setting the parameter to a non-zero value causes the use of the PCCC protocol encapsulated in the Ethernet/IP protocol. In this way, it is possible to communicate with older SLC 5/05 and PLC5E. At the same time, the symbolic address of the I/O tag starts to be interpreted as an address in SLC-500 format - see Allen-Bradley CSP/PCCC protocol (e.g. N:3 or $T4:0/ACC). | 0-240 bytes | 0 | ||||||
| Selection of PCCC commands used for communication with older SLC 5/05 and PLC5E if the PCCC Max Data Length parameter is set to a non-zero value. The following options are available for selection:
* - when using these commands, only writing is supported for the file types Status (S), Binary (B), Integer (N), Float (F), and even for these types only writing of whole elements is supported, not bits. Writing is not supported for the Timer (T) and Counter (C) file types. | - |
Kotva | ||||
---|---|---|---|---|
|
...