Issues with DNP data of PM5560

[SukhVirk7]

Hi

The PM5560 meter communicates with the DNP client and sends all other data successfully. It is on latest firmware V4.4.5. It does not send the power factor and frequency values correctly. When no voltage and current are applied, it transmits -2147483648 on point #27 and 31. When voltage is applied at the nominal frequency, it correctly reports 60Hz on DNP point #31. However, when voltage and currents are present with a non-unity power factor, it consistently shows zero on DNP point #27. Is this a known issue with Schneider?

@Jesus_Diaz 

[Mehran_Mehrnia]

Hi @SukhVirk7 

The value -2147483648 returned on point #27 (Power Factor) and point #31 (Frequency) via DNP3 protocol from the PM5560 meter when no voltage or current is applied is a known behavior indicating minimum possible 32-bit signed integer, and it is commonly used in DNP3 and other protocols to represent "Invalid" or "Not Available" data.

When there is no voltage or current, the meter cannot calculate Power Factor (PF) because it depends on both voltage and current, and accordingly cannot calculate Frequency because frequency is derived from the voltage waveform. As a result, the meter sends -2147483648 to indicate that these values are undefined or invalid under current conditions.

Here is the same result I got from the meter when there is no voltage and current connected to the meter:

Here are the results when voltage and current are present, but the power factor is unity:

Further investigation is required regarding the zero power factor (PF) value being returned, despite the presence of voltage and current at a non-unity PF.

Best Regards,

-Mehran

L3 Expert Advanced metering

[SukhVirk7]

Thanks for the clarification @Mehran_Mehrnia 

Have you tested your meter with a non-unity power factor, and does it consistently display zero? Do you believe this is an issue that could be addressed in a future firmware update? Please let me know the result, when investigation in completed. Thanks

[SukhVirk7]

[SukhVirk7]

Hi @Charles_Murison 

I noticed you provided a solution but I couldn't it here. Could you please re-post it?

Thanks

Sukh

[Charles_Murison]

Hello @SukhVirk7 ,

I deleted my post as I was responding to the post without reading the history. My response was for what to do with ION7400/PM8000/ION9000 meter. The solution cannot be applied to PM5000 meters as meters are fundamentally different architecture. I do not know what options the PM5000 series of meters offer to address what you are seeing.

Regards,

Charles

[Charles_Murison]

Hello @Jesus_Diaz ,

Do you know if it is possible to make the Power Factor a scaled value in DNP?

Regards,

Charles

[Jesus_Diaz · Accepted solution]

Hello @Charles_Murison and @SukhVirk7 

In the PM5500 series, the only configuration available on the meter side for DNP3 is enabling or disabling the protocol. All other configurations should be done in the client-side application.

You can change the variants as per the table provided in the manual (see page 115).

I tested this using Protocol Test Harness and selected both short and long float.

Results:

ION Setup:

The PF value of 1.520491958 can be interpreted using the table in the user guide: 2 - 1.5204 = 0.4796, which matches the value shown in ION Setup.

I hope this helps.

Regards,

JD