Connection to an ML1100 by ethernet - and it says ‘CONNECTED’. However, in the quick client and in add tag under the designer, when I click on the object for this device, it pauses, but no data files show up.
In the log, I get:
[ML1100] Browse Request request failed due to TIMEOUT
com.inductiveautomation.xopc.drivers.allenbradley.requests.ABMicroLogixBrowseRequest
I have a packet sniffer running, here is an example of the network traffic. We have the three-way TCP handshake to port 44818, then the ENIP Req and Rsp packets. That’s it. If I go to browse, it repeats the Req/Rsp and then that’s it. I also see some keep-alives, but I didn’t feel it necessary to display those.
Can you send me capture data bytes from your packet sniffer? In Wireshark you can save the capture to a .pcap file and email it to support@inductiveautomation.com.
I also noticed that when setting connection parameters to the device no network traffic flows until hit the save button. This is expected behaviour.
However, while playing with settings to get comms - when we have a comms failure frequently java.exe running as system user pegs my CPU to 99%. Stopping the Ignition service kills that process, so I know it is related. Can you make comms failure a little more graceful?
Also when I can get into the web interface and I delete a comms device, the network traffic does not stop until I restart the service. Is this intentional? I would have expected that network traffic to the device stops immediately without a service restart.
When a connection fails there should be a delay before trying to reconnect.
Can you
In the Configure section of the Ignition Gateway, select Console.
Select Levels tab then type in MicroLogixDriver and click the Set button.
Select Trace for the level of the xopc.drivers.allenbradley.MicroLogixDriver, xopc.drivers.allenbradley.requests.ABMicroLogixConnectRequest and xopc.drivers.allenbradley.transport.ABMicroLogixTransport items.
Add a MicroLogix device if one is not present and wait 60 seconds.
Reset the trace level back to info Info for the MicroLogixDriver items.
At your step 2, I get ‘displaying 0 of 197 loggers’. When I just search for xopc, I get more stuff but no AB looking drivers. Do I need to have the device configured first?
That did it - added ML1100 first then could change the log entry. There was only 1 log entry that looked like what you mentioned… I hope that I did it correctly. Wrapper is on it’s way by email.
I see in the logs where the communication stops. Are you connected directly to the MicroLogix 1100 or are you bridging to it? What is the model number and version of your ML?
Direct connection - on my local LAN. No bridging, routing, port forwarding or any other funny business. See attached picture for the specific firmware rev of this device…
It refuses to upload for some reason, so here is a copy from the built-in webserver:
Device Name 1763-L16BWA B/8.00
Device Description MicroLogix 1100 Processor
Device Location
Ethernet Address (MAC) 00-0F-73-01-8B-EF
IP Address 192.168.1.31
O/S Revision Series B FRN 8.0
HTML File Revision 1.10
Current Time Feb 2 2010, 18: 1:12
CPU Mode Remote Run
This thread is fairly old and the issue for this thread was fixed.
Starting from scratch:
Is you model of MLX an 1100?
What version of Ignition are you using?
Can you send in the logs?
When a connection fails there should be a delay before trying to reconnect.
Can you
In the Configure section of the Ignition Gateway, select Console.
Select Levels tab then type in MicroLogixDriver and click the Set button.
Select Trace for the level of the xopc.drivers.allenbradley.MicroLogixDriver, xopc.drivers.allenbradley.requests.ABMicroLogixConnectRequest and xopc.drivers.allenbradley.transport.ABMicroLogixTransport items.
Add a MicroLogix device if one is not present and wait 60 seconds.
Reset the trace level back to info Info for the MicroLogixDriver items.