# \[BUG-11664\] How to distinguish which Modbus device in logs

**URL:** <https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [May 16, 2019, 7:28pm UTC](https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083 "2019-05-16T19:28:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Herbie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/herbie/32/65288_2.png) [@Herbie](https://forum.inductiveautomation.com/u/Herbie)\
**Post date:** [May 16, 2019, 7:28pm UTC](https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083/1 "2019-05-16T19:28:47Z")

</div>

I have been noticing the Logs filled with ReadCoilsRequest and ReadInputRegistersRequest that have timeouts and error messages indicating exception codes of Illegal Data Address. This has happened several times in the past. We have several devices that are polling, and I cannot figure out a way to tell which device is generating the problem, or better, which tag is generating it easily. Current method is to disable these devices one at a time until the problem goes away.

Is there a better way?

---

<div class="post-metadata">

**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:** [May 16, 2019, 7:39pm UTC](https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083/2 "2019-05-16T19:39:32Z")

</div>

The wrapper log should have `device-name = ...` at the end of each line.

The logs in the gateway you can hover over the magnifying glass icon:

 ![Screenshot_20190516_123723-2](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/73f16c84698e3abc98dd65b500b5e35696b45a4a.png)

---

<div class="post-metadata">

**Author:** ![Herbie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/herbie/32/65288_2.png) [@Herbie](https://forum.inductiveautomation.com/u/Herbie)\
**Post date:** [May 16, 2019, 7:43pm UTC](https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083/3 "2019-05-16T19:43:39Z")

</div>

Kevin, I don’t get the magnifying glass in any of the log levels. I get a + sign to expand on some entries, but never the magnifying glass.

I am running 7.9.6 currently. Is that an 8.0 thing?

 ![modbus_log](https://us1.discourse-cdn.com/inductiveautomation/original/2X/9/952b5e7ca358067d65cc830486613af517ae6a67.png)

---

<div class="post-metadata">

**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:** [May 16, 2019, 7:46pm UTC](https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083/4 "2019-05-16T19:46:59Z")

</div>

Huh, it _should_ be there in 7.9, but something is broken in the logger system and there’s an open ticket to backport the fix from 8.0.

---

<div class="post-metadata">

**Author:** ![Herbie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/herbie/32/65288_2.png) [@Herbie](https://forum.inductiveautomation.com/u/Herbie)\
**Post date:** [May 16, 2019, 7:59pm UTC](https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083/5 "2019-05-16T19:59:03Z")

</div>

I’m not seeing it in the wrapper log files either. I just checked one of my other systems running 7.9.9 and the same thing.

Don’t know if this is a problem, but they are both running Java 1.8.0\_161-b12

---

<div class="post-metadata">

**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:** [May 16, 2019, 8:00pm UTC](https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083/6 "2019-05-16T20:00:16Z")

</div>

Yeah, it’s broken right now, sorry. 😕

This post will get updated when it’s eventually fixed.

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [June 21, 2019, 8:16pm UTC](https://forum.inductiveautomation.com/t/bug-11664-how-to-distinguish-which-modbus-device-in-logs/25083/7 "2019-06-21T20:16:54Z")

</div>

This issue was fixed in 7.9.12.
