David Cox

Pete, I have been reading the various posts both on this forum and the AOG (SA_WXR) forum and see there have been issues with SA-WXR and the latest versions of FSUIPC/WideServer/Client To resolve this, I have downloaded the interim versions of FSUIPC/WideServer/Client and the latest version of SA-WXR (1.2.2) but SA-WXR still fails to start with a CONFIG FILE ERROR message. Have I missed something ?

Pete, Hope you can help - over the last few days I have been experiencing wierd behaviour between my thrre PC's running FS & Project Magenta. Basically, the CDU and MCP appear to loose control of the A/C and the speed & altitude then flucuates wilfly on the PFD. Enrico thinks the problem is probably coming from FS and I have checked the FSUIPC & WideFS logs and have come up with the following (from WideFS) ********* WideServer.DLL Log [version 6.47] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 02/11/05, Time 15:31:57.078: Server name is P4 54204 Initialising TCP/IP server 54204 Initialising IPX/SPX server 54219 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 54219 Failed to start IPX/SPX Server 58329 Incoming connection Accepted ok (skt=388) 58407 Connected to computer "XEON" running WideClient version 6.470 (skt=388) 63844 Incoming connection Accepted ok (skt=532) 63922 Connected to computer "CELERON" running WideClient version 6.470 (skt=532) 63922 **** ERROR! Sumcheck or length fails on received socket 532 block, len=184 (time=0) 67875 **** ERROR! Sumcheck or length fails on received socket 388 block, len=25 (time=32203) 423344 **** ERROR! Sumcheck or length fails on received socket 388 block, len=43 (time=0) 1278282 **** ERROR! Sumcheck or length fails on received socket 388 block, len=67 (time=1242640) 1634079 Closing down now ... Memory managed: Offset records: 294 alloc, 294 free Total number of received blocks having sumcheck errors = 4 Throughput maximum achieved: 72 frames/sec, 13678 bytes/sec Throughput average achieved for complete session: 24 frames/sec, 4146 bytes/sec Average receive rate from "XEON": 2 frames/sec, 163 bytes/sec Average receive rate from "CELERON": 4 frames/sec, 408 bytes/sec ********* Log file closed ********* ********* WideClient Log [version 6.47] Class=FS98MAIN ********* Date (dmy): 02/11/05, Time 15:31:33.000: Client name is XEON 687 Attempting to connect now 1672 Trying TCP/IP host "P4" port 8002 ... 1672Okay, IP Address = 192.168.52.7 6172 New Client Application: "pmSounds" (Id=1328) 7718 New Client Application: "cdu" (Id=1260) 14984 New Client Application: "pfd" (Id=1396) 22672 Error on client pre-Connection Select() [Error=10060] Connection timed out 22687 Ready to try connection again 22718 Attempting to connect now 22734 Connection made okay! 82312 Error on send() of 25 bytes [Error=10014] Bad address 1598468 Error on client post-Connection Select() [Error=10053] Software caused connection abort 1598468 Connection closed by server! 1598468 The connection was terminated due to a time-out or other failure! 1598484 Ready to try connection again 1598484 Attempting to connect now 1598968 WRITESTATEDATA received with bad data size! 1598968 0 ReadLocal: Offset=2400000, Size=20000 2009000 0 ReadLocal: Offset=2400000, Size=20000 2096484 0 ReadLocal: Offset=2400000, Size=20000 ***************************************************** There is obviously something going wrong here as there are error messages - can you give me some idea what to look for here. Many thanks David

Pete, Using the GoFlight drivers for my TQ6 doesn't give me the facility to arm the spoilers. Is there a way to have an arm facility if I drive the spoiler lever using FSUIPC ? Many thanks David

Pete - many thanks

Can anyone help please. I am trying to program 2 buttons to shut down the engines on my PMDG 737 but I can't find the correct control in FSUIPC that operates the idle/fuel cut-off levers located just behind the throttles. If one doesn't exist then I am happy to use a FSUIPC offset but again, I've looked through the list and can't find the one I need Can anyone point me in the right direction Many thanks

Excellent, that's much better - thanks for your help. I didn't realise how Ffast functioned David

Tha same as the default GFDisplay.ini file. Namely : 11=XBF4 U16 =16383 ; Left Gear Down

Pete, Many thanks - I missed that bit. OK, I have now got it working using your default GFDisplay.ini file and adding the following entry : [GFRP48.0] Needs=E B B=8 L7.1=!C11 XBF4 U16 !=0 Ff10off ;Left Gear Moving L7.2=XBF4 U16 =16383 ;Left Gear Down Using this code & starting with gear UP the LED flashes for 10 seconds and stays on once the gear is DOWN. However, when I toggle the gear UP the LED only flashes very briefly before going out (long before the gear has retracted fully - 10 secs.) Any idea why this happens ? Cheers

Pete - Hi, hope you are well, I have successfully programmed LED 7 on my GoFlight RP48 to indicate when the gear is down via GFDisplay as follows : L7=XBF4 U16 =16383 Ff5on ;Left Gear Down As you can see I have included the Ff5on command but it doesn't really achieve what I want - I am trying to emulate the original GoFlight function that has the green light flashing when the gear is in motion and staying on when it is down, off when it is retracted but I can't figure out how to do this using GFDisplay - I wondered if the LED can have several line entries but I can't get this to work Can you point me in the right direction here Many thanks David Cox

Pete, Thanks for your input - all working OK now that I have turned the FSUIPC option on - the one aircraft length thing is annoying but I'll live with it Cheers David

Hi there - I hope someone can help ??? I cannot get pushback to work properly - when I use SHIFT + P The aircaft moves backwards but the 1 & 2 keys (on the main keyboard and NUM keyboard) do not cause the A/C to turn right or left and the rudder pedals do not work either. Has anyone come across this or have any idea what could be wrong ? Many thanks David

Hi, I have now finished this for Squawkbox 3 and everything is working well for both the transpnder and the COM1/2 functionality. I have programmed all my buttons in FSUIPC.INI manually because I use shift keys to assign multiple actions to the same button but I think all this stuff can be done via the Buttons GUI page in the FSUIPC moudle within FS2004. Anyway, here is the code I have used (substitute your joystick/button numbers for n/n and your line entry number in the [buttons] section for **..) Transponder : Standby mode **=Pn,n,Cx01007B91,x00 Normal mode **=Pn,n,Cx01007B91,x01 Ident **=Pn,n,Cx01007B93,x01 COM radios : COM1 active **=Pn,n,C66463,0 COM2 active **=Pn,n,C66464,0 BOTH radios (Toggle) **=Pn,n,C66465,0 Hope this helps David

Pete, Please disregard last posting - it is now working fine after re-starting WideFS on the client PC Once again, thanks for your help David

Pete, OK thanks for the clarification - that makes sense. This is the code I have used but it doesn't work - did I get it right as far as your instructions are concerned ? 62=P0,10,Cx01007B91,x01 (or x00) Many thanks David

Hi Pete, Can you just clarify something for me before I program my joystick button : The Squawkbox web-site says : "SquawkBox 3 Specific Offsets: 0x7b91 (1 byte) Transponder mode 0 = normal 1 = standby SquawkBox reads this value to determine which transponder mode to send to the network. Your transponder gauge should set this offset when the user changes modes with your gauge". If Iam reading this right then I need to use the Offset Byte setbits (or Clearbits) control for offset 7b91. Which bit am I setting/clearing, bit 0 or bit 1 (or have I got the wrong end of the stick again ???) Many thanks David

Pete, Ahhhh !............. the light finally dawns ............... I've just programmed my first button for SA_WXR following your advice and it works !!!. Please bear with me, up until a few weeks ago I had never attempted to program anything and the world of Hex, binary etc. is s completely new one to me. Anyway, many thanks for all your help - hopefully I can finish the task without any more input Thanks once again David

Pete, Thanks for the reply, I'll go back to using the FSUIPC dialogue if it's easier but I'm still struggling so I wonder if you can help me with this simple example and tell me what goes where : Say I want to turn on OFP using bit 3 (setting it to 1) at offset 6D00. 1) Which offset control do you suggest I use to handle the whole D-Word, Offset byte setbits ? 2) Once I have selected the right control from the drop-down list, I presume I modify the entry in the offset box to read x6D00 - correct ? 3) Lastly, I presume that the instruction to set bit 3 to 1 goes in the parameter box but I have no idea what it should look like. If you can fill in the blanks for me on this one then I will be able to work the rest out for myself I think Many thanks again for your help David

Hi Pete, I have just seen the above post - I too have just purchased SA_WXR and having problems programming the buttons. Can you just point me in the right direction please and tell me if my assumptions are correct as I think I am missing something here : From the SA_WXR FSUIPIC programmimg section : Control-Word at (Write) 0x6D00 as long as Bit 7 = 1 which means switch mode If Bit7 is set to 1, then following Control bits are used, they are all switched/steady. Bit7 Toggle/Switchselect(1) bit 3 OFP ON bit 2 GCS ON bit 1 Mode 1 bit 0 Mode 0 Bit15 Tilt7 bit 14 Tilt6 etc. As I understand it, the Control word 0x6D00 is 32 bit so we would see something like this fora button in the INI file: 52=P0,10,Cx01006D00 Looking at an example above the manual says that switch mode is activated by setting bit 7 to 1, then we can turn OFP on using bit 3 (set to 1), so if I am understanding this then it should look something like this : 52=P0,10,Cx01006D07,1 53=P0,10,Cx01006D03,1 Or have I completely misunderstood _ I get the feeling I am not understanding how the "bit" portion works or how it is written. Your advice appreciated as always

Pete, Ignore my last post - I see I got it right (338C) and all is now working well. Also, I have shortened LEFT + RIGHT to L+R and that has resolved the problem with the delay in the PM EICAS display. I tested without any other button programming and it did not resolve the display delay so I will let Enrico know what I found as it may be a problem with PM GC. Once again, many thanks for your guidance on this one - I think I'm starting to get my head around hexadecimal ! David

Pete, You are saying that just two of my lines of code have errors, I think ?. You said : "The zero terminator is being written to 3392, which is 10 bytes later than 3388, not 4. You seem to have reverted to counting in decimal, not hexadecimal. 8 + 4 in hex is C. Hex digits go 0-9 then A B C D E F". Sorry, this is all new to me and I'm confused (possibly thick !). So what should the zero terminator be written to - 338C ?. Please explain. I don't think I'm fully understanding how the HEX works with offsets. Many thanks David

Pete, A quick update for you - I've been flying with this new set-up and all is not a it should be yet - I have noticed two strange things : 1) Sometimes (usually after re-starting FS2004), the message LEFT + RIGHT gets corrupted with additional text (e.g. LEFT + RIGHT nwa MC). Yet on restart everything goes back to normal 2) Whilst AdvDisplay itself updates quickly the display (via AdvDisplay) in the PM EICAS page updates very slowly when displaying LEFT + RIGHT (approx. 7 seconds) but only when generated by button 0,10. When button 0,11 generates the same message it happens very quickly. I have also seen occasional truncation of the display in the PM EICAS (LEFT + R) but this is only very occasional. My code is : 20=CP(F+14,2)(F-14,3)0,10,Cx03003380,x5446454C 21=CP(F+14,2)(F-14,3)0,10,Cx01003384,x00 22=CP(F+14,2)(F-14,3)0,10,Cx020032FA,0 23=CP(F-14,2)(F-14,3)0,10,Cx03003380,x454E4F4E 24=CP(F-14,2)(F-14,3)0,10,Cx01003384,x00 25=CP(F-14,2)(F-14,3)0,10,Cx020032FA,0 26=CP(F+14,2)(F+14,3)0,10,Cx03003380,x5446454C 27=CP(F+14,2)(F+14,3)0,10,Cx03003384,x52202B20 28=CP(F+14,2)(F+14,3)0,10,Cx03003388,x54484749 29=CP(F+14,2)(F+14,3)0,10,Cx01003392,x00 30=CP(F+14,2)(F+14,3)0,10,Cx020032FA,0 31=CP(F-14,2)(F+14,3)0,10,Cx03003380,x48474952 32=CP(F-14,2)(F+14,3)0,10,Cx02003384,x0054 33=CP(F-14,2)(F+14,3)0,10,Cx020032FA,0 34=CP(F+14,3)(F-14,2)0,11,Cx03003380,x48474952 35=CP(F+14,3)(F-14,2)0,11,Cx02003384,x0054 36=CP(F+14,3)(F-14,2)0,11,Cx020032FA,0 37=CP(F-14,3)(F-14,2)0,11,Cx03003380,x454E4F4E 38=CP(F-14,3)(F-14,2)0,11,Cx01003384,x00 39=CP(F-14,3)(F-14,2)0,11,Cx020032FA,0 40=CP(F+14,3)(F+14,2)0,11,Cx03003380,x5446454C 41=CP(F+14,3)(F+14,2)0,11,Cx03003384,x52202B20 42=CP(F+14,3)(F+14,2)0,11,Cx03003388,x54484749 43=CP(F+14,3)(F+14,2)0,11,Cx01003392,x00 44=CP(F+14,3)(F+14,2)0,11,Cx020032FA,0 45=CP(F-14,3)(F+14,2)0,11,Cx03003380,x5446454C 46=CP(F-14,3)(F+14,2)0,11,Cx01003384,x00 47=CP(F-14,3)(F+14,2)0,11,Cx020032FA,0 Any idea what is casuing these eratic anomalies ? Many thanks David

Pete, Many, many thanks for your invaluable help - I understand it now (the bit I was missing was the control number). Now that it all makes sense I have programmed the two joytsick buttons to display what I need. For your information, my joystick has two shift buttons which gives me in excess of 60 possible buttons to play with in 4 tiers (Shift off, Left shift on, Right shift on, Left & Right shifts on). So I now display the status of the shift keys in the PM EICAS page via AdvDisplay - this eliminates the confusion of which "page" of joystick commands I'm using. Once again, thanks for all your help on this. David

Hi Pete, Sorry to bother you with this one again - I have been trying to work out how to do this (see earlier postings) over the last few evenings using the Advanced FSUIPC User Guide (section on adding offset conditions) and the offset list in the Programmers guide but I am getting nowhere - maybe I'm missing a trick or just not undersanding hexdecimal or something but I can't make head nor tail of how the examples in the Advanced user guide are constructed e.g. 31=P174,10,Cx510066C0,x00030001 - the value in the Byte at offset 66C0 is cycled from 0–3, and back to 0, by button 174,10 - trouble is I don't understand how to translate Cx510066C0,x00030001 into your explanation and I'm still trying to get to a point where I can display the status of my joystick shift buttons in FS2004 (via 32FA). Any chance you can show me a simple example to display the character L when the button is pressed Many thanks

Hi Pete - thanks for your prompt response. No, I am not writing a program, I just want a way of getting the status of my joystick shift keys displayed so I know which ones are set. I'm afraid this stuff is all new to me so please bear with me with what may appear to be stupid questions - here goes : 1) I assume then, that this is achieved by adding instuctions to the [buttons] section for the relevant joystick button 2) If this is so then I also assume that there is a way to tell FSUIPC to update AdvDisplay when the relevant button is pressed. 3) Can I ask you to give me a sample line for a button with an explanation of what each parameter means, please (I can't find anything in your docs that explains this - unless I've missed it !). Many thanks in advance for your guidance David

Hi Pete, Another question for you if I may. I use two keys on my joystick that perform shift function (Left & Right). I have programmed them to toggle (Set & Clear) in my FSUIPC.INI, example as follows : 68=CP(F-0,10)(F+0,11)0,1,C2024,0 69=CP(F+0,10)(F+0,11)0,1,C2031,0 Buttons 10 and 11 on Joystick 0 are obviously the ones I'm using. I would like AdvDisplay to show the words LEFT when 0,10 is set, RIGHT when 0,11 is set and LEFT/RIGHT when both are set but having looked in your SDK I have to admit I don't know where to begin. Can you give me some pointers please ??? Many thanks David