rjm21 (Customer) asked a question.

June 18, 2020 at 3:48 PM
P001: EA3-T4CL to Click Ethernet won't communicate.

I have several CLICK Ethernet PLC and EA3-T4CL combo systems running. I've never had communication issues between the PLC and HMI until now. We recently purchased an EA3-T4CL (We'll name this HMI1) and a C0-12DD1E-D to communicate together via ethernet. The HMI1 will not connect, always showing the P001: PLC COM Time Out error. Changing the IP Address and/or the TCP port makes no difference. I have verified that the HMI1 is set to communicate to the correct IP address and TCP port via the PLC protocol Automation Direct CLICK Ethernet.

 

I took this HMI1 and tried to connect it to two other Click Ethernet systems (HMI 2 and HMI3, also EA3-T4CLs) that are currently successfully communicating with their own EA3-T4CL's. The new HMI1 would not communicate, still giving the P001 error.

 

I also took the HMI2 and HMI3 from the two working Click Ethernet systems and was able to get them to communicate with the C0-12DD1E-D. This leads me to believe there is a problem with the new HMI1.

 

One thing I've noticed is on a successfully communicating Ethernet system, the PLC's Green Ethernet port light will flash rapidly. When I use this new HMI, the PLC's Ethernet port lights will not flash, but stay lit up solid green and amber.

 

I then restored this new HMI1, uploaded a successful program that is communicating with a BRX PLC via Ethernet. This worked. So I took the HMI (HMI4) that was previously connected to the BRX, uploaded a CLICK program and changed all the necessary settings, and could not get this one to connect to any of the CLICK ethernet PLCs. Same issue as HMI1.

 

I have a small hunch that the CLICK Ethernet PLC Protocol is not being successfully transferred to the HMI. All PLCs and HMIs are running the newest firmware revisions.

 

I have quadruple checked that the PLC protocol, TCP port, and IP address are correct in both the C-more programming software and Click programmnig software. I've tried using different PC's and different Ethernet cables as well.

 

Can you think of anything that I'm missing?

  • 40 answers
  • 3.73K views

  • ADC_HMI_PE (AutomationDirect)

    What version Software are you using?

     

    We found an issue in 4.35 with the power up ARP announcement on the EA3 Ethernet. This was corrected in version 4.40.

    Selected as Best

  • kewakl (Customer)

    When you swap the offending panel in an existing network, how are you powering the panel?

    --What supply voltage is the panel connected to--

    • rjm21 (Customer)

      I simply swap using the green terminal plug that comes with the EA3-T4CL. No rewiring necessary. All systems powered with 24VDC

      • CLICK_CMORE_SETTINGS

  • kewakl (Customer)

    Are you transferring project via ethernet/USB?

    • rjm21 (Customer)

      Via USB, which appears to be working.

  • Garry (Customer)

    Hi rjm21,

    There seems to be something not correct in the firmware of the EA3.

     

    I have the same hardware so I tried out a simple experiment.

    The current version of software is V4.35.0.0.

    Communication Settings:

    Click to EA3 T4CL 1

    Click to EA3 T4CL 2

    I put a simple program into the EA3-T4CL that would toggle Y6 on the Click PLC using the Ethernet Click driver.

    Click to EA3 T4CL 1

    The program worked as expected. See the picture above. IP addresses were static, but this initial connection was going through a DHCP server on the network. I then disconnected the Ethernet cable and plugged it directly into the PLC Ethernet connection. (Direct)

    The program still worked.

    I then cycled power to the PLC and HMI.

    I could no longer connect and the error message was the following:

    Click to EA3 T4CL 2

    It seems with a direct connection the HMI will not communicate with the PLC.

    Regards,

    Garry

    Expand Post

    • rjm21 (Customer)

      Thanks for trying this, Garry. What I find really confusing/frustrating is that I put firmware rev 4.32 on the EA3-T4CL and received the same errors.

       

      My next thought was that there was something physically wrong with the ethernet port on the HMI, but I know this is false because I was able to get the HMI to communicate properly via ethernet with a BRX PLC.

       

      I'm also perplexed how I have two other CLICK ethernet + EA3-T4CL systems communicated flawlessly via direct ethernet. All systems running the latest firmware revisions.

      Expand Post

      • Garry (Customer)

        Hi rjm21,

        That is strange.

        Hopefully someone from AD will shed some light on this situation.

        Regards,

        Garry

  • kewakl (Customer)

    For giggles, (if you have one) can you put an ethernet switch in the mix, to test the idea of direct connection failing?

    Maybe there could be an issue with connection-type detection..

    • Garry (Customer)

      Hi kewakl,

      I do not have an extra ethernet switch to try. However, once communication is established using the network with a DHCP server, I can disconnect and connect the ethernet cable directly and communication is still established.

      Upon powering down and restarting the system, communication is lost.

      This holds true the other way as well. If I have a direct connection and there is no communication, I switch to the network with a DHCP server and there is no communication.

      Upon powering down and restarting the system, communication is restored.

      Regards,

      Garry

       

      Expand Post

    • rjm21 (Customer)

      I did happen to have an ethernet switch. This did not resolve the issue.

10 of 40

 

Did this information resolve your issue?