I'm attaching two charts to this message.

Both show the start of the solar system in the morning.

Picture 1 ist with the older modified firmware 160.06 from @Coulomb

Picture 2 shows the same situation with the newer firmware 60.95

Before 8:00 the system is in charge mode (charging only), then the 230V output switches on.

In the first case, the MPPT restarts at 8:00, where the output is switched on, and finds a good working point

In the second case, the MPP tracking starts on its own.

 

 

Dear all 

Here is the modification logs from 25.08 to 25.12

 

1.     Added 2 more items in data logs

2.     Supporting the inverter mode on APP for “Hybrid” or “Off-Grid”

3.     Fix the bug of time delay with BMS communication.

4.     Upgraded Progc.12 setting range for 44-55Vdc.

 

 

2 hours ago, mhd_murad said:

Here is the modification logs from 25.08 to 25.12

Thanks for that.

But I'm curious: where do you get this information from?

5 hours ago, Coulomb said:

Thanks for that.

But I'm curious: where do you get this information from?

you are welcome 🤗 

I'm contacting with voltronic support by email 

So I'm assuming you're one of their OEM clients selling under a specific brand? Because they always refuse to talk to end consumers.

20 minutes ago, Tarek Yag said:

So I'm assuming you're one of their OEM clients selling under a specific brand? Because they always refuse to talk to end consumers.

Of course not, I hope so, I am an IT engineer and I have some interest in my inverter 

 

My inverter name is triple A vm iii 4kw 

Edited July 4, 20242 yr by mhd_murad

Yeah, totally understood! We all love tweaking with inverters 😁

So, how did you manage to make them give you more details? I've tried once to ask for a firmware update but they refused to give any details!

I also reported to Eybond about a few bugs in the inverter's monitoring system (DessMonitor), and asked for a firmware update for the Wi-Fi kit, but got no useful help at all!

I don't know 

I'm just send email to the sales team 

[email protected]

try this email 

Is there any documents about communication with inverter by local network without watchpower app

I'm searching about an method to monitor inverter in real time without his display

On 2024/07/01 at 8:59 PM, pintopf said:

Another positive thing about the software version is the fact that the MPP-Tracker no longer gets stuck at low voltage.

can you giv me more about this bug 

 

@Tarek Yag @Coulomb @pintopf

1 hour ago, mhd_murad said:

Of course not, I hope so, I am an IT engineer and I have some interest in my inverter 

 

My inverter name is triple A vm iii 4kw 

I have the same type but 6k Which versions do you recommend after trying it?

10 hours ago, mhd_murad said:

can you giv me more about this bug 

This bug means, that the inverter´s MPPT is stuck at his starting voltage at the begin of a new day, where the brightnes is increasing, until the current of the solar input reaches 200(400?) mA at 60V. The calculation of the output power results in a value that is too low to start the tracking.

If you have some Solarpanels in serial, you reach this current relativ late, you can´t use the first Energy of the day. If you have i.e. 350V panel voltage, are this 70 W (at 200mA)

If the MPPT starting voltage higher, the inverter calculates a higher power and the tracking starts earlyer.

In this thread @Coulomb presents his patched firmware, which sets the starting voltage from the MPP-Tracker to other voltages.

 

 

11 hours ago, mhd_murad said:

Is there any documents about communication with inverter by local network without watchpower app

I use a solution with an ESP32 microcontroller, which is connected to the serial interface of the display via a MAX232 converter.
The ESP cyclically sends a "QPIGS" request to the inverter and provides the result via the MQTT protocol via W-LAN.

(Example: String QPIGS = "\x51\x50\x49\x47\x53\xB7\xA9\x0D";  //hard coded string with CRC)

The ESP32 also receives commands via MQTT, appends the CRC16 checksum and sends the result back into the network.

The ESP32 is controlled via my home automation, using NodeRed.

Edited July 5, 20242 yr by pintopf

On 2024/07/04 at 9:42 AM, mhd_murad said:

Dear all 

Here is the modification logs from 25.08 to 25.12

 

1.     Added 2 more items in data logs

2.     Supporting the inverter mode on APP for “Hybrid” or “Off-Grid”

3.     Fix the bug of time delay with BMS communication.

4.     Upgraded Progc.12 setting range for 44-55Vdc.

 

 

That's weird, coz I have 44-55 range in 25.06 already

 @Coulomb will you try to apply your mppt fixes to the new firmware or is it finally fine as it is?
I'm ok with even older firmware capabilities, but I really want the "premature float" bug fixed 🙂

On 2024/07/05 at 5:37 AM, mhd_murad said:

Is there any documents about communication with inverter by local network without watchpower app

Yes. Search the files section of this forum for Axpert protocol documents. There are slight variations between the various Axpert (off-grid) models, but the Infinis (on-grid) use a completely different protocol. 

12 hours ago, WallK said:

@Coulomb will you try to apply your mppt fixes to the new firmware or is it finally fine as it is?

I'm more than happy to leave the MPPT code alone if it's truly fixed, as it seems to be. Especially since the factory firmware doesn't depend on how many panels you have. 

I can do a patch with only the premature bug fix if there is enough interest. 

On 2024/07/06 at 2:32 AM, Coulomb said:

I'm more than happy to leave the MPPT code alone if it's truly fixed, as it seems to be. Especially since the factory firmware doesn't depend on how many panels you have. 

I can do a patch with only the premature bug fix if there is enough interest. 

Great, thank you!
 

 

On 2024/07/04 at 10:37 PM, mhd_murad said:

Is there any documents about communication with inverter by local network without watchpower app

I'm searching about an method to monitor inverter in real time without his display

If you want to use esphome -- I use this project: https://github.com/syssi/esphome-pipsolar
I've done a fix for dual output inverters (longer QPIGS) and it's live in pip8048 branch

Edited July 19, 20242 yr by WallK

On 2024/07/04 at 10:37 PM, mhd_murad said:

Is there any documents about communication with inverter by local network without watchpower app

I'm searching about an method to monitor inverter in real time without his display

You can refer to another post of mine where I attached the latest communication protocol I'm aware of. It might be of a big help for your project. Additionally, you can find other documents using the search tool and the files section as @Coulomb just stated two posts before this post.
My other post link: https://powerforum.co.za/topic/19010-voltronic-axpert-vm-iii-twin-4kw/?do=findComment&comment=205780

On 2024/07/04 at 10:41 PM, mhd_murad said:

can you giv me more about this bug

You can refer to this post too: https://powerforum.co.za/topic/21234-axpert-vm-iv-twin-firmware-request/?do=findComment&comment=205765

On 2024/07/04 at 10:52 PM, mohamed.kh said:

I have the same type but 6k Which versions do you recommend after trying it?

From my perspective as a Software Engineer, I'd always recommend using the latest available firmware.

On 2024/07/05 at 2:19 PM, WallK said:

That's weird, coz I have 44-55 range in 25.06 already

I'd never expect any good enough or valid information from these amateur teams!

I just finished some experimenting with firmware on my VM IV Twin, and it just came to my attention that Voltronic started using a slightly different naming convention for firmware packages intended for use with the TWIN variants. Packages now are named "VM TWIN" with no indication whether it is for VM III or VM IV. At first, I thought it was missing the complete name by mistake, but as I re-downloaded all the packages again now, I made sure that it is not by mistake. Moreover, the instructions document inside each package named "VM TWIN" now says "VM III and IV" in its title at first line. So, I believe they're indicating now that they're interchangeable for both models of the Twin variant.

@Coulomb, what do you think?

18 hours ago, Tarek Yag said:

So, I believe they're indicating now that they're interchangeable for both models of the Twin variant.

@Coulomb, what do you think?

But I thought that they were still different power levels: 6kW/4kW for VM III, and 5.6 kW/3.6kW for VM IV? Oh wait, I see that 70.70 is labelled VM IV, and it's 6.0/4.0/1.5kW now. So yes, it looks like these are the same models now, just with a different display (removable for the VM III, and round/colour for the VM IV). At least for the Twin variants.

But IF they beefed something up the hardware to support 6.0 kW versus 5.6 kW (only a 7% increase), then it may not be safe to use a 6.0 kW firmware in a 5.6 kW hardware. 24 V hardware is 4.0/3.6 = 11% more, so that may be even more the case.

But maybe they are comfortable now with pushing the hardware a little more, so you can safely get more power out of the older hardware. It's hard to say.

 

I guess you're mixing power levels by mistake. I just revised my information on the official Voltronic Power website, and made sure that non-twin variants of VM III has 1.5/3/5 kW power levels (not 4 and 6), though you've got the right levels for VM IV which are (3.6/5.6 kW). Both non-twin models use firmware major number 61.xx right now.

On the other hand, TWIN variants of VM III and VM IV has two power levels (4/6 kW) and both are using firmware major number 60.xx right now (before versioning started getting messed up recently for both).

I believe this justifies it all. Though, I truly appreciate your hardware-wise caution!

Edited July 15, 20242 yr by Tarek Yag

On 2024/06/29 at 5:12 PM, AMalakani said:

I think they didn't test it in a 45^oC climate

On 2024/07/01 at 8:59 PM, pintopf said:

Much quieter fans at low loads and the heatsink temperature has never been above 45°C.
At higher loads (>1500W) the temperature drops again because the fan(s) then run faster.
The inverter hangs in my basement at around 19°C.

On 2024/06/25 at 12:40 PM, Tarek Yag said:

I will soon take the time to capture actual temperature readings at different times and operations and post it here for more reference and better discussion.

So, as I promised earlier, and since I don't put considerably high loads very often during the day. I have just captured a perfect heat sink temperature reading that should give a great insight about how good is the fans speed after the fan control update for the TWIN variants. I think they're really efficient now and balanced very well in versions (60.95 and 70.00) the ones that I've tested myself which have same fan control logic.

Given (approximate averages):
Room Temp: 33°C
Battery Voltage: 28 V
Battery Charging: 80 A
PV Charging Power: 1250 W
AC Output Apparent Power: 650 W

Surprisingly, heat sink temperature is 50°C only! And I think it's perfect for me given all these circumstances and the very high room temperature!!

Edited July 15, 20242 yr by Tarek Yag

On 2024/07/15 at 2:19 PM, Tarek Yag said:

non-twin variants of VM III has 1.5/3/5 kW power levels (not 4 and 6),

The older VM IIIs are indeed 3 kW and 5 kW, but the "refresh models" seem to be 4 kW and 6 kW, both twin and non-twin. For example, main firmware version 55.06 is for 1.5k/4k/6k, non-twin. But I see it's the only one; perhaps it is an anomaly?

Be open to the possibility at least.

 

Hi,

I have Axpert 6kw VM III Twin, The MCU Has a different version FW (57.07), can I flash it with 25.12 version? And what is the difference between them?

On 2024/07/16 at 6:34 PM, Khalil Koja said:

I have Axpert 6kw VM III Twin, The MCU Has a different version FW (57.07), can I flash it with 25.12 version? And what is the difference between them?

Alas, I do not have any 57.xx display firmware in my collection. My What Axpert FIrmware is That? page says that 57.xx is for Axpert King II models. I suspect that Axpert King II display firmware version 52.07 is designed to talk to most models and is Twin compatible, but that leaves almost nothing for 57.XX. Unless 52.xx is for King 1 and others, while 57.xx is for King II and others.

So sorry, I don't know the answer. If I had to guess, I'd say 25.xx would work, but if it doesn't, there is no 57.xx display firmware to restore it to.