Looking for a little advice trying to connect to an older control logix processor. The processor is an 1756-L55 running version 13, and the ENBT card is on version 1.06. Ignition will not connect to it, are there firmware limitations on ignitions side?
We only test/support as low as firmware v16. Which driver are you trying to use? What errors do you get?
It just shows connecting, and I do not see any errors in the logs. I am using the control logix (legacy). I don’t believe, L55 processors cannot be upgraded to version 16.
It might be useful to set the loggers you find searching for “ControlLogixDriver” to DEBUG and then see if there are any new logs in the gateway is it tries to connect.
Are you sure you have the right IP address and slot or connection path configured?
Filtering for ControlLogixDriver just shows logs for other plc's but not for the one that will not connect. The IP and slot are definitely correct, I do not have anything entered for the connection setting, should this be set to something?
Did you change the level to DEBUG first in the little gear menu?
Can you upload those logs somewhere? Or at least expand and show the details under the “Error connecting…” entry by clicking the “plus” on the right?
| ControlLogixDriver | 12Nov2021 08:21:45 | Error connecting to “172.20.3.47”. |
|---|---|---|
| java.net.ConnectException: Connection timed out: connect |
at java.base/java.net.PlainSocketImpl.connect0(Native Method)
at java.base/java.net.PlainSocketImpl.socketConnect(Unknown Source)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
at java.base/java.net.Socket.connect(Unknown Source)
at java.base/java.net.Socket.connect(Unknown Source)
at com.inductiveautomation.xopc.driver.api.AbstractSocketDriver.connect(AbstractSocketDriver.java:114)
at com.inductiveautomation.xopc.driver.api.AbstractDriver$5.run(AbstractDriver.java:731)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)|
Great, so you just have a network problem at this point.
That PLC either isn’t accepting your connection, or you have a firewall or routing problem, or you have the wrong IP address. It’s not getting far enough to know if firmware version is even a problem yet.
Aside from changing the IP address there’s no knobs to turn on the Ignition side right now. The problem is external.
Ok, Thanks
You are correct, I didnt scroll down in the software, 16 does show up.
I am experiencing a similar issue connecting to 1756-L55 with firmware 13. My logs show it's connecting but fails, "reading edit number from processor."
ControlLogixDriver 24Apr2024 08:12:59 [Cooling] notifyConnectFailed().
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Error reading edit number from processor.
ControlLogixDriver 24Apr2024 08:12:59 [Cooling] Looking for 4, Unconnected: <4>, Connected:
ControlLogixDriver 24Apr2024 08:12:59 getRequestKey() called - key returned: 4 dec, 4 hex
ControlLogixDriver 24Apr2024 08:12:59 messageLength() called - length returned: 46
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Connected request being send with transaction is 4
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Read processor mode successfully (reading edit number from processor).
ControlLogixDriver 24Apr2024 08:12:59 [Cooling] Looking for 3, Unconnected: <3>, Connected:
ControlLogixDriver 24Apr2024 08:12:59 getRequestKey() called - key returned: 3 dec, 3 hex
ControlLogixDriver 24Apr2024 08:12:59 messageLength() called - length returned: 52
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Connected request being send with transaction is 3
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Connected (sending read mode request).
ControlLogixDriver 24Apr2024 08:12:59 [Cooling] Looking for 2, Unconnected: <2>, Connected:
ControlLogixDriver 24Apr2024 08:12:59 getRequestKey() called - key returned: 2 dec, 2 hex
ControlLogixDriver 24Apr2024 08:12:59 messageLength() called - length returned: 56
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Connected request being send with transaction is 2
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Connected (sending forward close).
ControlLogixDriver 24Apr2024 08:12:59 [Cooling] Looking for 1, Unconnected: <1>, Connected:
ControlLogixDriver 24Apr2024 08:12:59 getRequestKey() called - key returned: 1 dec, 1 hex
ControlLogixDriver 24Apr2024 08:12:59 messageLength() called - length returned: 28
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Connected request being send with transaction is 1
ABControlLogixConnectRequest 24Apr2024 08:12:59 [Cooling] Creating connection request.
ControlLogixDriver 24Apr2024 08:12:59 [Cooling] Creating connection request using Ethernet/IP protocol.
ControlLogixDriver 24Apr2024 08:12:59 [Cooling] TCP connection successfully opened.
ControlLogixDriver 24Apr2024 08:12:59 Disconnected -> Connecting
ControlLogixDriver 24Apr2024 08:12:59 [Cooling] Opening TCP connection...
Is there anything I can try to do about this before updating the firmware to 16?
Wireshark?