18 hours ago, alex_pescaru said:

Both "stuck at 90V" and "shadow management" mods are implemented in the same function, right?

More or less. Most of the action happens in function MPPTControl (and MPPT2Control in dual MPPT models like the MAXs), though some of the suck at 90 patches are elsewhere (in SetBoost1CtrlSts and similar). All of the shade management is in that one or those two functions.

18 hours ago, alex_pescaru said:

From what I see, the main modification was to reduce the current limit (0.5A -> 0.05A) in order to not drop the MPPT voltage.

Yes. In some of my earlier patches, that's all I did (apart from changing the version number and fixing the premature float bug). But in later patches, I reverted to the full suite of patches. In some patches, I attempted to implement a sort of "restart the MPPT algorithm every X seconds if some conditions are met".

18 hours ago, alex_pescaru said:

And if the MPPT voltage was dropped, this was made slowly, with a constant value, up until a lower limit (different users choices) was reached.

Some control constant are changed, and I don't actually know exactly what the effect of those are. It may be that the MPPT voltage drops more slowly, but I actually don't think so. It's all rather complex.

18 hours ago, alex_pescaru said:

"Shadow management" mod

The current limit was increased (0.5A -> 1.5A), somehow negating the "stuck at 90" mod above.

The current threshold was changed, yes, but when that threshold is crossed, different things happen.

19 hours ago, alex_pescaru said:

The MPPT voltage is dropped all at once now, to a certain value, "restarting" the MPPT, if the current is below the limit for more than 10 minutes.

That sounds right. It seems that the lower voltage is needed to compensate for a part of a panel now being bypassed, and this somehow "activates the diodes". I assume that a new MPPT point is found after this, which the original algorithm would not have found.

19 hours ago, alex_pescaru said:

Can, therefore, consider that the "Shadow management" mod is superseding the "stuck at 90" mod, somehow also doing its job, but from a different angle?

That's not my understanding. I believe that the shadow management is a sort of last resort thing, and if you don't have shading issues, don't use the shading patch. I don't know what happens at low light conditions; I assume that the panels still get pulled down, but to the fixed value (125 V in the one I was reading), which would avoid the stuck at 90 V issue. However, if it somehow does both, that would be very interesting.

Do any users have real-world result to report on this? There are only a few, possibly just two, shade management patches, so unfortunately not many users would be in a position to compare.

Edited Tuesday at 01:183 days by Coulomb

I suppose that many have, on a certain MPPT input, just a single string of panels.

What about the situation when you have two strings of, let's say 5 panels, in parallel?
Something like the configuration below:

And only one (or two panels) from a string is shaded, lets say panel 3 (or 3 and 4), in schematic above ...

Is it possible that the full exposed string to somehow "mask" the problem induced by the shaded panel(s) from the other string?

How will be the MPPT's behavior in this case?

 

Edited November 23, 20232 yr by alex_pescaru

22 hours ago, alex_pescaru said:

What about the situation when you have two strings of, let's say 5 panels, in parallel?

This is not an area of expertise for me.  My understanding is that you often end up with a VI curve that has two or more peaks, and this can fool the simpler MPPT algorithms, like that of Voltronic.

Edited November 24, 20232 yr by Coulomb

Hello. I am little bit lost now in firmwares. I have installed version 90.09 with min. adjusted to 285V. Display version 12.21. I have some shadows in the morning an evening. Total time about 1 hour. Is shadow management version better for me? Today was cloudy weather and PV1 current about 0.5A whole day. PV2 the same. Is there available version with functional led bar?

17 hours ago, biondiba said:

I have some shadows in the morning and evening. Total time about 1 hour. Is shadow management version better for me?

I think you just have to try it and compare results. The shading algorithm replaces the "stuck at 90 V" algorithm, so in the mornings, there will be intervention every 10 minutes until the current reaches 1.5 A. Once the MPPT is past the stuck point, these interventions will cost a little production. So if your shading is minimal, it probably won't be worth it.

Hello, I am using version 272.62 on two inverters for the last 3 years and ist works fine. 😃
I have one EASUN Axpert Max and a Solarpower24 Axpert max both with the same firmware.
Should it be possible to use both devices with 272.62 in 1 phase parallel mode?
Because in my last try one was master and one slave and I got NO failure code.
But when starting the inverters AC output the inverters start, but they dont switch the load, so I get 0V on the output althoug I can hear the AC inverter running (the IEC power cable symbol doesn't appear).
Is there anything I can do?

On 2026/06/22 at 12:22 AM, sudo-st said:

Should it be possible to use both devices with 272.62 in 1 phase parallel mode?

Yes, as far as I know.

On 2026/06/22 at 12:22 AM, sudo-st said:

Because in my last try one was master and one slave and I got NO failure code.

That presumably means that you have paralleling cards installed, and all the wiring is correct.

I also assume that you must have the output mode of both set to PAR (parallel single phase mode).

All I can suggest is that you check the output wiring (no neutral and live swapped, for example). Though I would expect fault codes if the inverter somehow detected that.

You should have breakers on both AC outputs. Do you get AC out if you isolate one of the inverters?

Are both inverters using the same battery?

Yes the parallel cards were pre-assembled as far as I see. I have on both inverters two VGA ports and two current sharing ports for the twisted cable.
I connected the inverters with two VGA extension cable I bought (Inverter distance 2.5m, original cable only 1.8m) but I checked the pinout, the connected wires are the same.
I modified the current-sharing cable to the same length by changing the twisted black and red wires with longer again twisted 0.75mm² wires and connected them also.
And I set the output mode to parallel (PAL) on both inverters.

Both inverters use the same battery bank. The only thing I recognized is that the displayed voltage between both inverters differs by approx. 0.3 V - 0.4 V. Could this be already a problem and I should calibrate the voltage?
The strange thing is I don't get any failure code, but loads are not switched on. So I would assume that some internal condition for parallel operation is not being met.

Every Inverter had its own AC fuse box. I connected both fuse boxes together (but on the current rail before the fuses). Therefore, I can rule out swapped cables.
But I can check if the output starts if I disconnect the connecting cable that links the two AC outputs.

Hello, a small update, also when I disconnect the link between the two AC outputs, the loads don't switch on.
I also checked both inverters with watchpower / ma own read tool on a raspberry pi using the commuication protocol.
I dont see a failure or a warning during parallel mode. All firmwares of CPUs and display are simmilar. QPI is PI30 for both. Only device IDs are different of course.

The only thing I see that in the warning bits Line_Fail is active (because no AC-In connected) and after some times on both devices EEPROM fault bit gets set to 1.