Your best bet would be to call Inductive Automation tech support so they can see what is going on. Does anyone recognize this symptom and have a good direction to point me in? I didn't leave it in place long enough to watch it go up and down. These new numbers immediately started the same upwards tracking/counting. So, I tried that option in Ignition and ended up getting wildly ridiculous numbers (in the millions or billions). As I understand it, if you use the F suffix on a Modbus Register in Wonderware, you're identifying it as a 32-bit floating point number. However, when he sets it up in Wonderware, he uses the F suffix (because that is how they have their own meters addressed). So the issue is not the meter or the Digi, it is something in Ignition. The really strange thing is, we have a sister platform that uses Wonderware, and when a friend pulled the data into Wonderware, it came in perfectly clear. This happens with every relevant register address. I know that the range it is counting up and down with is the full range of a modbus register, but I don't know why it's scanning like that. Once the tag starts polling the register, it starts at zero, counts up to 32767, suddenly changes to -32767 and counts back down to zero. I can also create tags that poll the registers inside the flow analyzers. I can poll the Digi via Ignition by creating tags that are linked to the Digi's internal diagnostics. We have a series of flow analyzers that are connected to the network via Digi-Iaps. I'm having a strange issue that I just cannot solve.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |