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.

Eric Black Mr. Eric

After reviewing our addresses, there is an odd registers and even registers for real data type variables in the same request, but if I can not change the addresses, how can I solve this issue ?, so that Plant Scada splits request to 2 requests?

Eric Black Mr. Eric

After reviewing our addresses, there is an odd registers and even registers for real data type variables in the same request, but if I can not change the addresses, how can I solve this issue ?, so that Plant Scada splits request to 2 requests?

Just add the letter G before the tag address to force that variable to be read individually. That slows communications so you don't want to do that for too many variables. You could just do it for the even numbered REALs and LONGs, for example, or just the problem ones.

Here's a clip from the MODNET help page on Data Types:

Thank you so much, it is working after adding the letter G to the address.