@Coulomb I think he is confusing his model with the normal variant, cause he is saying that he has the Twin version in an earlier post by him

On 2024/03/29 at 9:51 AM, mhdite7 said:

I have axpert vm iii 4kw twin

Don't the firmware I gathered in a separate thread apply to his unit? Because AFAIK the VM III normal variant firmware is in the 61.xx range, not the 60.xx

On 2024/06/03 at 10:35 PM, Tarek Yag said:

I think he is confusing his model with the normal variant

Why do you say that?

On 2024/06/03 at 10:35 PM, Tarek Yag said:

Don't the firmware I gathered in a separate thread apply to his unit? Because AFAIK the VM III normal variant firmware is in the 61.xx range, not the 60.xx

Yes, your collection of 60.xx firmwares is relevant. And indeed you point out that 60.89 is later than 60.06. My bad, I overlooked 60.89. Sigh.

The 61.xx firmwares are 1500/3600/5600W non-twin, so these are not relevant to a 4 kW Twin model.

@mhdite7, Tarek Yag's link does indeed have a copy of 60.89, which is slightly later than 60.06. My apologies for the error. I don't know if it will address your specific problem(s).

Edited June 6, 20242 yr by Coulomb
61.89 → 60.89

On 2024/06/04 at 5:32 PM, Coulomb said:

Why do you say that?

Because @mhdite7 wrote that his inverter's model is a Twin version, then in a later reply he (I believe mistakenly) omitted the "Twin" part of the model, even though he was talking about his same inverter.

On 2024/06/04 at 5:32 PM, Coulomb said:

My bad, I overlooked 60.89. Sigh.

No worries, with a messed up versioning, it might happen very often with all of us, as it is very hard to keep up with all the duplicate numbering!!!

On 2024/06/04 at 5:32 PM, Coulomb said:

have a copy of 61.89

60.89 *

Edited June 5, 20242 yr by Tarek Yag

6 hours ago, Tarek Yag said:

Because @mhdite7 wrote that his inverter's model is a Twin version, then in a later reply he (I believe mistakenly) omitted the "Twin" part of the model, even though he was talking about his same inverter.

Alas, people aren't necessarily precise with the model names. Especially in this case where apparently they're not using the twin output feature. I'm curious to know definitively whether you can use a non-twin firmware in a twin machine, and possibly vice versa, if you don't use the twin output feature.

6 hours ago, Tarek Yag said:

On 2024/06/05 at 12:32 AM, Coulomb said:

have a copy of 61.89

60.89 *

Arrgh! Thanks. Corrected now. My apologies to anyone that was confused by my error.

@Coulomb, referring to this previous post of mine, right before you sent me the link to the latest display firmware (39.16) for my VM IV Twin inverter, I flashed the display firmware of the normal variant (22.21).

I first noticed that the built-in Wi-Fi Kit stopped sending any data to DessMonitor platform, although the inverter kept working normally and the display kept showing valid data for AC1 output with no signs for the other AC2 output which is totally expected, and there were no settings for AC2 too. However, what really amazed me, that the LED settings for the round display showed up in WatchPower app, unlike with the Twin firmware where LED settings never existed in WatchPower (not even with the stock firmware that came with the inverter)!!! I guess that's another bug made by these amateur firmware makers!!

I wanted to share my experience with you and the community, hoping to find someone who tried this with the DSP firmware. Note that all the testing I've been conducting the whole time since I bought this inverter in August 2023 is on the only unit I have at home which is supplying us about 95% of our needs in a semi off-grid installation here! I know, I'm crazy enough to do this 🤪

On 2024/02/09 at 4:37 PM, Coulomb said:

Sadly, it's not so surprising.

I've retested the issue now having solar panels
The OSO (solar only charging) mode will not charge batteries from grid if solar input is 0V
But as soon as a tiniest bit of sun shines on panels -- it will start drawing 1-2A from grid (charging with 300-400 watt)
So the issue wasn't really fixed, just a hack for 0 volts PV applied

3 hours ago, WallK said:

I've retested the issue now having solar panels
The OSO (solar only charging) mode will not charge batteries from grid if solar input is 0V
But as soon as a tiniest bit of sun shines on panels -- it will start drawing 1-2A from grid (charging with 300-400 watt)
So the issue wasn't really fixed, just a hack for 0 volts PV applied

Have you checked it on "solar first" mode?

On 2024/06/08 at 12:26 PM, bratpit said:

Have you checked it on "solar first" mode?

Yes
With Solar first -- it will charge battery from grid if moon shines, for example
But with SBU mode and battery above "Back to Grid" -- it will draw only 4w from grid periodically and not charge from grid at all, which is great

SUB and USB modes with "Solar only" charging will still charge with couple of amps from the grid if a tiniest amount of voltage exist on PV

I guess this is a well described bug now. Thanks!

@WallK I just came across a related command in the Communication Protocol for Axpert MAX II / VM IV / MKS IV

Could you relate your issue with the attached command shown in the attached image?

I also attached the complete communication protocol for future reference for the benefit of everyone.

Communication Protocol 20210804.pdf

12 hours ago, Tarek Yag said:

@WallK I just came across a related command in the Communication Protocol for Axpert MAX II / VM IV / MKS IV

Could you relate your issue with the attached command shown in the attached image?

I also attached the complete communication protocol for future reference for the benefit of everyone.

Communication Protocol 20210804.pdf 920.14 kB · 1 download

This command is not supported, it just replies with NAK

I think documentation reflects the bug, doesn't sound intentional
Especially, when it doesn't do this in SBU mode at all

Edited June 25, 20242 yr by WallK

To be honest, I didn't expect the command to work on your inverter, neither I thought about it. But I shared the command to make sure that it reflects your bug exactly.

So, can we now safely say that the behavior is by design and not a bug?

hi all please any one help

i have voltrex Axpert VM III TWIN 6K off grid

and i have 2 problem

first: fan won't stop 

second: i adjast max AC charging current at 50A
but current charging 21A 

 

note: i don't have solar panels just AC (utility)

main cpu firmware 60.07
secondary cpu firmware 25.12

any help😰

12 hours ago, modymishaSnail said:

hi all please any one help

i have voltrex Axpert VM III TWIN 6K off grid

and i have 2 problem

first: fan won't stop 

second: i adjast max AC charging current at 50A
but current charging 21A 

 

note: i don't have solar panels just AC (utility)

main cpu firmware 60.07
secondary cpu firmware 25.12

any help😰

What is the battery ?

14 hours ago, modymishaSnail said:

first: fan won't stop

In the Twin variants fans are always running, they don't stop at all. However, if you upgrade your inverter's main CPU firmware to one of the latest VM III Twin firmware versions you'll get much quieter fans, as Voltronic just recently introduced the fan speed logic, finally!

14 hours ago, modymishaSnail said:

second: i adjast max AC charging current at 50A
but current charging 21A

I need to know the following: Battery Type, Bulk Charging Voltage, Float Voltage, and a screenshot from the monitoring app when your inverter is charging your battery. Do you have any experience with inverters?

Good afternoon everyone, I have a Model AVM4T4K5K-24 inverter, connected to 2 PYLONTECH UP2500 batteries, the "A70" error often appears despite the batteries being at 75%. The firmware version is:
U16003
U23905
U30000.
The parameters 
12 is at 10%
13 is at 20%
29 is set to 10%
The inverter is not connected to the public electricity grid.
I had the manufacturer send me a new firmware, 60.87 and MC 39.17
Do you know if there is a newer version?
Furthermore, by changing parameter 5 from PYl to USE and setting the right voltages, the inverter works correctly. The batteries are all connected correctly with the original cables. The Dip Switches are 1 ON 2-3-4 OFF on both batteries.
Do you know if there is a newer version?
I attach received firmware.

VM TWIN_DSP_6087.7z

Firmware MCU39.17

Remote Panel_Reflash_MCU(39.17).rar

On 2024/07/18 at 12:31 PM, Taher Sylla said:

lithium lifepo4 200a 48v

 

@siedrosat, please be aware that your inverter's model name that you provided in your post (AVM4T4K5K-24) doesn't seem to represent an original Voltronic inverter. Trying to reflash a clone model might brick your inverter.

Your issue might be due to setting wrong addresses for the two batteries (DIP switches) as each battery should have it's own address, especially for a master-slave battery setup. If this is the case, then your issue is not related to your inverter's firmware.

@Tarek YagThanks for the reply. But I'm sure that my inverter is original voltronic, because the seller is official voltronic. I attach a photo of the label. Currently the battery configuration is as follows: 2 UP2500 batteries in parallel and the dip switches are:
Master Battery on 1st ON (Baud 9600 and 2-3-4th off, 
Slave battery on 1st ON (Baud 9600 and 2-3-4 on off, as per the Pylontech manual. 

Firmware now is U1 70.00 ad U2 39.17
I've seen on other forums that many have this type of problem.

Edited August 17, 20241 yr by siedrosat

4 minutes ago, siedrosat said:

Firmware now is U1 70.00 ad U2 39.17

Thanks for providing a photo of the sticker. From these firmware versions, I guess it is a legitimate Voltronic inverter, and the brand is known to me, indeed.

I would suggest the first step now is to upgrade your display firmware (MCU) which may solve your issue, as display firmware updates usually contain BMS connection improvements and bug fixes. The latest display firmware for VM IV Twin we have on the forums right now is 39.26. Here's the link for download:

I've just included the MCU Reflash Tool in that post too.

@Il mio amico Tarek Yag Tomorrow I will try to update the MCU to version 39.26

Edited August 17, 20241 yr by siedrosat

1 hour ago, siedrosat said:

@Il mio amico Tarek Yag Tomorrow I will try to update the DSP to version 39.26

I guess it's just a typo in your reply. But anyway, DSP version 70.00 is fairly recent, I don't think you need to update it.

Update the MCU to version 39.26 first, not DSP.

On 2024/08/17 at 12:25 AM, siedrosat said:

Do you know if there is a newer version? [ Than 60.87 ]

That's from February 2024, so it's later than anything else I have, including 60.89, 60.90, and 60.95.

It's also later than 70.00.

However, 39.16 is not the latest VM IV round display firmware; that's 39.26 here.

 

Edited August 18, 20241 yr by Coulomb

@Tarek Yag @Coulomb

Hi everyone, I updated the mcu to version 39.26.
Currently the inverter has DSP 70.00 and MCU 39.26.

Error 70 appears the same with the "PYL" setting, shedding the load.

So I think there is some problem in managing SOC PYL.

The 2 batteries have 3 LEDs lit.

At the moment to make everything work I am using the "USE" setting with :

parameter 12 at 23.4V

parameter 13 at 25V

parameter 25 and 26 at 28.4v

parameter 29 at 24V and parameter 30 disabled.

I hope the problem will be solved with the next updates.