Parking brake also operates flaps

[gaftp]

FSUIPC 4.9.28, WIN7 64bit

 

After programming Buttons & Switches to operate the parking brake I've found it also simultaneously operates flaps (either up or down). I've tried selecting "parking brakes" or keypress - "ctrl+." but the unselected flaps movement occurs with either instruction.

 

This appears to be within fsuipc because fsx keypress ctrl+. works normally from the keyboard. It's present in two default aircraft I've tried with fsuipc.

Fredpop 

 

[Pete Dowson]

FSUIPC 4.9.28, WIN7 64bit

 

You are out of date. I only support the current version - 4.929 or later.

 

 

After programming Buttons & Switches to operate the parking brake I've found it also simultaneously operates flaps (either up or down). I've tried selecting "parking brakes" or keypress - "ctrl+." but the unselected flaps movement occurs with either instruction.

This appears to be within fsuipc because fsx keypress ctrl+. works normally from the keyboard. It's present in two default aircraft I've tried with fsuipc.

 

There's absolutely no way FSUIPC will do anything you don't ask it to do. It simply sends whatever you tell it to do. Very simple. You must have some additional assignments, in FSUIPC or in FS which you've forgotten about.

 

If it is all too confusing for you, show me your FSUIPC4.INI file, and also try enabling Button logging and Event logging in FSUIPC's logging tab, and show me the Log file too. You can paste the text into a message here.

 

Pete

[gaftp]

Hello Pete

I'm running 4.929 now.

Here're the INI and Button & Event log files. I just ran FSX a very short time to select and deselect Parking Brakes.  
 

[General]

UpdatedByVersion=4929

History=RH8WACPNLX4GQIXXATM7R

InitDelayDevicesToo=No

NewInterceptTextMenu=No

UseSystemTime=No

UseMidMouseBtn=Yes

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

AutoScanDevices=Yes

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=No

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=Substring

UseProfiles=Yes

EnableMouseLook=No

DelayedMouseLookZoom=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

OOMcheck=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

 

[JoyNames]

AutoAssignLetters=No

0=Button Box Interface

0.GUID={EC941400-8BD1-11E3-8003-444553540000}

1=CH THROTTLE QUADRANT

1.GUID={EC4EA690-8BD1-11E3-8002-444553540000}

2=CH PRO PEDALS USB

2.GUID={EC193EB0-8BD1-11E3-8001-444553540000}

3=CH FLIGHT SIM YOKE USB

3.GUID={746E5E30-8BD2-11E3-8001-444553540000}

 

[buttons]

ButtonRepeat=20,10

1=P0,8,C66241,0

2=U0,8,C66241,0

3=P1,5,C65752,0

5=P1,4,C65752,0

6=P1,6,C65759,0

7=P1,7,C65758,0

8=R1,11,C65607,0

9=R1,10,C65615,0

 

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

 

[GPSout]

GPSoutEnabled=No

 

[GPSout2]

GPSoutEnabled=No

 

[WideServer]

WideFSenabled=Yes

 

[sounds]

Path=H:\FSX\Sound\

Device1=Primary Sound Driver

Device2=Speakers (Realtek High Definition Audio)

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

Device4=Realtek Digital Output (Realtek High Definition Audio)

********* FSUIPC4, Version 4.929 by Pete Dowson *********

Reading options from "H:\FSX\Modules\FSUIPC4.ini"

Running inside FSX on Windows 7

Module base=6E900000

User Name="FTP"

User Addr="@gmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

      515 System time = 02/02/2014 19:25:04

      515 FLT path = "C:\Users\thomas\Documents\Flight Simulator X Files\"

      531 Trying to connect to SimConnect Acc/SP2 Oct07 ...

      531 FS path = "H:\FSX\"

      656 LogOptions=00000000 00000001

      656 SIM1 Frictions access gained

      656 Wind smoothing fix is fully installed

      656 G3D.DLL fix attempt installed ok

      656 SimConnect_Open succeeded: waiting to check version okay

      656 Trying to use SimConnect Acc/SP2 Oct07

     1607 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

     1607 Initialising SimConnect data requests now

     1607 FSUIPC Menu entry added

     1638 C:\Users\thomas\Documents\Flight Simulator X Files\Welshpool.FLT

     1638 H:\FSX\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.AIR

   276465 Aircraft="Beech Baron 58 Paint1"

   276481 System time = 02/02/2014 19:03:34, Simulator time = 19:06:01 (18:06Z)

   281099 Starting everything now ...

   281099 Using "E:\GoFlight\GFDEV.DLL", version 2.2.2.0

   282393 Advanced Weather Interface Enabled

   303703 LogOptions changed, now 60000000 00000001

   307510 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR

   307556 Button changed: bRef=0, Joy=1, Btn=5, Pressed

   307556 [buttons] 3=P1,5,C65752,0

   307556 FS Control Sent: Ctrl=65752, Param=0

   307556 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES

   308149 Button changed: bRef=0, Joy=1, Btn=5, Released

   311519 Button changed: bRef=0, Joy=1, Btn=4, Pressed

   311519 [buttons] 5=P1,4,C65752,0

   311519 FS Control Sent: Ctrl=65752, Param=0

   311519 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES

   311519 *** EVENT: Cntrl= 65759 (0x000100df), Param= 0 (0x00000000) FLAPS_DECR

   311940 Button changed: bRef=0, Joy=1, Btn=4, Released

   323734 LogOptions changed, now 00000000 00000001

   329506 System time = 02/02/2014 19:04:27, Simulator time = 19:06:25 (18:06Z)

   329506 *** FSUIPC log file being closed

Average frame rate for running time of 25 secs = 22.3 fps

G3D fix: Passes 5163, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 13 Allocs, 13 Freed

********* FSUIPC Log file closed ***********

Thanks
fredpop

[gaftp]

Hello Pete

Do you think the log file indicates the flaps key operates when the adjacent brakes key is pressed? In the past I've opened TQ and this may be the cause....

[Pete Dowson]

Well, you have no Keys assigned in FSUIPC, so I don't understand your earlier reference to assignment of Ctrl+. in FSUIPC. Your button assignments are pretty simple:

[buttons]

ButtonRepeat=20,10

1=P0,8,C66241,0 master battery

2=U0,8,C66241,0 master battery

3=P1,5,C65752,0 parking brakes

5=P1,4,C65752,0 parking brakes

6=P1,6,C65759,0 flaps decr 

7=P1,7,C65758,0 flaps incr

8=R1,11,C65607,0 elev trim down

9=R1,10,C65615,0 elev trim up

 

In this sequence:from the log:

 

   307510 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR

   307556 Button changed: bRef=0, Joy=1, Btn=5, Pressed

   307556 [buttons] 3=P1,5,C65752,0

   307556 FS Control Sent: Ctrl=65752, Param=0

   307556 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES

   308149 Button changed: bRef=0, Joy=1, Btn=5, Released

  

that first FLAPS INCR command has occurred with no button pressed at all -- at least in the 4 seconds since you enabled the button and event logging, so I don't know where that comes from.

 

But when you pressed button 4, here:

 

   311519 Button changed: bRef=0, Joy=1, Btn=4, Pressed

   311519 [buttons] 5=P1,4,C65752,0

   311519 FS Control Sent: Ctrl=65752, Param=0

   311519 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES

   311519 *** EVENT: Cntrl= 65759 (0x000100df), Param= 0 (0x00000000) FLAPS_DECR

   311940 Button changed: bRef=0, Joy=1, Btn=4, Released

 

although FSUIPC only sent the one control, the FLAPS DECR control is sent as well. Not by FSUIPC -- so I believe that button is also assigned in FSX.

 

I notice you have no axes assigned in FSUIPC, even though you are using a yoke, pedals and a throttle quadrant. So either those are assigned in FS or being sent by some other control program. That is where you will find your duplicate assignments.

 

Pete

[gaftp]

Hello Pete

Before I opened up TQ I disconnected the yoke, pedals and buttons and found the problem was still present in TQ, the only USB connected.

With TQ opened up I could find no obvious reason why I was getting a spurious response from the allocated brake button. Perhaps there's a 'spike'.

I've now cleared the 'up' and 'down' actions and allocated them to a different button. Both 'flaps' and 'brake' now work normally. Both functions will be handled by dedicated hardware, when I get round to it, and will free the keys for when a need arises.

 

My earlier reference to ctr+. keypress was about when I was unsuccessfully trying to identify the problem when I had an earlier fsuipc version installed.

 

Thank you for your help. The logs pointed to the source.

fredpop

  

[Pete Dowson]

With TQ opened up I could find no obvious reason why I was getting a spurious response from the allocated brake button. Perhaps there's a 'spike'.  

 

But the log from FSUIPC shows no other "spurious" button press at all. If it isn't seeing one it won't be sending the additional control. That additional control is certainly being sent by something else, most likely FS itself, through assignments there.

 

 

I've now cleared the 'up' and 'down' actions and allocated them to a different button. Both 'flaps' and 'brake' now work normally. Both functions will be handled by dedicated hardware, when I get round to it, and will free the keys for when a need arises.

My earlier reference to ctr+. keypress was about when I was unsuccessfully trying to identify the problem when I had an earlier fsuipc version installed.

Thank you for your help. The logs pointed to the source.

 

I really don't see how. The log showed only the correct button being seen by FSUIPC, yet two controls being issued. Therefore the other was from a different source.

 

When you fail to disable controllers in FS, as I assume you have (else why no axis assignments in FSUIPC?), FS will sometimes make automatic assignments to those buttons it knows are available on the devices according to its list of device types. This is why you have to be very careful. Generally it is best to either do all assignments in FS and none in FSUIPC, or vice versa.

 

Pete

[gaftp]

Hi Pete

I've established a particular key also triggers an adjacent with a particular USB unit. When that key is cleared and the operation is transferred to a different key there is no problem.

Please consider this. My 'spike' is very brief but long enough to trigger the instruction but too short to allow fsuipc to identify and name the key!

Standing by for hollow laughter!

fredpop

  

[Pete Dowson]

Please consider this. My 'spike' is very brief but long enough to trigger the instruction but too short to allow fsuipc to identify and name the key!

 

But if it doesn't see it, it wouldn't act upon it and send another control. It would simply be the same as if it didn't occur.

 

That logging of the buttons being pressed and released is in-line with the code which acts upon those events. If the logging is enabled, you can't get one without the other.

 

Pete

[gaftp]

Hi Pete
I now use standard toggle switches instead of TQ switches which was only a temporary arrangement. These are mounted on my instrument panel and work well with fsuipc/FS assignments. My engine controls are two break before make rotaries switching five magneto contacts each. One worked perfectly but the other gave trouble quite like that TQ button, namely the intended assignment with a related second one, in this case "start both engines".

I replaced the offending switch. The new switch works normally with fsuipc. Without an oscilloscope I can't prove it but my opinion is contact bounce causes these glitches.

 

I'm not criticizing fsuipc, merely making this observation. Your work is so useful to the home developer.  

Fred