|
|
|
It is currently Sun May 19, 2013 1:47 am
|
View unanswered posts | View active topics | View unsolved topics
|
Page 1 of 1
|
[ 8 posts ] |
|
Ignition and PowerLogic EGX100 through modbus RTU
| Author |
Message |
|
SamJaimes
General
Joined: Tue Jul 26, 2011 2:34 am Posts: 160
|
 Ignition and PowerLogic EGX100 through modbus RTU
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?
|
| Wed Jun 27, 2012 6:27 am |
|
 |
|
Kevin.Herron
Moderator
Joined: Mon Oct 27, 2008 4:10 pm Posts: 1333 Location: Folsom, CA
|
 Re: Ignition and PowerLogic EGX100 through modbus RTU
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.
_________________ Kevin Herron Software Developer Inductive Automation
|
| Wed Jun 27, 2012 6:29 am |
|
 |
|
SamJaimes
General
Joined: Tue Jul 26, 2011 2:34 am Posts: 160
|
 Re: Ignition and PowerLogic EGX100 through modbus RTU
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
|
| Thu Jun 28, 2012 5:22 am |
|
 |
|
Kevin.Herron
Moderator
Joined: Mon Oct 27, 2008 4:10 pm Posts: 1333 Location: Folsom, CA
|
 Re: Ignition and PowerLogic EGX100 through modbus RTU
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.
_________________ Kevin Herron Software Developer Inductive Automation
|
| Thu Jun 28, 2012 6:33 am |
|
 |
|
SamJaimes
General
Joined: Tue Jul 26, 2011 2:34 am Posts: 160
|
 Re: Ignition and PowerLogic EGX100 through modbus RTU
I already did that test and I received the same results.
|
| Thu Jun 28, 2012 7:14 am |
|
 |
|
Kevin.Herron
Moderator
Joined: Mon Oct 27, 2008 4:10 pm Posts: 1333 Location: Folsom, CA
|
 Re: Ignition and PowerLogic EGX100 through modbus RTU
Time to start troubleshooting then. Look in the logs for error messages from the device.
_________________ Kevin Herron Software Developer Inductive Automation
|
| Thu Jun 28, 2012 7:28 am |
|
 |
|
diat150
General
Joined: Wed Feb 24, 2010 5:56 pm Posts: 384
|
 Re: Ignition and PowerLogic EGX100 through modbus RTU
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.
|
| Thu Jun 28, 2012 8:48 am |
|
 |
|
SamJaimes
General
Joined: Tue Jul 26, 2011 2:34 am Posts: 160
|
 Re: Ignition and PowerLogic EGX100 through modbus RTU
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? 
|
| Mon Jul 02, 2012 5:17 am |
|
 |
|
|
Page 1 of 1
|
[ 8 posts ] |
|
Who is online |
Users browsing this forum: Google [Bot] and 3 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|