for the moment, I try to change a 2x3 MP2 array to 3x3 configuration. All 9 Multis are daisy chained to a MK3. VE-BusSystemConfiguration can see all 9 devices and configure like expected.
For this, Venus reports alarm #25 what is a firmware incompability. Obviously, I need to update the 3 new or all 9 devices to come to compatible level. Remote console reports FW Version 498 and 552 depending from menue scrolled up or down. VRM reports one VE Bus system what contains the 6 old MP2 devices with FW 498. Unlike VE_BusSystemConfigurator the VRM cannot see the 3 new devices why I cannot perform FW update from VRM.
As far as I understand, VictronConnect is the next prefered method to update FW and VE_Flash is no more supported. VictronConntect shows unexpected errors if I try to connect the daisy chain by MK3 probably because of FW incompability. Connecting to a single MP2 device is succesfull.
Assume FW update is done in the setup menue, VictronConnect asks for a password what is neither 000000 nor the grid code password.
What is the prefered method to update FW for MP2 ?
The question remains why I dont have access to my own devices. Watched the how to video for VictronConnect FW update and even there the PWD is a secret. VictronConnect seems to do nothing more than other tools doing with the MP2 without this PWD.
Use VictronConnect but only 3 units at a time because VC only supports 3 devices.
After updating all to the same FW you can switch to the system configurator.
555 is not yet included in VC.
The changes between 552 and 555 are not relevant for all systems.
Why with VEflash?
VC is way more easier to handle for FW updates, especially if you have more than one device because it updates all in one swipe.
I only use VEflash as last option to recover a device after a failed update.
Updating VE.Bus devices with VC is possible for almost 6 years and I never had serious problems.
The worst thing that can happen is a corrupt FW due to a interrupted update but that can also happen with VEflash and can be fixed with VEflash in most cases.
The best is you don’t have to find the correct FW file manually.
(downside is that FW included in VC isn’t always up-to-date, but Victron is already working on that)
But if you happy with that, you can do it like you want.
The 3x3 system is up successfully again. Finally I used VC instead of VEFlash. About the file versions 26xx555.vff the xx was not available in the expected number. Correct filename needs to match the product ID displayed in VRM (last screenshoot here) what is 2623?
Nevertheless, VictronConnect did the job for v552 but is not always perfect.
The problem seems recursive. Arrays cannot be configured because of diffrent versions and version update cannot be performed because of unrecognized array configuration. To solve this chicken - egg problem, thei only way was to connect the MK3 cable 1:1 each device individually.
VEConfigure asks to download the configuration to all connected devices. This is a great feature but obviously not valid for any assistants. I had to download assistants 9 times individually. Luckily the assistant setups were possible to save and retrieve from file.
VRM is now also correct and hopefully the next update can be done remote from there.
