Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi Guys,

 

I am creating a text log of certain flight variables. All was going well, until I came to the Parking Brake.

 

It correctly registers if the parking brake is on or off using 'Ctrl + .' or clicking the button in the cockpit, however it is also activated when using the toe brakes on my rudder peddles.

 

I have managed to use a second OFSET (BCA) so that it does not register in my log if only one toe brake is pressed, however, if I touch both toe brakes, even only slightly it registers as set (even though its not actually set)

 

All ideas are welcome!

 

Thankyou,

Joe 

 

Posted

It correctly registers if the parking brake is on or off using 'Ctrl + .' or clicking the button in the cockpit, however it is also activated when using the toe brakes on my rudder peddles.

 

I'm afraid you need to explain more. How are your toe brakes assigned? All aircraft or only one specific one? What other offset were you testing?

 

Please use the FSUIPC logging facilities to see what is happening. Monitor the offsets and log the events which occur when you press your toe brakes.

 

Don't forget, also, that on most (if not all) aircraft the parking brake is merely the latched application of both toe brakes. In fact if programmed correctly, you have to press both toe brakes then pull the lever to lock them on. Releasing them is then a matter of pressing both toe brakes sufficiently. If assigned through FSUIPC there's actually a threshold value you can set for this in the INI file.

 

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.