Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MD11 Autobrake error

Featured Replies

Hello all,I have bought the boxed version of the PMDG MD11 1.20.0055 for FS2004. Everyting is more than perfect on this aircraft, also the framerates. Unfortunately there is one pretty important error with the Autobrakes. After touchdown they cannot be disarmed. Not with the button, not with the Period <.> key. It remains stuck. To erase the problem, the flight has to be reset or be remade. It occurs on all liveries. Is this a bug or am I doing something wrong in setting up the a/c for instance?I wonder if this problem occurs among more users of this very new boxed livery by Aerosoft, or if this a particular problem.Best regards,Leon Brouwer

  • 2 months later...
Hello all,I have bought the boxed version of the PMDG MD11 1.20.0055 for FS2004. Everyting is more than perfect on this aircraft, also the framerates. Unfortunately there is one pretty important error with the Autobrakes. After touchdown they cannot be disarmed. Not with the button, not with the Period <.> key. It remains stuck. To erase the problem, the flight has to be reset or be remade. It occurs on all liveries. Is this a bug or am I doing something wrong in setting up the a/c for instance?I wonder if this problem occurs among more users of this very new boxed livery by Aerosoft, or if this a particular problem.Best regards,Leon Brouwer
I have the same problem , see my quote on 6-7-09 PMDG MD-11 brake problem in FS2004Richard
  • 1 month later...

I bought the MD-11 for FS9 a few days ago, and so far I'm very impressed. Well done!However, I also often encounter situations where, desipte everything being set up correctly, autobrakes simply don't have any effect whatsoever.Most of the time they do work for RTO, but they almost never do after touchdown. As I said, I double checked everything is set up correctly (autobrakes switch set as required, ground spoilers armed, anti-skid active and so on).I noticed there might me some connection to the panel state that was loaded before flight. "Cold & Dark" almost always results in ABS not working for me.I have CH Pro-Pedals, which I configured for left and right toe-brakes using the according options within the FS9 settings menu. I read somewhere on this forum that one solution might be to try using FSUIPC for braking assignments, but I couldn't manage to set it up correctly (breakes where always applied). Can someone with a similar setup explain to me in a little more detail how to do it?Any help would be greatly appreciated! And keep up the amazing work (still hoping for 737 NGX in FS9 though... ;) ).Sincerly,Martin Buchheim

I prefer to create my own saved panel states for each saved flight. This might solve your intermittent ABS problem.

Dan Downs KCRP

Dan, thanks for your suggestion. I just did another flight with my own panel configuration. Again, no brakes on touchdown. I'll try configuring the brake pedals using FSUIPC again now, maybe that will be a (temporary?) solution.Cheers,Martin Buchheim

Brake pedals and autobrake seem to go together as a topic here. Try an advanced search to see what others have done. All I got is a cheap joystick.

Dan Downs KCRP

I don't have this problem. I'm using FS9, FSUIPC 3.85, and the CH Yoke and Pedals. FWIW, passing through 80 knots I press F1 (as keyed on my CH Yoke) to disegage reverse thrust, then passing through 60 knots I quickly move the throttle forward until I hear the click (spoiler returning to "arm"). That quick throttle spurt turns off the autobrake and spoilers, but is quick enough to not effect anything else. To me it makes it easier than trying to open a panel to retract the spoiler while turning off the runway. The autobrake disarming is just a side effect, but a welcome one.

- Chris

Gigabyte Z790 Aorus Elite AX | Intel Core i9 13900KF | Gigabyte GeForce RTX 4090 24 GB | 64GB DDR5 SDRAM | Corsair H100i Elite 240mm Liquid Cooling | 1TB & 2TB Samsung Gen 4 SSD  | 1000 Watt Gold PSU |  Windows 11 Pro | Thrustmaster Boeing Yoke | Thrustmaster TCA Captain X Airbus | Asus ROG 38" 4k IPS Monitor (PG38UQ)

Asus Maximus VII Hero motherboard | Intel i7 4790k CPU | MSI GTX 970 4 GB video card | Corsair DDR3 2133 32GB SDRAM | Corsair H50 water cooler | Samsung 850 EVO 250GB SSD (2) | EVGA 1000 watt PSU - Retired

Chris, thanks for the input. Did you use FSUIPC to configure your pedals, or did you do it via the FS9 configuration settings? Maybe you could make a screenshot of the sensitivity settings for your pedals, that would be very much appreciated.I talked to a friend with a similar hardware setup like the one I have, and he experiences the exact same problem: no autobrakes for him either on the eleven.I'm pretty sure there isn't anything wrong on my side, I also double checked that no unwanted brake inputs occur by looking at the raw (numeric) data from the brake pedals. I also saw the "auto_brakes=0" setting in the aircraft.cfg file and tried using 1 instead. That makes the autobrakes work but they can't be turned back off then once they were applied (and I'm also pretty sure PMDG had a reason to set this to 0...).I don't know what else I could do to fix this, so I'll stick with manual brakes for now and hope for a patch. If I come across a solution for this, I'll let you know. Cheers,Martin Buchheim

Perhaps your pedals are spiking input a little. The signal will be enough to deactivate the autobrake system. I use Saitek Pro Flight's yoke and pedals and have had no issues with the autobrake on the MD-11 under all situations, though I have not tested the RTO yet... (I suppose I should just to be sure that the setup works correctly)You might want to add some null zone to the brakes axes...In the VC, it is easy to lower the spoilers by clicking on the respective clickzone on the throttle quadrant... I can understand that it is a little bit more of an issue for 2D users, having to open the throttle quadrant to do this...I often roll off the runway onto an exit or hi speed exit under a little manual braking, pull the flaps and slats in, then throttle up a little to taxi in to the gate, doing so will automatically disengage the spoilers should I have forgotten to do so on final roll out... I have seen a couple of these things landing in Frankfurt, and the spoilers are often still deployed until after turnoff...Still loving every minute of it...Andrew

Andrew Entwistle

Perhaps your pedals are spiking input a little. The signal will be enough to deactivate the autobrake system. I use Saitek Pro Flight's yoke and pedals and have had no issues with the autobrake on the MD-11 under all situations, though I have not tested the RTO yet... (I suppose I should just to be sure that the setup works correctly)You might want to add some null zone to the brakes axes...
I already checked for spiking, but that's not the reason. Consequently, setting a nullzone doesn't do any good either (I've tried that, too). :(
Still loving every minute of it...
I do, too! Apart from that ABS flaw everything works very well.Martin Buchheim

Just wanted to give another status update, perhaps there're other ones who experience the same trouble.I did some more testing on this issue, and found out that the problems really seem to be related to the panel states. Not just "Cold&Dark" as I thought before, but pretty much every panel state that is pre-defined from PMDG causes the ABS system to fail when loaded.I managed to get ABS working by simply creating my own cold&dark-preset, and as far as I can tell so far everything seems to work as it should. Mabe those panel-states were created before the update, and aren't 100% compatible?!... but that's just speculation.Hope that helps,Martin Buchheim

I used the preset long turn around panel state last night, and did a full CATIII autoland, autobrake MED, spoilers armed...touched down, spoilers and brakes deployed, reverse thrust enabled and deployed, I shut off the autopilot at around 120-100 KIAS for directional control, below 80 KIAS reverse thrust off, reversers closed, dab on the brake pedals to disarm autobraking...No issues with the autobrake system at all... and I have the update installed...In my mind, I keep on thinking that your brake axis calibration is causing this... just an opinion though...Andrew

Andrew Entwistle

I checked my control settings and joystick raw numbers many times, there's really nothing more I can do. Are you using FS9 or FSX? Maybe there are multiple factors that lead to that bug on my configuration, but as long as it does work using my own panel-state, I am happy...Cheers,Martin

Chris, thanks for the input. Did you use FSUIPC to configure your pedals, or did you do it via the FS9 configuration settings? Maybe you could make a screenshot of the sensitivity settings for your pedals, that would be very much appreciated.I talked to a friend with a similar hardware setup like the one I have, and he experiences the exact same problem: no autobrakes for him either on the eleven.I'm pretty sure there isn't anything wrong on my side, I also double checked that no unwanted brake inputs occur by looking at the raw (numeric) data from the brake pedals. I also saw the "auto_brakes=0" setting in the aircraft.cfg file and tried using 1 instead. That makes the autobrakes work but they can't be turned back off then once they were applied (and I'm also pretty sure PMDG had a reason to set this to 0...).I don't know what else I could do to fix this, so I'll stick with manual brakes for now and hope for a patch. If I come across a solution for this, I'll let you know. Cheers,Martin Buchheim
IIRC, I use both the FS9 configuration and FSUIPC. I know they say you can disable or avoid using the windows and MSFS configuration for yoke and pedal calibration, but I don't have a problem with my setup. I just make sure I have a good null on all axes, mainly the pedal's braking axis.If I get time I'll try and double-check my FSUIPC settings, but I'm 95% sure I have the pedals calibrated in there. Same with the throttle. I don't have the yoke configured though. I just never had a reason to as I works fine. FWIW, the reason I calibrated the pedals through the FSUIPC was because of an autobrake issue years ago. FSUIPC fixed it and it never effected any other plane since.

- Chris

Gigabyte Z790 Aorus Elite AX | Intel Core i9 13900KF | Gigabyte GeForce RTX 4090 24 GB | 64GB DDR5 SDRAM | Corsair H100i Elite 240mm Liquid Cooling | 1TB & 2TB Samsung Gen 4 SSD  | 1000 Watt Gold PSU |  Windows 11 Pro | Thrustmaster Boeing Yoke | Thrustmaster TCA Captain X Airbus | Asus ROG 38" 4k IPS Monitor (PG38UQ)

Asus Maximus VII Hero motherboard | Intel i7 4790k CPU | MSI GTX 970 4 GB video card | Corsair DDR3 2133 32GB SDRAM | Corsair H50 water cooler | Samsung 850 EVO 250GB SSD (2) | EVGA 1000 watt PSU - Retired

  • 5 months later...
IIRC, I use both the FS9 configuration and FSUIPC. I know they say you can disable or avoid using the windows and MSFS configuration for yoke and pedal calibration, but I don't have a problem with my setup. I just make sure I have a good null on all axes, mainly the pedal's braking axis.If I get time I'll try and double-check my FSUIPC settings, but I'm 95% sure I have the pedals calibrated in there. Same with the throttle. I don't have the yoke configured though. I just never had a reason to as I works fine. FWIW, the reason I calibrated the pedals through the FSUIPC was because of an autobrake issue years ago. FSUIPC fixed it and it never effected any other plane since.
It has NOTHING to do with yokes/pedals/throttles. I have neither....

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.