Carefull when using P1 port. During my investigation and ESP32 program build, I had a 485 monitoring unit to see what is on the line.
Only with Total power and some currents, MP2-GX will NOT start communicating.
There are more registers asked by MP2 and meter shall answer to trigger a start. Yes, after communication is started, then currents, voltages and power are the ones requested every 100ms. Frequency and consummed / injected power, every 2-5 sec, etc.
I use an ELGRIS P1 netmeter so i don’t read the data directly from the P1 meter. Also a separate GX-device. Do You mean there is a synchronisation mismatch? Or is the P1-meter to slow?
Have you also physically handed the PV to the ACout? Normally, ESS handles this automatically through the MP2
Thx for your reply. Indeed the only good reference is the (total) power. I use some extra meters to adjust some data via nodered. I don’t use the 3 MP2’s as a 3-phase system but as 3 single mono systems with common battery.I also came to the conclusion that zero feed didn’t work well in combination with peak shaving. Peak shaving seems good for high load (more frequently load > PV) and ‘Grid setpoint’ for (more frequently) higher PV. So in winter and autumn: P.S. and in spring and summer: grid setpoint. Do you have any experience withs these parameters or any suggestions?
Well yes thats also a possibility.
Played a bit with peak shaving, but didnt use it seriously. Im happy with zero-feedin. If you want to reach more people with that question i suggest opening a new thread. Im sure theres people using it.
I can’t call it “mismatch”. Just GX will need certain answers (others than C, V, P) to start communicating. P1 speed is just 1 second. For GX might be slow, but if you accept some losses, then is fine.
I was referring to reading P1 directly. More fun and cheaper. But ELGRIS may know already what to provide to your GX.
