Kevin Brigden

That's awesome, thanks Roman! I'm going to be out of town for a few days doing a rally down to the south of France but I will report back next week when I've tried this latest version. Many thanks

Many thanks for your help on this Roman, it's much appreciated! :)

My mistake, I needed to remove the existing calibrations before recalibrating. It now works! I suppose the only thing I need to figure out now is how to prevent the activation of an axis suddenly changing the position of an axis after a mode switch. I.e. after setting the right throttle to 80% from idle, I don't the left throttle to flick up to 80% as soon as I move it. However, I think this is an unavoidable consequence of having the physical lever left in the 80% position and in any case I am prepared to live with that.

Strangely, that particular code works with the throttle but now the mixture and prop no longer respond in any setting.

Roman, That worked perfectly! Excellent work much appreciated! Can I ask a couple of questions of you please? 1. At the moment, this switching works by using a single switch to cycle through the modes. Is it possible for me to modify the scripting to enable use of an individual switch for each mode? i.e. switch 8 for mode 1, switch 9 for mode 2 and switch 10 for mode 3? My understanding is that I will need to use a different offset command to the one used in this profile data. I understand that at the moment the command is instructing the offset to increase by a single byte until it reaches a count of 0, 1, 2 and then it loops back to 0. So am I correct in thinking that I need to use a byte "select" or "set" command? 2. You have saved me from spending a needless £40 on a second throttle quadrant from Saitek. Please see your private messages. I also believe that on Pete's return this thread should be a made a sticky or placed in the FAQ because I seriously doubt I am the only person who wished to do this.

Roman my apologies, I should have said that I had fully followed Pete's instructions (including the LUA file) however thus far I have not been able to make it work. As such, I think I was missing something obvious. I'll try your tips now and see how I get on. Please bear in mind, I am a mechanical engineer, not a software engineer so my programming skills are... not the best!

Should also add that in the axis area: [Axes.Beech Baron (Default)] RangeRepeatRate=10 ... 2=0Z,256,F,L1:R,0,0,0

Just by way of an update I attempted this again this afternoon but to no avail. I'm sure it's something simple I've missed. [Buttons.Beech Baron (Default)] 3=P0,8,Cx030066C0,x000100E5 I appreciate Pete's away but if there's anyone who can spot the error please advise.

Yeah I did eventually find that last night funnily enough :) Unfortunately I can't seem to get that technique to work (although there's a high likelihood that's because I'm thick).

Hi Pete and the gang, hoping you all might be able to help me out here. I've read through the tutorial material and done a forum search but I've not quite found the answer I'm looking for. What I'd like to do I have a single throttle quadrant for the Saitek Pro Flight. I understand the concept of compound button mapping and I would like to apply this to twin engine controls. Specifically: I wish to be able to control both engines throttles, props and mixtures when in mode 1, the left engine controls in mode 2 and the right engine controls in mode 3. I thought this might be a case of simply applying the relevant logic statements as per compound buttons but that doesn't appear to be the case. i.e. [Axes.Baron 58 - Twin Piston] ... 2=C(+0,8)0Z,256,F,65765,0,0,0 3=C(+0,8)0U,256,F,66291,0,0,0 4=C(+0.8)0V,256,F,66292,0,0,0 In this instance, button 8 represents the mode 1 detent of the control wheel on the back of the right hand grip. My plan was to then generate similar lines of code for "engine 1 prop, engine 1 mixture" etc. Unfortunately, this first stage in my testing rendered the axes inoperable suggesting I cocked up the syntax or that it simply isn't supported. Any suggestions?