# Modbus TCP - 4 Consecutive Registers with Double Conversion **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [June 19, 2025, 4:25pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-4-consecutive-registers-with-double-conversion/107584 "2025-06-19T16:25:48Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Liam\_Dietrich](https://avatars.discourse-cdn.com/v4/letter/l/b5a626/32.png) [@Liam\_Dietrich](https://forum.inductiveautomation.com/u/Liam_Dietrich)\ **Post date:** [June 19, 2025, 4:25pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-4-consecutive-registers-with-double-conversion/107584/1 "2025-06-19T16:25:48Z")
Hi, I am attempting to read 4 consecutive registers via Modbus. I currently have the communication working properly for 2 consecutive registers, using the **HRF** designator. _Example:_ [DEVICE\_NAME]1.HRF4667 But when I attempt to access a value using the **HRD** designator, I am receiving a value of 0 (I am expecting a non-zero value). _Example:_ [DEVICE\_NAME]1.HRD2021) Is there anything I may be missing? Or is the only possibility I am pointing to the wrong address? _Ignition Version 8.1_ _Modbus TCP Driver_ ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 19, 2025, 4:30pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-4-consecutive-registers-with-double-conversion/107584/2 "2025-06-19T16:30:34Z")
It is also possible that the device doesn't use the word order for quad-word values that Ignition is expecting. Try reading the four registers as unsigned integers, and combine them in various orders using an expression, and passing that 64-bit value to [Double.longBitsToDouble()](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Double.html#longBitsToDouble(long)).