Could you explain in more detail what you did? I’d like to understand.
If you developed this Modbus TCP server on the Envoy, how did you get root access?
What software version is currently running on your gateway?
Could you explain in more detail what you did? I’d like to understand.
If you developed this Modbus TCP server on the Envoy, how did you get root access?
What software version is currently running on your gateway?
Hello,
My Envoy is an Enphase Envoy-S-Standard-EU, hardware reference 800-00553-r02, running firmware D8.3.5289.
To obtain root access, I used the Envoy’s UART serial console, then U-Boot.
The device has a Linux kernel and a recovery initramfs on its eMMC partition. From U-Boot, it’s possible to load these into RAM and boot directly into a BusyBox shell with root privileges. (I’m not going to go into the method here.)
Things got a little complicated when I “bricked” my gateway, without taking the precaution of making a complete dump beforehand…
After quite a bit of searching, I eventually managed to recover the complete firmware via Enphase Installer Toolkit, installed on an old Android phone that I had to root in order to access the downloaded files.
From there, I was able to rebuild the rootfs and get the gateway working again.
Next, I added my SSH public key to /root/.ssh/authorized_keys, then adapted the iptables firewall rules to allow SSH connections from my PCs and block Enphase support
.
Result: I now have permanent root access via SSH on my Envoy, without needing to go back through the serial console every time.
So I can explore the system, do some experimenting and develop my own services, including my second Modbus TCP server on port 1502, while keeping the original Enphase one.
In short, I’ve now got plenty to keep me entertained for a while…
Thanks.
Now I can see clearly what you did.
It’s been at least 15 years since I last played around with that.
I’m no expert, but it occurs to me that the factor 1:1 rule should be interpreted as an equivalence between two equipmements.
Perhaps it doesn’t matter if values are quoted in Watts or VA as long as both pieces of equipment (the PV and the MP2) are expressed in the same units?
The power-limiting setpoints were not being sent to my microinverters by my Envoy Standard (firmware 08.03.5422, without a meter).
Without a CT (Envoy-S Standard non-metered), the Envoy software detects 0 phases, even though my installation is single-phase. This incorrect value prevents the programme responsible for transmitting power setpoints over PLC from running the loop that sends commands to the microinverters. As a result, no limiting setpoints are sent to them.
Temporarily modifying an instruction in memory makes it possible to force the detection of one phase for this loop.
Test results:
Power limitation works correctly even without a meter; the issue is caused by a software limitation that prevents the PLC setpoints from being sent, even though my Envoy is perfectly capable of limiting the power.
I then added control via my Modbus TCP (port 1502), integrated with Home Assistant, allowing me to:
Initial tests show a delay of around 2 seconds between sending the setpoint and its processing over PLC by the Envoy.
Tomorrow, I will take a precise measurement of the delay between sending a power-limiting setpoint and its effective application by the microinverters.