VStabi Pioneer of Flybarless

After the first few flights, it would be a good idea to look at the logged data on the VBar Control or in the cloud. Our main concern is to use the logs to identify basic errors.

For example, we recently had a pilot in support whose (never viewed) logs were full of low-voltage warnings for the VBar and turbine. The actual reason for his call was a turbine telemetry that kept "dropping out". When we looked through the logs, it became clear to us that this helicopter would almost certainly have had a more serious problem in the next three flights. But - everything was identified, fixed and safe. That's how it should be.

So pay attention to low-voltage warnings in the VBar logs. If we have a helicopter with VBar telemetry, we can set the thresholds ourselves in the respective controller or turbine app.

If we don't have that or the RC voltage is not shown in the respective app with an alarm for setting, there is a separate RC voltage monitor app for the VBar Control.

In addition to the voltage entries, we pay attention to vibrations in flight. Here - assuming good stabilization as intended - there shouldn't be much to see with the scaler. Now and then, depending on the control system, maybe an entry - but not often. Please not when landing - that is occasionally normal.

Temperature warnings from the controller or turbine round off the field of observation.

Anyone who has an electric heli with a VBar Governor can even use the graphic logs and the controller opening to determine whether their drive design matches the desired speed. The aim would be to use around 85% opening when hovering and the battery is almost empty. This way you are not too much at partial load at the beginning of the flight and still have reserves at the end if necessary.