cbaye

Yep, Bone-head mistake... forrest for the trees stuff. The whole reason I asked for help in the first place. I tend to spend most of my time in the Advanced guide.. did not think to look and the User guide for clarification. I took your advice and used the FSUIPS options feature. It cleared things up for me. Computers are wonderful... They only do what you tell them to! Thanks for your help. - Chris

Hello Peter, OK, I've had some success but have encountered a small problem. I've been working with "Captain Decision Height" at offset 04FA as a way of learning the process. Based on a Signed Byte commands to inc/dec I acheived these results. I can set the value using: Cx010004FA, x14 -> Reports 200ft I can decrement the value: Cx410004FA,x01 -> Decrements value I cannot incement the value: Cx310004FA,x01 -> Sets value to zero If I change to an Unsigned Byte commands I get different results: I cannnot decrement the value: Cx210004FA,x01 -> Sets value to zero I cannot incement the value: Cx110004FA,x01 -> Decrements value I know the results above are confusing but it's true. The Increment command decrements and the decrement command sets the value to zero. I believe I'm not specifying the parameter correctly, can you provide assistance? Thanks, Chris

Hello Pete, I'd like to Increment and Decrement the First officer QNH (Offset 552E) and DH/MDH (Offset 5532) using pushbutton commands. I thought I've seen incr/decr commands in your documents but cannot find them (perhaps because I've been reading them late at night). Can you please give me a code snippet to work from. Many Thanks, - Chris

If you are using a sim that does not have specific keystrokes assigned to each Mode or Range switch-position but instead looks to those knobs for simple increment and decrement commands, I have made up this alternate code. It was made to help another simmer who uses PMDG and Level-D products. It can be substituted for lines 119-129 in the code in the previous post. You can change the command portions of lines 120-131 and 160-165 below. Do not change the commands of any other lines unless you have read Pete's documentation. You may renumber lines as required but do not change the order of the lines, as the order of operations is critical to proper function. - Chris ;Begin EFIS Range knob logic ;Increment or decrement Range Knob ;Reads current knob position and last knob position flag 120=CP(F+15,5)170,21,C65883,0;Inc Kohlsman 121=CP(F+15,6)170,22,C65883,0 122=CP(F+15,7)170,23,C65883,0 123=CP(F+15,8)170,24,C65883,0 124=CP(F+15,9)170,25,C65883,0 125=CP(F+15,10)170,26,C65883,0;Inc Kohlsman 126=CP(F+15,11)170,25,C65884,0 ;Dec Kohlsman 127=CP(F+15,10)170,24,C65884,0 128=CP(F+15,9)170,23,C65884,0 129=CP(F+15,8)170,22,C65884,0 130=CP(F+15,7)170,21,C65884,0 131=CP(F+15,6)170,20,C65884,0;Dec Kohlsman ;Clear and set Flags to mark last knob position ;Stores last knob position in joystick #15 flag locations. 132=P170,20,C1004,3846; Clear Flag 15,6 133=P170,20,C1003,3845; Set Flag 15,5 134=P170,21,C1004,3845 135=P170,21,C1004,3847 136=P170,21,C1003,3846 137=P170,22,C1004,3846 138=P170,22,C1004,3848 139=P170,22,C1003,3847 140=P170,23,C1004,3847 141=P170,23,C1004,3849 142=P170,23,C1003,3848 143=P170,24,C1004,3848 144=P170,24,C1004,3850 145=P170,24,C1003,3849 146=P170,25,C1004,3849 147=P170,25,C1004,3851 148=P170,25,C1003,3850 149=P170,26,C1004,3850 150=P170,26,C1003,3851 ;End EFIS Range knob logic ;Begin EFIS Mode knob logic ;Increment or decrement Range Knob ;Reads current knob position and last knob position flag 160=CP(F+15,0)170,17,C65883,0 ;Inc Kohlsman 161=CP(F+15,1)170,18,C65883,0 ;Inc Kohlsman 162=CP(F+15,2)170,19,C65883,0 ;Inc Kohlsman 163=CP(F+15,3)170,18,C65884,0 ;Dec Kohlsman 164=CP(F+15,2)170,17,C65884,0 ;Dec Kohlsman 165=CP(F+15,1)170,16,C65884,0 ;Dec Kohlsman ;Clear and set Flags to mark last knob position ;Stores last knob position in joystick #15 flag locations. 166=P170,16,C1004,3841; Clear Flag 15,1 167=P170,16,C1003,3840; Set Flag 15,0 168=P170,17,C1004,3840 169=P170,17,C1004,3842 170=P170,17,C1003,3841 171=P170,18,C1004,3841 172=P170,18,C1004,3843 173=P170,18,C1003,3842 174=P170,19,C1004,3852 175=P170,19,C1003,3853 ;End EFIS Mode knob logic

Peter has completed an FS9 beta version that fully supports GoFlight. It is available in the Downloads and Updates section as V3.716. An FSUIPC.ini code sample to support Project Magenta is listed below. 170 is the joystick number in the sample below. You may have to edit this in your file if your EFIS reports as another number. The usual precutions of backing up your file before editing apply. Also be sure to check for duplicate line numbers. As shown below, these lines go in the [buttons] section. - Chris Baye [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

Yes, the 5 mile range was omitted because the GoFlight unit was not marked for it. My pleasure. All in all it was a good excercie as I was able to learn how to program another of your products features. - Chris

Hello Peter, I was able to achieve my goal using the FSUIPC Compound Button Function. Lines 76-79 read the mode switch and set the appropriate Project Magenta Display Mode. Lines 93-99, set the range. Thanks for your help, -Chris 76=CU(-170,17)170,16,C2999,5 77=CP(-170,17)170,16,C2999,3 78=CU(+170,17)170,16,C2999,1 79=CP(+170,17)170,16,C2999,4 93=CU(-170,22)(-170,21)170,20,C2999,41 94=CP(-170,22)(-170,21)170,20,C2999,42 95=CU(-170,22)(+170,21)170,20,C2999,43 96=CP(-170,22)(+170,21)170,20,C2999,44 97=CU(+170,22)(-170,21)170,20,C2999,45 98=CP(+170,22)(-170,21)170,20,C2999,46 99=CU(+170,22)(+170,21)170,20,C2999,47

Hello Peter, I made a complete table of switch, encoder and button functions for the GoFlight EFIS and placed them in the attached spreadsheet. Each position of the rotary switches appears to be represented by the states of two or three buttons. Starting from the CCW-most position (lets call this pos 0) and rotating the switch CW the following beheavior is observed: Pos 1 - btn# 16 activated in FSUIPC Pos 2 - btn# 17 activated pressed in FSUIPC Pos 3 - btn# 16 activated pressed in FSUIPC (Last Position) Rotating CCW: Pos 2 - no btn activated in FSUIPC Pos 1 - btn# 16 activated in FSUIPC Pos 0 - no btn activated in FSUIPC If I could see the btn deactivated event I could confirm the beheavior. The question then becomes; How do I make use of this? Are there some user-accessible, non-reserved offsets that could be used to store the state of the rotaries? Once I have stored the state of the rotaries, are there facilities within FSUIPC to monitor them for change events and then activate functions like Keysend or set the states of other offsets? Thanks, - Chris GoFlight EFIS Buttons.zip

Hello Peter, A while back you had asked for beta testers for the New GF MCPpro and EFIS module. I now own both of these (along with Project Magenta) and have a achieved a high degree of integration except for two functions: The mode and range selectors. These, I suspect, operate differently than a traditional encoder or switch and perhaps rely on additional logic. If I plug the EFIS into the Project Magenta Glass Cockpit computer and use GoFlight's "GFKeys" program I can achieve full key-mapping functionality on the Mode and Range knobs, but for some reason they did not include support for the pushbutton functions of the two rotary encoders. I have contacted GoFlight separately on this issue. If I plug the EFIS into the FS computer, I can use FSUIPC to achieve full functionality on all pushbuttons and encoders, except the Mode and range knobs, which tend to act like standard encoders. The people at GoFlight tell me that they are working with you to achieve full support on this module. I would be happy to beta-test any new code but I am only running FS9 not FSX (although I have purchased FSUIPC and WideFS for both platforms). The FSUIPC solution would be far more robust than the GFKeys option in that I could directly access Project Magenta Offsets, Bypassing the keyboard commands entirely. Thanks for listening, - Chris Baye

Hello Peter, I found the culpret. It was a program called QuickCare that was installed when I changed to a new DSL router from Qwest, my local telephone company. I usually shut down all extrainious programs in my system tray before flying but I guess I missed a few... Thanks for you assistance. - Chris

Peter, I'm running WideServer (Machine name: BOEING) and two WideClinets (Machine names: MINCO_22254 and WHOOMAH) . One of the clients, MINCO_22254, connects and operates normally while the other, WHOOMAH, does not. When I start WideClient on WHOOMAH the window opens and indicates "Connected" but then the window cannot be moved, resized or closed (without using Task Manager) and CPU time for WideClient.exe fluxuates between 80 and 90%. The server status line in the MSFS Frame on BOEING indicates that 2 clients are connected. I have followed the network instructions in the manual and have not observed any changes in behavior. One more little tid-bit to keep this interesting (When WHOOMAH is the Server and BOEING is a client... Everything works just fine) The logs for both clients and the server are listed below. Server ********* WideServer.DLL Log [version 6.70] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 19/11/06, Time 19:36:34.989: Server name is BOEING 116627 Initialising TCP/IP server 116637 Initialising IPX/SPX server 116637 ServerNode=0.0.2816.1243.50302 116647 Initialising UDP/IP server 118280 Broadcasting service every 1000 mSecs 127313 Incoming connection Accepted ok (skt=2128) TCP 127613 Connected to computer "MINCO_22254" running WideClient version 6.710 (skt=2128) TCP 180539 Incoming connection Accepted ok (skt=2148) TCP 180689 Connected to computer "WHOOMAH" running WideClient version 6.710 (skt=2148) TCP 473270 Error 10054: client socket disconnected at Client: removing (skt=2128) TCP 566404 Error 10053: client socket disconnected at Client: removing (skt=2148) TCP 746303 Close signalled to clients 747414 Closing down now ... Memory managed: Offset records: 136 alloc, 136 free Read buffer usage: 846 alloc, 846 free, max in session: 1 Write buffer usage: 38690 alloc, 38690 free, max in session: 1 Throughput maximum achieved: 41 frames/sec, 1150 bytes/sec Throughput average achieved for complete session: 8 frames/sec, 194 bytes/sec Average receive rate from "MINCO_22254": 1 frames/sec, 36 bytes/sec Average receive rate from "WHOOMAH": 0 frames/sec, 13 bytes/sec ********* Log file closed ********* Functioning Client ********* WideClient Log [version 6.71] Class=FS98MAIN ********* Date (dmy): 19/11/06, Time 19:38:45.740: Client name is MINCO_22254 400 Attempting to connect now 420 Trying TCP/IP host "Boeing" port 8002 ... 420Okay, IP Address = 192.168.0.66 430 Connection made okay! 16684 New Client Application: "CDUDemo" (Id=1012) 346388 ****** End of session performance summary ****** 346388 Total time connected = 346 seconds 346388 Reception maximum: 40 frames/sec, 1054 bytes/sec 346388 Reception average whilst connected: 35 frames/sec, 790 bytes/sec 346388 Transmission maximum: 4 frames/sec, 430 bytes/sec 346388 Transmission average whilst connected: 2 frames/sec, 65 bytes/sec 346388 Max receive buffer = 518, Max send depth = 4, Send frames lost = 0 346388 **************** Individual client application activity **************** 346388 Client 1012 requests: 1627 (Ave 4/sec), Data: 3025919 bytes (8745/sec), Average 1859 bytes/Process 346388 ********* Log file closed (Buffers: MaxUsed 5, Alloc 13856 Freed 13856 Refused 0) ********* Non-functioning Client ********* WideClient Log [version 6.71] Class=FS98MAIN ********* Date (dmy): 19/11/06, Time 19:39:33.765: Client name is WHOOMAH 500 Attempting to connect now 516 Trying TCP/IP host "Boeing" port 8002 ... 516Okay, IP Address = 192.168.0.66 531 Connection made okay! 385938 ****** End of session performance summary ****** 385938 Total time connected = 385 seconds 385938 Reception maximum: 2 frames/sec, 198 bytes/sec 385938 Reception average whilst connected: 1 frames/sec, 43 bytes/sec 385938 Transmission maximum: 0 frames/sec, 100 bytes/sec 385938 Transmission average whilst connected: 0 frames/sec, 19 bytes/sec 385938 Max receive buffer = 374, Max send depth = 1, Send frames lost = 0 385938 ********* Log file closed (Buffers: MaxUsed 2, Alloc 740 Freed 740 Refused 0) ********* Thanks for the help. - Chris

:D With a little more study and experimentation, I was able to solve the problem by adding two items to the conditions list and then modifying my code. [Conditions] 49=X7B91 U8 =0 ; SB3 Transponder mode C 50=X7B93 U8 =1 ; SB3 Transponder IDENT active [GFRP48.0] Needs=E B B=8 L7.1=!C50 X7B91 U8 =0; SB3 Transponder mode C L7.2=C49 X7B93 U8 !=0 Ff4off; SB3 Transponder IDENT active

I've configured an RP48 in FSUIPC to use an encoder and button to operate the SB3 transponder using offsets: Encoder for mode, x7b91 and Button for ident, x7b93. I then used GFDiaplay to flash the button's LED when x7b93 was activated. The ideal beheavior is to have the LED turn on (steady) when the transponder is in mode C, Flash during ident and return to Steady. I think this is possible with the case statements disucssed in the manual but I am unsure how to proceded. Can someone please share a similar code-snippet with me? - Chris

Hello Frank, Thanks for the reply. I use both of the methods you suggested and find that I am looking for a more flexible method of control. I have used joysitcks with my laptop and have found most of them too bulky (and a little geeky) to travel with. The game controller was a nice compromise; it has 4 joystick-axes, a hat switch and 10 buttons. In a way I am trying to emulate Radio-Control style Elevator, Aileron, Rudder and Throttle control. Flying from a laptop is a compromise at best. I use my manual controls only in the early and final stages of flight and taxi. Once my hands are on the gamepad I'd prefer to keep them there rather than have to operate the pad with one hand and the KB/Mouse with the other. What I did not say in my original "design intent" statement is that I intend to implement this as a gauge and then put some logic behind certain behaviors. For instance, the thrust reverser function will be locked-out unless the aircraft is correctly configured, on the ground, and at appropriate speeds for safe operation. The function can only be activated if the throttles have been resting at idle for a set period of time (say 1 second).

I originally posted this on AVSIM but got no response, perhaps a member of this forum can provide some insight. - CB I have a nice home cockpit with lots of gadgets; but when I travel I like to use my laptop and gamepad (for it's compact size) to fly. The game pad does not feature a sliding throttle control like most joysticks have. I want to develop an alternate throttle control using the input from a self-centering joystick on a game pad. I Plan to use this feature with Jets only, so I think it might be possible to map a prop joystick axis as my input. FWIW, I have a registered copy of FSUIPC. Design Intent: The joystick input range will be divided into 5 zones: Null, Slow change, Fast change With changes in both the positive and negative directions. When the Joystick is in the null position, the throttle condition (% throttle) will remain fixed. In the +Slow zone it will slowly advance the throttle, in the +Fast zone it will quickly advance the throttle. Retarding the throttle will work the same way as -Slow and -Fast zones. The null zone will be quite wide to avoid changing the throttle as the second axis of joystick is used. Here are my questions: Will this approach work... i.e. if I use the prop-pitch axis or cowling axis while flying a jet will do I run a high risk of having an unstable system? Has anybody done anything like this in the past that I might use as an example? Thanks, - Chris