Willkommen! Einloggen - Log In Neuer Benutzer - New User

erweitert

Crashed new Vcontrol Evo+ and New Evo pro V8

geschrieben von volumaxter 
Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 04:41:57
So I have a basically new Goosky RS5 which I was flying with Radiomaster and Rotorflight for 30 flights with no issues. I just received a brand new Vcontrol Evo+ and New Vbar Evo with pro and V8 and on the 3rd flight not too long after take off I notice the tail starts piroutting on its own ending in a crash. On the log I see a Warmstart message. Any idea what can cause this? Again I have flown this bird for 30 flights no issues on another system and now I am afraid to fly it on Vbar.

Goosky Rs5
Hobbywing 150am V5
Xnova 4025-1120kv motor
RV
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 05:59:51
Please add the full logs of the VBar here (copy from cloud), name the SN of VBC and VBar so we can dive into a bit.

Which servos are in use, which frequency is set there?
WHich backup power is used, is there a additional cap installed against reverse voltages?

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 07:47:58
Sounds like a mechanical problem with the tail.

Stephan
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 11:09:31
Hi,

a Warmstart is usually evidence for an issue with the power supply, short interruption, power surge, loose contact.
But it also depends on where in the timeline it appears, could also be a result or aftermath.

I think I found your transmitter and VBar, in our system, but there are no log file entries in the cloud, else I could have looked.

Best,

Eddi

Born to fly ...
forced to work.
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 14:11:33
Hi Eddie, were you not able to find them in the cloud because I have the cloud off?



2 mal bearbeitet. Zuletzt am 16.06.2025 14:16 von volumaxter.
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 14:12:31
Hey Stephan thanks for your response. What makes it sound like a tail mechanical problem? I ask because as I stated in my post I had 30 flights without issues with another system.
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 14:14:13
RV schrieb:
-------------------------------------------------------
> Please add the full logs of the VBar here (copy
> from cloud), name the SN of VBC and VBar so we can
> dive into a bit.
>
> Which servos are in use, which frequency is set
> there?
> WHich backup power is used, is there a additional
> cap installed against reverse voltages?


Thank you Rainer for your response I will answer once I am home. What I find interesting is I am using exactly the same components I was using with a flydragon and never once did I have an issue. I will post once I am home with the radio and helicopter at hand. Thanks
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 15:04:32
You said the heli starts pirueitting on its own.
So maybe here is a mechanical issue. And maxbe the warm start is after that.
But anyway it looks like a tail or a electric power problem.

Stephan
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 15:16:13
Fingolf schrieb:
-------------------------------------------------------
> You said the heli starts pirueitting on its own.
> So maybe here is a mechanical issue. And maxbe the
> warm start is after that.
> But anyway it looks like a tail or a electric
> power problem.
>
> Stephan


But the big question is, why would I have a mechanical/electrical problem that I did not have until I put a Vbar on the helicopter? I said on the 3rd flight the helicopter started pirouetting on its own and crashed. I did not stay it starts pirouetting everytime I fly it, I did have 2 successful flights, maybe I did not explain it well and you thought it is always pirouetting on its own?
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
16.06.2025 15:25:57
You had 2 successfull flights.

Then you got a problem. I don't think it is the vbar.

Stephan
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
17.06.2025 04:25:14
Fingolf schrieb:
-------------------------------------------------------
> You had 2 successfull flights.
>
> Then you got a problem. I don't think it is the
> vbar.
>
> Stephan

I don't think you are reasoning here, but thanks for your help...
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
17.06.2025 04:27:06
Eddi E. aus G. schrieb:
-------------------------------------------------------
> Hi,
>
> a Warmstart is usually evidence for an issue with
> the power supply, short interruption, power surge,
> loose contact.
> But it also depends on where in the timeline it
> appears, could also be a result or aftermath.
>
> I think I found your transmitter and VBar, in our
> system, but there are no log file entries in the
> cloud, else I could have looked.
>
> Best,
>
> Eddi

Hi Eddie, I have activated the cloud on the Vcontrol in case you can check. Thanks
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
17.06.2025 04:41:19
RV schrieb:
-------------------------------------------------------
> Please add the full logs of the VBar here (copy
> from cloud), name the SN of VBC and VBar so we can
> dive into a bit.
>
> Which servos are in use, which frequency is set
> there?
> WHich backup power is used, is there a additional
> cap installed against reverse voltages?

So I dont know how to get the full log from Vbar Cloud but this is it complete from the radio attached. SN of VBC is 11006966 and Vbar is 27007525. I am using AFRC D3625 HB cyclic servos and AFRC D3626 HBH tail servo running at 333Hz 1520us and 500 760us respectively. No backup or additional cap. I have been running this same setup without issues until switching to Vbar and I keep mentioning it because I know that some people that would like to comment will simply say its not a Vbar problem without considering anything else.

Thanks for your help Rainer
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
17.06.2025 04:56:45
Here are the photos of complete log
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
17.06.2025 09:14:03
Hi again,

checking, none of the logs in the cloud now seems to contain the tell tale warm start entry.

One log has static hit, modem chip resynchronization, and packet losses, and the corresponding brief drop in the packet rate in it (in the additional radio link log which is not publicly accessible yet). Evidence that something could be afoot, on the model, and such a hiccup (spark/spike in the electrical system, power supply or signal processing) can technically cause anything, glitches, twitches, spins out of control.
No evidence that it happened then and there, though, but still.

Please check on your transmitter, or in your cloud, and point me to the log which is relevant (by date, time, entries if possible).

About 18 years of experience with VBar, supporting all kinds and generations of hardware, power supplies, helis has it that, most of the time, it's something on the model. And I guess the foremost are electronics issues, that subset lead by power supply issues.
But of course we would never shrug it off that easily, but try and get to the bottom of things.

Flydragon is a different animal, the radio system used, too, mounting location, antenna layout very likely, too, and different control loops put different stress on components (particularly the servos, consumers, and the BEC or power supply in general).

Plus, swapping out components is always a possibility for issues—can be, and don't get me wrong please, I don't want to imply—I had my own share of home grown issues, lessons learned smiling smiley

Lastly, unfortunately, anything can happen. A pinion or a pulley can slip, a servo can fail, a bolt can go AWOL.
On the other hand it's pretty unlikely that the gyro will just hit full rudder.

It's a bit as in forensics, finding out what really caused it, if possible.

Best,

Eddi

Born to fly ...
forced to work.
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
17.06.2025 17:05:18
Eddi E. aus G. schrieb:
-------------------------------------------------------
> Hi again,
>
> checking, none of the logs in the cloud now seems
> to contain the tell tale warm start entry.
>
> One log has static hit, modem chip
> resynchronization, and packet losses, and the
> corresponding brief drop in the packet rate in it
> (in the additional radio link log which is not
> publicly accessible yet). Evidence that something
> could be afoot, on the model, and such a hiccup
> (spark/spike in the electrical system, power
> supply or signal processing) can technically cause
> anything, glitches, twitches, spins out of
> control.
> No evidence that it happened then and there,
> though, but still.
>
> Please check on your transmitter, or in your
> cloud, and point me to the log which is relevant
> (by date, time, entries if possible).
>
> About 18 years of experience with VBar, supporting
> all kinds and generations of hardware, power
> supplies, helis has it that, most of the time,
> it's something on the model. And I guess the
> foremost are electronics issues, that subset lead
> by power supply issues.
> But of course we would never shrug it off that
> easily, but try and get to the bottom of things.
>
> Flydragon is a different animal, the radio system
> used, too, mounting location, antenna layout very
> likely, too, and different control loops put
> different stress on components (particularly the
> servos, consumers, and the BEC or power supply in
> general).
>
> Plus, swapping out components is always a
> possibility for issues—can be, and don't get me
> wrong please, I don't want to imply—I had my own
> share of home grown issues, lessons learned smiling smiley
>
> Lastly, unfortunately, anything can happen. A
> pinion or a pulley can slip, a servo can fail, a
> bolt can go AWOL.
> On the other hand it's pretty unlikely that the
> gyro will just hit full rudder.
>
> It's a bit as in forensics, finding out what
> really caused it, if possible.
>
> Best,
>
> Eddi


The log was the 08.06.2025 19:44:21
I am trying to upload a picture of the log but it is not showing



1 mal bearbeitet. Zuletzt am 17.06.2025 17:06 von volumaxter.


RV
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
17.06.2025 22:01:35
Which radio was used here? - could you name the SN so we can dive into the cloud?

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
18.06.2025 09:13:56
Hi,

this log looks like a normal power on, which you can repeat as often as you like.

Cold start (power on)
Reset reason (power on)—OK
Bank 1—switch position, OK
Calibration finished—OK
ESC detected—OK
All within a reasonable time frame.
Then, Motor On, and that's it.

Problem is, there seem to be gaps in the cloud, or you have used a different transmitter which is possibly not registered to you, or not at all, so no cloud.

Kind regards

Eddi

Born to fly ...
forced to work.



1 mal bearbeitet. Zuletzt am 18.06.2025 09:14 von Eddi E. aus G..
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
19.06.2025 17:05:05
RV schrieb:
-------------------------------------------------------
> Which radio was used here? - could you name the SN
> so we can dive into the cloud?


VBC is 11006966
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
19.06.2025 17:06:50
Eddi E. aus G. schrieb:
-------------------------------------------------------
> Hi,
>
> this log looks like a normal power on, which you
> can repeat as often as you like.
>
> Cold start (power on)
> Reset reason (power on)—OK
> Bank 1—switch position, OK
> Calibration finished—OK
> ESC detected—OK
> All within a reasonable time frame.
> Then, Motor On, and that's it.
>
> Problem is, there seem to be gaps in the cloud, or
> you have used a different transmitter which is
> possibly not registered to you, or not at all, so
> no cloud.
>
> Kind regards
>
> Eddi


Hi Eddie, I only have 1 transmitter. Maybe the gaps are there because I had the Cloud inactive until you asked me to activate it. After my last post I had 4 flights everything was normal. Just 5 minutes ago I went up for another flight and once again the helicopter froze and crashed and looked down into the radio screen to see another Warmstart.
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
19.06.2025 17:13:49
19.06.2025 10:49:37;VBar Start -- RS5 -- 0027007525 -- V 8.1 -- pl 7
19.06.2025 10:49:37 Good;Coldstart
19.06.2025 10:49:37 Good;Reset Reason: Power On
19.06.2025 10:49:37 Good;Bank 1 Loaded
19.06.2025 10:49:39 Warn;Init Failed, retrying...
19.06.2025 10:49:39 Warn;Init Failed, retrying...
19.06.2025 10:49:43 Good;HW ESC detected
19.06.2025 10:49:44 Good;Calibration Finished
19.06.2025 10:50:30 Info;Governor Active
19.06.2025 10:50:30 Good;Motorswitch Motor On
19.06.2025 10:50:45 Info;Raised Vibration Level
19.06.2025 10:50:48 Error;Warmstart
19.06.2025 10:50:48 Good;Reset Reason: Power On
19.06.2025 10:50:48 Good;Bank 1 Loaded
19.06.2025 10:51:50;VBar Logfile End -- 19.06.2025 -- 10:51:50
19.06.2025 10:51:50 Good;HW ESC Disconnected


This was the full log. I was able to fly it with its bend parts after this crash and flew ok for 30 seconds. If anyone can help on where to start to diagnose the issue as I have no idea. I feel like giving up on Vbar even though Ive always been a fan but I cannot believe this is happening on a helicopter that was flying 100% fine with another system.
RV
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
19.06.2025 20:28:23
A Warmstart is a serius issue with the heli and the reason must be searched, probably with the helicopter manufacturers support.

It could be:

- static hit (check ground connection of all pulleys to motor plate)
- reverse voltage from servo (is the small cap coming with HW ESC installed?)
- rc voltage drop (Is there any backup installed?)
- defective motor insulation (check with a insulation tester)

etc.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
Re: Crashed new Vcontrol Evo+ and New Evo pro V8
20.06.2025 09:31:44
Hi,

yes, +1 ...

There's one thing you can do on the ground, to get to see when it happens—seeing is believing: power up, initialize, then—very briefly—cut power and power up again, like, connector out-in. The unit will start flashing pink, indicating a brief power loss, and log a warm start.

Same happens in flight, we must assume, reason yet unknown.
I suspect some electrical issue, and the VBar is just falling victim to it.

In your case, after the warm start, there was even an entry 'reset reason: power on' as when you initially powered up, so the issue was even more severe.
A warm start alone wouldn't cause a crash necessarily, the VBar remains initialized and operational, there's enough power capacity inside to buffer it's own electronics internally, as a precaution for such issues.
But a cold start/reset (sufficiently longer loss of power but in this case still like a loose contact issue, or sparking, or what Rainer wrote) will cause the VBar to initialize mid-flight. Still, it was not dead in the water, kept logging, kept transmitting data back to the transmitter.

—Eddi

Born to fly ...
forced to work.
Sorry, in diesem Forum dürfen nur registrierte Benutzer schreiben.

Hier klicken um Dich einzuloggen- Click here to login