John Fee

March 20, 2012

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

November 4, 2011

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.

November 1, 2011

Engines don't all perform exactly the same and the cable connections etc do not all stretch or contract at the same rates.

I realise that. It is just that the misalignment of the levers on the quadrant frame is getting ridiculous.

The values aren't relevant. You should be calibrating with some leeway left at both extremes in any case.

Thanks for this. I will check out the manual again.

Regards

John

November 1, 2011

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

September 26, 2010

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

September 26, 2010

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.

September 25, 2010

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

March 25, 2010

Pete

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

John

March 25, 2010

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

March 9, 2010

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

Regards

John

March 5, 2010

But surely you park it in the centre of the calibrated zone for 13. Why are you nudging it into different zones? surely you only want to do that when you actually want to select different zones! If the lever wouldn't move into those zones it would be pretty useless to you, after all!

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

March 2, 2010

With 2cm of travel surely a little "nudge" as you call it shouldn't change things. you should have the lever in the middle of the 2 cm really. And in any case a "dead zone" is one which sends nothing at all to the sim, it is an area calibrated with no changes whatsoever. i.e "dead".

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.

The whole problem would be easy peasy to solve using zones on the right-hand side of the axis assignments, one well-defined zone to set each individual value which the AIR file needs to set its thrust. You could have a nice little dead zone between each 'gate' that way.
You need to specify a parameter with the AXIS controls, which will be forwarded to the Sim unmolested. Don't calibrate, no need for that then. You just program your 4 zones for the 4 throttle "gates" and assign the axis control with a fixed parameter which makes the air file set that gate. I have no idea what the parameter should be -- you could find out by determining the centre of the range of "OUT" values at present which engage that gate setting.

You can use "Axis throttleN set" (N = 1 to 4 for 4 engines), which has a range of -16383 to +16383, or "ThrottleN Set", which has a range of 0 to 16383 (the negative values are for reverse thrust).

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.

BTW With all this trouble I would expect 99% of the purchasers of this aircraft to have immense difficulty. Are you the only one using it? If not, have you had a look to see if there's a Forum somewhere where users are solving things?

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

February 27, 2010

You need to calibrate every lever properly first, with special care with Engine 1 levers, because they won't change thereafter and are used as the "measure" for recording the equivalent positions on all the others. Naturally get them lined up for min. centre and max positions. The sync positions are only taking care of making them match correctly at the intermediate positions. Don't go overboard with too many "sync" positions -- depending how bad the alignment is you shouldn't need many. FSUIPC will replace any too close though, using the latest.

Okay, but I will leave this adjustment till last.

Sounds like there's no real dead zone then. You could make a dead zone span half of the movement available if you wanted to. I'm sure you should be capable of making it enough so that a slight movement will be ignored -- providing you leave it in its parked position of course.

With these settings:

Throttle 1: -16035, -9586, 512, 15512

Throttle 2: -16203, -9542, 356, 16205

where are you "parking" the throttles whilst taxiing? In the centre idle position? If so there should surely be enough movement available with that 10,000 odd space. You certainly don't seem to have any noticeable "dead zone" at either minimum or maximum positions -- 16383 is the very limit of possibility.

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?

I think some Airbus implementations actually use fixed controls or keypresses to select throttle modes, in which case those controls or keypresses would be sent instead, but it sounds like your aircraft needs the actual throttle values but interprets ranges rather than specific values. So why not send the correct specific values in the first place?

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

February 26, 2010

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

February 25, 2010

I'm very grateful for your advice, Pete. Thanks a bunch.

The aircraft models the FADEC engine control system in the RW plane giving basically four power settings - idle, climb (2 speed settings here), and TOGA.

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!

When I used a simple CH Flightstick Pro along with keyboard commands, it was possible to use the keyboard pitch controls to control the taxi speed with the throttles set at idle. This is neatly modelled in this version of the Dreamwings Q400 and is what happens in the RW aircraft as far as I know. (It is one of the delights of the plane, along with the superb sounds).

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.

I cannot do this with the set up above. In fact it is almost impossible to taxi since the throttle goes from idle to max thrust in three steps in the style of an Airbus.

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.

I also cannot get the throttles to synchronise on autopilot. They are fine on manual but on switching to AP there is a 9% difference in torque (left engine > right).

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.

Throttle1=-16209,-9063,512,16035

Throttle2=-16203,-9002,512,16027

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.

The FSUIPC.ini file is a bit of a mess - the result I suppose of many attempts to get things exactly right. I do not know the structure of this file or I would try to tidy it up manually.

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 ??

February 25, 2010

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

February 25, 2010

After a lot of mostly self-induced hair pulling, I have managed to set up the Dreamwings Dash Q400 to use CH Eclipse yolk, Saitek rudder pedals, and GoFlight TQ6 throttle quadrant.

I assigned the yoke to FS; the rudder pedals and the GF inputs are managed by FSUIPC.

This version of the Q400 has a customised panel which includes a merge with vasFMC gauges. This may be the reason my settings seem so difficult to get right. The aircraft models the FADEC engine control system in the RW plane giving basically four power settings - idle, climb (2 speed settings here), and TOGA. There are thrust reversers which work on the throttles.

I have two problems:

When I used a simple CH Flightstick Pro along with keyboard commands, it was possible to use the keyboard pitch controls to control the taxi speed with the throttles set at idle. This is neatly modelled in this version of the Dreamwings Q400 and is what happens in the RW aircraft as far as I know. (It is one of the delights of the plane, along with the superb sounds). I cannot do this with the set up above. In fact it is almost impossible to taxi since the throttle goes from idle to max thrust in three steps in the style of an Airbus.

I also cannot get the throttles to synchronise on autopilot. They are fine on manual but on switching to AP there is a 9% difference in torque (left engine > right). The relevant FSUIPC.ini details are below.

PropPitch1=-16209,-9063,512,16039

PropPitch2=-16203,-9002,512,16023

Throttle1=-16209,-9063,512,16035

Throttle2=-16203,-9002,512,16027

The FSUIPC.ini file is a bit of a mess - the result I suppose of many attempts to get things exactly right. I do not know the structure of this file or I would try to tidy it up manually. I could delete it and start again but I've spent so many days and nights setting up five aircraft of various types that I want to avoid doing that if possible.

Thanks for any help.

John

February 19, 2010

I'm still struggling with setting up thrust reversers for twin jet and turboprop types. I'm running 3.972 and I've set PollGFTQ6=No. The reversers are identified as Joy 2, buttons 1, 2.

On the GoFlight module I have calibrated throttles and flaps (4 stages) and spoilers using FSUIPC and all work fine. (I also have prop pitch controls and mixture settings successfully calibrated for props and turboprops).

I have managed to get as far as reverse thrust activation with the TQ6 using key press F2 but this acts only momentarily. I have set F2 to repeat. I also tried using the FS control with Throttle Dec but this produced the same result - momentary reverse thrust only. Parameter showed 0.

Update:

Messing around, I just discovered that the mixture axes in the GoFlight TQ6 (far right levers 5,6) activate reverse thrust. No need for buttons! Hooray! All working like a dream now. Thanks, as always, Pete.

February 10, 2010

As for "FSUIPC seeing thrust reversers as buttons", there is no way to "see axes as buttons", ever.

.

Okay.

The "buttons" we were talking about are those also built into the TQ6 and, I think, depressed when you pull the sticks right back.

There are no actual buttons on the TQ6. The point is that the four upper middle axes can be set using the GoFlight setup program to function as thrust reversers. In the photo they are the four small white levers using the same 'runs' as the throttles. They look like levers (axes) but function as switches. They do not have potentiometers. They switch ON when pulled aft towards the user and OFF, hopefully, when pushed for'ard. I would like to know if it is possible to set these 'switches' up using FSUIPC.

Thanks.

John

February 10, 2010

So where are we on this? I have the same problem. How to set the TQ6 thrust reversers to activate and deactivate using FSUIPC (v.3.966) in FS9. I have levers 3 and 4 set up as throttles, levers 1 and 2 are prop pitch controls. Levers 5 and 6 are unused in this aircraft (F-50). I have disabled the FS joystick controls. How can I make FSUIPC see the thrust reversers in the photo above as buttons? Maybe I have missed something obvious.

John

February 4, 2010

There are a few companies around these days making those, though whether they come flat-packed or pre-assembled I don't know -- most likely flat-packed as they're shipped world-wide. For 737NG especially you can get the MIP (main instrument panel, pilot only or both pilot and copilot) pre-cut and ready for glass screens and switches, also overheads and centre pedestals, all of which you can fit the switches and gauges and do your own wiring. Your choice of fittings and electronics, or they'll supply too, usually.

No, you'll be surprised at what you can find if you look around. My eyes were opened when I first visited the Lelystad FS Weekend a couple of years ago. There's a tremendous variety of stuff available, and more, it seems, every day. Pay a visit to MyCockpits some time and scan through the variations there, for starters. http://www.mycockpit.org

Regards

Pete

Thanks, yet again. I've just been listening to your interview on the mycockpit site. Excellent stuff. I looked at the SimSamurai site too and will go through the FSUIPC tutorial as soon as I get a chance. I'm sure his FS9 guide is equally good - I might even buy it. Between these two websites, and the next Lelystad FS show (?) I've got plenty to chew on.

February 4, 2010

Thanks again. I like your precise way of doing things! I will take a look at the other website but I am pleased with my progress using your guides, especially now that I can 'profile' types of aircraft.

I am at the start of upgrading my controls and I do not really know where that will lead. I know that I would not have the expertise or the patience to design a cockpit but I could certainly build one if it came flat-packed. That is meant as a serious suggestion. A flat pack would just be a skeleton into which controls, switches and screens could be placed when or if required. Hopefully, there is some standardisation between different brands of switches etc. A cockpit like that would have to be adaptable to different aircraft types and would be designed for single seat operation only.

It is just that there would seem to be scope for a bare bones 'ready made' cockpit to fill a gap between the 'keyboard/joystick/monito-on-a-table' set up and the all-singing, all-dancing cockpits shown on the Project Magenta, PFC or GoFlight websites.

Just a thought. Probably unrealistic. :roll:

February 3, 2010

As well as reversing (and re-calibrating afterwards), you will find you also need to calibrate the "brakes off" position with both pedals slighly pressed, otherwise you can find yourself inadvertently getting braking when simply using the rudders.

Joy! Reversing and recalibration cured the problem. I don't have exactly the same numbers for the Min ('brakes off') values but this doesn't seem to be critical.

Now that I have crept up the learning curve a little, I would like to delve deeper into FSUIPC. Without a knowledge of programming I find parts of the Users Guide a bit daunting, and the Advanced Guide is mostly incomprehensible. For example, now that I have set up a functioning, admittedly basic, Q400 profile, can I create 'generic' versions for GA singles, GA twins, twin engined jets, other twin turboprops, tail-draggers etc? Or is it better to set up individual aircraft? I have dozens!

Thanks very much again.

February 2, 2010

It still certainly sounds like you are suffering from the rather over-strict timeout checks I put into FSUIPC 3.96. I would strongly advise you to replace the DLL with the later one from the Updates and other Goodies announcement above.

I did this and it did help I think. I have elevator, ailerons, throttles (2), prop pitch control (2) all functioning well - smoother inputs than when using FS9 calibration. I have assigned elevator trim and hat view buttons and these all work fine. I have also assigned rudder pedals and differential toe brakes.

I am beginning to understand the immense power and flexibility of FSUIPC but for now my remaining problem is with the brakes. I can operate differential brakes (shown by red indicators) with either toe brake but this is being over-ridden by a general brake command which does not respond to keyboard 'full stop'.

Are you sure you don't have interference occurring from assignments in FS? You must not have the same axes or buttons assigned in both FS and FSUIPC. Only one or the other, or they will certainly interfere with each other.

Yes, absolutely sure. In normal and slew modes. In fact, I have disabled joystick in FS9 Options/Controls.

Thanks again.

John

February 2, 2010

Thanks.

I'm using 3.96. I made some progress since I posted. I had to close and re-open FSUIPC before I could set the 3rd and 4th assignments on the GF-TQ6 (axis propeller 1 and 2). When I re-opened FSUIPC again I could use the joystick calibration - page 5 prop pitch. I am still not sure that I used the calibration routine correctly. It was good for prop 1 but I could not calibrate prop pitch 2 separately. I just checked map 1 to 12; 2 to 34 and this seems to work quite well although sometimes it is not consistent - may indeed have something to do with timing. The Dreamwings Q400 models the real world FADEC system very faithfully so the manually controlled engine response curves are not a straight line - if that makes sense.

I am still not sure how to alter the sensitivity of the elevator/ailerons - is it simply by altering the slope function?

Thanks again for FSUIPC, WideFS and your help.

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Fee

Important Information