# Modbus tcp float/real **URL:** \ **Category:** Ignition\ **Created:** [December 6, 2024, 8:31am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-float-real/99517 "2024-12-06T08:31:07Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [December 6, 2024, 9:36am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-float-real/99517/2 "2024-12-06T09:36:07Z")
> [@Issue Reading Modbus Registers with Float conversion](https://forum.inductiveautomation.com/t/issue-reading-modbus-registers-with-float-conversion/99350/2): > > Have a look here, I believe that this might be what you are looking at. Essentially a float is two words, and in certain instances if you are either word swapped or off by one register (generally caused by 0 based addressing) then you can get instances where you are looking at very similar data. Try move your register address up by one or down by one and see if it affects it. If that doesn't work, try setting the "Reverse Word Order" setting in the Modbus driver. Then try moving the address… This might be what you are looking at, your least significant bits might be overlapping with a value that is changing. --- _[View the full topic](https://forum.inductiveautomation.com/t/modbus-tcp-float-real/99517)._