# Debugging and Troubleshooting device connections

**URL:** <https://forum.inductiveautomation.com/t/debugging-and-troubleshooting-device-connections/66625>\
**Category:** Ignition\
**Created:** [November 17, 2022, 8:04am UTC](https://forum.inductiveautomation.com/t/debugging-and-troubleshooting-device-connections/66625 "2022-11-17T08:04:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michal\_Goralczyk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michal_goralczyk/32/55564_2.png) [@Michal\_Goralczyk](https://forum.inductiveautomation.com/u/Michal_Goralczyk)\
**Post date:** [November 17, 2022, 8:04am UTC](https://forum.inductiveautomation.com/t/debugging-and-troubleshooting-device-connections/66625/1 "2022-11-17T08:04:10Z")

</div>

Hello,

I am looking for answers to the question about debugging and troubleshooting device connections. I would like to diagnose device connections a little more accurately. I know that it is possible to view logs in diagnostic but is it possible to check more precisely what is happening e.g. in transmitted frames? This can be done through wireshark and other such tools, is it possible to look into this directly from the gateway in a web browser?

For example, could I preview modbus communication frames or anything like below?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/a/2a1587a3d86313bfa3f0282d83a1fdf110b6eb79.png)

Best regards,  
MG

---

<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:** [November 17, 2022, 1:03pm UTC](https://forum.inductiveautomation.com/t/debugging-and-troubleshooting-device-connections/66625/2 "2022-11-17T13:03:27Z")

</div>

Sorry, no. Java's not really a good platform for packet captures. Many drivers **do** have loggers that will report traffic on the TRACE log level.

---

<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:** [November 17, 2022, 1:52pm UTC](https://forum.inductiveautomation.com/t/debugging-and-troubleshooting-device-connections/66625/3 "2022-11-17T13:52:14Z")

</div>

> [@Michal\_Goralczyk](#):
>
> For example, could I preview modbus communication frames or anything like below?

Click the gear in that screenshot, search for "ReadCoilsRequest", set it to TRACE.

Like Phil said, though, this is totally driver dependent and not something you can universally count on.

---

<div class="post-metadata">

**Author:** ![Michal\_Goralczyk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michal_goralczyk/32/55564_2.png) [@Michal\_Goralczyk](https://forum.inductiveautomation.com/u/Michal_Goralczyk)\
**Post date:** [November 17, 2022, 9:32pm UTC](https://forum.inductiveautomation.com/t/debugging-and-troubleshooting-device-connections/66625/4 "2022-11-17T21:32:27Z")

</div>

Understandable, thank you for your answers!