Created Date: July 30,2010

Created by: clintonp

What do you get when you run the CPU access test in NetEdit 3? How many many devices are polling the PLC? I have also had alot of problems with the HO-ECOM100 acting the exact same way. It would heat up considerably and lose CPU access if 15+ devices were trying to talk to it. The only cure was to replace it with another ECOM and allow the module to cool down.

Interesting... Only one device is polling the PLC -- OK, sometimes 2, if we 're running DS5 and the PC application. The interesting part is that you mentioned temperature. I remember that once when I pulled the ECOM yesterday, I was surprised at how HOT it was.

Anyway, I have not run the CPU access test -- but I will!

Paul in Wisconsin

Created Date: July 30,2010

Created by: Bob S BN

We can most readily recreate the error by disconnecting the Ethernet cable and then reconnecting it.

The only thing that has ever cleared the problem is turning off the PLC, removing the ECOM100 from the PLC, and then re-seating it. This ALWAYS works.

I just have to throw this out here, because you told us how to recreate it, and you probably disconnect and reconnect the cable when you pull the module.

Are you sure you don't have cable/connector issues?

Just a thought,

Created Date: July 30,2010

Created by: clintonp

I just have to throw this out here, because you told us how to recreate it, and you probably disconnect and reconnect the cable when you pull the module.

Are you sure you don't have cable/connector issues?

Just a thought,

Thanks, Bob, for the idea.

I don't disconnect the cable. when I pull the module -- in fact, I leave the cable in the module and pull on the cable connector to get the module out! Further, it's disconnecting and reconnecting the cable that triggers the problem. And I'm using two different cables -- a regular one to connect to my Ethernet switch, and a crossover cable to connect directly to the laptop. Same result either way. I don't think it's the cable/connector.

Regards,

Paul

Created Date: July 30,2010

Created by: clintonp

I am having a problem with an H0-ECOM100 that seems similar to what harncw has described in his post, overworking a DL06 H0-ECOM100 with modbus tcp of 5/26.

We have been working with the ECOM100 for a while now, using it for programming (what a joy versus serial!) and for MODBUS TCP/IP. Periodically we get errors that lock-up the ECOM. I don't think that my problem is related to the speed at which I'm posting requests (as harncw is experiencing); we are polling once each second, requesting only a few words of data. And sometimes we get them when we are not using the MODBUS application, only DirectSoft5.

We can most readily recreate the error by disconnecting the Ethernet cable and then reconnecting it.

Initially, of course, we suspected software. The first problem that we noticed was that our PC code would work and then begin to report socket errors. Only later did we notice that with DirectSoft5 the link was flagged as Disabled, and DS5 could not access the PLC. Accessing the ECOM100 by entering its IP address into a browser always works -- the web page built-in to the ECOM pops right up.

Turning the PLC off and back on DOES NOT clear our problem. The only thing that has ever cleared the problem is turning off the PLC, removing the ECOM100 from the PLC, and then re-seating it. This ALWAYS works. This is very disheartening. It suggests to me something like a nasty error in the ECOM hardware/firmware that locks up, and is held locked by the supercapacitor or the battery in the PLC, something like that. But I'm talking through my hat...

We'd be grateful for a push in the right direction to troubleshoot this problem.

Thanks in advance,

Paul in Wisconsin