# Modbus Address UINT32 Read Problem

**URL:** <https://forum.inductiveautomation.com/t/modbus-address-uint32-read-problem/27828>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [August 28, 2019, 9:10am UTC](https://forum.inductiveautomation.com/t/modbus-address-uint32-read-problem/27828 "2019-08-28T09:10:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuhaohf](https://avatars.discourse-cdn.com/v4/letter/y/8491ac/32.png) [@yuhaohf](https://forum.inductiveautomation.com/u/yuhaohf)\
**Post date:** [August 28, 2019, 9:10am UTC](https://forum.inductiveautomation.com/t/modbus-address-uint32-read-problem/27828/1 "2019-08-28T09:10:37Z")

</div>

If ModbusTCP address such as attachment JPG file ,  
 ![Problem](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/c1121e5b0de902bdcfef15b4f37eb5d8adfaf480.jpeg)

Ex: 44001=1 / 44002=2  
Count\_1 Value=131073=(65536x2+1)

How to setting ModbusType in gateway Config \> Opcua \> Devices \> Address Configuration?

Thanks for help~

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 28, 2019, 3:50pm UTC](https://forum.inductiveautomation.com/t/modbus-address-uint32-read-problem/27828/2 "2019-08-28T15:50:45Z")

</div>

The address mapping would look something like this - you may need to play with settings on the device for zero based addressing, and you may need to change the ‘Unit ID’ to match your device.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/5e16b7fac15b659cbf96f4fb633711db24ba8d98.png)

---

<div class="post-metadata">

**Author:** ![yuhaohf](https://avatars.discourse-cdn.com/v4/letter/y/8491ac/32.png) [@yuhaohf](https://forum.inductiveautomation.com/u/yuhaohf)\
**Post date:** [August 29, 2019, 2:17am UTC](https://forum.inductiveautomation.com/t/modbus-address-uint32-read-problem/27828/3 "2019-08-29T02:17:06Z")

</div>

Thanks for you replay.

I have two case,now

case 1: Hi-Word before Lo-word ,count value is correct

 ![UINT32%E6%AD%A3%E5%B8%B8%20](https://us1.discourse-cdn.com/inductiveautomation/original/2X/f/f3739caa2dfe26c249bc13ca1817781d41f80a02.jpeg)

case 2: Lo-Word before Hi-word ,count value is wrong

 ![UINT32%E9%8C%AF%E8%AA%A4%20](https://us1.discourse-cdn.com/inductiveautomation/original/2X/b/b9be305291cd23a808219dfe53de5e7854b2d4fa.jpeg)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 29, 2019, 2:34am UTC](https://forum.inductiveautomation.com/t/modbus-address-uint32-read-problem/27828/4 "2019-08-29T02:34:06Z")

</div>

You can change the Word Order setting in the driver, but it applies to all multi-word values for that driver instance. You can’t have some values that are “word-big-endian” and some that are “word-little-endian”.