Created Date: July 11,2018

Created by: gottspeed

I'm having a hell of a time figuring out how to get doubles and floats to display properly coming from the click to VTScada and myScada HMI applications. Modscan shows the proper value, but the value I'm reading in VT Scada / myScada is completely different. I 've tried adjacent memory addresses, and changing byte order parameters to no avail, so, I hope to understand the standard endianness on the Click better so that I can troubleshoot this issue.

How are bits oriented in bytes on the Click, and how are bytes oriented in words in the Click?

Created Date: July 11,2018

Created by: franji1

The byte order may be correct because of the Modbus specification requirements for 16 bit registers (not sure what it is, but both Master and Slave, if following the protocol, know what to do based on THEIR endian-ness).

However, there is no Endian-ness at the WORD order (so DWORDs and 32 bit FLOATs may be off). Hence try just swapping WORDs (keeping the BYTEs as-is).