Modbus Temperature Device (Slave) Display Value different from Labview displayed Value

[Austyno]

When I read Register 1100, I still have same issue which is Display (=835)  is greater than labview value (=834) by value of 1. it was Register 1014 9CJC) that gave me a value (382)

[Austyno]

When I read Register 1100, I still have same issue which is Display (835)  is greater than labview value (834) by value of 1. it was Register 1014 9CJC) that gave me a value (382)

[JÞB]

So it likely is a round/truncate error.  what happens when you show 1 digit past the decimal point? is it 1 Degree or 0.1 Degrees different

[Austyno]

The value out of the register is an integer value without any decimal e.g 834 while the value on the display is shown as 83.5. So the modbus register value (834) has to be multiplied by 0.1 in the labview code in order to make it 83.4.

[JÞB]

increase to 2 digits past the decimal .  Again we are simply triing to confirm ist a round truncate error

[JensG69]

Just to make sure that it's not a bug of your LabVIEW code: Which modbus-API do you use?

Further suggestions:

Check as many different values as possible, as already stated here, it might be a bug (or feature ) of your instrument.

Regards, Jens

[Austyno]

I am using Modbus RTU API. I have a gateway for TCP connection to Master (Labview Code) and serial connection to slave devices.

[Austyno]

I did increase the digit to two places but the display was still showing me one decimal place of 83.5

[JensG69]

I am using Modbus RTU API. I have a gateway for TCP connection to Master (Labview Code) and serial connection to slave devices.

Well, I wanted to know, if you use a widely available API, like Modbus Master by Plasmionique Inc. ,  the "old" NI Modbus Library, the Modbus Library that comes with the DSC or RT toolkit, or anything else.

Regards, Jens

[Austyno]

using NI Modbus Library