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.
I have a customer here who has some PM8000 meters, they would like to read the HS values from the modbus registers shown below.
In Demo mode these do not seem to update any faster than 1 second.
Has anyone tried this before? and do you get a much faster update of the registers.
Thanks
HS Current A | 21000 | 2 | FLOAT32 | A | R/O | numeric | --- | HS I a | CT_A | MEM | None | |
HS Current B | 21002 | 2 | FLOAT32 | A | R/O | numeric | --- | HS I b | CT_A | MEM | None | |
HS Current C | 21004 | 2 | FLOAT32 | A | R/O | numeric | --- | HS I c | CT_A | MEM | None | |
HS Current N | 21006 | 2 | FLOAT32 | A | R/O | numeric | --- | HS I 4 | CT_A | MEM | None | |
HS Current G | 21008 | 2 | FLOAT32 | A | R/O | numeric | --- | HS I 5 | CT_A | MEM | None | |
HS Current Avg | 21010 | 2 | FLOAT32 | A | R/O | numeric | --- | HS I avg | CT_A | MEM | None | |
HS Frequency | 21016 | 2 | FLOAT32 | Hz | R/O | numeric | --- | HS Freq | HZ | MEM | None | |
HS Voltage, A-B | 21018 | 2 | FLOAT32 | V | R/O | numeric | --- | HS Vll ab | PT_V | MEM | None | |
HS Voltage, B-C | 21020 | 2 | FLOAT32 | V | R/O | numeric | --- | HS Vll bc | PT_V | MEM | None | |
HS Voltage, C-A | 21022 | 2 | FLOAT32 | V | R/O | numeric | --- | HS Vll ca | PT_V | MEM | None | |
HS Voltage, L-L Average | 21024 | 2 | FLOAT32 | V | R/O | numeric | --- | HS Vll avg | PT_V | MEM | None | |
HS Voltage, A-N | 21026 | 2 | FLOAT32 | V | R/O | numeric | --- | HS Vln a | PT_V | MEM | None | |
HS Voltage, B-N | 21028 | 2 | FLOAT32 | V | R/O | numeric | --- | HS Vln b | PT_V | MEM | None | |
HS Voltage, C-N | 21030 | 2 | FLOAT32 | V | R/O | numeric | --- | HS Vln c | PT_V | MEM | None | |
HS Voltage, L-N Average | 21034 | 2 | FLOAT32 | V | R/O | numeric | --- | HS Vln avg | PT_V | MEM | None |
Link copied. Please paste this link to share this article on your social media post.
Hi Andrew,
You are correct that the HS Power Meter Module only updates once per second in demo mode. With a non-demo volts mode, the data is refreshed every half-cycle.
The caveat with reading this over modbus, is that the round-trip comm delay in making a request and getting a response for highspeed data is variable. Depending on the meter loading it could take up to a second to get a response (metering and logging is always higher priority than comms). You will need to benchmark it in your specific scenario to see if it will be fast enough for your needs.
Posted: 2016-10-04 07:28 AM
Link copied. Please paste this link to share this article on your social media post.
Since the are almost in order I guess it would be smart to create a Modbus Register Group that reads all signals at a time
I assumed it was SmartStruxure, but maybe it wasn´t
Christer
Link copied. Please paste this link to share this article on your social media post.
Hi Andrew,
You are correct that the HS Power Meter Module only updates once per second in demo mode. With a non-demo volts mode, the data is refreshed every half-cycle.
The caveat with reading this over modbus, is that the round-trip comm delay in making a request and getting a response for highspeed data is variable. Depending on the meter loading it could take up to a second to get a response (metering and logging is always higher priority than comms). You will need to benchmark it in your specific scenario to see if it will be fast enough for your needs.
Link copied. Please paste this link to share this article on your social media post.
Hi Patrick,
Thanks for the reply, that is exactly as I had hoped.
My customer is redaing the registers from a PLC connected via TCP, so it should be fast enough.
Thanks
Andy
Link copied. Please paste this link to share this article on your social media post.
Hi,
I have also same concern with PM8000, but it was monitored to Power Monitoring Expert. Can PM8000 supports the 100ms report template of PME?
Link copied. Please paste this link to share this article on your social media post.
Hi @DPMalagar
As mentioned above, communications in ION meters such as PM8000, is the lowest priority on the meter and it is the first thing to get dropped if meter is highly loaded and CPU loading is a factor(meter is busy with power quality events, waveform recordings, alarms, etc.). Therefore there is no way to guarantee high speed communications.
For real-time data, PME polls ION meters' data via the native ION protocol within a range of seconds, and the values are updated on the meter's diagram.
The 100 ms Report shows 100 ms measurements from the meter where data had been logged before with 100 ms interval on meter's onboard log and is totally different from polling meter and meter's response in 100 ms.
For historical data, depending on the report type and how the meter is configured with the desired interval logs (for example, 15 minutes, 1 minute, 100 milliseconds, etc.), PME retrieves logged data from the meter's onboard log (default is every 30 seconds) and pushes it into the SQL database. Depending on which report is executed, the results are replicated in the report tables.
Best Regards,
-Mehran
L3 Expert Advanced metering
Link copied. Please paste this link to share this article on your social media post.
Hi @Mehran_Mehrnia,
Thank you very much for your help. On the PME, does it retrieve the log from the Meter's onboard log even its FIFO? I believe it has a maximum log of 3360, which limits to less than a day, if I used a 1sec interval. I also think that PME has a software log., but I can only edit on 3rd party using Device Type Editor, I cannot locate the default logging file for native PM8000 PME Driver.
Regards,
Dennis
Link copied. Please paste this link to share this article on your social media post.
Hi @DPMalagar
You're welcome.
Each Data Recorder in the meter for example Load Profile has the log depth(35 days) with 15 minutes interval per each day means 4(each hour has 4*15 minutes)*24(each day is 24 hours)*35 days = 3360 records that each record for example in this Load profile has only 4 linked channels and since the 'Record Mode' is Circular, after 35 days the logged values start to be overwritten as FIFO(first in first out).
The log depth specifies how long the recorder can keep the recorded values before being overwritten and the shorter the logging interval is set, the more log memory is used. As mentioned before, PME retrieves logged data from the meter's onboard log (the default is every 30 seconds), which is sufficient to avoid losing any logged data unless the log depth is too short or the communication between the device and PME is lost for a while, resulting in data being overwritten on the device.
Software logging in PME is only for third-party device drivers, while native devices in PME, such as the PM8000, have their own onboard logging that can be configured directly on the device.
If you need more assistance on PME, kindly post your question in the EcoStruxure Power Monitoring Expert forum.
Best Regards,
-Mehran
L3 Expert Advanced metering
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.