diy solar

diy solar

Megarevo RxLNA Discussion

The firmware install instructions i received from megarevo are no good. I went and bought a USB A-A cable just to find out that the inverter now uses a USBC input in a completely different location. Unless I am blind and dumb. Possible.

So I plugged into the USBC and got nothing in the firmware app (no "COM" option under the 2nd dropdown). Tried rebooting the inverter with cable connected still nothing.

To those who have applied updates, what USB interface does your inverter use? Which version of windows did you succeed with?
 
My units both use USB-C. I installed the update software, then plugged in the USB cable, and the com port shows up in my device manager. I use that com port in the drop down, and it works fine. The only catch is that you need the .axf and .out files in the root directory of your drive or it won't see them.
 
My units both use USB-C. I installed the update software, then plugged in the USB cable, and the com port shows up in my device manager. I use that com port in the drop down, and it works fine. The only catch is that you need the .axf and .out files in the root directory of your drive or it won't see them.
Which version of windows did you use?
 
My units both use USB-C. I installed the update software, then plugged in the USB cable, and the com port shows up in my device manager. I use that com port in the drop down, and it works fine.

First time I did that, my windows recognized the new USB device and fetched a driver from the internet and I got a message that the "usb serial port is now usable" (or something similar)
At that point COM3 was selectable and it seemed to work [TM]
The only catch is that you need the .axf and .out files in the root directory of your drive or it won't see them.
I had in directory few levels deep. Directory should not contain any special characters (like the chinese subdir it is extracted to) and NO SPACES.
But it works perfectly fine several levels deep ;-)

I am using a VM windows10 on a debian linux machine with the USB device forwarded to the VM.
 
DOD. is % you want your battery to discharge to. Grid is when there is grid connected. EPS is when grid is disconnected. return is where it will start to use the battery again after some charge has occurred.

My settings are 90% on grid and 95% on EPS. You may or may not want to discharge your battery that low. 80% would limit cell degradation if that is a concern. I think my return is 85%. So lets say you discharged 90% over night. The next morning you get an hour or two of charge and the battery is now at 80% DOD or 20% SOC, and you get a load greater then what PV can supply. The balance can now be used from the battery instead of grid.

Run settings I have yet to fully understand. The GSI manual mentions them but no instructions. I had issues when using what I think was react mode. Changed to PF mode and seemed to not have same issues. But take that with grain of salt.
 
I tried a different W10 machine and it worked o_O

It would be nice if return is not an absolute value, but relative to the grid status. For example:

grid discharge = 80
off grid discharge = 95
return = 20

grid discharges to 80, then charges to 60 (40 SOC) before discharging again
off grid discharges to 95, then charges to 75 (25 SOC) before discharging

I just set mine up like this, so we'll find out soon if that's how it works!
 
I tried a different W10 machine and it worked o_O

It would be nice if return is not an absolute value, but relative to the grid status. For example:

grid discharge = 80
off grid discharge = 95
return = 20

grid discharges to 80, then charges to 60 (40 SOC) before discharging again
off grid discharges to 95, then charges to 75 (25 SOC) before discharging

I just set mine up like this, so we'll find out soon if that's how it works!
Return = 20% DOD would be 80% SOC. So if grid discharged to 80% DOD the battery would not return to discharge until it reached 80% SOC.

Should be 80% DOD with return set at 60% DOD if you want to have discharge set to activate at 40% SOC
 
After the firmware update I am still showing 0 load on GRID, even when it's definitely being used. Anyone else having this issue?

In this screenshot you can see 749 pv, 1610 charge, 268 consumption, meaning ~ 1.1 KW should be coming from grid (assuming I understand this correctly)
 

Attachments

  • flow.png
    flow.png
    37.3 KB · Views: 13
After the firmware update I am still showing 0 load on GRID, even when it's definitely being used. Anyone else having this issue?

In this screenshot you can see 749 pv, 1610 charge, 268 consumption, meaning ~ 1.1 KW should be coming from grid (assuming I understand this correctly)
Solarman is lacking or more then likely the Megarevo does not send that data. Mine shows same thing. I think the CT that measures grid is inside the unit so only reading what is on the grid connection, not from the CT's.

Here is mine this morning. Battery reached the limit of DOD, so only a little bit of PV, and rest is from grid to the EPS panel.

Screenshot 2022-08-04 at 07-43-13 SOLARMAN Business.png
 
The Megarevo display also shows 0A always. So it doesn't have the right data in the first place as far as I can tell.

What software is your screenshot from?
 
@flygeek Have you made anymore progress on the modbus protocol? I've just started playing around with scanning the registers using python and umodbus with the PVSolarman5 script. It seems to be easier to access via IP & Serial# than making a cable. As you've guided me, I've found the battery info in the 8850 area, notable SOH at 8856, and battery voltage at 8857, etc. I'd like to get these integrated into something like home assistant or ideally just into graphana. But its going to take quite a while to match all the registers by comparing the returned data vs what the inverter is reporting on screen. Have you found a better source than the GOODWE document?

Looks like daily production at 12627 and daily consumption at 12631
 
Last edited:
I just installed HASS today, and I've been playing around all day trying to pull the numbers from the WIFI stick into the interface. I have found a few parameters, but today is my first day ever with Home Assistant, Python, Modbus, etc. LOL. Its been a looooong day. :ROFLMAO:
 
Back
Top