PLC Unresponsive

This is an issue that one of my customers has.

  1. He will receive an email from an eWON Flexy. This tells him that the Flexy is in communication with the processor.

  2. When he goes online with the Flexy, through e-catcher, he is unable to connect to the processor (AB MicroLogix) using RSLogix 500. When he uses RSLinx to scan the addresses, he is able to see the HMI which is on the same network as the processor.
    Waiting for the network to normalize or settle itself out doesn’t seem to help. When he pings the IP address of the processor he receives a 100% packet loss – request timed out. However, he can ping the HMI.

  3. This happens with Multiple eWONs

  4. Firmware is never higher then 13.3

  5. IP address of the processor is usually 192.168.1.244 or 245

  6. There has been no communications loss between the HMI and the PLC or he would be receiving Service calls that the HMI is broken.

His questions are:

  • Are there any advanced diagnostic / secret webpages to help me diagnose ethernet communications from the office.
  • What other tips do you have in diagnosing when he has issues like this…

Hi @albrownie

What is the LAN IP address of the Ewon device? Can you send me a backup.tar file of the device with support files included?

-Tim

PLC – usually 192.168.1.244

HMI – usually 192.168.1.246

eWon – 192.168.1.53

I will work on getting the backup.tar file on Monday. Thank you!

Is the Ewon responding to pings on the 192.168.1.53?