Comx210 reading PM8000

[sesa102217_brid]

I have a problem, with Comx210 it is not reading PM8000 meter, but if I select another driver like pm5000 I can read it.
Comx210 is with the latest firmware v6.8.4 and PM8000 v3.0.0
thanks in advance.

[Tom_Stevenson]

Hi - what are the communication settings on the PM8000?  Has the protocol been changed from ION to Modbus for the communications port you are using?

Thanks

Tom

[sesa102217_brid]

I´m using modbus TCP for Comx210 communication with PM8000.

 attached some screens.

[Tom_Stevenson]

Are  you able to connect to the device with ION Setup?

[sesa102217_brid]

Yes, 

[Tom_Stevenson]

There is a Modbus TCP security setting shown in the attached picture - worth ensuring it is on.  Does the ComX indicate whether the connection is successful, but cannot read, or is the connection not succeeding? (There is a setting in the Security Options module to disable read access for Modbus).

Tom

[sesa102217_brid]

I have other meters (iem and pm5560) modbus and modbus TCP already working on this comx210. 
Only the PM8000 that was installed now doesn't work,
and checking in IONsetup the modbus tcp connection is active.

Tks

[Charles_Murison]

Hello @sesa102217_brid ,

Are you able to read the modbus registers using a modbus client like in FA180037 . This would help determine if there could be something on the PM8000 or the gateway to investigate further. While connected to the meter in ION Setup. Switch to advanced configuration -> Security Option Modules -> Security Option module 1 -> Setup registers -> Modbus Map access, Be sure that read or read/write is selected.

Regards,

Charles

[sesa102217_brid]

Hi, Charles. 

Yes, 

I can read modbus logs through another client, I used modscan.
Regarding the advanced option, it was read-only and I changed it to read and write, but still no communication.

On the 3rd party protocols Communication screen the default modbus slave is showing N/A.
Do you know if it's normal?

Tks 

[sesa102217_brid]

In another test I did, I changed the driver from pm8000 to PM5560 and the readings started to appear, 
wrong but communicated.

[Charles_Murison]

Hello @sesa102217_brid ,

Having the default Modbus Slave showing "Default" as N/A is normal when there are no custom modbus registers. The PM8000 meters support 3 different configurations, Default only, Default + custom, Custom only. 

I do not have a Com'X so I am not 100% sure of the driver. I am wondering if possible that a request to the meter includes registers that are "N/A" inside the meter. For example power factor leading if you have a lag system. If this is the case, 3 options,

1) Wait for the next release of meter firmware (currently under development)

2) If registers in the request are known to always be N/A, it is possible to unlink the registers from the data mapping module in question

3) Place a convert module in front of the data mapping module to convert N/A to either 0 or 1 depending on the need.

4) I am not sure if this is possible, modify the PM8000 driver to not include the N/A registers. Without knowing exactly what the driver is requesting I can't give more specifics. If the driver is doing big block reads, perhaps change to multiple smaller block reads. If already small block reads, either modify blocks to be smaller to avoid the N/A or remove the block completely if not needed.

Regards,

Charles

[sesa102217_brid · Accepted solution]

 @Charles_Murison  the customer will wait for the next release of meter firmware.

Thanks

[arjan_greenwave]

hi,

I have the same problem

Seems that the PM8000 Modbus driver is not working.

When I select PM5560 data is coming through.

Seems like this wasn't resolved?

Regards,

[sesa102217_brid]

Hi, Arjan.

Not yet, but I created a custom driver for pm8000 on comx210,

if you need me let me know that I'll forward it to you.

Send e-mail for me. 

[arjan_greenwave]

arjan@greenwave.co.za

Thank you will appreciate it!

[Romain_Polette]

Hello @arjan_greenwave , 

I have the same behavior on my Com'X510 v6.8.4:

• PM8000 v2.1.0 is working fine with the native Com'X model
• ION9000 v3.0.0 is not working as expected with the native model

Issue is related to the current FW Version 3.0.0 of the PM8000 / ION9000 platform. Things will not change until next release of PM8000 FW release (no date confirmed yet). This is not planned to update the ION native models to change the Modbus Registers polling method.

You can try to apply the workaround provided by Charles above or in the following thread:

https://community.se.com/t5/Metering-Power-Quality/The-Value-of-quot-N-A-quot-register-of-PM8000-fir...

Or also create a custom PM8000 driver mapping the register you want to log and publish.

Regards, 

[Charles_Murison · Accepted solution]

Hello @arjan_greenwave  @arjan_greenwave  @sesa102217_brid 

Wanted to let you know the latest release of firmware is available to address the modbus N/A exception.

https://community.se.com/t5/Metering-Power-Quality/New-Firmware-version-3-1-0-for-Advanced-Meters-is...

Regards,

Charles

[Romain_Polette]

Hello @Charles_Murison , 

It seems that the upgrade to v3.1.0 do not fix the issue with the Com'X.

Update on the following thread:

https://community.se.com/t5/Gateways-and-Energy-Servers/PM8000-predefined-model-for-COMX210-fw-6-8-4...

Regards, 

[Charles_Murison]

Hello Romain,

Randi was able to test with a Com'X and did not have trouble connecting to PM8000 and reading values.

Regards,

Charles