← VBar Control Touch / EVO

RTF models on VBar Control touch/EVO translated

VBar Control › VBar Control Touch / EVO · Started by thomas1130 on 22 November 2025 08:2122.11.2025 08:21
thomas1130 22 November 2025 08:2122.11.2025 08:21
First of all - THANK YOU Rainer for the finished macrocell setup for RTF models - it really makes life noticeably easier :-)

I do have one question about that, though:

What effect does the parameter "maneuverability" have?

Does this affect the overall cost of the tax route? - so less, approximately 100?

Exposure is clear - this can be set in the transmitter or in the external FBL (better not in both at the same time).

Thanks!

Best regards,
Thomas
machine-translated from German · Show original
RV 22 November 2025 10:0422.11.2025 10:04
That's right. Basically dual rate or something like that.

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
thomas1130 22 November 2025 12:3322.11.2025 12:33
Thanks - all clear :-)

LG
machine-translated from German · Show original
thomas1130 23 November 2025 08:4123.11.2025 08:41
Additional question:

According to the OMP "VBC-Manual", it is recommended to always leave the maneuverability at 65 - as this is the only way to utilize the entire range of motion - and higher values can lead to "clipping".

That applies at least to "their version" of the macrocells - I don't know if yours differ (apart from the numbering)?

Initial hovering tests with an OMP M2 V3 (with OFS3) with a maneuverability of approximately 90 resulted in an extremely "unpleasant" and very toxic feeling - especially on pitch.

Are the OMP macro cells programmed differently than yours - or can the recommendation with agility 65 also be used with your presets?

I simply want a linear output that utilizes the path linearly from -100 to +100.

(Or can I find some kind of "servo monitor" somewhere on the VBC - where I can see the output visually?)

Thanks!

Best regards,
Thomas



Edited once. Last edited on 24/11/2025 at 18:42 by thomas1130.
machine-translated from German · Show original
RV 23 November 2025 10:0323.11.2025 10:03
There was indeed a change to their flight control.

In the channel output cells for the affected functions, simply set the paths and endpoints to 65 (all 4 per channel).

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
VStabi VStabi Pioneer of Flybarless