# Modbus Addressing and combing 32 bit addresses

**URL:** <https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403>\
**Category:** Ignition\
**Created:** [November 27, 2023, 10:56pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403 "2023-11-27T22:56:40Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Logan\_Krohn](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Logan\_Krohn](https://forum.inductiveautomation.com/u/Logan_Krohn)\
**Post date:** [November 27, 2023, 10:56pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/1 "2023-11-27T22:56:40Z")

</div>

I am trying to correctly address these tags that cover a range of addresses. I have tried HR(float) and IR(float) with no luck. Can anyone offer some help or point me in the right direction on how to wrap my head around how addressing is supposed to work? Thank you!

 ![EC1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/0/209e9a6c836c5eb6123e822900a14450c0ab9de9.png)  
 ![EC2](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/3/a38d2cdcf6316f362cb89a8174038aae69719d02.png)  
 ![EC3](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/a/7a9cfdf5cbc5f7da21acb8665d170ee329ddeb2b.png)  
 ![EC4](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/6/46c231e4af985231421657850984e4d4ad665cf0.png)

---

<div class="post-metadata">

**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:** [November 27, 2023, 11:00pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/2 "2023-11-27T23:00:18Z")

</div>

Please show the documentation for that device. (The address mappings pages are not recommended any more--just use the documented address syntax on your tags' OPC Item Path.)

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [November 28, 2023, 8:05pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/3 "2023-11-28T20:05:00Z")

</div>

That's a Micro8xx controller (which I'm patiently waiting for the native driver to be released), and you'll have to turn on reverse word order, and turn off span gaps in the modbus driver advanced settings. I also reduced my Max Holding Registers per Request to 32.

Once you have those settings changed, like @pturmel mentioned, don't use the address mappings and do the addressing directly in your tags/UDTs. I'm also assuming your tags like PT\_15A\_Val si actually an array of 30 REALs? I don't know that I've ever used BOOLs with it, but you should be able to read those with something like HR1 for TAS\_Panel\_Val and your reals would be HRF80 for the first item of PT\_15A\_Val

---

<div class="post-metadata">

**Author:** ![Logan\_Krohn](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Logan\_Krohn](https://forum.inductiveautomation.com/u/Logan_Krohn)\
**Post date:** [November 30, 2023, 10:41pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/4 "2023-11-30T22:41:16Z")

</div>

Thank you for the help! I applied the settings changes you mentioned and have been trying to correctly address the tags without using the OPC item browser. Is there any documentation out there to help me understand? I have tried variations of HR1, HRF80, IR1, and IRF80 for my addresses. My syntax might be wrong.

 ![Capture1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/e/ae532d41dd3fc1fc0aa0c308f76ea75805e3d8b3.png)  
 ![Capture](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/0/60d4e86622576faa0edeb755255861d91fae4708.png)

---

<div class="post-metadata">

**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:** [December 1, 2023, 1:57am UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/5 "2023-12-01T01:57:35Z")

</div>

You may need a slave unit number in your addresses. Ignition's driver defaults to unit #0 if not included.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [December 1, 2023, 3:11am UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/6 "2023-12-01T03:11:17Z")

</div>

I just checked my tag config and you will need the modbus ID, so you'd need 1.HRF1

For example, here's the first few modbus mappings I have:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/d/0da6ff80bed7bc980b5b0be9e8e70601d51dec95.png)

To read 400001 here's my OPC Item Path:

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/b/3bdc487504c897008c2f9de724bb576c086e3c4b.png)

---

<div class="post-metadata">

**Author:** ![Logan\_Krohn](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Logan\_Krohn](https://forum.inductiveautomation.com/u/Logan_Krohn)\
**Post date:** [December 1, 2023, 10:34pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/7 "2023-12-01T22:34:43Z")

</div>

Thanks again! This might be a dumb question but where do I find or distinguish the modbus ID?

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [December 1, 2023, 10:35pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/8 "2023-12-01T22:35:32Z")

</div>

I believe on these Micro8xx controllers it will always be 1.

---

<div class="post-metadata">

**Author:** ![Logan\_Krohn](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Logan\_Krohn](https://forum.inductiveautomation.com/u/Logan_Krohn)\
**Post date:** [December 1, 2023, 10:35pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/9 "2023-12-01T22:35:49Z")

</div>

Thank you sir.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [December 1, 2023, 10:44pm UTC](https://forum.inductiveautomation.com/t/modbus-addressing-and-combing-32-bit-addresses/82403/10 "2023-12-01T22:44:56Z")

</div>

One other thing I just noticed you were doing is using coil addresses (each address is a single bit) instead of holding registers. Is this what you intended? Holding registers are more typically used, and as you can see in mine we used INT arrays for packing our individual bits.

That could be part of your issue especially with the REALs. Start your REAL at 400001 and it will only use 2 16-bit addresses instead of 32. So your next one would be 400003, etc.

Edit: To read the 400001 REAL value, you'd use 1.HRF1
