I hate myself for having started the whole update idea…now I am exactly in the situation where I ended up with a non working system.
Issue Description:
Quattro not turning on by switching the main switch to on
What happened:
Firmware was v413, as firmware updates failed due to VE.Bus Main dect shutting down the device I removed the VE Assistant through VE.Config and deployed the configuration
after deplyoment Quattro did not start anymore
My guess: the VE.Main dect still doe some “magic” telling the Quattro not to startup due to whatever reason.
I disconnected the Main Dect RJ45 but the result stays exactly the same, switching on the Quattro does not result in any LED lighting up so sth is “blocking” it from startup
Any help is highly appreciated…I pray that I can somehow fix without unmounting the quattro.
Hi…thx for helping…I did not come to the point of starting the update, first step I did was to get rid of that VE.Bus behaviour that previously prevented me from updating:
so I removed the VE.Bus Assistant and then pushed the configuration change to the device.
SInce that push the device does not turn on anymore, so I can also not connect through VEConfig/MK3 as the device needs power to be detected within VEConfig.
So in case I could “somehow” make the device switching on again I could continue and push the update but as the Main Dect does some strange things in between I can not power up the quattro.
Disconnecting the Mains dect you mean just unplugging it? From what I can see in the diagram there should be a circuit protect between…
Also from what I see in the diagram: the AC flows through the main dect, so I do not see that disconnecting it can help as otherwise the Quattro would not have any AC and most likely will not start at all?
P.S.: maybe I am only wrong on the major issue: if I switch the main switch on the quattro to on, I do not see any light…and if I connect through the MK3 it does not show the device (which it previously did) so my assumption is that for some reason it does not want to startup. But maybe that assumption is wrong and I need to switch it to “charger on” and connect then? No clue but my guess is that some dark magic is happening within the Mains Dect but there is alsmot no documentaion around the Mains Dect and erros etc…
Yes I disconnected the BMS and also the Mains Dect. The “chain” actually was:
Quattro → RJ45 - Main Dect → RJ45 → VE.Bus
Initially I always connected my MK3 behind the Main Dect which enabled me to communicate with the device through VE.Config:
Quattro → RJ45 - Main Dect → RJ45 → MK3 → VE.Config
Now since the Quattro stays off I try to connect directly at the Quattro with no more men in the middle:
Quattro → RJ45 → MK3 → VE.Config
With this configuration I can not see the Quattro, but also connecting somewhere “behind” results in the same issue. So my guess is I “somehow” need to get the quattro “up” again but something is preventing it from starting.
You are talking about doing a firmware update again if it failed. But Florian did not yet start the actual firmware update, they only changed and loaded a modified config
just came back from the caravan, so result stays the same:
firmware update was not started, only a configuration changes (remove VE.Bus Assistant) has been pushed to the system, since that the system does not want to startup
so no chance to connect to the device as something is kind of “blocking” it and I assume not that the software Assistant is not around anymore but the power cables between Mains Dect and Quattro are still connected (RJ45 between Quattro and Mains dect disconnected and I am directly plugging into the quattro)
So I somehow need to get rid of that “sleeping” behavior whatever causes that behavior.
One information that I forgot to mention all time: behind the VE-Bus there is a display sitting. The display currently shows blinking E7.
Checked the error code here:
The BMS lockout protection is activated when the external BMS instructs the SBP to switch off sequentially and then switch back on three times (typical behavior during a shutdown caused by low cell voltage).
Once E7 is active, the SBP remains disabled until the input voltage exceeds 13 V (for 12 V systems) or 26 V (for 24 V systems).
Check the BMS error codes/logs to identify the cause of the shutdown and resolve the issue.
Switch off/disconnect loads and recharge the battery.
Check the wiring between the BMS and the SBP remote control terminal.
Verify that the BMS is operating correctly.
———————————-
This still does not help me beacause it simply proves that the BMS is “blocked” which from my point of view is a logical consequence of the VE.Bus Assistan not being around.
But this is my interpretation, any hint will be used.
Tried to connect through VEFlash but result is the same. Following VEFlash instructions step by step but starting firmware update is not possible, see image (Com Port etc is 100% set correctly).
So basically this is the same behaviour I was facing when I tried to update in the past. With the difference that I simply could connect the BMS after the failed attempt and everything came up as expected.
Difference now is that connecting BMS leaves the Quattro dead, guess this is due to the lack of missing VE.Bus Assistant which previously detected that VE.Bus is back and connected.
I simply would need a way to startup the Quattro again, then I would be able to do all kind of gymnastics like reinstalling VE.Bus Assistant etc.
Is there any way of booting a Quattro? This Main Dect seems to be the reason for all that trouble, hopefully someone can help somehow
Open the configuration file you originally pulled from your device, the previous assistant should be there and allow you to export it and reimport it to your new configuration.
ye but this implies that the quattro is “responsive” - the issue right now is that I can not reach the quattro anymore through MK3 (which previously worked), so I do not have any way to playback the original configuration as VEConfig will not let me connect since I removed the VE.Bus Assistant from the Quattro.
So sth inside the quattro prevents it from comin alive again since I removed the VE.Bus Assistant from the configuration.
I am not sure whether I am completely on the wrong track regarding the Main Dect, from my understanding if not connected through RJ45 to the quattro the Main dect should not be the part from preventing the quattro to start. Also I still have enough battery so in case I switch off the AC the inverter still doe not turn on.
