# Ignition and PowerLogic EGX100 through modbus RTU **URL:** \ **Category:** Ignition\ **Created:** [June 27, 2012, 2:27pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711 "2012-06-27T14:27:00Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![SamJaimes](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SamJaimes](https://forum.inductiveautomation.com/u/SamJaimes)\ **Post date:** [June 27, 2012, 2:27pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/1 "2012-06-27T14:27:00Z")
Ignition is connected to a gateway PowerLogix EGX100 using modbus RTU. This gateway is connected to a PowerLogix PM710 device. The gateway can be configured through a webpage and is possible visualizing data (comming from the device) from the same webpage. The problem is not showing I can’t see the data from the device. Why is this happening? ---
**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 27, 2012, 2:29pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/2 "2012-06-27T14:29:13Z")
Have you subscribed to any tags on the device? Modbus doesn’t support browsing. You need to either create SQLTags manually, or specify some ranges of tags in the address configuration for that device and then subscribe to them. ---
**Author:** ![SamJaimes](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SamJaimes](https://forum.inductiveautomation.com/u/SamJaimes)\ **Post date:** [June 28, 2012, 1:22pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/3 "2012-06-28T13:22:41Z")
I have specified ranges in the address configuration. When I try to visualize those tags in the quick client I just can see: Status: OPC\_NOT\_CONNECTED Value: null Quality: Not Connected ---
**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 28, 2012, 2:33pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/4 "2012-06-28T14:33:47Z")
You’re probably specifying too large a range then. A lot of devices will “freak out” and close the connection if you address registers that don’t exist or aren’t being used. Try addressing one register you know exists and has a valid value, manually, by creating a SQLTag. ---
**Author:** ![SamJaimes](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SamJaimes](https://forum.inductiveautomation.com/u/SamJaimes)\ **Post date:** [June 28, 2012, 3:14pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/5 "2012-06-28T15:14:52Z")
I already did that test and I received the same results. ---
**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 28, 2012, 3:28pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/6 "2012-06-28T15:28:38Z")
Time to start troubleshooting then. Look in the logs for error messages from the device. ---
**Author:** ![diat150](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diat150](https://forum.inductiveautomation.com/u/diat150)\ **Post date:** [June 28, 2012, 4:48pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/7 "2012-06-28T16:48:45Z")
are you able to see the device using a modbus test program? like modbus poll, or modbus scanner? I usually start testing using one of these programs first, cause they are easy to change settings on quickly. Its especially useful when trying to pull floats because some manufacturers order the data differently from others. ---
**Author:** ![SamJaimes](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SamJaimes](https://forum.inductiveautomation.com/u/SamJaimes)\ **Post date:** [July 2, 2012, 1:17pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/8 "2012-07-02T13:17:50Z")
I used simply modbus and I realized that I was using the wrong driver. I was using modbus RTU instead of modbus TCP. Now Ignition is reading correctly. My question is why I was not able to connect this same device to Ignition using modbus v1 but I could using modbus v2? ![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:") ---
**Author:** ![papermaker](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@papermaker](https://forum.inductiveautomation.com/u/papermaker)\ **Post date:** [June 24, 2014, 2:50pm UTC](https://forum.inductiveautomation.com/t/ignition-and-powerlogic-egx100-through-modbus-rtu/4711/9 "2014-06-24T14:50:46Z")
I believe you were “double-converting” - your gateway strips off the TCP wrapper and reformats the message as an RTU type to send out the serial end of the gateway (I think that mainly involves the CRC, but don’t hold me to that) - so you need to communicate with the gateway as a straight Modbus TCP style device.