mihaigsm2003

This is factory firmware version 72.08 for the Axpert Max E 8kW '28066 non-Twin. Do not use with any other model or version.
Use at your own risk. The hex file is dated 23/10/2024. As of this post, it is the most recent firmware for this model, but it does not have the "presumed good" MPPT logic. As a result, low light performance may be poor. For better MPPT performance in low light, consider factory firmware version 72.75, or patched firmware version 272.66.
Firmware upload instructions for models with a removable display.
This firmware processes the QDOP command, so with suitably recent display firmware, it should support SoC% for settings 12,13, and 29 when connected to a suitable battery's BMS.
MAX_8K_72.08.7z

The axperts can throw odd errors if the SPS capacitors, in particluar the ones on the -12V rail have failed. It's worth replacing all the SPS capacitors if you can.
I have seen the output IGBTs fail when trying to invert under the high voltage however they test fine in circuit and using a multimeter. Maybe there is a similar situation here and they are dragging the battery into protection mode and triggering F03 and the battery protection resets when you measure the battery? Here's a link showing this situation https://powerforum.co.za/topic/14666-repair-of-axpert-inverters-a-journey-started/page/27/#findComment-214451

Serial number can be changed ! Settings also. also i read chips 24256, i put backup here. Use only memory 24256, or M24C256  32k
 
8Kw_good.bin 11kw_good.bin

i test all eeproms chips from same control board with problem: i can read data but i cand write, i try erase chip but data still there, chips are broken. i place new chip with data from bad chip, remake serial and inverter work very good. will see in 60-90 days if problem is. Also, monitoring software no report anymore "eeprom fault"!

Serial number can be changed ! Settings also. also i read chips 24256, i put backup here. Use only memory 24256, or M24C256  32k
 
8Kw_good.bin 11kw_good.bin

That may or may not be a Voltronic Infini model. I don't know them well, but I do collect some of the firmwares.
What are the present firmware versions?

I can replace uC, but i don't find firmware with bootloader to write via jtag, also can't read from good control board

Hallo!
BOOM!!! this processor (STM32F107VCT6) is not read protected!!! I can read good processor and write in new processor data to repair any communication board and display detachable for voltronic inverters! I see any board have jtag connection for this.
Now can use empty processor without bootloader.
I have some readed data from STM32F107 and will post soon




 


 
 

hi, i found this, maybe help:
https://www.amosplanet.org/how-to-activate-control-board-of-off-grid-inverter-that-failed-upgrading/#comment-1451

And here is the remote display/panel(U2: 80.35)) firmware for EASUN/POWLAND...IGRID SV IV 5.6K (parallel)
Remote Panel - 3573-08S7 INFINISOLAR V IV 80.35.zip

i test all eeproms chips from same control board with problem: i can read data but i cand write, i try erase chip but data still there, chips are broken. i place new chip with data from bad chip, remake serial and inverter work very good. will see in 60-90 days if problem is. Also, monitoring software no report anymore "eeprom fault"!

True, but not many people know the appropriate command (or how to change the data in the EEPROM directly).
The thing that concerns me is that the serial number is used as part of the authentication of the firmware, and there is a possibility of running into fault code 90 with unpatched firmware, and some patched firmware. A few models can't even be patched as the firmware update files are not yet available. You might be able to get your supplier to send you an appropriate setserial program that will fix it, but that takes time, and they will be wanting to make sure that you aren't running Voltronic firmware on a clone. Meanwhile, fault code 90 bricks the inverter.
I would check the result of the QBOOT command (you might need to use ATE0 to get it through, use AET1 afterwards to restore normal command flow). If it returns 0, then you are likely to get fault code 90 60 days after changing the serial number. The setserial programs send a mysterious and undocumented command with cryptographically generated parameters; it's not feasible for anyone other than Voltronic to use this command to normalise the EEPROM contents.
This is a hazard of living in the clone era, unfortunately.

Hi, i will get correct firmware for this inverter: DSP and MCU, tested on easun 11kw TWIN, communication  with battery work
11kw.zip

This is full firmware with bootloader. Write with jtag. Firmware for serial like U2 not exist for VE series

Firmware for Easun 11kw (Tested!)
MAX11K_TWIN_DSP_6407.7z Remote Panel_Reflash_MCU(38.06).rar

Hi, i will get correct firmware for this inverter: DSP and MCU, tested on easun 11kw TWIN, communication  with battery work
11kw.zip

Thi is Model:

This come to me with no communication with pylonytech. I try many version of display (MCU U2) no way to communication. After, i write DSP firmware for 8kw, now i have communication, but inverter show in application 8000W as model.
Original Vers was 64.03 for U1 and 38.04 for U2

Thank yooouuu!
Flash worked very well (used the cable with 1 kohm resistor hack on white wire)
Now i have 112.19! Watchpower certify this by version number, and it's kept 11 KW, version of Axpert Max 1 - MPP Solar 11kw)
I connected MPP Solar inverter with the Pylontech battery bank with cable ( 3-8; 5-7 pins) and now communication with battery works!
Thank you very much Coulomb for your valuable work!
 
and to Mihai for opening this topic
 

Thi is Model:

This come to me with no communication with pylonytech. I try many version of display (MCU U2) no way to communication. After, i write DSP firmware for 8kw, now i have communication, but inverter show in application 8000W as model.
Original Vers was 64.03 for U1 and 38.04 for U2

Use GD-Link for GD32, not work with ST-Link, also need aplication for GD32
i programmed GD device with jlink interface

For 5 kW models and above, the block diagram is:

So for the 450-500 V max PV models (green paths, not blue paths), PV voltage is boosted to bus voltage, then pushed right to left in the diagram above through the buck converter and DC-DC converter. The buck converter is what regulates battery charging current (PV or utility). All utility charging (only for non-King 5 kW models and above) is by pushing power backwards from the AC-out (connected to AC-in via the left switch) to the DC bus via the full bridge (DC↔AC converter).
My belief is that most of this is due to leakage from PV terminals to earth. The high PV voltage Solar Charge Controllers are referenced to the negative side of the DC bus, since the output is the DC bus itself. This has high potentials with respect to earth, because the neutral output is at basically earth potential, and so earth is connected alternately to the negative end of  the DC bus or to the positive end. That means that the PV terminals have hundreds of volts with respect to earth half the time, and currents from earth into the neutral output of the full bridge can push up the bus voltage (I think). I haven't sat down and proven it to myself, but it seems likely.
This increase in bus voltage is not under firmware control, so it can ramp up over seconds or minutes to exceed the safe level, and fault code F08 results.
PV panel frames have to be earthed, especially in South Africa where there is a lot of lightning activity, and rain in conjunction with bad wiring practices and/or cheap panels can cause leakage to earth. I believe that Voltronic in their user manuals actually warn that only certain types of PV panel should be used with these high voltage PV models, or the frames should not be earthed at all.
It should be relatively easy to establish this by switching in and out strings of panels and hosing one of the strings (use care not to get electrocuted by the water stream!!). This is one of the reasons that I don't like these high voltage PV models, especially Voltronic ones that don't have insulation monitoring.

Hey guys
 
Thanks a million! I had the same experience with my 48V VMIII tonight. Updated main FW to 41.17 as per link in another thread on this forum, but display was not working after the update. Tried what jarjarbeens  said  with no success initially. I Just kept trying and trying and FINALLY got communication between the flashing tool and the inverter after about 20 attempts, trying different sequences.  When I powered the inverter on after the Main FW update, you could hear relays clicking with the fans on. The fans would go off after a few seconds, with some relay clicking that followed.
I followed what Jajarbeens posted above. The only thing I can add is that the power button needs to be IN (on) on the removable display. I got success when I pressed "Update MCU" on the flash tool about 3-4 seconds after I switched the AC power to the inverter on, just before the fans stopped. I figure that would before the normal starting 6 second countdown elapsed. Took about 20 seconds and then the flash started. Whole flash took 9 minutes and the display came on immediately after the flash completed. Restarted the inverter and confirmed that the Main FW was indeed 41.17, and the MCU version is 02.66 (that coulomb provided).
Once again thank you for all the generous information on this forum.

Firmware for display or communication board is not protected.

I started a new thread in the Axpert Firmware sub-topic for this. Let's continue there.