← VBar NEO/EVO VLink

VBar maneuverability in °/s translated

VBar › VBar NEO/EVO VLink · Started by MikeBravo on 26 June 2026 16:2626.06.2026 16:26
MikeBravo 26 June 2026 16:2626.06.2026 16:26
Hello everyone,

A question regarding the conversion or adjustment of the maneuverability/turning rates in VBar (Ulli can probably answer this best).

I want to tune my helicopters (all 700-size helicopters) and the simulator (Heli-X) as similarly as possible, so that both feel comparable at the same RPM.

My target values would be:

Bank 1 (2000 RPM): 305°/s pitch & roll | 565°/s stern

Bank 2 (2200 RPM): 340°/s pitch & roll | 630°/s stern

Bank 3 (2200 RPM): 375°/s pitch & roll | 660°/s tail

My specific question is: What maneuverability setting would I need to choose in VBar to achieve approximately these rotation rates?

I know I could determine this experimentally, for example by filming the helicopter and measuring how long a full rotation takes. Alternatively, I could take my laptop to the field and directly compare the real helicopter with the simulator. But before I go to all that trouble, I thought I'd just ask you guys directly :-)

Thanks in advance.

Regards, Kilian
machine-translated from German · Show original
ulrich 26 June 2026 17:0326.06.2026 17:03
Oh, you won't be able to avoid taking a practical measurement.

The theoretical maneuverability of the TS is exactly 284.3°/s with a maneuverability setting of 100 at full steering deflection. At the tail, this should translate to 410°/s.

Why the odd values? Those were always my default settings. That's why I normalized them to 100.

In practice, however, the values aren't accurate because we're almost always using the direct input. This means the effective rotation rate is higher than the specified value. This is primarily due to the desired control response of the 3D pilot. Furthermore, significant inertial forces also come into play, so the rotation rate doesn't stabilize instantly as it does in the simulator, but rather builds up gradually. Naturally, very high integral (I) values are necessary to maintain consistent rates.

So long... Uli
http://www.vstabi.de
machine-translated from German · Show original
MikeBravo 26 June 2026 17:4226.06.2026 17:42
Hi Uli,

Great, thank you so much for your detailed answer, that helps a lot.

I still have a few questions:

The explanation for the tail rotor rotation rate states: A value of 100
That's roughly equivalent to one pirouette per second, which would actually be 360°/s, right?

Does the maneuverability/turning rate scale linearly (as long as no expo is involved, i.e., 1 point = x°/s)? And is it dependent on the rotational speed?

Could you perhaps give me some rough starting values if I want to aim for the target rates mentioned above? For example, TS maneuverability for ~305/340/375°/s and tail yaw rate for ~565/630/660°/s, just as a "first approximation" before I start actually measuring everything. (The weather will finally be a bit cooler from next week, so we can fly during the day again :-) )

In Heli-X, the rate isn't perfectly constant either, but fluctuates somewhat; the values mentioned are more of an approximate average. My main concern is the rotation rate during constant pirouettes with full control input (e.g., 10 rolls, flips, or pirouettes in a row), once the rotation rate has somewhat "settled," so that the simulator and real helicopters aren't completely different.

Regards, Kilian
machine-translated from German · Show original
Eddi E. aus G. 29 June 2026 09:2929.06.2026 09:29
Good morning,

I think that this could be linear at the sensor (if the value curve 0...100 smoothly covers the rotation rate curve 0...284.3).
Specification, measurement, fits.
Then one could extrapolate from that.

However, since the control loop can only work approximately, positive/negative acceleration takes time, the compensation of torque changes also 'disturbs' (unlike, or even with, constant pirouettes at constant torque), and aerodynamics also plays a role, even a projection will only be an approximation.

The sim has it easy (at first), it can at most rotate the graphics as fast as set, but the entire dynamics have to be programmed in reverse (and that's where it probably gets complicated, more complicated).

And with helicopters outdoors, there is simply a (from helicopter to helicopter) fairly constant physical limit, and even a dynamic one from day to day (temperature, air pressure (alpine pilots know what I mean).

From my point of view, you would have to tune the helicopter outdoors as you want, possibly comparing different models to determine what's possible with the weakest one (which allows the lowest rotation rates before it simply stops working), and then set the sim to simulate that.
Trying to simulate the simulator using reality... interesting approach ^^

I'm curious to hear what you have to report; it will certainly be valuable information for many who also want to optimize their systems!

—Eddi

Born to fly ...
forced to work.



Edited once. Last edited on June 29, 2026 at 9:30 AM by Eddi E. from G.
machine-translated from German · Show original
ulrich 29 June 2026 23:4429.06.2026 23:44
I actually made a mistake with the stern. It should be 393.6°/s. The rates scale linearly, as Eddi says.

So long... Uli
http://www.vstabi.de
machine-translated from German · Show original
HelischuleGonzalez 5 July 2026 17:4905.07.2026 17:49
Proposal No. 8 Minute 30:13

See suggestion no. 8 at 30:13, I would also like to know that.

Since rotation rates can vary completely depending on the blades, helicopter, servo frequency, etc., such an app would be pretty cool :-)
machine-translated from German · Show original
MikeBravo 6 July 2026 14:0106.07.2026 14:01
So, I'll be doing some test flights in the next few weeks and filming the whole thing.

But we have a helicopter meet at the airfield this Saturday in Ermstal, and that takes priority this week :-)



Edited once. Last edited on 06/07/2026 at 14:02 by MikeBravo.
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless