Metering & Power Quality
Schneider Electric support forum about Power Meters (ION, PowerTag, PowerLogic) and Power Quality from design, implementation to troubleshooting and more.
Posted: 2016-06-24 10:04 AM
Link copied. Please paste this link to share this article on your social media post.
I've been asked to match a clients PM800 register map to equivalent PM8000 registers.
I need help finding the equivalent PM8000 register for these PM800 items because I just can find tjem.
PM800 register:
1211 THD/thd Voltage, Phase A-B
1212 THD/thd Voltage, Phase B-C
1213 THD/thd Voltage, Phase C-A
1231 Current Fundamental Coincident Angle, Phase A
1233 Current Fundamental Coincident Angle, Phase B
1235 Current Fundamental Coincident Angle, Phase C
1245 Voltage Fundamental Coincident Angle, A-N/A-B
1247 Voltage Fundamental Coincident Angle, B-N/B-C
1249 Voltage Fundamental Coincident Angle, C-N/C-A
1961 Present Demand Current, Phase A
1971 Present Demand Current, Phase B
1981 Present Demand Current, Phase C
2151 Present Demand Real Power, 3-Phase Total
2166 Present Demand Reactive Power, 3-Phase Total
2181 Present Demand Apparent Power, 3-Phase Total
3214 Scale F – Power
8000 Requested Command
8001 Command Parameters
Thank you !
Link copied. Please paste this link to share this article on your social media post.
Hal is correct to point out that access to complex data (or advanced configuration) typically requires use of the ION protocol. However, compared to previous ION meters, the PM8000 provides a much more comprehensive set of real-time values in its default Modbus map. Most/all of the real-time values should now be present in the default Modbus map. As a result, some of the registers that you are asking about do exist in the default Modbus map for the PM8000, although perhaps under a slightly different name. But some of them do not exist on the meter at all, due to some small differences in implementation compared to the PM800.
I have provided my comments here on the specific registers from your original post, to the best of my knowledge.
1211 THD/thd Voltage, Phase A-B
1212 THD/thd Voltage, Phase B-C
1213 THD/thd Voltage, Phase C-A
[On the PM8000, the present implementation provides voltage harmonics for either line-to-neutral voltages or line-to-line voltages based on the wiring mode, but not both at the same time. When the PM8000 is configured in 4W-WYE, 3W-WYE or SINGLE mode, it will provide voltage harmonics as line-to-neutral values. When the PM8000 is configured in DELTA mode, it will provide voltage harmonics as line-to-line values. The equivalent THD values in the PM8000 register list can be found at registers 21330, 21332 and 21334. The published register list does look misleading to me, so I can understand the confusion.]
1231 Current Fundamental Coincident Angle, Phase A
1233 Current Fundamental Coincident Angle, Phase B
1235 Current Fundamental Coincident Angle, Phase C
1245 Voltage Fundamental Coincident Angle, A-N/A-B
1247 Voltage Fundamental Coincident Angle, B-N/B-C
1249 Voltage Fundamental Coincident Angle, C-N/C-A
[On the PM8000, all individual harmonics (up to the 63rd) are published in the register list, with values provided for both magnitude and angle. The term "coincident angle" is not used in the PM8000 register list, so that might have made it harder to find. You can find the H1 Angle registers for three-phase voltage and current at registers 22880, 23268, 23656, 24432, 24820, and 25208.]
1961 Present Demand Current, Phase A
1971 Present Demand Current, Phase B
1981 Present Demand Current, Phase C
2151 Present Demand Real Power, 3-Phase Total
2166 Present Demand Reactive Power, 3-Phase Total
2181 Present Demand Apparent Power, 3-Phase Total
[On the PM8000, there is no value provided for "present demand" (which on the PM800 was a type of accumulated integration over each demand interval). Instead, the PM8000 provides registers for "Last Demand" (the value from the last completed demand interval), "Predicted Demand" (the value predicted for the end of the present demand interval based on the accumulation so far), and "Peak Demand" (the maximum of all the completed demand intervals since the last reset). You can find these values in the Modbus map in the section starting around register 29884, which includes per-phase current demand, real/reactive/apparent power demand, and a number of other derivative cases.]
3214 Scale F – Power
8000 Requested Command
8001 Command Parameters
[On the PM8000, there is no direct equivalent for these ones. As I understand, the "Scale F - Power" register is a scaling factor used for determining the proper scaling of an alarm setpoint related to power measurements. Alarming is done differently on the PM8000 than the PM800, and while the equivalent function is still absolutely available the configuration of alarming is not done through Modbus. Similarly, the other two registers here are related to the Modbus command interface, which is not present on the PM8000 (its functionality is replaced by the ION protocol, which is largely abstracted through the ION Setup configuration tool).]
As Hal explained, it may still be worth considering creating a custom Modbus map using the Modbus Slave modules, to remap the measurements of interest to match the PM800 map as closely as possible. And any custom measurements added on top of the default ION framework will require this to expose them via Modbus. But if you're looking to use the default Modbus map for the meter's default real-time measurements, most/all of the real-time values should be available.
Best regards,
David Tuckey
Firmware Architect
Posted: 2016-06-24 10:26 AM . Last Modified: 2022-10-18 10:36 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2016-06-24 10:46 AM
Link copied. Please paste this link to share this article on your social media post.
Thank you Jorge. Actually that's the first post I read when I was looking for the PM8000 register list.
The problem I'm having is the points I'm looking for don't seem to be in that list.
Link copied. Please paste this link to share this article on your social media post.
I had a replacement job replaced the ION7300. I just simply rewrote the Modbus map of the PM8000 using ION7300 map then replaced the unit.
Posted: 2016-06-28 06:58 AM
Link copied. Please paste this link to share this article on your social media post.
Thanks Yut !
I will suggest that to our client.
That will make his SCADA work more simple for sure.
The issue still is finding all the PM800 points in the PM8000.
For example the PM8000 register list doesn't show THD volts L-L, but I'm sure it's capable of this measurement.
Greg.
Link copied. Please paste this link to share this article on your social media post.
Most ION devices calculate THD Volt L-L parameter but it probably is not be mapped to a Modbus register by default. In that case you will need to link the register you wish to expose to a Modbus slave module (create a new or link to an existing one). The Modbus slave module setup registers will define the Modbus register address the input register will be mapped to, the format of the register, etc.
For more information check out the ION Reference document as it will fully explain how the Modbus slave module works and they can be configured.
It is recommended to use the ION protocol in most cases with an ION device. Modbus does not allow the download of any complex data measured by the device. Exclusively exposing an ION device via Modbus is the equivalent of taking a high end sports car and replacing its engine with one from a golf cart. The Modbus slave modules are meant for the application where only a few registers need to be exchanged with other software packages.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Have list but this page will not allow me to attach a file.............
Link copied. Please paste this link to share this article on your social media post.
Hal is correct to point out that access to complex data (or advanced configuration) typically requires use of the ION protocol. However, compared to previous ION meters, the PM8000 provides a much more comprehensive set of real-time values in its default Modbus map. Most/all of the real-time values should now be present in the default Modbus map. As a result, some of the registers that you are asking about do exist in the default Modbus map for the PM8000, although perhaps under a slightly different name. But some of them do not exist on the meter at all, due to some small differences in implementation compared to the PM800.
I have provided my comments here on the specific registers from your original post, to the best of my knowledge.
1211 THD/thd Voltage, Phase A-B
1212 THD/thd Voltage, Phase B-C
1213 THD/thd Voltage, Phase C-A
[On the PM8000, the present implementation provides voltage harmonics for either line-to-neutral voltages or line-to-line voltages based on the wiring mode, but not both at the same time. When the PM8000 is configured in 4W-WYE, 3W-WYE or SINGLE mode, it will provide voltage harmonics as line-to-neutral values. When the PM8000 is configured in DELTA mode, it will provide voltage harmonics as line-to-line values. The equivalent THD values in the PM8000 register list can be found at registers 21330, 21332 and 21334. The published register list does look misleading to me, so I can understand the confusion.]
1231 Current Fundamental Coincident Angle, Phase A
1233 Current Fundamental Coincident Angle, Phase B
1235 Current Fundamental Coincident Angle, Phase C
1245 Voltage Fundamental Coincident Angle, A-N/A-B
1247 Voltage Fundamental Coincident Angle, B-N/B-C
1249 Voltage Fundamental Coincident Angle, C-N/C-A
[On the PM8000, all individual harmonics (up to the 63rd) are published in the register list, with values provided for both magnitude and angle. The term "coincident angle" is not used in the PM8000 register list, so that might have made it harder to find. You can find the H1 Angle registers for three-phase voltage and current at registers 22880, 23268, 23656, 24432, 24820, and 25208.]
1961 Present Demand Current, Phase A
1971 Present Demand Current, Phase B
1981 Present Demand Current, Phase C
2151 Present Demand Real Power, 3-Phase Total
2166 Present Demand Reactive Power, 3-Phase Total
2181 Present Demand Apparent Power, 3-Phase Total
[On the PM8000, there is no value provided for "present demand" (which on the PM800 was a type of accumulated integration over each demand interval). Instead, the PM8000 provides registers for "Last Demand" (the value from the last completed demand interval), "Predicted Demand" (the value predicted for the end of the present demand interval based on the accumulation so far), and "Peak Demand" (the maximum of all the completed demand intervals since the last reset). You can find these values in the Modbus map in the section starting around register 29884, which includes per-phase current demand, real/reactive/apparent power demand, and a number of other derivative cases.]
3214 Scale F – Power
8000 Requested Command
8001 Command Parameters
[On the PM8000, there is no direct equivalent for these ones. As I understand, the "Scale F - Power" register is a scaling factor used for determining the proper scaling of an alarm setpoint related to power measurements. Alarming is done differently on the PM8000 than the PM800, and while the equivalent function is still absolutely available the configuration of alarming is not done through Modbus. Similarly, the other two registers here are related to the Modbus command interface, which is not present on the PM8000 (its functionality is replaced by the ION protocol, which is largely abstracted through the ION Setup configuration tool).]
As Hal explained, it may still be worth considering creating a custom Modbus map using the Modbus Slave modules, to remap the measurements of interest to match the PM800 map as closely as possible. And any custom measurements added on top of the default ION framework will require this to expose them via Modbus. But if you're looking to use the default Modbus map for the meter's default real-time measurements, most/all of the real-time values should be available.
Best regards,
David Tuckey
Firmware Architect
Posted: 2016-07-22 11:28 AM
Link copied. Please paste this link to share this article on your social media post.
David,
THANK YOU for taking the time to research the answer to my question.
I really appreciate the thoroughness and commitment.
Cheers,
Greg.
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.