← VBar NEO for external transmitters

NEO with futaba translated

VBar › VBar NEO for external transmitters · Started by jean-marc on 7 May 2025 20:1507.05.2025 20:15
jean-marc 7 May 2025 20:1507.05.2025 20:15
Hello everyone
My Neo doesn't power on. It works briefly, and when it ignites, it flashes red very quickly. The tumbler servos twitch up and down for a few seconds, and then it's red. Nothing works. What's causing this? I have a log file. Can someone help me? What do I need to do? Thanks.

machine-translated from German · Show original
RV 7 May 2025 21:5807.05.2025 21:58
Please create a service case for this NEO.

To do this, log in to vstabi.info and navigate to your device list (bottom left). Click on the service icon next to the relevant device.

Please fill out the form (first contact details, then a description of the problem). You can also attach images, logs, etc. If it's a warranty claim, please upload your purchase invoice.

After submitting the form, a confirmation email will be sent automatically.

Our service will then contact you via email as soon as possible.

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.
machine-translated from German · Show original
Eddi E. aus G. 8 May 2025 09:3808.05.2025 09:38
Good morning,

There's an error code 94, the Z-axis is stuck.

In most cases, this is related to vibration/resonance on the model.
This can cause the Z-axis (top/bottom) sensor to temporarily become mechanically stuck/adhere/jammed in its housing.
It resolves itself just as quickly; only if it's still stuck the next time it's switched on will the error message appear.

'Quick Help': in Setup/Swashplate/Rescue ( ) deselect Precision.
This means that the VBar can initialize even with a stuck Z-axis (jammed sensor), so you can fly.
But the rescuer could still lose sight of the horizon over the course of a flight :-/

Background:

The thing about Rescue (for all known systems) is: it has to be able to rely on its accelerometers – blindly.
We need to measure +/- 1 G (gravity) on 3 axes with decimal places to determine the position in a virtual space.

Many current high-performance models cause high-frequency vibrations or resonances that easily exceed 30, 50, 100, 150 G acceleration.

The source is usually the gearbox, not what one would assume (track alignment, balancing, etc.), which only causes comparatively low-frequency vibrations, but can of course also play a role.

Then it becomes very difficult to filter out the useful signal (as if someone were whispering in your ear at a heavy metal concert... even if the person were shouting, it would be difficult to understand the words).

If this condition becomes prevalent, the virtual horizon can only be 'guessed' by coupling (updating values, including the gyros in the calculation), and it can – and will eventually – tip over or flip.

To get to the bottom of this, you can a) use the normal rescue mode: simply leave the screen open, fly, for example, hover every minute (or land for safety), check if the ball returns to the center of the crosshairs (or almost), and if the displayed flight attitude is correct. The rescue will go to where the ball is.

More precisely, b) Vibration Analysis Pro from the Pro/Value Pack, for VBar Control Touch or EVO/+, record the graph there while hovering for 10-15 seconds in all three banks/at all three speeds (to see a baseline level), then fly as usual, e.g. for another half minute or so.

Then land and take a screenshot. That way you can see what's actually happening on the helicopter.

To reduce the effects, one can try to move the installation position away from sources of interference (from motor/gearbox, also from electrical sources of interference, motor, controller, power cable) and/or try different adhesive pads (also doubling up, sandwiching with a metal plate, SAB even had to develop a fastening with rubber dampers...).

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
Eddi E. aus G. 8 May 2025 15:4908.05.2025 15:49
Hi,

Oops, I missed that earlier: Futaba.

This means you can't see it on the broadcast.

But at least one could make an emergency landing there, let the engine run down, or call for help:
If the swashplate goes straight up, OK; if it were to warp -> rescue -> forest :-(

—Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
jean-marc 8 May 2025 19:5908.05.2025 19:59
Hello Rainer and Eddi
Thank you for the quick reply. What I understand is that I have to send the neoprene in. How much will that cost approximately? Otherwise, there's nothing I can do, right? What I don't understand is that I don't have any protection on it.
Regards, Jean-Marc
machine-translated from German · Show original
Eddi E. aus G. 9 May 2025 09:0809.05.2025 09:08
Hi Jean-Marc,

A few questions beforehand: the VBar is from 2018 and is apparently from the first owner; you are the first and only owner.

Has anything unusual happened before?
Did anything not work as expected?
Could this have only started happening after a recent update?

Because... it's actually Express, so no salvation.
But... with version 6.4, the parameter Lightness was added, which also uses the accelerometers.
However, it is not used with Express, cannot be set, and _should_ be set to zero in the background.

However, there were isolated cases where a default value of 35 was incorrectly set in all banks.
I have no idea how or why.
As soon as the parameter has a value > 0, the acceleration sensors are also queried when switching on, then the message can appear.

For verification and possible remedies:
First, open the PC software (VBar is _not yet_ connected, _not yet_ switched on)
Click the graduation cap (expert parameter) on the main rotor.
Now connect the VBar to the computer and turn it on.
The expert menu will remain open.
Now check if the value for Lightness is greater than 0.
. set this to 0 (switch through the banks on the transmitter to check all banks and set them to 0)
Try again.

If it already showed 0... it must be something else.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
jean-marc 9 May 2025 21:1809.05.2025 21:18
Hello Eddie
You guessed right, I opened the expert menu and lo and behold, it showed 35 in all banks. I set them all to 0 and pressed enter for each bank, cycled through them all. Okay, it works again. Do I need to pay attention to anything else, or is it the same as before?
Up until now, there was nothing to the helicopter except for having fun and flying; it's a TDF.
Regards, Jean-Marc
machine-translated from German · Show original
Eddi E. aus G. 12 May 2025 09:4912.05.2025 09:49
Hi Jean-Marc,

Please double-check to be sure that the 8° cyclic and, for example, +/- 12° pitch are correct in the setup, and (immediately after switching on, without controlling roll-pitch, whether 0° pitch (approximately) is also displayed at stick center).

Some people, out of ignorance, have trimmed the swashplate so that it's at 0° in flight mode despite lightness, but without lightness it would be -3° (heavyness instead of lightness ^^).

Lightness gives the feeling that the helicopter is lighter by influencing pitch proportionally and/or via the accelerometers depending on the flight attitude and flight dynamics.

Without this parameter, the model will feel heavier (normal in this case), requiring more stick deflection for the same lift.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
jean-marc 25 September 2025 12:4325.09.2025 12:43
Hello Eddy
Can I do the same thing to my second Neo? It does exactly the same thing: flashing red and twitching, but there's a rescue button on it. When I pull it, the swashplate gets stuck very tightly.
Regards, Jean Marc
machine-translated from German · Show original
Eddi E. aus G. 26 September 2025 09:1726.09.2025 09:17
Hello Jean Marc,

Please check the log (VBar software, menu bar, Info, Event Log) to see what error message is listed there.
The latest entries (Get all entries) can be found at the very bottom.

Red and twitching indicates an error message; the log contains what VBar is trying to tell us.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless