FSUIPC Buttons code for GoFlight EFIS

Hello All,

Since this is my first post. I'm including an introduction.

My name is Chris Baye and I live in The Twin Cities of Minneapolis and St. Paul, Minnesota, USA. I've been building my SimPit around GoFlight Modules and have recently purchased Project Magenta and am having a great time moving my flight sim experience to the next level. I am a big fan of the Boeing 757-series aircraft and so my pit layout and PM configuration are designed, as much as possible, to emulate the 757 experience specifically and the Boeing envrionment in general. At some future time I'll post the relevant photos and SolidWorks files for those who are interested.


On to my topic...
The PM software fully supports the GoFlight MCP-Pro but not their EFIS Module. Using FSUIPC I was able to fully program all of EFIS unit's functions for Project Magenta for FS9. Please see the button code is below.

Link to an excel file with more data.
http://www.visi.com/~cbaye/GoFlight_EFIS_Buttons.xls

- Chris

1. Backup your current FSUIPC.ini file.
2. Copy the lines below into your FSUIPC.ini file.
3. Change the Joysitck number (if not 170) 49 times in all
4. Change the line number if you end up with duplicates from your existing file

How to read and FSUIPC.ini entry: line#=(eventstring)joystick#,btn#,Datatype/address,value
The eventstring is everything between the equal sign and the first digit of the joystick number. (don't mess with it)
For more detail please see the FSUIPC documentation.

Code:

---

[Buttons]
100=P170,0,C2999,82
101=P170,1,C2999,96
102=P170,2,C2999,95
103=P170,3,C2999,94
104=P170,4,C2999,93
105=P170,5,C2999,90
106=P170,6,C2999,72
107=P170,8,C2999,74
108=U170,8,C2999,73
109=P170,9,C2999,75
110=U170,9,C2999,73
111=P170,10,C2999,77
112=U170,10,C2999,76
113=P170,11,C2999,78
114=U170,11,C2999,76
115=P170,12,C2999,26
116=P170,13,C2999,14
107=P170,14,Cx010004FA,x14
118=P170,15,C66040,16211
119=CU(-170,17)170,16,C2999,5
120=CP(-170,17)170,16,C2999,3
121=CU(+170,17)170,16,C2999,1
122=CP(+170,17)170,16,C2999,4
123=CU(-170,22)(-170,21)170,20,C2999,41
124=CP(-170,22)(-170,21)170,20,C2999,42
125=CU(-170,22)(+170,21)170,20,C2999,43
126=CP(-170,22)(+170,21)170,20,C2999,44
127=CU(+170,22)(-170,21)170,20,C2999,45
128=CP(+170,22)(-170,21)170,20,C2999,46
129=CU(+170,22)(+170,21)170,20,C2999,47
130=P170,24,C65884,0
131=P170,25,C65884,0
132=P170,26,C65883,0
133=P170,27,C65883,0
134=P170,28,C2064,0
135=P170,29,C2064,0
136=P170,30,C2065,0
137=P170,31,C2065,0

---

Hi Chris and Welcome! Looks like you have been busy! This is great information for Go-Flight users! Thank you for sharing what you have done. I look frorward to the pictures of your project!

[This is my work, also cross-posted to the GoFlight Forums]

Pete Dowson just informed me that he has released a beta version of FSUIPC 3.7 that fully supports the EFIS module.
Pete and I were working on this for the last few days. I did Alpha testing last night and was very satisfied with the results. As from my earlier posts on the topic, if you turn the rotary switches fast you may get the wrong range or mode; to correct this just move the selector one position and then back again. You will also have to do this to synchroize the switch to the display when you start FS.

Links to the update (DLL only) and more detail are below.
http://fsuipc.simflight.com/beta/FSUIPC3716.zip

Downloads and updates section of the Pete Dowson Forum on Simflight: http://forums.simflight.com/viewforum.php?f=54

A complete explaination of each line of code and function cross reference is available at: http://www.visi.com/~cbaye/GoFlight_EFIS_Buttons.xls

I have also included code from my FSUIPC.ini file so you can just cut and paste. (Note, This supports Project Magenta; but once loaded into FSUIPC it will be easy to edit it for other FS functions using the regular FSUIPC interface.

As always, Backup your ini file before editing, Check for duplicate line numbers (the numbers in front of the "=" sign) and make sure to correct the joysitick number if necessary (170 in the example below).

Happy Flying,

- Chris

Code:

---

[Buttons]

100=P170,0,C2999,82
101=P170,1,C2999,96
102=P170,2,C2999,95
103=P170,3,C2999,94
104=P170,4,C2999,93
105=P170,5,C2999,90
106=P170,6,C2999,72
107=P170,8,C2999,74
108=U170,8,C2999,73
109=P170,9,C2999,75
110=U170,9,C2999,73
111=P170,10,C2999,77
112=U170,10,C2999,76
113=P170,11,C2999,78
114=U170,11,C2999,76
115=P170,12,C2999,26
116=P170,13,C2999,14
117=P170,14,Cx010004FA,x14
118=P170,15,C66040,16211
119=P170,16,C2999,5
120=P170,17,C2999,3
121=P170,18,C2999,1
122=P170,19,C2999,4
123=P170,20,C2999,41
124=P170,21,C2999,42
125=P170,22,C2999,43
126=P170,23,C2999,44
127=P170,24,C2999,45
128=P170,25,C2999,46
129=P170,26,C2999,47
130=P170,28,C65883,0
131=P170,29,C65884,0
132=P170,30,C2065,0
133=P170,31,C2064,0

---

Hi Cbaye

Great work, that's what I needed ! (Don't have EFIS but RMK GF166 cards and want to drive my PMRJ cockpit).

So I needed a FSUIPC.ini model

Denis

Hey Chris,

Great work. I inserted the code in the FSUIPC config file, renumbered my lines and it works perfectly. I've got a right-side EFIS also but can't get it to work using the FSUIPC button function... so obviously you've done some custom work on the offsets. Do you know how to modify your code for the co-pilot side EFIS?

Martin Arant - Vmax

[quote=cbaye;7479][This is my work, also cross-posted to the GoFlight Forums]

Pete Dowson just informed me that he has released a beta version of FSUIPC 3.7 that fully supports the EFIS module.

Do you get any response in fsuipc when you push a button or turn a knob?
If you do, from this you can figure out the new button numbers and then its time to figure out the new functions you want to associate. Are you using the First Officer Project Magenta software? If yes, there will be a different set of offsets for that side. I'm willing to help you with this but I'll need some data. Can you send me your current FSUIPC.ini file to look at?

- Chris

Chris,

Thanks for your offer of help. Yes... I am using a full 737 PM cockpit, with 1st officer side. I have (2) EFIS units. When I try to program the right 1st offier EFIS using the FSUIPC buttons... some work and some don't work. I can, for example, program the APP, VOR, PLAN functions of the mode switch... but not the MAP. I can program the ranges, but not the Decision Height or Barometer functions.

I think the best thing for me to do is send the FSUIPC. INI file with your code and my attempts to add button code. How many functions do you want added to the 1st officer side? All codes of just those that work... and also, any particular order?

Quote:

---

Originally Posted by cbaye

Do you get any response in fsuipc when you push a button or turn a knob?
If you do, from this you can figure out the new button numbers and then its time to figure out the new functions you want to associate. Are you using the First Officer Project Magenta software? If yes, there will be a different set of offsets for that side. I'm willing to help you with this but I'll need some data. Can you send me your current FSUIPC.ini file to look at?

Can you send me an email at vmax@simpilot.com so I can respond privately to you?

Thanks for your help.

Martin

- Chris

---

Chris,

Thanks for your offer of help. Yes... I am using a full 737 PM cockpit, with 1st officer side. I have (2) EFIS units. When I try to program the right 1st offier EFIS using the FSUIPC buttons... some work and some don't work. I can, for example, program the APP, VOR, PLAN functions of the mode switch... but not the MAP. I can program the ranges, but not the Decision Height or Barometer functions.

I think the best thing for me to do is send the FSUIPC. INI file with your code and my attempts to add button code. How many functions do you want added to the 1st officer side? All codes of just those that work... and also, any particular order?

Quote:

---

Originally Posted by cbaye

Do you get any response in fsuipc when you push a button or turn a knob?
If you do, from this you can figure out the new button numbers and then its time to figure out the new functions you want to associate. Are you using the First Officer Project Magenta software? If yes, there will be a different set of offsets for that side. I'm willing to help you with this but I'll need some data. Can you send me your current FSUIPC.ini file to look at?

Can you send me an email at vmax@simpilot.com so I can respond privately to you?

Thanks for your help.

Martin

- Chris

---

HEy guys,

did anybody got the offsets for the DH and QNH inc ,dec for F/O side????? using Goflight EFIS with PM