T6 engine starter using FSUIPC

Post any technical issues here. This forum gets priority from our staff.
new reply
alehead
Staff Sergeant
Posts: 410
Joined: 24 Aug 2005, 09:18
Location: Würzburg, Germany

T6 engine starter using FSUIPC

Post by alehead »

Hi,

Since buying the Texan when it was released, I have logged almost no time in anything else on FSX. It is such an immersive aircraft to fly...

I like the configuration tool that has allowed me to assign various functions to different axes and buttons of my now more comüplex hardware setup (MFG Crosswind pedals, Thrustmaster Warthog HOTAS, two Saitek trim wheels, and a Virtual-Fly TQ6 on order...)

I have been thinking for some time to reconfigure all the controllers to work solely through FSUIPC, as I have the registered version (which I need alone in order to run one of the Saitek trim wheels as rudder trim, there is no standard function in FSX' hardware configuration interface to assign rudder trim to a wheel).

So far, I have been able to map a lot of the switches to various buttons and so on. What I fail to map is the engine starter. Does anyone have an idea how this might be done in FSUIPC keeping separate from the magnetos, which I have switched elsewhere? If I want to keep everything clean, I need to deactivate the controllers within FSX, so that everything runs through FSUIPC alone.

So, in FSUIPC, how do I map the engine starter to, say, the spring-loaded trigger switch on the HOTAS throttle of the Warthog? Any ideas?

Thanks

Andrew
Andrew
i5 8600K @ 5.0GHz (Der8auer delidded) on air (NH-D15), ASUS MAXIMUS X Hero, 16Gb RAM
EVGA GTX1070Ti, Win10Pro on Samsung M2 500Gb SSD, P3D V4 on 850 EVO 1Tb
Accusim (P3D): T6/Comanche/Cherokee/Spitfire/P51D Mustang (Civ)/V-Tail Bonanza

User avatar
Nick - A2A
A2A Captain
Posts: 13728
Joined: 06 Jun 2014, 13:06
Location: UK

Re: T6 engine starter using FSUIPC

Post by Nick - A2A »

Hi Andrew,

If you prefer to use FSUIPC for mapping the engine starter, you'll probably need to use a text macro and the relevant L:Var which is "L:Eng1_StarterSwitch" I believe (see this thread for more info).

However, there's no harm in using FSUIPC in conjunction with the A2A input configurator; that is, using functions in the A2A configurator wherever they're available (the T-6 starter pedal for example) and using FSUIPC where they're not. (For instance, I used FSUIPC to map a key to hand swing the prop so I don't need to open the shift + 3 window, but I used the input configurator to map the starter to a key.)

Cheers,
Nick

alehead
Staff Sergeant
Posts: 410
Joined: 24 Aug 2005, 09:18
Location: Würzburg, Germany

Re: T6 engine starter using FSUIPC

Post by alehead »

Thanks for your reply. The problem I think I noticed is that the functions in the configurator do not seem to be available if I have the controllers deactivated in FSX itself in order to rely on FSUIPC alone...

At least that was my observation yesterday when trying this out...

Thanks for the info. I have no experience of using L:Vars at all. How would I go about this? Thanks again

A
Andrew
i5 8600K @ 5.0GHz (Der8auer delidded) on air (NH-D15), ASUS MAXIMUS X Hero, 16Gb RAM
EVGA GTX1070Ti, Win10Pro on Samsung M2 500Gb SSD, P3D V4 on 850 EVO 1Tb
Accusim (P3D): T6/Comanche/Cherokee/Spitfire/P51D Mustang (Civ)/V-Tail Bonanza

User avatar
Nick - A2A
A2A Captain
Posts: 13728
Joined: 06 Jun 2014, 13:06
Location: UK

Re: T6 engine starter using FSUIPC

Post by Nick - A2A »

alehead wrote:The problem I think I noticed is that the functions in the configurator do not seem to be available if I have the controllers deactivated in FSX itself in order to rely on FSUIPC alone...
Yeah, that's correct. You just need to enable your controllers in the host sim in able to assign them through the input configurator, but you can still delete any and all assignments if you wish to use FSUIPC instead.

I linked some topics for getting started with L:Vars in this post. It's a useful ability, but the input configurator is much quicker. :)

Nick

alehead
Staff Sergeant
Posts: 410
Joined: 24 Aug 2005, 09:18
Location: Würzburg, Germany

Re: T6 engine starter using FSUIPC

Post by alehead »

Thanks for the help, Nick! Gives me something to do in the evenings!

A
Andrew
i5 8600K @ 5.0GHz (Der8auer delidded) on air (NH-D15), ASUS MAXIMUS X Hero, 16Gb RAM
EVGA GTX1070Ti, Win10Pro on Samsung M2 500Gb SSD, P3D V4 on 850 EVO 1Tb
Accusim (P3D): T6/Comanche/Cherokee/Spitfire/P51D Mustang (Civ)/V-Tail Bonanza

User avatar
Nick - A2A
A2A Captain
Posts: 13728
Joined: 06 Jun 2014, 13:06
Location: UK

Re: T6 engine starter using FSUIPC

Post by Nick - A2A »

You're welcome - tinkering away with with stuff in FSUIPC can certainly eat some time! :mrgreen:

Nick

User avatar
guenseli
A2A Master Mechanic
Posts: 3650
Joined: 30 Jul 2008, 19:32
Location: Berlin, Germany

Re: T6 engine starter using FSUIPC

Post by guenseli »

You can also have a look at LINDA.
At least you can use the actions.LUA scripts to see, what Lua Variables are used.
or you use simply LINDA

http://www.avsim.com/forum/424-linda/

Gypsy Baron
A2A Master Mechanic
Posts: 3396
Joined: 02 Aug 2008, 17:04
Location: San Francisco

Re: T6 engine starter using FSUIPC

Post by Gypsy Baron »

I pretty much map everything through FSUIPC4. On the T-6 even the circuit breakers :)

As for the starter, I use a simple toggle of the L:Var "Engine1_Starter_Switch"
I also map the primer for a stroke and a return on a press and release of a switch.

Here are my MCRO and INI entries for those functions:

MCRO file entries (CM23 assigned by FFSUIPC4):

78=L:PrimerState=SET
79=L:Eng1_StarterSwitch=TOGGLE

FSUIPC4.ini entries:

2=PD,16,CM23:78,2 ;// Set PRIMER = 2 on Press
3=PD,17,CM23:79,0 ;// TOGGLE STARTER 1
4=UD,16,CM23:78,3 ;// Set PRIMER = 3 On Release

Note that my FSUIPC4 is set for the controllers to be assigned letters to prevent
having to edit the 2000+ lines of my INI file shoud Windows decide to charge the
order of the controller assignments!

I have 80 lines in my T-6 MCRO file, not all of them used.
My INI file for the T-6 is over 125 entries, using the FSUIPC4 'conditional assignment'
feature to map 8 functions to each of my Saitek dual throttle quad switches.
That is essentially 8 'modes', if you will, for each switch.

Here are a couple of pix of 'cheat sheets' I made for my B-377 and B-17G
control mappings before I started using Lua scripts to display the current set
data for a couple of seconds when I changed modes

Image

Image

To 'fill this out'....here is my T-6 Buttons section of my FSUIPC4.ini file:

Code: Select all

[Buttons.North American T-6 Texan]
1!==//------- Control Set 1 -----------------
0=B66C0=0 PD,14,Cx0D0066C8,x01 ;//GPU Toggle via Lua Event
1=B66C0=0 PD,15,C66506,440 ;// PANEL ID TOGGLE  RADAR
2=B66C0=0 PD,16,CM23:78,2 ;// TOGGLE PRIMER
3=B66C0=0 PD,17,CM23:79,0 ;// TOGGLE STARTER 1
4=B66C0=0 PD,18,C65635,0 ;// MAG INC
5=B66C0=0 PD,19,C65634,0 ;// MAG DEC
6=B66C0=0 PA,0,CM23:45,1 ;// GENERATOR ON
7=B66C0=0 PA,1,CM23:45,0 ;// GENERATOR OFF
8=B66C0=0 PA,2,C66241,0 ;// TOGGLE MASTER BATTERY
9=B66C0=0 PA,3,C66293,0 ;// TOGGLE AVIONICS MASTER
10=B66C0=0 UD,16,CM23:78,3 ;// TOGGLE PRIMER
2!==//------- Control Set 2 -----------------
20=B66C0=1 PD,14,C66379,0 ;// NAV LIGHT TOGGLE
21=B66C0=1 PD,15,CM23:34,0 ;// NAV LIGHT INTENSITY
22=B66C0=1 PD,16,CM23:35,0 ;// PASSING LIGHT
23=B66C0=1 RD,17,CM23:47,100 ;// CABIN VENTS CYCLIC
24=B66C0=1 PD,18,C65560,0 ;// STROBE LIGHT TOGGLE
25=B66C0=1 RD,19,CM23:48,100 ;// CABIN HEAT CYCLIC
26=B66C0=1 PA,0,C65858,0 ;// PITOT HEAT
27=B66C0=1 PA,1,CM23:49,0 ;// CONTROL LOCK TOGGLE
28=B66C0=1 PA,2,CM23:46,0 ;// COCKPIT LIGHT
29=B66C0=1 PA,3,CM23:44,0 ;// FUEL GAUGE LIGHT
4!==//------- Control Set 3 -----------------
30=B66C0=2 PD,14,CM23:50,2 ;// LEFT WING FUEL TANK SELECT
31=B66C0=2 PD,15,CM23:51,0 ;// MANUAL FUEL PUMP
32=B66C0=2 PD,16,CM23:50,1 ;// RIGHT WING FUEL TANK SELECT
33=B66C0=2 RD,17,CM23:52,100 ;// CARB HEAT CYCLIC
34=B66C0=2 PD,18,CM23:50,0 ;// FUEL TANK SELECT OFF
35=B66C0=2 PD,19,CM23:53,1 ;// MARKER TEST ON
36=B66C0=2 UD,19,CM23:53,0 ;// MARKER TEST OFF
37=B66C0=2 PA,0,CM23:58,1 ;// LEFT LOW FUEL TEST ON
38=B66C0=2 UA,0,CM23:58,0 ;// LEFT LOW FUEL TEST OFF
39=B66C0=2 PA,2,CM23:59,1 ;// RIGHT LOW FUEL TEST ON
40=B66C0=2 UA,2,CM23:59,0 ;// RIGHT LOW FUEL TEST OFF
41=B66C0=2 PA,0,CM23:60,1 ;// REAR LEFT LOW FUEL TEST ON
42=B66C0=2 UA,0,CM23:60,0 ;// REAR LEFT LOW FUEL TEST OFF
43=B66C0=2 PA,2,CM23:61,1 ;// REAR RIGHT LOW FUEL TEST ON
44=B66C0=2 UA,2,CM23:61,0 ;// REAR RIGHT LOW FUEL TEST OFF
45=B66C0=2 PA,1,CM23:56,1 ;// LEFT GEAR LIGHT TEST ON
46=B66C0=2 UA,1,CM23:56,0 ;// LEFT GEAR LIGHT TEST OFF
47=B66C0=2 PA,3,CM23:54,1 ;// RIGHT GEAR LIGHT TEST ON
48=B66C0=2 UA,3,CM23:54,0 ;// RIGHT GEAR LIGHT TEST OFF
49=B66C0=2 PA,1,CM23:57,1 ;// REAR LEFT GEAR LIGHT TEST ON
50=B66C0=2 UA,1,CM23:57,0 ;// REAR LEFT GEAR LIGHT TEST OFF
51=B66C0=2 PA,3,CM23:55,1 ;// REAR RIGHT GEAR LIGHT TEST ON
52=B66C0=2 UA,3,CM23:55,0 ;// REAR RIGHT GEAR LIGHT TEST OFF
4!==//------- Control Set 4 -----------------
55=B66C0=3 PD,14,CM23:64,1 ;// NAV Swap
56=B66C0=3 UD,14,CM23:64,0 ;// NAV Swap release
57=B66C0=3 PD,15,CM18:41,1 ;// <========== SPARE
58=B66C0=3 UD,15,CM18:41,0 ;// <========== SPARE
59=B66C0=3 PD,16,CM23:65,1 ;// COM Swap
60=B66C0=3 UD,16,CM23:65,0 ;// COM Swap release
61=B66C0=3 PD,17,CM23:67,3 ;// <========== SPARE
62=B66C0=3 UD,17,CM18:40,0 ;// <========== SPARE
63=B66C0=3 PD,18,CM18:33,0 ;// COM/NAV ON/OFF
64=B66C0=3 PD,19,CM23:66,0 ;// <========== SPARE
65=B66C0=3 PA,0,CM23:68,3 ;// XPDR MODE UP
66=B66C0=3 PA,1,CM23:69,0 ;// XPDR MODE DOWN
67=B66C0=3 PA,2,CM23:70,0 ;// GPS ON/OFF
68=B66C0=3 PA,3,CM23:71,1 ;// XPDR IDENT ON
69=B66C0=3 UA,3,CM23:71,0 ;// XPDR IDENT OFF
5!==//------- Control Set 5 -----------------
70=B66C0=4 RD,14,CM23:72,0 ;//AP MASTER
71=B66C0=4 PD,15,CM23:73,0 ;//AP MODE SWITCH
72=B66C0=4 UD,15,CM23:73,0 ;//RELEASE
73=B66C0=4 PD,16,CM23:74,1 ;//AP ALT MODE SWITCH
74=B66C0=4 UD,16,CM23:74,0 ;//RELEASE
75=B66C0=4 PD,18,CM23:76,1 ;//HDG DEC
76=B66C0=4 UD,18,CM23:76,0 ;//RELEASE
77=B66C0=4 PA,0,CM23:77,1 ;//HDG INC
78=B66C0=4 UA,0,CM23:77,0 ;//RELEASE
79=B66C0=4 PA,2,CM23:75,1 ;//AP DISCONECT
80=B66C0=4 UA,2,CM23:75,0 ;//RELEASE
81=B66C0=4 PD,19,CM23:42,1 ;//LANDING LIGHT LEFT
82=B66C0=4 PA,1,CM23:43,1 ;//LANDING LIGHT RIGHT
83=B66C0=4 PD,17,CM23:76,1 ;// GYRO ZERO
84=B66C0=4 PD,17,CM23:77,1 ;// GYRO ZERO
85=B66C0=4 UD,17,CM23:76,0 ;// GYRO ZERO RELEASE
86=B66C0=4 UD,17,CM23:77,0 ;// GYRO ZERO RELEASE
87=B66C0=4 PA,3,Cx0D0066C7,x01 ;//Headphones Toggle via Lua Event
6!==//------- Control Set 6 -----------------
90=B66C0=5 RD,14,C65663,0 ;// VOR 1 OBI INC
91=B66C0=5 RD,15,C65662,0 ;// VOR 1 OBI DEC
92=B66C0=5 RD,16,C65665,0 ;// VOR 2 OBI INC
93=B66C0=5 RD,17,C65664,0 ;// VOR 2 OBI DEC
94=B66C0=5 RD,18,C65881,0 ;// ADF CARD INC
95=B66C0=5 RD,19,C65882,0 ;// ADF CARD DEC
96=B66C0=5 PA,0,CM20:48,0 ;//NAV/GPS MODE
97=B66C0=5 PA,1,CM20:30,0 ;//AP HDG MODE
98=B66C0=5 PA,2,CM20:32,0 ;//AP APR
99=B66C0=5 PA,3,CM20:33,0 ;//AP REV
7!==//------- Control Set 7 -----------------
100=B66C0=6 PD,14,CM23:1,1 ;// RESET BREAKERS SET1
101=B66C0=6 PD,15,CM23:3,1 ;// RESET BREAKERS SET1
102=B66C0=6 PD,16,CM23:5,1 ;// RESET BREAKERS SET1
103=B66C0=6 PD,17,CM23:7,1 ;// RESET BREAKERS SET1
104=B66C0=6 UD,14,CM23:2,1 ;// RESET BREAKERS SET1
105=B66C0=6 UD,15,CM23:4,1 ;// RESET BREAKERS SET1
106=B66C0=6 UD,16,CM23:6,1 ;// RESET BREAKERS SET1
107=B66C0=6 PD,18,CM23:8,1 ;// RESET BREAKERS SET2
108=B66C0=6 PD,19,CM23:10,1 ;// RESET BREAKERS SET2
109=B66C0=6 PA,0,CM23:12,1 ;// RESET BREAKERS SET2
110=B66C0=6 PA,1,CM23:14,1 ;// RESET BREAKERS SET2
111=B66C0=6 UD,18,CM23:9,1 ;// RESET BREAKERS SET2
112=B66C0=6 UD,19,CM23:11,1 ;// RESET BREAKERS SET2
113=B66C0=6 UA,0,CM23:13,1 ;// RESET BREAKERS SET2
7!==//------- Control Set 8 -----------------
114=B66C0=7 PD,14,CM23:15,1 ;// RESET BREAKERS SET3
115=B66C0=7 PD,15,CM23:17,1 ;// RESET BREAKERS SET3
116=B66C0=7 PD,16,CM23:19,1 ;// RESET BREAKERS SET3
117=B66C0=7 PD,17,CM23:21,1 ;// RESET BREAKERS SET3
118=B66C0=7 UD,14,CM23:16,1 ;// RESET BREAKERS SET3
119=B66C0=7 UD,15,CM23:18,1 ;// RESET BREAKERS SET3
120=B66C0=7 UD,16,CM23:20,1 ;// RESET BREAKERS SET3
121=B66C0=7 PD,18,CM23:22,1 ;// RESET BREAKERS SET4
122=B66C0=7 PD,19,CM23:24,1 ;// RESET BREAKERS SET4
123=B66C0=7 PA,0,CM23:26,1 ;// RESET BREAKERS SET4
124=B66C0=7 UD,18,CM23:23,1 ;// RESET BREAKERS SET4
125=B66C0=7 UD,19,CM23:25,1 ;// RESET BREAKERS SET4
126=B66C0=7 UA,0,CM23:27,1 ;// RESET BREAKERS SET4
161=PA,4,Cx510066C0,x00070001 ;//INCREMENT 0X66C0 VALUE BY 1, MAX 7 THEN 0, CYLCLIC
162=PA,5,Cx610066C0,x00070001 ;//DECREMENT 0X66C0 VALUE BY 1, MIN 0 THEN 7, CYLCLIC
274=CR(-C,6)C,0,C65588,0 ;//Brakes
275=CP(+C,6)C,0,C65752,0 ;// PARKING BRAKE

Lots of 'cool things' one can do with FSUIPC4 and Lua and a bit of imagination :)

Paul

Image

new reply

Return to “T-6 "Texan" Tech Support”

Who is online

Users browsing this forum: No registered users and 4 guests