Cannot Calibrate Rescue with V6.4.65

Hello;
I successfully updated my VBar Neo to the latest version of 6.4.65. All went smoothly on both my helicopters. I have gone over all the parameters and verified everything.
But when I went to calibrate Rescue on one of helicopters, the calibration failed. My radio reported the following error, "Calibration failed! Check sensor orientation and level model". I performed this calibration on a level workbench, the same workbench as my other model. I simply cannot perform a calibration. Yes, I have the Rescue set to "Standard" precision, just like before.
Any ideas to solve this would be appreciated.
Thank you!

/Hal

The calibration may require a precise init - so could you try this?

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 did. Tried setting to Precision. Same error. Then switched back to Standard; same error. Have no idea what's going on.

Is there any entry in the event log which could be helpful?

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.

Here is the log from my last attempt:

13.09.2020 15:10:23;VStabi Start -- Kraken 700
13.09.2020 15:10:25 Good;Scorpion ESC detected
13.09.2020 15:10:26 Good;Reset Reason: Power On
13.09.2020 15:10:26 Info;Bank 2 Loaded
13.09.2020 15:10:27 Info;Bank 3 Loaded
13.09.2020 15:10:27 Warn;IMU Sensor Z Axis hangs
13.09.2020 15:10:27 Good;Motorswitch Motor Off
13.09.2020 15:10:27 Good;Motorswitch Idle Bailout
13.09.2020 15:10:27 Warn;Init Failed, retrying...
13.09.2020 15:10:29 Info;Calibration Finished
13.09.2020 15:10:29 Info;Initializing with virtual Z Axis
13.09.2020 15:10:32 Good;/battery/bt_2
13.09.2020 15:10:32 Good;Battery selected manually: 12S-S1
13.09.2020 15:10:33 Warn;Battery not fully charged! Full: 50.4V Curr: 46.3V
13.09.2020 15:10:48 Error;Horizontal calibration error
13.09.2020 15:11:08 Error;Horizontal calibration error
13.09.2020 15:11:57 Error;Horizontal calibration error
13.09.2020 15:12:12 Error;Horizontal calibration error
13.09.2020 15:12:57 Error;Horizontal calibration error
13.09.2020 15:13:26 Error;Horizontal calibration error
13.09.2020 15:13:49 Error;Horizontal calibration error
13.09.2020 15:13:56 Error;Horizontal calibration error
13.09.2020 15:16:18 Error;Horizontal calibration error
13.09.2020 15:16:25 Error;Horizontal calibration error
13.09.2020 15:17:21 Error;Horizontal calibration error
13.09.2020 15:17:29 Error;Horizontal calibration error
13.09.2020 15:17:36 Error;Horizontal calibration error
13.09.2020 15:17:59 Warn;Scorpion BEC Voltage: 7.60V
13.09.2020 15:18:05;VBar Logfile End -- 13.09.2020 -- 15:18:05

/Hal

Hi,

13.09.2020 15:10:23;VStabi Start -- Kraken 700

Kraken – somewhat renowned for it's vibration levels.

13.09.2020 15:10:25 Good;Scorpion ESC detected 
13.09.2020 15:10:26 Good;Reset Reason: Power On 
13.09.2020 15:10:26 Info;Bank 2 Loaded 
13.09.2020 15:10:27 Info;Bank 3 Loaded 
13.09.2020 15:10:27 Warn;IMU Sensor Z Axis hangs

Vibration caused the z-axis sensor (up/down) of IMU to mechanically stick or hang, in the flight before.
A tap to the NEO will probably release it (then: power-cycle), or vibration on the next flight will release it (or make it stick again, it happens on and off).

13.09.2020 15:10:27 Good;Motorswitch Motor Off 
13.09.2020 15:10:27 Good;Motorswitch Idle Bailout 
13.09.2020 15:10:27 Warn;Init Failed, retrying... 
13.09.2020 15:10:29 Info;Calibration Finished 
13.09.2020 15:10:29 Info;Initializing with virtual Z Axis

Initialization happened anyway because Standard is selected, allows the VBar to decide a) all well, Precision or b) z-axis hangs, calculate the horizon with a virtual z-axis.

But in this state, calibration is not allowed, because calibrating (hard-coding) the horizontal position with a sensor which is not delivering useful data at he moment would be no good, or more clearly, dangerous.

But it's not necessary to calibrate the horizon, not in the beginning, not every so often.

If Rescue goes anywhere, it's most likely because of the ongoing vibration on the model, not because the horizontal calibration becomes faulty, or because of a faulty sensor.

On the Kraken, SAB has done all they can to keep away vibration from the flybarless unit and it's sensors (no matter which brand), with Option 3 FBL mount, drift effects at ridiculously high RPM are in check (no guarantee, though), and with Option 4 with the rubber dampening, Rescue issues have been mostly resolved (but also, no guarantee, and only scarce customer feedback anyway).

Kind regards

Eddi

Born to fly ...
forced to work.

Okay. I think I understand.

I'll try tapping the Neo to release the Z-axis sensor. Hopefully, that works. I'll keep an eye on it.

What happens if it doesn't get released? Will the Neo need repair?

/Hal

Hi,

well,

Quote:

me
Initialization happens anyway if Standard is selected, this allows the VBar to decide a) all well, Precision or b) z-axis hangs, calculate the horizon with a virtual z-axis.

So leave it at Standard but please mind that there's something going on which _could_ cause Rescue to go the wrong way.

The VBar NEO, to the best of our knowledge for five years now, does not take damage/is not damaged, so sending in won't help.
In the beginning, we replaced NEOs by the dozen, because we didn't know yet, but we learned that the same thing will happen again on the same helicopter, because the source/cause of the issues is still there.

Kind regards

Eddi

Born to fly ...
forced to work.

Understood. I will look in to the other FBL mounts for the machine if this continues to be an issue.
I tapped the Neo a few times, and now all is well.
Thanks for the assistance.

/Hal