[SA WXR functionality in the Fire Module]

Thanks, is that functionality provided by the SA-WXR button in the Fire Module, so that button simply has to be pressed to achieve that? 

[Fire test switch not working]

Pls see ticket 9503 - All seems to be working ok except the Fire test switch does nothing, neither if I press it on the cpflight hw (running the latest firmware and I checked the button is working), nor if I press it directly in PMSystems (v202). Can you just try this and see if you have the same issue? (On an earlier version of PMsys this was working ok so I would assume the problem must be in the pm737sys.lgc file).

 

Attached is the lgc file that you sent me to use with pmsys v 202

 

Is there anything I can try out offline, as it seems to be difficult for us to find time to hook up on Teamviewer,...although I will be with the sim until Wed

 

Best

Charles

pmsys737.zip

[SA WXR functionality in the Fire Module]

Hi, I have the Boeing fire module v 2.7.1.0 and see that there is a button in the software for SA-WXR, which I run on my Project Magenta suite (via the CDU and GC).  I have CPFlight hardware which runs from the CPFlight MCP.

 

What functionality does the SA-WXR button provide with the CPFlight WXR module? I could not see anything mentioned on the product description

 

Best

Charles

[Fire system and link with FSX failures]

Ok, please let me know when ready

Best

Charles

[Fire system and link with FSX failures]

HI Achilles, any joy with this?

Best

Charles

[Fire system and link with FSX failures]

Brilliant, many thanks Achilles!

[Fire system and link with FSX failures]

Thanks Achilles, I am not very confident of doing this, I would be very happy to pay for this functionality if you can help out. 

 

What I want is that, where there is a fire failure triggered within FSX (engines or APU), that it triggers the same failure within FSPS.  Also, if I correct the failure within FSPS (eg putting out the fire by activating the bottles) this corrects the failure within FSX.

 

(I use FSPS with PMsystems v202.  I use FSCaptain which generates random failures including fires, these all being FSX failures and not PM failures)

[Fire system and link with FSX failures]

I discovered that if you have an FSX fire failure, it does no interact with the FSPS fire system to set off fire bells, etc.  Worse still there is no way of putting the fire out via FSPS, only way is to get into the FSX cockpit and press the fire discharge bottles there, which is very difficult if you have a real cockpit.

 

I have failures armed via FSCaptain and would like that when a fire is triggered by this (which presumably must be  an FSX fire failure) that it would trigger FSPS too and can be extinguished by FSPS.  Is this possible?  At the very least I need to be able to put out the FSX fire failure using FSPS

[FSPS fire module broken with project magenta]

I am now on the latest version of project magenta's PM Systems version 202 and latest PM MCP version 503a and latest CPFlight firmware 1.16 and FSPS fire system version 2.7.1.0.  I removed the logic from the pmsys737.lgc file as per the manual, although the manual is way out-of-date because PM has added in additional logic, concerning which it is unclear whether this needs to be deleted or not.

 

With all this nothing on the CPflight fire module works, no bell test, nothing.  On an earlier version of pmsys this was working ok, although I had a problem (ticketed) of the cpflight fire cutout button not stopping the fire bell and the master caution light staying on.

 

First thing I need is for someone at FSPS clearly to show what needs to be removed from the version 202 pmsys737.lgc file.  Then I can test again 

 

I appreciate the FSPS guys must be busy but I am around 2 months with no answer to this on the support ticket system, I'll raise another ticket and see if that helps

 

Best 

Charles

[What to remove from pmsys737.lgc file]

There is a new release of pmsystems (v201k) and it is therefore unclear exactly what bits to remove from the pmsys737.lgc file, as the version of the manual I have is out-of-date.
 
I have highlighted in magenta in the attached file the bits that are different.  Can you let me know exactly which bits I should remove?
 
Would it be possible to be able to get access to the latest version of your fire system software and an updated manual?  For example, create a Downloads section on your site or within "Myaccount"?  That way, each time PM updates pmsys we won't have this problem

 

Rgds

Charles

FSPSC manual vs pmsys lgc file.doc

[Other Project Magenta/CPflight add-ons]

Hi, I run PM software and cpflight hardware

 

I took quite a time to buy the fire system, but since buying it I realise how much more it adds....nowhere when buying it does it mention that it also brings alive the cpflight WXR module, if you use this with SA-WXR...this is excellent and I would have bought this much earlier if I had known....thank you very much for this, it is excellent to know....I suggest you mention this in the product sale page.

 

This also got me thinking that you could develop (you probably already are) a load more products that bring alive cpflight hardware that PM has not addressed.  For example, a few that spring to mind are:

 

• The sys test buttons and inhibit buttons on the copilot MIP are non-functional
• The transponder module does not enable setting of standby and Charlie mode, a big gap if you are using vatsim or IVAO

Thanks again for the great additions you have made

 

Best

Charles

[Unable to load FSX since the new FSUIPC]

Sorry, Pete, apologies I didn't see it. I read the FAQ....good news re your point about persistence because I have not had the message for some time now, so it may just have been due to my reinstall of FSUIPC, but now it has got thru all will hopefully be ok. If not I will try some of the ideas on the FAQ

[Unable to load FSX since the new FSUIPC]

Any thoughts on this?

[Pete's Cockpit]

I loved the video and cockpit, Pete, these always make you feel motivated again!

Btw, re your lack of space, why don't you try 2 LCDs on either side?.I have 2 projectors for the front view connected via Matrox DualHead2Go and my video card handles the extension to 2 LCDs on either side. If this is too much for your video card/CPU you can do this with Wideview too, but I tried that and I found it more fiddly, better to invest in a good CPU and GPU than 2 extra PCs...around Gatwick with UK2000 scenery I am still pumping fps of 40. This 220 deg view gives you so much more immersion and you don't have to use that hat switch anymore, which was the only bit of the video that was not so good

Other thing re the plane, have you tried the Project Opensky 737?....its flight dynamics and feel are very close to the real thing I am told and they have an awesome sound package to go with it. I use it with PM software, there is no difficulty making it work with PM like PMDG and ifly and the models are very well painted (file here http://www.flightsim.com/vbfs/fslib.php?searchid=10491781)

Now I have praised you can you help with my dll issue on loading FSX!?

Best Charles

[Unable to load FSX since the new FSUIPC]

Could it be because it is in my fsx.cfg twice, see below?

[Trusted]

C:\FSX\fsdreamteam\couatl\couatl.exe.ctotreaniuiriteutecwuozhkueateqletqchtai=1

C:\GoFlight\GFDevFSX.exe.neatcoaehunierqttlrrotranenurbnretoacicw=1

C:\FSX\bglmanx.dll.lqohnbcrhiqnbhbohrzqtrrqhhketcrhnbrhnkbe=1

C:\FSX\FsPassengers\bin\fspassengersx.dll.llbokehaiurallquankeoroqonuctkwbkqrzqrkl=1

C:\FSX\VistaMare\ViMaCoreX.dll.ciuczebwbuubbnlewbzlabiaqbhnioqclbuwrche=1

C:\FSX\Modules\FSUIPC4.dll.qbcoubowoobuhroqcitkwearnzbnntcczewobzrt=1

C:\FSX\Modules\FSCopilot.dll.weclqqqhnlenttaucuewewznikhqinoknooqwwel=1

C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll.kzkbcihbutkkzrrthrceqkcozokbcczrtowwlnei=1

C:\FSX\GAUGES\XGauge.DLL.lwnrrnarwnqbbnlaqqzeoeuenrztaatzuubikeut=2

C:\FSX\GAUGES\737-400.DLL.eknnwqqzblklolhzucthwtbrwbrktbrclqhrwque=2

C:\FSX\GAUGES\Mooney_Bravo.DLL.luaqewwezbuecuwczqhatlrctitchunlcohcakhl=2

C:\FSX\GAUGES\Bendix_King_Radio.DLL.nwwwbeawcrqeltukqnacthzcquotcotitwnbocto=2

C:\FSX\FsPassengers\bin\FsPassengersMini.DLL.rozrrlcqlackeaurzbhenukhziihkzikznhwrlwe=2

C:\FSX\fsdreamteam\couatl\couatl.exe.aiqkuaiqruatorlaniznhtabcheubnohozwihhcz=1

C:\FSX\bglmanx.dll.znncqinokqliquwacqoqtbbwkaekabutabirhkqh=1

C:\FSX\Modules\FSUIPC4.dll.bacnrhtoewrnlqituhkzztcnalkinwzcirwuwuuh=1

C:\GoFlight\GFDevFSX.exe.kwehiekcqhothanzbhcazcbhwbetuqlohiqqcork=1

C:\FSX\Modules\FSUIPC4.dll.telrawnqqiqeieqqhoqcuaebaaetiubawwkqucot=1

C:\FSX\fsdreamteam\couatl\couatl.exe.rabenwkqnrakuntqrnbnqeztoiwkbbzhchineaqw=1

C:\FSX\bglmanx.dll.uellencobbrzwirheuaqqhwaeokizinarnknizwb=1

C:\FSX\GAUGES\BoeingGeneric.DLL.khelcneezrhaozitruhqqqitlhuebewnthkknriq=2

C:\FSX\GAUGES\Magnetic_Compass.DLL.obblrqwzckkneeqwzwnoztuhorcoctzwclbzrnbi=2

[Unable to load FSX since the new FSUIPC]

Hi Peter, since I did the reinstall after the certificate issue, I too am unable to load FSX and I have never had this problem before, my FSX has been going strong without problem for 2 years now and I have not loaded anything else. When I boot FSX the following error message appears (this does not happen always, only on occasion):

Flight Simulator has detected a problem with a third-party software program (add-on):

Name: FSUIPC4DLL: FS new universal IPC interface

Version: 4,90

Company: Pete Dowson

File: Modules\FSUIPC4.dll

Do you want to run the software (not recommended):

To avoid seeing the message in the future, uninstall the program or disable its ability to start when running flight simulator. For more information about third-party programs, contact the publisher....

Could it be because I have multiple mentions of fsuipc dll in my fsx cfg, have a look below. Can I just delete all mention of these and let FSX request them to be trusted again or how fix this?

[Trusted]

C:\FSX\fsdreamteam\couatl\couatl.exe.ctotreaniuiriteutecwuozhkueateqletqchtai=1

C:\GoFlight\GFDevFSX.exe.neatcoaehunierqttlrrotranenurbnretoacicw=1

C:\FSX\bglmanx.dll.lqohnbcrhiqnbhbohrzqtrrqhhketcrhnbrhnkbe=1

C:\FSX\FsPassengers\bin\fspassengersx.dll.llbokehaiurallquankeoroqonuctkwbkqrzqrkl=1

C:\FSX\VistaMare\ViMaCoreX.dll.ciuczebwbuubbnlewbzlabiaqbhnioqclbuwrche=1

C:\FSX\Modules\FSUIPC4.dll.qbcoubowoobuhroqcitkwearnzbnntcczewobzrt=1

C:\FSX\Modules\FSCopilot.dll.weclqqqhnlenttaucuewewznikhqinoknooqwwel=1

C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll.kzkbcihbutkkzrrthrceqkcozokbcczrtowwlnei=1

C:\FSX\GAUGES\XGauge.DLL.lwnrrnarwnqbbnlaqqzeoeuenrztaatzuubikeut=2

C:\FSX\GAUGES\737-400.DLL.eknnwqqzblklolhzucthwtbrwbrktbrclqhrwque=2

C:\FSX\GAUGES\Mooney_Bravo.DLL.luaqewwezbuecuwczqhatlrctitchunlcohcakhl=2

C:\FSX\GAUGES\Bendix_King_Radio.DLL.nwwwbeawcrqeltukqnacthzcquotcotitwnbocto=2

C:\FSX\FsPassengers\bin\FsPassengersMini.DLL.rozrrlcqlackeaurzbhenukhziihkzikznhwrlwe=2

C:\FSX\fsdreamteam\couatl\couatl.exe.aiqkuaiqruatorlaniznhtabcheubnohozwihhcz=1

C:\FSX\bglmanx.dll.znncqinokqliquwacqoqtbbwkaekabutabirhkqh=1

C:\FSX\Modules\FSUIPC4.dll.bacnrhtoewrnlqituhkzztcnalkinwzcirwuwuuh=1

C:\GoFlight\GFDevFSX.exe.kwehiekcqhothanzbhcazcbhwbetuqlohiqqcork=1

C:\FSX\Modules\FSUIPC4.dll.telrawnqqiqeieqqhoqcuaebaaetiubawwkqucot=1

C:\FSX\fsdreamteam\couatl\couatl.exe.rabenwkqnrakuntqrnbnqeztoiwkbbzhchineaqw=1

C:\FSX\bglmanx.dll.uellencobbrzwirheuaqqhwaeokizinarnknizwb=1

C:\FSX\GAUGES\BoeingGeneric.DLL.khelcneezrhaozitruhqqqitlhuebewnthkknriq=2

C:\FSX\GAUGES\Magnetic_Compass.DLL.obblrqwzckkneeqwzwnoztuhorcoctzwclbzrnbi=2

[Question: FSUIPC and VR Insight and Vatsim]

Hi Christof

I am thinking of doing the same, using a touchscreen to operate the buttons on the FSINN client, rather than a mouse. Have you tried it yet and does it work? As soon as you know pls advise.

You can assign buttons/keys to FSINN but that only works if you use FSINN on your main FS pc. If, like me, you use FSINN on a networked client this assignment does not work and I don't think FSUIPC can help here either. That was why I think my only solution is the touchscreen. I was thinking of putting it on the lower EICAS in my 737 cockpit

Best

Charles

[Strange rudder problem]

I have now completed the 2nd test, which was a Vatsim flight in the Posky Thomsonfly 737-800 from the Posky site and totally flawless. The 1st test was a Vatsim flight in the Posky KLM 737-900 from the Posky site and totally flawless as well.

I have now freshly downloaded Thomson VA Bluesky (the pirep software) again and installed it and next test will be this with the a Vatsim flight in the Posky Thomsonfly 737-800 from the Posky site again (not from the T VA site). If this works I will not download the Posky Thomsonfly 737-800 from the Thomson VA site, but close this issue.

Btw, after I downloaded the Thomson VA Bluesky sw this time, it came up with a similar message as before that "Your version of Macromedia Flash ActiveX Control is not compatible with this version of windows". It then redirects me to Adobe for resolution and download of v 11.3.300.257 (I have W7 and had Flash v 10 installed). Before when I installed this (when I had the subsequent problems) I uninstalled V10 and installed this new version and I have a slight suspicion (but not 100%) that something unwanted may have entered at this point. But this time I simply downloaded and installed the new version and it seemed to replace V10 automatically.

I'll let you know how the test goes.

[Strange rudder problem]

OK, thanks, I'll update after the next test. The other odd thing re the above (reading it again) is that things went wrong at time of landing...up until then the flight was flawless, I could taxi on departure and take-off was ok....ie something kicked in on the arrival phase which is what is weird. If I had double assignments, etc you would expect the problem to occur from the start.

[Strange rudder problem]

I just completed a Vatsim flight with my PC restored to before installing the Thomson VA B737 and their Bluesky software, as before there were no issues at all (ie using my Posky KLM B737)

I have updated to FSUIPC 4,839 now.

My next test will be to do a flight with my KLM 737 and the Thomson Bluesky software.

Which numbers on the calibration page are you talking about "IN" or "OUT"? If IN they will be identical to the axis tab readouts UNLESS one of these things is true:

1. There are multiple assignments to the item being calibrated - i.e. rudder in this case,

2. The Axes assignments themselfs have multiplers or other scaling actions defined in the INI file

3. The rudder is not assigned "direct to calibration" and something else is intercepting the FS rudder controls before FSUIPC sees them.

Sorry, was unclear. I am talking about IN and OUT, when I pressed on the left pedal both would go positive in the Axis Assignment page, when I pressed on the right pedal both would go negative. But when I did the same in the Joystick Calibration page immediately after, press left would go positive and then jump to negative and press right would be negative (on both IN and OUT). I checked at the time that the rudder was assigned to direct to FSUIPC.

The rescan will simply pick up whatever axis is changing, which may or may not be the same one. Without knowing more I couldn't answer the "clear" question. If the axis was jittering al the time you might never get in.

Normally I would press "rescan" or clear and then the values next to "Press" would blank out, but in this case neither would do anything. The rudder values were extremely jittery because I tried pressing filter to see if it would calm down but there was little effect.

The "Max" field? That's set from the parameters in the INI file, once when you enter the tab (or again if you click "reload"), and then only changed if you press the "Set" button just above. There's absolutely no code to change it on its own, it has to be by user action. It sounds like something is actually infiltrating the Windows dialogue in order to do such a thing. It can be done by hooking and subclassing standard controls, but it seems to be a weird thing for somenoe to do -- unless it's virus code

I mean the Max Set field in the Joystick calibration page for the Aileron. When I moved the pedal on one of the tests only that field changed which is when I started to think of virus.

I would need a lot more information anyway -- like how things are assigned, what the calibrations look like 9eg your INI file would help).

I have FS axis controls completely disabled and all my axis movements assigned through FSUIPC direct. I did all axes assignments like this, simple MIN and MAX with dead zone in the middle for some (aileron, rudder and elevator) and detentes for flaps and spoilers, nothing more complex.

Attached is my ini file although this is after restoring my PC back...and as mentioned above it is working fine. If I get the same problem on one of the future tests I will send you the ini before restoring

[General]

UpdatedByVersion=4839

History=W6S1U6R0PZK9037A1QJ4S

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=Yes

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=Yes

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

DeleteVehiclesForAES=Yes

EnableMouseLook=No

AxesWrongRange=No

InitDelay=0

MouseWheelMove=No

AutoScanDevices=Yes

OOMcheck=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

1=PFC USB Pedals 2

1.GUID={6CE4EAD0-6492-11E1-8002-444553540000}

2=GoFlight GF-TQ6 Throttle System

2.GUID={6CE67170-6492-11E1-800E-444553540000}

0=PFC USB Yoke

0.GUID={6CE4EAD0-6492-11E1-8001-444553540000}

[buttons]

ButtonRepeat=20,10

4=P101,14,C2999,36

5=P101,15,C2999,37

6=P109,15,K53,9

7=R0,0,C65588,0

9=P0,6,K83,8

10=P109,0,K65,8

14=P167,0,C66079,0

15=P167,1,C66080,0

16=P167,3,C65752,0

17=P167,2,C65752,0

18=P109,7,C66531,0

19=P174,8,C1007,0

20=P174,9,C1007,1

21=P174,10,C1007,4

22=P174,11,C1007,5

25=R101,0,C65671,0

26=R101,1,C65672,31

33=P175,0,K66,8

39=R169,2,K113,8

40=U169,2,K112,8

41=R0,2,C65615,0

42=R0,3,C65607,0

43=U167,3,C65752,0

44=U167,2,C65752,0

45=R101,6,C65734,0

46=R101,7,C65735,0

47=P101,8,C2999,30

48=P101,9,C2999,31

49=P101,10,C2999,32

50=P101,11,C2999,33

51=P101,12,C2999,34

52=P101,13,C2999,35

53=P174,0,C2999,38

54=P174,1,C2999,39

55=P109,8,K13,24

56=U109,8,K13,24

59=P0,7,C66654,0

60=R0,1,C1001,0

61=P109,14,C2999,60

66=U109,0,K65,8

68=U109,14,C2999,61

69=U109,15,K53,9

70=P109,3,Cx0900561A,x01

71=U109,3,Cx0500561A,x01

72=P109,4,Cx0900561A,x02

73=U109,4,Cx0500561A,x02

74=P109,13,K51,9

75=U109,13,K51,9

76=U0,1,C1002,0

78=P101,3,C1120,0

79=P101,4,C1122,0

80=P141,1,C1119,0

81=P141,2,C1120,0

82=P141,0,C1122,0

83=P142,1,C66463,0

84=P142,2,C66464,0

85=P141,17,C66447,0

86=P141,18,C66451,0

[AutoSave]

AutoSaveEnabled=No

Next=1

Interval=60

Files=10

SaveOnGround=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[sounds]

Path=C:\FSX\Sound\

Device1=Primary Sound Driver

Device2=Speakers (Realtek High Definition Audio)

Device3=Realtek Digital Output (Realtek High Definition Audio)

Device4=Realtek Digital Output(Optical) (Realtek High Definition Audio)

[ClientNames]

1=PHILIPSPC

2=CHARLES-1

3=CHARLES-2

[Window.Radar Contact]

Docked=1536, 75776, 28672, 77824

[Axes]

0=0X,256,D,1,0,0,0

1=0Y,256,D,2,0,0,0

2=1R,256,D,3,0,0,0

3=2X,256,D,22,0,0,0

4=2Z,256,D,9,0,0,0

5=2R,256,D,23,0,0,0

6=2U,256,D,10,0,0,0

[JoystickCalibration.Project Opensky Continental Boeing 737-900]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=Yes

FlapStarts=-16384,-11392,-10368,-9472,-6528,-2176,3381,8192,11703

FlapEnds=-11520,-10624,-10112,-8448,-3584,1170,6891,10662,16384

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-15898,-1666,1946,15630

Elevator=-15453,-6950,-3072,15490

Rudder=-15439,-5998,553,14834

Throttle1=-11963,-512,512,9472/32

Throttle2=-11572,-512,512,10240/32

Spoilers=-11264,-9984,-6016,11312/16

Flaps=0,16380/16

[JoystickCalibration.POSKY KLM NC B737-900]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=Yes

FlapStarts=-16384,-10880,-10368,-9472,-7040,-1920,3771,8192,11963

FlapEnds=-11520,-10624,-9984,-8064,-3456,2080,6631,10922,16384

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-16036,-3263,2825,15567

Elevator=-15422,-5802,-1303,14417

Rudder=-15106,-3332,1993,15830

Throttle1=-11963,-512,512,10112/32

Throttle2=-11703,-512,512,10112/32

Spoilers=-11648,-8960,-6144,11572/16

Flaps=0,16380/16

[Profile.Project Opensky Continental Boeing 737-900]

1=Project Opensky Continental Boeing 737-900

[Profile.POSKY KLM NC B737-900]

1=POSKY KLM NC B737-900

[Axes.POSKY KLM NC B737-900]

0=0X,256,D,1,0,0,0

1=0Y,256,D,2,0,0,0

2=1R,256,D,3,0,0,0

3=2X,256,D,22,0,0,0

4=2Z,256,D,9,0,0,0

5=2R,256,D,23,0,0,0

6=2U,256,D,10,0,0,0

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=Yes

FlapStarts=-16384,-11264,-10368,-9344,-7040,-2048,3381,8062,11442

FlapEnds=-11392,-10624,-9728,-7936,-3840,1820,6761,10922,16384

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-15889,-2119,4204,15642

Elevator=-15505,-4183,-316,14974

Rudder=-15717,-5387,6587,15110

Throttle1=-11963,-512,512,9600/32

Throttle2=-11703,-512,512,10240/32

Spoilers=-11264,-9088,-5632,11312/16

Flaps=0,16380/16

[Strange rudder problem]

Hi Pete

I fly at least once a day on Vatsim and have had a very stable-running setup for the last 4 months flying the Posky 737-900 KLM on FSX with Project Magenta and FSUIPC 4.80 in a home-built cockpit. No crashes, no issues.

I recently thought of moving to the next stage which was logically to a virtual airline, my prime concern being that I would have to use a new aircraft of the VA's fleet and the consequent risk to the stability I had worked hard to get to.

I made the plunge and recently joined Thomson VA and was pleased with how everything was going and saw that there was a Posky 737-8K5 available as part of the fleet which I downloaded (apparently just the Thomson 737-800 from the Posky site with textural chnages). I also downloaded Blue Sky which is their Pirep software, which apparently has no input to my flight sim other than send a message to my screen, they use the bridge fsuipc to communicate between blue sky and FSX. I then did a test flight of everything and all was absolutely fine until on final approach I made a poor landing and ran off to one side of the runway and could not get back (fortunately not very usual!). I discovered that my rudder was not working properly (it had worked fine on taxxing to the dep runway), so much so that I could not taxi to gate, it was all over the place (I have used flypfc pedals for some years now with no problem). I thought maybe the pedals themselves were not working, but I did a test in the windows device settings and it was fine, I even recalibrated them to be sure.

Looking into this further, I found out that within FSUIPC´s axis assignment all was well, so that when I pressed the left pedal the numbers increased and when I pressed the right they decreased and went negative. But when I went into the Joystick assignment and pressed the left pedal sometimes the numbers would go negative rather than positive and when I pressed the right pedal they would be negative again! (this is not the “reverse” button because that was off). Then I went back into axis assignment and selected to “rescan” or “clear” and nothing would happen (the assignment would not clear), I had to exit FSUIPC and go in again. Then in the axis assignment page the numbers move absolutely fine still, ie positive (when push left) and negative (when push right). I noticed too that on one of my tests, when I moved the pedals on the FSUIPC joystick calibration page the values for the Aileron Max field were changing! Then again I could not clear/rescan on the axis assignment page and had to close and re-enter FSUIPC. I put my pedals in a different USB slot but no change. These tests were occurring without Bluesky running.

I double-checked that I have no other conflicting assignments (eg within FSX) but these were all as I had before with my KLM, ie all deactivated.

I have never experienced any problem with FSUIPC before and I have used it for the last 3 years extensively. So luckily I made a restore point before all this, I loaded up my old KLM and the Thomson 737 from the Posky site (not the Thomson site) and sure enough the pedals are absolutely fine, although this may mean nothing as they were fine when I departed with the Thomson site's Posky 737.

I have raised this with Thomson VA and we agreed I´ll try flying my KLM without Bluesky, then I´ll try my KLM with Bluesky, then (the Posky Thomson Fly 737 from the Posky site with and without Bluesky and then © the Posky Thomson Fly 737 from the Thomson site with and without Bluesky. Hopefully that may give more information for us! In the meantime, can you shed any light on possible causes? I thought of static but never had this before and would be very coincidental for this to occur when I change aircraft and load Bluesky.

[Goflight radios (GF-166) and ATC not lighting up]

Thanks for the input, I have found the culprit, my GF modules were plugged into USB 3 rather than USB 2 slots, I plugged them back into the USB 2 and now all fine. I am not sure if this is a GF v USB 3 problem or the other issue may be that USB 3 goes to sleep as GF suggested in their response (copied below), I have put this back to John Krieg at GF. Sorry to use up space on a non-FSUIPC issue:

"Disable power management on the USB

To preserve power, Microsoft Window's tries to disable USB when a device is not used.

Under certain circumstances this function does not work and may cause USB devices to fail

to respond when called. To resolve this issue, disable power management.

a..Open your Control panel.

b..Click on Change Power plan.

c..Click on Change Advanced Power setting.

d..Now in Advanced setting's expand the USB.

e..Under USB Selective Suspend Settings.

f..Set to Disable Apply and exit."

[Goflight radios (GF-166) and ATC not lighting up]

Hi Pete

I have had the GF airliner module for about 2 yrs now and not had any problem. Recently I have upgraded to W7 and from FSX Deluxe to Gold. I check in the Goflight Software and all my modules are showing, I then launch GFDEV.fsx and then fsx (Gold with Acceleration). When FSX is loading all the modules light up and then go out as per normal. But then when FSX is loaded, engines running and battery/avionics on, there is no display on the radios nor on the ATC module. If I turn the radio knobs they do not change the radios in FSX. However the movement of their knobs does show up in FSUIPC.

I uninstalled and reinstalled the latest version of GF (203) and I upgraded FSUIPC to the latest (4,80) but still no joy.

I did the same procedure, but deleting GFDEV.dll in the modules folder first, but still no joy.

I have raised this with GF too, but knowing that you use GF and I saw you commented on similar problems in the past (but I could not see a resolution), I thought I would ask you too

Best

Charles

[Assigning a button to a client PC keypress]

Understood, many thanks Pete

[Assigning a button to a client PC keypress]

Hi Pete

I am trying to assign a button to a keypress on one of my clients (it is CTRL+O on the client which shows the frame rates within the PM Glass Coclpit). Within the button section of FSUIPC the button press shows up, I thought if I then selected "keypress" and hit CTRL+O on the client PC, this would show up but it doesn't. I checked the wideclient.ini and it has buttonScanInterval on, see below:

[Config]

Port=8002

Window=-32000,-32000,160,34

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

[sounds]

Path=C:\WideClient\Sound\

Device1=Driver de som primário

Device2=Realtek HD Audio output

Hardware/Software spec:

Server spec

CPU Intel E8600

Motherboard XFX 790i Ultra

Graphics BFG GTX 280 OC

Memory 4GB DDR3 1600

HD 300GB Velociraptor

O/S Vista Basic 64 bit

I have the 3GB switch enabled

Server contents

· FSX + SP1 + SP2 – settings are around medium (water is 1x and very low cars/ships/airport vehicles) and frame rates set at unlimited (I get frames rates of 40+ although at a very detailed airport (eg Heathrow) down to 20)

· FSUIPC 4.703 and WideFS 6.8.6

· Project Magenta MCP 490B and PMsounds

· Goflight Software 2.03 (to work the buttons and switches on the Goflight hardware below incl Goflight MCPPro)

· Weather – Active Sky Evolution SP2

· ATC - Radar Contact 4

· Scenery - Ground Env Xtreme and Ultimate Terrain X and FSGenesis World Terrain Mesh

· Traffic X

· Airplane – Project Opensky Continental 737-900

Control hardware connected to Server

· Goflight MCPPro, throttle quadrant and Airliner system

· PFC yoke and pedals

Client 1

Project Magenta Glass Cockpit (PFD) 490A

Client 2

Project Magenta Glass Cockpit (EICAS) 490A

Client 3

Project Magenta CDU 490 – connected to flyengravity CDU hardware

Client 4

Project Magenta PMSystems 182

3 DOF platform software (Motionforsimulators FAST program)