← VBar NEO/EVO VLink

Swashplate type with twisting translated

VBar › VBar NEO/EVO VLink · Started by TomD on 14 September 2025 12:5714.09.2025 12:57
TomD 14 September 2025 12:5714.09.2025 12:57
Hello everyone,

I've noticed that the pitch servo always responds when I only send a roll input. Here's a video of it.

https://www.youtube.com/shorts/Sv7cktsTFTo

It's only a minimal difference, but it shouldn't be happening. The setting is TS type HR-3 (120 degrees), see photo.
You can also rotate the TS (Turbo Shaft) now, of course. I did that too. The type then showed "User Defined." One click to the left corrected this. The pitch servo then remained stable. But it's no longer a standard HR-3 with 120 degrees.

I also spoke to a friend about this who runs a helicopter school in Munich. He'd noticed it too. Specifically, that in a certain head position, the rotor blades move slightly with just a roll input. After correcting this by twisting the controls, it was fixed. But in flight, the handling was somehow slightly worse than before.

Therefore, I think that Mikado had something in mind and that it's perhaps normal for Nick to go along with it slightly.
But I would really like to understand why that is.

Thanks and regards
Thomas



Edited once. Last edited on 14.09.2025 at 12:58 by TomD.

machine-translated from German · Show original
RV 14 September 2025 20:1014.09.2025 20:10
Ask:

If you disconnect the pitch servo linkage, does the arm still move?

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
TomD 15 September 2025 07:5615.09.2025 07:56
Hello Rainer,

Yes, even if I disconnect the linkage, the servo arm still moves.

greeting
Thomas
machine-translated from German · Show original
Eddi E. aus G. 15 September 2025 09:5115.09.2025 09:51
Good morning,

V7 or V8.

Completely new setup, or a copied/foreign/V8-updated one?
Are all benches the same?

I'm thinking of the phasing parameter from V7, which allowed you to set an additional twist per bank.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
TomD 15 September 2025 10:0515.09.2025 10:05
Hi Eddi,

Completely new setup in the V8. Same in all banks. Also available in the setup menu.

greeting
Thomas
machine-translated from German · Show original
Eddi E. aus G. 15 September 2025 12:0615.09.2025 12:06
Hmm, strange.

Please save the setup on your transmitter and let it write it to the cloud.
Then we can download it, copy it to a VBar, and take a look.

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
Chriss 15 September 2025 12:1515.09.2025 12:15
Hello,

I'm having the same problem, it's happening to me too ???

Why ?

Kind regards
machine-translated from German · Show original
Eddi E. aus G. 15 September 2025 12:1715.09.2025 12:17
Hi,

Perhaps the bug is also a feature.

Another question: is it also 'inverted' in setup mode, or only outside of setup?

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
TomD 15 September 2025 12:5115.09.2025 12:51
Yes, as I mentioned above, it's the same in setup mode. The pitch servo moves easily, just like in the video.
machine-translated from German · Show original
HelischuleGonzalez 15 September 2025 13:0615.09.2025 13:06
That's right. It's the same with all my V8 Evos. If you don't have it with Mikado, it might be because you selected "Logo Heli" in the setup instead of "other 700-size helicopter," and this bug doesn't occur there?

Or does the bug only occur when switching from V7 to V8?

Or is it not a bug, but intentional?

I only tested it briefly for 10 minutes before flight class and had the feeling that it was slightly worse with twisting. But it was just a quick test. The distances also change with twisting.

What already drove me crazy as a perfectionist with V7 and V6 is the fact that channel 1 always shows 29 instead of 30, and the distance is not 100 everywhere, but 99 for servo number 1.

To make matters worse, once you've set a rotation and then reversed it, you can never return to the standard 270-150-29 and 99-100-100 spacing, unless you select the 120 TS again.

Then all pitch curves are reset to 100, as is the cyclic 8-degree value, and all trims, which is incredibly annoying. Because you can't just quickly test anything, and the only solution is to save and load the setup.

I just didn't know that, which really took up a lot of my time.

Therefore, three questions:
- Bug or not a bug with the pitch servo?
- Why 29 and not 30 for servo number 3?
- Why is the distance 99 for servo no. 1 and not 100?
- Why can't you revert to the original values after a rotation?

Best regards,
Daniel

machine-translated from German · Show original
TomD 15 September 2025 13:1515.09.2025 13:15
Eddi E. from G. wrote:
-------------------------------------------------------
> Hmm, strange.
>
Please save the setup to your transmitter.
> and let him write it in the cloud.
Then we can download it to a
Copy VBar and take a look.
>
> Greetings
>
> Eddie

You just need to create a new setup, select a different 700, and set the TS to HR-3. I've experienced this with all my helicopters, and my friends have too. I'm also interested in the answers to Daniel's questions :-)
machine-translated from German · Show original
TomD 15 September 2025 13:2515.09.2025 13:25
I just created a completely new logo setup. It's the same with that one. The pitch servo moves easily.
machine-translated from German · Show original
TomD 15 September 2025 14:2315.09.2025 14:23
Rainer and Eddie, I have some important information. I actually still have an EVO with V7 installed. I just plugged in some servos, and the pitch servo doesn't move a millimeter when I only control roll. So it seems to be a V8 issue.
machine-translated from German · Show original
ulrich 15 September 2025 14:5015.09.2025 14:50
https://www.vstabi.info/forum/read.php?42,208239

So long... Uli
http://www.vstabi.de
machine-translated from German · Show original
JMalberg 15 September 2025 16:0715.09.2025 16:07
Good morning,

same applies to my RAW700 with V8 in the setup:
- Roll right pitch servo moves pitch back
- Roll left, pitch servo moves pitch forward

Strictly speaking, at about 3/4 roll to the left or right, there's another step where the servo moves a touch faster from this position.

This behavior also occurs with pure pitch control.
- Pitch forward -> Roll left
- Backward tilt -> Right roll

The TS rotation has the opposite effect on the other axis:
If you reverse the direction so that Nick stops moving, the unwanted rolling motion is about twice as large; if you reverse the direction so that Roll stops moving, Nick is twice as large.

Regards, Jürgen
(Here are the missing commas for free use in my posts: ,,,,,,,,, )



Edited once. Last edited on 15.09.2025 at 16:13 by JMalberg.
machine-translated from German · Show original
Chriss 15 September 2025 17:1315.09.2025 17:13
OK, great, then the issue with Nick is resolved.

Unfortunately, the question arises as to why this wasn't noticed during the beta tests, where professionals and 3D experts were testing?

Rainer from Vstabi Support also flies multi-blade heads, didn't he notice that?

When can the customer/pilot expect a remedy?

And then there are even more questions from the flight school:

"Therefore, three questions:

- Why 29 and not 30 for servo number 3?
- Why is the distance 99 for servo no. 1 and not 100?
- Why can't you revert to the original values after a rotation?

What about the questions?


Thanks

Kind regards



Edited once. Last edited on 15.09.2025 at 17:19 by Chriss.
machine-translated from German · Show original
RV 15 September 2025 21:1215.09.2025 21:12
I can answer the questions about the numbers. The rest is just how it is. To paraphrase Monika Gruber's saying: "There's always something." And since it's more of a "cosmetic flaw," it'll be fixed when something else is due for release anyway. There's no need for it at the moment.

Regarding the information displayed with the numbers:

What you see here are values prepared for children... uhhh, pilots.
If we were to process these numbers in the algorithm in this way, it would be computationally intensive and cumbersome.
The algorithm calculates the axes "purely" according to their type. That is, nimble, roll, and pitch.
Finally, the required deflection for each servo must be calculated based on the pilot's information about the installed swashplate.

If you were to use these values – well, who wants to calculate what would need to be done with a 140° swashplate and differently sized control levers at "Cyclic at 14:32 with 17% stick travel"? – Trigonometric nerds, step forward! – And that 500 times per second for each swashplate servo. Have fun!

Therefore, it's advisable to perform these calculations in the setup software and only transmit the mixed values from the three axes for each servo position to the stabilizer. This results in three multiplications and one addition per servo and cycle – that's it.

From these values, the display is then calculated – again using extensive trigonometric functions – to show what you see and can adjust. Pilot-friendly, in other words. If these values match the values we've defined for H3, etc., the TS (Torque Position) is displayed; otherwise, it's user-defined.

During all the back-and-forth calculations, rounding differences can occur – that's why you might lose 1-2 points. Either leave it as is (it's irrelevant in this dimension) or enter it manually.

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.




3 mal bearbeitet. Zuletzt am 15.09.2025 21:15 von RV.
machine-translated from German · Show original
HelischuleGonzalez 15 September 2025 21:4315.09.2025 21:43
Rainer's problem is that if you type it in manually again, i.e., 270-150-29 and 99-100-100, and then go out and back in, it's no longer there.

It then reads as if changed by magic:

270-151-30 and 98-99-99, see photos (this is V7, but the same thing happens with V8).

I don't understand why you're writing back to Rainer so vehemently. People invest time and effort to find bugs, and in return they get a snarky and seemingly ungrateful reply.


VG,
Daniel

machine-translated from German · Show original
RV 15 September 2025 22:2715.09.2025 22:27
Hi Daniel,

This is how it is now:

To ensure smooth operation of the sliders, I can't use the calculated mixing ratios (converting them into mixing proportions using trigonometric functions) as the input basis for calculating the beam's display while adjusting the sliders, due to the complex calculations involved. It would be a vicious cycle because of the complexity.

Therefore, when the panel is opened, everything is calculated once as displayed and put into an intermediate variable, which is then used in the panel. In the background, however, the "real" mixing proportions calculated with the counter-calculations are sent to the model.

We calculate this as a float – but even that has its limits in terms of the number of decimal places – and we see that. And due to rounding during the transfer to the model (which then uses integer values), it also differs slightly – but this may only become visible upon reloading, as the calculation is then performed again based on the data in the stabilization module.

Incidentally, this was also the case with the V6 ;-)

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.




3 mal bearbeitet. Zuletzt am 15.09.2025 22:31 von RV.
machine-translated from German · Show original
ulrich 15 September 2025 23:1315.09.2025 23:13
That's not ideal at all. It's a leftover from the past. It's something that could be addressed and improved.
It's not actually a flight parameter, but was originally intended as an input aid for special swashplates.

So long... Uli
http://www.vstabi.de
machine-translated from German · Show original
Chriss 16 September 2025 06:5116.09.2025 06:51
Hello,

I find it very unfortunate to the technically savvy customer who invests time in figuring out why they might have made a mistake during the settings/setup. And then, when they discover errors that clearly originate from the manufacturer, they are simply dismissed with "That's just how it is."

And the term "child" isn't really ideal either.

Rainer, where in the help menu does it say that the values behave this way for the TS rotation?
Unfortunately, I can't find it.

Thanks Uli for possibly helping to fix that.

Thank you

Kind regards



Edited once. Last edited on 16.09.2025 at 06:52 by Chriss.
machine-translated from German · Show original
Eddi E. aus G. 16 September 2025 09:2316.09.2025 09:23
Hi Chriss,

Let's not get carried away. Otherwise, your constant passive-aggressive phrasing will eventually drive me up the wall.
And I usually have a damn thick and long fuse.

Error... what (real) error?
This is a feature that is intentional and optimizes flight behavior.
This should be hidden in the setup, like all other control loop components.
The testers apparently didn't notice this, call it tunnel vision, or because they simply take it for granted, or because they simply work through the steps in the setup without paying attention to it, because it's not a step.
Outside the control loop, strange movements are known and normal; how often has it been noticed that 'after an update' the swashplate also nods at pitch (which it has always done), etc.?
The option to hide the feature will surely be included in the next update.

Whether child-friendly, soldier-proof, or simply easy... is simply necessary (and desired, I think) if you want to cater to everyone from the 3D expert who basically just loads or copies a setup and goes flying, but doesn't bother with the settings, to the 96-year-old.
For the small group who always have to set the volume control to even numbers in order to sleep peacefully (passive-aggressive, I can do that too ^^), the rounding differences would now have to be straightened out in the display.
And make sure that all controls work with integer values, not, for example, in steps of 2, 3 or 5 as has been the case elsewhere.

What was this all about again?

Oh yes, model airplanes ^^

:-)

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
JMalberg 16 September 2025 09:2616.09.2025 09:26
Can we please get down to business now?

If Uli determines that the mutual mixing of the axes in the setup is relevant for the controller algorithm, he will certainly address it immediately. If it's just a "display" problem, there will also be a solution.
Uli/RV has already written something about this.

Regards, Jürgen
(Here are the missing commas for free use in my posts: ,,,,,,,,, )
machine-translated from German · Show original
HelischuleGonzalez 16 September 2025 09:4016.09.2025 09:40
Hello Rainer,

I have no problem if someone tells me:
"Hey, something isn't quite optimally solved, there are these and these reasons for it, don't worry, they are absolutely negligible rounding errors that have no noticeable effect whatsoever."

Wonderful, no problem at all. The only important thing is clear communication, so that the other person feels respected.

Incidentally, I've noticed this since version 6, but since I only have 1% scale (which is a shame because I love scale and am good at it), I've practically never had to work with rotation and therefore never mentioned here that my perfectionism is triggered by these rounding errors ;-)

Now I finally know that, so it's not a big deal.

The fact that the pitch servo moves during roll, while suggesting that a swashplate twist is necessary, is much more relevant. I tried to compensate for this twist and then noticed in two quick test flights, "...hmmm, strange...it feels like it flies worse with the twist, even though there's no twist at all?!?"

So it makes perfect sense that if this going along with Nick makes sense, then it should be deactivated in the setup editing mode.

Firstly, it prevents confusion and potentially resulting mistakes, but secondly, especially with scale heads where, for example, a 30° rotation is necessary, you simply can't precisely set the correct rotation otherwise – at least that's what my gut feeling tells me.

Most scale heads don't need to be twisted, but sometimes it is. This also rules out any mechanical issues.

That's great, Uli, that you want to tackle this :-)

VG,
Daniel



Edited twice. Last edited on 16.09.2025 at 09:44 by HelischuleGonzalez.
machine-translated from German · Show original
Chriss 16 September 2025 12:3216.09.2025 12:32
Hello,
Of course the church will stay in the village; where else would it go? It can't walk.

But then the user/pilot/customer starts searching for why this is the case, and it turns out to be a visual bug.

Why is it so bad if customers point out that something might be wrong?
One could easily get the impression that constructive criticism is not welcome.
Whether it's called a mistake/bug or whatever, it doesn't matter.


Kind regards
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless