On 04.01.2023 at 14:22, Coulomb said:

Impresia mea este că firmware-ul din fabrică cu cablul solar deconectat era încă blocat la 90 V uneori.

Deci, ce părți trebuie să rămână și ce părți merg?

@Georg594, ceva ganduri?

How is better now, with solar cable disconnected only, or with the grid cable out too ? Which is the difference???

On 2023/03/01 at 12:29 AM, add1c7ed55 said:

And in the other topic, said that dont have nothing for max 2 11k, dont understand...

Firmware availability changes quickly at times.

Plus, I get confused over whether a firmware is for Max 1 or Max II. [ Edit Jan 2024: I can tell the difference now. There is a call to a function that controls the LEDs for Max E (=1) models; this is not present in Max II models as the display controller, being built-in, has access to the LED ring and takes over this chore. ] It seems that there is a Max E 11kW, but only in Twin and Duplex variants. I've not seen any Duplex firmware as yet.

For the Axpert Max II 11kW non-twin, I have 57.61 for '2809 and 91.70 for '28066. There is already patched firmware version 291.70, based on 91.70.

I don't yet know if you can use twin firmware in a non-twin, or standard firmware in a twin (ignoring the second set of output relays and connectors).

I'm hoping to find time to do a "what firmware is that?" post one day and attempt to keep it up to date. Until then, things are somewhat confusing, sorry. It drives me crazy too 🤪

Edit: Also, my bad: I didn't mention that the firmwares I said I didn't have were already-patched ones. Sorry for the confusion.

Edited January 31, 20242 yr by Coulomb

3 hours ago, Coulomb said:

Disponibilitatea firmware-ului se schimbă rapid uneori.

În plus, sunt confuz dacă un firmware este pentru Max 1 sau Max II. Se pare ca exista un Max E 11kW, dar doar in variantele Twin si Duplex. Nu am văzut încă niciun firmware Duplex.

Pentru Axpert Max II 11kW non-twin am 57,61 pentru '2809 si 91,70 pentru '28066. Există deja versiunea de firmware corecţionată 291.70, bazată pe 91.70.

Încă nu știu dacă puteți utiliza firmware-ul dublu într-un non-twin sau firmware-ul standard într-un geamăn (ignorând al doilea set de relee de ieșire și conectori).

Sper să găsesc timp să fac un "ce firmware este?" postează o zi și încearcă să-l ții la zi. Până atunci, lucrurile sunt oarecum confuze, îmi pare rău. Și pe mine mă înnebunește 🤪

Edit: De asemenea, răul meu: nu am menționat că firmware-urile pe care am spus că nu le am erau deja patch-ate. Ne pare rău pentru confuzie.

And for the 8k max II have firmware?

5 hours ago, add1c7ed55 said:

And for the 8k max II have firmware?

For the non-twin models and '28066: yes: 81.04 and 81.05. There is even 281.05 patched firmware.

I have no firmware for any other Max II 8kW models: either the '2809 or twin variants.

On 2023/03/01 at 12:35 PM, Coulomb said:

I'm hoping to find time to do a "what firmware is that?" post one day and attempt to keep it up to date.

I've started it; let's see if I keep it up to date:

https://forums.aeva.asn.au/viewtopic.php?p=95278#p95278

@Coulomb , Hi, Isn't there a new firmware for Aexpert Max II 10 Kw? Tx .

 

 

9 hours ago, ClauBebe said:

Isn't there a new firmware for Axpert Max II 10 Kw? Tx .

None that I have seen, unfortunately. Firmwares have dried up a bit with Segen tightening up access, and for whatever reason 10 kW firmwares don't seem to come out as often as say 11 kW firmwares.

On 2023/05/06 at 4:04 AM, Coulomb said:

None that I have seen, unfortunately. Firmwares have dried up a bit with Segen tightening up access, and for whatever reason 10 kW firmwares don't seem to come out as often as say 11 kW firmwares.

 

Hi Coulomb, I've got a Kodak OG 10kw from the store: https://powerforum-store.co.za/collections/inverters/products/kodak-solar-off-grid-inverter-mksiii-5kw-48v

Main CPU version is 82.04 and Secondary is 35.03.

Am I correct in saying the below 2 FW are the latest available?:

 

Just confused about going "back" to 22.20 on the display firmware? You also mentioned somewhere (I've been doing a lot of googling) a 291.70 patched main firmware but I can't find it anywhere.

Scott

[img]https://i.imgur.com/5MOIULL.jpg[/img]

 

Edited July 25, 20232 yr by LiFePOWER
.

3 hours ago, LiFePOWER said:

Am I correct in saying the below 2 FW are the latest available?:

Those are both '2809 firmwares; 56.05 is the later of the two (March 2022 versus September 2021).

But you have a '28066 processor, so you need 82.xx firmware. Unfortunately, I've not seen any of these, and as far as I know there are none available for downloading.

20 hours ago, Coulomb said:

Those are both '2809 firmwares; 56.05 is the later of the two (March 2022 versus September 2021).

But you have a '28066 processor, so you need 82.xx firmware. Unfortunately, I've not seen any of these, and as far as I know there are none available for downloading.

 

Damn, ok thanks!

Here is a the DSP firmware for the MAXII10k inverter: Version 56.07. Despite the information to the manufacturer, the 90V problem has not been solved! (If the voltage is clamped at 90 V and the solar field is switched off and on the voltage increases and the solar power is now 4 times higher.)

"New" is that when PV power is available, the battery is also charged with some mains power (despite mode solar only): bug or feature?

MAXII10K_DSP_5607.zip

Edited January 4, 20242 yr by Volker

16 minutes ago, Volker said:

Despite the information to the manufacturer, the 90V problem has not been solved!

I'm shocked! Not.

The hex file is dated 2022-08-29, so it's 5 months later than 56.05, the only other version I've seen, but it's still 16 months old as I type. If they were to fix the stuck at 90V bug, I'd expect the firmware to be only a few months old at most.

Thanks for posting it.

[ Edit: 57.05 -> 56.05 ]

Edited January 4, 20242 yr by Coulomb

Yes, I have seen the date. I received the firmware from my dealer (solarpower24.it) in October 2023.

Ok, I wasn't very active last year (had to take care of bigger private things until now). But I kept pointing out the 90 V problem to my dealer. After I had a second serious error, I received the "new" firmware in October 2023.

The error was that the inverters often (90% !) start with the default parameters after switching on (except when the battery is PYLON). This caused one inverter to break (Explosion ! and parts of the IGBTs went through the fans, a bad sound). After replacing the MOSFETS, an exploded high-voltage capacitor and an SMD resistor, the mainboard is running again. Then I pushed "a little harder" my supplier and received the "new" firmware. Unfortunately, there were no positive changes.

The "forgotten" parameters are also a big problem. It took me 30 minutes to restart and re-parameterise the system. An error here will burn one or more inverters again.

I would like to ask you to repeat the patch for this firmware. Is that possible?

Do you have any ideas about the "forgotten" parameters?

Best regards

17 hours ago, Volker said:

I would like to ask you to repeat the patch for this firmware. Is that possible?

Yes, I'll get to it soon.

17 hours ago, Volker said:

Do you have any ideas about the "forgotten" parameters?

I vaguely recall bad firmware causing EEPROM contents and therefore forgetting of parameters, so that is possibly fixed in this later firmware. I'll try and keep an eye out for changes that could affect EEPROM.

One thing to bear in mind: the EEPROM contents are vital for preventing fault code 90, one of Voltronic's anti-clone measures. Your serial number should be in there, and if it isn't (along with a heap of invisible other data), then the firmware will eventually cause that fault code to come up and the inverter won't work. I can patch around it, saving you the trouble of getting a "setserial" program from your supplier. Each of those programs is totally custom to each inverter.

As a point of interest, does your monitoring software recognise the inverter by its correct serial number? If the serial number comes out as something like 5533... with all 5's and 3's, then it has lost its real serial number, and fault code 90 is on the way. It's easy enough to correct the serial number, but not all the invisible data that goes with it.

I went back to dsp 656.05 to generate any PV yield at all in the winter here.

Just to clarify: Error 90 has not occurred (so far) and all serial numbers are and have always been ok (as I use MultiSIBControl, I can always see the numbers).

The error of the "forgotten parameters" could actually have been caused by the patches. Because before our tests I had switched the system off and on many times and there was no such problem!?

On 2024/01/05 at 1:20 AM, Volker said:

I would like to ask you to repeat the patch for this firmware. Is that possible?

It turns out that patched firmware version 56.05 was one that where I implemented a suggestion for continually checking and resetting the MPPT voltage if needed. I didn't realise this until I was part way through implementing Georg's "standard" patches. So this will be a bit different to x56.05. The MPPT control functions are very similar to that of 90.06, the basis of Georg's original patches, so it was easy to implement the same patches.

I found half a dozen or so differences between 56.05 and 56.07, more than one to do with the solar charger temperature. None had anything to do with saving EEPROM settings or other values. One change had to do with turning the SCRs off when in non-single output mode. The SCRs are used to make the switch to and from bypass mode quicker. There is less code in 56.07 at the end of processing the PBMS command; something to do with maximum discharge current. There is also less code handling solar charge current limiting; fault code 02 is no longer raised in some conditions. If the input voltage range is APL (appliance), the inverter appears to now tolerate much line frequency from 40 to 65 Hz, regardless of the 50/60 Hz frequency setting.

 

These are patched firmwares versions 256.07, 556.07, and 156.07, based on factory firmware version 56.07 for the Axpert Max II 10kW non-twin with the '2809 DSP. Do not use with other models, not even other Axpert MAX models. Your existing main firmware should be 56.xx. The patches implement Georg's patches for the 90.06 firmware: current threshold is reduced from 0.50 A to 0.05 A, the minimum MPPT voltage is changed as below, a pair of control constants is changed, and the boost functions are modified. In addition, the premature float bug is fixed, and the version number reported by monitoring software should be the full 5 digits. The LC Display will continue to show 56.07 (U1 56 07).

Version 256.07 implements a minimum MPPT voltage of 200 V.

Version 556.07 implements a minimum MPPT voltage of 150 V.

Version 156.07 implements a minimum MPPT voltage of 120 V. (100 V is too close to the default 90 V).

As always, the original factory firmware is provided as dsp_original.hex. The old reflash tool has to be used with this processor, and it looks for a fixed hex file name of dsp.hex . As unzipped, dsp.hex is the same as dsp_256.07_patched.hex. To use other minimum MPPT voltages or the original factory firmware, delete dsp.hex, make a copy of the file you want to reflash, and rename that copy to dsp.hex.

Use at your own risk. Firmware update instructions are here.

[ Edit: "f the output mode is not PAR (note: it could be three phase, and several inverters could be paralleled on one phase), the inverter appears to now tolerate..." → "If the input voltage range is APL (appliance), the inverter appears to now tolerate..." ]

 

dsp_x56.07_patched.zip

Edited January 9, 20242 yr by Coulomb

On 2024/01/05 at 12:32 AM, Volker said:

Here is a the DSP firmware for the MAXII10k inverter: Version 56.07.

Compiled at 29/Aug/2022, this one is 4.5 months more recent than 56.05, but it's probably older than 56.09 mentioned in Dec 2023. Here is a little more detail about the differences between the two known versions (56.05 and 56.07).

There is a change in the timer interrupt handler; 56.07 now does a check for non-SNG output mode, battery mode and some other checks, and may send an event to a task that asserts Input/Output expander bit 4. This seems to be important for paralleled inverters.

56.07 has more code checking for over-current and over-temperature of the solar chargers. The current limit can now be set at 80% or 40% of the rated 18 A, depending on conditions. Code to set fault code 02 is removed in 56.07, for MPPT2 only. In 56.05 the handling of MPPT1 and MPPT2 for over-current and over-temperature is a little different; it's more pronounced in 56.07.

If the input voltage range is APL (appliance), the inverter appears to now tolerate much line frequency from 40 to 65 Hz, regardless of the 50/60 Hz frequency setting.

Solar current seems to be limited to 12.8 A in 56.05, but is set to either 14.4 A or 7.2 A in 56.07. The specifications say that the limit is 18 A.

 

 

Edited January 9, 20242 yr by Coulomb

The firmware works well. 👍

Unfortunately, 4 inverters displayed SINGEL after the restart as before. After setting the inverters to 3Px, all parameters were OK again (unlike before). Somehow something has changed here!?

Now to the PV test (winter in north germany, no direct sun!!):

(HYUNDAI SOLAR MODULE HiE-S400VG: Voc = 46.4; Vmpp = 38.6)

1. Test with 5 modules connected in series: 5 * Vmpp = 193 V
a) therefore I chose the 150V version ("PV2 I1", with snow on top): looks good, no more 90V problem after sunrise.
b) a further test with the 120V version showed long interventions of the algorithm with the associated fluctuations in voltage and power

2. With 10 modules in series ("PV I1", the snow on these modules had already been blown away) the voltage and output increased rapidly: no more 90V problem after sunrise.

I will have a look for a few more days and then possibly update all inverters to the 200V version...

On 2024/01/06 at 12:22 PM, Coulomb said:

It turns out that patched firmware version 56.05 was one that where I implemented a suggestion for continually checking and resetting the MPPT voltage if needed. I didn't realise this until I was part way through implementing Georg's "standard" patches. So this will be a bit different to x56.05. The MPPT control functions are very similar to that of 90.06, the basis of Georg's original patches, so it was easy to implement the same patches.

I found half a dozen or so differences between 56.05 and 56.07, more than one to do with the solar charger temperature. None had anything to do with saving EEPROM settings or other values. One change had to do with turning the SCRs off when in non-single output mode. The SCRs are used to make the switch to and from bypass mode quicker. There is less code in 56.07 at the end of processing the PBMS command; something to do with maximum discharge current. There is also less code handling solar charge current limiting; fault code 02 is no longer raised in some conditions. If the input voltage range is APL (appliance), the inverter appears to now tolerate much line frequency from 40 to 65 Hz, regardless of the 50/60 Hz frequency setting.

 

These are patched firmwares versions 256.07, 556.07, and 156.07, based on factory firmware version 56.07 for the Axpert Max II 10kW non-twin with the '2809 DSP. Do not use with other models, not even other Axpert MAX models. Your existing main firmware should be 56.xx. The patches implement Georg's patches for the 90.06 firmware: current threshold is reduced from 0.50 A to 0.05 A, the minimum MPPT voltage is changed as below, a pair of control constants is changed, and the boost functions are modified. In addition, the premature float bug is fixed, and the version number reported by monitoring software should be the full 5 digits. The LC Display will continue to show 56.07 (U1 56 07).

Version 256.07 implements a minimum MPPT voltage of 200 V.

Version 556.07 implements a minimum MPPT voltage of 150 V.

Version 156.07 implements a minimum MPPT voltage of 120 V. (100 V is too close to the default 90 V).

As always, the original factory firmware is provided as dsp_original.hex. The old reflash tool has to be used with this processor, and it looks for a fixed hex file name of dsp.hex . As unzipped, dsp.hex is the same as dsp_256.07_patched.hex. To use other minimum MPPT voltages or the original factory firmware, delete dsp.hex, make a copy of the file you want to reflash, and rename that copy to dsp.hex.

Use at your own risk. Firmware update instructions are here.

[ Edit: "f the output mode is not PAR (note: it could be three phase, and several inverters could be paralleled on one phase), the inverter appears to now tolerate..." → "If the input voltage range is APL (appliance), the inverter appears to now tolerate..." ]

 

dsp_x56.07_patched.zip 1.82 MB · 4 downloads

I also managed to install the new firmware 56.07
  and I chose the 150V version (Reflash dsp_x56.07_patched - 556.07_150V) to see how it behaves compared to the previous Coulomb patched version 56.05 (OG-10 DSP Reflash_656.05 patched) which I have had for more than a year and which perform extraordinarily well compared to the mess of the original firmware that was stuck in 90V forever on a cloudy day !
I will come back with an update after a few days of using the new  firmware!
Thank you Coulomb and Volker 

 

 

Edited January 29, 20242 yr by ClauBebe

Here are graphs for today, a very beautiful and sunny day from morning to evening with the mention that the sun rises at 8:00 AM and sets at 17:36 PM.
Coulomb, which firmware would be the most suitable for me considering that I have two strings of 10 Canadian solar panels 455W with Voc 41.2 (412V / string)

P.S.What does the 150V mean? Is it not the voltage from which the mppt starts or did I understand wrongly?

And is there for the 11 Kw Inverter firmware of 150, 180, 200,280,380 and what would be the difference?

 

Thank you

It's a possibility to create a new firmware with 380V like a 11Kw inverter? 

Edited January 30, 20242 yr by ClauBebe

22 hours ago, ClauBebe said:

which firmware would be the most suitable for me considering that I have two strings of 10 Canadian solar panels 455W with Voc 41.2 (412V / string)

Unfortunately, it's not something I can predict in advance. Since these patches don't truly cure the problem (only Voltronic with the source code and extensive lab equipment can do that), it's a matter of trial and error.

22 hours ago, ClauBebe said:

P.S.What does the 150V mean? Is it not the voltage from which the MPPT starts or did I understand wrongly?

It sets the minimum value for a firmware variable that represents the set point for the MPPT voltage. In this context, set point means the point that the control system is aiming for. So if that value is 150.0, then the MPPT won't ever be aiming for say 140.2 V, even if that is the true Maximum Power Point (MPP) for the present conditions.

Starting is sometimes different to running, but with Voltronic's firmware, they don't seem to do anything special for starting, apart from forcing the MPPT voltage set point low under some conditions, and ironically, this seems to be the crux of the problem. Too often in cloudy conditions, it's acting as though the sun is extremely weak, and it has to drive the panel voltage down to extract enough power from that very weak sun to get everything started. It has no memory of operating at 90% of rated power two minutes ago, for example.

22 hours ago, ClauBebe said:

And is there for the 11 Kw Inverter firmware of 150, 180, 200,280,380 and what would be the difference?

These are "families" of patches, all identical except for the minimum MPPT voltage as mentioned above. With my latest patching "technology" (developed in conjunction with colleague Weber who helped tremendously on the fully patched Axpert MKS and Axpert King firmwares), it's relatively easy to produce these sets of patches. From the way that users have responded, it looks like this is the way I should do all future MPPT patches, at least until some breakthrough comes along that allows for a "one size fits all" patch. As it happens, he has no interest in these MPPT patches, so it's just me for these. And I don't own an inverter with the problem! None of these MPPT patches would have happened without the help of owner @Georg594 (thanks, Georg!)  Of course, he only owns one model, but at least that one has the actual problem. He "translated" his patches to one other model, from memory; I've been extending this to several models' firmwares, because, well, that's what I do 🤓. There aren't many of us that can do this sort of thing, so when I find the time, it seems only right to use this uncommon "superpower" for the common good.

Time has been a bit tight for me just lately; we're having a heat wave here (37-38°C and ~80% humidity, interspersed with thunderstorms) and our air conditioner has packed it in. Before anyone makes a sneaky comment, it's nothing to do with firmware; the motor bearings wore out after 19 years of operation. So it's been a bit of a priority to organise a replacement.

 

Quote

Buy Coulomb a coffee for his hard work !!!

Thanks for the suggestion/sentiment, but of course it will always be completely optional for people to support my efforts.

On 2022/12/22 at 1:45 PM, ClauBebe said:

here is voltaj on MPPT1 and MPPT 2 , on both of them is identic  10 pics of 375W Canadian Solar PV, both strings on south

Do you have a file of version 56.02?  

9 minutes ago, farok98 said:

Do you have a file of version 56.02?  

I think u asked by wrong reply. quote; ask claubeb

 

On 2024/01/31 at 3:39 PM, Coulomb said:

... it's a matter of trial and error....

Unfortunately I was busy with other topics - sorry...

I've just had a proper look at the various data for my system (all inverters are currently patched with dsp_556.07). The MPPT algorithm does not seem to work well at low currents. The voltage remains close to Vmax for a long time (Fig. 1). It does not look like the optimum operating point!
I have of course looked at many older measured values (including older firmware versions) - it never looked really optimal (Fig. 2). But the problem only occurs with little sunlight (rather only indirect light). But then I just need optimum efficiency...
The algorithm seems to me to be in need of improvement. Do you see a possibility for this?

(Unfortunately, I was also unable to solve my problem with the “forgotten” parameters. If you make a mistake when restarting the inverter, there is a loud bang. I've already had to replace all the MOSFETs and an electrolytic capacitor in an inverter - it was a difficult job...)

The implementation of Georg594's Shadow Management in the firmware version dsp_556.07 (Max II 10 kW) should solve the problem. Maybe there is some time for that?