Vbar rescue after tail failure

I will never buy anything with Align written on it after today. Had a really fun day today flying my helis and enjoying my new vcontrol and setup. Everything was flying beautifully all day. I increased the head speed on one of my helis for some light 3D, until the new tail blades I recently fitted on my Freya decided to crack and break off in flight. Which resulted in my old bird spinning aggressively out of control and hitting the ground.

Looking back at the log I see just before the blade failed high vibration alert was detected on the vbar which makes sense as a blade detached which would create massive amounts of vibration.

However i can't understand why looking at the log it stated I used rescue twice during the tail failure..

Ofcourse It's possible I flicked the trigger switch subcontiously but for the life of me I have no memory of me doing that at all during the incident.

My question is..

Is there any situation that the vbar will activate the Rescue function without triggering it? Such as extreme vibration, signal packet loss etc?



1 mal bearbeitet. Zuletzt am 27.07.2023 00:06 von lucasuk86.

Nope, there isn't.

but - using 3rd party radio ... which one is it? Is the FS done by the RX? - iF yes - we won't mention it as the signals to us were still valid. So in this case probably a FS setting to "rescue" in TX could be a reason.

Tell me more ... which radio, how is rescue configured 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.

I'm using vbar neo (non vlink) with vsatelite. Vcontrol transmitter. Rescue is set up using option 3 on the vcontrol.

Hi,

I would lean on the subconscious ... technically, the VBar NEO doesn't do anything on it's own. Only in Fail Safe, it puts the servos on hold and throttle to Off until another signal packet comes in. The reconnect is instantly.
Of course, with a third party receiver which has Fail Safe programmed itself, the NEO won't know about the Fail Safe situation, and do what the receiver outputs, for which it was intentionally or inadvertently programmed.

With VLink, any switch position change is technically a bit or byte transmitted to the VBar NEO, the VBar does what it's supposed to do, queues a log file entry, which is then written a) to the VBar's internal log (ring memory) and b) back to the radio so it will be logged there, too.

Could be of interest to read the log from the unit directly, using the computer software, if there's anything in it which is not in the radio, but I doubt it: only in case of a Fail Safe, logging is (obviously) interrupted, and resumed once the connection comes back (if).

Sometimes when you notice such seemingly random entries, you also see motor switch actuations or bank switches at the same time, which points to the subconcious (or reaction in a stress situation, or just grabbing the radio tightly in a way so you accidentally pull physical SW1 or SW6, the spring loaded ones, or also other switches).

Kind regards

Eddi

Born to fly ...
forced to work.

Thanks Eddie, I'm leaning towards your explanation of me hitting rescue in the stressful situation..

In the log it doesn't say anything about packets lost or fail safe. So would that 100% rule out loss of signal?


26.07.2023 14:36:13 Info;Bank 3 Loaded
26.07.2023 14:36:19 Info;Governor Active
26.07.2023 14:36:19 Good;Motorswitch Motor On
26.07.2023 14:36:19 Info;Raised Vibration Level
26.07.2023 14:36:30 Error;Extreme Vibration Level
26.07.2023 14:36:40 Info;Raised Vibration Level
26.07.2023 14:36:50 Info;Raised Vibration Level
26.07.2023 14:36:58 Info;Rescue Start
26.07.2023 14:36:58 Info;Governor Stop
26.07.2023 14:36:58 Good;Motorswitch Motor Off
26.07.2023 14:36:59 Info;Rescue End
26.07.2023 14:37:00 Warn;High Vibration Level
26.07.2023 14:37:02 Info;Rescue Start
26.07.2023 14:37:03 Error;Elevator Sensor Value out of Range
26.07.2023 14:37:04 Error;Aileron Sensor Value out of Range
26.07.2023 14:37:04 Info;Rescue End
26.07.2023 14:37:05 Info;Rescue Pilot Oversteer
26.07.2023 14:37:10 Info;Raised Vibration Level
26.07.2023 14:37:57;VBar Logfile End -- 26.07.2023 -- 14:37:57

Hi again,

looks like it ...

26.07.2023 14:36:30 Error;Extreme Vibration Level
-> the tail blade went AWOL

26.07.2023 14:36:58 Info;Rescue Start
26.07.2023 14:36:58 Info;Governor Stop
26.07.2023 14:36:58 Good;Motorswitch Motor Off
-> Motor Off and Rescue

26.07.2023 14:36:59 Info;Rescue End
-> Rescue was even ended the normal way, model leveled out (can you confirm?)

26.07.2023 14:37:00 Warn;High Vibration Level
-> close to blade stop, model starts to shake?

26.07.2023 14:37:02 Info;Rescue Start
-> 2nd Rescue

26.07.2023 14:37:03 Error;Elevator Sensor Value out of Range
26.07.2023 14:37:04 Error;Aileron Sensor Value out of Range
-> reverse the adage: the fan hit the sh*t, shock impact

26.07.2023 14:37:04 Info;Rescue End
26.07.2023 14:37:05 Info;Rescue Pilot Oversteer
-> aftermath of Rescue, here it ended by timeout, and you were also probably desperately trying to control the model down, to not much avail :-/

In a tail rotor failure, if you can keep your calm, Rescue can actually still save the model: if the model spins out of control, Rescue can still level it out. So if you manage to descend to an altitude (model spinning, use Rescue multiple times if necessary), where you can switch off the motor and let it float to the ground, if you then switch off the motor the spin will slow down quickly, and you might be able to land without damage (on an even surface), or just with a tip-over (on a surface where the skids might get caught.
Iirc Ulrich recounted that once, just a ball link had popped off, and with Rescue, after landing, he just connected it again and on he went

—Eddi

Born to fly ...
forced to work.

Your story to the time line is exactly what happened lol.

Model did level out on rescue correctly surprisingly as it was spinning so fast. Hats off to the programming

It was my lack of experience and lack of autoroation due to the crash.

However I have learnt a lot from this. The data analysis you get from vbar is paramount and priceless. The support from yourself and Rainer is 10/10.

Thanks for your patience.

(Just to confirm I have also looked at the log directly connecting neo to computer using software and log is exactly the same as vcontrol).

Now onto the next heli



1 mal bearbeitet. Zuletzt am 27.07.2023 09:59 von lucasuk86.

For reference this is the culprit. Found over 50m from crash site. Other blade also done the same. Other sections still attached to blade holders. Complete failure only at 1800 main head speed.

Hi,

ouch ... looks as if there is no carbon fiber or rovings, where they're needed most ... I would expect broken or ripped carbon to look different, with filaments sticking out and such. This looks clean like broken plastic. But of course it's hard to tell from the photos only.

—Eddi

Born to fly ...
forced to work.