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.

Collection of DSP Axpert Firmware for VM III TWIN and VM IV TWIN

Featured Replies

  • Replies 523
  • Views 94.2k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Mohammad Jawish
    Mohammad Jawish

    Thanks for your reply    I upgrade my inverter to the mentioned version  The twin problem not solved  I faced other problem after the update  Max charging current reduced to 1

  • esmail-kassir
    esmail-kassir

    @Coulomb as I can see they shared FTP link so you can explore other folders , and I found many interesting things such as a firmware with 60.10 dated june-2024 (in the file meta data ) , accordin

  • [ Edit: There is a problem with this patched firmware; DO NOT USE! See here for the corrected version, now called x60.96, but still based on factory firmware version 60.95. It may be that unpat

Posted Images

On 2024/11/23 at 12:50 AM, mhd_murad said:

I have 4 panels

That might be a bit low for reliable operation. It it possible to add one or two panels?

On 2024/11/23 at 12:50 AM, mhd_murad said:

Main v 60.89

You could try updating the main firmware; 60.10 is about 6 months later than 60.89:

On 2024/11/23 at 12:50 AM, mhd_murad said:

electricity volt 220 and 49 Hz 

49 Hz might be part of the problem, especially if it's not particularly stable.

It might also be worth switching the inverter to 220 V operation; by default, it's expecting 230 V.

21 hours ago, ahmad almawal said:

What software is there for this inverter?

That appears  to be a VM IV 5.6 kW Twin. Both the DSP 12.xx and the display 63.xx are quite rare. I have no firmware update files for either of those, sorry.

[ Edit: Sigh! I see that the sticker says that it's rated at 8000W. So now I have no idea what that firmware is. ]

It might be possible to update to a later main (DSP, U1) VM III or VM IV 5.6 kW  Twin firmware with a different major firmware version number, but I strongly do not recommend it.

Edited by Coulomb

On 2024/11/24 at 12:25 PM, Coulomb said:

You could try updating the main firmware; 60.10 is about 6 months later than 60.89:

can you send me this firmware (60.10) please 

  • 2 weeks later...

Hi i have Axpert VM III TWIN 4kW, now the seller send to me this firmware and it will be the latest according your collection, but i have the stuck voltage bug, i have 8 solar panel in series so i have a total VOC of 400V, can you adjust the mppt starting point to avoid the buffer time to start the MPPT? @Coulomb

@esmail-kassir  you have tested many fw have you see which is the best for MPPT starting point? 

Can you confirm that the Axpert VM III TWIN firmaware is the same of 4kW 24V and 6kW 48V?

 

image.thumb.png.0756ac33e65d1212d171e4863dcb7a2c.png

VM TWIN_60.10.7z Remote Panel_Reflash_MCU(25.16).rar

Edited by lucass

8 minutes ago, lucass said:

you have tested many fw have you see witch is the best for MPPT starting point? 

The MPPT behavior looks identical for all these firmware for me ( unfortunately most of the test was during summer so it could be some different during winter)and If I am not wrong  @Coulomb couldn't find any different in MPPT code in those firmware (except the patched ones )

currently I am satisfied with 60.76 (no fan noise and decent PV input ) 

5 hours ago, lucass said:

Hi i have Axpert VM III TWIN 4kW, now the seller send to me this firmware and it will be the latest according your collection, but i have the stuck voltage bug, i have 8 solar panel in series so i have a total VOC of 400V, can you adjust the mppt starting point to avoid the buffer time to start the MPPT? @Coulomb

@esmail-kassir  you have tested many fw have you see which is the best for MPPT starting point? 

Can you confirm that the Axpert VM III TWIN firmaware is the same of 4kW 24V and 6kW 48V?

 

image.thumb.png.0756ac33e65d1212d171e4863dcb7a2c.png

 

If there is no enaugh current to start mptt  at the chart  voltage is about 60V and this is not stuck at it but simply can not start because lack of current in low light conditions . This is normal.

Next if it goes at about 70V mptt starts working but only for self consumption of the inverter .No production on chart.

After , a some time  if current rises above self consumption  inverter start showing  production.

In winter go parallel  with panels so they double current hence mptt better reacts for low light.

Chart from today. Winter is coming :)

 

Przechwycenie obrazu ekranu_2024-12-05_13-56-21.png

Edited by bratpit

15 minutes ago, bratpit said:

 

If there is no enaugh current to start mptt  at the chart  voltage is about 60V and this is not stuck at it but simply can not start because lack of current in low light conditions . This is normal.

Next if it goes at about 70V mptt starts working but only for self consumption of the inverter .No production on chart.

After , a some time  if current rises above self consumption  inverter start showing  production.

In winter go parallel  with panels so they double current hence mptt better reacts for low light.

Chart from today. Winter is coming :)

 

 

 

After 7:00 the voltage go to 238V but zero power, so the voltage go down and when it is above 110V start the production at 8:10, so my limit is 110V not 70V as you 

 

image.thumb.png.4d2870da395e717f7b7a42efe5ff06af.png

1 hour ago, Coulomb said:

Yes. Also 1500W 24V.

Perfect, can you adjust the current or voltage to have better perfomance in cloudy condition? @Coulomb

image.thumb.png.b4a0502eb521837032da9641528d19d1.png

you can see the Axpert VIII Twin has some problem to start, today only after 11:00 to 12:00 it is started

 

This is the voltage graph where you clearly see the voltage go to 370V when the soalr panels start to produce energy

 

image.thumb.png.23b0e13045a24710810f2ef76e29c323.png

For those waiting for VM III firmware version 60.10 to be patched, here it is.

These are patched firmwares version x60.10, based on factory firmware version 60.10 for the Axpert VM III Twin 6kW, 4kW, and 1.5kW, and the Axpert VM IV Twin 6kW, 4kW and 1.5kW. These patches implement most of Georg's MPPT "stuck at 90V" patches (here it would be "stuck at 60 V"), and fix the premature float bug. The only patches not applied are for the forward current constant, which doesn't seem to be changed based on solar voltage in any VM firmwares. The version number should display in full when using monitoring software, but will still show as 60.06 on the front panel display. Do not use with any other models, not even older VM III and VM IV models with power ratings like 5 kW or 3 kW, or non-twin models. Use at your own risk.

In the reflash tool, you may have to navigate to the folder with the patched files the first time it is run. Choose the hex file with the minimum MPPT voltage you want: 90, 100, 150, or 200 V, or choose the one with no MPPT patches at all (see below). Use a minimum MPPT voltage that your panels rarely go below unless it's so dark that there is no significant solar power available. This will depend on how many and what type of panels that you have, and may benefit from some experimentation.

960.10 has a minimum MPPT voltage of 90 V. Use this if you have the bare minimum number of panels (e.g. 4 72-cell panels).

160.10 has a minimum MPPT voltage of 100 V.

560.10 has a minimum MPPT voltage of 150 V.

260.10 has a minimum MPPT voltage of 200 V.

860.10 has no MPPT patches at all, just the premature float patch.

dsp_original.hex is the unpatched original (factory) firmware version 60.10, in case you want to revert to the original.

 

Firmware upload instructions for models with a removable or round display.

dsp x60.10_patched.zip

Edit Jan 2025: In some VM patched firmwares, I used simple code that unfortunately failed to ever reach the float stage. This patched firmware does not have that problem, and as far as I can tell it never did. Earlier patched firmware versions x60.06 had the bad premature float bug code.

Edited by Coulomb
Added some words about the 860.10 variant, and clarified nearby text. 90.06 -> 60.10

2 hours ago, Coulomb said:

dsp_original.hex is the unpatched original (factory) firmware version 90.06, in case you want to revert to the original.

Maybe you mean that dsp_original.hex is 60.10 not 90.06? 

Can i install only the U1 firmware not MCU?

 

 

According my previus post i had U1 56.11 e U2 25.08 

https://powerforum.co.za/topic/16007-axpert-vmiii-4kw-24v-firmware-miscellaneous/?do=findComment&comment=152129

now i have U1 60.10 e U2 25.16 

https://powerforum.co.za/topic/29708-collection-of-dsp-axpert-firmware-for-vm-iii-twin-and-vm-iv-twin/?do=findComment&comment=213006

 those firmware are original, can you see any differences in the part of mppt firmware?

 

 

Now i have some issue in early mornig and cloudy condition, i have 8S configuration of panels, so i have enought voltage like 370V in working conditions, is the best fw for me the 260.10? can i install only the inverter fw and not the mcu?

 

 

 

 

14 hours ago, lucass said:

Maybe you mean that dsp_original.hex is 60.10 not 90.06? 

Duh! Yes. Too many firmwares! Edited. Thanks for the pointer.

14 hours ago, lucass said:

those firmware are original, can you see any differences in the part of mppt firmware?

Comparing firmwares is a big job, and a lot of the changes are presumably in the BMS comms part, which I'm less familiar with. So sorry, I have not compared these two. 

14 hours ago, lucass said:

Can i install only the U1 firmware not MCU?

Yes, though it's possible that the other way around won't work (new display firmware sends new commands to the DSP, and gets stuck when the DSP just NAKs the new commands.

 

14 hours ago, lucass said:

Now i have some issue in early morning and cloudy condition, i have 8S configuration of panels, so i have enought voltage like 370V in working conditions, is the best fw for me the 260.10?

Yes, you have plenty of panel voltage for the 200 V minimum MPPT voltage variant (260.10).

On 12/5/2024 at 10:59 AM, esmail-kassir said:

The MPPT behavior looks identical for all these firmware for me ( unfortunately most of the test was during summer so it could be some different during winter)and If I am not wrong  @Coulomb couldn't find any different in MPPT code in those firmware (except the patched ones )

currently I am satisfied with 60.76 (no fan noise and decent PV input ) 

Greetings, my dear brother Can you send it to me? With the appropriate screen software Thank you in advance

On 2024/07/29 at 11:52 PM, bratpit said:

VMIII 6kw twin.FW 60.95

Never go to bulk 55V. Go to float 54.5 and current go down gradually .

Is that premature float bug ???

 

Forgive my laziness, I just wanted you to make sure that know, @bratpit, about the x60.96 firmwares, that fix the premature float bug in factory firmware version 60.95. Patched firmware version 860.95 has only the premature float bug fixed, no MPPT changes. But of course you may benefit from the MPPT changes as well.

Thanks again for the generous coffees!

 

  • 2 weeks later...
On 2024/12/30 at 6:19 AM, ahmad almawal said:

what is the best software for this device

If you mean what is the best firmware to update to, usually you should not update firmware unless you need a particular bug fixed or feature only available in a later version.

In the 56.xx firmware version range, the latest is 56.72, available from the link in this post:

Firmware upload instructions  for models with a removable display.

Edited by Coulomb
"56.62" → "56.72"

  • 2 weeks later...
On 9/25/2024 at 9:18 AM, esmail-kassir said:

@Coulomb

as I can see they shared FTP link so you can explore other folders , and I found many interesting things such as a firmware with 60.10 dated june-2024 (in the file meta data ) , according to @Mohammad Jawish they told him that it is the last official version !

 

Main folder:

https://ftps.voltronic.com.tw/T/Temp-987EB17E23484B20A6C2/

Twin modified version :

https://ftps.voltronic.com.tw/T/Temp-987EB17E23484B20A6C2/VM TWIN_84.00.7z

Big thanks to @Mohammad Jawish for sharing the link with us 

it seems there is no newer versions from Voltronic since a while 

On 9/10/2024 at 9:27 PM, Tarek Yag said:

Hahaha 😁 I contacted Eybond support a long time ago about this exact settings issue, and it turned out that our inverters are not supported by their web app, unlike the mobile app which is working totally fine. I contacted them a second time about a month ago and got the same answer.

I tried the upgrade feature and it never and will never work, and from a communication perspective, never try to upgrade online, because if you lose connection while upgrade is in progress, you'll get a disaster!

I Tried changing the settings from the PC web portal again , and voila it works now . but the strange thing that the settings button disappeared from the mobile app

 

also now the is a paid option to increase the data fetching speed to 1 per minute so it is becomes more real time monitoring 

Hello @Coulomb , thank you for your work. Sorry for my English, I'm from Ukraine and I'm writing through a translator

I have an inverter Axpert vm 3, and it doesn't work very well, it has a problem with freezing at 60v and also a problem with float charge. Yesterday there was an eeprom fault error.

I wanted to change the firmware to your 560.10, but in the neighboring topic I saw that they wrote about the errors found in your code. Tell me, is it safe or is it better to change it to the factory 60.10 for now?

Screenshot_20250117_092104_Gallery.jpg

Screenshot_20250117_092108_Gallery.jpg

Screenshot_20250117_091155_WatchPower.jpg

Screenshot_20250117_091205_WatchPower.jpg

On 2025/01/17 at 5:22 PM, dmytryk31 said:

I wanted to change the firmware to your 560.10, but in the neighbouring topic I saw that they wrote about the errors found in your code. Tell me, is it safe or is it better to change it to the factory 60.10 for now?

I just checked, and 60.10 has the proper premature float bug fix. So don't avoid the patched versions for that reason.

Factory firmware version 60.10 has been reported as having fixed the stuck at 60 V issue. I have not had time to understand why it might be fixing the problem, I need to research some more. So it might be worth trying factory firmware version 60.10, or possibly 860.10, which has only the premature float bug fixed. 

On 2025/01/17 at 5:22 PM, dmytryk31 said:

Yesterday there was an eeprom fault error.

It's possible that 60.10 has a fix for this, but it also could be a hardware fault. EEPROM faults seem far too common lately.

For convenience, here is the patched x60.10 firmware, which includes the unpatched factory firmware version 60.10:

 

 

On 2024/12/20 at 1:15 PM, Coulomb said:

Forgive my laziness, I just wanted you to make sure that know, @bratpit, about the x60.96 firmwares, that fix the premature float bug in factory firmware version 60.95. Patched firmware version 860.95 has only the premature float bug fixed, no MPPT changes. But of course you may benefit from the MPPT changes as well.

Thanks again for the generous coffees!

 

Thanks for response.

860.96 not fixed it in my inverter.

In the morning diode blinking that states that it is in the bulk state but goes far too early to float state often below 54V (this is not one point of voltage but within narrow range ) . So never arrives absorbtion point. So I charge may batteries to float point ( here 54.9V) . This is the picture how it goes today. Blue circle indicates zone when inverter switches to float state. I think it might be a hardware problem because this happens both when charging from the sun and from the grid.

 

Przechwycenie obrazu ekranu_2025-01-19_14-11-29.png

Edited by bratpit

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.