On 2023/10/03 at 10:40 AM, Coulomb said:

Gladly!

One thing I noticed (and should have noticed when I perused 69.05) is that this firmware is for the '28066. If you have a '2809, this will not work at all (unless you force it, and then it would brick your machine).

Just thought I'd get that out quickly before I check your existing firmware.

Edit: Ah, yes, it was 88.02, and I don't have any 88.* to check. Hopefully they know what they are doing; just don't mix up and load the wrong firmware from another folder (as is sadly very possible with their new Arena reflash tool). At least, you will see the meaningful file name (as opposed to always being dsp.hex, no matter what's inside). Worst case then, the firmware upload doesn't do anything, but you restart the inverter and nothing is lost.

Hello,

I confirm I have DSP 28066 and this new firmware 69.06 was updated by supplier on my inverter and that now I can select charge current at max 80A, instead of 120A of previous version (88.02).

I have the impression 90V bug has not been solved

Could this be patched, please?

 

Edited October 23, 20232 yr by pongo

On 2023/10/23 at 7:29 PM, pongo said:

I confirm I have DSP 28066 and this new firmware 69.06 was updated by supplier on my inverter and that now I can select charge current at max 80A, instead of 120A of previous version (88.02).

I have no 88.xx firmwares at all. I wonder what it is; it sounds like it's not exactly suitable for the Axpert MAX 7.2 kW. There is patched firmware version 269.61 based on factory firmware version 69.61; it seems to me that this is the correct firmware for Axpert Max 7.2 kW with '28066 DSP.

It looks like 69.06 is actually later than 69.61 by about 6 months. Until I can get around to patching that, 269.61 could be worth trying:

 

Thanks @Coulomb

I'm waiting for original 88.02 from my supplier.

Meanwhile I will try 269.61 (69.61)(Voltronic version numbering is quite confusing).

Is safer to upgrade from USB On-the-GO or PC via RS232?

6 hours ago, pongo said:

Is safer to upgrade from USB On-the-GO or PC via RS232?

I've never successfully done a USB on-the-go flash programming; I always use RS-232.

But to answer your question: I think it's about the same if you know you can trust your USB to RS-232 adapter; if you don't yet know, I guess USB would be fine.

I'm pretty sure that you'd need just the hex file on the USB stick and I'm 99% sure that it has to be named  dsp.hex, even though it might be a blah.inv file originally. So I guess with USB firmware updating, there is the uncertainly about what exactly is in this particular dsp.hex file, unless you just prepared it moments ago.

Edited October 25, 20232 yr by Coulomb

Hello,

I installed version 269.61 yesterday.

Now I can see Voltage differences on morning and afternoon.

Before upgrade (sunny day):

After upgrade (cloudy morning):

 

Thanks

Good day everyone,
I am in contact with George regarding a patch for my MAX.
But I would like to ask here on the forum. In the operating instructions for the AXPERT MAX 7200, it is stated, that the microUSB on the control panel of the inverter, can also be used to update the firmware. Does anyone have personal experience with this route? Has anyone done a firmware update just via USB flash?

Thank you

So today I plucked up the courage and tried to flash my MAX via microUSB. It took 10 minutes, it looked like MAX was processing the update, but in the end, even after a restart, nothing. Next, MAX shows version 45.07
Is it possible that for a hard restart it is not enough to turn off with the button, but it is necessary to disconnect from the battery?
Otherwise I'll have to get a NB with a COM port...

18 minutes ago, Marek_K said:

Next, MAX shows version 45.07

The display will still show only 4 digits; apparently Voltronic didn't get my memo that all firmware versions will be 5 digit from now on 😀

You need to use monitoring software or the QVFW command.

7 minutes ago, Coulomb said:

The display will still show only 4 digits; apparently Voltronic didn't get my memo that all firmware versions will be 5 digit from now on 😀

You need to use monitoring software or the QVFW command.

Show the same in Solar Assistant as in WatchPower...

2 hours ago, Marek_K said:

Next, MAX shows version 45.07
Is it possible that for a hard restart it is not enough to turn off with the button, but it is necessary to disconnect from the battery?

No. When the inverter switches off, all power to the DSP is gone. I can't see that disconnecting the battery would do anything further.

Odd that it appeared to update, yet did not. I assume that you used patched firmware version 245.11?

Even on the display, the two last digits should have changed.

Edited October 31, 20232 yr by Coulomb

4 minutes ago, Coulomb said:

No. When the inverter switches off, all power to the DSP is gone. I can't see that disconnecting the battery would do anything further.

Odd that it appeared to update, yet did not. I assume that you used patched firmware version 245.11?

Even on the display, the two last digits should have changed.

Hi Coulomb, thanks for support.

From the zip file "dsp 245.11 patched Max 7.2kW '2809 120V" i take the file "dsp 245.11 patched.hex", copy it on the USB stick (root), rename as "dsp.hex" and then try update MAX with them.
Unfortunately it doesn't work, or the update will not take place.

Am I making a mistake somewhere in the process?

12 hours ago, Marek_K said:

Am I making a mistake somewhere in the process?

No, that's spot on.

I get the feeling that Voltronic don't test the USB updating very often. Almost like some manager decided this was a great feature, the engineers reluctantly threw something together, then forgot all about it. But that's just my cynical guess.

Though I'm pretty sure others have had success flashing from USB.

Edited November 1, 20232 yr by Coulomb

Thanks George, Coulomb for the support and the new FW to my Max.
I have no idea why the update via microUSB didn't work.
However, a new USB/RS232 cable arrived today and the MAX is already running version 245.11
Once again, I thank both gentlemen for their advice and support.
Let the sun shine for you and the batteries don't get old.
Have a nice day.

@Coulomb or others:

A acquaintance with a Max 7.2 has the problem that if the inverter shuts down, when it boots up again it resets to AGM defaults, with is a big problem with their Dyness Li batteries.

Do you have any idea why this happens and how to solve it?

The 7.2 kW models were the first MAX models to come out. It's possible that they have older main (U1) firmware that neglected to send an event to the supervisor task to save settings after receiving certain commands, although as I type this is seems unlikely.

Even so, can you find out what main (U1) version they are running?

The other possibility is a bad EEPROM chip where the settings are stored, but that's a big can of worms.

On 2023/11/04 at 11:36 AM, Coulomb said:

The 7.2 kW models were the first MAX models to come out. It's possible that they have older main (U1) firmware that neglected to send an event to the supervisor task to save settings after receiving certain commands, although as I type this is seems unlikely.

Even so, can you find out what main (U1) version they are running?

The other possibility is a bad EEPROM chip where the settings are stored, but that's a big can of worms.

They have your 245.11 running.

The inverter was part of a parallel setup, being the slave. (both had your 245.11)

Error 60 suddenly showed on the master, so they disconnected the 2 inverters.

Now they have 6 panels and 5 Dyness B4850 batteries connected to what used to be the slave and have the issue I described above. Also, the bms PYL setting is not working: error 61, while before with the paralleled inverters it did work (bms cable and PYL setting to the other: 'master' inverter)

 

31 minutes ago, birdibird said:

Now they have 6 panels and 5 Dyness B4850 batteries connected to what used to be the slave

Paralleled inverters have to share the same battery; is this the case?

32 minutes ago, birdibird said:

Also, the bms PYL setting is not working: error 61, while before with the paralleled inverters it did work

I believe that in a paralleled inverter setup, the inverter with the cable to the BMS (or to the monitoring software, I guess) has to be set to PYL, but all the others have to be set to USE. Since they are having trouble with the EEPROM and/or settings, I'll bet that's the problem.

@Coulomb
Sorry, I think I wasn't clear.

old situation:

2 Max's paralleled. Both connected electrical to 6 Dyness B4850.

Master inverter with bms cable to batteries on PYL, Slave on USE

Dit worked perfect for a long time, until suddenly F60 appeared.

new situation:

only 1 single Max in use: the one that used to be slave, so did not have the bms cable before

problems:
-Max doesn't remember settings
-bms cable connecion does not work

So you think both these problems can be related to a bad EEPROM?
Could it be related to the F60 showing up before?


 

Edited November 6, 20232 yr by birdibird

11 hours ago, birdibird said:

problems:
-Max doesn't remember settings

It may be that you never paid attention to the slave's individual settings, as most of these get overridden by the master when in parallel. So switching over to the slave on its own may find a lot of changes to settings.

But if you change the settings on the slave (via font panel or monitoring software), they should stick. But if the slave isn't connected to the computer that tries to change the settings, it won't see those changes.

11 hours ago, birdibird said:

-bms cable connection does not work

You need to change the BMS cable over to the slave's BMS port.

11 hours ago, birdibird said:

So you think both these problems can be related to a bad EEPROM?

Maybe, but address the above first.

11 hours ago, birdibird said:

Could it be related to the F60 showing up before?

I don't think so. Perhaps the battery modules have gotten out of balance, and just need some time to balance.

hello, i've got 1 x Axpert Max 7.2 kW with U1 45.13 (sell at 45.06) and U2 12.21.

I've got a big problem that i don't know how to solve; i hope someone can help me.

i set manually the hour and the time but the inverter don't stay with the correct time.

For example if i set 16:00 after 1 hour inverter can say that the time is 16:60, at 17:00 can say that are 17:05. I dont know because use random minutes and it's unstable. I've got this problem with firmware 45.06, hope that update can solve it but nothing.

It's a big problem for me because i need to change at 23:00 my setting of the inverter because i have night fare free from 23:00 to 7:00 and i use for charge my battery. But with the inverter that change time randomly is impossible to me use it manually every day. Thank you

On 2023/11/07 at 10:28 AM, Coulomb said:

It may be that you never paid attention to the slave's individual settings, as most of these get overridden by the master when in parallel. So switching over to the slave on its own may find a lot of changes to settings.

But if you change the settings on the slave (via font panel or monitoring software), they should stick. But if the slave isn't connected to the computer that tries to change the settings, it won't see those changes.

Of course I paid attention. Slave and Master were set exactly the same, except for having the master on PYL and the slave on USER. The system was connected to Solar Assistant, so I could see all of both.

As said above, the 2 inverters are now disconnected. Not in parallel anymore.

The ´old slave' as said does not keep the settings. You change it on the slave itself, and a day or so later when the batteries were empty and the system switches off, after the system is back on the settings are back to default AGM.
I have never experienced this with any other Voltronic inverter.

To cross check, we now connected the 'old master' on its own to this system, and that one is working fine. So, the 'old slave' is faulty.

On 2023/11/07 at 10:28 AM, Coulomb said:

You need to change the BMS cable over to the slave's BMS port.

Of course we did.

After connecting the 'old master' we connected the bms cable to that one and it is working fine.

 

So, the 'old slave' Max 7,2k has these 2 problems that I never have seen before,

Is that solved you think by replacing the motherboard? Or is it something else?

 

13 hours ago, birdibird said:

Is that solved you think by replacing the motherboard? Or is it something else?

The settings are held in a tiny 8-pin Eeprom chip on the control board. You could verify that the problem follows the control board when you temporarily swap control boards. So no, I don't believe that replacing the main board will fix it.

It may be possible to read the old eeprom, perhaps many times comparing the results, and copying the data to a new eeprom chip.

I suppose it's possible that the problem is with a power supply or bypass capacitor. In that case it might be the main board after all, or not. 

9 hours ago, Coulomb said:

The settings are held in a tiny 8-pin Eeprom chip on the control board. You could verify that the problem follows the control board when you temporarily swap control boards. So no, I don't believe that replacing the main board will fix it.

It may be possible to read the old eeprom, perhaps many times comparing the results, and copying the data to a new eeprom chip.

I suppose it's possible that the problem is with a power supply or bypass capacitor. In that case it might be the main board after all, or not. 

Ok, got it.

Is the problem that the bms communication is also not working with this inverter also in the control board?

14 hours ago, birdibird said:

Is the problem that the bms communication is also not working with this inverter also in the control board?

Only a small part of it is; there are also optos that commonly fail or get slow /weak with age, and a small board between the control board and the inverter.

The optos are on the "comms" board and in the display. That "comms" board (very different to the models without a removable display) splits and combines the data stream to the display and Bluetooth / WiFi board. Of course, BMS comms has to get through the whole chain: display, "comms" board, control board. There is also power for the display and "comms" boards; that comes from the main board.

Hello,

finally I received original firmware from my vendor: 88.03.

Differences I can see, comparing with version 69.61:

• Max Charge current
  • 69.91: 80A
  • 88.03: 120A
• Back To Grid, Re-Discharge, Cut-Off (parameters 12, 13, 29) when supported battery connected:
  • 69.61: parameters are i SoC %
  • 88.03: parameters are in V

Could this firmware be patched for 90V bug, please?

Could parameters be changed to use SoC %?

Thanks

MAX_7.2K_88.03.7z