EtherNet/IP
Connection String Options
Name |
Type |
Default Value |
Required |
Description |
Name |
EthernetIP |
|||
Code |
|
|||
Maven Dependency |
<dependency> <groupId>org.apache.plc4x</groupId> <artifactId>plc4j-driver-eip</artifactId> <version>0.13.0-SNAPSHOT</version> </dependency> |
|||
Default Transport |
|
|||
Supported Transports |
|
|||
Config options: |
||||
|
INT |
1 |
Without using routing information the backplane defaults to 1. This is overridden if communicationPath is provided. |
|
|
INT |
0 |
The slot within the backplane the CPU is located. |
|
|
BOOLEAN |
true |
Configure if the connection should be set to transport data in Big-Endian format, or not. |
|
|
BOOLEAN |
false |
Forces the driver to use unconnected requests. |
|
Transport config options: |
||||
tcp |
||||
|
BOOLEAN |
false |
Should keep-alive packets be sent? |
|
|
BOOLEAN |
true |
Should packets be sent instantly or should we give the OS some time to aggregate data. |
|
|
INT |
1000 |
Timeout after which a connection will be treated as disconnected. |
|
Address Format
To read and write data to a PLC4X device, the EtherNet/IP driver uses symbolic segments. This is used to refer to objects through their symbolic names. This makes reading data a lot easier, as you do not need to specify the Datatype for reading.
%{tagname}[{startIndex}]:{numberOfElements}
%{tagname}[{startIndex}]:{numberOfElements}:{DataType}
| Name | Description |
|---|---|
Tagname |
symbolic name of the Data |
Start Index (optional) |
if the data is an array, we can specify a starting index from where we want to read |
Number of elements (optional) |
if the data is an array, we can specify the number of elements we want to read. Use this in combination with the starting index to get the exact scope you want. |
DataType (writing) |
Specify the Data-type of the value you want to write (mandatory) |