nigelsimm

Thanks again Peter! The first line is set to toggle the ATC window so that there's a logic to the number of button presses for each ATC option (1 for option 1, and so on). Otherwise, it's press once for menu option 2, twice for option 3 etc... I decided to tweak the arrangement from my last post - having the commands sent on release of the ATC button was problematic with ATC sub-menus (eg: parking options) that appear automatically without closing the ATC window. I have now an arrangement on the 3 buttons on the left side of the CH Throttle: Button 0 - Toggles the ATC window and resets the offset. Button 9 - Increments the offset on press. Button 8 - Send the command on press and resets the offset on release. 10=P0,0,Cx010066C0,x00 11=P0,0,C65564,0 29=P0,9,Cx510066C0,x000A0001 30=B66C0=0 P0,8,C65564,0 31=B66C0=1 P0,8,C66172,0 32=B66C0=2 P0,8,C66173,0 33=B66C0=3 P0,8,C66174,0 34=B66C0=4 P0,8,C66175,0 35=B66C0=5 P0,8,C66176,0 36=B66C0=6 P0,8,C66177,0 37=B66C0=7 P0,8,C66178,0 38=B66C0=8 P0,8,C66179,0 39=B66C0=9 P0,8,C66180,0 40=B66C0=10 P0,8,C66181,0 41=U0,8,Cx010066C0,x00 It's all working as I wanted now. Thanks again for your advice. Regards, Nige

Got it! 10=P0,0,Cx010066C0,x00 11=P0,0,C65564,0 13=B66C0=0 U0,0,C65564,0 14=B66C0=1 U0,0,C66172,0 15=B66C0=2 U0,0,C66173,0 16=B66C0=3 U0,0,C66174,0 17=B66C0=4 U0,0,C66175,0 18=B66C0=5 U0,0,C66176,0 19=B66C0=6 U0,0,C66177,0 20=B66C0=7 U0,0,C66178,0 21=B66C0=8 U0,0,C66179,0 22=B66C0=9 U0,0,C66180,0 23=B66C0=10 U0,0,C66181,0 29=P0,9,Cx510066C0,x000A0001 Works fine now! Thanks v. much. Regards, Nige

Hi again! I just rechecked the syntax for this on page 24 of the Advanced Users manual and changed the fsuipc.ini entries accordingly: 10=P0,0,Cx010066C0,x00 11=P0,0,C65564,0 12=P0,9,Cx5100660C,x000A0001 13=B66C0=0 U0,0,C65564,0 14=B66C0=1 U0,0,C66172,0 15=B66C0=2 U0,0,C66173,0 16=B66C0=3 U0,0,C66174,0 17=B66C0=4 U0,0,C66175,0 18=B66C0=5 U0,0,C66176,0 19=B66C0=6 U0,0,C66177,0 20=B66C0=7 U0,0,C66178,0 21=B66C0=8 U0,0,C66179,0 22=B66C0=9 U0,0,C66180,0 23=B66C0=10 U0,0,C66181,0 But it's still not working. The offset doesn't look as though it's incrementing: 11144812 Button changed: bRef=0, Joy=0, Btn=0, Pressed 11144812 [buttons] 10=P0,0,Cx010066C0,x00 11144812 IPC Offsets Control: Ctrl=x0100, Length=1, Offset=66C0, Param=x0 11144812 [buttons] 11=P0,0,C65564,0 11144812 FS Control Sent: Ctrl=65564, Param=0 11149906 Button changed: bRef=0, Joy=0, Btn=9, Pressed 11149906 [buttons] 12=P0,9,Cx5100660C,x000A0001 11149906 IPC Offsets Control: Ctrl=x5100, Length=1, Offset=660C, Param=xA0001 11149906 [buttons] 29=P0,9,Cx5100660C,x000A0001 11149906 IPC Offsets Control: Ctrl=x5100, Length=1, Offset=660C, Param=xA0001 11150218 Button changed: bRef=0, Joy=0, Btn=9, Released 11150703 Button changed: bRef=0, Joy=0, Btn=9, Pressed 11150703 [buttons] 12=P0,9,Cx5100660C,x000A0001 11150703 IPC Offsets Control: Ctrl=x5100, Length=1, Offset=660C, Param=xA0001 11150703 [buttons] 29=P0,9,Cx5100660C,x000A0001 11150703 IPC Offsets Control: Ctrl=x5100, Length=1, Offset=660C, Param=xA0001 11151031 Button changed: bRef=0, Joy=0, Btn=9, Released 11151468 Button changed: bRef=0, Joy=0, Btn=9, Pressed 11151468 [buttons] 12=P0,9,Cx5100660C,x000A0001 11151468 IPC Offsets Control: Ctrl=x5100, Length=1, Offset=660C, Param=xA0001 11151468 [buttons] 29=P0,9,Cx5100660C,x000A0001 11151468 IPC Offsets Control: Ctrl=x5100, Length=1, Offset=660C, Param=xA0001 11151750 Button changed: bRef=0, Joy=0, Btn=9, Released 11152281 Button changed: bRef=0, Joy=0, Btn=9, Pressed 11152281 [buttons] 12=P0,9,Cx5100660C,x000A0001 11152281 IPC Offsets Control: Ctrl=x5100, Length=1, Offset=660C, Param=xA0001 11152281 [buttons] 29=P0,9,Cx5100660C,x000A0001 11152281 IPC Offsets Control: Ctrl=x5100, Length=1, Offset=660C, Param=xA0001 11152593 Button changed: bRef=0, Joy=0, Btn=9, Released 11153218 Button changed: bRef=0, Joy=0, Btn=0, Released 11153218 [buttons] 13=B66C0=0 U0,0,C65564,0 11153218 .... Offset check: x66C0/1 = 0? (0), Result = TRUE 11153218 FS Control Sent: Ctrl=65564, Param=0 11153218 [buttons] 14=B66C0=1 U0,0,C66172,0 11153218 .... Offset check: x66C0/1 = 1? (0), Result = FALSE 11153218 [buttons] 15=B66C0=2 U0,0,C66173,0 11153218 .... Offset check: x66C0/1 = 2? (0), Result = FALSE 11153218 [buttons] 16=B66C0=3 U0,0,C66174,0 11153218 .... Offset check: x66C0/1 = 3? (0), Result = FALSE 11153218 [buttons] 17=B66C0=4 U0,0,C66175,0 11153218 .... Offset check: x66C0/1 = 4? (0), Result = FALSE 11153218 [buttons] 18=B66C0=5 U0,0,C66176,0 11153218 .... Offset check: x66C0/1 = 5? (0), Result = FALSE 11153218 [buttons] 19=B66C0=6 U0,0,C66177,0 11153218 .... Offset check: x66C0/1 = 6? (0), Result = FALSE 11153218 [buttons] 20=B66C0=7 U0,0,C66178,0 11153218 .... Offset check: x66C0/1 = 7? (0), Result = FALSE 11153218 [buttons] 21=B66C0=8 U0,0,C66179,0 11153218 .... Offset check: x66C0/1 = 8? (0), Result = FALSE 11153218 [buttons] 22=B66C0=9 U0,0,C66180,0 11153218 .... Offset check: x66C0/1 = 9? (0), Result = FALSE 11153218 [buttons] 23=B66C0=10 U0,0,C66181,0 11153218 .... Offset check: x66C0/1 = 10? (0), Result = FALSE

Pete, Thanks for the reply. I understand the principle, but the syntax is defeating me at the moment. Yes, I do need to increment the offset using a different button, but how to pass the results of those presses to the ATC button on release? This is what I have so far, but according to the log the offset never changes from the first entry. Where have I gone wrong? Logic tells me that I need to pass on the value of the offset to the conditional lines on the ATC button release, rather than using offset increment, but I'm at a loss as to how to do that! 10=P0,0,Cx010066C0,x00 11=P0,0,C65564,0 12=U0,0,Cx5100660C,x000A0001 13=B66C0=0 U0,0,C65564,0 14=B66C0=1 U0,0,C66172,0 15=B66C0=2 U0,0,C66173,0 16=B66C0=3 U0,0,C66174,0 17=B66C0=4 U0,0,C66175,0 18=B66C0=5 U0,0,C66176,0 19=B66C0=6 U0,0,C66177,0 20=B66C0=7 U0,0,C66178,0 21=B66C0=8 U0,0,C66179,0 22=B66C0=9 U0,0,C66180,0 23=B66C0=10 U0,0,C66181,0 24=P0,9,Cx5100660C,x000A0001

FSUIPC Version: 3.98a FS Version: 9.1 Hardware: CH Yoke OS: Windows XP (SP3) Hello, me again! This is what I'm trying to achieve: 1. Press button on yoke to display ATC window 2. Press another button on yoke the required number of times to select an ATC menu option (eg: press button twice for option 3 etc...) This is what I have so far, from my FSUIPC.ini [buttons] section: 12=P0,9,Cx510066C0,x00090001 13=B66C0=0 P0,9,C66172,0 14=B66C0=1 P0,9,C66173,0 15=B66C0=2 P0,9,C66174,0 16=B66C0=3 P0,9,C66175,0 17=B66C0=4 P0,9,C66176,0 18=B66C0=5 P0,9,C66177,0 19=B66C0=6 P0,9,C66178,0 20=B66C0=7 P0,9,C66179,0 21=B66C0=8 P0,9,C66180,0 22=B66C0=9 P0,9,C66181,0 This works to a degree, but of course, after each menu option has been chosen the offset needs to be cleared, or reset (I think), so that all the options on any subsequent menu are available. Do I need a line after each button to reset this (example below), or could I/should I use another method? 19=B66C0=6 P0,9,C66178,0 20=B66C0=6 U0,9,[reset offset],0 Any advice gratefully received! Thanks Nige

Peter, The penny just dropped! I started the log (buttons and key presses) and could clearly see that when I move the switch to the up ("on") position, FSUIPC detected a PRESS of button 64,0 and ran the macro. I could also see that when I moved the switch to the down ("off") position, FSUIPC recorded a RELEASE of button 64,0. So, I assigned the same macro to the release option of button 64,0 and all works fine. Sorry to have bothered you. I had failed to grasp the logic, but I'm there now! Thanks Nige

Peter, Thanks for your reply. The aircraft doesn't take any notice of FS's standard battery switch, no. Otherwise I wouldn't be attempting to use a far more complex method of trying to achieve what I want! With regard to the switch - In short, only moving the rocker to the "UP" position does anything - ie: If the battery is off, then the UP switch turns it on. My typo at step 3 (sorry) it should say "off" where it says on. The down movement of the switch doesn't trigger anything. By default, the SAITEK switch panel uses standard FS controls for its functions. SPAD allows one to use either keyboard shortcuts or virtual buttons to modify this behaviour. Since I can find no keyboard command for the PIC 737 Master battery, and the default behaviour of the panel does nothing, I had thought that a way around the issue would be to use a virtual button and a mouse macro. I have tried assigning the same Virtual Button to the macro, but with the same effect. The plane is loaded cold and dark, so the Master Battery is OFF. The rocker switch on the panel is in the down (Off) position. I press the rocker to move it to the up (ON) position and the Master Battery turns ON. I then press the switch to the Down (off) position and nothing happens. I then press the rocker to move the switch to the up (On) position and the battery turns off. So, yes I have to rock the switch twice for anything to happen. The SPAD option "Event when switched ON" refers to the physical position of the button on the panel (on = Up position). The option allows one to assign either a keyboard shortcut or a virtual button (to bypass the default behaviour). I have assigned this to Joystick 64, button 0, which in FSUIPC is in turn assigned to the MasterBattery mouse macro. The "Event when switched OFF" refers to the physical position of the button when it it "down" (off). I have also assigned this to Joystick 64, button 0, and have also tried assigning it to Joystick 64, button 1 as per my original post. I'll send a log later. Do you need all options ticked for the log, or just specific ones? Thanks again Nige

FSUIPC Version: 3.98a FS Version: 9.1 Hardware: Saitek Switch Panel Hardware Driver: SPAD (version 0.41) Aircraft: PIC 737 OS: Windows XP (SP3) Hi All! I wonder if anyone can help. I'm trying to program the Saitek switch panel's Master Battery switch. It's a rocker switch (like a light switch - up and down positions). I've had some success with it so far - I created a mouse macro, which worked when tested using the TAB key, and also worked when I assigned it to a "regular" push button on my CH Yoke. (press the yoke button = Battery On. Press the yoke button again = Battery Off). I then sent a virtual joystick button from SPAD ("Event when switched ON"), (Joystick 64, button 0) to FSUIPC and assigned the macro to this virtual joystick button in FSUIPC. I then assigned another virtual button in SPAD ("Event when switched OFF"), (Joystick 64, button1 ) and assigned the macro to this button in FSUIPC. This is what happens: 1. When I move the SAITEK switch panel Master Battery switch to the "Up" (on) position, the Master battery switches on in the sim. 2. When I move the SAITEK switch panel Master Battery switch to the "Down" (off) position, nothing happens in the sim (ie: battery stays on) 3. If I then move the SAITEK switch panel Master Battery switch back to the "Up" (on) position, the Master battery switches on in the sim, and... repeat from step 2. Have I misunderstood the concept of Virtual Joystick buttons and mouse macros, or am I missing something? Any advice gratefully received! Thanks Nige

Hi! Just got WideFS - I also have a registered version of FSUIPC (3.5.3). I've managed to get fsmeteo working, and my VA's Offline Server Program, and ShowText is working a treat too! However, whenever I try to connect Flight Deck Companion Live Cockpit, I get an error message: "NO Hotkey Slots...Wrong Version of FSUIPC Installed...Unable to continue!". FDC work fine on the host pc, and before connection it can detect my current airport. Am I missing something, or does WideFS not work with FDC? Thanks