The Value of "N/A" register of PM8000(firmware version 3..0.0)

[Tomohiro-Okada]

I have a question about the value of register.

The user manual of PM8000 said that

the Modbus invalid read registers responses are

word 1 = "1111111111000000"

word 2 = "0000000000000000"

when the registers are float32.

It means if the value of the register is "N/A", the responses of meter are above.

So, I tried to confirm it by using software(the name of the software is modscan)

and PM8000 meters (firmware version 1.4.3 and 3.0.0）

Then, the responses of PM8000(ver. 1.4.3) was same as the sentences above.

but the responses of PM8000(ver.3.0.0) was not same as the sentences above

and the responses of PM8000(ver.3.0.0) was error code of modbus frame.

(Error code: 0x83, Exception code: 02, I checked it by using Wireshark）

If the value of the register is not "N/A", PM8000(ver.3.0.0) also be able to response

correct value.

But, if the value of the register changed from normal value to "N/A",

the response change to error code of modbus frame.

I'd like to know why is it happen?

Is the expression method of "N/A" changed when updating ver. 3.0.0 ?

or is it bug of ver.3.0.0?

Do you have any idea?

[Charles_Murison · Accepted solution]

Hello @Tomohiro-Okada ,

Assuming that you are using the default framework on the meter, this will be addressed in the next release of the PM8000 firmware. 

Regards,

Charles

[Tomohiro-Okada]

Hi Charles, 

Thank you for your response.

You said "Assuming that you are using the default framework on the meter".

Does it mean I can avoid this problem by using another template files(dcf files)?

or it depends on firmware version?

[Charles_Murison]

Hello @Tomohiro-Okada ,

"Does it mean I can avoid this problem by using another template files(dcf files)?"

In a way, both.

This will happen on V3.0.0 if an input to data mapping module is N/A and the request includes this input. 

Regarding the framework, there may be options, first option is to unlink the input to the data mapping module, this would be easiest and would be an short term workaround until this is fixed in firmware. A second option could be to use a convert and/or arithmetic module so that N/A is not feed to data mapping module, not ideal and a lot more work.

Third options would be to change the requests from 1 large request to multiple smaller requests explicitly not requesting registers known to be N/A.

Again this are just workarounds until this is fixed in firmware.

Regards, 

Charles

[Charles_Murison]

One note about the firmware, it is not possible to downgrade the meter from V3.0.0 to V2.X.X

Regards,

Charles

[Tomohiro-Okada]

Hi Charles,

Thank you for your quick response.

I understand what you said.

I'm looking forward to release of modified firmware.

Regards,

Okada

[Roman5444]

@Charles_Murison is there any update on the firmware update ?

[Charles_Murison · Accepted solution]

Hello @Roman5444 ,

Q4 is the timeline I have heard.

Regards,

Charles

[DuperUser]

As I was affected by this bug specifically, I can confirm that proper requests and non error responses were addressed in the latest firmware (V003.001.000). You can find the latest here: https://download.schneider-electric.com/files?p_enDocType=Firmware&p_File_Name=PM8000_V003.001.000%2... 

If you are worried about your custom framework, simply backup the unit first, (save the .DCF file), and when you are doing the firmware update, just make sure you don't also wipe out the template file (if gives you the option for different updates, like the remote display etc.). You will select your recently created DCF backup to use during the process. I have conducted this on  appx 30 PM8244's. Each one took about 15-20 minutes (depending on your network traffic), Hope this helps, this previous version absolutely bricked two of my integrations. Was waiting patiently for this upgrade. 

[Tom_Stevenson]

Hi DuperUser

Note, however, that the new ION Framework released with 3.1.0 contains framework fixes - you may want to consider saving a sub-framework in ION Designer of JUST your modifications and applying those to the newly released V3.1.0.0.0 framework.  It depends of course on what applications you are using the meter for as to whether you want the fixes (PQ and Xformer loss compensation primarily - see release notes).

Tom