# Node-red-contrib-modbus - Errors when polling numerically high registers

**URL:** <https://discourse.nodered.org/t/node-red-contrib-modbus-errors-when-polling-numerically-high-registers/74892>\
**Category:** Industrial\
**Created:** [8 February 2023 15:15 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-errors-when-polling-numerically-high-registers/74892 "2023-02-08T15:15:54Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)\
**Post date:** [13 February 2023 20:10 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-errors-when-polling-numerically-high-registers/74892/6 "2023-02-13T20:10:39Z")

</div>

Im glad you found the solution to the problem 👍  
now that you mention it i read a couple of times on the forum that some devices start their register numbering with an offset of 1 ([example](https://discourse.nodered.org/t/can-not-get-float-value-from-energy-meter-using-modbus-rtu-serial/62921/12))

does that mean you need to make corrections to all reads you were making ?  
even the lower number register ones ? For example 40,001 you should have actually started reading from 0 ?

---

_[View the full topic](https://discourse.nodered.org/t/node-red-contrib-modbus-errors-when-polling-numerically-high-registers/74892)._