unfortunately I have to open up a new thread as my previous threads turned into a new, separate problem that maybe someone can help me with.
Basically I am trying to do a firmware update to my Quattro 12/5000 using VE FLash as the current FW (413) does not support Victron Connect so I have to use VEFlash.
If you follow the steps through VEFlash there is a point where it will ask you to remove all connected devices including VE.Bus BMS. Then you have to switch off the Quattro, connect MK3 and switch on the Quattro again. But after that VEFlash does not detect the Quattro, which is because the Quattro does not startup (no LED showing activity) if the BMS is not connected.
So I am facing the situation of not being able to connect the quattro through MK3 if the BMS is disconnected.
Is there any hint how to solve that dilemma and unfortuantely I can not do any jumper configs as the device is build from the previous use soooooo deep into the caravan
Maybe someone has an idea/clue,
thx a lot for your help,
Florian
Can you go into the Quattro programing and on the battery page temporarily remove the tick mark for “Configured for VE Bus BMS “, disconnect the VE Bus devices, do your firmware upgrade then enable “Configured for VE Bus BMS “ again.
hmmmm…unfortunately I do not have that VE.Bus setting. But I just saw on the left “show VE.Bus monitor” maybe this will get me to these settings?
But I think I found the cause for the whole system behaving a little bit bitchy at the moment:
there is a VE.Bus assistant configured for the Quattro, as far as I can judge this software piece is doing exactly the magic of keeping the device off in case of VE.Bus disconnected
The cable I am pluggin into my lptop does not lead to the Quattro directly: it leads to a “VE.Bus Main Detector”, and from the Main Detector to the Quattro. Unfortuantely I can not access the Main detector without breaking my arms like 8 times to get there
=> does anyone have experience in doing a Quattro update with a VE.Bus Main Detector between the MKBus and the Quattro?
The mains detector makes things easier in this case. Its purpose is to switch on the Quattro if mains voltage is present but at the same time the VE.bus BMS has shutdown the system (or is disconnected), which would otherwise be a deadlock. So by connecting mains voltage, the mains detector should switch on the Quattro. All it does is switch pin 6 or 7, cant remember, but the data pins are unaffected
so you think an update with connected mains detector is possible? As said the VE.Bus disconnect currently causes the shutdown but if VE Assistant is removed from the Quattro I think this behaviour should be solved, so the Quattro stays on and the Mains Detector becomes a device routing through the signal…my only concern is that during an update for some reason the Quattro starts to communiucate with the Mains Detector, the Mains Detector switches off due to some routines done during firmnware update and the whole firmware update is half baked…
Long stories short: is there a chance that the quattro during an update procedure will switch off the Main Detector, assuming AC is present all time during the setup procedure?
yep you were 100% right with your approach as it does exactly that…but currently I am a little bit careful regarding reset as I never did that before, removing an Assistant seems less inversive but in the end your approach might be the easier one as I need to import settings then anyway.
Do you know whether update with VE.Bus Main detector “in the middle” between computer and quattro works?
