Ethernet DAQ - Adavantech ADAM6000 (6017) - DL-250-1

[Acadien]

My ECOM100 failed again, without the C-more on the network. So I am back to the Modbus theory, the only problem my wireshark capture did not show anything usefull, it stopped recording about 4 hours before the crash. I have ordered a new ECOM100 card to replace the existing one.

[Greg]

I cannot download the file you posted. When I do and try to open it in Wireshark, I get "The capture file appears to be damaged or corrupt. (pcap: File has 3932160-byte packet, bigger than maximum of 65535)".

Was the capture supposed to show a crash?

Also, we have seen crashes with Modbus TCP on older firmware and have fixed them. So, it is possible that there is another such crash that we need to fix. I doubt it is the ECOM100 hardware that is the problem. But a capture showing the crash would certainly tell the tale.

[Acadien]

Unfortunately, the data capturing laptop stop capturing about 4 hours before the crash. It had been recording for 2 1/2 days. I am thinking of replacing the ADAM module with a DL06 with an Analog input card and another ECOM100 module for communications. I will install another laptop running Linux ans start another capture run. Is the continuous UDP traffic from the c-more normal?

[derrick]

Please keep us informed of your findings.  I was about to start a project using the exact same equipment, but given your troubles I am now hesitant to do so.  The question then becomes do I avoid the DirectLogic PLC or the Advantech I/O?

[Acadien]

I have ordered equipment to attack my problem on two fronts. First, I will replace all my UTP-Cat5 cables with Sheilded TP cat5e, properly install and ground them as I would Shielded analog twisted pair (i.e. one end of the drain grounded an the other floating) this should eliminate most of the noise. The other "front" will be the replacement of the ADAM module with a DL-06 PLC + 4Ch AI module and ECOM100. This was actually my first idea in the pre-design of the system, the DL+AI+ECOM was more expensive that the ADAM-6017 module. I will still communicated with the ECOM but I will not be using Modbus TCP/IP. It will be at least 2 week until I can confirm all is well, one week to install and one week of "wiresharking". It is my understanding that the ECOM100 is more susceptible to noise that the ECOM. If this works out and is a noise issue I will have learn a great deal. I don't mind replacing the ADAM module with a PLC, although more expensive, it will be more usefull for other monitoring activities. From reading the specs, the DL-06 CPU is very similar to the DL-250-1 (PID, Float etc..).

[franji1]

From reading the specs, the DL-06 CPU is very similar to the DL-250-1 (PID, Float etc..).

Actually, it is even closer to the DL-260 CPU:

• more memory than the 250-1
• more instructions than the 250-1
• faster PLC scan times than the 250-1

[Acadien]

This is an update on the ADAM Vs ECOM trouble I was having. I am happy to say my communication network is working fine now, I have removed the ADAM module from the system and sold it on e-bay  . I now only use ECOM100 to ECOM100 communication and everything is going fine. I never found out what the exact problem was with the ECOM100 and ADAM not playing well together.

[Greg]

Acadien,

This is a long time in coming, but I may have some good news. It depends upon whether it is relevant still.

We were finally able to duplicate these weird types of errors after working on this for a very long time and we discovered some definite bugs in the ECOM100 firmware in the area of the TCP stack (thus, Modbus TCP). After extensive testing and also some field testing, we believe we have fixed all these mysterious lockups. Firmware with these fixes is available for download using NetEdit Live Update.

H0-ECOM100 v4.0.222 (or later)
H2-ECOM100 v4.0.1444 (or later)
H4-ECOM100 v4.0.1444 (or later)

Just wanted you to know in case you were still seeing rare lockups.

[Acadien]

Thanks I will update the modules firmware next week (I have a never-update-anything-on-Friday rule). I ended up replacing the ADAM module with a DL-06 with a H0-ECOM100 card. This setup has never failed. I am glad you found a Modbus related bug, since we are planning as expansion of our system to connect to a generator and a drive. I am sure it was difficult to catch, I had a laptop running wireshark for a few days, and of course the comms never failled.... I can now reconsider Modus over IP using the Ecom's. Good job guys.