group of IO/Devices & MODNET1 mixing registers

Another possibility is the address mapping in the modbus device you're communicating with has a mistake in it and Plant SCADA is reading the correct register but it does not contain the value you expect. You could use a Modbus TCP test client to verify what value is actually in address 422119.

Mr. Eric

Actually I am using the ini parameter CheckAddressBoundary = 0 to neglect the compile error you was talking about (Odd and Even Registers), and to be clear, the display order of bytes is 100% correct because i am reading another registers from the same device, both long and real data types, the modbus client is reading the right value from device in the right register 422119, so it is a plant scada issue, thank you so much in advance.

Mr. Eric

Actually I am using the ini parameter CheckAddressBoundary = 0 to neglect the compile error you was talking about (Odd and Even Registers), and to be clear, the display order of bytes is 100% correct because i am reading another registers from the same device, both long and real data types, the modbus client is reading the right value from device in the right register 422119, so it is a plant scada issue, thank you so much in advance.