I have 2 Ignition installation, one was used for testing and development, the other is the live system.
Live system:
Operating System: Linux CentOS 5.6 64 bit
Ignition Version: 7.6.2 (b2368) (64 bit)
Java Version: Sun Microsystems Inc. 1.6.0_24 (64 bit)
Allen-Bradley drivers 1.6.2 (b504)
Test environment:
Operating System: Windows Web Server 2008 (32 bit)
Version 7.6.2 (b2368) (32 bit)
Java Version Oracle Corporation 1.7.0_25 (32 bit)
Allen-Bradley drivers 1.6.2 (b504)
3 PLC’s are connected, 2 of them are AB ControlLogix, 1 is AB Compact Logix. In the test environment all 3 connected without any issue. In the live environment (Linux 64 bit) I have the 2 ControlLogix working perfectly but it cannot connect to the CompactLogix. Configuration is the exact same on the two Ignition servers.
I wonder if someone have an idea in what direction I should start troubleshooting…
Thanks in advance!
The full error message I get on the live system is:
Disconnected: Protocol: EIP - Unknown Error:
java.lang.Exception: Error reading processor mode.
com.inductiveautomation.xopc.drivers.allenbradley.requests.ABControlLogixConnectRequest.receiveMessage(ABControlLogixConnectRequest.java:129)
com.inductiveautomation.xopc.drivers.allenbradley.requests.ABControlLogixConnectRequest.receiveMessage(ABControlLogixConnectRequest.java:21)
com.inductiveautomation.xopc.driver.api.BasicRequestCycle.deliverMessage(BasicRequestCycle.java:176)
com.inductiveautomation.xopc.driver.api.BasicRequestCycle.messageArrived(BasicRequestCycle.java:162)
com.inductiveautomation.xopc.driver.api.AbstractDriver.messageArrived(AbstractDriver.java:700)
com.inductiveautomation.xopc.driver.api.AbstractSocketDriver.messageArrived(AbstractSocketDriver.java:191)
com.inductiveautomation.xopc.driver.api.AbstractSocketDriver$DriverIOEventHandler$1.run(AbstractSocketDriver.java:253)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
java.util.concurrent.FutureTask.run(FutureTask.java:138)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
java.lang.Thread.run(Thread.java:662)
If you go to the levels tab of the console on the Ignition gateway, you can search for whatever the name you gave the device that isn’t connecting. Turn the logger for the driver itself (drivers.ControlLogixDriver[NameYouChose]) as well as the one for ABControlLogixProcessorStatusRequest to TRACE.
Let it try to connect, then export the logs.bin.gz and attach it here or send it in to support.
You can also feel free to call into support and they’ll troubleshoot and go through this with you over the phone/GoToMeeting.
I could find drivers.[color=#FF0000]Compact[/color]LogixDriver[TESTPLC] and enabled TRACE level for it and all sub-entry (happened automatically). I could not find ABControlLogixProcessorStatusRequest or ABCompactLogixProcessorStatusRequest for the PLC in the list.
I have gzipped the logs.bin file and the wrapper.log file and attached here. I did not find a logs.bin.gz pre-zipped?
It looks like you are receiving responses, but still getting a lot of “Error Reading Processor Mode” messages. What firmware is that device using? Ignition 7.6 only supports up to firmware 20.
I see the following when connecting to the PLC, hope it is helpful:
Device Name 1769-L16ER/A LOGIX5316ER
Product Revision 20.013 Build 81
Firmware Version Date Mar 1 2012, 09:59:59
Serial Number 602D734C
Also, the very same version of Ignition running on a 32-bit Windows server (which is an old piece of hardware, on my desk for testing) connects to the PLC perfectly. The other installation of Ignition with the same version on a 64 bit Linux server (on a HP ProLiant ML110 G7 server) has this problem. At the same time, this Linux installation connects to two ControlLogix on the live running system and works just fine.
What is annoying, that when I want to try something on this little CompactLogix PLC, I need to fire up this test system.
At the moment, this is not a show stopper for anything, but makes testing uncomfortable. I wonder if there are others with similar issues…
Dev PC is Windows 7 Pro 64-bit laptop running Ignition 7.6.4 (b2013112117) | 64-bit
Production PC is Windows 7 Pro 32-bit running Ignition 7.6.4 (b2013112117) | 32-bit
PLC is CompactLogix L33ER revision 20.13
The production PC and PLC now in production are on a different LAN than the Dev PC, so the PLC IP address is different than it was when I was using it with the Dev PC (during development, PLC was here on LAN with Dev PC). I never had any problem connecting in either of these scenarios.
FYI I had never had both connected at the same time (now that PLC is in production, I’ve been developing directly off the production PC Gateway), so I just tried connecting the Dev PC to this PLC and it went from “Connecting” to “Connecting: Protocol: EIP - Unknown” to "“Connecting: Protocol: EIP - Run Mode” to “Connected: Browse Pending…”. It just kept cycling through that. I wasn’t sure why the browse was not successful. Perhaps something to do with the high latency link in the WAN between Dev PC and production PLC. So I increased the timeout from 2000 to 15000ms and this problem went away; it now shows “Connected: Protocol: EIP - Run Mode”.
It’s probably not related to the problem as you have it on the working gateway as well, however I don’t believe you need a connection path in your device settings with the newer generation CompactLogix PLCs like you are using. I’ve always left this blank for the L33ER.
A shot in the dark: is it possible your CompactLogix is running low on the system overhead time slice (that handles communications)?
I think the easiest thing to do here is just call into the tech support line and see if we can troubleshoot this over the phone and with a gotomeeting. If this option doesn't work for you just let me know and we can arrange something else.
The point goes to witman, I am grateful for spending the time and taking a look into the details of somebody else’s problem.
Surprisingly enough it was the Connection Path. I am quite sure that when I first set up (several versions earlier), I needed the connection path to be “1.0” (I remember spending plenty of time to figure out how to connect). It is still working well in the test environment.
However, now that I cleared the Connection Path setting in the live environment, it suddenly connected and works perfectly!
Checked in the test environment, it still works happily with or without the connection path, the live installation only works without it.
Great learning for me and probably useful for others.
Hi , Similar issue i am facing right now . 5 Nos of L33ERM with 33 ver connected to ignition via EWON NAT Switch . In Development PC shows connecting but when switch to live disconnecting error coming . Do you have any idea ?
Welcome to the forum but ...
You're replying to a thread that was started in 2013 and to a user who was last seen in 2014. I suggest you delete your post and start a new thread with full details of your setup, what you expected and what you got.
The point goes to witman, 
I am grateful for spending the time and taking a look into the details of somebody else’s problem.