FSUIPC 44.53 Problem

[saabpilot]

Hi Pete,

Need help.

When assigning control sequences to my CH USB Brakes for TSR Autobrake (offset and parameters) FSUIPC do not write those to FSUIPC.ini :(

This happened with previous FSUIPC version too as well as the latest one 44.53

I can see FSUIPC reports all joysticks OK.

When I run RESCAN and press e.g. left pedal I get the IN/OUT values OK too.

Then I tick the "Control Sent" and enter "Offset byte Setbits" and its offset and parameter.

Continues with Control to Repeat and "Control Sent" plus "Offset Byte Clrbits" + its offset and Parameter.

Finally I press OK and FSUIPC seems to save the settings.

But when looking in the ini file no setting is there and it does not show again after a restart of FS and "Reload all Assignments"

I have in vain tried this for ½ day :(

Do you have any hint what could be wrong?

Best,

Bjorn

[Pete Dowson]

When assigning control sequences to my CH USB Brakes for TSR Autobrake (offset and parameters) FSUIPC do not write those to FSUIPC.ini :(

This happened with previous FSUIPC version too as well as the latest one 44.53

Version 44 already? ;-). No, you mean 4.53.

I can see FSUIPC reports all joysticks OK.

Not sure what that means. FSUIPC doesn't issue reports.

When I run RESCAN and press e.g. left pedal I get the IN/OUT values OK too.

Then I tick the "Control Sent" and enter "Offset byte Setbits" and its offset and parameter.

Erare you talking about the range setting, on the right-hand side? For getting specific controls sent when the axis passes through any of up to 10 ranges, in either direction? Why are you wanting to do that? That can be useful for some very specialised purposes, but i cannot think of anything useful for it with brakes!

What range did you set? How many ranges? Up or down? What bits are you trying to set to what offset? Are you merely discarding the brake value altogether -- you aren't using proportional braking, but specific bits in specific offset at specific points on the axis?

Can you show me the [Axes] section of the INI file. that might help me understand what you are trying to do.

Continues with Control to Repeat and "Control Sent" plus "Offset Byte Clrbits" + its offset and Parameter.

Finally I press OK and FSUIPC seems to save the settings.

You checked the [Axes] sections of the INI file? Why not show me them, then?

I have in vain tried this for ½ day :(

Do you have any hint what could be wrong?

I'm really puzzled as to what you are trying to do. Why have bits in an offset being set when an axis passes through a specific range?

Please, explain what you want to do or explain what it is you are trying to do. It sounds like you are misunderstanding something quite fundamental.

Regards

Pete

[saabpilot]

Hi again Pete,

A picture says more than a thousand words, so I have attached an extract from Thomas Richters manual for TSR Autobrake Pro.

This is an add-on fto PMsystems.

I am trying (in vain) to get FSUIPC to keep those settings neccessary for the A/B function.

Same applies for right brake but with x02 as parameter.

Best,

Bjorn

P.S. The download file name for my FSUIPC (from PM) says FSUIPC 44.53 :)

[Pete Dowson]

A picture says more than a thousand words, so I have attached an extract from Thomas Richters manual for TSR Autobrake Pro.

Strange. Looking at the range he wants you to set (-12223 to 16383), that is nearly the whole movement of your toe brakes. With those settings, nothing happens when you press the toe brakes except once when you push them slightly, and again once when you release them. Makes the use of pedals a bit of a waste of time, if you ask me. Two buttons would accomplish that, one for each brake! Won't you be using toe brakes normally, proportionally -- for example whilst taxiing?

Having the control repeat al the time, setting the same bit, wouldn't accomplish anything, unless of course the TSR Autobrake program is clearing that same bit when it sees it. But if this were the case, why bother with assigning the ClrBits control at all? As soon as you are out of the range again, the bit would be cleared by TSR in any case.

It's a mystery. Maybe Thomas can explain what he's attempting to do here?

I am trying (in vain) to get FSUIPC to keep those settings neccessary for the A/B function.

Same applies for right brake but with x02 as parameter.

You appear to have forgotten to include the information I asked for, the [Axes] section of the INI file?

The download file name for my FSUIPC (from PM) says FSUIPC 44.53 :)

No it doesn't. The filename is FSUIP4.ZIP. The label on the Schiratti website is "FSUIPC4 4.53", meaning "FSUIPC4 version 4.53". He's left the word "version" out, but he has left a space in!

You get the version number from the main front tab in FSUIPC options, or from the Log file, or by right clicking on the DLL and selecting Properties-Version.

Regards

Pete

[saabpilot]

The TSR autobrake program simulates correctly B737 autobrakes together with PMsystem.

Details in the programming is out of my knowledge but I can forward your comments to Thomas Richter who is the author.

The FSUIPC.ini does not have the "AXIS" subpart, I am enclosing a copy of my file here below.

As I told you, the settings does not stay nor become written to FSUIPC.ini

But - all other settings I make e.g. "buttons" writes OK.

[JoyNames]

AutoAssignLetters=No

0=CH Pro Pedals USB Rudder Pedals

1=CH 3-Axis 10-Button+POV USB Yoke

2=BU0836X Interface

[General]

History=MY6W6UFL6GW23ECN0YQA9

TCASid=Flight

TCASrange=40

TrafficScanPerFrame=10

AxisCalibration=No

CentredDialogue=Yes

ClearWeatherDynamics=Yes

OwnWeatherChanges=No

WeatherReadInterval=4

MoveBGLvariables=Yes

TimeForSelect=4

MainMenu=&Modules

SubMenu=&FSUIPC ...

WindSmoothing=Yes

AutoTaxiWind=No

PropTaxiWind=No

TimeSetMode=Partial

WhiteMessages=No

ThrottleSyncAll=No

GraduatedVisibility=Yes

LowerVisAltitude=0

UpperVisAltitude=25000

UpperVisibility=6000

GenerateCirrus=Force

WindShearSharp=No

UpperWindGusts=Yes

ExtendMetarMaxVis=Yes

DisconnTrimForAP=No

ZeroElevForAPAlt=No

AutoClearWeather=Yes

ExtendTopWind=Yes

WindSmoothness=5

SmoothPressure=Yes

PressureSmoothness=5

SmoothVisibility=Yes

VisibilitySmoothness=2

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

MinimumVisibility=0

MaximumVisibilityFewClouds=6000

MaximumVisibility=2000

MaximumVisibilityOvercast=2000

MaximumVisibilityRainy=1000

OneCloudLayer=No

ThinClouds=No

ThinThunderClouds=No

CloudThinness=1000

ThunderCloudThinness=10000

CloudTurbulence=Yes

CloudIcing=Yes

WindTurbulence=No

SuppressAllGusts=No

ExternalOptionControl=Yes

AutoTuneADF=No

KeepFS98CloudCover=No

ShowPMcontrols=Yes

MagicBattery=Yes

RudderSpikeRemoval=Yes

ElevatorSpikeRemoval=Yes

AileronSpikeRemoval=Yes

ReversedElevatorTrim=No

TrapUserInterrupt=Yes

NavFreq50KHz=Yes

ClockSync=No

SmoothIAS=Yes

SetVisUpperAlt=No

VisUpperAltLimit=6000

MaxIce=-4

WindSmoothingDelay=0

WindSmoothAirborneOnly=Yes

VisSmoothingDelay=0

VisSmoothAirborneOnly=Yes

SuppressCloudTurbulence=No

SuppressWindTurbulence=No

SpoilerIncrement=512

ShortAircraftNameOk=No

FixWindows=No

FixControlAccel=No

StopAutoFuel=No

MinIce=-4

LimitWindVariance=No

TrafficControlDirect=Yes

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

WeatherReadsFast=No

CorrectVSsign=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

AxisInterceptIfDirect=No

ZapSound=firework

UpdatedByVersion=3930

UseProfiles=No

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

Aileron=-16344,-4840,465,8099/8

SlopeAileron=6

Elevator=-16355,-6823,0,16267/8

SlopeElevator=-2

Rudder=-16383,-5591,-3083,16383/8

SlopeRudder=6

LeftBrake=-16380,16380/16

RightBrake=-16380,16380/16

[buttons]

ButtonRepeat=20,10

1=P1,7,C2040,0

2=P1,6,C1001,0

3=U1,6,C1002,0

4=R1,8,C65607,0

5=R1,9,C65615,0

6=P1,0,C1079,0

7=U1,0,C1013,0

8=P1,4,C65829,0

9=P1,5,C65567,0

10=P1,1,C66147,0

11=R1,32,C65735,0

12=R1,34,C65672,0

13=R1,38,C65671,0

14=R1,36,C65734,0

15=U1,1,C65875,0

16=P2,31,C1001,0

17=U2,31,C1002,0

18=P2,2,Cx010031F4,x00

19=P2,1,Cx010031F4,x02

20=P2,6,Cx010031F4,x03

21=P2,5,Cx010031F4,x01

22=P2,0,Cx0D006DB3,x08

23=P2,30,Cx05006DB3,x01

24=U2,30,Cx09006DB3,x01

25=P2,4,Cx05006DB3,x04

26=U2,4,Cx09006DB3,x04

28=P2,3,Cx05006DB3,x02

29=U2,3,Cx09006DB3,x02

[Pete Dowson]

The TSR autobrake program simulates correctly B737 autobrakes together with PMsystem.

Yes, I know -- it is part of the 737 package Thomas makes too. I have used parts of this, but never disabled my proportional manual braking in favour of only autobraking. That doesn't seem right to me, somehow. Are you sure you shouldn't assign the brakes AS WELL as those additional controls?

The FSUIPC.ini does not have the "AXIS" subpart

It isn't "Axis" but Axes.

I see you are calibrating your toe brakes in FSUIPC:

LeftBrake=-16380,16380/16

RightBrake=-16380,16380/16

though not correctly, as those look like default values. You should always leave a null area at each end.

If you aren't assigning toe brakes, how are you calibrating them? Are your axes assigned in FS, not it FSUIPC then?

Can you actually try assigning a real axis in the Axes assignments tab, please? It looks like there's something missing in what you are doing. Is the ONLY thing you are using the Axis assignments tab for this weird Setbits/Clrbits action? I'll try just that here. It may be that with no axes actually assigned as axes, the [Axes] section is not written -- it probably counts as being empty.

You are likely the first person ever to try such a thing. The right-hand side assignments you are using are really an "addendum", a useful extra, to the main job of efficiently assigning all of your axes for direct use via FSUIPC, bypasssing all the problems of FS.

Regards

Pete

[saabpilot]

Answer is, I dont know - never needed to calibrate my CH pedals :)

However you have a good idea so I will try to assign the brakes in FSUIPC and that might fix the problem.

I let you know tomorrow.

Why use TSR autobrakes? - Simply because they give you "runway condition" prone brakes - e.g. they simulate wet/snowy/dry runways and they simulate the B737 brake accu correctly.

I will buy you a beer at Lelystad if the tip worked :D

Best

Bjorn

www.boeing737sim.se

[Pete Dowson]

Answer is, I dont know - never needed to calibrate my CH pedals :)

But you have clicked the "Set" entry for the brakes in FSUIPC's Joystick Calibration, which is the first step in calibrating. If you didn't mean to you should go there and press the button again -- it will be labelled "Reset" now.

In fact, though you say you never had to calibrate the pedals, it seems you've done all three -- elevator, aileron and rudder, in FSUIPC:

Aileron=-16344,-4840,465,8099/8

SlopeAileron=6

Elevator=-16355,-6823,0,16267/8

SlopeElevator=-2

Rudder=-16383,-5591,-3083,16383/8

SlopeRudder=6

For these you have definitely calibrated, as the values are certainly not defaults, and you've even used the slopes on them for varied response.

Why use TSR autobrakes? - Simply because they give you "runway condition" prone brakes - e.g. they simulate wet/snowy/dry runways and they simulate the B737 brake accu correctly.

I know that -- I think I tried them here, long ago, as part of the TSR complete 737 package, but I don't remember having to mess with offsets on the toe brakes. I had trouble with the TSR package messing with my fuel quantities during pre-flight, and the 6-pack indicators, so I don't use it at present.

I will buy you a beer at Lelystad if the tip worked :D

Thanks -- but if it works then it would appear to be an unintentional mistake on my part in any case, so maybe it is I who owes you a beer! ;-)

Regards

Pete

[Pete Dowson]

I will buy you a beer at Lelystad if the tip worked :D

Okay. I've tested it and fixed it this morning.

My "tip" will work. If the axis is assigned as well as having range actions set for it, the data is saved correctly. But I owe you the beer, not vice versa, as it is a definite bug.

I will provide the fix in versions 3.932 and 4.532, in the "Updates" announcement above very soon, within an hour.

Thanks for the good feedback, &

Best Regards

Pete

[saabpilot]

After assigning the Rudder and Brake axes in FSUIPC I got one of the two brakes (Axes) written OK into FSUIPC.ini

The remaining (0Y) only writes = "0=0Y, 256" in the ini file. :(

Then I manually changed the ini file on basis of the X axes values (but with different value = x02)

This seems to "stick" in FSUIPC.ini so now I have this:

......

Rudder=-16345,-560,219,16267/8

SlopeRudder=-6

LeftBrake=1497,13619/8

RightBrake=357,13044/8

......

[Axes]

0=0Y,BR,-15183,-1130,x05006DB0,x02,x09006DB0,x02

1=0X,BR,-15183,-1130,x05006DB0,x01,x09006DB0,x01

I will watch the ini file closely when I make other settings to see if it changes the "Axes" values and will let you know if this happens.

Any case, it seems like a small bug somewhere in the axes setting preventing the settings partially from being written into Fsuipc.ini

Bjorn

[Pete Dowson]

After assigning the Rudder and Brake axes in FSUIPC I got one of the two brakes (Axes) written OK into FSUIPC.ini

The treatment of each axis is independent and the code path exactly the same, so I really don't understand how it could be different. I've tested everythnig here, and fixed the original bug. Without knowing exactly what you did there I can't really comment further.

I will watch the ini file closely when I make other settings to see if it changes the "Axes" values and will let you know if this happens.

Any case, it seems like a small bug somewhere in the axes setting preventing the settings partially from being written into Fsuipc.ini

The only one I found is the one now fixed if you download the update, which is there now.

Regards

Pete

[saabpilot]

The new version might have fixed that problem. :D

I did not note that you had changed the dll but will install it a.s.a.p.

Thanks a lot for the fast respond.

Best,

Bjorn