powermbr

I guess this is the problem with the cheap chinese knockoffs, they have critical bugs that you are pretty much on your own to figure out. I've asked for help from jesudom the company and so far -- **crickets**.

Thanks T but sadly Max E is not the same model.

I have two AXPERT MAX II 11KW in parallel both on fw 73.03. The slave reported error F90 earlier today and I'm unable to clear. Does anyone know of any factory reset commands I can send via COM. I've tried FRTCRST but no luck. Have also tried resetting via front panel ( power on , hold return and up/down). Last resort is to reflash firmware in the hope that clears the error. Any help appreciated and/or linkl to firmware 73.03 or higher.

Hello Screech, Your post is 3 weeks old so you may have resolved your issues since. In any case, I have 6 pytes batteries and had similar issues. Stupid question, but can I assume you have it connected to the rs485 port and not the console port on the first battery? I set the protocol to Lib and used the follow pinouts which are also specified as compatible with MPP.

I just dont understand how they can put out critical firmware with so many bugs. According to solar assistant my inverters just sent an 88KW spike back to the grid except grid-tie is disabled. Be aware that if you install the same firmware you might see similar issues.

I did both and I don't think the order matters. What do you use to monitor the system? I use solar assistant and the latest beta version has some decent automation added which forces the state of lots of different parameters during specific times such as output source priority. It runs on a raspberry pi and super easy to setup. I think I would have the same issue as you without it ie it would be more than 15 mins or so of loss per hour as you say. You're probably looking at 100 bucks to get a pi and the software and maybe another 10 or 20 for a console cable to connect to your inverter and batteries.

EASUN sent me some firmware for my EASUN INFINI V IV 5.6K as I had the same problem with paralleling 3 of the buggers ie straight to battery voltage fault within a few seconds on power up. The fw update resolved the parallel issue but I am honestly sick of the things. To clarify I have them in an off grid config wth grid backup and pytes lithium batteries but I have issues such as grid spikes every hour of around 500W for 12-15 mins where the mode switches from solar/battery to hybrid for no reason that I can fathom which adds 100GBP to my bill each month(UK) and phantom power surges back to the grid. EASUN have ignored requests for help so my advice is steer clear if you will, as I do, need support. I also have two external fans cooling them constantly as they overheat easily but I fully expect them to fail by the end of the year. 4165-07G FW Upgrade_28066_DSP INFINI V IV 5.6K 56.12.7z Remote Panel - 3573-11S3 INFINISOLAR V IV 80.41.7z

NA

Hello All, I have solar assistant monitoring my system(solar/battery/axpert 11kw) with the mqtt server enabled and I have a linux server that runs a python script every couple of minutes to query and modify the settings based on the time and/or battery soc. The system has been running fine since I installed but I made a change to the script last night to set the solar charge max to 10A at the end of the cycle which triggered F08 which I verified from the log outputs of the mqtt script. I've commented the solar charge max changes from the code so lets see if that makes a difference tonight.