Neo reset in flight

I was flying my Synergy 556 today, and at the end of an auto right when I flared I lost all control and it crashed. I was less than a meter from the ground when it happened, so it was pretty much instant. It killed the engine, and right after it hit I heard the Vcontrol reconnect. Here is the log:

VBar Start -- Synergy 556 -- 09.09.2018 -- 16:21:12
16:21:12;1;Reset Reason: Power On
16:21:13;2;Bank 1 Loaded
16:21:14;2;Bank 4 Loaded
16:21:14;1;Motorswitch Motor Off
16:21:14;1;Motorswitch Idle Bailout
16:21:18;2;Calibration Finished
16:24:28;3;The Cyclic Ring is active
16:24:28;3;The Cyclic Ring is active
16:24:29;3;The Cyclic Ring is active
16:24:29;3;The Cyclic Ring is active
16:24:30;3;The Cyclic Ring is active
16:24:31;3;The Cyclic Ring is active
16:24:31;3;The Cyclic Ring is active
16:24:32;3;The Cyclic Ring is active
16:24:47;2;Governor Active
16:24:47;1;Motorswitch Motor On
16:25:01;3;High Vibration Level
16:25:08;2;Bank 2 Loaded
16:26:13;2;Bank 1 Loaded
16:29:35;2;Raised Vibration Level
16:31:17;2;Bank 4 Loaded
16:31:17;2;Governor Idle
16:31:17;1;Motorswitch Idle Bailout
16:31:21;2;Governor Stop
16:31:21;1;Motorswitch Motor Off
16:31:25;1;Motorswitch Idle Bailout
16:31:26;2;Bank 1 Loaded
16:31:26;2;Governor Active
16:31:26;1;Motorswitch Motor On
16:31:26;3;High Vibration Level
16:31:36;2;Raised Vibration Level
16:31:46;2;Raised Vibration Level
16:31:49;2;Governor Idle
16:31:49;1;Motorswitch Idle Bailout
16:31:49;2;Bank 4 Loaded
16:31:57;3;Reset Reason: Watchdog
16:31:57;2;Bank 1 Loaded
16:31:57;2;Bank 4 Loaded
16:31:57;4;Aileron Sensor Value out of Range
16:31:58;1;Motorswitch Motor Off
16:31:58;1;Motorswitch Idle Bailout
16:31:58;3;Init Failed, retrying...
16:32:01;1;Motorswitch Motor Off
16:32:01;2;Bank 1 Loaded
16:32:02;2;Calibration Finished
16:32:22;2;Raised Vibration Level
16:32:46;3;RC Voltage: 6.82V
16:34:23;3;RC Voltage: 6.82V
VBar Logfile End -- 09.09.2018 -- 16:34:25

I'm guessing it's right there at Reset Reason: Watchdog. This is a Neo that I purchased new in July and upgraded to Pro Rescue. This is a heli that I use to train my son with using a single Spektrum satellite and crossover buddy boxing. At the end of July the heli did the same thing in my N5C. I blamed it on my own thumbs and didn't check the log, and unfortunately I don't have that log anymore.

So does anyone have any ideas? I have 8 Vlink Neos in use, and this is the only one where I am using a Spektrum satellite for crossover buddy boxing. It has probably 100 flights out of the 500 or so that I've put on all of my Neos with my Vcontrol, and it is the only one that has had any issues, and the 2 times it was during a flight where I was training my son.

I won't be doing the crossover buddy boxing much longer, at some point my Vcontrol Touch will ship. I'd like to know that this Neo is safe to keep using though.

Just as a followup, I plugged the Neo into my computer and ran Vbar COntrol Manager and it updated itself. This is the log from that.

VBar Device found at Path: G:\
VBar Device connected Serial: 20015507
Version: 6.3.60
Updating: (Firmware Pl:61) updating...
Updating (Firmware) OK
VBar Device disconnected.
VBar Device connected Serial: 20015507
Version: 6.3.61
vbar_rescue_VL -- VBar Professional Rescue 6.3 Firmware - is current
VBar Device disconnected.

Hi,

the watchdog entry is raised if the VBar's self-monitoring detects a glitch or lock-up and instantly reboots, without re-initializing the sensors.
There is no obvious reason for it in the log, though.
I could imagine that you notice a brief hold, then 'life goes on'.

I guess it was the wrong time :-/ ... and it's a very rare entry anyway.

The update afaik is the one which adds VBar Control Touch OTA update functionality, nothing more. There was or is no safety relevant update, so I am pretty sure it has nothing to do with the incident.

But a watchdog entry makes me keen-eared ... I would at least check the wiring, connectors, probably disconnect the Spektrum satellite for the time being/next tests. I would also check the saved event logs for that model/VBar for similar entries, which could have gone unnoticed – if the logs were still there :-/
On the N5C, were there any of the components which are now on the Synergy 556, apart from the NEO?
Was the unit harmed in the first incident?

If in doubt, better send in the unit for a check-up, don't risk anything.

Kind regards

Eddi

Born to fly ...
forced to work.

It definitely happened at exactly the worst moment. I had just flared so it still had negative pitch and the tail was just off the ground. That split second where I needed to feed positive did me in.

Everything is the same as my N5C. Right now I’m operating on the thought that it is related to the satellite being used for buddy boxing since both times I’ve had something similar I was using that and it’s fairly rare that I buddy box on this heli. I’ve pulled the satellite off and will wait for my Touch to come in before training my son on it again. I’ll keep an eye on the logs and see if that message shows up again. If it does I’ll send it in.