mattriggins

Pete: Ignore the initial post below the slashes.I think I have this figured out. I'm basically going to have to run pmsystems fsuipc widefs GFDisplay While FSUIPC deals with the buttons, etc. GFDisplay drives the LEDs on and off. So, for now, I have programmed FSUIPC for the GF button to: On button press, send offset 56F8 bit 1, to tell pmsystems (demo) that the CW button was pressed. On button release, send offset 5530 bit 0 to turn off the light. Obviously I still have to tell GFDisplay what and where to send the offset/bit information also, am I correct on that? Correct me if I'm wrong but a LOT is happening here at once if I'm not mistaken: pmsystems says caution light comes on. then pmsystems has to communicate over WideFS to GFDisplay running on the FS computer to turn on the LED, which is specificed in the GFDisplay ini file. That gets the GF LED on. Then, when I press the GF button below the LED, FSUIPC on the FS computer is seeing that, sending offset 56F8.1 to pmsystems over WideFS and pmsystems says ok the recall button was pressed. Then, when I release the GF button below the LED, FSUICP on the FS computer is seeing that, sending offset 5530.0 to pmsystem over WideFS and pmsystems then turns off the caution light. Finally, pmsystems over WideFS talks to GFDisplay on the FS computer and sends the offset/bit to have GFDisplay turn off the LED. Is that about right? ---------------------------------------------------------------------------------------------------------------- Yeah too bad they don't simulate these things. Well it keeps you in business! So at this point, I've got GFDisplay running. I'm learning how the ini file works. Eventually I'll find the bit that turns the GoFlight LED on and Off. Of course, to your genius its easy. And you conveniently left out P8 information to make me have to learn this? How dare you!! (just kidding) Natrually I can program a button to do something in FSUIPC, but I can't program FSUIPC to automatically turn that LED on and off because there is no logic, correct? So, I get pmsystems, which is running the logic and says ok, the caution lite comes on. Does FSUIPC look at pmsystems, and say oh I have an offset and a bit to turn an LED on, and then sends that to the GoFlight LED (using the offset/bit infomation provided by GFDisplay) to turn on the right LED? Or, is it pmsystems that sends the offset/bit to the LED in the GoFlight module? My final question is, if it's FUSIPC that would send that information to the LED, where do you program that at? (To look for logic from pmsystems then act upon it, or, do I have the meachnis wrong?I just want to understand how these two fantastic pieces of software talk to each other, which will bring down the level of my confusion later on. I setup the goflight button to offset 56F8.1, and upon release 5530.0. That works for telling pmsystems I've pressed the button, and it turns off the light in pmsystem. I'm currently using the pm instructor to initiate engine failures so I can get the caution light to come on. I'm still just unclear what program (pmsystems, or FSUIPC) would turn the LED on and off. To me it would (now) make sense that pmsystems was doing it. If thats the case, I'd have to figure out where (the ini file?) in pmsystems you'd put the offset/bit information (from GFDisplay?) to be able to turn on/off the correct LED. Or have I got it all half *** backwards? heh Thanks Pete as always. Matt Riggins

Thanks for your very helpful info Peter! I didn't even see GFDisplay down there in your list of apps. I'll start to tackle that. One thing that is working for the moment in regards to a button press. It appears FS has no FS Commands for pressing the C/W button for a default craft. If I'm wrong and missed it, please let me know. That being said, and being an owner of Pilot in Command 737, I found in their panel setup utility the ability to program a keyboard command for turning off (their) C/W light. I set that keyboard command, deleted that same keyboard command in the FS key assignments. Then in FSUIPC, pressed my goflight button and set it for a key press using the same command. That of course does work and lets me turn off the CW light (in the PIC 737 panel) via the goflight button. Now, to figure out using GF Display how to get the LED above the button on the GF P8 to lite up when the CW comes on :) Thanks again!

Peter, I have a GoFlight GF-P8 and I had a thought about using two of it's buttons/LEDs for Fire/Caution and Warning. Obvious it's not perfect but for my current budget (Hey, I just bought WideFS!!) its the only option for now. So, I started looking up offsets, etc. I own the PM Boeing GC/MCP/CDU. I found PM Offset 04FE, bits 2 and 3. I found offset 5530, and Offset 5540. I'd assume you'd have to have a bit for the button AND the LED? Besides that, I believe that for ANY of these offsets to even be considered, they are all passed through pm systems, is that correct? IF so... do you have any thoughts on if I (purchased) pm systems, I COULD get the GoFlight P8 to work for Fire/CW? IE, Leds above the button would lite up, press button and they go out. I more then likely would not be able to purchase pmsystems at this time, but for future reference, I wanted your input on this. OR... do you feel there IS a possible way to make the GoFlight P8 work for a Fire/CW system without pmsystems? Your expertise is always appreciated!! Thanks! Matt Riggins

So having both the GC and the MCP resolved it. Thanks for having patience with a noob! Greatly appreciate the help!! Matt

Heh well you may have already solved it. I'm going to test now but if some of those bits are handled by the pm mcp then that would be the problem..... I have only had the PM GC open, but not the MCP. I'll fire the sim up now, open both the PM GC and the PM MCP and will let you know.

This is a little puzzling. I went into FSUIPC and I set the same (non working button) to use PM ND Rage 320 with 0 for parameter. Pressing that works. I set the same button to then PM ND Range 10 with parameter set to 0, and that works. But PM ND Range Inc and PM ND Range Dec with the paramter set to 0 doen't work, ie it doesn't go from 2.5, to 5, etc up to 320 or vice versa. Thoughts? Update: So some PM ND commands work, others don't. For example, I can set 3 keys up, one to PM ND Map Arc Mode, the 2nd to PM ND Ctr Mode and the last button to PM ND Plan mode. Pressing those buttons changes to the mode I specificed for that button. But if I set one of those buttons to PM ND Mode Inc or PM ND Mode Dec, they don't cycle through the modes. The same for range, if I set a button to a direct range (say 160) it works, but using Range Inc or Dec doesn't work. It's like cycling through something is broken. I'm stumped. How can I help debug this? Update 2: Heh Pete, look at this post from 2005. viewtopic.php?f=54&t=43773&start=0&st=0&sk=t&sd=a Sound familiar? I can't imagine after 4 years this is still broken?

Thanks for the prompt reply Pete. I'm at work but will check the logging tab when I get home to see if there is any communication going on. Prior to discovering that "include project magenta" actually put in PM xyz commands, I was trying to setup a word set with the x04F4 offset, but wasn't sure I was doing it properly. There was a vaule of 322 for the command I was testing and I assumed that went into the parameter section. However upon closing FSUIPC, it would reset that paramater to a x0 value. So I figured I was doing something wrong there. That's why I was elated to see there was a direct PM command, but alas, it wasn't working. I'm assuming you simply linked those offsets to the PM commands? (And if so, thank you, thats a life saver) Also, where can I find the advanced FSUIPC user guide that everyone mentions? It was very difficult to locate it on your site. I was hoping to read through that regardless, knowledge is power. When I get home I'll check the logging tab to see if the PM command is indeed sending out an offset, however according to the PM site it wasn't bits but values. Could that be an issue? The FSUIPC PM offset page I was referencing from was: http://www.projectmagenta.com/pmoffsets.html Thanks again Pete! Matt Riggins

just to note, I do not have any functions for these P8 buttons set within the goflight software, so it's not an over ride issue.

FSUIPC4 4.50 Latest Project Magenta Boeing GC FSX SP1 Goflight P8 w/latest GoFlight software. When FSX starts, my config file loads the goflight software which lets me use their modules in FSX, pretty basic. So I want one of my P8's buttons to control a few of the PM ND commands, like increase range, decrease, etc. Again pretty basic. I open up FSUIPC within FSX (I'm registered) and hit the buttons and switches tab. I press a button on the P8 and it shows up with it's joystick # 101 and button 7 number. Awsome! I press select for FS and include PM checkboxes. From the drop down, I choose PM ND Range Increase I hit OK I'm back in my cockpit, I press the goflight button, and nothing happens on the ND of the project magenta boeing GC. If I click into the PM window, and press say G or H, range increases/decreases. I click back into FSX, hit the go flight button, nothing. What am I doing wrong? Thanks!