2 hours ago, Coulomb said:

De fapt, acest lucru nu este adevărat. Puntea plină poate arunca puțină energie înapoi în sursa de intrare AC pentru a reduce tensiunea magistralei, dacă, desigur, este prezentă o sursă de intrare AC.

Până acum: versiunea de firmware 90.06 (pentru un 8kW Max) limitează curentul de încărcare la 80A dacă tensiunea PV este > 360V și AC-in nu este prezentă și nu limitează altfel (pe baza tensiunii PV; există mai multe alte tipuri de derating).

Firmware 78.08 (pentru 11kW Max, 24 iunie 2024): dacă tensiunea fotovoltaică depășește 360V: curentul de încărcare este limitat la 100A dacă este prezentă intrarea AC și la 90A dacă nu este prezentă intrarea CA. De asemenea, limitează curentul de încărcare la 100 A dacă tensiunea de intrare AC este mai mare de 250 VAC, probabil pentru că umflarea de energie la aceasta ar face ca tensiunea să fie foarte mare. Acum că pot urmări această parte a codului firmware-ului, pot verifica mai multe firmware-uri pentru a vedea ce fac. 90,06 este din 2022; Îl folosesc pentru că este cel mai bine comentat dezasamblarea firmware-ului Max.

Firmware 63.04 (pentru Max E 11kW non-Twin, 2023): La fel ca pentru 78.08.

Firmware 46.82 (pentru Max E 8kW non-Twin, 2023): La fel ca pentru 90.06 (ambele sunt firmware de 8kW).

Firmware 72.08 (pentru Max E 8kW non-Twin, 23 octombrie 2024, cel mai recent pe care îl am): La fel ca și pentru 90.06.

Firmware 81.08 (pentru 8kW Max II non-Twin 23 octombrie 2024, cel mai recent pe care îl am): La fel ca și pentru 78.08.

Deci, se pare că firmware-urile de 8 kW pentru modelele E nu limitează deloc curentul maxim de încărcare dacă tensiunea PV este > 360 V și este prezentă intrarea AC. Cu toate acestea, singurul model Max II la care m-am uitat face! Și două firmware-uri cu fișiere hexadecimale datate în aceeași zi au algoritmi diferiți.

Va trebui să mă uit puțin mai departe.

I use it offfrid, dont have Ac In, pv voltage all the time >360v, do.u think i can try the disabled derating option ? I can burn Something? Inverter...ot battery...?

19 hours ago, add1c7ed55 said:

I use it off-grid, don't have Ac In, PV voltage all the time >360v, do u think I can try the disabled derating option ?

That's a tough question. All the 11 kW firmwares seem to have this limit. Many of the latest Max firmwares for other models have it, though it becomes less common with the lower powered models (e.g. the latest 7.2 kW firmware that I have does not have this limit).

I just don't know enough about how these models regulate the bus voltage to be able to say. It's safer to keep the limit, obviously, even though in your situation it means that you can't charge your very large battery very quickly.

@Coulomb Hi Coulomb, I'm new to the forum and I think you're one of the wisest.

I have a problem with my 2 inverters connected in parallel.

They are the SMW 11KW 48V Easun/POWLAND model, these in short https://amzn.to/4cUGdMH

Early in the morning they stop at 90V, I think they suffer from what I read here ("90V bug").

If I disconnect and reconnect the differentials in the string boxes, the voltage rises to 270V for each of the 4 strings I have.

The firmware for both inverters are U1 64.09 and U2 38.14.

With what update or setting can the problem be solved?

Thank you very much

Edited April 28, 20251 yr by cjb

Assuming that it's an EASun (legal rebrand of Voltronic) and not Powland (work-alike with different firmware), you should be able to run patched firmware versions x64.62.

Thanks for the reply. If it doesn't work as I hope, can I go back to the original? I mean, is there a way to extract the original firmware before proceeding? I must use dsp_x64.62_patched_200V_150V_90V.zip ?

Edited April 28, 20251 yr by cjb

9 minutes ago, cjb said:

can I go back to the original?

Yes. Each of my patched firmware sets has the original factory firmware from which it is derived, in this case 64.62. Or you can go back to 64.09 that your inverter came with here.

11 minutes ago, cjb said:

is there a way to extract the original firmware before proceeding?

No. That requires special equipment and a 128-bit "password" that only Voltronic knows.

12 minutes ago, cjb said:

I must use dsp_x64.62_patched_200V_150V_90V.zip ?

Yes; you have to choose one of the three patched firmware versions, based on the voltage that your PV string rarely goes below even in poor light. Or you could try all three to see which one seems to work best for you. But unless your PV string is very low voltage (few panels in series), either the 150 or 200 volt variants will likely be best.

Thank you so much

they are sold by Powland but on the inverters there is the Easun logo. I have 4 strings of 6 panels (Longi 535wp) for a total of 24 panels (12 to the EAST and 12 to the WEST). Each string should give 270V, so I guess I will choose the 200V version. I rename the file to dsp.hex and launch ReflashTool_Xseries.exe via COM1 ? Just this? can i flash only the primary one or do i have to flash the secondary one of the screen as well?

Edited April 28, 20251 yr by cjb

Thanks Kuba.cz
Just a quick feedback: my inverter still works perfectly with the removed derate firmware. :)


For just analysis purpose today i made 3 get status within 10 minutes in the mid of the day when PVs provides almost maximum (113A).

• 1st status is with Battery charge current was limited to 10A.

• 2nd Battery charge current was limited to 100A.

• 3rd when Battery charge current was limited to 150A.

10A

mppsolar --getstatus -P pi30max

Command: QPIGS2 - General Status Parameters inquiry 2

--------------------------------------------------------------------------------

Parameter Value Unit

ac_input_voltage 235.5 V {'icon': 'mdi:transmission-tower-export', 'device-class': 'voltage'}

ac_input_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'}

ac_output_voltage 228.6 V {'icon': 'mdi:power-plug', 'device-class': 'voltage'}

ac_output_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'}

ac_output_apparent_power 645 VA {'icon': 'mdi:power-plug', 'device-class': 'apparent_power'}

ac_output_active_power 525 W {'icon': 'mdi:power-plug', 'device-class': 'power', 'state_class': 'measurement'}

ac_output_load 6 % {'icon': 'mdi:brightness-percent'}

bus_voltage 465 V {'icon': 'mdi:details', 'device-class': 'voltage'}

battery_voltage 52.8 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'}

battery_charging_current 10 A {'icon': 'mdi:current-dc', 'device-class': 'current'}

battery_capacity 56 % {'device-class': 'battery'}

inverter_heat_sink_temperature 44 °C {'icon': 'mdi:details', 'device-class': 'temperature'}

pv1_input_current 0.8 A {'icon': 'mdi:solar-power', 'device-class': 'current'}

pv1_input_voltage 358.9 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'}

battery_voltage_from_scc 0.0 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'}

battery_discharge_current 0 A {'icon': 'mdi:battery-negative', 'device-class': 'current'}

is_sbu_priority_version_added 0 bool

is_configuration_changed 0 bool

is_scc_firmware_updated 0 bool

is_load_on 1 bool

is_battery_voltage_to_steady_while_charging 0 bool

is_charging_on 1 bool

is_scc_charging_on 1 bool

is_ac_charging_on 0 bool

battery_voltage_offset_for_fans_on 0 10mV

eeprom_version 0

pv1_charging_power 306 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

is_charging_to_float 0 bool

is_switched_on 1 bool

is_dustproof_installed 0 bool

solar_feed_to_grid Disabled

country Invalid key: 3030

solar_feed_to_grid_power 0 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

pv2_input_current 2.1 A {'icon': 'mdi:solar-power', 'device-class': 'current'}

pv2_input_voltage 434.8 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'}

pv2_charging_power 935 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

--------------------------------------------------------------------------------

100A

mppsolar --getstatus -P pi30max

Command: QPIGS2 - General Status Parameters inquiry 2

--------------------------------------------------------------------------------

Parameter Value Unit

ac_input_voltage 236.9 V {'icon': 'mdi:transmission-tower-export', 'device-class': 'voltage'}

ac_input_frequency 49.9 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'}

ac_output_voltage 229.9 V {'icon': 'mdi:power-plug', 'device-class': 'voltage'}

ac_output_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'}

ac_output_apparent_power 666 VA {'icon': 'mdi:power-plug', 'device-class': 'apparent_power'}

ac_output_active_power 523 W {'icon': 'mdi:power-plug', 'device-class': 'power', 'state_class': 'measurement'}

ac_output_load 6 % {'icon': 'mdi:brightness-percent'}

bus_voltage 442 V {'icon': 'mdi:details', 'device-class': 'voltage'}

battery_voltage 53.6 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'}

battery_charging_current 100 A {'icon': 'mdi:current-dc', 'device-class': 'current'}

battery_capacity 64 % {'device-class': 'battery'}

inverter_heat_sink_temperature 57 °C {'icon': 'mdi:details', 'device-class': 'temperature'}

pv1_input_current 8.1 A {'icon': 'mdi:solar-power', 'device-class': 'current'}

pv1_input_voltage 323.9 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'}

battery_voltage_from_scc 0.0 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'}

battery_discharge_current 0 A {'icon': 'mdi:battery-negative', 'device-class': 'current'}

is_sbu_priority_version_added 0 bool

is_configuration_changed 0 bool

is_scc_firmware_updated 0 bool

is_load_on 1 bool

is_battery_voltage_to_steady_while_charging 0 bool

is_charging_on 1 bool

is_scc_charging_on 1 bool

is_ac_charging_on 0 bool

battery_voltage_offset_for_fans_on 0 10mV

eeprom_version 0

pv1_charging_power 2648 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

is_charging_to_float 0 bool

is_switched_on 1 bool

is_dustproof_installed 0 bool

solar_feed_to_grid Disabled

country Invalid key: 3030

solar_feed_to_grid_power 0 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

pv2_input_current 8.2 A {'icon': 'mdi:solar-power', 'device-class': 'current'}

pv2_input_voltage 393.5 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'}

pv2_charging_power 3255 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

--------------------------------------------------------------------------------

150A

mppsolar --getstatus -P pi30max

Command: QPIGS2 - General Status Parameters inquiry 2

--------------------------------------------------------------------------------

Parameter Value Unit

ac_input_voltage 235.8 V {'icon': 'mdi:transmission-tower-export', 'device-class': 'voltage'}

ac_input_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'}

ac_output_voltage 229.6 V {'icon': 'mdi:power-plug', 'device-class': 'voltage'}

ac_output_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'}

ac_output_apparent_power 574 VA {'icon': 'mdi:power-plug', 'device-class': 'apparent_power'}

ac_output_active_power 266 W {'icon': 'mdi:power-plug', 'device-class': 'power', 'state_class': 'measurement'}

ac_output_load 5 % {'icon': 'mdi:brightness-percent'}

bus_voltage 422 V {'icon': 'mdi:details', 'device-class': 'voltage'}

battery_voltage 53.8 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'}

battery_charging_current 113 A {'icon': 'mdi:current-dc', 'device-class': 'current'}

battery_capacity 66 % {'device-class': 'battery'}

inverter_heat_sink_temperature 70 °C {'icon': 'mdi:details', 'device-class': 'temperature'}

pv1_input_current 9.2 A {'icon': 'mdi:solar-power', 'device-class': 'current'}

pv1_input_voltage 304.4 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'}

battery_voltage_from_scc 0.0 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'}

battery_discharge_current 0 A {'icon': 'mdi:battery-negative', 'device-class': 'current'}

is_sbu_priority_version_added 0 bool

is_configuration_changed 0 bool

is_scc_firmware_updated 0 bool

is_load_on 1 bool

is_battery_voltage_to_steady_while_charging 0 bool

is_charging_on 1 bool

is_scc_charging_on 1 bool

is_ac_charging_on 0 bool

battery_voltage_offset_for_fans_on 0 10mV

eeprom_version 0

pv1_charging_power 2814 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

is_charging_to_float 0 bool

is_switched_on 1 bool

is_dustproof_installed 0 bool

solar_feed_to_grid Disabled

country Invalid key: 3030

solar_feed_to_grid_power 0 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

pv2_input_current 9.4 A {'icon': 'mdi:solar-power', 'device-class': 'current'}

pv2_input_voltage 370.4 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'}

pv2_charging_power 3514 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'}

--------------------------------------------------------------------------------

The bus voltage is highest in the lowest load of course.

5 hours ago, robert1968 said:

Just a quick feedback: my inverter still works perfectly with the removed derate firmware. :)

Great news ! Looking at the status output, your Vmpp on PV2 seems to be only 10V above the original derate limit. That should be safe.

Good morning, forgive me again but I am new to both the forum and photovoltaics. Before flashing the firmware as requested by @Coulomb , this morning at 7:00 I noticed a strange thing: even though they both had the same firmware (U1 64.09 and U2 38.14) the first inverter to the east had the usual bug at 90V while the second to the west marked 230V. I repeat, same strings for both and same firmware. How is this possible?

On 2025/04/28 at 10:14 PM, cjb said:

Each string should give 270V, so I guess I will choose the 200V version.

In poor light, you may find that the Maximum Power Point is under 200 V, so perhaps the 150 V version would work better in cloudy conditions.

On 2025/04/28 at 10:14 PM, cjb said:

I rename the file to dsp.hex and launch ReflashTool_Xseries.exe via COM1 ? Just this?

Your USB to serial adapter may not be on COM1, it might be COM5 for example. If you have a compatible USB to serial adapter and the right cables, then yes, that's all you do. The reflash should take about 10 minutes.

On 2025/04/28 at 10:14 PM, cjb said:

can i flash only the primary one or do i have to flash the secondary one of the screen as well?

There is no need to update the display (secondary) firmware in this case. The PV control is all handled by the main DSP firmware.

Edited April 30, 20251 yr by Coulomb

thanks again. I'm scared to death! They are 2 inverters in parallel and I really don't want to buy them again.

Why do you think this happens?

"this morning at 7:00 I noticed a strange thing: even though they both had the same firmware (U1 64.09 and U2 38.14) the first inverter to the east had the usual bug at 90V while the second to the west marked 230V. I repeat, same strings for both and same firmware. How is this possible? "

Edited April 29, 20251 yr by cjb

22 hours ago, cjb said:

even though they both had the same firmware (U1 64.09 and U2 38.14) the first inverter to the east had the usual bug at 90V while the second to the west marked 230V.

It could be that the available PV power was such that one just barely passed the current threshold, and the other just barely did not. The factory firmwares all set the current threshold too high (0.5 A); patched firmware reduces that to 0.05 (earlier patches) or 0.1 A (later patches) to help with this situation.

top thank you!

Edited April 30, 20251 yr by cjb

Hi @Coulomb , I bought a third inverter with the same firmware as the two that are in parallel. I did it to have a safety backup. Maybe I'll test the update first on this one and then on the other 2. To proceed, is it enough to power the inverter with AC or do I also have to connect the panels and battery? Thanks

Hi @Coulomb in addition to what I wrote to you, I have news that could be useful to the community. Easun support to whom I had asked the 90V problem about a month ago before doing it in this forum, sent me a firmware 64.62. Do you want to analyze it for all of us? Thank you very much

MAX 11K TWIN 64.62.rar

Edited May 14, 20251 yr by cjb

23 hours ago, cjb said:

To proceed, is it enough to power the inverter with AC or do I also have to connect the panels and battery?

Just the battery. Depending on the model, it may run with just the AC-in, but I would not trust it.

3 hours ago, cjb said:

Easun support to whom I had asked the 90V problem about a month ago before doing it in this forum, sent me a firmware 64.62. Do you want to analyse it for all of us?

It's nearly 2 year old firmware, but it is the latest in that series that has the "presumed good" MPPT logic. The latest is 64.09, 10 months old, and doesn't have that logic. But it might have fixed the stuck at 90 V issue elsewhere in the firmware.

Edited May 15, 20251 yr by Coulomb
Added "in the firmware" at the end.

so it's not very useful for you to have it?

13 hours ago, cjb said:

so it's not very useful for you to have it?

Sorry, I should have been clearer. That firmware (version 64.62) has been in my collection for a long time. I've even made patched firmware versions x64.62 based on it.

My conclusion is that it's nothing special, apart from being the most recent (least ancient?) firmware with the "presumed good" MPPT logic, which seems almost as good as patched firmware for mitigating the "stuck at 90V" issue.

ok perfect. I'm not very experienced and I'm new to the group. What does the patched one solve besides the 90V problem? plus I would really like to learn how to do it? What software do you use for patches?

Edited May 15, 20251 yr by cjb

10 minutes ago, cjb said:

What does the patched one solve besides the 90V problem?

I usually fix the premature float problem, as it's a single byte fix (after you've found the right place to patch). But when I patch a firmware that has the "presumed good" MPPT logic, it's a combination of not having recognised the presumed good logic as such, and also reducing a current threshold that seems to make patched firmware perform a bit better than the presumed good logic. This threshold is the PV current beyond which the firmware no longer tries to drive the PV voltage ever lower, which is presumably needed to get things started, especially considering the presence of a fixed power drain needed to power the control logic from available PV power.

Other patches in the past have been to add features like KettleKomp™ (load/charge compensation), Dynamic Charge Control so users can send commands to alter the maximum charge rate on the fly, enhance data displays, even "font" improvements, but these are a lot of work, and I don't have access to the more recent models to test them out. So the MPPT patches that I do are all "blind", in the sense that I mimic what user Georg594 did (he did own an Axpert Max0 and adapted those changes to other models.

14 minutes ago, cjb said:

plus I would really like to learn how to do it? What software do you use for patches?

Heh. A handful of people have expressed this wish to learn patching, but few have been able. It seems to take a certain kind of personality (madness?) to pore over countless pages of assembly language instructions, figuring out the meaning of thousands of variables (global and stack temporaries), and learning the peculiarities of a Digital Signals Processor whose instruction set was never designed for humans to understand (save a very few engineers that write the very low level code).

To patch a firmware, first you have to understand the part of the firmware that is relevant, at least to a reasonable degree. I can't pretend to understand all the ins and outs of even the MPPT logic, for example. But you need to know it pretty well, and for that you need a good reverse engineering tool, and have the required mindset to be able to use it effectively. I use the Ida Pro disassembler, which is expensive, but few other tools come close to it. I started poking at early firmwares, and am able to transfer the ideas more or less well to later firmwares.

Then there is the process of patching itself. A colleague of mine (Weber on the forums) and I started by painfully editing the hex files by hand, and maintaining a text file recording what we'd done, with before and after lines of hex, so we could debug it if necessary and perhaps adapt one patch to another firmware or another patch requirement. We performed our first few "fully patched" firmwares that way, with dozens of individual patches and occasional new pieces of assembly language code, and occasionally used a JTAG interface to single step through modified code when a particular condition was detected. This has to be done carefully, as single stepping a DSP can lead to inductors saturating and other unpleasant outcomes. The only "automation" we had then was a spreadsheet that would calculate the checksum for a line of hex code. Every hex file has a checksum at the end of every line to make sure that communication errors don't end up corrupting a flash image during the reflash process. Oh, and a set of macros to allow for more or less structured programming when using assembly language.

Towards the end of that collaboration, we ended up developing a set of Python scripts to make life much easier. These take care of many of the details, like automatically calculating checksums, merging hex files, and the like. So now for most patches, I just modify an assembly language source file that is typically one or two pages in length, including about 50% comments, and "compile" (it's only assembling) them with a product from Texas Instruments called Code Composer Studio. This latter is free under certain conditions like assembly language only projects, and has the ability to add "steps" to the "compile" which call the python scripts. The result is a new hex file, which I can disassemble with Ida Pro to ensure that the changes are made as intended. This last step is made easier by Ida's ability to save most of the annotations made when reverse engineering to a large script file, which can then be loaded into the disassembly of the new hex file, so it's possible to quickly jump to the parts of the code where the changes should be. After that, it's a matter of zipping up the appropriate files and uploading them, usually to this forum but sometimes to the Australian Electric Vehicle Association where I'm also active.

If I haven't turned you off the idea already, and you know what the result of xoring (performing an exclusive OR function) on the same value is, know what the stack is an how it's used, and have at least a passing knowledge of things like timers and Pulse Width Modulation modules are, then PM me and we can chat further. I don't make all my secrets available to all so as not to enable clone makers to profit from Voltronic's intellectual property.

what can I say you are great! I like these things but from your description I think the path for me will be long. I built my system and now I came across this forum because of the problem with the 90V. You are really prepared and kind and I take advantage of you because I am afraid of bricking my inverters and losing a lot of money. Thanks again for your availability

@Coulomb Hi, I mounted on a gable roof with east and west exposure 4 strings of photovoltaic panels connected two by two on two hybrid inverters connected in parallel communicating with each other. From this parallel I get the 230V single phase. Each string is 3 kwp. The slope is 30 degrees and it is the month of June. Without any load connected to the system, at the end of the sunny day one inverter marks a production of 5kWh and the other 7kWh. Is this normal? Thk

6 minutes ago, cjb said:

@Coulomb Hi, I mounted on a gable roof with east and west exposure 4 strings of photovoltaic panels connected two by two on two hybrid inverters connected in parallel communicating with each other. From this parallel I get the 230V single phase. Each string is 3 kwp. The slope is 30 degrees and it is the month of June. Without any load connected to the system, at the end of the sunny day one inverter marks a production of 5kWh and the other 7kWh. Is this normal? Thk

Hi CJB, welcome to the forum. Sorry to jump in but this topic is specific to an Inverter model being limited at 100amps when charging batteries. I note your queries are a bit different and there are other topics on stuck at 90v etc in this forum. Some of us are subscribed to specific topics, like myself on this one (as I have this specific issues of being limited at 100amps batteries charging) and again from the recent posts it is going offtopic and I receive email notifications for each post. But when I open the topic thread it diverts to other subjects. Would appreciate if you could please stay on the specific topic or look for specific topic threads related to your specific issues. Thank you in advance.

thank you

Edited June 19, 20251 yr by cjb