Skip to content
View in the app

A better way to browse. Learn more.

Power Forum - Renewable Energy Discussion

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Axpert Max II, 10kW

Featured Replies

Now 00056.06 and 00656.05 (latest version)

The effect of getting stuck also occurs, so the patched firmware has an advantage in the morning and evening.

233336014_2023-01-09PV1Inverter1an2.thumb.PNG.84ce89488bb78801395e6037739eba9c.PNG

Now one array with 10 PV modules and the other with only 4 modules (PV2).
The hanging has a stronger effect on PV2 because Voc is lower. Please note V (thin line).

1130375347_2023-01-09Inverter1.thumb.PNG.8e9691db52fc964748a83f365f536445.PNG

Edited by Volker

  • Replies 236
  • Views 38k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Try to ask for firmware your supplier, is it possible that you can succeed. I have done that several times but with no results unfortunatelly

  • I've just realised another possible reason for the jitter. In the previous patched version, when the MPPT reference voltage was set to max (450V), the direction was set to 0, meaning that we expect th

  • I think it has. I should be doing the resets after an adjustment cycle, when the accumulated power is set to zero, so the next cycle, you'll get a clean measurement of the difference between 175 V and

Posted Images

6 hours ago, Volker said:

I soldered a diode between Bus+ and Solar+ and disconnected Gid from the PLC; SOLAR is connected

I thought this made some sense if the solar cable is disconnected. When the boost converter is working, bus voltage is higher than PV voltage, so i assume that the diode was connected such that power can flow from PV to the bus. What is this expected to achieve?

If the diode is connected the other way, then as soon as the boost converter boosts, you are trying to boost in circles. Also, the bus soft start circuit will attempt to run the solar charge controller, but it can't. Hence fault code F09.

What am I missing here? 

On 2023/01/10 at 8:02 AM, Volker said:

Now 00056.06 and 00656.05 (latest version)

The effect of getting stuck also occurs, so the patched firmware has an advantage in the morning and evening.

Aren't these both patched versions? 56.06 being Georg's patches on 56.05?

Edited by Coulomb
Typo

7 hours ago, Coulomb said:

I thought this made some sense if the solar cable is disconnected. When the boost converter is working, bus voltage is higher than PV voltage, so i assume that the diode was connected such that power can flow from PV to the bus. What is this expected to achieve?

If the diode is connected the other way, then as soon as the boost converter boosts, you are trying to boost in circles. Also, the bus soft start circuit will attempt to run the solar charge controller, but it can't. Hence fault code F09.

What am I missing here? 

The diode goes in the same way as the two diodes on the MPPT board in the direction of the SPS board (all cathodes to SOLAR+). Since Georg probably connected the SOLAR cables directly to the bus, my diode should have worked in the same way!?
(I would have liked to minimise the 300W inherent losses of the 4 active inverters. The two inverters that are in standby mode in winter only need 10...15 W each.)

_____________________________________________________________________________________________________

Your circuit is correct, by the way. PV- is connected to SOLAR- and Bus-. The two PV inputs PV1+ and PV2+ are directly connected to SOLAR+ via the two diodes.

Edited by Volker

On 2023/01/10 at 4:58 AM, Coulomb said:

Aren't these both pstched versions? 56.06 being Georg's patches on 56.05?

Yes, Georg's version is called 56.06 (based on 56.05)

Edited by Volker

  • 2 weeks later...

I am a little frustrated as the inverter readings used so far are not really accurate.

Examples:
With a PV field I always had +8 to +15 % more power than with the almost identical field, although due to some large conifers at my neighbour's I would expect slightly less yield. After switching to another inverter, the field was now mostly lower (-5 %). The PV power measurement is very inaccurate.
Since I also read out the pylon readings, I see at least 500 W less charging power than the inverters report. Often the inverters show that the battery is being charged and Pylon shows discharging. There are also differences when discharging, and here too the own consumption of an estimated 150 W per inverter and the losses during charging and discharging are not displayed. E.g. after 10 days the inverters show +100 kWh (charge - discharge), but Pylontech shows only +10 kWh and SOC is almost the same after the 10 days.
In battery mode, consumption from the grid is also not displayed by the inverters.

I have daily losses of approx. 3.x kWh per inverter. I do not have independent measurements for an exact measurement. Actually, a measurement value recording system should be installed at all inputs (PV, grid) and at the AC output. At the moment, I can only trust the pylon readings but not the values measured by the inverter. Both measurement errors and conversion losses of up to 20% are possible.
Since I have little PV power in winter and also little consumption, my total losses reach almost 50% (PV -> Bat -> AC, PV -> AC and Grid -> Bat -> AC). If I had switched off the system and thus lost the daily average of 14 kWh PV, my grid consumption would still not be higher...
(But in summer I was able to supply myself, despite much higher consumption).

Conclusion: I have to calculate with losses of 3.5 kWh per inverter and day. The PV measurements taken so far should be interpreted with caution, as an error of up to 20 % is possible.  Self-consumption and losses cannot be seen with the measured values supplied by the inverter.

 

On 2022/12/29 at 7:39 AM, Coulomb said:

Good idea, and easy to implement. It eliminates one change.

This is patched firmware version 656.05 (yes, I had to use a different method to make the version number come out > 655.36, the limit for 16 bits). It's identical to 556.05, except that the resets are considered every minute instead of every 5 minutes. In the mornings and afternoons, 5 minutes is a long way up or down the ramp.

Use at your own risk.

OG-10 DSP Reflash_656.05 patched.zip 1.6 MB · 7 downloads

The firmware is now running on all inverters, it works satisfactorily with one exception: The PV array with only 4 modules only has a Vmppt min/max of 120V/170V, here the setting of the voltage naturally not pertect - the power drops.

I would be pleased if a change is still possible. As already written

it would make sense to do nothing below 89 volts and then only set it only to 120 V or to test the change with 10 V add - perhaps this intervention is already sufficient? It may not be enough!

The power drop is not visible in the first diagram (resolution) but you can see the voltage fluctuations. In diagram B you can see it.

2023-01-23 PV1 10 modules and PV2 4 modules Inverter 1.PNG

2023-01-23 PV1 10 modules and PV2 4 modules Inverter 1 B.PNG

First of all congrats for the great thread!

I would like to point out one thing that I noticed when looking at different manuals from voltronic vs clone inverters.

When you look for example at the Growatt spf 5000 es, that is made by voltronic, we can see that it has a mppt voltage range of 120v-430v but it has a start up voltage of 150v. Now if we look at the manual from the voltronic mks iv you can see that it has the same mppt voltage range of 120v-430v but it is missing the start up voltage.

 

Can it be that Growatt did see the mistake in the Voltronic devices and added the extra start up voltage in the bios of the inverter to only begin producing from 120v on to overcome this clamping?

Maybe it would be interesting to see what the code is for the Growatt inverters and compare them with the voltronic and maybe try out a moded bios version with start up voltage added maybe 120v for the 8kw models and 150v for the 5kw/6kw models.

 

I would love to see a powercurve from the Growatt spf 5000 es inverter! maybe DavidPoz from the below channel could help us here.

 

 

 

Growatt.JPG

voltronic.JPG

On 2023/01/26 at 5:12 PM, Jsengxx said:

When you look for example at the Growatt spf 5000 es, that is made by voltronic,

Err, do you have evidence for this? I notice a lot of similarity between Axpert and Growatt firmware code, but also a lot of differences. I always assumed that Growatts started out as Axpert clones, then diverged, and were always made in a different factory by a different company.

On 2023/01/26 at 5:12 PM, Jsengxx said:

Can it be that Growatt did see the mistake in the Voltronic devices and added the extra start up voltage in the bios of the inverter to only begin producing from 120v on to overcome this clamping?

That's not a really bad idea. I happen to have collected a few Growatt firmwares about 2-3 years ago, then gave up as it was hard work and didn't look like it would do much good.

But IF there is an equivalent MPPT control function, it would be interesting to compare with what is in all the Voltronic firmwares (with minor variations). So I had another look, and made some progress, but for technical reasons it's a lot harder to read than most Voltronic firmware. So I still haven't even found the BusBatProtectTask that calls MPPTControl() in Voltronic firmware.

But I've homed in on what I'm currently calling Task2, and I've eliminated perhaps a quarter of the candidate function calls. It's unlikely to bear fruit, but I'll keep it in mind and nibble at it as I find time and think of it.

I'm not at all convinced that it's the startup voltage that would make a big difference, but it's still a reasonable idea to attempt to compare the code. It could well be that other engineers' eyes have spotted the MPPT error while Voltronic doesn't even seem to be aware of its existence.

2 hours ago, Coulomb said:

I'm not at all convinced that it's the startup voltage that would make a big difference, but it's still a reasonable idea to attempt to compare the code. It could well be that other engineers' eyes have spotted the MPPT error while Voltronic doesn't even seem to be aware of its existence.

If you look at the Infinisolar line up for example that is the better or next line up of inverters from Voltronic, they all have Start-up Voltage and Initial Feeding Voltage for example 120vdc/150vdc this means that the inverter will only wake up at 120vdc (I think it is even wake up at 150vdc and start producing) and start producing at 150vdc and only stops producing below 120vdc. From what I can see from the max and mks line, this is not present in the inverter and I think the inverter is trying to produce right away at the bottom of the MPPT range and in practice the inverter will begin producing, panels get warm and you will get the drop in voltage, going below MPPT range, and inverter gets stuck. There is no margin like in the other inverters, begin production at 150V but you will have 30V (the 120v start up voltage) sitting below for the inverter to work properly.

  • 3 weeks later...

Greetings.  I have an Axpert MAX II 8KW and it has the same voltage problem at 90V.  But to my surprise firmware 81.03.  Has anyone encountered this firmware or a compatible patched firmware?  Thank you

20 hours ago, dobris22 said:

But to my surprise firmware 81.03.  Has anyone encountered this firmware or a compatible patched firmware?

81.xx seems to be the firmware series for Axpert Max II 8kW with the '28066 processor. Almost certainly 81.03 is an earlier version of 81.04 and 81.05. There is patched firmware version 281.05 for 200 V MPPT minimum.

Edit: In the files section:

 

Edited by Coulomb

10 hours ago, Coulomb said:

81.xx seems to be the firmware series for Axpert Max II 8kW with the '28066 processor. Almost certainly 81.03 is an earlier version of 81.04 and 81.05. There is patched firmware version 281.05 for 200 V MPPT minimum.

Thank you @coulomb. I did a reflash and everything seems to work so far. It should be cloudy tomorrow morning, so I'll see how the inverter reacts. I really admire your work. 

On 2023/02/14 at 12:36 PM, Coulomb said:

81.xx seems to be the firmware series for Axpert Max II 8kW with the '28066 processor. Almost certainly 81.03 is an earlier version of 81.04 and 81.05. There is patched firmware version 281.05 for 200 V MPPT minimum.

Edit: In the files section:

 

Hello.
You made this firmware for me a few months ago.
I am grateful for it! It has been on the inverter ever since.
I would like to ask if you have changed it since then? Did you just change the PV voltage, etc.?
Should I update this or is it the same as a few months ago?
I have a display firmware update. Max 2 8kw, dsp28066. Are you interested? Shall I send it?

On 2023/02/16 at 7:25 AM, Rozsda said:

Should I update this or is it the same as a few months ago?

It hasn't changed, and it's still the latest for that model and processor. If I change the patched firmware, I'll always give it a new version number.

On 2023/02/16 at 7:25 AM, Rozsda said:

I have a display firmware update. Max 2 8kw, dsp28066. Are you interested?

Yes. I think all I have for Max IIs is 122.15 that is also for VM IVs. You could attach it here, or I could PM you with a link to my Google Drive.

6 hours ago, Coulomb said:

Nem változott, és még mindig a legújabb az adott modellhez és processzorhoz. Ha módosítom a javított firmware-t, mindig új verziószámot adok neki.

Igen. Azt hiszem, a Max II-ekhez csak 122.15 van, ami a VM IV-ekhez is. Csatolhatod ide, vagy küldhetek egy linket a Google Drive-omra.

Here is the update of Axpert MAX 2 display for Gygadevice chip.
I installed it.
Old firmware version 122.14
New firmware version 22.20
There will be even more chaos!

Remote Panel_Reflash_MCU(22.20).rar

19 hours ago, Rozsda said:

I installed it.
Old firmware version 122.14
New firmware version 22.20

Annnnd... Did it work? 😀

It turns out I had that firmware already. So I had another look at it, trying to figure out why it is supposed to work on both chipsets. All I learned is that my original theory about what is different for the two chipsets was wrong. Sigh.

Quote

There will be even more chaos!

I don't get what you mean by that.

  • 2 weeks later...
On 2023/02/14 at 1:36 PM, Coulomb said:

81.xx pare să fie seria de firmware pentru Axpert Max II 8kW cu procesorul '28066. Aproape sigur 81.03 este o versiune anterioară a 81.04 și 81.05. Există versiunea de firmware corecţionată 281.05 pentru minim 200 V MPPT.

Editare: În secțiunea fișiere:

 

Hi Coulumb, do u know if MAX II 11K twin have the same problem with 90v input? If yes, can be solved ? We have firmwares for it ? Thanks

Screenshot_2023-02-27-15-13-30-270_com.android.chrome.jpg

Edited by add1c7ed55

2 hours ago, add1c7ed55 said:

Hi Coulomb, do u know if MAX II 11K twin have the same problem with 90v input?

I don't know for sure, but the MPPT control code looks very similar to all the others. So my strong guess would be: yes.

2 hours ago, add1c7ed55 said:

If yes, can be solved ? We have firmwares for it ?

It would be solvable to the extent that the others can be "solved". Yes, I have factory firmwares version 64.61 for the '28066 DSP and 64.07 for the '2809 DSP.

3 minutes ago, Coulomb said:

Nu știu sigur, dar codul de control MPPT arată foarte asemănător cu toate celelalte. Deci presupunerea mea puternică ar fi: da.

Ar fi rezolvabil în măsura în care celelalte pot fi „rezolvate”. Da, am versiunea de firmware din fabrică 64.61 pentru '28066 DSP şi 64.07 pentru '2809 DSP.

And for max II 8k too ? Have firmware for this too ?

4 minutes ago, add1c7ed55 said:

And for max II 8k too ?

Yes. I've already done a patched firmware: 286.05.

4 minutes ago, add1c7ed55 said:

Have firmware for this too ?

I only currently have 86.04 ad 86.05, both for the '28066 DSP. 

18 hours ago, Coulomb said:

I don't know for sure, but the MPPT control code looks very similar to all the others. So my strong guess would be: yes.

It would be solvable to the extent that the others can be "solved". Yes, I have factory firmwares version 64.61 for the '28066 DSP and 64.07 for the '2809 DSP.

The 11k max twin that i want to buy have firmwares: 

U1: 64.03

U2: 22.12

 

What do u think ???

 

2 hours ago, add1c7ed55 said:

U1: 64.03

U2: 22.12

What do u think ???

Looks like 64.07 will be a nice update for it, even just factory. But of course, we all want an MPPT that performs.

So: suitable for patching.

1 hour ago, Coulomb said:

Se pare că 64.07 va fi o actualizare plăcută pentru el, chiar și doar din fabrică. Dar, desigur, cu toții ne dorim un MPPT care să funcționeze.

Deci: potrivit pentru petice.

U said here that for AXPERT MAX 2 11KW have factory firmwares version 64.61 for the '28066 DSP and 64.07 for the '2809 DSP.

And in the other topic, said that dont have nothing for max 2 11k, dont understand...sorry...have or dont have ? Cause if have i want to buy that inverter..if not have..i wont.

Edited by add1c7ed55

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.