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 I 11kw 100v sticking

Featured Replies

which version should I put now so it doesn't blow up again

 

at 291.70 mppt falls asleep, this is also the update bench. but now there are more issue

Edited by Vector_

  • Replies 74
  • Views 11.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Yes. This is patched firmware version 373.63, based on factory firmware version 73.63 for the Axpert Max E 11 kW non-twin and the '28066 DSP. Do not use with any other model of inverter, or if yo

  • This is patched firmware version 273.63, based on factory firmware version 73.63 for the Axpert Max E 11 kW non-twin with '28066 processor. Do not use with any other model, not even an Axpert Max E 11

  • I have update the firmware to the Coulomb's firmware 273.63, and it looks like is doing much better Thanks @Coulomb    

Posted Images

the inverter was factory with 291.70 and you say that it should be factory with 73.63, which latest version should be the real factory version of the firmware so that I can install it

 

[ Edit: I've posted this in the wrong thread. Rather than attempt to move it, or duplicate it, I'll leave it here. Sigh. ]

This is patched firmware version 491.70 for the Axpert Max E 11 kW non-twin with the '28066 DSP. This is a BUG FIX for patched firmware version 391.70. It is based on factory firmware version 91.70. It should be the same as 291.70 except that it has the missing pair of compares, as mentioned much earlier. Do not use with any other model of inverter.

This firmware is basically for those that are running patched firmware version 391.70, and want exactly the same thing but with the bugs fixed. Most users should try patched firmware versions 273.63 or 373.63, based on the later factory firmware version 73.63, also for the Axpert Max E 11kW non-twin '28066.

Use at your own risk. Please report results, good or bad, and even if you could not get it work etc.

Firmware upload instructions for models with the removable display.

dsp_491.70_patched_200V_fixed.zip

 

Edited by Coulomb

1 hour ago, Vector_ said:

the inverter was factory with 291.70

I assume you mean 91.70.

1 hour ago, Vector_ said:

which latest version should be the real factory version of the firmware so that I can install it

You could install the bug-fixed version of 391.70, called 491.70 above. Or you could use either of patched firmwares versions  273.63 or 373.63; use 373.63 (fixed 200V minimum MPPT voltage) unless you have panels with often less than 200 V, in which case try 273.63. Or you could use factory firmware version 73.63, and put up with the stuck at 90 V problem.

Edit: Actually @Vector_, what is your lowest typical MPPT voltage? 200 V may be too high, and if 291.70 doesn't work for you, then 273.63 is unlikely to work either. I could make a lower voltage version of 373.63 if needed.

Edited by Coulomb

  • 3 weeks later...
On 2023/12/20 at 8:31 AM, Coulomb said:

It seems that x73.63 are still very simple patches; it's still not using the full suite of patches. 373 only has one more patch (5 total) than 273 (4 patches). There is a small chance that adding the full suite will make a difference.

I'll add it to the queue; no promises.

During this past month i try swapping between 373 and 273;I see 373 is little better give me about 100-150 watts more.

Pv imput voltage is from 250 to 320 volt.

Now the sun is not anymore far South (for vinter solstice)...so should produce more power...but dont.

Stay about 2700-2850 watt.Missing 400-600 watt compared to my old Pip 5048Mgx!

I noticed that Mppt controller is like slow to rump up the power...

Can you please find some time to implement other patches?

 

 

 

 

 

 

 

ModScreenshot (207).png

First off, the differences between 73.63 (2023-Jan-11) and 73.06 (2023-Feb-17):

* The MPPT control functions are simplified. For example, the voltage forward constant is not set up and not used.

* 73.63 had a comparison of the PV voltage with the arbitrary constant 250.0; this is removed in 73.06.

These seem to be the only differences, at least that my crude comparisons can find. So 73.06 seems to be more of a "cleaned up", "production" version of 73.63, which has possibly somewhat experimental.

This gives me the confidence to apply the next set of patches to 73.06 rather than 73.63. 

Ah...ok.. 73.06 looks interesting.

Would be very nice if you can implement set  of patches to 73.06.

I saw you post original 73.06,is it safe?  can I try to install it?

 

Thank you very much.

Edited by ans
mistake

Today i got a new Fw from Mpp Solar ,Version 73.78 for Max 11....

tonight i install and tomorrow can test.

Hope this will solve Stucked 90Volt and some power generation issue.

 

13 minutes ago, ans said:

Today i got a new Fw from Mpp Solar ,Version 73.78 for Max 11....

tonight i install and tomorrow can test.

Hope this will solve Stucked 90Volt and some power generation issue.

 

Hi @ans please could you upload, provide a link to this firmware. thank you 

On 2024/02/06 at 4:17 PM, ans said:

Today i got a new Fw from Mpp Solar ,Version 73.78 for Max 11....

tonight i install and tomorrow can test.

Hope this will solve Stucked 90Volt and some power generation issue.

 

mmmmmmmmmm....

I test for 2 days....i dont see any improvements:

 

Screenshot (210).png

Screenshot (211).png

Screenshot (212).png

9 hours ago, ans said:

I test for 2 days....i don't see any improvements:

Well, thanks for the data, @ans. I had a theory for a while that MPPSolar had somehow fixed the "stuck near 90 V" issue with a fork of the main firmware. This was enhanced by noting that 73.78 had some code that few of the other firmwares have. But on examination of that code, it seems that it's only reached when the MPPT is not active. This still might be important, but less so when considered with the fact that the MPPT control code is identical (as far as I can tell) to that of 73.63. For a while,  considered whether perhaps few people had run 73.63 after I made public that 73.06 appears to be a later firmware than  73.63.

So this new data seems to confirm this: MPPSolar don't have any magic sauce, or at least there isn't any that pertain to the "stuck near 90 V" issue in version 73.78.

So then the questions become:

* Is it actually true that the MPPSolar firmwares are an "experimental" fork of the main firmware, perhaps like the 90.xx through 93.xx firmwares?

* If so, is it better to run and patch MPPSolar firmware or main firmware? Perhaps 9x.xx firmware is actually best? Recall that 90.06 is old but still well regarded, but that might be more due to @Georg594's first successful patches being applied to that release. Or is "later" always "better"?

To answer the first question, I think I need to go back and compare the other changes between 73.06 and 73.78 (the latest "main branch" and MPPSolar "fork" versions). I put "main branch" and "fork" in quotation marks because this is still a fairly wild, untested theory of mine. Understandably, I have been focusing so far on the MPPT control parts of the code. That comparison should help answer the second question.

So joy: more work for Coulomb... 🤓

But at least, we are getting closer to the answer I think. Unfortunately, at this stage, the answer seems to be: Voltronic's and MPPSolar's tinkerings don't seem to work, but Georg's patches do seem to work. Sadly with the patches we seem to need a family of patched firmware versions (with different minimum MPPT voltage constants). Maybe one day I or someone else will think of a way to make the firmware somehow aware of how many panels there are, but that seems very tricky at this stage. A new setting would mean patching the display as well as the main firmware, and I'd really like to avoid that if possible. Learning each time the firmware "starts" seems tricky, especially when it can't tell if this is a good or a poor solar day, but it may be doable.

Fortunately, these patches are so far not  too arduous to produce these days. But obviously, I'd rather not do the work and risk making mistakes by patching firmware that isn't the best starting point. So please be patient.

Thanks once again for the data, @ans. It must feel frustrating to find yet another hope for a permanent, official solution dashed. And of course, to Georg594 for kicking off this whole adventure.

ooo I see ..things look more complicated..many thinks to think about...more work

 what I can do is test 73.06.and see how it work....so we can find best Firmware to start on.

I would put a new inverter  setting to set Total Panel Voltage...like this can change Voltage to match every user configuration,

and also use one voltage for winter and others for summer.

and can do more with Homeassistant and 1 light sensor...can send new Voltage setting to inverter accordingly if cloudy or not!

would be nice ..Daily voltage regulation...

 

This evening i will install Fw 73.06 and see how it work,and  i will update info about it.

 

 

 

On 2024/02/09 at 11:55 PM, Coulomb said:

To answer the first question, I think I need to go back and compare the other changes between 73.06 and 73.78 (the latest "main branch" and MPPSolar "fork" versions).

This turns out to be quite tricky, as 73.78 seems to be compiled with a different compiler, or at least with different optimisation settings. 73.78 seems to have faster, more compact code, except for 16-bit compares that are often extended to 32 bit registers and a 32-bit comparison is made. As a result, most 73.78 functions are a little shorter, but some are a bit longer. This makes finding subtle differences nearly impossible.

On top of that, most command handlers have an extra variable set to 20, and this doesn't happen in any of the other firmwares. Weirdly, this change appears to delay updating of the big array of data about all paralleled machines if you are continually sending commands.

However, 73.78 has two additional commands, that query and set the MPPT minimum voltage! It would  therefore be possible to have one firmware image, and users could experiment with various minimum MPPT minimum voltages by sending a command, and not having  to reflash another firmware version!

Hence, thus far, 73.78 appears to be the best firmware to patch for the Axpert Max E 11 kW non-twin models for '28066 processor.

For the curious, the command to change the MPPT minimum voltage is PMPL (Put Maximum Power Low panel voltage), followed by a 3 digit whole number of volts. For example, to set it it 95V, send PMPL095 (leading zero required); for 150 V, PMPL150. The usual two CRC characters and the carriage return should follow. Values below 90 and above 250 will be rejected with a NAK response. QMPL should return for example (095 if the limit is set to 95 V. I have no idea whether this command will be continued, or if it will appear in all new firmwares. It may be just a temporary change to facilitate their testing in the lab.

On 2024/02/13 at 12:21 AM, Coulomb said:

This turns out to be quite tricky, as 73.78 seems to be compiled with a different compiler,

So I've decided to use 73.78, even though it seems to have some debugging code left in, and the new commands actually won't be useful, except for those trying out the factory firmware. If I make it so that the patched firmware listens to the new command, then users will have to use the command to get a new value for the minimum MPPT  value. I'd rather not mandate that, and I suspect that later versions of the firmware won't have these new commands (i.e. my suspicion is that the new commands are for debugging only).

Having started patching that version, I realise I have to decide what current forward constant to use for the various measured PV currents. It turns out that 73.63 and 73.78 both use a forward current constant, when the measured PV current is under 2.00A, of 30, which is quite high: 73.06 uses 13, and @Georg594's patch uses a value of 4 up to 0.35A, and 21 for 0.36 to 2.99 A. I have the option of using a different value for between 0.35 A and 2.99 A. I've settled on 13, the same value as 73.06 would use for < 2.00A, and it's about the middle between 4 and 21. The forward current constant seems to control how fast the MPPT ramps towards higher current, although the way that panels work, this is also the way towards low panel voltage! It seems to me that smooth increases of this constant would be better, and the very low value of 4 that Georg settled on is likely a major factor in his patch's success. In the region from 2.00 to 2.99 A, my proposed value (13) is lower than Georg's (it would be 21 in this region). It will be interesting to see if it works better than other patches.

Rain if forecast for tomorrow,  so I'll hopefully finish the patch then, if air conditioning concerns don't override.

This is patched firmware versions 273.78, 573.78, and 173.78, based on factory firmware version 73.78 for the Axpert Max E 11 kW non-twin running the TMS320F28066 DSP chip. Use only if you know that your processor is a '28066, e.g. if your main firmware from the factory was version 73.xx. If you get this wrong, the upload will refuse to work, but it should not brick your inverter (just restart). The factory hex file is dated 2024-Jan-09.

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 73.78 (U1 73 78). See the post above for how I chose one of the control constants; I can't exactly copy Georg's patches.

Version 273.78 implements a minimum MPPT voltage of 200 V.

Version 573.78 implements a minimum MPPT voltage of 150 V.

Version 173.78 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_73.78_original.inv. When you run the Arena reflash tool, navigate to the folder with the unzipped files, and choose one of the four .inv files (these are hex files). Choose a voltage such that your panels will almost never be below that voltage, even in rainy weather.

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

dsp x73.78_patched.zip

Edited by Coulomb

During this days of full sun I tested Fw 73.06..

100 V bug is still there,but is more reactive to rump up power from panels.In the morning goes up quickly to 2000 watt about 9.45.

This Fw tend to keep Voltage more hight and lower the ampere...this seem working to produce more Watt in the morning and evening..i still get some watt after 18.00 Pm!!

the peak power is same.Also when cloud go away ,immediately panel Watt go up.

May be is worth to give a try to patch 73.06.

As i mention in the previus post ,about a funcion to set Minimum Panel voltage for MPPT...you mention is present now in the new FW 73.78

I post graph to understand.

Later I will install one of your new patched fw.

Thanks for the job.

 

UPDATE: just installed 573.78,all fine.

I try with with Communication tool to send command   QMPL , i get NAKss  response.

 

 

Screenshot (222).png

Screenshot (223).png

Screenshot (224).png

Screenshot (219).png

Edited by ans
update

  • Author

Does anyone had this issue?

The inverter is axpert max 11kw with removable display non twin, and the problem I have is when the inverter is set to SUB it has problem tracking MPP, panel voltage is everywhere going down to 90v and up to 400v and current is kept at max most the time, but when I change to SBU everything is working as it should and charging with max power. The problem became apparent when I added  second string of panels, both strings are matched voltage, and if I disconnect the new string problem is still there. This problem was on firmware 373.63 and I updated to 73.06 but problem remains.

Edited by miki1986

Today I test Version 573.78 MPPT voltage of 150 V.

I notice more watt in the morning and even after 18.00 Pm still give me some watts.

Stack at 100 V for a little in the morning only.

i notice strange behaviour today,when i switch inverter in SUB mode... Mppt start going crazy..Hight Voltage ..low amp..low watt...

after i switch to Line panels start again to produce normal power.

I attach graph.

Tomorrow will test more.

 

Screenshot (228).png

Screenshot (230).png

Screenshot (231).png

On 2024/02/18 at 9:02 PM, miki1986 said:

when the inverter is set to SUB it has problem tracking MPP, panel voltage is everywhere going down to 90v and up to 400v and current is kept at max most the time, but when I change to SBU everything is working as it should and charging with max power... This problem was on firmware 373.63 and I updated to 73.06 but problem remains.

18 hours ago, ans said:

Today I test Version 573.78 MPPT voltage of 150 V...

I notice strange behaviour today, when I switch inverter in SUB mode... Mppt start going crazy.. High Voltage ..low amp.. low watt...

after I switch to Line panels start again to produce normal power.

This is sounding like a problem with factory firmware, presumably present back in 73.63 and hence 373.63, still present in 73.06, presumably also in factory 73.78, and now in 573.78. Always in SUB output source priority; it seems not to show up in SBU output source priority (basically battery mode) or when in line mode.

SUB output source priority is where AC-in is connected to AC-out, and solar power goes to the  DC bus and supports the loads by pushing that solar power from the DC bus to the AC-in / AC-out connection. This is a configuration that my own inverters never go into, so I have no feel for what is going on.

It would be wonderful to be able to solve this, but I think it's beyond my ability. It would be nice to confirm that the patches of the patched firmware for "stuck near 90 V" are not the source of this. @miki1986's post strongly suggests to me  that the patches are not involved, but it would be good to have others confirm or deny this.

18 hours ago, ans said:

I attach graph.

Thanks, it's interesting behaviour. At one point, the system reports zero panel volts. I'm wondering how that can happen; presumably some higher level function has decided to turn off solar assistance (charging and load support) altogether, for a brief period. There are dives to 150 V, but also several to closer to 90 V. The system still has parts that believe that the minimum MPPT voltage is 90 V, but I didn't think that these would affect anything. There is lots to think about.

Before installing 573.78 i never had this problem,I check from my old graph.

In some old graph pictures i post before,can see Voltage and Amp go up and down,but that are the 2 water pumps alternatelly start and stop...one 850Watt other 1150 Watt.. 

and goes on till 17.30.

Today sunny with some clouds passing...i get even 3200 watt from panel..(after cloud passing)

but many strange things happened:

Battery finish charging 13.55 (SBU mode) Pv Input 3200 watt;water  pump 850 watt start...

and there Volts from 267 goes 334V,but Amp drop to 0,5A...watt drop to 198w,so inverter start to take from the battery...

I switch to SUB mode,power start to rump up,but stops and go down again..so i switch  LINE mode,start to rump up,but stops and go down again!!

switch back again to SUB same behaviour ramp Up and go down...only at 15.13 i swich To Line and Power goes to 2100 Watt..

 

All this is very strange never happen with 73.06,73.78,373.63 or 273.73.

I think best think to do is try 273.78 because is same 200V as 373.73.

If the problem not fixed i will install 73.78 and see.

P.S:...mmm i dont remember how many times is possible do do Fw update.

I post today graph Fw 573.78.I made more detail graph.

 

 

 

 

 

Screenshot (234).png

Screenshot (236).png

Screenshot (237).png

Edited by ans
mistake

2 hours ago, miki1986 said:

I want to try factory firmware 73.78 but cant find it, last zip file that @Coulomb posted have file VP5K_original.inv is this it?

Yes,that one is correct.

I tested yesterday and today with full sun...I no get voltage dropping...still stuck 100V in early morning.

Edited by ans
update

On 2024/02/18 at 2:36 AM, ans said:

I try with with Communication tool to send command   QMPL , i get NAKss  response.

Interesting. I can't see why it would not have worked. It won't be useful on the patched versions, though, only on factory firmware version 73.78.

Edit: Sorry for the late response; things have been nuts here.

Edited by Coulomb

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.