John Fee

Thanks again, Pete. You been incredibly patient. I resisted FSX for years because I have such a lovely FS9 triple monitor setup. Just recently I thought I'd give FSX a go. As far as I know the only program on my client which uses Simconnect is ASE. The others, various loggers and Radar Contact use WideFS. Similarly, FSKeeper uses WideFS I think, but I am not sure. It may seem a silly question but apart from running an addon program on the client, how do you know if/when Simconnect is connected? John

All checked again. Cut and pasted from your post. In correct places. I already copied to the client application folder. Not a dicky-bird! It just refuses to connect! I don't know where to go to from here. Regards John

WideFS connected! :grin: Simconnect still not, unfortunately. J

Pete Many thanks again. I modified the .cfg and .xml files. Still no joy, even with GRETEL instead of the IP numerals. Yes, simconnect.cfg is in the Client's Documents folder. I attempted to run ASE on the Client - just to see. Initially it could not find the FSX application. When I pointed the program to ../Roaming/Microsoft/FSX it loaded up a database. It produced weather but it did not transmit this to FSX. I wonder if the dual boot arrangement is causing problems. John PS More crossing. Will do as per #11. J

Thanks for #8 too, more crossing! I will try your settings. John

Pete Thanks for #6. My post crossed with yours 03.17. I have indeed two versions of the WideClient.exe. I've attached both pairs of .ini and .log files. Obviously this is a complete mess so I'm very grateful for your help. I also have a WideServer.ini and WideServer.dll included in the FSX version of the install. [Config] Port=8002 ;------------------------------- [user] Log=Errors+ ;------------------------------- Regards John WideClient_FS9.zip WideClient_FSX.zip

Pete Simconnect files attached. I included the .cfg (client) as well. Thank you for looking at these. Regards John Simconnect_John.zip

That's kind. I should have said that WideFS does not connect from the Client either. The server is waiting for connection....which is why I sent the first batch of files. It is not only Simconnect. As I said, I never had any trouble with WideFS and FS9. Used it for years and you wouldn't know it was there. If you think FSX's Simconnect is a triumph of software design, and a better way of connecting, I'm surprised. You must be one of very few. ;-) I have to admit that although I have read extensively I am still unclear as to the separate roles of Simconnect and WideFS in FSX. As I understand it, Simconnect is used by FSX to connect to addons such as ASE. Wide FS is used to control hardware from the Client, although this could more easily be done directly on the server machine. Maybe I am completely mixed up! I'll post the simconnect files to you later this morning. Thanks again. John

Pete Yes, of course I installed Simconnect.msi on the Client. There is every reason to install the SDK on the Client. In fact you have to do it to test the connection. The Server and Client SDKs must be the same version though. I ran out of ideas myself. Sorry to trouble you. Yes, obviously I am. I'll just go back to FS9, its a better program anyway. Thanks for your advice. Regards John

Pete I've been struggling with Simconnect for weeks. I now have it running on FSX - checked via FSUIPC4 console log. My problem is that I wish to run Simconnect from a client but cannot make it connect. I've followed all the very detailed installation instructions on the FSDevelopers wiki site for installing the FSX Acceleration SDK. Of the guides I've seen, they were the clearest. My set up: Wireless LAN PC Server: Dual boot Disk 1 - W7 on partition; FSX on separate partition as F:FSX; FSUIPC 4.80 Disk 2 - XP on partition; FS9 on separate partition; FSUIPC 3.997 FSX Acceleration SDK All relevant folders are shared, including the FSX root folder. Everyone can read/write to shared folders. Avast antivirus. Avast Firewall with exclusions for all I.P. addresses in network. Separate permission set to allow all network connections. Windows Firewall off. Laptop Client: W7, FS9 installed FSX Acceleration SDK (FSX itself is not installed on the client) WideFS/WideClient Same Avast firewall permissions as on Server. Windows firewall off. When I run the recommended AI Traffic.exe test from the Client SDK I get nothing. If a connection is made there should be a message to that effect. I get nought! Not even an error. When I attempt to run ASE on the Client it doesn't find FSX on the Server. I have checked, and re-checked the simconnect.xml file (server) and simconnect.cfg file (client) and that these are correct and in the correct folders. I've added the [Config] ServerName=GRETEL and also Protocol=TCP to the WinClient.ini file. There are no problems when running WideFS with FS9 running various addons. I've attached FSUIPC4.ini; FSUIPC4.log;WinClient.ini; WinClient.log files. Sorry to bombard you with this, but I have really done my best to make this work. It has me beat! :( John FSUIPC4.zip

A thorough re-read, and some careful calibrations has brought the 'faulty' throttles back to perfect working order. I reset to maximum sensitivity and zero null zone as well. And I added the STICK_SENSITIVITY_MODE=0 to the fs9.cfg file. Before I posted about my problems with the throttles I had checked that there were no dual assignments. But I had not realised that under Options-Control in FS9 the joystick should be disabled before FSUIPC calibrations. After FSUIPC calibration, the joystick needs to be re-enabled if a control yoke is to be operated under FS control and not FSUIPC. Thanks again, Pete.

I realise that. It is just that the misalignment of the levers on the quadrant frame is getting ridiculous. Thanks for this. I will check out the manual again. Regards John

I run FS9 and my throttle quadrant is calibrated with FSUIPC (3.997p). Over the last few weeks I've noticed that the two throttles are not in synchrony - getting worse. I have not used the sync facility in the program. When I calibrate the max value on throttle 1 is 15539/16384. Throttle 2 is 16038/16384. Is the hardware bust? Or am I missing something with the calibration? Thanks

With FSUIPC 3.98, axis re-allocation, re-calibration, and with a new .ini file, the un-commanded throttle changes have vanished. Everything is working properly now. I've tested the 'problem' aircraft - the Q400 Dreamwings Dash 8, and other aircraft. My guess is that the .ini file posted above was corrupt in some way. I have no plans to install the FSUIPC3989d .dll in the meantime. Thanks for the prompt support, Pete. Regards John

Thanks. I did not refer to other odd effects as I thought one thing at a time. (These included power surges when using the elevator; non-functioning reverse thrust on one engine; erratic prop pitch controls; slow throttle responses generally). Yes, I checked that only the elevator is assigned as an FS2004 control. On approach all is fine, stable power both engines. At around 500 ft above surface the starboard engine goes to full thrust - uncommanded. This makes it practically impossible to land. Eventually, when both prop pitch controls are feathered I can land (not on the runway of course). At that stage the starboard engine remains at full thrust on the ground even when both throttles are at idle. Yes, it sounds crazy but it happens, and it happens every time, and at different airfields. It did not happen with earlier versions of FSUIPC which is why I think it might be FSUIPC-related. As you say, perhaps some bug has been corrected. I have deleted the FSUIPC3989d.dll and re-installed the 3.98 version. I deleted the FSUIPC.ini file and am now re-allocating axes and re-calibrating. Hopefully, this will solve the problem. Regards John P.S. At one stage I thought it might be related to disconnecting the autopilot. I flew an 18 nm final manually and the same thing happened.

I run FS2004 in XP. I just installed FSUIPC3989d after 3.98a and have had this trouble since. Before this, I was running an earlier version reasonably successfully. This particular engine problem occurs when flying a Q400 Dreamwings Malev addon. I use a Go Flight throttle quadrant. All of a sudden I am getting odd effects. I have checked the axes and the calibrations a dozen times but I still cannot identify the cause of the problem. Throttles, rudder (Saitek Pro), brakes, prop pitch are run from FSUIPC; I use FS2004 to control the elevators and the ailerons. I have attached the .ini file and would be grateful for advice. [General] History=8ET4XJ33OYUEKL6SC0SCN TCASid=Type+ TCASrange=40 TrafficScanPerFrame=10 AxisCalibration=No CentredDialogue=Yes ShowMultilineWindow=Yes SuppressSingleline=No ClearWeatherDynamics=Yes OwnWeatherChanges=No WeatherReadInterval=4 MoveBGLvariables=Yes TimeForSelect=4 WeatherReadsFast=No MainMenu=&Modules SubMenu=&FSUIPC ... WindSmoothing=Yes AutoTaxiWind=No PropTaxiWind=No TimeSetMode=Partial WhiteMessages=No ThrottleSyncAll=No GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=6000 GenerateCirrus=Yes WindShearSharp=No UpperWindGusts=No ExtendMetarMaxVis=Yes CorrectVSsign=Yes DisconnTrimForAP=Yes ZeroElevForAPAlt=Yes AutoClearWeather=Yes ExtendTopWind=No WindSmoothness=5 SmoothPressure=Yes PressureSmoothness=1 SmoothVisibility=Yes VisibilitySmoothness=2 MaxSurfaceWind=0 WindLimitLevel=0 WindDiscardLevel=0 WindAjustAltitude=No WindAjustAltitudeBy=2000 MinimumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 OneCloudLayer=No ThinClouds=No ThinThunderClouds=No CloudThinness=100 ThunderCloudThinness=10000 CloudTurbulence=No CloudIcing=No WindTurbulence=No SuppressAllGusts=No ExternalOptionControl=Yes AutoTuneADF=No KeepFS98CloudCover=No ShowPMcontrols=No MagicBattery=Yes RudderSpikeRemoval=Yes ElevatorSpikeRemoval=Yes AileronSpikeRemoval=Yes ReversedElevatorTrim=No StopAutoFuel=No TrapUserInterrupt=Yes NavFreq50KHz=Yes ClockSync=Yes SmoothIAS=Yes SetVisUpperAlt=No VisUpperAltLimit=0 MaxIce=-1 MinIce=-1 WindSmoothingDelay=0 WindSmoothAirborneOnly=No LimitWindVariance=No VisSmoothingDelay=0 VisSmoothAirborneOnly=No TrafficControlDirect=Yes SuppressCloudTurbulence=No SuppressWindTurbulence=No SpoilerIncrement=512 ShortAircraftNameOk=No FixWindows=No FixControlAccel=Yes MouseWheelTrim=No MouseWheelTrimSpeed=1 AxisInterceptIfDirect=No ZapSound=firework UpdatedByVersion=3989 UseProfiles=Yes BrakeReleaseThreshold=75 DontResetAxes=No JoystickTimeout=20 PollGFTQ6=No BlankDisplays=No LuaRerunDelay=66 SuppressMultilineFS=No [JoystickCalibration] SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes AllowSuppressForPFCquad=Yes Aileron=-16185,-2714,2713,16349 Elevator=-15727,-2331,2076,15893 UseAxisControlsForNRZ=No PropPitch1=-13595,-6100,-1917,16211 PropPitch2=-14223,-7202,-2341,16383 LeftBrake=-16384,9249/16 RightBrake=-16384,9513/16 Throttle1=-16035,-10806,-6449,16383 Rudder=-16190,-1097,1088,16320 FlapStarts=-16384,-12183,-2886,16383 Flaps=-16201,16023/48 FlapEnds=-16384,-12183,-2886,16383 SyncSlopePropPitch2=0/0 Spoilers=-13072,7761,9658,16211/16 Throttle=-16380,16380 PropPitch=-15512,16039 Mixture=-15831,16383 Throttle4=-16035,-10806,-6449,16383 Throttle2=-16203,-10802,-6661,16205 Throttle3=-16203,-10802,-6661,16205 [MacroFiles] 1=vasfmc [JoyNames] AutoAssignLetters=No 1=Saitek Pro Flight Rudder Pedals 0=GoFlight GF-TQ6 Throttle System 2=CH ECLIPSE YOKE 0.GUID={4D297B30-0C2D-11DF-8001-444553540000} 1.GUID={5B6F44C0-0B67-11DF-8001-444553540000} 2.GUID={8D7601C0-1C65-11DF-8001-444553540000} [buttons] ButtonRepeat=20,10 2=R0,3,K35,8 3=U0,3,K35,8 4=R0,2,K36,8 5=U0,2,K36,8 8=P0,5,K66,8 9=P0,4,K190,8 12=P0,20,K190,10 13=P0,22,K113,8 14=U0,22,K112,8 22=R0,9,K35,8 23=R0,8,K36,8 [Axes.Dreamwings Q400 Malev] 0=0X,256,D,17,0,0,0 1=0Y,256,D,18,0,0,0 2=0Z,256,D,9,0,0,0 3=0R,256,D,23,0,0,0 4=0U,256,D,6,0,0,0 5=0V,256,D,0,10,0,0 6=1X,256,D,7,0,0,0 7=1Y,256,D,8,0,0,0 8=1R,256,D,3,0,0,0 9=2R,1,D,9,0,0,0 [JoystickCalibration.Dreamwings Q400 Malev] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-16185,-2714,2713,16349 Elevator=-15727,-2331,2076,15893 Rudder=-16190,-1097,1088,16320 PropPitch1=-15686,-4357,-349,16211 PropPitch2=-15483,-5041,-900,16383 LeftBrake=-16384,16383/16 RightBrake=-16384,16383/16 Flaps=-16201,16023/48 SyncSlopePropPitch2=0/0 Throttle1=-16035,-10283,-7146,16209 Throttle2=-16384,-10442,-7022,16205 [Axes] 0=0Z,256,D,9,0,0,0 1=0Z,U,-10806,-7320,65820,0 2=0Z,U,-5926,-1569,66226,0 3=0R,256,D,23,0,0,0 4=0U,256,F,65767,0,0,0 5=0V,256,D,0,10,0,0 6=1X,256,D,7,0,0,0 7=1Y,256,D,0,8,0,0 8=1R,256,D,3,0,0,0 [Profile.Dreamwings Q400 Malev] 1=Dreamwings Q400 Malev 2=Dreamwings Dash 8 -Q400 Malev 3=Dreamwings Dash 8 Q400 Malev HA-LQA 4=Dreamwings Dash 8 Q400 Malev HA-LQD 5=Dreamwings Dash 8 Malev-HALQB 6=Dreamwings Dash 8 -Q402 Team Lufthansa 7=Dreamwings Dash 8-Q400 flybe G-JEDI 8=Dreamwings Dash 8-Q400 flybe G-JECV 9=Dreamwings Dash 8-Q400 flybe G-JECT 10=Dreamwings Dash 8 Q400 Malev HA-LQB [Profile.F50] 1=Dreamwings Fokker v3 Flugfelag 2=KLM-PAOB Fokker 50 version 1.0 3=KLM-new-PAOB Fokker 50 version 1.0 [Axes.F50] 0=0X,256,D,17,0,0,0 1=0Y,256,D,18,0,0,0 2=0Z,256,D,9,0,0,0 3=0R,256,D,23,0,0,0 4=0V,256,D,10,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1R,1,D,3,0,0,0 [JoystickCalibration.F50] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-16380,-512,512,10000 Elevator=-16380,-512,512,16380 PropPitch=-16380,16380 LeftBrake=-16384,7168/16 RightBrake=-16380,7168/16 Throttle1=-16035,-9935,-5403,16209 PropPitch1=-16384,0,512,16039 PropPitch2=-16203,0,512,16203 PropPitch3=0,0,512,16380 PropPitch4=0,0,512,16380 Rudder=-16384,-2129,1984,16383 Flaps=-16203,16384/16 Throttle2=-16203,-9902,-5401,16205 [Profile.Dash 7] 1=Dash 7-100 Greenland Air [Axes.Dash 7] 0=0X,256,D,5,0,0,0 1=0Z,256,D,9,10,0,0 2=0R,256,D,23,0,0,0 3=0U,256,D,6,0,0,0 4=0V,256,D,12,11,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1R,256,D,3,0,0,0 8=2Y,256,D,2,0,0,0 [JoystickCalibration.Dash 7] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=No ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-16380,-512,512,16380 Elevator=-16380,-512,512,16380 LeftBrake=10306,16384/16 RightBrake=11627,16384/16 PropPitch2=-16384,-15303,-15303,16027 PropPitch3=0,0,512,16380 PropPitch4=0,0,512,16380 Rudder=-16384,-710,704,16128 MapProp=Yes Flaps=-16201,16023/16 Mixture=-15831,16383/16 MapThr12to34=Yes MapThrottle=Yes Throttle1=-16035,-12549,-9935,16380 [Profile.A320] 1=Airbus A320-232 IAE British Airways G-EUUM 2=Project Airbus A320-210 Airbus Housecolors vasFMC 3=Project Airbus A320-200 Swiss International Air Lines 4=Airbus A319-132 British Airways G-EUPZ [Axes.A320] 0=0X,256,D,22,0,0,0 1=0Z,256,D,9,0,0,0 2=0R,256,D,23,0,0,0 3=0V,256,D,10,0,0,0 4=1X,256,D,7,0,0,0 5=1Y,256,D,0,8,0,0 6=1R,256,D,3,0,0,0 [JoystickCalibration.A320] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No FlapStarts=-16384,-11522,-7562,-720,12925 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Rudder=-16254,-129,64,16192 LeftBrake=9472,16383/16 SlopeLeftBrake=6 RightBrake=9513,16380/16 SlopeRightBrake=6 Throttle1=-14641,-8540,-4357,16035 Throttle2=-14583,-9182,-4321,16027 Spoilers=-13769,16039/16 FlapEnds=-16203,-9542,-4861,1638,16384 Flaps=-16201,16380/16 [buttons.A320] 0=P2,1,K113,8 [Profile.Single engine GA] 1=Cessna Skyhawk 172SP 2=Cessna Grand Caravan Paint2 3=Piper PA28-161 Warrior II -1 4=Cessna Skylane 182S 5=Cessna Skyhawk 172SP Kangan Batman TAFE by RealAir Simulations 6=PA-28 Archer REDBROWN 7=Piper Warrior-II_nwf_panel_16x9 [Axes.Single engine GA] 0=0X,256,D,6,0,0,0 1=0Y,256,D,5,0,0,0 2=0Z,256,D,4,0,0,0 3=0R,256,D,23,0,0,0 4=0U,256,D,6,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,0,8,0,0 7=1R,256,D,3,0,0,0 [Profile.1900D] 1=Danish Air Transport Beech B1900D [Axes.1900D] 0=0X,256,D,17,0,0,0 1=0Y,256,D,0,18,0,0 2=0Z,256,D,9,0,0,0 3=0Z,U,-10806,-7320,65820,0 4=0Z,U,-5926,-1569,66226,0 5=0R,256,D,23,0,0,0 6=0U,256,D,23,0,0,0 7=0V,256,D,0,10,0,0 8=1X,256,D,7,0,0,0 9=1Y,256,D,0,8,0,0 10=1R,256,D,3,0,0,0 11=2U,256,D,6,0,0,0 12=2V,256,D,4,0,0,0 [JoystickCalibration.1900D] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No FlapStarts=-16384,-12183,-2886,16383 FlapEnds=-16384,-12183,-2886,16383 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-15688,-1390,1580,15181 Elevator=-15530,-1510,1736,15742 Rudder=-16380,-2774,1664,16256 Throttle=-16035,15861 PropPitch=-16023,15843 Mixture=-15686,16039 LeftBrake=-6144,16384/16 SlopeLeftBrake=9 RightBrake=-6400,16384/16 SlopeRightBrake=9 Throttle1=-14641,-9238,-5221,16205 Throttle2=-14943,-10082,-5221,16205 PropPitch1=-16035,-2963,512,16383 PropPitch2=-16203,-3061,512,16380 PropPitch3=0,0,512,16380 PropPitch4=0,0,512,16380 Flaps=-16201,16203/16 Reverser=-16384,16319 [Profile.PMDG_B736] 1=B737-600 2=British Airways B737-700 3=PMDG 737-8AS (Winglets) Ryanair NC EI-EBB - Virtual Cockpit & Cabin 4=FeelThere Boeing 737-400 British Airways full 5=FeelThere Boeing 737-400 Malev full 6=B737-700 Alaska Airlines - Virtual Cockpit/Stairs 7=Boeing 737-700 continental 8=Project Opensky - Boeing 737-600 Malev [Axes.PMDG_B736] 0=0X,256,D,22,0,0,0 1=0Z,256,D,9,0,0,0 2=0R,256,D,23,0,0,0 3=0V,256,D,0,10,0,0 4=1X,256,D,7,0,0,0 5=1Y,256,D,0,8,0,0 6=1R,256,D,3,0,0,0 [Profile.DC3] 1=Douglas C-47 RAF KG444 2=Douglas DC-3A BEA Keyline [Axes.DC3] 0=0X,256,D,5,0,0,0 1=0Z,256,D,9,0,0,0 2=0Z,U,-10806,-7320,65820,0 3=0Z,U,-5926,-1569,66226,0 4=0R,256,D,23,0,0,0 5=0U,256,D,6,0,0,0 6=0V,256,D,0,10,0,0 7=1X,256,D,7,0,0,0 8=1Y,256,D,0,8,0,0 9=1R,256,D,3,0,0,0 10=2U,256,D,6,0,0,0 [JoystickCalibration.DC3] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No FlapStarts=-16384,-12183,-2886,16383 FlapEnds=-16384,-12183,-2886,16383 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-15688,-1390,1580,15181 Elevator=-15530,-1510,1736,15742 Rudder=-16190,-2129,1984,16192 Throttle=-16035,15861 PropPitch=-16035,16211 Mixture=-16384,16201 LeftBrake=-6144,16384/16 SlopeLeftBrake=9 RightBrake=-6400,16384/16 SlopeRightBrake=9 Throttle1=-16209,-13595,-12549,16383 Throttle2=-16203,-13683,-12783,16383 PropPitch1=-16203,0,512,16039 PropPitch2=-16203,0,512,16203 PropPitch3=0,0,512,16380 PropPitch4=0,0,512,16380 Flaps=-16023,16201/16 Reverser=-16384,16319 [Profile.Pilatus PC12] 1=F1_Pilatus_PC-12 HB-FPA 2=F1_Pilatus_PC-12 N476D [Axes.Pilatus PC12] 0=0X,256,D,17,0,0,0 1=0Y,256,D,17,18,0,0 2=0Z,256,D,9,0,0,0 3=0Z,U,-10806,-7320,65820,0 4=0Z,U,-5926,-1569,66226,0 5=0R,256,D,23,0,0,0 6=0U,256,D,23,0,0,0 7=0V,256,D,0,10,0,0 8=1X,256,D,7,0,0,0 9=1Y,256,D,0,8,0,0 10=1R,256,D,3,0,0,0 11=2Z,1,D,4,0,0,0 12=2U,256,D,6,0,0,0 13=2V,256,D,4,0,0,0 [Profile.Fokker_F100/70] 1=Gmax V2 F-70 Malev Tay620-15 2=Fokker 70 Malev HA-LME [Axes.Fokker_F100/70] 0=0Z,256,D,9,0,0,0 1=0Z,U,-10806,-7320,65820,0 2=0Z,U,-5926,-1569,66226,0 3=0R,256,D,23,0,0,0 4=0V,256,D,0,10,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,0,8,0,0 7=1R,256,D,3,0,0,0 [Profile.B777] 1=Project Opensky -- Boeing 777-200ER - British Airways - Union Flag [Axes.B777] 0=0X,256,D,22,0,0,0 1=0Z,256,D,9,0,0,0 2=0Z,U,-10806,-7320,65820,0 3=0Z,U,-5926,-1569,66226,0 4=0R,256,D,23,0,0,0 5=0V,256,D,0,10,0,0 6=1X,256,D,7,0,0,0 7=1Y,256,D,0,8,0,0 8=1R,256,D,3,0,0,0 [Profile.PMDG_B738] 1=PMDG 737-8AS (Winglets) Ryanair NC EI-EBB - Virtual Cockpit [Axes.PMDG_B738] 0=0X,256,D,22,0,0,0 1=0Z,256,D,9,0,0,0 2=0Z,U,-10806,-7320,65820,0 3=0Z,U,-5926,-1569,66226,0 4=0R,256,D,23,0,0,0 5=0V,256,D,0,10,0,0 6=1X,256,D,7,0,0,0 7=1Y,256,D,0,8,0,0 8=1R,256,D,3,0,0,0 [JoystickCalibration.PMDG_B738] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No FlapStarts=-16384,-12183,-2886,16383 FlapEnds=-16384,-12183,-2886,16383 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-16185,-2714,2713,16349 Elevator=-15727,-2331,2076,15893 Rudder=-16190,-1097,1088,16320 LeftBrake=-16384,9249/16 RightBrake=-16384,9513/16 Throttle1=-12375,-9586,-5054,16209 Throttle2=-13323,-10082,-4861,16383 PropPitch1=-13595,-6100,-1917,16211 PropPitch2=-14223,-7202,-2341,16383 SyncSlopePropPitch2=0/0 Spoilers=-13072,7761,9658,16211 Flaps=-16201,16023/48 [Programs] [Profile.Aviat Husky] 1=Aviat Husky A-1B TT 2=Pilatus Porter [Axes.Aviat Husky] 0=0X,256,D,5,0,0,0 1=0Z,256,D,9,0,0,0 2=0Z,U,-10806,-7320,65820,0 3=0Z,U,-5926,-1569,66226,0 4=0R,256,D,23,0,0,0 5=0U,256,D,6,0,0,0 6=1X,256,D,7,0,0,0 7=1Y,256,D,0,8,0,0 8=1R,256,D,3,0,0,0 [JoystickCalibration.Aviat Husky] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No FlapStarts=-16384,-12183,-2886,16383 FlapEnds=-16384,-12183,-2886,16383 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-16185,-2714,2713,16349 Elevator=-15727,-2331,2076,15893 Rudder=-16190,-1097,1088,16320 Throttle=-16380,16380 PropPitch=-15512,16039 Mixture=-15831,16383 LeftBrake=-16384,9249/16 RightBrake=-16384,9513/16 Throttle1=-16035,-16035,512,16383 Throttle2=-16384,-9362,-7562,16383 PropPitch1=-13595,-6100,-1917,16211 PropPitch2=-14223,-7202,-2341,16383 SyncSlopePropPitch2=0/0 Spoilers=-13072,7761,9658,16211/16 Flaps=-16201,16023/48 [Profile.Bristol Britannia] 1=JBK Britannia [Axes.Bristol Britannia] 0=0X,256,D,17,20,0,0 1=0Y,256,D,18,19,0,0 2=0Z,256,D,9,12,0,0 3=0Z,U,-5926,-1569,66226,0 4=0R,256,D,23,0,0,0 5=0U,256,F,65767,0,0,0 6=0V,256,D,10,11,0,0 7=1X,256,D,7,0,0,0 8=1Y,256,D,8,0,0,0 9=1R,256,D,3,0,0,0 10=2X,256,D,1,0,0,0 11=2Y,256,D,2,0,0,0 [sounds] Path=C:\Program Files\Flight Simulation\FS9\Sound\ Device1=Primary Sound Driver Device2=SoundMAX HD Audio

Pete This is just the info I need. Thanks a bunch. John

Pete Sorry if this is a bit off FSUIPC topic. I need to know how .ini files work in FS9. Are they used to set parameters OR do they simply reflect parameters set by a .cfg or .exe or .gau etc file somewhere else. In other words, if I change some values in an .ini file and then re-run FS9, will the program generate another .ini file which ignores my changes? I hope this makes sense. John

Many thanks. You have indeed tried your best. It is quite possible that the designer has made an impossible design. Regards John

I'm nudging it because I want a torque of 16-18. At 13 the engines are at idle. At 23 we are doing 50 knots. I don't taxi at 50 knots. I am tweaking the aircraft.cfg file in order to try to control this runaway tendency. I cannot do it with FSUIPC. The good news is that I now have working profiles for twin jets and single engined pistons. I am close to getting something acceptable for the Dreamwings Dash 8. This has been a very difficult aircraft to set up with the GoFlight TQ6 throttle quadrant. The reason is that torque is programmed to increase in a step-wise and not a linear fashion. Oddly, these step-wise increments (or should I say decrements) do not occur as power is reduced. To reduce torque for descent, the levers must be brought back to idle and then advanced to the lower setting (e.g. to reduce from TRQ 65% to TRQ 35%). This behaviour seems to be programmed into the .air file and I have not been able to modify it using FSUIPC. The same thing happens when using keyboard controls. John

No because when the upper limit of the 'dead' zone is reached another nudge takes TRQ from 13 to 23. Clearly this is built into the .air file but I hoped that FSUIPC might allow me to change this. Easy peasy for me it weren't! :wink: Try as I might I could not get consistent results with this. The main problem was synchronising the two throttles for several 'active' and 'dead' zones for left and right engines. This was a freeware plane so no purchasers! I am certainly not the only one using it - there is quite a little gang of us! But I may well be the only one using it with the GoFlight throttle quadrant. The throttles I suspect were designed to be used with keyboard controls. Either that or a joystick wheel controlling two engines. Both those worked well for me. The problem has been the throttle quadrant. I will fiddle on with this and if I find settings which are consistent and produce the desired results I'll maybe post again. Thanks for your help, Pete. Regards John

Okay, but I will leave this adjustment till last. You misunderstand this bit. There is a 'dead' zone. The throttle lever moves maybe 2 cm between the lever positions which give a TRQ of 13% and 23% . The problem is that the TRQ suddenly jumps from 13% to 23% once I hit the next 'active' part of the travel. In this way, although there is a 2cm dead zone, at the upper end of the zone there is only millimetres between TRQ 13 and TRQ 23. There is nothing in between these values. I suppose the throttle control values reach a 'gate' which triggers this jump. Is there any way to produce an intermediate value between 13 and 23 for TRQ? Or is that built into the .air file? Or the aircraft.cfg file? Do you mean I should use the right hand side of the panel to send the correct ranges in the first place? If so, how can I do this without using buttons or switches? These seem to be the only controls available on the right side. The Dreamwings Dash 8 Q400 engine controls seem to be set up exactly like an Airbus. Thanks again for your patience with this. Rgrds John

I increased the dead zone but not the 'Delta' value. This helped and I am now beginning to get the hang of flying this bird. The throttles are synch'd to produce torque (TRQ) values within approx 3% of each other - this varies depending on the power setting - 0% at TOGA, 1% at idle, 2% at taxi (first gate), 3-4% at climb thrusts and cruise settings. So far I have kept prop pitch at full fine for all this testing but I will experiment with this. On the use of 'Sync Pos' - should this be activated when all the calibrations settings are at the desired values? Or in pairs? For example, when setting the max values for the two throttles? Then the same for the min values etc? The settings now are: Throttle 1: -16035, -9586, 512, 15512 Throttle 2: -16203, -9542, 356, 16205 The larger dead zone has helped with the taxi but even so, the tiniest pressure on either throttle lever will increase TRQ from 13% (idle) to 23% (taxi) - this TRQ delivers taxi speeds of up to 40 knots :shock: That is really the nub of the problem. Also, the AIR file makes constant adjustments so that when the throttle reaches a new 'gate' the TRQ takes time to balance. I did not use autothrottle for any of this testing. For approach and landing I have found that if the TRQ is set to 40% (this matches one of the power 'gates') then once the initial approach speed is reached, the use of flaps at the designated speeds will result in the correct approach speeds - more or less. In a sense if you let it, this plane will fly itself. Which brings me on to trim. It is vital for anyone flying this plane (Dreamwings Q400 with vasFMC mods for Malév Hungarian available on AVSIM) to disconnect the AP by at least at 1000 ft or 4-5 nm before runway threshold. This will give vital extra seconds to trim the plane, essential for control with AP disconnected at minimums and for a smooth landing. In Cat II it is probably best to wait till DH before disconnecting AP and to trim at 150 feet - not ideal I know. Pete, I am not sure what you mean about using the axis calibrations on the right side to help with allocating power zones. That part of the panel seems to do with setting buttons and switches to do certain things under pre-defined conditions. For example when a particular throttle setting is reached the landing gear will deploy. I cannot see how this section can be used to 'zone' power output via throttle axes. Have I missed something? Not again, surely! Best regards John

I'm very grateful for your advice, Pete. Thanks a bunch. Really analogue axes are not terribly suited to that sort of control. But FSUIPC does attempt to allow such "gate" systems by allowing assignments to specific, fixed, controls on the right-hand side of the Axis assignments tab -- the ability to assign controls to different ranges within the axis movement. Is this what you used? No, I've not tried that, and to be honest, I'm not sure I want to. At the moment I seem to have something near to what I had before with the Flightstick. For me, that is progress! The prop pitch controls, you mean? (When I first read that I was thinking elevator, which is of course your prime aircraft pitch control! ;-) ). Yes, prop pitch. But, in fact since my first post I have discovered that the .air file or the aircraft.cfg file does this by adjusting prop pitch via the power settings at taxi, providing the props are not set to feather. But if you are not using the throttles to taxi, what is the problem using pitch as you stated? I've obviously missed something See above. Do you mean on auto-throttle? The A/P controls throttles as well? If there is no autothrottle then there should be no difference at all between the throttle with A/P on or off. If there is an auto-throttle then then your throttle setting shouldn't have anything to do with it, surely? The version I have has an autothrottle but it works with the FADEC. For example if I set speed to 170 knots for climb and VS 1500 ft/min the power settings will adjust to 155 knots for that climb. In cruise and descent the A/THR works normally but it's not very responsive and can vary by 10 knots or more. The RW aircraft has no autothrottle but here it is a great help for descents and on approach. So you aren't using the axis region facilities to assign fixed controls for your 4 modes? Wouldn't that be more precise? Perhaps that's the problem? Maybe. Which parts of the file are you unsure of. most of those parts which users are expected to want to mess with are explained in the Advanced Users guide, and I can explain other parts for you if you wish. I am attaching the FSUIPC.ini but really do not expect you to spend precious time on it. I have 'profiles' I think on Dreamwings Malev Q400; Dreamwings Fokker 50 (Flugfelag Island); Dash 7 (Milton Shupe); Project Airbus A320; and Cessna Skyhawk (this is probably incorrectly set). Of these I only have confidence that the Q400 and the Airbus are correctly set up. Apart from that, there seems a lack of order to say the least! Regards John It's not possible to upload FSUIPC.ini as .txt or .doc ??

Overnight, after a good few attempts, including four separate 'sync positions' in the calibration, I now have the difference between power outputs in the two engines down to 2% on AP. This is acceptable and probably similar to RW. I have also discovered that this Q400 (again as in RW) uses the power output to adjust prop pitch and therefore taxi speed. As long as the prop pitch is set to be 'working' and not feathering, the power levers do the rest. John