# AB Micro820, Modbus TCP Addressing on Ignition Edge

**URL:** <https://forum.inductiveautomation.com/t/ab-micro820-modbus-tcp-addressing-on-ignition-edge/84119>\
**Category:** General Discussion\
**Created:** [January 11, 2024, 4:10pm UTC](https://forum.inductiveautomation.com/t/ab-micro820-modbus-tcp-addressing-on-ignition-edge/84119 "2024-01-11T16:10:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Blake\_Guidry](https://avatars.discourse-cdn.com/v4/letter/b/a5b964/32.png) [@Blake\_Guidry](https://forum.inductiveautomation.com/u/Blake_Guidry)\
**Post date:** [January 11, 2024, 4:10pm UTC](https://forum.inductiveautomation.com/t/ab-micro820-modbus-tcp-addressing-on-ignition-edge/84119/1 "2024-01-11T16:10:13Z")

</div>

Hi,  
I am trying to pull values from this Allen Bradley Micro 820 into a test project for Ignition Edge.  
I have tested separately A INT value and BOOL value successfully, and read the correct value.  
But I am having trouble pulling the correct value for DINT and REAL tags.

The Green highlights are the INT and BOOL Ive been testing,  
Yellow are the REAL / FLOAT and DINT that I have not able to pull the correct value.  
For "ModbusTest" on the PLC I am sending value "10" and reading "655360"  
For "ConductVal" on the PLC I am sending value "4.5" and reading "2.316E-41"

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/a/eac16c7b20e3208c7473f33e1d04e89469e881f2.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/a/9a9519eb97dc985f8b57e137775858de6f5e91e6.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/f/af641ee3a7d7df5da81b1adf0b2ac7c8f42367ae.png)

Any suggestions on what I am missing? tried different address setups with no success.

---

<div class="post-metadata">

**Author:** ![Blake\_Guidry](https://avatars.discourse-cdn.com/v4/letter/b/a5b964/32.png) [@Blake\_Guidry](https://forum.inductiveautomation.com/u/Blake_Guidry)\
**Post date:** [January 11, 2024, 4:10pm UTC](https://forum.inductiveautomation.com/t/ab-micro820-modbus-tcp-addressing-on-ignition-edge/84119/2 "2024-01-11T16:10:50Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/7/a7a059c211fe6b715abbf481233d188c5c00414e.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:** [January 11, 2024, 4:20pm UTC](https://forum.inductiveautomation.com/t/ab-micro820-modbus-tcp-addressing-on-ignition-edge/84119/3 "2024-01-11T16:20:21Z")

</div>

First, abandon the address mappings. Only necessary for browsing with the native driver.

Instead, create Ignition tags with manually-constructed OPC Item Paths, following this documentation:

[https://docs.inductiveautomation.com/display/DOC81/Modbus+Addressing#ModbusAddressing-ManuallyCreateanAddressforaSingleTag](https://docs.inductiveautomation.com/display/DOC81/Modbus+Addressing#ModbusAddressing-ManuallyCreateanAddressforaSingleTag)

Note the use of `HRI` instead of `HR` to get 32-bit handling at a given starting address. Similar for other conversion types.

If you need a node address other than zero, it goes before that type prefix, with a dot delimiter.

If you encounter other strange behaviors (off-by-one addresses, scrambled conversions, odd errors when multiple tags are subscribed), examine the device's connection options, particularly:

- Word swapping
- Zero-based addressing
- Spanning gaps
- Maximum request sizes

[https://docs.inductiveautomation.com/display/DOC81/Connecting+to+Modbus+Device#ConnectingtoModbusDevice-DeviceConnectionSettings](https://docs.inductiveautomation.com/display/DOC81/Connecting+to+Modbus+Device#ConnectingtoModbusDevice-DeviceConnectionSettings)

---

<div class="post-metadata">

**Author:** ![Blake\_Guidry](https://avatars.discourse-cdn.com/v4/letter/b/a5b964/32.png) [@Blake\_Guidry](https://forum.inductiveautomation.com/u/Blake_Guidry)\
**Post date:** [January 11, 2024, 5:00pm UTC](https://forum.inductiveautomation.com/t/ab-micro820-modbus-tcp-addressing-on-ignition-edge/84119/4 "2024-01-11T17:00:44Z")

</div>

I got it to work with the manually constructed OPC Item paths.. thank you.

---

<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:** [January 11, 2024, 9:03pm UTC](https://forum.inductiveautomation.com/t/ab-micro820-modbus-tcp-addressing-on-ignition-edge/84119/5 "2024-01-11T21:03:23Z")

</div>

Also, be on the lookout for a native driver for these PLCs coming soon (at least Beta is coming soon). This should simplify things hopefully in time for your project since you're just testing it out for now.

---

<div class="post-metadata">

**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\
**Post date:** [January 30, 2024, 4:12pm UTC](https://forum.inductiveautomation.com/t/ab-micro820-modbus-tcp-addressing-on-ignition-edge/84119/6 "2024-01-30T16:12:02Z")

</div>

any examples of your mappings?
