Ivgeny (Customer) asked a question.

September 12, 2022 at 11:09 PM
No communication between CLICK PLC and Weinteck HMI (Ethernet)

Hello,

Need help with troubleshoot my connection of CLICK (Ethernet) C0-11DD2E-D with Weintek PLC.

According to instructions, everything is pretty straight forward but the HMI says that "Device no response". I made an IP settings in both sides successfully, checked ping OK

Did I missed something in the configuration ?

all my ports in PLC are busy. I connected online with my PC via port-2 (rs232). PLC connected to VFD via port-3 modbus, and it supose to be connected to HMI via port-1 (Ethernet)

 

Capture3Capture2CaptureThanks

  • 3 answers
  • 441 views

  • ADC TechnologyGroup_05 (AutomationDirect)

    Release notes from CLICK Programming Software:

    • Version: 3.10
    • Date: 07/21/2021

     

    Improvement:

    1. ...
    2. Improved Security by disabling external communications of 3rd party HMIs using the proprietary programming port on UDP 25425. These devices should be reconfigured to use ModbusTCP 502.
    3. ...

     

    Whereas your 3rd party device is a PLC rather than HMI, the statement is still relevant. Modbus TCP on port 502 should be used for communication between the two devices.

     

    CLICK_V3_10_ReleaseNotes_Screenshot

    Expand Post
    Selected as Best

  • Orion HE (Customer)

    I've never connected the two together, but is your subnet mask configured correctly on the Weinteck? It's the only thing that I couldn't verify from a simple networking standpoint.

  • ADC TechnologyGroup_05 (AutomationDirect)

    Release notes from CLICK Programming Software:

    • Version: 3.10
    • Date: 07/21/2021

     

    Improvement:

    1. ...
    2. Improved Security by disabling external communications of 3rd party HMIs using the proprietary programming port on UDP 25425. These devices should be reconfigured to use ModbusTCP 502.
    3. ...

     

    Whereas your 3rd party device is a PLC rather than HMI, the statement is still relevant. Modbus TCP on port 502 should be used for communication between the two devices.

     

    CLICK_V3_10_ReleaseNotes_Screenshot

    Expand Post
    Selected as Best

  • Ivgeny (Customer)

    Thank you ADC, for this info

     

    I'll try modbus TCP.

 

Did this information resolve your issue?