Modbus TCP Tag Not Reading, What Could Be the Reason?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • HMIDesign
    Junior Member
    • 11.08.2025
    • 7

    #1

    Modbus TCP Tag Not Reading, What Could Be the Reason?

    Hello everyone, I have started a new project and I am setting up a SCADA system. I am trying to read data from a device using the Modbus TCP protocol. I am sure that I have entered the device address and port settings correctly. In my SCADA software, I created a Modbus tag, but the tag value is showing as '0'. I can see that the device is communicating over the TCP port, but the data is not coming through properly. What could be the possible reasons for this? Could it be an issue related to the device's register address? Or could it be a wiring problem?
  • Technical Support
    Member
    • 11.08.2025
    • 40

    #2
    Entering the device’s IP and port information correctly establishes the initial communication phase with the tag. A critical aspect to consider here is the frame containing the tag. The frame's start address combined with the tag’s Modbus address determines the actual Modbus register address being read.

    Do not input the Modbus address directly into the tag’s Modbus address property. Instead, adjust this value by taking into account the frame’s Start Address parameter. By doing so, the accurate tag value will be reflected correctly on the server.


    Click image for larger version

Name:	Frame_StartAddress.png
Views:	9
Size:	13.6 KB
ID:	100

    Comment

    Working...