3 hours ago, esmail-kassir said:

so when I try to use it after updating, I was surprised. 

Try updating your MCU (dispaly) firmware, as it is the one responsible for battery communication.

3 hours ago, esmail-kassir said:

related to the most optimized manual settings? 

It all depends on your battery specifications and your usage. I recommend using the same values that are declared in the data sheet of your battery pack, some minor changes could be made if you know what you're doing, be careful! Also you might be interested in visiting forums containing Felicity battery discussions for more specifics.

2 hours ago, esmail-kassir said:

Is it different than the alarms section in watch-power mobile app ? 

I guess it is different, as the alarms section records statuses only without any values, and the update interval is 5 min, so most probably it never contains any fault data log.

Please always try to post your questions in one reply only. You can quote multiple sentences and posts in one reply.

8 hours ago, esmail-kassir said:

is there any post or thread about Lib and Lic in this forum

I don't recall seeing anything about LIB or LIC protocols. I note that when using LIB or LIC protocols, the label for some settings on the VM IV display can be any three letters taken from RAM; I haven't figured out what sets those letters yet. So these may be in some sense "generic" protocols, whatever that means in practice.

There is this older FelicitySolar document; it doesn't say anything about LIB or LIC:

Felicitysolar BMS Communication Protocol RS485 20210608.pdf

7 hours ago, esmail-kassir said:

I used QPIWS\xB4\xDA\r

and the output was in hexa 

 “ 28 30 30 30 30 30 31 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 B2 A7 0D” 

The result is "(000001000...000" in ascii. All command responses start with an open parenthesis '(' or 0x28. The sixth digit is a 1, all other digits are zero.

With your model, it seems that the sixth digit indicates "line loss status".

* Is the AC input off?

* Could the mains have dropped out overnight?

* Could the mains voltage and/or frequency have gone out of spec?

* What is your AC input range setting? (Usually APL or UPS). APL is less strict, though it may cause slightly longer change-over from battery mode to utility powering the loads (possibly with the help of battery and/or solar with SUB output priority).

4 hours ago, Coulomb said:

The result is "(000001000...000" in ascii. All command responses start with an open parenthesis '(' or 0x28. The sixth digit is a 1, all other digits are zero.

With your model, it seems that the sixth digit indicates "line loss status".

* Is the AC input off?

* Could the mains have dropped out overnight?

* Could the mains voltage and/or frequency have gone out of spec?

* What is your AC input range setting? (Usually APL or UPS). APL is less strict, though it may cause slightly longer change-over from battery mode to utility powering the loads (possibly with the help of battery and/or solar with SUB output priority).

 

 

 

It’s interesting. Which manual or reference did you use to interpret the output? I couldn’t manage to make ChatGPT convert the output, even though I have the Axpert protocol file. I managed to do this with other commands, though.

1. It seems that this command queries alarms (the same alarms as in WatchPower). Don’t worry about the AC loss. In my country, public electricity is available for only 1 hour every 6 hours, so the battery is the main power source, not a backup. Therefore, the PV loss and AC line fail alarms are normal.

2. I’ve attached the PDF I used to form my commands and interpret the output. Some of them don’t work, and I get a NAK reply (negative acknowledgment). Is there a better document for my model that is more compatible?

3. I discovered something weird while checking the commands. Previously, when I tried to set my inverter to “only solar” charging, I noticed that during the night, the charging LED turns solid, and the battery charges at 2A, even though it shouldn’t charge from AC at all. I found this bug as an option in the BMS command, which I don’t fully understand yet. I’m not sure why this is happening.

4. I have attached the firmware I am using, which I thought was version 60.89, but I discovered it is actually 60.76 after the upgrade. I used to have version 60.08 with loud fans, and the Lib protocol wasn’t working with my Felicity 200*48 battery, so I was forced to use Lic. But now I have quieter fans, and the Lib protocol is working.

Communication Protocol 20210804.pdf VM3.hex

On 2024/08/27 at 4:55 PM, esmail-kassir said:

Which manual or reference did you use to interpret the output?

Heh. I read the firmware. Texas Instruments C2000 DSP assembly language code.

On 2024/08/27 at 4:55 PM, esmail-kassir said:

I couldn’t manage to make ChatGPT convert the output, even though I have the Axpert protocol file. I managed to do this with other commands, though.

Interesting. I guess it's because it's not documented anywhere, apart from some old pages of mine, where I state that the output is model specific. I have disassemblies of over 100 Axpert fimwares.

 

On 2024/08/27 at 4:55 PM, esmail-kassir said:

Don’t worry about the AC loss. In my country, public electricity is available for only 1 hour every 6 hours, so the battery is the main power source, not a backup. Therefore, the PV loss and AC line fail alarms are normal.

Yikes. But it may be possible to change settings such that line loss isn't considered a fault. Maybe it's just a warning, but I think that the QFS command reports some warnings. 

Perhaps experiment with setting 22, "Beeps while primary source is interrupted". It may be that turning off the beeps also turns off the warning.

On 2024/08/27 at 4:55 PM, esmail-kassir said:

2. I’ve attached the PDF I used to form my commands and interpret the output. Some of them don’t work, and I get a NAK reply (negative acknowledgment). Is there a better document for my model that is more compatible?

The protocols and their manuals are a mess. The one you have is probably one of the best for your model.

I note that 60.xx firmwares don't support the PBATCD command. The 2 A utility charging should be a result of a suitable Charge Source Priority setting (setting 16), and the maximum utility charge current (setting 11), which can be set to 2 A.

On 2024/08/27 at 4:55 PM, esmail-kassir said:

3. I discovered something weird while checking the commands. Previously, when I tried to set my inverter to “only solar” charging, I noticed that during the night, the charging LED turns solid, and the battery charges at 2A, even though it shouldn’t charge from AC at all. I found this bug as an option in the BMS command, which I don’t fully understand yet. I’m not sure why this is happening.

What exactly do you mean by "the BMS command"? If you mean PBATCD, that's not it. There are many undocumented commands relating to BMS.

On 2024/08/27 at 4:55 PM, esmail-kassir said:

4. I have attached the firmware I am using, which I thought was version 60.89, but I discovered it is actually 60.76 after the upgrade.

I can confirm that the VM3.hex you posted is from a 60.76 firmware update file. Can you attach the complete firmware update file, or at least post what the date stamp on the VM3.hex file is within that update file, please? It would be good to know how recent that firmware is. They are not necessarily in consecutive order past yy.60 these  days.

4 hours ago, Coulomb said:

Yikes. But it may be possible to change settings such that line loss isn't considered a fault. Maybe it's just a warning, but I think that the QFS command reports some warnings. 

Perhaps experiment with setting 22, "Beeps while primary source is interrupted". It may be that turning off the beeps also turns off the warning.

I already have disabled the beep while primary source intercepted and still the same

4 hours ago, Coulomb said:

What exactly do you mean by "the BMS command"? If you mean PBATCD, that's not it. There are many undocumented commands relating to BMS

Yes , I found in the document that PBATCD has options to keep 2A charging from AC even I selected only solar charging 

 

4 hours ago, Coulomb said:

can confirm that the VM3.hex you posted is from a 60.76 firmware update file. Can you attach the complete firmware update file, or at least post what the date stamp on the VM3.hex file is within that update file, please? It would be good to know how recent that firmware is. They are not n

I already attached the firmware file , so what exactly do you mean when u r referring to complete firmware. Is 60.76 has 60v fixed? Do you recommend using 60.89 or later instead of it ? 

7 hours ago, Coulomb said:

I have disassemblies of over 100 Axpert fimwares.

 @Coulomb what a massive mind-blowing number! Good for you, man!

7 hours ago, Coulomb said:

Yikes. But it may be possible to change settings such that line loss isn't considered a fault. Maybe it's just a warning, but I think that the QFS command reports some warnings. 

It is not considered a fault in the VMs too, a warning only, and it shows in apps too.

7 hours ago, Coulomb said:

Perhaps experiment with setting 22, "Beeps while primary source is interrupted". It may be that turning off the beeps also turns off the warning.

Doesn't change anything for the VMs, just the beep sound.

3 hours ago, esmail-kassir said:

I already attached the firmware file , so what exactly do you mean when u r referring to complete firmware. Is 60.76 has 60v fixed?

He's asking you to upload the complete .ZIP file of the firmware you uploaded, not the .HEX file alone.

Edited August 28, 20241 yr by Tarek Yag

5 minutes ago, Tarek Yag said:

He's asking you to upload the complete .ZIP file of the firmware you uploaded, not the .HEX file alone.

 

VM3.zip

@esmail-kassir what we really need is the original firmware package from the original source, which contains the reflash tool too. It is exactly similar to others like the attachment in this post:
https://powerforum.co.za/topic/19010-voltronic-axpert-vm-iii-twin-4kw/page/2/#comment-192984

15 hours ago, Tarek Yag said:

what we really need is the original firmware package from the original source, which contains the reflash tool too.

That would be ideal, especially if this was a specially good firmware. However, it seems to be dated 2023-5-31, which means that four firmwares are available that have later time stamps. So unless it turns out that this one has something that the others don't, then it's not a problem.

@esmail-kassir,thanks for that .zip. I assume that's not how you received it from your supplier; it has a link to the AEVA website for the upload instructions. I assume that these have not overtaken the official upload instructions!

38 minutes ago, Coulomb said:

I assume that these have not overtaken the official upload instructions!

I will be changing all my firmware attachments soon to both protect the HEX file properties, and link it to its specific flash tool that came originally with it. I just realized the bad effect that we discussed a few days ago.

Edited August 29, 20241 yr by Tarek Yag

On 2024/07/17 at 12:29 PM, Coulomb said:

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.

Sorry for delay, to keep you updated:

I have successfully update my 6000W VM III Twin display's FW from 57.07 to 25.08.

I got an error 032 first (maybe i should upgrade display then inverter) ?, finally a server center fix it and upgrade the FWs.

On 2024/08/22 at 12:54 PM, Fawad said:

Hi, i have VM 4 Twin model with 6kw variant with main firmware version 76.60 , can you please confirm is this new firmware or old 

here is link

https://drive.google.com/file/d/1Wdy-faZo4SiGAOnmrzFCnu1vG8RM3B5o/view?usp=sharing

@Coulomb @Tarek Yag @Nabeel Raza

can any one help which vm model is this, i have this firmware installed on my inverter but in low light its not working as expected , stuck at 60v , the fans are quiet only work when there is load percent thank you

22 hours ago, Fawad said:

can any one help which vm model is this,

You told us that it's a VM  IV 6kW Twin. It's unclear to me whether there are actually VM III or VM IV  specific firmwares; certainly many people use them interchangeably. At first pass, I see nothing unusual  about 76.60; it looks much the same as other VM III Twin and VM IV Twin firmwares.

If you want to try patched firmware, the only patched firmwares for these models are  x60.95 and x60.06, available here:

https://forums.aeva.asn.au/viewtopic.php?p=98208#mppt_VM34

It seems to me that it should work on your model, but I can't guarantee it.

22 hours ago, Fawad said:

can any one help which vm model is this, i have this firmware installed on my inverter but in low light its not working as expected , stuck at 60v , the fans are quiet only work when there is load percent thank you

I, and @Coulomb already replied to your first post in this thread. Please refer to our replies at:

We can't be of any more help to you. You can try and test the patched firmware by Coulomb at your own risk.

On 2024/08/08 at 10:21 PM, Coulomb said:

I'll check my work; somehow I doubt that I screwed up.

I've checked again; I can't see any problems, unless as I said earlier the whole idea of "translating" Georg's 90.06 patches to VM firmwares is somehow flawed.

Why I keep have this message when I update MCU, Please help!

@Khalil Koja, please give us complete details again. Your inverter's model number, your current MCU firmware version and what version are you trying to upload, and any other necessary info. From what the reflash app is reporting, it seems like an adapter issue. Did you set the Baud Rate correctly in Windows Device Manager?

Connection settings for MCU reflash should be: Baud Rate: 2400, Parity: None, Data Bits: 8, Stop Bits: 1, Flow Control: None.

Anyway, re-read all instructions written by Coulomb for reflashing firmware.

Edited August 31, 20241 yr by Tarek Yag

41 minutes ago, Tarek Yag said:

@Khalil Koja, please give us complete details again. Your inverter's model number, your current MCU firmware version and what version are you trying to upload, and any other necessary info. From what the reflash app is reporting, it seems like an adapter issue. Did you set the Baud Rate correctly in Windows Device Manager?

Connection settings for MCU reflash should be: Baud Rate: 2400, Parity: None, Data Bits: 8, Stop Bits: 1, Flow Control: None.

Anyway, re-read all instructions written by Coulomb for reflashing firmware.

#1

Axpert VM III 6000W Twin

Sn: 96342304xxxxxx

MCU FW: 57.08 to 25.08

Inverter FW: 60.05

 

#2

Axpert VM III 4000W

Sn: 96322110xxxxxx

MCU FW: 119.12 to 19.18

Inverter FW: 55.03

 

Both failed to upgrade MCU FW (Connection Failed!)

I have tried :

3 different adapter (USB to RS232) and test them successfuly with check PL2303 tool.

2 different cable (RS232 to LAN).

 

 

 

Wow, this seems like a lot of work. As I recommended for you, did you check your adapter's port settings in Device Manager? Any incorrect settings will prevent a successful connection. Attached are the correct settings.

3 minutes ago, Tarek Yag said:

Wow, this seems like a lot of work. As I recommended for you, did you check your adapter's port settings in Device Manager? Any incorrect settings will prevent a successful connection. Attached are the correct settings.

All is correct but Bits Per second: 9600

Is this my problem?

 

I have attached my RJ45 port:

Edited August 31, 20241 yr by Khalil Koja

2 hours ago, Khalil Koja said:

Why I keep have this message when I update MCU, Please help!

I had the same.

Change driver

Yes, you strictly need to match the Baud Rate of the connection with the inverter. Try first if you can make a successful connection with the Inverter via WatchPower, then, most importantly, close it before trying to reflash any firmware. I attached the correct cable pinout, if you don't get a connection via WatchPower, switch lines 1 (TX) and 2 (RX) on your RJ45 cable side.

I have had the same issue for months, I purchase multiple connector, leads however still can’t communicate to update firmware or use watch power. I purchase inverter second hand and the previous owner who informed me that he updated the firmware to use pylontech batteries and following the update lost all communications with PC & batteries.

The inverter works with my voltronic batteries however I cant resolve the issue with the RS232 port. I get the same message when I try and update the MCU firmware. 

Edited September 1, 20241 yr by alan_1969uk

On 2024/08/08 at 2:21 PM, Coulomb said:

OK, that's weird. You seem to have compared like for like pretty well. I'll check my work; somehow I doubt that I screwed up. My guess is that the original patches for Axpert Maxs just don't translate to VM firmware, for complex reasons.

For now, I've marked the patched firmware as experimental.

Thanks for the reports.

I checked once again patched 60.95 (this time 960 version) and it is the same.

Next I checked only anti premature float bug version (860).

It is free from mptt goes to 0W at current change but:

1. Full SUN no clouds

At the morning bulk phase began and goes till 53.8(9) V. Diode CHG blinking. After that goes to float. Bulk never cross 54V. On inverter it is set 55.2.

2.Some clouds yestarday.

 

Bulk phase ends at 53.6 V.

 

 

Edited September 1, 20241 yr by bratpit