...
| Keyword | Full title | Description | Unit | Replacement value | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Read Wait Timeout | Waiting between individual reads of data from the communication if no data has been received.. | sec.mss | 0.010 | ||||||
| Batch Size | The number of messages after sending of which, the Send Delay is performed. | - | 1...1000 | ||||||
| Send Delay | Waiting after sending a batch consisting of Batch Size message. The purpose is not to overload the device with too many messages. Note: while testing the Micro820 device, problems were encountered when sending approximately 200 messages (browsing instances of the class File Object [0x37] with zero delay. Waiting for 1 ms solved the problem. | sec.mss | 0.001 | ||||||
| Max Pending Requests | Maximum number of unacknowledged messages. If the number of unacknowledged messages reaches the value of the parameter, the KOM process waits before sending the next message. A value of 1 means that each message must be confirmed before sending another one (so that the PLC cannot be overloaded due to intensive communication). | 1..100 | |||||||
| Write Symbolic: Array Elements | Methods of writing array using symbolic addressing (Rockwell). There are three supported modes:
| - | 0 .. Array Index | ||||||
| Optimized write of array element | Optimized write is used when only one array element is written. Optimization consists of writing only one specific element and specifying its index (in the protocol specified as Member ID). Note: the tested Micro820 device supported the optimization, the test software server did not. | - | False | ||||||
| Max Packet Size | The maximum size of Ethernet/IP messages (Unconnected Explicit message) - according to the standard 504 bytes. Note: in symbolic mode (Rockwell) it is also possible to work with larger arrays using proprietary services Read Tag Fragmented Service and Write Tag Fragmented Service. Note: this size does not include the Encapsulation Header (24 bytes - Command/Length/Session Handle/Status/Sender Context/Options) or the SendRRData/Common Packet Format header (16 bytes - Interface Handle/Timeout/Item1 + Length/Item2 Length). Note: values greater than 504 bytes are used only if the parameters Use Connected Transport and Large Forward Open have the value YES (Connected Explicit Messages are used and the CIP connection is established with the Large Forward Open message). Note: for a specific CompactLogix (1769-L24ER-QBFC1B/A LOGIX5324ER) the maximum value of the parameter was 4002. For larger values, the response to the Large Forward Open message contained an error code: Received Rockwell LargeForwardOpen Response [xDB] with GeneralStatus: Connection failure [x01], Additional status: <09><01><A2><0F> INVALID CONNECTION SIZE | Bytes | 504 | ||||||
| Response Timeout | Timeout to receive an answer for a request. If the response for a request is not received within this time, this is considered an error, and the TCP connection will be closed. | sec.mss | 10.000 | ||||||
| Optimized Work with Symbolic Names | Optimization of work in a symbolic mode (Rockwell) - so-called Symbol Instance Addressing. Instead of using symbolic names, a Symbol Instance ID is used for reading. The Symbolic name is converted to the Instance identifier by the same service which is used for browsing. Note: Not every device or Rockwell firmware version supports this optimization (tested Micro820 with firmware 10.0.12 or 11.0.11 did not support this optimization). In this case, if the device returns the Service not supported [0x08] error code, the optimization will be disabled until the KOM process is restarted or the configuration of the respective line is re-saved. | - | False |
...
| 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 Transport Parameters --- | |||||||||
| The parameter enables the use of connected CIP transport. Instead of Unconnected Send, a connection is created (with a Forward Open/Large Forward Open message) and then messages are sent through the created connection. | YES/NO | NO | ||||||
| The number of parallel logical CIP connections. A larger number allows faster handling of messages, on the other hand, PLCs support a limited number of CIP connections. Only one message can be handled by one CIP connection at a time. | 1-16 | 4 | ||||||
| The parameter specifies the ID of the first logical CIP connection. If CIP Connections>1, then the configured and subsequent IDs (e.g. 10, 11, 12) are used. IDs of logical CIP connections must be unique, i.e. if there are several stations (on one/multiple lines) that communicate with the same PLC using connected CIP transport (Use Connected Transport=YES), it is necessary to configure a non-repeating ID. | 0-65535 | 1 | ||||||
| The Connection Path The Connection Path parameter of the Forward Open/Large Forward Open message. The default value means:
| octet string | 01 00 20 02 24 01 | ||||||
| The Vendor ID parameter of the Forward Open/Large Forward Open message indicates the vendor ID (identification of the D2000 KOM process). | 0 - 65535 | 0x1234 | ||||||
| The Tick Time parameter of the Forward Open/Large Forward Open message indicates the size of the time interval used to calculate the Forward Open message timeout. See the Timeout Ticks parameter. | ms | 128 | ||||||
| The Timeout Ticks parameter specifies the number of time intervals (of size Tick Time) used to calculate the Forward Open/Large Forward Open message timeout. Timeout is calculated as Tick Time * Timeout Ticks. | - | 1-255 | ||||||
| The O->T RPI parameter of the Forward Open/Large Forward Open message indicates the size of the Originator -> Target Requested Packet Interval in microseconds. | μs | 2000000 | ||||||
| The T->O RPI parameter of the Forward Open/Large Forward Open message indicates the size of the Target -> Originator Requested Packet Interval in microseconds. | μs | 2000000 | ||||||
| Parameter Connection Timeout Multiplier of Forward Open/Large Forward Open messages messages. Specifies the multiplier by which the O->T RPI and T->O RPI parameters are multiplied to determine the timeout of the CIP connection in the O->T or T->O direction. The default timeout is therefore 2 000 000 μs * 16 = 32 seconds. Note: the parameters Connection Timeout Multiplier, O->T RPI and T->O RPI must be adjusted if the period/reading values defined on the station is greater than the CIP timeout , because the CIP connection will may expire during inactivity. | x2 - x512 | x16 | ||||||
| The parameter allows a Large Forward Open message to be used instead of a Forward Open message to create a connected CIP transport. In this, it is also possible to specify a larger size of the Connection Size parameter than 504 bytes, so that the messages can be larger. See the note on the Max Packet Size parameter which specifies the Connection Size for Forward Open/Large Forward Open. | YES/NO | NO | ||||||
--- 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. | - | |||||||
...