Bug? TRB245 GPS modbus registers shows different values

Networking Solutions Issue
1

TRB245 shows different decimal coordinates than WebUI Map

Firmware updated to 00.07.14.4. Factory reset also done

Same also with older 7.13 firmware. Modbus data is not correct for GPS coordinates.

WebUI Map shows correct Coordinates (Satellites 4, Accuracy 2.1)

Latitude x.057317

Longitude y.442726

Reading registers 143 & 144 Float / from Modbus

Latitude x.002205

Longitude y.389324

Checked also from Teltonika

Reading directly Teltonika own modbus data from WebUI (Modbus TCP Client configuration).

register 143, count 4: ( 32b Float, order 3,4,1,2)

Request successful, result: x.002205,x.389324

GPS date (Ascii, register 163 / count 16)

Request successful, result: “\u0000\u00002026-02-26 15:52:30\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000”

Why registers 143 and 144 have different numbers values than WebUI MAP shows?

(WebUI map shows correct place, but Modbus Coordinates points several kilometers away)

p.s Checked data also from SSH.

gpsctl -i shows coordinate x.057289

gpsctl -x shows coordinate y.442649

Do I need to code custom registers for correct data?

(Code sample for this would be good and how to run code behind.)

This looks like that build in modbus data have error

3

Greetings,

Could you please try reading the register using the 32-bit float data type and 1,2,3,4 byte order ? Selecting this specific configuration was necessary to get accurate values on a RUTX device.
In the meantime, I will conduct further testing on a TRB2XX device and let you know the results.

Best Regards,
Justinas

4

Only byte order 3,4,1,2 gives meaningful data

All others are byte orders are zero or almost zero float numbers. (read tested on Teltonika and Schneider Modbus Client)

5

Problem solved. It was byte wrong byte order indeed, but also reading from register 142 same time. Not sure why didn’t notice allready before as tryed allmost every combination for reading values.