Turbine setup on Vplane Questions

Ok, so, I've gone down a pretty complicated path of getting a turbine jet setup on VPlane. Am experiencing some really weird issues with the setup though.

Jet config: Dual aileron servos, Dual flap servos, dual elevator servos, rudder servo, steering servo, retracts and brakes.

Issues:


* Macrocells do not always show their names.
This is a really odd one, and mainly just a frustration as I was trying to go through and change settings. It's a little difficult to change a cell when you have to remember the channel number rather than just see it by name. It does seem to only correct itself if you power off the model and power up again.

* Model throws in setup.
I'll be honest, this one is on me for not RTFM. https://www.vstabi.info/en/node/1786 Either the How to setup section needs to be moved up in the current very out of date VPlane manual, or a new manual should be put together. It makes sense once you get to the bottom of the section and see it. But it's not how one would normally think of setting up a plane.

* Automatic parameter change from a dial.
I might be crazy, but I could have sworn there was a way on the first gen VControl that you could pull up an adjustment on screen and then just have to turn a dial and it would automatically allow you to control that feature while flying. I have yet to figure out how to get this feature again. I know you have the assignable dials in Modify Config, but that menu doesn't allow you to assign dials to things like Integral Gain/Range, etc.

Any feedback, thoughts, comments????



1 mal bearbeitet. Zuletzt am 27.05.2026 08:25 von nem3_2.

Hi,

macrocell names, please tell serial no.s (transmitter and VBar on model) and make sure your transmitter was on the cloud so all current data are there.
Save the macrocell setup and the model setup (its current state), too.
Then we can have a look.

Throws in setup, I'm afraid for now it's the way it is. It's basically similar to a heli setup, in setup, you adjust directions, center, travels, limits (which a combined/mixed travel may not exceed), by ear or exactly to degrees or deflection in mm given in the model's documentation, then you use Agility and Expo per bank to the feel you want to have.

This is so kind of logical, almost genetic to me that I wonder how it could be different but I'm by no means a benchmark or anything.
Also the explanation (even if old but not really outdated, functionally at least), first the screens, parameters, then a summary.
But it would be simple to put that at the top, of course.

VBar Control Classic was different (simpler), and it had that feature with the two knobs on the top. With VBar Control Touch and EVO, there's Modify Config, right, but you can no longer just 'pick' a parameter by rotating an input.
If you find parameters are missing in the Modify Config list of parameters, and maybe also only in VPlane, please let us know, I'm sure they an be added eventually.

Best,

Eddi

Born to fly ...
forced to work.

Hi Eddi,

Thanks for your reply. I've actually been somewhat fighting to get my model and macrocells saved to the cloud properly. I was just now playing with image files and it seems my current settings have been uploaded. Both are the EA_Viper_v3 config's

Tx serial - 11005890
Neo Evo master serial - 27010213
Neo Evo slave serial - 27010151

Throws - yah, same here on the heli side. But I also figured out that the plane itself had a massive geometry problem. For instance, with the preinstalled surface horns and recommended servo horns, I was only using 32 servo throw on elevator and aileron. I was able to get this into the mid 70's, but wish I could get it higher.

Manual - I think my issue is that between the VCcontrol classic and the current version touch, settings have been added and some renamed. The in radio help screens don't explain them all, and the ones missing, usually are not in the old manual.

Modify Config - It's missing Integal Gain, Range and Stick to params. all things you'd really like to adjust in flight



1 mal bearbeitet. Zuletzt am 29.05.2026 09:04 von nem3_2.

Hi Nick,

looks OK, particularly the macrocell setup has all the names, I guess. See vstabi.info/cloud where you can already view some of the setup files online, in table form.
Can't tell why those names should show or disappear randomly, maybe Rainer has an explanation.
A guess would be, the transmitter needs a minute to parse the name file, and sometimes it's ready when you need it, sometimes not yet, and then the parsing is maybe interrupted.

Throws, well, is something I notice frequently ... short horns make for a sleek and less breakable layout, but there are mechanical and spatial limitations, and then there are lever principles

Manual, if you find something missing or incomprehensible in the online help (?), please feel free to list it.
VPlane is unfortunately still a stepchild with some regards :-/

Modify Config, copy.

—Eddi

Born to fly ...
forced to work.

Eddi E. aus G. Wrote:
-------------------------------------------------------
> Hi Nick,
>
> looks OK, particularly the macrocell setup has all
> the names, I guess. See vstabi.info/cloud where
> you can already view some of the setup files
> online, in table form.
> Can't tell why those names should show or
> disappear randomly, maybe Rainer has an
> explanation.
> A guess would be, the transmitter needs a minute
> to parse the name file, and sometimes it's ready
> when you need it, sometimes not yet, and then the
> parsing is maybe interrupted.
>
> Throws, well, is something I notice frequently ...
> short horns make for a sleek and less breakable
> layout, but there are mechanical and spatial
> limitations, and then there are lever principles
>
>
> Manual, if you find something missing or
> incomprehensible in the online help (?), please
> feel free to list it.
> VPlane is unfortunately still a stepchild with
> some regards :-/
>
> Modify Config, copy.
>
> —Eddi

Thanks Eddi, and sorry for the very late reply. Have been going back and forth trying to resolve a bunch VPlane/Vcontrol oddities. I've opened a ticket with MikadoUSA as well. Happy to open separate threads about this, but all seems related to Vplane or Vplane setup requirements so here goes. I'll list the full setup, in case I haven't previously. Airframe is an Elite Aerosports Viper Sport V2, Kingtech 102G5, Dual Vbar Evo's (1 Master, 1 Extender), Xpert MM-3301's (Elevator and nose steering), Xpert AS8601 (Ailerons, Flaps, Rudder). Radio is VControl Touch Evo.

Also, small back story if it helps, I have flown VPlane on a number of different types/styles of planes in the past, including small EDF jets. Everything I am experiencing with the system now makes the Vbar system look VERY buggy at best, which is the complete opposite of everything I have experienced before.

1: Since the maiden flight, I have been fighting with VERY odd flight characteristics with the gyro enabled (default settings). The odd thing is it is NOT an immediate problem. A derivative gain error seems to build up and then the whole plane starts feeling mushy and uncontrollable. Elevator starts bobbing up and down, aileron just kind of makes the wings rock back and forth. As soon as I switch back to Bank 1 (zero gyro) everything resolves and the plane flies fine. You can even see it just settle.

1a: In my first two outings I tried removing head hold by lowering the Integral gain to zero. This seems to almost completely remove any gyro correction, proportional and integral. Very odd behavior if it's supposed to only affect head hold gain.

1b: Today, 2 flights, first flight was reverted to default Vplane settings. Noticed the same exact issue when the gyro is on. So before the second flight rather than lowering the Integral Gain, I zero'd out the Integral Range. This, and this alone did exactly what I was looking for, stops the head hold portion but leaves the proportional untouched. Finally was able to get a nice and predictable flight in. No elevator bobbing, no weird aileron.

2: Due to the huge variety of settings that need to be adjusted and the nature of flying a turbine jet, I had an idea of grabbing a second hand VControl that I could use for buddy boxing. Idea was let the buddy fly the plane while I was tuning parameters on the master. Well, buddy boxing is completely non-functional with this setup. I am leaning towards it having something to do with the dual Vbar Evo's. I have tried buddy boxing with everything from a VControl Classic (the one I bought second hand) all the way to a matching VControl Evo. In every case, as soon as you power on the model, the servos just start jittering. Any control movement just results in larger jitters. As soon as you exit buddy mode on the slave radio, the model returns to normal.

3: VPlane manual/explanations - Honestly I think the biggest problem is a combination of the language translation barrier and the small adoption of VPlane. There just aren't enough people flying it outside of default settings. Consequently, when I'm trying to resolve an issue there isn't much to research against. That said, and as I said above, for the most part, default VPlane settings have almost always worked very well out of the box. I seem to have stumbled upon the instance where that is not the case.

4: Macrocell names - Yah, this is a very odd one, because when the names do NOT show up, they never seem to come back unless I power off everything and reinitialize. Even then, it's hit or miss if they come up.



5 mal bearbeitet. Zuletzt am 21.06.2026 10:07 von nem3_2.

Hi Nick,

weird.

I'd say, VPlane is the same, no matter if on a park flyer, sailplane, EDF Jet, or a turbine.
So whatever weird things you experience lie with that particular setup/configuration, or with the working conditions on that particular plane.
Quite broadly defined, granted.

1b sounds like we're getting somewhere, but it does not explain 1 and 1a, just that something must be different now, was different before.

2 ... there is one known bug with buddy boxing, with EVO: when using it with our remote antenna, what you're experiencing would unfortunately be normal. And it would require sending in that item for us to update it, or have it replaced for a quicker turnaround. For whatever reason, buddy boxing with remote antenna wasn't tested properly or with the final versions :-/ but fortunately you notice immediately when you set up, there's no hidden surprise which hits you at the worst moment.
But I shouldn't think it's a thing with two VBar EVO VLink ... still I'd have to try, my only available Interbus Setup right here right how is still NEO/NEO.

3. I hear you. We are still looking for someone like Rainer (RV), who burns for the thing and wants to bring it forward, who has a good grasp on all the particularities with planes but is open to blazing a new trail, not just into mimicking all the old ways, good or bad.
In the meantime, and to be completely honest, we can only do so much, als natural born heli people
Kyle Dahl, back in his days as a competition and show pilot, did some videos on fine-tuning VPlane, and I guess he and particularly his father in law together might still have some of the best hands-on experience with flying VPlane on Jets (also thrust vector), and they speak the language.
Maybe a good idea to connect with Kyle or Georges van Gansen, one or another way?

4. something Rainer and/or Uli must have a look at, I guess, who can look behind the curtain and most likely see more.

—Eddi

Born to fly ...
forced to work.

Hi Eddie, thanks again.

Weirdness - I can say this is one of the more complicated VPlane setup's I have done. So config might be an issue. It's just weird that the odd flight characteristics don't start immediately. It takes 30-60 before the plane will start flying what feels like, uncontrollably.

1b: I argue it actually might. Since D gain is not adjustable from the radio, is it possible there is an issue with that part of the control algo?

2: Sorry, no remote antenna in use here. But I also have a ticket open with MikadoUSA and chatting with Peter.

Hi Nick,

1b: ... hard to tell, I'm _so_ out of my depth here

2: yeah, I figured already. Peter came back to me already, asking your same questions ^^

I have now taken Uli in the loop so he can check if he can identify the issue (probably similar to remote antenna, both use the Extender bus to add antenna diversity after all), and hopefully fix it quickly

Best,

Eddi

Born to fly ...
forced to work.

Update on the “weirdness” I zeroed out the Integral Range on all three and no longer getting any weird tendencies. Talking with the jet guys, learning that no one flies with heading hold. ¯\_(?)_/¯

Hi,

thanks for the heads-up.

I took the time to compare the last two setups you saved, and the macrocell setups.

One thing I didn't comment on the last time is, you seem to have gone full-manual, with the programming.
Of course you can do that, and the result is probably similar if not the same, using unchanged FC as inputs (w/stabilization), but I guess starting with the regular Model Setup and only linking in extra control surfaces could or would make things easier.

Says one who never got beyond four-flap electric gliders but who's helped quite a lot of pilots already.
So, just an observation.

But what meets my eye today is, in an earlier setup you have quite narrow servo travels, like in the 29-34 range for Elev L+R, 45-45 for Ail L+R.
In your latest setup, it's in the 89-100 range for elevator, and 100/100 for aileron.
Did you make any mechanical changes? If so, they are for the way better I guess, they leave the servos room to work, and help with precision/resolution.

With the narrow limitation, smallest corrections have a huge impact on the control surface deflection (_very simplified_, like, having 29+34=63 steps resolution vs. 89+93=182).
This alone could show as a somewhat erratic 'jitter', on the ground, probably also explain the buddy boxing thing where things work a little differently, and it could also explain why the heading hold is running in circles (more like hexagons, octagons, too little points to draw a more rounded circle, figuratively speaking ).

Maybe it's a Jet thing, flying only with small control surface deflections, and getting there with limiting the servo travel instead of getting it right mechanically, and maybe that's why they (have to?) omit heading hold.

Just a mental game, rather a hypothesis than a theory

—Eddi

Born to fly ...
forced to work.

Hi Eddie,

I do apologize for my late response. To answer you're questions first -

Rates: yes, I adjusted everything as much as I mechanically could. Rates are higher, but still not were I'd like them. I do understand what you mean, but also, these are 4096 servos. While I think I could tell the step difference between the 29% and 80%, that's not exactly the jittering I was seeing.

Manual setup/Macrocells: Yah, I did start off with one of the default setups, but it was fairy limited for what I needed just for control surfaces. After I got that all working I had a little more fun with stuff like nose gear steering only working when the gear was down.

Jittering: I shared this video with Peter, let me know if the link doesn't work for you - https://share.icloud.com/photos/007eWEK32-EIxk-kLm_5XLLPA

That is with the buddy switch activated and just pulling a little elevator. When you let go, the surface returns to center, jittering only slightly.



2 mal bearbeitet. Zuletzt am 15.07.2026 08:09 von nem3_2.

Hm, weird, still.

If you apply the same amount of elevator from the master transmitter, it doesn't jitter, right?

Can you please check if the latest setup and macrocell setup is saved to your transmitter, so I can load those from the cloud, and load them onto a pair of VBar EVOs here? To which physical port is that control surface connected exactly?

Then, I can test and even check the signal output with an oscilloscope, and see.

What radio modules are in use, on both transmitters, and with which settings (if the multi region was in one or both of them)?

Best,

Eddi

Born to fly ...
forced to work.

Sorry, I misstated that. Either transmitter will do that once the buddy is connected.

The jittering happens on all control surfaces, but here is how I had them configured:

M ESC - Turbine throttle
M Tail - Rudder servo
M Ch1 - Elev L
M Ch2 - Elev R
M Ch3 - Ail L
M Ch4 - Ail R
M Aux2 - -
M Aux3 - E Aux 3

E ESC - -
E Tail - -
E Ch1 - Flap L
E Ch2 - Flap R
E Ch3 - Retract
E Ch4 - Brakes
E Aux2 - -
E Aux3 - M Aux 3

As far as I know, none of them are multi region. They were all US purchased, so whatever Mikado USA sells.

Question, to trigger an update to the VBC-t Cloud, does the model need to be connected? Any other things that need to be done?

Hi again,

you can see if it is Multi Region, directly on the screen (see attachment), with the tiny signal strength graphics there (not functional, just pixels).

Or in Settings / Transmitter, if so, there's a signal strength icon where you can select between the options (and read up on them, too (?)).

Transmitters purchased at Mikado USA or Mikado USA could have them by default already.

VBar Control will push out data into the cloud if there are new data (not yet archived), and if it's idling (no model connected) and on a WiFi, with Online Service (x) enabled.

Just check your cloud, Setups, if the latest (by name and date/time stamp) are there, usually in a couple of seconds.

Best,

Eddi

Born to fly ...
forced to work.



1 mal bearbeitet. Zuletzt am 16.07.2026 10:09 von Eddi E. aus G..