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 MKS II firmware upgrade

Featured Replies

3 minutes ago, Tubby said:

Do I understand correct if I say those two units can be paralleled without changing firmware?

I don't know for certain about 71.70, but 71.71 for Axpert MKS II uses the same paralleling constant (118) as 71.80 for Axpert MKS II.

In other words, it should work just fine. There is a small chance that they won't parallel correctly, but if so, you'll notice weird behaviour like one machine changing between SL (for SLave) and NE (for NEw). You can discover this before you connect the outputs together (using your AC-out breaker/isolators that you should have installed), so the chances of anything bad happening are extremely low.

Usually I would recommend updating the older machine to the newer firmware, and the firmware update file is available in this case, but since you're not confident of re-flashing, just go ahead and try it (with outputs not paralleled initially, of course).

Thanks Coulomb for your input. I will do so as soon as I have every thing ready for installing my 2nd inverter. If it does not work out, I will ask for some assistance.

  • Author
On 2020/07/20 at 2:53 PM, Coulomb said:

I don't know for certain about 71.70, but 71.71 for Axpert MKS II uses the same paralleling constant (118) as 71.80 for Axpert MKS II.

In other words, it should work just fine. There is a small chance that they won't parallel correctly, but if so, you'll notice weird behaviour like one machine changing between SL (for SLave) and NE (for NEw). You can discover this before you connect the outputs together (using your AC-out breaker/isolators that you should have installed), so the chances of anything bad happening are extremely low.

Usually I would recommend updating the older machine to the newer firmware, and the firmware update file is available in this case, but since you're not confident of re-flashing, just go ahead and try it (with outputs not paralleled initially, of course).

I'm running 2 units in parallel which have 71.50 firmware and everything works perfectly

  • 3 weeks later...

Thanks Riff-Raf, I have paralleled the 71.70 and 71.80 and it seems to be running fine. Only problem I now see, is ICC not reading any PV watts.

On 2020/07/20 at 1:24 PM, Riff-Raf said:

After my initial upgrade issue and Mustek generously replacing the control board under warranty, I frankly don't have the guts to do any upgrades. Also changed to Lithium batteries, so the inverter works perfectly with the original firmware.

Would be good to know if there is a new firmware though.

After reading this post, I have decided to leave my inverter firmware alone. No idea what version it is on as I am only installing it next week. Its the Kodak variant of the MKsII and I figured whatever is on there, shall stay as is. 

 

Glad you came right in the end though!

  • Author
On 2020/08/07 at 3:00 PM, Tubby said:

Thanks Riff-Raf, I have paralleled the 71.70 and 71.80 and it seems to be running fine. Only problem I now see, is ICC not reading any PV watts.

You are braver than me... I would think that the units need to have the same firmware version when using in parallel. As some of the settings carry through to both units when paralleled, irrespective which unit the setting is applied, it would be logical to have both units' firmware the same. There may be some reporting protocol difference between firmware versions, hence your PV data reporting issue.

Unfortunately, I'm no Axpert at the data protocol level 😏

I checked the two outputs separately before joining them together as Coulomb suggested and it looked like it would parallel.

At this time I only have PV connected to one inverter, the 71.80 which is the master. This morning I made 71.70 the master and now it reads PV. If I had the guts to flash my firmware, I would most definitely make both inverters the same. Problem is, I have no idea where to start or what to do. I tried contacting Mustek to see if they are willing to help, but I just can't get hold of anybody other than the switchboard.

I just upgraded my MKS II (yes the 450V MPPT) to 71.82.  I wouldn't upgrade unless you have an issue.  If you do have an issue, the supplier/installer should give you the latest firmware and provide support if something goes wrong.  In my case my installer came to my house and did the upgrade with me.  It's not that it's hard to do, but if something goes wrong it should be fixed as part of warranty.  That is just my opinion and perhaps not industry tendency.

 

  • 5 months later...
On 11/8/2020 at 22:05, Denarius said:

Acabo de actualizar mi MKS II (sí, el MPPT de 450V) a 71.82. No actualizaría a menos que tengas un problema. Si tiene un problema, el proveedor / instalador debe proporcionarle el firmware más reciente y brindarle asistencia si algo sale mal. En mi caso, mi instalador vino a mi casa e hizo la actualización conmigo. No es que sea difícil de hacer, pero si algo sale mal, debe repararse como parte de la garantía. Esa es solo mi opinión y quizás no la tendencia de la industria.

 

Hello, could you put the firmware file 71.82 to download it. I have a PIP 5048MG with 71.70 firmware with the premature float error ...

On 2021/01/24 at 12:26 AM, ittnor said:

Hello, could you put the firmware file 71.82 to download it. I have a PIP 5048MG with 71.70 firmware with the premature float error ...

71.82 is factory firmware, so it does NOT have the premature float bug fixed. Patched firmware version 71.80a does, but it's based on 71.80, so it has some minor bug that is fixed in 71.82. Both are available here:

https://forums.aeva.asn.au/viewtopic.php?f=64&t=5830

Edited by Coulomb

I received a brand new EASun ISolar SMII 5kw (equal to the PiP-5048MG and others), manufactored in Nov 2020. It's running on 71.85. As my other three are running on 71.70 I requested the firmware to integrate the new one into my setup.

On 2021/01/30 at 11:32 PM, Payback2 said:

It's running on 71.85. As my other three are running on 71.70 I requested the firmware to integrate the new one into my setup.

I suspect that the paralleling constant will be unchanged at 118, but that doesn't necessarily mean that the firmwares are truly compatible (they sometimes neglect to change the paralleling constant when making CAN packet data format changes).

Please keep us informed. It would be a shame to have to revert back to 71.82 for your new inverter.

  • 3 weeks later...
On 2021/02/26 at 2:29 AM, Payback2 said:

 maybe you can have look to analyse the changes.

I gave it a day's work. There are quite a few changes since the previous latest version I had, which is 71.82. So far:

QPGS Command response near the middle, probably battery voltage, there is an extra test against constant 08.0; if less or equal, it reports 00.0

QPIWS Command response has a new field SCC_OK at the start

Commands QMCHGCR, QMUCHGCR, MCHGC, MNCHGC and MUCHGC can now take values up to 100 amps. In some cases, this is 4 extra values. This may indicate that the firmware will support up to 100 battery amps of utility charging, so this business of allowing up to 5000 W of PV might be because the solar charge controller can produce that much now. Of course, it may be that only models with upgraded hardware can safely use the new values.

[ Edit: or it may be that while you can only get 4000 W through the PV charger as before, you can now get a total of 5000 W from PV plus utility charging. That means that they are allowing up 5000 W to flow backwards through the inverter back to the battery; previously this was limited to 4000 W. ]

There is extra logic in a function that checks for overload. It's quite tricky code, making many tests on the present mode (battery, line, bypass, standby, fault, etc). The logic also involves the timed absorb setting.

One of the changes in 71.82 has been dropped in 71.86, involving a test for fault code 11. All of the changes in one of the firmwares called 71.82 ("correct PV MPPT) have also been lost.

There is extra logic in a function that handles fault mode, deciding whether to shut down or not.

That's with checking about 15% of the code; it's slow going. If they didn't change the addresses of memory, it would be about five times faster to check for changes.

Edited by Coulomb
"up to 100" → "up to 100 amps"

4 hours ago, Coulomb said:

I gave it a day's work.

Thank you very much! I've updated meanwhile all inverter and I can see no major difference so far. I had some issue with one of the inverter during bad light conditions (see my other post) but I need to wait for cloudy weather as at the moment the sun is shining all day 😄

I'll keep you updated, if I can spot something.

16 hours ago, Payback2 said:

I'll keep you updated, if I can spot something.

After 24 hours I can observe the following: my problematic inverter is now constantly >200W below his twin, who has the some sunny conditions. Before the software update it was just ~120W. So it seems the firmware update confirmed, that there is an issue with the inverter. I will replace it now with the new one to confirm.

@Coulomb I noticed that the own consumption dropped from ~ 125W for all 3 inverter to  <100W. This based on the delta of the overall AC consumption of all three phases vs the total amount used out of the battery at night with no PV power. Have you spotted something in the code linked to this?

Thx!

  • 4 months later...
9 hours ago, Dirkie said:

So is the 71.86p firmware for the

MKS ii 450v models

There are two firmwares with the version number 71.86. How handy is that?

One is indeed for the Axpert MKS II, the other is for the Axpert King.

The Isolar SM II 5K firmware from a few posts above is indeed main firmware for the Axpert MKS II.

 

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.