Jump to content

Axpert MAX I 11kw 100v sticking


miki1986

Recommended Posts

Hi, I am new to this forum, I have axpert max 11kw with the removable display,
I have a problem early in the morning and on cloudy days the panel's voltage stay at 90v-100v until the sun shines clear and the voltage goes to normal panel voltag

 

I was wondering if this FW will work on my inverter?

and MPP Solar has an FW update for this model 73.63, my factory firmware is 73.03 and 12.13 for display
 

Voltage.jpg

Link to comment
Share on other sites

6 hours ago, miki1986 said:

I was wondering if this FW will work on my inverter?

Yes, I believe that it will. The firmware that the above patched firmware is based on (92.70) is a bit older than 73.63. It's possible that I'll do a "short form" patch of 73.63, where I only adjust the current thresholds, if time permits.

Link to comment
Share on other sites

If you find time to adjust fw 73.63 that would be great.

Mpp solar "This update is applicable only to “11K MAX” MPP solar inverters to address MPPT freeze issue found on some units due to the chip performance variation."  Is it possible mpp solar fix this freeze issue? Or mine is different problem?

 

Link to comment
Share on other sites

11 hours ago, miki1986 said:

Is it possible mpp solar fix this freeze issue?

I highly doubt it; they are still comparing with 50, which I believe represents 0.50 A, and that seems to be the crux of the problem. Patched firmware compares with 05 now.

11 hours ago, miki1986 said:

Or mine is different problem?

Your problem looks like classic "stuck at 90 V" to me.

Link to comment
Share on other sites

On 2023/07/25 at 12:57 AM, miki1986 said:

If you find time to adjust fw 73.63 that would be great.

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 kW with '2809 processor.

This firmware works around the "stuck at 90 V" problem by changing the current threshold from 0.50 A to 0.05 A. It also fixes the premature float bug, and changes the reported version number to 273.63. The removable display will continue to show version U1 73 63.

Use at your own risk; I cannot test this firmware as I do not own an Axpert Max. It has been "sanity checked" by disassembling the firmware and confirming that the intended changes are present.

Firmware upload instructions.

 

dsp_273.63_patched_05.zip

Edited by Coulomb
Clarified what display will show
Link to comment
Share on other sites

  • 2 weeks later...

Is it possible to edit this firmware to raise the lower limit of pv voltage to 200v?

Because on cloudy day I still have "stuck" at 100 to 150v, it ramps up the amps to 3amp and pv voltage drip to 100-150v and it stays there, when I disconnect and reconnect pv voltage goes up to 320v and amp's  around 2-2.5v and I get double the power, but after some time goes back to 100-150v.

Edited by miki1986
Link to comment
Share on other sites

14 hours ago, miki1986 said:

Is it possible to edit this firmware to raise the lower limit of pv voltage to 200v?

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 you have the '2809 DSP chip; see Chipset Chatter. This is the same as patched firmware version 273.63, except that the minimum MPPT voltage is pegged at 200 V. Note that some users might find that 273.63 works better for them, especially if they have the bare minimum of panels.

Use at your own risk.

Firmware upload instructions.

 

dsp_373.63_patched_05_200V.zip

Link to comment
Share on other sites

  • 3 months later...

Hi all

I just get a new MppSola Max 11  with remuvable LCD Display.

Firmware version:U1=73.07 and U2=12.21.

Have only 1 string:8x470 W in series 43.7 Volt...10,7 Amp

As can see from attach file,panels are stack 100V...this week was cloudy,Never test with sunny day.

But I can remember with previus inverter Pip5048Mgx,start to produce Watts about 7 Am..I using a solar tracker.

see 273.63 or 373.63  that come from new   faactory fw 73.63.

-373.63 have MPPT voltage is pegged at 200 V.   and what voltage is 273.63 Mppt Set?

What firmware should install for my setting?i    try original 73.63 first?

 

This from 11Max;Voltage on top and Amp on bottom (1day only).

Screenshot(192).thumb.png.7883533a2e191aa930290ecb3a704542.png

 

-

This from 5048Mgx...can see start early in morning.

Screenshot(183).thumb.png.94a86de3fbcc03052ef9c3c82eaa81de.png

 

 

Link to comment
Share on other sites

10 hours ago, ans said:

-373.63 have MPPT voltage is pegged at 200 V.   and what voltage is 273.63 Mppt Set?

273.63 was one of my earlier patches, where I was experimenting with just changing the threshold current, not changing anything else. So it still has the minimum MPPT voltage set to 90 V.

Quote

What firmware should install for my setting? Try original 73.63 first?

I would try 373.63 first, though it might be interesting to try the factory firmware (73.63) first to get a feel for the changes. Don't expect the factory firmware to fix the MPPT issue, though one day I have to believe that they will get it right.

Quote

This from 5048Mgx...can see start early in morning.

That's interesting, thanks. My impression has long been that this issue goes way back to the first Axpert MKS II model. I should go compare the code if I get some time.

Edited by Coulomb
Pressed send too early by mistake.
Link to comment
Share on other sites

Hi Coulomb,thanks for reply.

Ok,I ll try  FW: 373.63.

Question:can be the inverter connected to the battery and to external electric company ?(i know load must be 0)

or is better i keep only battery connected or only utility.

 

Another question:

I see from Qpiri command that  Setting max charging time at C.V stage is set to 480 minutes(too much),

(230.0 47.8 230.0 50.0 47.8 11000 11000 48.0 49.0 47.0 54.8 53.8 2 002 060 0 1 2 9 01 0 0 52.0 0 1 480 0 000)

i have to lover Bulk Voltage otherwise battery start peaking...

I my previus 5048 MGX have inverter menu N.32 where can set max charging time at C.V stage ,usually i set 60 minute.

How i can send  PCVT060 command from a windows machine to change  Setting max charging time at C.V stage?

which program?

I attch today Pv Input Voltage,just to compare...today was more sunny.

Screenshot(193).thumb.png.703258ed9150ce66f278f610f127f68a.png

 

 

Link to comment
Share on other sites

14 hours ago, ans said:

can be the inverter connected to the battery and to external electric company ?

I'm pretty sure that it doesn't matter if the utility is connected or not; as soon as the reflash starts, all relays are turned off so the utility input will be ignored.

14 hours ago, ans said:

How i can send  PCVT060 command from a windows machine to change  Setting max charging time at C.V stage?

which program?

I would assume that you would just use monitoring software. But to send the command from Windows, use the Voltronic comms tool; details at the start of this post.

Link to comment
Share on other sites

All worked fine,I set parameter PCVT060 .i update to  FW: 373.63,

I try MY CONVERTER Prolific PL2303GTbut cant connect even to watchpower,

before connection with 5048MGX inverter was fine.I try with another laptop,but same no connection,,,,I borrow a FTDI converter and all fine.

Please stick this info somewhere.

 

 

Today was cloudy cover with little rain and Pv Voltage was stuck 100V till 15.17when I updated Fw,then Pv input jump to 300V.

Hope tomorrow is sunny,to make a nice test.

I attach graph. for real understanding.

Screenshot(198).thumb.png.882b3c7aa2e0801b967659d8a6bdfd38.png

 

Thanks to Coulomb for his great job.

Link to comment
Share on other sites

  • 3 weeks later...

During this past 20 days,i try FW: 373.63 and FW: 273.63,

but I notice PV1 Solar Panel input stay about 2600-2800 watt,even with full sunny days.

This is very strange,because before with Pip 5048MGX i was normally gettin Pv imput about 3000-3400.

Panel are clean,and I am using a solar tracker.

Any suggestion?

 

Link to comment
Share on other sites

On 2023/12/19 at 2:41 AM, ans said:

During this past 20 days,i try FW: 373.63 and FW: 273.63,

Any suggestion?

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.

Link to comment
Share on other sites

5 hours ago, 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.

I got same problem with 5048 MGX,and this get fixed by Pip 5048 Mgx 71.10 Firmware sent my by Pip.

I attach you this file on 23/09/21 on the other forum in private message...you should have in your Goo  gle drive.

i was thinking if you can check what is the modify they made,compared to previus Fw....that is the difference.

Thanks for all your  help.

Link to comment
Share on other sites

3 hours ago, ans said:

I got same problem with 5048 MGX,and this get fixed by Pip 5048 Mgx 71.10 Firmware sent [ to me ] by [MPPSolar].

I had a quick look at 71.10, and did not find anything special about it in the areas I expected (where the MPPT power is controlled). But maybe there are more changes elsewhere; it will take me some time to compare the rest of the code.

Link to comment
Share on other sites

  • 4 weeks later...
14 hours ago, Vector_ said:

at MAX 11 kw  with U1: 291.70 which option is best to go up?

The good news: you can update to patched firmware version 373.63.

The bad news: There is factory firmware version 73.06 available that is slightly (1 month) later than 73.63. So I might get around to patching that one day.

Also bad: 373.63 doesn't have the complete set of patches; 291.70 has slightly more patches. I have no idea how significant those extra patches are, sorry.

Also good to know: If you have a small number of panels, like 4S or 5S such that you don't reliably get to 200 V with some level of clouding, you could also update to patched firmware version 273.63, which does not have the minimum MPPT voltage change, only the current threshold change.

Link to comment
Share on other sites

hello Coulomb. as I already wrote the inverter was initially with e U1: 291.70 I updated it with 391.70 then it works only on battery and panels. When the AC is turned on, an error 32 appears, which is strange. after a short work like this, about 2 min. the inverter exploded and almost all the transistors were damaged. the damaged elements have already been replaced, the inverter works again but error 32 is displayed when AC is present. My question is now should I get my 291.70 back or ???

Link to comment
Share on other sites

22 hours ago, stakoz said:

is there a link somewhere for download of the 73.06 firmware as I don't find it on the forum.

Neither did I. In fact, I could not find an original zip/7z/rar file for this firmware. I may have obtained it via some back channel, so I created a zip file with just three files in it below.

This is factory firmware version 73.06 for the Axpert Max E 11 kW non-twin with '28066 processor. Do not use for any other model; use at your own risk. The hex (.inv) file is dated 2023/02/17, so this is slighty more recent than version 73.63 (2023/01/11).

MAX11K_DSP_73.06_28066 Non-twin.zip

Let me know if there are any problems. Upload instructions.

 

Link to comment
Share on other sites

23 hours ago, Vector_ said:

My question is now should I get my 291.70 back or ???

Arrgh! I found a fault in patched firmware version 391.70. Sigh. I hope it wasn't the cause of your explosion, but it might have been, or at least contributed to it. It likely caused one of the task's stacks to overflow, with unknown consequences. I'm surprised it ran at all.

You should hold off until I generate a fixed patched firmware, likely 491.70.

So sorry for the problems. As I say in the edit, unfortunately something like this can happen since I generate so many patches. One lapse of concentration and something like this can happen. Hopefully, I do far more good than harm in aggregate.

Link to comment
Share on other sites

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...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...