# Modbus driver fail to read HRUS register followed by HRF register (32bit float) **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [June 20, 2023, 4:19pm UTC](https://forum.inductiveautomation.com/t/modbus-driver-fail-to-read-hrus-register-followed-by-hrf-register-32bit-float/75287 "2023-06-20T16:19:19Z")\ **Posts on this page:** 1\ **Showing post:** 14
**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:** [March 10, 2025, 1:02am UTC](https://forum.inductiveautomation.com/t/modbus-driver-fail-to-read-hrus-register-followed-by-hrf-register-32bit-float/75287/14 "2025-03-10T01:02:02Z")
I finally got around to addressing this feature. My latest beta will split access requests to abutting configured address ranges, as noted here: > [@Automation Professionals' Advanced Modbus Driver](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/82): > > Well, I didn't declare it production grade, as I found a couple minor items in the DriverAdapter to Device conversion. I also refactored my CSV versus binary serialization format in the internal database to make it easier to excise the latter in v8.3. Which enabled a feature I've been cogitating on for a while: mitigating the bad behavior of some devices when abutting register ranges cannot be spanned. My config will no longer merge configured ranges of addresses that abut without overlapping… Presumably too late for @mazeyrat, but if others run into it, they won't be stuck. --- _[View the full topic](https://forum.inductiveautomation.com/t/modbus-driver-fail-to-read-hrus-register-followed-by-hrf-register-32bit-float/75287)._