# MiR AMR Modbus TCP Addressing **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [June 9, 2023, 1:11pm UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827 "2023-06-09T13:11:28Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Alex\_Guyer](https://avatars.discourse-cdn.com/v4/letter/a/a4c791/32.png) [@Alex\_Guyer](https://forum.inductiveautomation.com/u/Alex_Guyer)\ **Post date:** [June 9, 2023, 1:11pm UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827/1 "2023-06-09T13:11:28Z")
Has anyone had experience with correctly addressing a MiR robot? I have it connected via the Modbus TCP driver and can read all of the diagnostic tags. I have enabled Modbus in the MiR setup. There are registers (bools) for missions, and PLC holding register for Ints and Floats. There is some documentation of the addressing, but so far I have not yet figured out the correct addressing setup. Any recommendations? ![MiRmenu](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/3/f37231417848678524ce63a2b1efa7414b6a1eff.png) ![MiRdocs](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/2/f22beb92d85906586b5a7a794e716ef7abaadad8.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [June 9, 2023, 1:17pm UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827/2 "2023-06-09T13:17:23Z")
Create an OPC tag in Ignition. Try addresses like: - `[DeviceName]HR1` - `[DeviceName]HRF101` - `[DeviceName]C1` - `[DeviceName]1.HR1` - `[DeviceName]1.HRF101` - `[DeviceName]1.C1` ---
**Author:** ![Alex\_Guyer](https://avatars.discourse-cdn.com/v4/letter/a/a4c791/32.png) [@Alex\_Guyer](https://forum.inductiveautomation.com/u/Alex_Guyer)\ **Post date:** [June 9, 2023, 1:59pm UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827/3 "2023-06-09T13:59:18Z")
I'm getting some information with almost any of those configurations, but it doesn't seem to be the correct information. ![TagTrial](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/7/37e4a368a37bd5666a7b5aaebad1a5eba878cc81.png) Ideally, I'm wanting to get all of the addressing set up then derive tags from it. (I've just been checking via the OPC Quick Client after making addressing/setup changes) So far, no configuration of addressing, start/end, step, type, or ID have gave me correct information. ![ModbusSetup](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/7/d765be056ff309e9f161463a8802a998d2c56140.png) ---
**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 9, 2023, 2:21pm UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827/4 "2023-06-09T14:21:43Z")
When providing a Modbus address to Ignition, you must omit the type prefix digit ('0' for coils, '1' for digital inputs, '3' for analog inputs, and '4' for holding registers), whether you are using the mappings or directly entering OPC item paths with IA's syntax. In other words, typical register address `41001` =\> IA `HR1001` and so forth. This is necessary in part because the underlying protocol supports a 16bit offset, which means the prefix could be followed by five digits in some cases instead of four. ---
**Author:** ![Alex\_Guyer](https://avatars.discourse-cdn.com/v4/letter/a/a4c791/32.png) [@Alex\_Guyer](https://forum.inductiveautomation.com/u/Alex_Guyer)\ **Post date:** [June 9, 2023, 3:19pm UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827/5 "2023-06-09T15:19:44Z")
Got it, Thank you. That works great when configuring the OPC tag. ![WorkingTag](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/e/ee9cb1e99fa0d2233d183a1c937d63227873b7ad.png) I've still had not success setting up the address configurations. Any ideas on that? ---
**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 9, 2023, 3:41pm UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827/6 "2023-06-09T15:41:39Z")
> [@Alex\_Guyer](#): > > setting up the address configurations I don't use them. But then, I have [my own Modbus module](https://inductiveautomation.com/moduleshowcase/module/automation-professionals-llc-advanced-modbus) that makes addresses browsable without mappings. (: ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [June 9, 2023, 4:08pm UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827/7 "2023-06-09T16:08:04Z")
> [@Alex\_Guyer](#): > > I've still had not success setting up the address configurations. Any ideas on that? Use the information from the successfully addressed OPC Tags to guide you. Or, better, just don't use the address mapping. It's a pointless extra layer of confusion. Just make all the OPC tags you need. ---
**Author:** ![clifford.ayer](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/clifford.ayer/32/78030_2.png) [@clifford.ayer](https://forum.inductiveautomation.com/u/clifford.ayer)\ **Post date:** [October 8, 2023, 2:54am UTC](https://forum.inductiveautomation.com/t/mir-amr-modbus-tcp-addressing/74827/8 "2023-10-08T02:54:50Z")
Bud, this just saved me hours of heartache!