XtaC
11 July 2025 21:0511.07.2025 21:05
Vbackup app shows error since I updated my Vcontrol classic.
It was working fine and showed the status of charge on the main screen this has been replaced by an exclamation mark !
The app shows error and when opened it shows Vbackup overload/undervolt.
The system seems to be working correctly but I am reluctant to fly with any sort of error.
I have unloaded and reloaded all apps without success.
It is the same on all all 4 of my models x3 NEO & EVO so defo not an issue with the VBACKUP / FBL units.
Any help appreciated, I would happily roll back the update if this is an option.
Thanks in advance ????
Eddi E. aus G.
14 July 2025 09:1314.07.2025 09:13
Hi,
I'm curious myself, I'm seemingly not familiar with all the error messages which can come up, yet.
Overload in my book would mean, higher current draw than 40+ amps, undervolt, a lower voltage than ..?
Question is, when in the timeline is the entry actually written, and is there more to see?
Can you retrieve the corresponding log from the transmitter, and post it here?
Best,
Eddi
Born to fly ...
forced to work.
XtaC
14 July 2025 13:3314.07.2025 13:33
Hi Eddi
I have attached x5 logs for two different models, the messages were present at all times on the bench & pre and post flight on the flights.
Nothing seems untowards in the logs but the trasnsmitter was constantly showing an error.
I am now as confused as ever as I have connected both models this morning and I have no error messages the charge status is shown on the user screen and it shows standby and connected when the sticks are active in the application.
The only difference is that when I was testing / flying on the 11th July I was using fully charged batteries and today they are at storage.
I am currently charging a pack to see if the message re-appears with a fully charged battery.
Thankyou for your quick response
XtaC
Eddi E. aus G.
14 July 2025 15:0214.07.2025 15:02
Hi,
well, nothing to see here, or so it seems.
Weird.
Battery charge (of the flight pack, I presume) doesn't matter, the BEC almost always has enough voltage to step down to r/c voltage.
Even at 1 V/cell, where the flight pack would already be dead.
Ghost in a machine ...
Best,
Eddi
Born to fly ...
forced to work.
XtaC
14 July 2025 15:5614.07.2025 15:56
Yes I was referring to the flightpack, not that it should make a difference as FBL power is via CC BEC PRO, but it was the only variable I could think of.
Anyway I can't get it to fail at all today but was failing on all 3 models every time (approx 20 power applications).
I'll keep my eye on it, it's something I check each flight and picking up a new EVO+ soon so should have more control over the Vbackup settings than i currently have with my classic.
Hopefully just a Gremlin that won't show it's head again.
Once again thankyou for your quick response as per usual.
XtaC
ulrich
14 July 2025 18:2214.07.2025 18:22
The "Problem" is, that the Classic lacks the Error Clear button, since it does not support the backchannel.
The Error state is maintained as long as the device has power or the clear command is issued. The Buffer has of course power, even if not actively supporting. So in this case the error goes away if the buffer was fully drained and then powerd up again.
Undervolt can happen if the cap voltage drains too low during being active. So it will happen, if not powerd down properly by the VBar i.e. Overcurrent happens if the output Mosfets get too hot, which happens i.e. on Short circuit. Currents for this to trigger are beyond 60A for a few seconds. So probably the undervolt was the case.
To reset the Error with the VControl Classic, let the cap drain completely. Take care the EVO/NEO is up to date, so it switches the buffer correctly.
so long ... Uli
http://www.vstabi.de