I just wanted to update my Quattro 12/5000 in our camper to the latest & greatest firmware as this has not been done from the previous owner the last 5 years. The good news: connecting the Quattro via MK3-USB works and I can see the device.
But: it is telling me directly that my firmware is 413 and I need latest 415 to use all features from Victron Connect, that implies: creating a backup & saving the settings. So I could do a firmware update to latest 5xx but I dont have a chance to store the settings.
So I did some research and came across another tool called VEConfig, with this tool I can read & store the current settings as a .vcs File, which enabled me to write back the settings through the old VEConfig tool after the update.
My only concern is that the inverter is not compatible with VEConfig after the update, so is there anyone who used VEConfig with a newer version and can confirm it is possible to write back the settings through VEConfig after the update?
I also checked whether Victron Connect Appliocation is able to read .vcs files but it only can deal with .vcsf files.
Any help or anyone with a similar experience, happy to receive any help. If anyone with a firmware > 5xx could try to install VEConfig and let me know whether it is still possible to connect with VEConfig, that would be super amazing.
thx for your help…so I “did” it today or let’s say “dared to do” but in the end it failed. The good news: everything is running as previously, the bad news, it did not work.
During the update I receive the error V8 with the message “the boot loader did not react to the boot loader setup” - any idea?
I did the firmware update using Victron Connect or is it required to use VE Flash to initially get it to a higher state?
damn…now I got it - thought that I should prefer Victron Connect over VE Flash as I could not find VE Flash for download - just realized it has been installed in parallel with VEConfig and is sitting in the same directory. I will give it a try with VE Flash, minor additional questions:
it says that direct firmwatre download is only available for Victron professionals - is there a way to get it as a normal user as well or should I simply register as preofessional?
there is an additional component connected to the QUattro which is a VE.Bus BMS, it’s firmware also has not been touched since 5 years…so I guess this one should be updated with VEFLash then as well or should it be updated before the Quattro update? Just want to avoid non reversible incompatibilities that is why I am picking your brain
=> I can also buy you a coffee using one of the public donation portals, really appreciate your help and I am very thankful for that.
ok…srry skip the first question, just realised that this is a simple signup flow that enables me to get access to the list of FW.
I will cross check how to determine the correct firmware but based on the images attached I assume for the quattro the “2633556” would be required (type + fw). I also assume that the FW identifiers at Victron are unique so this is not the FW for a totally different device I would assume…, see images attached
lovely! Just for the possible future in case the update works: in the future I should be able to do Updates using Victron Connect in case I am running on FW 556? Or is it best practice to go with VEFlash in any case? Currently I do not have the choice, just want to understand the software tooling required for the future then…
Victron moves to VictronConnect as a global tool, VEconfig and VEflash will be obsolete at some point, its just that your particular firmware version does not support VictronConnect yet. Currently not everything is available through VC yet, even with up-to-date firmware, so you may still need VEconfig for some things, but they are getting there
…one last question: during update of the Quattro using VEFlash: do you unplug the inverter from the 230V source? I mean it is still connected to the batteries so not sure which is the correct approach.
Unfortunately I just came back from the caravan and still could not do the Quattro firmware update. The good news: the whole system is still running stable with the current configuration…
The issue now: I followed the instructions from VEFlash on switching off the inverter and on and then VEFlash should be able to either auto detect or use the defined port (in my case COM3). But I receive an error that the correct COM port can not be found, even the MK3 is correctly connected, I can see this because opening VECOnfig and selecting COM3/autodetect will connect to the quattro.
Any ideas? Or is there a super special magic on when exactly to plugin the ethernet to MK3?
checked this - always made sure I only have one program open to avoid any Software port conflicts.
After my experience yesterday I will keep my fingers away the next couple of weeks from firmware updatzes, happy that everything is up and running on 413 again.
I am afraid, in case I reset the quattro, I run into the same issues like the quattro being “dead” as VE.Bus is disconnected from software point of view (and from my point of view also from hardware as I disconnected the VE.Bus RJ45 connection) and so0me magic in the quattro/my setup preventing the quattro from starting up.
btw as couple of people tagged you as expert, so maybe shooting that question to you helps, as I still can not explain to myself what happened yesterday:
yesterday I plugged into the quattro directly and did not get any response: Quattrro → RJ45 → MK3 => no quattro detetced
the device was only detected in that chain, that is how I actually managed to get the VE.Bus Assistant back to the Quattro:
Quattrro → RJ45 → Mains Detect → RJ45 → VE.Bus BMS → RJ45 → MK3 => quattro detected
I am a little bit confused why VE.Config does not detect the quattro in case it is connected directly to it, rathe than that I plug in at the very very end of the chain and then am able to detect &configure the Quattro again. This seems a little bit weird to me and also prevents me from trying updates again as I am super afraid of any part in that chain not responding after the update and then I am sitting on a non rebootable Quattro.
So if you have any clue/guess/explanation for that behavior, glad to hear
Also if someone tells me that I need to use VE.Flash and VE.Bus connected is not an issue, I might give it another try, but please only drop stuff that you are 100% sure aka done on your own, I feel like there is a lot of fragility in case of more complex setups….
