Progaming of The sticky throttle hold with Phoenix

With Devo 7 and version 4.0.1 nighty-c3007aa I use the simulator Phoenix to start 3D flight. I programmed on the switch Hold the "sticky throttle hold" and the Fmod the iddle up (I have put no programming curves etc ..) on Channel 5, except the switch Fmod. The simulator works well with the sticky throttle when the switch is Fmod position 0, but does not work when it is on position 1 (Iddle up) (thottle is not cut.) The mixer screen output shows that the throttle is cut, so for Deviation that's OK. I put on phoenix and affected the switch Fmod 0 channel 5 . In phoenix I have the Fmod position switch. So whatever the position of the Throttle stick or switch Hold when I switch on Fmod, the engine starts.
In order to take good habits, how to make the simulator works like TX, ie the Fmod be well controlled in sticky throttle.

If I understand correctly, you've got things set up so that throttle hold is handled by the Tx and flight mode (i.e. - the FMOD switch) is handled by Phoenix. So the problem is that Phoenix doesn't know that you've turned on throttle hold, and in FMOD1 will go right on mapping the Tx throttle output of 0 to a it's normal 3d throttle setting and the appropriate negative pitch setting.

The easy fix is to set up a channel that's a 1-1 map of the virtual channel that's your sticky throttle hold, and tell Phoenix that channel is the hold switch. I'm not sure how to do that.

Alternatively, you can delete the Idle up setting from Phoenix, and program pitch and throttle curves for the FMOD switch on your Devo. That's the most common option, as you're making the simulator act like your helicopter, amd can use the same settings on your Tx as you do on a real helicopter.

It is the same like with Spektrum DX8.
Same with RealFlight.

You have to assign
- hold
- f-mode
- dualrate

switches to extra channels (5-. Not sure about 9-12CH.


Basically don't try to do any advanced firmware configuration stuff in your model (safety switches, mixers, e.g).
The SIM needs to see your switch as a separate channel.

You have to configure the switch / channel in the channel TX editor and assign it to the appropriate SIM function (e.g hold, fmode).

I once was successful setting up fixed throttle curves on a DX8 to run it with Phoenix (FM1/FM2).
You may need to activate an advanced Phoenix setting in your heli model for that.
But I do not have the Phoenix SIM on my own.

Trying to configure everything in the transmitter (model editor) and let just map the heli/acro functions TX-SIM model 1:1 (like in real pitch CH6, throttle, curves, mixers, CCPM for flybar) is more advanced and may be more complicated depending on the SIM manual.

"Throttle curves" from the TX are "virtually" mapped in Phoenix (in the Phoenix model) too.
<=> 3 fixed points.
Therefore Phoenix will not take your fixed throttle curve 1:1 in the standard settings.
But you can just select between the 2-3 Phoenix fixed throttle curves.

I tried to put on channel 8 channel output 3 (THR) and tell to Phoenix that's the sticky throttle hold, but it does not work. And when I switch the Fmod to enter Iddle up, the gases are almost always the maximum with curves 1 to 1 throttle. So I'll make it simple. It can be a good exercise for a specialist ...
Thank you to both of them to help me.

THR channel 3 to Phoenix channel 8? No.

Configure in the advanced mixing GUI normal channel which you map the hold switch to.
You can do it with the simple, 1-1, I had seen this somewhere.
Personally I used the (two) complex mixer(s) on that channel (e.g CH8) and set Hold0 to -100 and Hold1 to +100. Or was it vice versa or 0? Well depends what the SIM needs...all possible.
SRC is the switch which you map it to.

If CH3 is your THR channel, you can not map that to the hold switch.
At least ot with the easy model setup in the SIM.

I've done an all-singing, all-dancing model.ini for the Devo10 and phoenix. I wrote up a blog post that walked you through configuring Phoenix and the deviation config. Possibly that will help you sort out what you need to do. However, it's for the Devo 10 and deviationTx 3.0, so the model.ini file won't be much use to you.

rc.mired.org/2013/07/configuring-deviati...-on-devo-10-for.html

Hello,
Actually Phoenix manages its Idlle up, I put Channel 5 the Fmod switch and when I switched on it didn't account other commands TX. On your advice, so I deleted totally. So I did not think we could do differently.
Now Phoenix is mapped like this in Mode 2:
Throttle: CH3
Collective Cyclic: CH6
Elevator: CH1
Aileron: CH2
Rudder: CH4
Now I put mixes on TX and Phoenix works just like a real helicopter. I will be able to practise properly.
Thank you for your help.
I forgot
By the way, is it OK for my issue 632?

Well, then you have to do it for each model in the SIM.
You actually also need for each SIM model a model on your TX - probably.


If I where you I would drop Phoenix, get RealFlight not with the USB dongle interface but with the USB elite interlink (Futaba 6EX like) controller.
Works out of the box without any configuration within the RF model configurations.

You just have to do a very simple channel - channel and switch - channel configuration in RealFlight.

With the RF dongle interface you connect your transmitter to it is somehow as complicated as you now configure out...


I do not get the benefit using your TX for the SIM - if not for advanced model to model configuration like you are now trying to do.

But still...somehow overkill.

RF helis fly with the interlink controller just fine.

According to various user experiences RF helis fly better than Phoenix. I really like RF heli feeling.
So many advanced / good helis designed by users on the Knife Edge SwapPages...


So if you may get fed up with this config go the easier RF + elite interlink route and just have fun

Thomas.Heiss wrote: I do not get the benefit using your TX for the SIM - if not for advanced model to model configuration like you are now trying to do.

You want the habits you develop on the SIM to work on your real aircraft. For that, you need to have the same set of switches and the same configuration on both. You can do that with one model per model type, or given the power of deviation, one model that has a mode per model type, controlled by some switch that's you use for accessory control on real aircraft - assuming you use the same setup for all aircraft of the same type on your Tx. If you don't use the same setup for all aircraft of the same type on your Tx, you should. You want your habits to work right on all of them.

The hard core pilots take the time to tune their sims to behave exactly like their real aircraft. They then use their Tx in trainer mode with the same model file that they use to fly the real aircraft. Except deviation doesn't can't do that, as it doesn't have a "trainer mode".

I'm not so much into sim's any more. A nano-size CP heli over grass is nearly indestructible, and when you take damage you can replace the entire thing for less than the cost of a blade strike on a large heli, This is more fun than a sim, and better for learning than the sim unless I take the time to make a sim model behave exactly like my heli, and I'm not hard core enough for that. So I use the nano's to practice new things.

In fact I think it does not work quite correctly.
1 If I put "On" the "sticky throttle" it controls the throttle stick and the switch Fmode, then I think it's OK.

2 If I put "Off" the "sticky throttle" and I move the switch Fmode and throttle stick without going down background, I have the cut of gas, then I also think it's OK.
3 If I put the throttle stick gas down, and that I ride, the engine starts I again think it's OK.
4 If I put the throttle stick gas down, and I switching the Fmode in position 1 (Iddle up) the engine starts full throttle. Is this normal, because in this case where is security? As if I switch off the TX and I put off the "sticky throttle" and throttle stick down and Fmode in position 1 (Iddlle up) the engine starts full throttle. what do you think?
File attached

What do you think about my question 4?

Heli startup:

Hold ON
Fmode0->Fmode 1
Throttle stick to the middle (0-pitch)

Hold OFF
-> soft start of the engine

In Fmode1 stick down = negative pitch.

Maybe your FMode0-2 sends the wrong throttle signal on the THR channel?? Do you have any throttle mixers defined?
You need to check for the three curve way points in Phoenix, when which one applies.
e.g 25, 50, 75.
Actually you would need to map that to 3 throttle mixers for FM0-2.
Mapping the F-mode switch alone to a channel is not enough.


To your question 4:
You forget about throttle hold.
You will never ever put the throttle/pitch stick down and then switch to fmode1 (idle up 1 / stunt mode 1).
But well, in your 1st posting you described that ST1 does not work in any way.

Even if you have a reduced pitch curve -40 or -30 (instead of -100) as starting point (lowest point), you would not spool your heli up with THAT pitch values.


Not sure what is Phoenix doing....maybe it requires zero pitch / middle stick?
Maybe it can recognize soft startup when you switch TH (mapped to extra Phoenix hold switch/channel)?


Maybe you should just try to startup in FM0 and once the heli is spooled up you can switch to FM1/ST1.
You can also do that in flight.


You may want to check your throttle curve points (fixed rates) in the monitor for FM0, FM1, FM2.
Going full throttle 100% on FM1+FM2 does not seem correct.

Please remember: I am coming from the RealFlight SIM side.

Thomas