# Modbus Device Identification in Error Logging

**URL:** <https://forum.inductiveautomation.com/t/modbus-device-identification-in-error-logging/32198>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [February 12, 2020, 8:39pm UTC](https://forum.inductiveautomation.com/t/modbus-device-identification-in-error-logging/32198 "2020-02-12T20:39:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ahiero](https://avatars.discourse-cdn.com/v4/letter/a/a698b9/32.png) [@Ahiero](https://forum.inductiveautomation.com/u/Ahiero)\
**Post date:** [February 12, 2020, 8:39pm UTC](https://forum.inductiveautomation.com/t/modbus-device-identification-in-error-logging/32198/1 "2020-02-12T20:39:31Z")

</div>

When a Modbus device is failing communication, there are entries made in the logs as expected. Sometimes the driver state is still showing “Connected” for all Modbus devices when viewed from the gateway page. Is there a way to determine the gateway device name from the entries in the logs?

---

<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:** [February 12, 2020, 8:44pm UTC](https://forum.inductiveautomation.com/t/modbus-device-identification-in-error-logging/32198/2 "2020-02-12T20:44:37Z")

</div>

It depends what version you’re on, but in later versions (barring the few releases where it wasn’t working…) there is a little magnifying glass over on the right side of some log messages that have additional information in key/value format.

Look for a “device-name” key/value entry.

---

<div class="post-metadata">

**Author:** ![Ahiero](https://avatars.discourse-cdn.com/v4/letter/a/a698b9/32.png) [@Ahiero](https://forum.inductiveautomation.com/u/Ahiero)\
**Post date:** [February 12, 2020, 11:50pm UTC](https://forum.inductiveautomation.com/t/modbus-device-identification-in-error-logging/32198/3 "2020-02-12T23:50:57Z")

</div>

This is an example of what we get in the logs with Modbus Driver 5.9.8 (b2018060714):

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/4/4660e072fcc1f8d11c5f708b554c9c3d8f86879a.png)

Is there an updated version available for Ignition 7.9.8 (b2018060714)?

---

<div class="post-metadata">

**Author:** ![Ahiero](https://avatars.discourse-cdn.com/v4/letter/a/a698b9/32.png) [@Ahiero](https://forum.inductiveautomation.com/u/Ahiero)\
**Post date:** [February 13, 2020, 12:03am UTC](https://forum.inductiveautomation.com/t/modbus-device-identification-in-error-logging/32198/4 "2020-02-13T00:03:13Z")

</div>

I found in the release notes that for Ignition release 7.9.12 the key/value pairs were added back in. Thanks for the tip on what to look for. Any concern of using the updated Modbus driver on Ignition 7.9.8?

---

<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:** [February 13, 2020, 12:07am UTC](https://forum.inductiveautomation.com/t/modbus-device-identification-in-error-logging/32198/5 "2020-02-13T00:07:01Z")

</div>

> [@Ahiero](#):
>
> Any concern of using the updated Modbus driver on Ignition 7.9.8?

Won't work, it requires platform 7.9.12 as well.