Metering & Power Quality
Schneider Electric support forum about Power Meters (ION, PowerTag, PowerLogic) and Power Quality from design, implementation to troubleshooting and more.
Link copied. Please paste this link to share this article on your social media post.
Hello
Customer have PME 7.2 and more than 20s ION7550-RTU devices which are read on Modbus muster (COM1/COM2 on ION) data and recorded in ION. ION in this case, work like datalogger. If they lose network connection, ION send data after connection back to PME7.2 database. All devices (IONs) are communicate through internet (public IP address)
We need to implement six new ION7550-RTU devices which are have on serial network connected iEM3155 and one main measurement PM3255.
I know, that ION7550-RTU couldn’t represented number type INT64 (for Energy). Only two registers number type INT32 or float. In device iEM3000 and PM3000 I think that have Energy represented with two registers.
Also in PM800 I remember there need enabled to see Energy with different number type. I think that is the same here in iEM3000.
In standard manual Modbus mapping not include this registers. Could somebody put here Modbus table to enabled this registers for each tariff?
Thank you
Link copied. Please paste this link to share this article on your social media post.
Reading the 64 bit in 2 X 32 bit into the arithmetic module then calculate to give energy reading. What do you think ?
Link copied. Please paste this link to share this article on your social media post.
Hello Yut
I finaly finished this project. Thank you for your typ. I found (L2 support sent me) manual where is from 45200 registers energy in two registers. Typ of number is Float (IEEE- Float). I compare whit registers INT64 3204-3207 and it is the same.
Yut, Thank you again.
Buy
Link copied. Please paste this link to share this article on your social media post.
The meters typically use float32 internally for any process required. Since float32 is smaller than the full 64 bit range the data will likely get truncated for certain value ranges. The data recorder module records values as float32 values as well so onboard logging is likely to cause the same issue. Reading 32 bit values into the ART module will cause this range truncation so that will not work for some input values.
Remember that the measurement accuracy of the meter is considerably less than any 32 bit value can represent (never mind 64 bit values). A 32 bit float should have more than enough accuracy for the vast majority of applications.
Look up the definitions for accuracy vs precision for more information and this should be before clearer.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.