MiSp (Customer) asked a question.

January 25, 2023 at 12:24 PM
Button on Weintek HMI not shown when linked to Click PLC (Modbus TCP)
But I have no communication error..

Hi there,

 

Hopefully someone can help me out with a problem I have with a Click PLC C0-10DD2E-D connected to a Weintek MT8071iE HMI through ethernet (modbus).

 

I've setup the Click PLC ethernet port (port 1) with Modbus TCP and enabled the Modbus TCP Server (TCP Port 502).

On the Weintek HMI I've added the Koyo click V3 modbus TCP/IP device with port number 502 (UDP not selected. Also tried with UDP on, but no luck).

Both are on the same IP range with the PLC on 10.1.2.20 and the HMI on 10.1.2.10.

 

On the HMI I’ve created 2 buttons. One to toggle a Bit (C20) on the Click PLC and one to change a Bit on the HMI it self. When I write this to the HMI, it runs, but the button to change something on the Click PLC does not show. The button to change something on the HMI itself does show and I’ve no communication error message on the HMI.

 

I’m probably missing something, but can’t see what. So maybe someone can give some ideas i can try.

 

Many thanx in advance.

Regards,

Michiel

  • 13 answers
  • 965 views

  • MiSp (Customer)

    Took me some time, but I know what i did wrong.

    In "System Parameter Settings" > "device settings" I set Location to "Remote" in stead of "Local". (I'm using Koyo click V3 modbus TCP/IP driver)

    Now it works fine.

    Hopefully this answer helps someone else as well.

     

    Thanks to you all. Kind regards,

     

     

    Expand Post
    Selected as Best

  • Todd Dice (Customer)

    I'm not completely understanding your question, however, with Modbus the address you're reading/writing to can be off by 1 in either direction.. So, for example, if you were writing to address 41002, try instead writing to 41001 or 41003.

    • MiSp (Customer)

      Hi Todd,

       

      Thanks for your answer.

       

      What you mention I've have heard before, but can't recall where.

      With the “Koyo Click V3 Modbus TCP” driver I can not put in the modbus address itself.

      Instead I can choose (like in the Click software) what I want to read or write e.g. C (bit marker) and the number between 1 and 2000. I tried multiple options, but no luck yet..

       

      Expand Post

  • facorp (Customer)

    I'm experiencing the same issue as above. Though, I'm using the Koyo Click Ethernet driver and not the Modbus TCP.

    The buttons or objects (Bit Lamp, Numeric Display, etc) do not show on the actual HMI screen.

    Static text on the other hand will show up just fine.

    Click Software v3.41

    EBpro v6.08.01.296

  • ADC Community_02 (Automationdirect.com)

    No experience with Weintek HMI's. However, is there a visibility option for these objects? 0 = OFF 1 = ON ?

    https://www.youtube.com/watch?v=svqPTx_TXe4

     

    Does the software have a simulator? If yes, when you run the simulator are the objects visible?

    • MiSp (Customer)

      Like facorp, I've no issue with the visibility settings. But in the online and offline simulator the buttons linked to the click does not show up. Everything else not linked to the click driver shows up fine.

  • facorp (Customer)

    No issue with the visibility settings.(Nothing is hidden based on user security level or anything of the sort).

    Yes, the simulator works as intended

    (All objects show on screen(s).

  • facorp (Customer)

    UPDATE.

    I tried the same setup on an older VM with EBpro v6.05 and Click v3.41.

    Same issue with objects not showing.

     

    I went back to the original setup (as per my 1st post) using EBpro v6.08.01.296 & Click v3.41 with FW v3.41

    I made a cable and used ComPort 2 on the Click part No. C0-10DD2E-D

    When using the serial setup everything works just fine.

    All objects show on the HMI and I can verify functionality (button press, registers working as expected).

     

    Seems to be an issue with the Ethernet Driver, at some point something has changed (not sure if it is the newer version of click or a FW version or what)

     

    If anyone can follow up it would be greatly appreciated.

    Expand Post

    • MiSp (Customer)

      I've the same experience as facorp. Connected to Com Port 2 it works fine.

  • ADC Community_02 (Automationdirect.com)

    In version 3.10 an improvement was made:

    "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."

  • MiSp (Customer)

    Yes, thats right.

    I've tried Modbus TCP 502 and also UDP 25425 as well to be sure. But nothing changes, the buttons does not show on screen.

10 of 13

 

Did this information resolve your issue?