gr8guitar

Hello Mr. Dowson, earlier you mentioned that if I write a lua for mouse movements that I would share it. I haven't really delved into that yet. But using Autohotkey, I've been happy with using a very simple code. Note that one of the function keys (F9-F12), in this case, needs to be activated first: f9:: pix = 1 f10:: pix = 5 f11:: pix = 40 f12:: pix = 100 ;using 2 rotary switches each with pushbutton (1st: buttons 1,2,5 and 2nd: 3,4,6) ;=x,y,s,r: X(positive >),Y(positive v),Speed (0=fastest,100=slowest),Offset/relative if = "r" 1joy1:: mousemove, -pix,0,0,r ;left 1joy2:: mousemove, pix,0,0,r ;right 1joy3:: mousemove, 0,pix,0,r ;down 1joy4:: mousemove 0,-pix,0,r ;up 1joy5:: MouseClick, left 1joy6:: MouseClick, right return ... back to flying.

Hello, I recently installed CaptainSim 757 for FS2004(FS9) and FSUIPC quit working. I can see it working when I go to the menu and select modules and I can see the activation of the buttons, etc., however, in the fs itself, no reaction to button activation, no traffic display and VRInsight and SPAD (for Saitek) both say FSUIPC is not running, what do you recommend? I did reboot and ran the default Cessna 172 but no change. Thanks. Nevermind, I deleted fsuipc.dll and re-installed the dll, version 3.000e (or whatever the latest is, 3.999n) and it worked, strange ! And CS757 is a strange program, can't get VRinsight CDU or FSUIPC for mouse macros to work. Oddly, I can get Saitek's autopilot/radios to work but AP not reflected on panel but radios are. Good thing it was cheap! Will see if I can marry 767PIC and CS757 ... I believe that's what edetroit on youtube has done. ****************************************** An update. I now have a way to assign joystick buttons to Captain Sim's 757 (FS2004/FS9). There are 3 ways that I know of to access the gauge (if it's xml). 1) Open the .CAB and see the xml's. 2) Use Blackbox 3, it's free. 3) Use FSPanel Studio, fastest method. In any case, I assigned keys in the .lua or .xml (I uncab and copy contents to a folder, could recab but don't) and then assign buttons to the keys using FSUIPC. I don't know if joystick buttons can be assigned in xml directly, haven't found a method yet. To assign a key, say "J", use: <Keys> <On Key="J"> do stuff </On> </Keys> or <On Key="74">, to use say, [sH][J] = 74 + 256 so... <On Key="330">, [CT][J] is 74+256+256 ="586" [CT][sH][J] is 74+256+256+256="842". Also, for some reason, this only works at the end of an .xml files, after the <Mouse> do stuff </Mouse>. Now I can finally use hardware instead of mouse movements.

An update, not sure what's going on with using PID so far. It works great as far as 1/4 wave damping and holds fairly well but I'm not able to get the critical damp desired. 1/4 wave damping is not a nice way to fly. So far my PID is a 1st order differential equation (DE) and my research seems to indicate that critical damping is 2nd order DE. This requires finding out the undamped natural frequency. WOH !!! and descreting a 2nd order DE in Excel - oh boy! I can see that the flight sim' autopilot does a good job of it though even though it seems that a person can only modify (in aircraft.cfg): nav_proportional_control, nav_integrator+control, etc. I don't' know what max_bank_acceleration/velocity does. So I'm not sure how the flight sim (FS9) is able to do this so well. When I fly in my real aircraft, I lead reducing the bank by the amount of heading difference that is left. As an example, if in my turn and I'm banking 10°, I'll begin to level off when my desired heading is within 10°. Not sure how to do this in Excel(VBA)/VB6 and use traditional PID. If there are parameters in FSUIPC that can assist, please let me know. Again, very pleased that FSUIPC allows me to test this. --- another update in case it might help someone else. I came up with what I call "gr8guitar smoothing." Not too technical and not sure how it would work with pneumatic controllers but using Excel: Output = p + i + d ' turn rate derived from GPS, Turn rate limit: if abs(TurnRate)>=3 then ' 3 deg per sec Output = -Output * .2 ' .2 seems to work well for turn rate limit end if ' gr8guitar smoothing if abs(Error)<= 10 then ' Error is setpoint heading vs. actual heading Output = Error/10*Output ' thought of this after I wrote the above and works surprising well end if ' still curious how FS does this and their PID algorithm ' aileron linkage required from stepper motor to the yoke to sufficiently move the real airplane's ailerons Output = Output *5.2 In any case, I can at least more forward and not worry about the damping ratio, 2n order DE. <whew>

Of course ! I did do a search (find) of "aileron position"and it ONLY showed 0BB8 up. I did not do a search of "aileron" by itself as I thought I was only interested in the aileron's position. I realize you can't possibly know all the offsets, just thought I'd ask in case I did miss something. Thanks for your time and info, always grealy appreciated. So glad for FSUIPC, wished I messed with it years ago. Heres' what's going to happen. I can now see and modify the PID parameters and watch the result in FS9. Next I'll being using a DC step motor connected to my yoke and see how it controls the FS9. Upon successful application of that, I will take the DC step motor and attach it to my airplane's (actually my brother-inlaw's) yoke and test the heading changes. It doesn't have an autopilot so here's perhaps an alternative for those long trips I take. Seems a bit bizarre, I agree, but worth a try.

Chill out please, I wasn't upset and more importantantly I was able to use heading (being True Heading) and applying Magnetic Variance to get the gyro compass (I wasn't concerned about drift - turned it off for testing), so I was able to get the info needed albeit, a round-about way I'll admit. You are right in that I did not catch the difference between 64 bit floating and 64 bit fixed. If the explanation of the datatypes are shown, please tell me where? In addition, as I may have mentioned before, I am now using FSUIPC, along with Excel to apply PID control theory. It took some reading up how to do charts of live data but got there. My question/observation is this: When I read 0BB8 (Aileron Position Indicator), the manual says: (may be adjusted from input), which would be fine (cuz not using joystick - unplugged) however, When I'm not sending 0BB8 info, the reading of 0BB8 also shows 0 even after in autopilot and making a heading bug change. Is there a direct reading of the actual aileron displacement? I suppose banking info might work but like to see direct aileron position. My PID is working ok, per 1/f4 wave damping but I would it rather control like the PID of FS and smooth out as the desired heading is near. I wanted to plot what the aileron position itself is doing.

Cool, thanks!

Hello, well I hope you know that I DID read and I also used FSInterrogate which suggests the same info. But it does not work. I even derived information from the FSUIPC_SDK's file ReadThisVB.txt by Stuart Browne and I was able to get the altitude (0570) to work great but not 2B00. This is what I attempted (plus other modifications of * 360, π/180,180/π,65536 etc., - to no avail): Dim HI64 As Currency Dim HI As Double If FSUIPC_Read(&H2B00, 8, VarPtr(HI64), dwResult) Then If FSUIPC_Process(dwResult) Then HI = HI64 * 10000# Range("a7") = HI I get some really large number (despite the HI64 * 10000# => converts from currency to double) and that would be okay if that number was linear to the actual heading - then I could determine the formula. I found out that when I go from a heading of 360° and turning right back to 360° that the difference say, between 360° to 1° is very relatively large number compared to 359° to 360°. As I turned right, I took readings of every 30° and looked at the numbers received and then took the difference and the resultant started large but got progressively smaller as I came about to 360°. By the way, here is the code for altitude and again, it works great: Dim Altitude64 As Currency Dim Altitude As Double If FSUIPC_Read(&H570, 8, VarPtr(Altitude64), dwResult) Then If FSUIPC_Process(dwResult) Then Altitude = Altitude64 * 10000# Altitude = Altitude * 3.28084 / (65536# * 65536#) Range("a5") = Altitude Also, I have no idea what Heading (0580) is sensing. I have the heading bug set at 330°, the heading indicator shows 330°, the whiskey compass show 330° [shft]-z shows 330° but FSInterrogate shows 350° and input to spreadsheet shows 350°, I suspect it's true heading since I have a magvar of 23° but then shouldn't I be reading 353°, is this only viable for slew mode? ... so a bit confused. Still confused about why the 2B00 doesn't work and what the [shft]-z shows is a mag var of 23° but the FSUIPC/FSInterrogate is showing 20° so that makes sense now - sort of (I was in KSEA area). Heading is True Heading. So given the MagVar and TH, I can derive the Mag Heading, would have rather received it directly though. As I may have stated before, it's too bad I got into FSUIPC so late. It wasn't until I got unhappy with Saitek really that made me motivated to learn FSUIPC. Quite happy with FSUIPC too! Not only do I have the button controls I like, ...NOW ..... I can do something else that I've been wanting to do for a very long time and that is test/teach PID controls. There are various simulators out there, including for Excel but none of them, within reasonable cost, can interract with "real" world. With FS2004, FSUIPC and Excel, I can show and see not only the results through the flight sim, I can see the interaction through the charts in "real" time.

okay.... what is a crikey? Yes, I use Excel for just about everything !!! Probably the only thing I don't use it for is word-processing. I use it for color analysis to ensure consistent pigment , real GPS input for my own "FMC", HMI for PLC programming, and now that I can receive joystick input, found a really cheap way for I/O. Plus many, many other uses. If Mr. Dowson reads, this, I was accessing offset 2B00 (gyro compass) and I found out that as I turn around, the numbers received vs degree heading is not linear, what is the formula to get from FS so I can get degrees for heading? Thanks.

Hello Anyone, did you ever get FSUIPC to communicate with Excel's VBA? I got it to work with VB6 but not Excel. I don't have any runtime errors reported but also no data is coming in. I keep getting an error: dwResult = 9, which is "link not open." Thanks. Oops, nevermind, got it to work! 1) deleted the BitwiseOps.bas, 2) cleaned up FSUIPC.bas and General.bas and instead of using the form timer object (required by VB6), I call(ed) my module. I haven't attempted to Write to FSUIPC but that's next.

Okay, thank you for the information. :)

1) there isn't a problem, just curious. 2) I was using the logging part of FSUIPC, at looking that the offset that represents True Airspeed (TAS). Here's why: In the piston aircraft, there is a bug that allows a person to find TAS based on setting the outside air temp (in C) against the pressure altitude. Well, i can'r really read the dial independent of screen resolution as I was adjusting so I wanted a verification by seeing the logging info. I'm not using a separate program.

Hello again, I do have another question. Here is the setup. When I first started using FSUIPC I must admit in my anxiousness and not understanding much of the setup process, for mouse macros I would basically make and name the mouse macros the same as the button assignment (for 767PIC) so I have a lot of macros nearly for each button action. I aw the message that I could keep the same but I didn't really get it at that time. When I went to program the B732ADV, I realize I didn't need to do that. I made one macro name and then proceeded to assign the buttons. Well... I am thinking about going back through the 767PIC macros and making it so I just have one macro name. I came across something that has me confused, below is a macro, "10= ..." in particular: [Macros] Module="B767Woh.GAU" 1=767PIC_RWY=RX10a0*X5500 2=767PIC-TURNOFF=RX10de*X5500 3=767PIC_POSITION=RX116b*X5500 4=767PIC_RED=RX1186*X5500 5=767PIC_WHT=RX11a1*X5500 6=767PIC_W-=RX11bc*X5500 7=767PIC_LT_S=RX111c*X5500 8=767PIC_LANDING=RX11fc*X5500 Module1="B767Wpedestal.GAU" 9=767PIC_FIRE_TEST=R1:X2b80*Xa190 10=767PIC_PARK_BRK=R1:1 Module2="767FMC.GAU" 11=767PIC_INIT/REF=R2:X26270*Xa190 The parking brake with the R1:1 (especially the last "1") has me confused. I saw on page 41 the mouse flags but I did not see the # "1", what does it mean and does it know the info like RXaaaa*Xbbbb? Also I wanted to read True Airspeed (x02b8 - i think). I got it read but it I see that it needs to be divided by 128, is there way way to do that automatically (by programming it)?

ah.... okay, thanks. BTW, fully tested Tinmouse II with FSUIPC's direct calibration and works just fine. I see I have to (choose to) come up with a way to have mechanical detents for each aircraft type.

I was trying to say ugh, because I got tunnel vision and 1) didn't see the Flaps options and 2) didn't see page 47 explaining the ranges. I have the flaps working perfectly now with the Joystick Calibration method. I was using a small joystick, again for testing. I normally use Saitek's TQ's for nearly everything else the Yoke doesn't do so self-centering isn't normally an issue. As far as using the [Axis], it too is working but not perfectly but it may be the joystick actuation as it's not very precise. I may need to shift the difference between the D's and the U's values but will worry about that when I get to setting up the Saitek TQ's. So in conclusion, I have the Flaps working with FSUIPC, but except for the rare caes, like Tinmouse II, I just normally use FS assignment for the flaps. It's good to have FSUIPC for those rare case though :). I was wondering if you've seen that video I mentioned above. I am curious what software made that panel. edetroit mentions Edward Cox (not available) and I've searched the Internet, so far, haven't found it.

ugh, saw the explanation on pg 47, so finally, have you seen that virtual cockpit and where it comes from?

wow, caught my own oops! Found out I didn't assign "flaps" after sending direct to FSUIPC. All good. I still am wondering about the range question I had above, mainly because some software requires using the mouse to extend and retract the flaps. And also, have you seen this video on youtube? youtube.com/watch?v=Z1q5BhgmCv4. Do you recognize that virtual cockpit? Supposedly FS9 is being used. I asked edetroit but no response.. I would like to obtain/purchse if possible. I hadn't been a fan of vc until I saw that video.

ah... good catch!!! Well, I corrected and reloaded, re-looked at the ini file and you were correct (as usual), the values remained. The thing is, it's still not working. I move the joystick axis, in this case just using Y (removed elevator option in FS). After I reload, I would assume that the flaps would move somewhere in the middle since the joystick is self-centering (since normally used for elevator) but nothing happens. Also, on the Axis Assignment page, I see "Setup to 10 ranges for actions." I could see that this effects what I tried to do with the : 0=2Y,256 1=2Y,D,-16383,-12743,65758,0 2=2Y,D,-12742,-9104,65758,0 etc. What can this actually do? I saw a picture of it on page 44 of the users manual but no explanation, and I did not see anything about it in the Adv. manual, or I may have missed it somehow, like the ','

Hello, well I tried to use FSUIPC joystick calibration to make the flaps functional with no luck. I then hand-typed the following: FlapStarts=-16384-16219,-15450,-12975,-6980,-573,4606,15600,16217 FlapEnds=-16256,-16200,-15417,-12950,-6950,-550,4644,15650,16384 Flaps=-16384,16384 FlapDetents=Yes per the example and I when I reloaded, I would get the following: FlapStarts=-16384,-15450,-12975,-6980,-573,4606,15600,16217 FlapEnds=-16256,-15450,-12975,-6980,-573,4606,15600,16217 it would remove the other pair of -16219, -16200 and reset the Ends the same with the Starts (???). I then tried this: [Axes] 0=2Y,256 1=2Y,D,-16383,-12743,65758,0 2=2Y,D,-12742,-9104,65758,0 3=2Y,D,-9103,-5463,65758,0 4=2Y,D,-5462,-1820,65758,0 5=2Y,D,-1819,1819,65758,0 6=2Y,D,1822,5460,65758,0 7=2Y,D,5461,9101,65758,0 8=2Y,D,9104,12742,65758,0 9=2Y,D,12743,16383,65758,0 10=2Y,U,16383,12745,65759,0 11=2Y,U,12742,9104,65759,0 12=2Y,U,9101,5463,65759,0 13=2Y,U,5460,1822,65759,0 14=2Y,U,1819,-1819,65759,0 15=2Y,U,-1822,-5463,65759,0 16=2Y,U,-5464,-9103,65759,0 17=2Y,U,-9104,-12742,65759, But that only worked partially. i747 and Tinmouse don't seem to respond to the FS flap axis and I normally have assigned but require the mouse ....

Okay, lol. I was trying. Thanks :). Alright back to the rotary switches/buttons. Here is what I came up for using 2 rotary switches and 2 pushbuttons: With this scheme, 1 rotary switch selects a value, the other inc/dec as needed. 1 pb to select airspeed bugs and the other for dimmers. The below is for 2 airspeed bugs and 2 panel dimmers: 116=P2,2,Cx610066C0,x00090001 ;6100 -=>DECREMENT 66C0,MAX=9,STEP=1 117=P2,3,Cx510066C0,x00090001 ;5100 -=>INCREMENT 118=B66C0=1 P2,32,C1003,3841 ;SET EADI FLAG 119=B66C0=1 P2,32,C1004,4353 ;CLR ASB1 FLAG 120=B66C0=1 P2,32,C1004,3842 ;CLR EHSI FLAG 121=B66C0=1 P2,32,C1004,4354 ;CLR ASB2 FLAG 122=CP(F+15,1)2,0,CM56:1,0 ;CHK 15,1 SET,ON PRESS OF 2,0 THEN RUN CM56:1(EADI DEC) 123=CP(F+15,1)2,1,CM56:2,0 ;CHK 15,1 SET,ON PRESS OF 2,1 THEN RUN CM56:2(EADI INC) 124=B66C0=1 P2,38,C1004,3841 ;CLR EADI FLAG 125=B66C0=1 P2,38,C1003,4353 ;SET ASB1 FLAG 126=B66C0=1 P2,38,C1004,3842 ;CLR EHSI FLAG 127=B66C0=1 P2,38,C1004,4354 ;CLR ASB2 FLAG 128=CP(F+17,1)2,0,CM49:1,0 ;CHK 17,1 SET,ON PRESS OF 2,0 THEN RUN CM49:1(ASB1 DEC) 129=CP(F+17,1)2,1,CM49:2,0 ;CHK 17,1 SET,ON PRESS OF 2,1 THEN RUN CM49:2(ASB1 INC) 130=B66C0=2 P2,32,C1003,3842 ;SET EHSI FLAG 131=B66C0=2 P2,32,C1004,4354 ;CLR ASB2 FLAG 132=B66C0=2 P2,32,C1004,3841 ;CLR EADI FLAG 133=B66C0=2 P2,32,C1004,4353 ;CLR ASB1 FLAG 134=CP(F+15,2)2,0,CM56:3,0 ;CHK 15,2 SET,ON PRESS OF 2,0 THEN RUN CM56:1(EHSI DEC) 135=CP(F+15,2)2,1,CM56:4,0 ;CHK 15,2 SET,ON PRESS OF 2,1 THEN RUN CM56:2(EHSI INC) 136=B66C0=2 P2,38,C1004,3842 ;CLR EHSI FLAG 137=B66C0=2 P2,38,C1003,4354 ;SET ASB2 FLAG 138=B66C0=2 P2,38,C1004,3841 ;CLR EADI FLAG 139=B66C0=2 P2,38,C1004,4353 ;CLR ASB1 FLAG 140=CP(F+17,2)2,0,CM50:1,0 ;CHK 17,2 SET,ON PRESS OF 2,0 THEN RUN CM50:1(ASB2 DEC) 141=CP(F+17,2)2,1,CM50:2,0 ;CHK 17,2 SET,ON PRESS OF 2,1 THEN RUN CM50:2(ASB2 INC) I realize there are a lot of remarks but it's to help me keep it straight. I believe it's fairly clean code (with what I know). As I add airspeed bugs (ASB3-5) and more dimmers (EICAS-U&L), I believe all I'll need to do is take care of the flags, pb's and respective macros. This was a test-run and it ran great for me. And one doesn't affect the other but I do have to hit one of the pb's to make active. I really like being able to use 66C0 (etc.) and the flags(256*x+y). That was thinking way ahead for FSUIPC and am in great appreciation for it. Thanks Mr. Dowson for FSUIPC!

Yes, the 66C0 is changing beautifully. Right now as I've mentioned before, the airspeed bugs are working great! I can select between airspeed bugs 1-5 and increment/decrement fine with the code up above using only 12 lines of code. I would also like to be able (recall with only 2 rotary switches available- and for testing, using keys for now) use one rotary switch to be able to select values of 66C0, so far working great, and use the other rotary switch to be able to increment/decrement, also working great. But I would like to be able to select using a button (key) for the airspeed bugs1-5( using B66C0=1-5), and then be able to select 1-4 (using B66C0=1-4) for the brightness options with a different button (key for now) keeping the current increment/decrement rotary switch (keys for now). I hope I've explained it correctly. Again, currently for the airspeed bugs, it's working just fine. I'm probably trying to to do too much with too little adding the brightness options.

well, trying to use 1070, I think it's: key +256*shift code so... 70 + 256*8 = 2118. A bit lost here. It's true, I mostly used the 6xxxxx offsets (list of FS2004 controls.pdf) and started programming. I had no idea that the offsets were available and never saw past my own macros or basic autopilot stuff as that was what I was working on, or as I skimmed through, I never saw the o's. This is the task I'm trying to do, with keys for now: 1) Select a value (using 66C0) then 2) Select an option (using a key) and finally 3) be able to increment/decrement that option. Currently with just with the airspeed bugs it works great as I've indicated in my last message but only part way. I.E.: 1=70,8,x610066C0,x00090001 2=71,8,x510066C0,x00090001 3=B66C0=1 189,8,M49:1,0 ;189 = "-" to decrement airspeed bug 1 4=B66C0=1 187,8,M49:2,0 ;187 = '+=" to increment airspeed bug 1 5=B66C0=2 189,8,M50:1,0 ;airspeed bug 2 6=B66C0=2 187,8,M50:2,0 ;airspeed bug 2 etc. But say I want to now select EADI, EHSI, EICAS upper or lower brightness but use the same 66C0 value to pick between the four and keys of 189 & 187 to Inc/Dec. I'm trying to see how I can opt for selecting which brightness function I want as well as the airspeed bugs.

Thank you for the info. In my earlier message, I mentioned that I removed the "C" and tried: 2=P71,8,x510066C0,x00090001 but that did not work. I re-read the manual and tried something like this: 4=70,8,1070,2118 and it came back as: 4=70,95,1070,2118 with no errors but then I wasn't sure how to use the 2118 (ugh - using (F+ x,y). You mentioned FSUIPC Options dialogue (page 29). I read this in the manual but I don't see it in the FSUIPC program and mainly, I didn't see it in the manual how it could apply it to the 5 airspeed bugs. These are independent of the main airspeed bug, and works fine with direct key to macro (FSUIPC generated: 4=70,8,M34:1,0). Hmm....... I don't know how I missed it but I did not realize that offsets were part of the options, never went past my own macros (they start as 767PIC...) or even into the o's. So NOW I know what you mean about the options. Having said that. I opted for offset byte cyclic inc (as stated on page 27) and this did nothing, I then opted for SByte increment (as the logging shows 66C0 as S8) and it DID increment once but not again. In addition, when I input in the parameter 00090001 and confirm, I get 145/1. What does 145/1 mean? FSUIPC generated this: 4=70,8,x310066C0,x00015F91 5=70,8,x410066C0,x00015F91 = didn't work I then manually changed it to: 4=70,8,x510066C0,x00090001 5=70,8,x610066C0,x00090001 = and this worked! Not sure why, when manually before - it didn't. so finally this works gr8! 8=70,8,x610066C0,x00090001 ; sets the value I want 9=71,8,x510066C0,x00090001 ;same as above 10=B66C0=1 72,8,M49:1,0 ; decrements as required 11=B66C0=1 74,8,M49:2,0 ;increments as required 12=B66C0=2 72,8,M50:1,0 ;etc. 13=B66C0=2 74,8,M50:2,0 etc. <whew>

Sorry, Mr. Dowson, I still don't understand. I hope it's obvious that I used the manual. 1) That's how I got the info. about the error messages and 2) On page 27, it states: ... The entries in Buttons or Keys might look like this: 31=P174,10,Cx550166C0,x00030001 32=B66C0=0 P117,6,C1030,0 etc. Reading that, I would think it would be reasonable to replace the button P174,10 with a key P70,8,...... And yes, I am trying to do multiple tasks. Since my "resources," that being rotary switches, I was trying this. Use one rotary switch to select the value (0-9) and with a button press and a rotary switch, then be able to select the Inc or Dec. I was trying to use keys to test this instead of the rotary switches/buttons as I wasn't near my home computer and had only access to my laptop which is not connect to my hardware. In addition, I did not see the options I need starting on page 27. In the B767 (becoming a real pain at times I'd admit, and this is same for RPB 747v2) there are 5 speed bugs that can be adjusted. So I was trying to select 1-5 using one rotary switch and then hit a pushbutton and be able to Inc or Dec that value with a different rotary switch. I feel confident I can get it to work with the hardware. It would have to be a mouse macro since the speed bugs are not available options that I know. And I can get the keys to work directly with the mouse macros but again, I was trying to set it up just using keypresses to be able to increment/decrement 66C0, instead of buttons since I wasn't at home with the hardware. So I guess what I'm requesting to know is: can keys be used to increment/decrement 66C0's?

Hello, why didn't this work? (it works with buttons). [buttons] 1=P2,2,Cx510066C0x00090001 2=P2,3,Cx610066C0,x00090001 = work [Keys] 1=70,8,Cx510066C0,x00090001 2=71,8,Cx610066C0,x00090001 = didn't work <<error 24 = bad control value>>, i think I understand this one. When I programmed within FSUIPC, it generated this: 1=70,8,M34:1,0 when I looked at fsuipc.ini so I didn't use a P initially when I attempted the Cx...... so I tried this: 1=P70,8,Cx510066C0x00090001 2=P71,8,Cx610066C0,x00090001 = didn't work <<error 21 = virtual key not in range 1-255>> This one has me confused since I'm using 70 (=F). And I tried removing the C since the generated program didn't use CM34:1,0 but M34:1,0 but that didn't work. also, this didn't work: 1=P70,8,C1003,3840 <<error 21>>

Sounds fair enough. Not sure when I'll get to it. Currently I'm using autohotkey for joystick to mouse functions. All of this has been a bit overwhelming with all the hardware work and the learning curve. I've been at it for at least 2 weeks straight but thanks to you, I finally got my MCP and my "aux" panel working perfectly the way I want it to work. Very happy to finally be "flying." Your assistance was amazing. I don't fly FSX but I went ahead and got FSUIPC for it as well.