How to use the tool to get an address?

[SgtFoose]

Hi,

So I used the scanner on a project to scan for the used addresses. So far happy with the tool, useful feature in our situation.
Now I have one address written on paper out of many that does not work. In this case it's an HVAC system TCPIP with 8 chiller units. I know the IP and the Port and the scan did find a match on the expected register address. Unfortunately, out of 60 units, one wall mounted HVAC keypad does not want to work with my code for automaton. The wall mounted keypad does work and the chiller functions, so let's take for granted the whole system works as intended, but my datasheet is not up to date and I'm using the wrong Modbus register for my integration. Can this tool help me to find the address when I use the wall keypad to change the room temperature and capture the register address? If yes, please advise!

[SgtFoose]

[serhmarch]

Hi,

If I understand the situation correctly, you need to find the Modbus register that is responsible for setting the parameter.

The Modbus protocol itself does not provide information describing the data stored in the memory cells of the device (unlike, for example, OPC UA).
To understand what information is stored in the device register, you need a datasheet from the device developer.

But you can do certain things by indirect methods. If the value in the register is known (or approximately known) and the location of the register is approximately known (for example, it can be in the address range from 1 to 1000), then you can add these registers to the DataView list, push Run button and find the value that may correspond to the temperature setpoint, etc.

[SgtFoose]

Thanks you! That worked well for me 💪