V-Control Switches & Lost Power - Crash
Posted by 3D Dave
|
May 19, 2021 04:09AM |
|
May 19, 2021 04:17AM |
I changed the switch positions on the top right back when the TX was new (2015)
Here's a pic of my V-Control showing the switch positions and assignments for the last 6 years.
Here's a pic of my V-Control showing the switch positions and assignments for the last 6 years.
|
May 19, 2021 09:11AM |
Hi Dave,
sorry to hear.
About the vibration warnings, they are not critical _if_ it doesn't affect flight (like drift on one or more axis).
They are measured at the gyros as always, and they cover a frequency range of 0...500 Hz (0...30,000 1/min 'shaft rpm', whatever is spinning at that speed, this is also what you see in the graphic vibration analysis).
Vibration doesn't cause a power loss, unless it causes wires to chafe/get harmed, or connectors to disconnect.
In the last log, there is no evidence for a motor-off from the VBar (switch action) or a loss of radio link and subsequent fail safe.
Means, the VBar was constantly outputting a throttle signal to the ESC.
Also, no low voltage warnings, no warm start, so the power supply was good all the time.
The conclusion can only be, there was something else going on or going wrong, ESC disconnected, wire harmed and a short circuit, a glitch on the ESC's signal line, or the ESC simply quitting on you. I mean, it sounds threadbare, but the sky is blue, the water is wet, ESCs sometimes just quit on you.
Still I would check the NEO's ESC signal output, with home tools, connect a servo, wiggle/press/squeeze and see if it goes limp or acts erratic, with an oscillocope, also check the voltages and signal, if they drop.
What comes then substantiates this:
You hit Rescue, the VBar tries to upright the model, but it can't, has not much authority left, with the quickly dropping head speed.
Tell tales are the cyclic ring entries, means, the VBar outputs full cyclic and runs into it's own internal electronic limits, because the model doesn't come around.
Then, like a leave in the wind, then the the impact, sensors out of range, you switch off the motor, and already on the ground, 4 secs (of timeout) later, the VBar ends the Rescue because it was not able to upright the model, and it even 'rats you out'
that you tried to help, that you were working the sticks at that time, too.
In my opinion, and per the log, all your switch operations came through—I mean, the log entries are generated by the VBar NEO and are subsequently Morsed back, it's not the radio just writing it and maybe not sending it. If there's a log entry, it happened _on the model_, if there isn't, there was no situation to raise the alarm.
I can not tell about the other incidents, but honestly, hardly any two are the same, even if it always looks the same: oops, drop, crash, sh*t.
That's my interpretation, and with that, I would pretty much rule out the NEO and almost absolutely rule out the radio.
So ... motor, wiring, ESC, wiring, connectors, insulation, load of the ESC during that flight ... if the ESC has internal logging, that could help.
If there was a U/I Log, that could help. Both could e.g. show that there was a PWM signal to the ESC all the time, but that it quit anyways, or they could even have warnings, like over current, over temperature, whatever there is.
Or, even simpler, something just let go in the power train, pinion, a set screw, the one way bearing.
—Eddi
Born to fly ...
forced to work.
sorry to hear.
About the vibration warnings, they are not critical _if_ it doesn't affect flight (like drift on one or more axis).
They are measured at the gyros as always, and they cover a frequency range of 0...500 Hz (0...30,000 1/min 'shaft rpm', whatever is spinning at that speed, this is also what you see in the graphic vibration analysis).
Vibration doesn't cause a power loss, unless it causes wires to chafe/get harmed, or connectors to disconnect.
In the last log, there is no evidence for a motor-off from the VBar (switch action) or a loss of radio link and subsequent fail safe.
Means, the VBar was constantly outputting a throttle signal to the ESC.
Also, no low voltage warnings, no warm start, so the power supply was good all the time.
The conclusion can only be, there was something else going on or going wrong, ESC disconnected, wire harmed and a short circuit, a glitch on the ESC's signal line, or the ESC simply quitting on you. I mean, it sounds threadbare, but the sky is blue, the water is wet, ESCs sometimes just quit on you.
Still I would check the NEO's ESC signal output, with home tools, connect a servo, wiggle/press/squeeze and see if it goes limp or acts erratic, with an oscillocope, also check the voltages and signal, if they drop.
What comes then substantiates this:
You hit Rescue, the VBar tries to upright the model, but it can't, has not much authority left, with the quickly dropping head speed.
Tell tales are the cyclic ring entries, means, the VBar outputs full cyclic and runs into it's own internal electronic limits, because the model doesn't come around.
Then, like a leave in the wind, then the the impact, sensors out of range, you switch off the motor, and already on the ground, 4 secs (of timeout) later, the VBar ends the Rescue because it was not able to upright the model, and it even 'rats you out'
that you tried to help, that you were working the sticks at that time, too.
In my opinion, and per the log, all your switch operations came through—I mean, the log entries are generated by the VBar NEO and are subsequently Morsed back, it's not the radio just writing it and maybe not sending it. If there's a log entry, it happened _on the model_, if there isn't, there was no situation to raise the alarm.
I can not tell about the other incidents, but honestly, hardly any two are the same, even if it always looks the same: oops, drop, crash, sh*t.
That's my interpretation, and with that, I would pretty much rule out the NEO and almost absolutely rule out the radio.
So ... motor, wiring, ESC, wiring, connectors, insulation, load of the ESC during that flight ... if the ESC has internal logging, that could help.
If there was a U/I Log, that could help. Both could e.g. show that there was a PWM signal to the ESC all the time, but that it quit anyways, or they could even have warnings, like over current, over temperature, whatever there is.
Or, even simpler, something just let go in the power train, pinion, a set screw, the one way bearing.
—Eddi
Born to fly ...
forced to work.
|
May 19, 2021 04:45PM |
|
May 19, 2021 04:51PM |
|
May 31, 2021 05:55AM |
|
May 31, 2021 09:45AM |
|
May 31, 2021 10:29PM |
Sorry, only registered users may post in this forum.