PLC4J EIP #1982

mjoseph909 · 2025-01-20T19:34:47Z

mjoseph909
Jan 20, 2025

I'm trying to use the EIP protocol in the connection string to communicate with a Compact GuardLogix 5380 5069 -L306ERMS2 processor; however, after specifying big endian as false, I'm still getting an error that the remote device doesn't use big endian byte order.

Here is my connection string:
String connectionString = "eip://192.168.10.2:44818?big-endian=false";

Here is the error I'm getting:
[nioEventLoopGroup-2-1] WARN io.netty.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.handler.codec.DecoderException: org.apache.plc4x.java.api.exceptions.PlcRuntimeException: The remote device doesn't seem to use BIG_ENDIAN byte order.

Additionally, I have the dependency in the pom file. Any help would be appreciated, as I'm new to using PLC4X. Thanks!

chrisdutz · 2025-01-20T19:59:38Z

chrisdutz
Jan 20, 2025
Collaborator

Hi Joseph (hope that's right)

First off all, welcome to PLC4X.

You are reaching us in a bit of an odd situation. Many of the previous contributors had to switch away from PLC4X as consulting in this area didn't help pay the bills. So we are currently running a bit low on people working behind the scenes. I also am currently taking a 2 month sabbatical, where I'm working with wood in my garage instead of working on software.

I would be willing to jump in and help, but unfortunately not for free. I had done that for 8 years, but it kept on burning me out.

Possibly you would even have the biggest advantage by debugging into the code yourself and trying to find the solution to your problem on your own. It's super rewarding to find stuff like that on your own ... believe me ;-)

As you are not stating which version of PLC4X you are using. A first step always is using the latest SNAPSHOT version. I think the EIP driver received quite a bit of an update since the release of 0.12.0. Possibly your problem is already fixed there. If that's the case you're lucky as the team is currently preparing for the next release of 0.13.0.

If you need any help ... as I mentioned, I'm willing to give it after a noticeable donation on https://buymeacoffee.com/christoferu

Hope you understand and good luck ;-)

0 replies

glcj · 2025-01-21T14:25:43Z

glcj
Jan 21, 2025
Collaborator

Hello,

Can you document the dependency failure in the pom, I think that when compiling it should generate the exception. Can you post the trace that is generated?

We are going to perform an EIP test with ControlLogix, it should be standard.

Thanks for posting the equipment model.

1 reply

mjoseph909 Jan 23, 2025
Author

Hi,
Here is the whole console message when I run my project:

[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Instantiating new PLC Driver Manager with class loader jdk.internal.loader.ClassLoaders$AppClassLoader@5c29bfd
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering available drivers...
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol ab-eth (Allen Bradley ETH)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol ads (Beckhoff TwinCat ADS)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol bacnet-ip (BACnet/IP)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol c-bus (Clipsal C-Bus)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol genericcan (Generic CAN)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol canopen (CAN open)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol eip (EthernetIP)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol logix (Logix CIP)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol firmata (Firmata)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol iec-60870-5-104 (IEC 60870-5-104)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol knxnet-ip (KNXNet/IP)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol open-protocol (Open-Protocol)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol modbus-ascii (Modbus ASCII)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol modbus-rtu (Modbus RTU)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol modbus-tcp (Modbus TCP)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol opcua (Opcua)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol plc4x (PLC4X (Proxy-Protocol))
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol profinet (Profinet)
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol s7 (Siemens S7 (Basic))
[main] INFO org.apache.plc4x.java.DefaultPlcDriverManager - Registering driver for Protocol simulated (Simulated PLC4X Datasource)
[nioEventLoopGroup-2-1] WARN io.netty.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.handler.codec.DecoderException: org.apache.plc4x.java.api.exceptions.PlcRuntimeException: The remote device doesn't seem to use BIG_ENDIAN byte order.
	at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:98)
	at io.netty.handler.codec.MessageToMessageCodec.channelRead(MessageToMessageCodec.java:111)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
	at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
	at io.netty.handler.codec.MessageToMessageCodec.channelRead(MessageToMessageCodec.java:111)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318)
	at io.netty.handler.codec.ByteToMessageCodec.channelRead(ByteToMessageCodec.java:103)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.apache.plc4x.java.api.exceptions.PlcRuntimeException: The remote device doesn't seem to use BIG_ENDIAN byte order.
	at org.apache.plc4x.java.eip.base.protocol.EipProtocolLogic.lambda$4(EipProtocolLogic.java:200)
	at java.base/java.util.function.Consumer.lambda$andThen$0(Consumer.java:65)
	at org.apache.plc4x.java.spi.Plc4xNettyWrapper.decode(Plc4xNettyWrapper.java:183)
	at io.netty.handler.codec.MessageToMessageCodec$2.decode(MessageToMessageCodec.java:81)
	at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:88)
	... 28 more
[nioEventLoopGroup-2-1] ERROR org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection - unknown error, close the connection
java.io.IOException: An existing connection was forcibly closed by the remote host
	at java.base/sun.nio.ch.SocketDispatcher.read0(Native Method)
	at java.base/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
	at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:276)
	at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:233)
	at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:223)
	at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:358)
	at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255)
	at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132)
	at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357)
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:834)
[main] ERROR iwt.Pipe - PLC Connection Exception: java.util.concurrent.ExecutionException: org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated by remote
[nioEventLoopGroup-2-1] WARN io.netty.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
java.io.IOException: An existing connection was forcibly closed by the remote host
	at java.base/sun.nio.ch.SocketDispatcher.write0(Native Method)
	at java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51)
	at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:113)
	at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:58)
	at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:50)
	at java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:466)
	at io.netty.channel.socket.nio.NioSocketChannel.doWrite(NioSocketChannel.java:415)
	at io.netty.channel.AbstractChannel$AbstractUnsafe.flush0(AbstractChannel.java:931)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.flush0(AbstractNioChannel.java:355)

Let me know if this helps. If not, I can provide more information. I appreciate the help.

chrisdutz · 2025-01-23T20:49:41Z

chrisdutz
Jan 23, 2025
Collaborator

Let me ask again: Which version of PLC4X are you using 0.12.0 or 0.13.0-SNAPSHOT?

3 replies

mjoseph909 Jan 23, 2025
Author

Sorry, I am using 0.12.0

chrisdutz Jan 23, 2025
Collaborator

Yeah ... then I can stop trying to have a look .. please try with 0.13.0-SNAPSHOT and if that doesn't work, report that. From a quick look in that banch, the connection string needed a different name for the parameter (We streamlined the naming convention to be the same for all drivers) ...

With 0.12.0 your connection string should have been:

String connectionString = "eip://192.168.10.2:44818?bigEndian=false";
Hmmm ... well that's also what our website says for the latest released version 0.12.0: https://plc4x.apache.org/plc4x/latest/users/protocols/eip.html

This will change to "big-endian" in 0.13.0: https://plc4x.apache.org/plc4x/pre-release/users/protocols/eip.html

mjoseph909 Jan 28, 2025
Author

Thank you so much, I really appreciate the help. I must have looked at the wrong documentation for the big endian parameter.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

PLC4J EIP #1982

{{title}}

Replies: 3 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

PLC4J EIP #1982

mjoseph909 Jan 20, 2025

Replies: 3 comments · 4 replies

chrisdutz Jan 20, 2025 Collaborator

glcj Jan 21, 2025 Collaborator

mjoseph909 Jan 23, 2025 Author

chrisdutz Jan 23, 2025 Collaborator

mjoseph909 Jan 23, 2025 Author

chrisdutz Jan 23, 2025 Collaborator

mjoseph909 Jan 28, 2025 Author

mjoseph909
Jan 20, 2025

Replies: 3 comments 4 replies

chrisdutz
Jan 20, 2025
Collaborator

glcj
Jan 21, 2025
Collaborator

mjoseph909 Jan 23, 2025
Author

chrisdutz
Jan 23, 2025
Collaborator

mjoseph909 Jan 23, 2025
Author

chrisdutz Jan 23, 2025
Collaborator

mjoseph909 Jan 28, 2025
Author