Brake Problem, will not disengage

[bradrcfii]

I am a lttile embarrased I have not been able to solve this as I thought my FSUIPC skills have evolved futher than my current problem. My brakes will not disengage after applying the brakes and then releasing. Additionally, the parking brake will not disengage when pushing the brakes to their full limit.

I need to use Control "." to release the parking brake.

I am using FSUIPC for calibration. The rudders are fine. I have checked the brake reverse boxes in the calibration screen.

What did I miss?

[Pete Dowson]

My brakes will not disengage after applying the brakes and then releasing.

You have not calibrated them correctly then. When setting the "minimum" (off) point you should have the pedals depressed somewhat, so you can be sure they always go back passed that point when released. You should do this in any case to avoid accidental pressing of brakes when using the rudders.

Additionally, the parking brake will not disengage when pushing the brakes to their full limit. I need to use Control "." to release the parking brake.

Check the BrakeReleaseThreshold parameter in your INI file (read its description in the Advanced users guide). By default that releases Parking Brake when both toe brakes are over 75% pressure. So, it sounds as if you've not calibrated theat end of the brake travel very well either. Set the maximum calibration point well before the end of the brake travel.

Regards

Pete

[bradrcfii]

Thanks Pete. I discovered my pedals had worn and were not sending correct values. I have since purchased and installed Saitek Pedals.

Now, when I press on one brake, it turns the aileraons and the other the elevators while also contrrolling the respective brakes. Not sure why?

From my fsuipc.ini file.

[JoyNames]

AutoAssignLetters=Yes

T=CH THROTTLE QUADRANT

T.GUID={598567D0-FA35-11DF-8004-444553540000}

A=Saitek Pro Flight Yoke

A.GUID={598567D0-FA35-11DF-8005-444553540000}

1=CH THROTTLE QUADRANT

1.GUID={598567D0-FA35-11DF-8004-444553540000}

B=Saitek Pro Flight Rudder Pedals

B.GUID={C7D70A70-EF3C-11E0-8001-444553540000}

0=Saitek Pro Flight Yoke

0.GUID={598567D0-FA35-11DF-8005-444553540000}

2=Saitek Pro Flight Rudder Pedals

2.GUID={C7D70A70-EF3C-11E0-8001-444553540000}

R=<< MISSING JOYSTICK >>

Y=<< MISSING JOYSTICK >>

[Pete Dowson]

Now, when I press on one brake, it turns the aileraons and the other the elevators while also contrrolling the respective brakes. Not sure why?

Because FS is automatically assigning them, thinking it's a yoke.

You should never have the same things assigned in both FS and in FSUIPC. If you are assigning everything in FSUIPC, disable the controllers in FS.

Pete

[bradrcfii]

I was running a hybrid configuration where only the yoke was calibrated by FSX. I did this based on Simsamari's recomendation due to the hat switch. I use ezdok now so I moved everything over to FSUIPC. Yoke works better than ever now.

Concerning my .ini file, why are their duplicate numbered and lettered joy lines and why the missing Joy lines(in previous post this thread). If I delete them, the like to re-appear.

Thanks,

[Pete Dowson]

Concerning my .ini file, why are their duplicate numbered and lettered joy lines and why the missing Joy lines(in previous post this thread). If I delete them, the like to re-appear.

Look again. I sorted the lines so that the entries are next to each other, to make it more obvious:

T=CH THROTTLE QUADRANT

T.GUID={598567D0-FA35-11DF-8004-444553540000}

1=CH THROTTLE QUADRANT

1.GUID={598567D0-FA35-11DF-8004-444553540000}

A=Saitek Pro Flight Yoke

A.GUID={598567D0-FA35-11DF-8005-444553540000}

0=Saitek Pro Flight Yoke

0.GUID={598567D0-FA35-11DF-8005-444553540000}

B=Saitek Pro Flight Rudder Pedals

B.GUID={C7D70A70-EF3C-11E0-8001-444553540000}

2=Saitek Pro Flight Rudder Pedals

2.GUID={C7D70A70-EF3C-11E0-8001-444553540000}

See how FSUIPC can deduce from this that your joystick "A" is device number 0 in Windows, and so on?

Originally only the names were used, but then folks had trouble with multiple units with the same name (eg two throttle quadrants). So I included the GUIDs from the Registry, which are guaranteed to be unique.

The "missing" lines

R=<< MISSING JOYSTICK >>

Y=<< MISSING JOYSTICK >>

indicate that you have assignments somewhere in your Buttons or Axes sections to joysticks lettered "R" and "Y" but no matching device. Maybe ones you've removed or re-lettered?

This won't be doing any harm, but you could search for those assignments in those sections, and remove them.

Regards

Pete

[bradrcfii]

Ihave seemed to develop a new problem. I am calibrating the elevator.

Pushing forward elevator(pitch down) and setting the minimum seems to be no problem. Itrecords about 16128 when depressing the set minimum button. When I pullaft elevator and hit the set button, I hear a windows tone but no change ismade. I am left with basically the same values in the Min and MAXwindows. FSUIPC or windows is simply is not accepting my MAX value input.

EDIT: I edited the ini file chnaging one value to absolute which fixed the problem but still wonder why the user interface was not working?

[Pete Dowson]

Pushing forward elevator(pitch down) and setting the minimum seems to be no problem. Itrecords about 16128 when depressing the set minimum button. When I pullaft elevator and hit the set button, I hear a windows tone but no change

Since the range will be something like -16000 or so to +16000 or so, setting the MINIMUM to +16128 will obviously completely prevent you from setting a MAXIMUM or CENTRE anywhere above it!

Please think about what the words mean: MINIMUM means smallest or lowest number, MAXIMUM means highest. Look them up in a dictionary if you are still confused! And negative numbers are ALWAYS lower than positive numbers.

FSUIPC simply wants the numbers to be in order -- MIN less than CENTRE less than MAX. It cannot calibrate with a meaningless jumble of numbers. The sound is merely it telling you that you have it wrong.

Pete

[bradrcfii]

Just following the simsamri directions which have worked in the past.

Thanks for the math lesson.

[Pete Dowson]

Just following the simsamri directions which have worked in the past.

Hmm. Something is very wrong with them if they get you setting the minimum calibration point at almost the maximum value you can possibly get! :-(. Why not try the simply numbered steps in the FSUIPC User Guide?

Pete