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>pre-release</version> </dependency> |
|||
Default Transport |
|
|||
Supported Transports |
|
|||
Config options: |
||||
|
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. |
|
|
INT |
10000 |
Default timeout for all types of requests. |
|
|
STRING |
The communication path allows for connection routing across multiple backplanes. It uses a common format found in Logix controllers. |
||
Transport config options: |
||||
tcp |
||||
|
INT |
5000 |
||
|
INT |
0 |
||
|
INT |
0 |
||
|
BOOLEAN |
true |
||
|
BOOLEAN |
false |
||
|
INT |
81920 |
||
|
INT |
81920 |
||
|
STRING |
|||
|
INT |
0 |
||
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) |