← VBar NEO for external transmitters

crash - neo blinking red translated

VBar › VBar NEO for external transmitters · Started by ReadyToFly on 25 February 2016 22:2025.02.2016 22:20
ReadyToFly 25 February 2016 22:2025.02.2016 22:20
hey guys,
i was flying today when the heli lost control and crashed even after turning rescue on.
now, on the bench, neo won't initialize and keeps blinking red.
manual says the receiver "isn't configured".
i recently started using a vcontrol. i bound vlink successfully to it and flew 5 flights or so w/o any issues. not today.
i've just noticed i hadn't changed the receiver type to vcontrol on the pc software. it was still set to my older futaba sbus receiver. despite of that, i had flown the w/o any problem.

what does vlink blinking red mean and how to fix it, please?

thanks.
ReadyToFly 26 February 2016 00:0026.02.2016 00:00
hey guys,

it seems a flashing red led doesn't mean receiver configuration issues, at all. it seems it is something way more serious.

finally neo now is solid green again. i didn't do anything for it to happen. it just decided to come back to green just how it had decided to flash red.

on vcontrol i can see the log file of the crash, but i can't save it via the pc software. on the pc software the only log that i can see and save is the one attached.

i had many flights with this neo w/o any issue. only a few flights after using vcontrol it happened. is this neo still reliable?

one thing i noticed during the crash is the motor rpm almost coming to a stop. rescue also didn't work as expected and barely was able to flip the heli to its normal position.

was the problem caused because i failed to set the receiver type to vcontrol on the pc software? if so, how was i able to bind vcontrol and fly at least 5 times w/o any issue?

thanks.



2 mal bearbeitet. Zuletzt am 26.02.2016 00:05 von ReadyToFly. Dateianhänge:
öffnen | Download - vbar neo log.pdf (137.3 KB)
öffnen | Download - log-20001861-Feb-25--2016-7-07-01-PM - Notepad.pdf (15.6 KB)
Eddi E. aus G. 26 February 2016 08:2826.02.2016 08:28
Hi RTF,

I hate to say it but it seems like the IMU sensors failed. This is the gyro- and first level accelerometer sensor array.
But even then, the VBar should have fallen back to emergency mode, the heli still being controllable but without stabilization (harder to control of course, and at the wrong moment ...).

Red-green flashes if _no_ receiver is configured/connected. You can always connect a VBar Control Satellite to a NEO and bind, and it will work right away, even if a different receiver type is selected. This is a feature and does not affect safety or flying.

There's just one situation where it could or would, in case you set up throttle so it is controlled directly from the other radio, by re-routing throttle through AUX3. VBar NEO with VBar Control always assumes the NEO is set up properly (head speed requests or throttle percentages set for each bank, ESC connected to the port ESC).

Red means there is something seriously wrong. If it initializes now again green, please do no longer use this VBar, it's simply unsafe and could fail any time again.

Please open a service case here www.vstabi.info/service or create an RMA with your dealer, we should have that NEO back and replace it, and transfer your Pro+Rescue license to the new device.

Kind regards

Eddi

Born to fly ...
forced to work.
ReadyToFly 26 February 2016 13:0426.02.2016 13:04
hello eddi,
did you receive my PM?
i'm having a hard time here with my browser today.
thanks.
VStabi VStabi Pioneer of Flybarless