Hi all,
Pretty new to Modbus, how do I set up this register to be displayed in tag browser?
I tried ns=1;s=[Power Meter N2]HR1700 but no luck.
Appreciate all your insights!
PM800 Register List FMW_11.500_P.pdf (1.9 MB)
Do you need to provide a slave adress? Like
ns=1;s=[Power Meter N2]0.HR1700?
Did you enable the "Zero-based Addressing" at the connection configuration under advanced settings?
Do you get a strange value or error?
Can you try HRD (double) and or HRF (float)
The docs show a size 4 but the not the type other than mod10 which makes no sense.
Edit: mod10 should be a floating value
Tried HRD and HRF no luck. Pretty sure it's an INT type.
1700 is de energy input from like solar.
I think you where looking for 1708 energy Real Out.
Dont forget that the data type is WH from modbus, KW is showing in the dashboard.
Do you get any value? Zero addressing can also be checked by setting the adress on 1707.
Does the GW show any errors?
This should likely be:
ns=1;s=[Power Meter N2]1.HRD1700
1 Like
1 Like
"mod10" is a Schneider-specific multi-word encoding for very large numbers. It is not supported by Ignition's native driver. You can bring in the individual words as separate tags and construct the composite with an expression tag.
This data type is directly supported by my alternate driver.
2 Likes
I actually have some pm800 series meters and had to figure this out. I read the 4 registers in a UDT and then created an expression tag to combine them.
({[.]kWh_Reg4}*10000^3 + {[.]kWh_Reg3}*10000^2 + {[.]kWh_Reg2}*10000 + {[.]kWh_Reg1})/1000
1 Like
how do you set up the opc path of each Kwh_Reg?
Thanks all
Apparently it should be 1.HR1700 , then 1701..1704. Then use josborn's xpresion to come up with total kwh.
Hi all,
Just encountered to another issue. When I tried to create a OPC 1.HR1700 to one power meter, its modbus connection keeps disconnect and connect. The other one is fine!
Log saying Modbus TCP Socket Connection Closed, DriverState was Connected
Is the GW and the Meter on the same Factory/location? Or are they connected over a VPN?
The Ignition server is on a VM. But this issue is happening with the meter not on the same location with the good ones. What do you think Rick? Firewall?
When the meter is connected over a VPN the connection can become unstable due to the connection speed or drops and more cases.
The firewall is not the problem once connected.