Saitek Pro Multi Panel

[Royal Eagle]

Hi Pete,

I hope I can find an solution for this !! I'm a registered FSUIPC user, not an advanced one though (Hopefully once I get this work ... I will be tackling the advance user manual) ...

I'm working on a simple Home Simulator with the following components:

- Windows Xp Pro (32bit)

- FSX Gold Edition (With Acceleration Package)

- Wilco Airbus Vol.1 & Vol 2 Software

- Saitek:

- Pro Multi Panel

- Pro Radio Panel

- Pro Switch Panel

- Pro Instrument Panel (2)

- Throttle Quadrant

- Logitech Force 3d PRO Joystick

- CH Pro Pedals USB

Now, I got most of the equipment working using FSUIPC, but now having a real delima with Saitek Pro Multi Panel ...

- I used the default Wilco Commands (Ctrl +Shift +F7 & Ctrl +Shift +F8) for toggling HDG and NAV switch in the A320 IAE panel and used the Mouse Macro technique to define the commands.

- I used SPAD Software to program these commands to HDG & NAV buttons in the Multi Panel.

Scenario 1:

- Kept the default Wilco Command Configuration for both actions and programmed a mouse macro with the same keys combination in FSUIPC.

- Hitting the key combination on the Keyboard, its working and I can see the knob Pull & Push action with the change in the A320 FCU and PFD Panels (Changing form Managed to Selected and from HDG to NAV) as should be

- Programmed these commands using SPAD Software in the HDG and NAV Buttons of the Saitek Pro Multi Panel

- Pushing the buttons, I can see the Knob Pull & Push actions and hear their sound but with no change in the FCU or PFD panels.

Scenario 2:

- Deleted the default Wilco Command Configuration for both actions and programmed a mouse macro with the same keys combination in FSUIPC.

- Hitting the key combination on the Keyboard, I can see the Knob Pull & Push actions and hear their sound but with no change in the FCU or PFD panels.

- Programmed these commands using SPAD Software in the HDG and NAV Buttons of the Saitek Pro Multi Panel

- Pushing the buttons, I can see the Knob Pull & Push actions and hear their sound but with no change in the FCU or PFD panels.

Accordingly, it seems that the FSUIPC mouse macro (Trap) did not capture the function of Pull & Push, it just captured the moving of the switch !!! Though using the mouse left button for push and Right for Pull is working fine and change from HDG to NAV in both scenarios

- I tried any other function and program it to the same buttons and it worked ... like the QNH Pressure switch, even the HDG Increment and Decrement ...

I guess you need to see a copy of my FSUIPC.INI file :

[General]

UpdatedByVersion=4600

History=YPOTA8IFHQEF3D1WXZTEE

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

ConsoleWindow=88,116,757,543

Console=No

[JoyNames]

AutoAssignLetters=Yes

0=Logitech Force 3D Pro USB

0.GUID={65A44860-0615-11E0-8003-444553540000}

1=CH PRO PEDALS USB

1.GUID={E0007520-0633-11E0-8006-444553540000}

2=Saitek Pro Flight Throttle Quadrant

2.GUID={3EA823E0-0628-11E0-8001-444553540000}

A=Logitech Force 3D Pro USB

A.GUID={65A44860-0615-11E0-8003-444553540000}

B=CH PRO PEDALS USB

B.GUID={E0007520-0633-11E0-8006-444553540000}

C=Saitek Pro Flight Throttle Quadrant

C.GUID={3EA823E0-0628-11E0-8001-444553540000}

[buttons]

ButtonRepeat=20,10

[MacroFiles]

1=1 APU Bleed

2=1 APU

3=1 Batteries

4=1 Landing Lights

5=1 Taxi Lights

6=1 Strobe Light

7=1 Open Climb

8=1 ALT Control

9=1 ALT Switch

10=1 AP HDG Switch

[AutoSave]

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[WideServer]

WideFSenabled=Yes

[Axes.Feelthere A320 IAE Royal Jordanian]

0=CZ,256,D,9,10,0,0

[Keys.Feelthere A320 IAE Royal Jordanian]

2=67,9,M3:1,0

4=73,9,66242,0

6=73,10,M1:1,0

8=85,10,M2:1,0

12=78,9,M4:1,0

14=74,9,M5:1,0

16=81,9,M5:2,0

20=88,9,66053,0

22=79,8,66052,0

38=104,10,M10:1,0

40=103,10,M10:2,0

44=120,11,M11:1,0

48=115,11,M11:2,0

58=118,11,M10:2,0

64=119,11,M10:1,0

[Monitor]

Display=8

[Keys]

2=119,11,M10:1,0

Also, A copy of a small Logging file while pressing the HDG & NAV on the Saitek Multi Panel:

********* FSUIPC4, Version 4.60a by Pete Dowson *********

User Name="Mohammad Byouk"

User Addr="mbeauke@yahoo.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

14711672 System time = 21/12/2010 08:38:21, Simulator time = 09:54:27 (07:54Z)

14711672 LogOptions changed, now 60000000 00000001

14712125 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

14712125 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

14713141 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

14713157 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

14714141 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

14714141 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

14715063 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

14715063 .. Key not programmed -- passed on to FS

14715063 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

14715063 .. Key not programmed -- passed on to FS

14715063 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

14715063 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc

14715063 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc,31

14715063 .. This key is programmed in FSUIPC4 'Keys' options

14715063 KEYUP: VK=118, Waiting=0

14715063 KEYUP: VK=17, Waiting=0

14715063 KEYUP: VK=16, Waiting=0

14715110 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

14715110 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

14716141 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

14716141 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

14716907 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

14716907 .. Key not programmed -- passed on to FS

14716907 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

14716907 .. Key not programmed -- passed on to FS

14716907 KEYDOWN: VK=119, Waiting=0, Repeat=N, Shifts=3

14716907 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc,31

14716907 .. This key is programmed in FSUIPC4 'Keys' options

14716907 KEYUP: VK=119, Waiting=0

14716907 KEYUP: VK=17, Waiting=0

14716907 KEYUP: VK=16, Waiting=0

14717125 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

14717125 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

14718141 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

14718141 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

14719094 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

14719094 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

14722563 LogOptions changed, now 00000000 00000001

[Pete Dowson]

I used the default Wilco Commands (Ctrl +Shift +F7 & Ctrl +Shift +F8) for toggling HDG and NAV switch in the A320 IAE panel and used the Mouse Macro technique to define the commands.

That statement has me completely confused I'm afraid. If the aircraft panel res[ponds to known keyboard combinations as you say, why would you need to resort to the FSUIPC mouse macro facilities? Why not use the keyboard combinations provided? Seems much cleaner, even if the panel is written in a way which will support mouse macros.

- I used SPAD Software to program these commands to HDG & NAV buttons in the Multi Panel.

Arh, is SPAD that freeware program for interfacing the Saitek gear to FS or FSUIPC?

So what actual 'commands' are you making SPAD send? Keys or buttons or offset changes or what?

Scenario 1:

- Kept the default Wilco Command Configuration for both actions and programmed a mouse macro with the same keys combination in FSUIPC.

Sorry, something is very confused there. Mouse macros don't have key comninations. Mouse macros instigate calls directly in C/C++ coded gauges. Please explain what you mean.

- Hitting the key combination on the Keyboard, its working and I can see the knob Pull & Push action with the change in the A320 FCU and PFD Panels (Changing form Managed to Selected and from HDG to NAV) as should be

So this merely confirms that the default Wilco Commands (Ctrl +Shift +F7 & Ctrl +Shift +F8) work as Wilco intended, I assume?

- Programmed these commands using SPAD Software in the HDG and NAV Buttons of the Saitek Pro Multi Panel

So now SPAD is sending those keystrokes? So far FSUIPC has nothing to do with it. Correct?

- Pushing the buttons, I can see the Knob Pull & Push actions and hear their sound but with no change in the FCU or PFD panels.

So SPAD isn't doing what you asked? Where is FSUIPC involved?

- Hitting the key combination on the Keyboard, I can see the Knob Pull & Push actions and hear their sound but with no change in the FCU or PFD panels.

- Programmed these commands using SPAD Software in the HDG and NAV Buttons of the Saitek Pro Multi Panel

- Pushing the buttons, I can see the Knob Pull & Push actions and hear their sound but with no change in the FCU or PFD panels.

Right. I am now thoroughly lost. Sorry. You have a panel which can be operated by keystrokes. So why not assign buttons to send those keystrokes? Where do mouse macros come into it, and what is SPAD being used for?

Accordingly, it seems that the FSUIPC mouse macro (Trap) did not capture the function of Pull & Push, it just captured the moving of the switch !!! Though using the mouse left button for push and Right for Pull is working fine and change from HDG to NAV in both scenarios

As the documentation tells you, in some implementations it is not the simple click of the mouse which finishes the action. The detection of the code to be called is the automatic part of the FSUIPC programming facility, but then, sometimes, you have to experiment with the parameter part too. Some switches need to see both mouse button press and release, separately, and so on. The documentation of the mouse macro facility gives a list of the parameters you can add, manually, to get different actions. And you may need more than one, in which case you may also have to edit them into the macro manually (to make a multi-line macro).

But why even try using mouse macros if keypresses work? It doesn't make sense to me at all.

14715063 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

14715063 .. Key not programmed -- passed on to FS

14715063 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

14715063 .. Key not programmed -- passed on to FS

14715063 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

14715063 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc

14715063 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc,31

...

14716907 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

14716907 .. Key not programmed -- passed on to FS

14716907 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

14716907 .. Key not programmed -- passed on to FS

14716907 KEYDOWN: VK=119, Waiting=0, Repeat=N, Shifts=3

14716907 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc,31

You seem to have already programmed a double action of the Ctrl_Shift_F7 key. The '31' added to the macro call is one of the parameters I was talking about.-- it's the code for a single Right Click.

The Ctrl_Shift+F8 combination is just sending the second part of what the earlier one did. A single right click.

I don't know how you arrived at these, but more to the point, if the default Wilco commands are Ctrl+Shift+F7 and F8 as you state, and they work, why even try to reprogram the same key combinations to use Mouse Macros which you'll need to experiment with in any case to make work?

Pete

[Royal Eagle]

Appreciate your reply Pete, And apologies for causing a confusion !! I guess it goes this way to start the discussion ;-),

I hope the following can clarify your questions:

Pete : That statement has me completely confused I'm afraid. If the aircraft panel res[ponds to known keyboard combinations as you say, why would you need to resort to the FSUIPC mouse macro facilities? Why not use the keyboard combinations provided? Seems much cleaner, even if the panel is written in a way which will support mouse macros

I agree with you, if the panel switches has a Wilco key commands, and its working, why not just use the keystrokes ..... simply cause I have the Saitek Pro Flight Panel, and it has this push buttons labeled as HDG, NAV, ALT, IAS, VS and APP, so I wanted to use it to make it as convenient as possible, and more realistic ....

Pete: Arh, is SPAD that freeware program for interfacing the Saitek gear to FS or FSUIPC?

So what actual 'commands' are you making SPAD send? Keys or buttons or offset changes or what?

Sorry, something is very confused there. Mouse macros don't have key comninations. Mouse macros instigate calls directly in C/C++ coded gauges. Please explain what you mean.

So this merely confirms that the default Wilco Commands (Ctrl +Shift +F7 & Ctrl +Shift +F8) work as Wilco intended, I assume?

SPAD as I understood by reading through your forum, and Maxximas should do the job !! because Saitek doesn't provide any editing or configuration options for the Pro Panels, and the default Saitek buttons doesn't operate these function (HDG, NAV ...etc) as required in Wilco Panel (It does in the default FSX Aircrafts like B737 and A321)

I used the Key Emulation option in SPAD Panel Configuration to send these commands without doing anything in FSUIPC, but its not working.

Using the FSUIPC Logging (Button and key operations &Event (non-axis controls)) it gives (This Key is not programmed in FSUIPC, send to FS), and i couldn't find the right Control set from the FSUIPC menu that describes or emulate these functions

So I used the Mouse Macro to emulate the functions hoping FSUIPC will recognize the Saitek buttons .... and as I explained, it just emulate the Wilco HDG & NAV Pull & Push actions without changing the functions.

Using Logitech G13, or BELKIN n52et Game Pad to program these functions and Key Strokes worked .... but I wanna use the buttons on the Saitek Pro Flight Panel as I said earlier (its there and labeled and on the same control panel, so why not use it!!!)

Pete: You seem to have already programmed a double action of the Ctrl_Shift_F7 key. The '31' added to the macro call is one of the parameters I was talking about.-- it's the code for a single Right Click.

The Ctrl_Shift+F8 combination is just sending the second part of what the earlier one did. A single right click.

I see it ...!!, ok i will check to remove the double action ...

Let me send you the following:

1. FSUIPC Logging with only the default Saitek Pro Multi Panel Configuration (FSUIPC Offset Change Option) and no mouse macros (Not working at all, nothing happens)

********* FSUIPC4, Version 4.60a by Pete Dowson *********

User Name="Mohammad Byouk"

User Addr="mbeauke@yahoo.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

375844 System time = 21/12/2010 16:48:59, Simulator time = 09:58:51 (07:58Z)

375844 LogOptions changed, now 60000000 00000001

376750 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

376750 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

376969 *** EVENT: Cntrl= 66106 (0x0001023a), Param= 0 (0x00000000) AP_PANEL_HEADING_ON

377750 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

377750 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

378578 *** EVENT: Cntrl= 65811 (0x00010113), Param= 0 (0x00000000) AP_NAV1_HOLD_ON

378750 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

378750 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

379734 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

379734 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

380750 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

380750 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

384281 LogOptions changed, now 00000000 00000001

2. FSUIPC Logging with (Ctrl_Shift_F7 & Ctrl_Shift_F8) programmed in Saitek Pro Multi Panel using SPAD Configuration (Keyboard Emulation Option) and no mouse macros (Not working, just button Push & Pull Actions)

********* FSUIPC4, Version 4.60a by Pete Dowson *********

User Name="Mohammad Byouk"

User Addr="mbeauke@yahoo.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

806703 System time = 21/12/2010 16:57:48, Simulator time = 10:06:04 (08:06Z)

806703 LogOptions changed, now 60000000 00000001

806813 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

806813 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

807828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

807828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

808313 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

808313 .. Key not programmed -- passed on to FS

808313 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

808313 .. Key not programmed -- passed on to FS

808313 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

808313 .. Key not programmed -- passed on to FS

808313 KEYUP: VK=118, Waiting=0

808313 KEYUP: VK=17, Waiting=0

808313 KEYUP: VK=16, Waiting=0

808828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

808828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

809219 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

809219 .. Key not programmed -- passed on to FS

809219 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

809219 .. Key not programmed -- passed on to FS

809219 KEYDOWN: VK=119, Waiting=0, Repeat=N, Shifts=3

809219 .. Key not programmed -- passed on to FS

809219 KEYUP: VK=119, Waiting=0

809219 KEYUP: VK=17, Waiting=0

809219 KEYUP: VK=16, Waiting=0

809828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

809828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

810813 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

810813 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

815047 LogOptions changed, now 00000000 00000001

3. FSUIPC Logging with (Ctrl_Shift_F7 & Ctrl_Shift_F8) programmed in Saitek Pro Multi Panel using SPAD Configuration (Keyboard Emulation Option) with mouse macros (Not working, just button Push & Pull Actions)

********* FSUIPC4, Version 4.60a by Pete Dowson *********

User Name="Mohammad Byouk"

User Addr="mbeauke@yahoo.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

1165938 System time = 21/12/2010 17:03:47, Simulator time = 09:54:00 (07:54Z)

1165938 LogOptions changed, now 60000000 00000001

1166766 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1166766 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1167656 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

1167656 .. Key not programmed -- passed on to FS

1167656 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

1167656 .. Key not programmed -- passed on to FS

1167656 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

1167656 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc,31

1167656 .. This key is programmed in FSUIPC4 'Keys' options

1167656 KEYUP: VK=118, Waiting=0

1167656 KEYUP: VK=17, Waiting=0

1167656 KEYUP: VK=16, Waiting=0

1167750 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1167750 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1168750 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1168750 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1169719 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1169719 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1169891 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

1169891 .. Key not programmed -- passed on to FS

1169891 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

1169891 .. Key not programmed -- passed on to FS

1169891 KEYDOWN: VK=119, Waiting=0, Repeat=N, Shifts=3

1169891 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc

1169891 .. This key is programmed in FSUIPC4 'Keys' options

1169891 KEYUP: VK=119, Waiting=0

1169891 KEYUP: VK=17, Waiting=0

1169891 KEYUP: VK=16, Waiting=0

1170063 *** EVENT: Cntrl= 66709 (0x00010495), Param= 0 (0x00000000) AP_MAX_BANK_INC

1170734 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1170734 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1171719 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1171719 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1176578 LogOptions changed, now 00000000 00000001

4. FSUIPC Logging with (Ctrl_Shift_F7 & Ctrl_Shift_F8) programmed in BELKIN Game Pad with mouse macros (its working)

********* FSUIPC4, Version 4.60a by Pete Dowson *********

User Name="Mohammad Byouk"

User Addr="mbeauke@yahoo.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

1370031 System time = 21/12/2010 17:07:11, Simulator time = 09:57:06 (07:57Z)

1370031 LogOptions changed, now 60000000 00000001

1371016 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1371016 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1371984 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

1371984 .. Key not programmed -- passed on to FS

1371984 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3

1371984 .. Key not programmed -- passed on to FS

1371984 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

1371984 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc,31

1371984 .. This key is programmed in FSUIPC4 'Keys' options

1372031 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1372031 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1372031 KEYUP: VK=118, Waiting=0

1372031 KEYUP: VK=16, Waiting=0

1372031 KEYUP: VK=17, Waiting=0

1373031 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1373031 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1373609 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

1373609 .. Key not programmed -- passed on to FS

1373609 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3

1373609 .. Key not programmed -- passed on to FS

1373609 KEYDOWN: VK=119, Waiting=0, Repeat=N, Shifts=3

1373609 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc

1373609 .. This key is programmed in FSUIPC4 'Keys' options

1373734 KEYUP: VK=119, Waiting=0

1373734 KEYUP: VK=17, Waiting=0

1373734 KEYUP: VK=16, Waiting=0

1374000 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1374000 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1375016 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1375016 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1379500 LogOptions changed, now 00000000 00000001

5. FSUIPC Logging with (Ctrl_Shift_F7 & Ctrl_Shift_F8) programmed in BELKIN Game Pad without mouse macros (its working)

********* FSUIPC4, Version 4.60a by Pete Dowson *********

User Name="Mohammad Byouk"

User Addr="mbeauke@yahoo.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

1627813 System time = 21/12/2010 17:11:29, Simulator time = 09:55:03 (07:55Z)

1627813 LogOptions changed, now 60000000 00000001

1628172 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1628172 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1629219 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1629219 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1629938 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

1629938 .. Key not programmed -- passed on to FS

1629938 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3

1629938 .. Key not programmed -- passed on to FS

1629938 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

1629938 .. Key not programmed -- passed on to FS

1629984 KEYUP: VK=118, Waiting=0

1629984 KEYUP: VK=16, Waiting=0

1630031 KEYUP: VK=17, Waiting=0

1630266 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1630266 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1631203 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1631203 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1631391 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

1631391 .. Key not programmed -- passed on to FS

1631391 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3

1631391 .. Key not programmed -- passed on to FS

1631391 KEYDOWN: VK=119, Waiting=0, Repeat=N, Shifts=3

1631391 .. Key not programmed -- passed on to FS

1631484 KEYUP: VK=119, Waiting=0

1631484 KEYUP: VK=17, Waiting=0

1631484 KEYUP: VK=16, Waiting=0

1632266 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1632266 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1633203 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 16 (0x00000010) FUEL_SELECTOR_SET

1633203 *** EVENT: Cntrl= 66523 (0x000103db), Param= 16 (0x00000010) FUEL_SELECTOR_2_SET

1636781 LogOptions changed, now 00000000 00000001

[Pete Dowson]

So I used the Mouse Macro to emulate the functions hoping FSUIPC will recognize the Saitek buttons

Except for VRi and GoFlight, FSUIPC does not see buttons unless the device is recognised as a normal Joystick type device by Windows. If it was that type of device you wouldn't need SPAD. I was considering adding Saitek button support too, when they reneged on their licensing agreement for FSUIPC use.

Using Logitech G13, or BELKIN n52et Game Pad to program these functions and Key Strokes worked

Are they standard joystick type devices, or simply keyboard replacements?

1. FSUIPC Logging with only the default Saitek Pro Multi Panel Configuration (FSUIPC Offset Change Option) and no mouse macros (Not working at all, nothing happens)

That appears to be because Saitek's software is sending those specific FS controls. Neither FSUIPC nor SPAD is involved.

2. FSUIPC Logging with (Ctrl_Shift_F7 & Ctrl_Shift_F8) programmed in Saitek Pro Multi Panel using SPAD Configuration (Keyboard Emulation Option) and no mouse macros (Not working, just button Push & Pull Actions)

808313 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

808313 .. Key not programmed -- passed on to FS

808313 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

808313 .. Key not programmed -- passed on to FS

808313 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

808313 .. Key not programmed -- passed on to FS

808313 KEYUP: VK=118, Waiting=0

808313 KEYUP: VK=17, Waiting=0

808313 KEYUP: VK=16, Waiting=0

Ok. That looks correct EXCEPT that the key up parts are sent at exactly the same time as the keydown parts. Maybe there needs to actually be enough time for something to detect the keypress correctly? If it is SPAD doing this, can you not program it to send the press when you press the button, and the release when you release it?

I am combining the next two examples with the relevant parts only showing so you can see that they are identical except for the timing:

3. FSUIPC Logging with (Ctrl_Shift_F7 & Ctrl_Shift_F8) programmed in Saitek Pro Multi Panel using SPAD Configuration (Keyboard Emulation Option) with mouse macros (Not working, just button Push & Pull Actions)

1167656 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1

1167656 .. Key not programmed -- passed on to FS

1167656 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3

1167656 .. Key not programmed -- passed on to FS

1167656 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

1167656 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc,31

1167656 .. This key is programmed in FSUIPC4 'Keys' options

1167656 KEYUP: VK=118, Waiting=0

1167656 KEYUP: VK=17, Waiting=0

1167656 KEYUP: VK=16, Waiting=0

4. FSUIPC Logging with (Ctrl_Shift_F7 & Ctrl_Shift_F8) programmed in BELKIN Game Pad with mouse macros (its working)

1371984 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

1371984 .. Key not programmed -- passed on to FS

1371984 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3

1371984 .. Key not programmed -- passed on to FS

1371984 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

1371984 Macro: mouse action="A320IAE_feelThere.DLL":X34c40*X8bcc,31

1371984 .. This key is programmed in FSUIPC4 'Keys' options

1372031 KEYUP: VK=118, Waiting=0

1372031 KEYUP: VK=16, Waiting=0

1372031 KEYUP: VK=17, Waiting=0

The only difference between these two is the timing of the KEYUPs. In the one that works the KEY releases are following a little later. In the one which doesn't they are occurring in the same millisecond as the keydowns and the mouse macros.

I think the panel, is sensitive to both the key combination being pressed (which it won't see as you've programmed it to do something else -- send the mouse macro) but also the key release.

You either need to get SPAD to send the key releases later (eg when you release the button) -- in which case it should work without Mouse macros (and without FSUIPC being involved at all) -- or, maybe, if that's not possible, you could assign the key release to something else, something completely harmless, in FSUIPC, so the panel doesn't see it and therefore mess up its obedience of the mouse macro.

5. FSUIPC Logging with (Ctrl_Shift_F7 & Ctrl_Shift_F8) programmed in BELKIN Game Pad without mouse macros (its working)

1629938 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2

1629938 .. Key not programmed -- passed on to FS

1629938 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=3

1629938 .. Key not programmed -- passed on to FS

1629938 KEYDOWN: VK=118, Waiting=0, Repeat=N, Shifts=3

1629938 .. Key not programmed -- passed on to FS

1629984 KEYUP: VK=118, Waiting=0

1629984 KEYUP: VK=16, Waiting=0

1630031 KEYUP: VK=17, Waiting=0

Again illustrating the difference in timing of the release, only.

Pete

[Royal Eagle]

Noticed that ... The thing is that SPAD doesn't provide a timing or delay options when programing a keyboard emulation (BILKIN n52te - a programmable game keypad, offers this!!)...SPAD has just 2 option .. Short Click & Long Click .. I remember I tried both ....!!! let me double check, and see if i can do anything regarding the timing of release .....

[Pete Dowson]

Noticed that ... The thing is that SPAD doesn't provide a timing or delay options when programing a keyboard emulation (BILKIN n52te - a programmable game keypad, offers this!!)...SPAD has just 2 option .. Short Click & Long Click .. I remember I tried both ....!!! let me double check, and see if i can do anything regarding the timing of release .....

Or, as I suggested, simply assign the key release in FSUIPC to do something you don't care about, something completely innocuous.

Regards

Pete

[Royal Eagle]

Hi Pete,

Merry Xmas and Happy New Year ..

Apologies for taking a long time to reply ... I have used the programming functions in Bilkin n52te to emulate the functions I need .. for now, <br><br>One thing might be the cause of all of this which has to do with the USB power supply of the Saitek Pro Flight panels, It seems that I needed a voltage regulator to stabilize the power of the computer, .....I will give it another try later to check if the Siatek Multi Panel Buttons ...

Cheers

[Pete Dowson]

Merry Xmas and Happy New Year ..

Thank you. You too (at least the Happy New Year part ;-) )

Apologies for taking a long time to reply ... I have used the programming functions in Bilkin n52te to emulate the functions I need .. for now, <br><br>One thing might be the cause of all of this which has to do with the USB power supply of the Saitek Pro Flight panels, It seems that I needed a voltage regulator to stabilize the power of the computer, .....I will give it another try later to check if the Siatek Multi Panel Buttons ...

Okay.

Regards

Pete

[Thorsten Groß]

Hi everyone, hi Pete,

 

even though this thread is a bit older, I guess that it might be interesting to know a simple solution, as a research on the internet finds similar questions, but no answers.

 

I found a simple way that seems to work:

 

In SPAD, instead of assigning a key combination, you should assign a so-called "FSUPIC virtual joystick button", for example Joystick # 64, Button # 00, #01 and so on, for each desired function.

 

Then, open the FSUIPC dialog window and go to the "Buttons" tab. Select the Button you just created in SPAD, by simply clicking the button on the Saitek device. The assigned numbers will appear in FSUIPC.

 

Next, Chose the "Select for Keypress" option and then enter the keypress, for example Ctrl+Shift+F7. No Key should be entered on "release". The checkbox "Key press not to be held" should be checked, and "Key press to repeat" should be unchecked, as by default.

 

That's all and seems to work nicely with Wilco Airbus Evolution A319/320/321 as well as the Wilco A380. 

 

Greetings

Thorsten