VBar Neo Initilization Problem

Hi

I just installed this Neo. It flew good and then there is a warning on my VControl. Init Problem check logs. This is on my Diabolo 550. MKS 9767 Servos, MKS 9780 tail servo, XNova 4020-1000 motor, scorpion tribunus esc, internal bec at 7.3 volts, running vbar governor, revolectrix 4400 6s battery. The heli has continuity from motor mount through to tail case.

This log is from the flight today.

VBar Start -- Diabolo550 -- 28.05.2017 -- 13:52:53
13:52:53;1;Reset Reason: Power On
13:52:54;2;Bank 2 Loaded
13:52:54;1;Motorswitch Motor Off
13:52:54;1;Motorswitch Idle Bailout
13:52:57;1;Batt sel manually: 44006S
13:52:57;2;Calibration Finished
13:55:15;2;Bank 1 Loaded
13:55:27;2;Governor Active
13:55:27;1;Motorswitch Motor On
13:55:39;2;Raised Vibration Level
13:55:44;2;Bank 2 Loaded
13:55:50;2;Raised Vibration Level
13:56:00;2;Raised Vibration Level
13:56:10;2;Raised Vibration Level
13:56:30;3;IMU Sensor Z Axis hangs
13:56:30;2;Raised Vibration Level
13:56:40;2;Raised Vibration Level
13:57:11;2;Raised Vibration Level
13:57:21;2;Raised Vibration Level
13:57:31;2;Raised Vibration Level
13:57:41;2;Raised Vibration Level
13:57:42;2;IMU Sensor Z Axis released
13:57:51;2;Raised Vibration Level
13:57:52;3;IMU Sensor Z Axis hangs
13:58:01;2;Raised Vibration Level
13:58:11;2;Raised Vibration Level
13:58:22;2;Raised Vibration Level
13:58:32;2;Raised Vibration Level
13:58:42;3;High Vibration Level
13:58:52;2;Raised Vibration Level
13:59:02;2;Raised Vibration Level
13:59:12;2;Raised Vibration Level
13:59:32;2;Raised Vibration Level
13:59:43;2;Raised Vibration Level
13:59:53;2;Raised Vibration Level
14:00:03;2;Raised Vibration Level
14:00:13;2;Raised Vibration Level
14:00:20;2;IMU Sensor Z Axis released
14:00:23;2;Raised Vibration Level
14:00:24;3;IMU Sensor Z Axis hangs
14:00:33;3;High Vibration Level
14:00:43;2;Raised Vibration Level
14:00:54;2;Raised Vibration Level
14:01:04;2;Raised Vibration Level
14:01:05;2;IMU Sensor Z Axis released
14:01:10;3;IMU Sensor Z Axis hangs
14:01:13;2;IMU Sensor Z Axis released
14:01:14;2;Raised Vibration Level
14:01:15;3;IMU Sensor Z Axis hangs
14:01:24;2;Raised Vibration Level
14:01:53;2;Governor Idle
14:01:53;1;Motorswitch Idle Bailout
14:01:53;2;ESC - Umin:21.3V Imax:81.8A Temp:52°
14:01:53;2;Governor Stop
14:01:53;1;Motorswitch Motor Off
14:01:54;2;Raised Vibration Level
VBar Logfile End -- 28.05.2017 -- 14:03:15


Then this log when it would not init.

VBar Start -- Diabolo550 -- 28.05.2017 -- 14:55:48
14:55:49;1;Reset Reason: Power On
14:55:50;2;Bank 1 Loaded
14:55:50;2;Bank 2 Loaded
14:55:50;3;IMU Sensor Z Axis hangs
14:55:50;1;Motorswitch Motor Off
14:55:50;1;Motorswitch Idle Bailout
14:55:53;2;Calibration Finished
14:55:53;4;IMU Sensor fail
VBar Logfile End -- 28.05.2017 -- 14:56:03


another log

VBar Start -- Diabolo550 -- 28.05.2017 -- 14:56:18
14:56:18;1;Reset Reason: Power On
14:56:19;2;Bank 1 Loaded
14:56:19;2;Bank 2 Loaded
14:56:19;3;IMU Sensor Z Axis hangs
14:56:19;1;Motorswitch Motor Off
14:56:20;1;Motorswitch Idle Bailout
14:56:22;2;Calibration Finished
14:56:22;4;IMU Sensor fail
VBar Logfile End -- 28.05.2017 -- 14:56:32


VBar Start -- Diabolo550 -- 28.05.2017 -- 14:57:15
14:57:16;1;Reset Reason: Power On
14:57:16;2;Bank 1 Loaded
14:57:17;2;Bank 2 Loaded
14:57:17;3;IMU Sensor Z Axis hangs
14:57:17;1;Motorswitch Motor Off
14:57:17;1;Motorswitch Idle Bailout
14:57:20;2;Calibration Finished
14:57:20;4;IMU Sensor fail
VBar Logfile End -- 28.05.2017 -- 14:58:10

VBar Start -- Diabolo550 -- 28.05.2017 -- 15:00:28
15:00:29;1;Reset Reason: Power On
15:00:29;2;Bank 1 Loaded
15:00:29;2;Bank 2 Loaded
15:00:29;3;IMU Sensor Z Axis hangs
15:00:30;1;Motorswitch Motor Off
15:00:30;1;Motorswitch Idle Bailout
15:00:32;2;Calibration Finished
15:00:32;4;IMU Sensor fail
VBar Logfile End -- 28.05.2017 -- 15:00:43

Not sure the reason please help.

Thank you, Ken

Quote:

this is a issue based on some helicopters (especially TDR2 with a very stiff frame) and thier microvibrations. They can't be monitored - and can't be dampened in a known way.

We have tested this effect extensively on a TDR2 - and it was nothing that could be solved permanantely (i talk about 200 flights in each variation, i have a local buddy here who did all the extensive testing on this heli) when using another NEO, dampening or mounting position. It resists with the heli and its mechanical things like gear, bearings, motor, stiffnes of the frame, tail drive, dampenings etc.

So - unfortunately we can't do anything to solve the initial trigger effect, just watch the sensor and if it hangs - give a message. The 15g z-axis sensor is driven to its end due those microvibs and stucks there. It could possibly also release again in next flight or ground handling as it is mechanical.

So - what we do - and why we can (and others not):

We have 9 sensors inside the NEO - 3 rate sensors as for all VBars already for flight control, then 3 accelerometers with 15g range, then 3 accelerometers with 200g range.

The 15g accelerometers have a factory calibration and are used during power up to calibrate the 200g ones which have no factory calibration. Both sets are used in flight to align the "virtual rescue model" together with the rate sensors (they are mainly used but have always a bit drift) from time to time when flying will permit this.

Now - knowing that a heli has some vibrations in flight - we measured them and found that even a Logo with plastic frame has 13g, a 600 nitro has 43g, a gasser up to 85g vibrations. So we have the 200g sensors in use in flight and fade over to them when the heli starts as the 15g were at the end of their measuring range.

So - if the high range sensors are once calibrated during power up - the rescue is safe.

And here we started to work. We added a "standard initialization" to the rescue panel which gives us the possibility to decide on power up based on a hanging 15g z-Axis sensor. If it hangs - we calculate the z-Value out of x and y (which is very close to a measured result, no noticeable difference in flight when using rescue) - and calibrate the 200g with this result. The swash will bump 3 times then as info for the pilot. If it does not hang - it will do the usual init and bumps 1 time as known.

The only disadvantage now is - you can't turn on the heli more than 45 deg (!!!) off from its "skids down" levelled position - but this won't care 99,999999% of all pilots as we think.

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.

So please check out the standard init - and retry:

http://vstabi.info/en/node/1930

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.

Hi Rainer

Thank you !! I set it for standard initialization and it did initialize.

Thank you, Ken