# Error when connecting to Banner DXM700 via Modbus TCP

**URL:** <https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995>\
**Category:** Ignition\
**Created:** [February 17, 2023, 1:55pm UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995 "2023-02-17T13:55:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Edward\_Neubecker](https://avatars.discourse-cdn.com/v4/letter/e/34f0e0/32.png) [@Edward\_Neubecker](https://forum.inductiveautomation.com/u/Edward_Neubecker)\
**Post date:** [February 17, 2023, 1:55pm UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995/1 "2023-02-17T13:55:39Z")

</div>

Hi,  
Ignition rookie here and new to the forum and looking for some guidance.  
I am trying to connect Ignition to a Banner DXM700 to read registers and also write registers to control and monitor things that are connected to the controller. I have successfully connected the device.

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

But I the value that shows up in designer is "bad" and the error I get is Bad(bad\_timeout: Operation timed out").

Here are some screen shots from designer to help understand my setup.

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

and the error

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

Any guidance here?

---

<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:** [February 17, 2023, 2:51pm UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995/2 "2023-02-17T14:51:20Z")

</div>

Unit number?

---

<div class="post-metadata">

**Author:** ![Edward\_Neubecker](https://avatars.discourse-cdn.com/v4/letter/e/34f0e0/32.png) [@Edward\_Neubecker](https://forum.inductiveautomation.com/u/Edward_Neubecker)\
**Post date:** [February 18, 2023, 1:52pm UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995/3 "2023-02-18T13:52:19Z")

</div>

The device is a DXM700-B1. Is that what you mean by Unit?

---

<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:** [February 18, 2023, 2:57pm UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995/4 "2023-02-18T14:57:16Z")

</div>

The modbus slave unit number. Ignition's driver defaults to slave unit #0. Many devices need something else, particularly if the Modbus TCP interface is really translating to Modbus RTU under the covers.

`DXM0` isn't a normal Modbus address, so I presume you used a mapping. Show your mapping.

---

<div class="post-metadata">

**Author:** ![Edward\_Neubecker](https://avatars.discourse-cdn.com/v4/letter/e/34f0e0/32.png) [@Edward\_Neubecker](https://forum.inductiveautomation.com/u/Edward_Neubecker)\
**Post date:** [February 22, 2023, 12:48am UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995/5 "2023-02-22T00:48:09Z")

</div>

Very insightul. This is my 1st time trying to connect to a modbus device through ignition. I thought it was odd that I never had to enter the address of the device. How does one change the unit ID of the device I am trying to communicate with?  
I have attached a snipet of code from a node-red flow that does what I need. I am trying to eliminate node red and use a integration platform for this work 🙂

![Snag_18173c](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/a/aa84f4000e4e142a42158cc702b4c6895eb878ac.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:** [February 22, 2023, 12:14pm UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995/6 "2023-02-22T12:14:47Z")

</div>

When you are manually entering OPC item paths, you prefix the rest of the address with `199.`, so a complete OPC item path would be something like `[deviceName]199.HR1234`

I don't use or recommend the address map.

---

<div class="post-metadata">

**Author:** ![Edward\_Neubecker](https://avatars.discourse-cdn.com/v4/letter/e/34f0e0/32.png) [@Edward\_Neubecker](https://forum.inductiveautomation.com/u/Edward_Neubecker)\
**Post date:** [March 11, 2023, 11:15am UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995/7 "2023-03-11T11:15:23Z")

</div>

Thanks Phil for the advice. I finally got back to this project and implemented your advice and it worked like a champ!  
Appreciate the advice to not use the address map and encode the address into the OPC path

---

<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:** [March 11, 2023, 12:11pm UTC](https://forum.inductiveautomation.com/t/error-when-connecting-to-banner-dxm700-via-modbus-tcp/69995/8 "2023-03-11T12:11:57Z")

</div>

> [@Edward\_Neubecker](#):
>
> Thanks Pat

???
