PMDG 737NG Autobrake issue

[Tom_L]

Hi Pete,

I am using ver. 5.11 and have assigned the axes by FSUIPC. I am also using LINDA to assign buttons. Install.log and FSUIPC.log show nothing abnormal - at least to me. Whenever I set the autobrake back to "off"  in the PMDG 737 the brakes are applied - be it from RTO or another setting. Disabling FSUIPC reverts the function to normal, e.g. autobrake is disarmed while the aircraft keeps moving. I have not assigned any button to autobrake functions, neither in FSUIPC nor in LINDA. Not a big deal, but nagging nevertheless.

Cheers

Tom

[Pete Dowson]

28 minutes ago, Tom_L said:

Whenever I set the autobrake back to "off"  in the PMDG 737 the brakes are applied - be it from RTO or another setting. Disabling FSUIPC reverts the function to normal, e.g. autobrake is disarmed while the aircraft keeps moving. I have not assigned any button to autobrake functions, neither in FSUIPC nor in LINDA. Not a big deal, but nagging nevertheless.

FSUIPC most certainly doesn't touch any autobrake or brakes unless programmed to or asked to by a client program.  In fact it probably couldn't in a PMDG aircraft since probably doesn't even uses the FS autobrake system. Test in a default aircraft to see if it happens there too.

It seems more likely that you or LINDA have programmed the wrong code for autobrake, one actually being used for the brakes instead. 

I don't use PMDG aircraft or LINDA, but maybe by enabling button/switch and non-axis event logging in FSUIPC you'll be able to see precisely what happens when you operate your autobrake. Obviously if FSUIPC isn't running, neither is LINDA. That should be a clue in itself.

You can work out the PMDG custom control numbers from the .h file in the aircraft's SDK folder. The list is near the end. You have to add two numbers together to arrive at the control number which needs programming.

Pete

 

[Tom_L]

Thx Pete,

I put the 737 on the runway, started logging per your instructions, put autobrakes to RTO and back and stopped logging, just a couple of seconds. But the log file (585kb) consists of hundreds of lines like

118608 *** EVENT: Cntrl= 70092 (0x000111cc), Param= 4194304 (0x00400000)  <70092>

and then somewhere in between:

118670 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

While "70092" is related to the autobrake, "65588" seems to be the control for applying brakes. A quick internet search for these numbers led to a thread from 2013 here in this forum with similar symptoms. The OP had his Brake axis assigned as normal FS axis - and BINGO: changing my assignment to "direct" solved the issue. No idea why I had it assigned it like that as I usually have it calibrated. Anyway - problem solved, thank you

Tom

[Pete Dowson]

16 minutes ago, Tom_L said:

The OP had his Brake axis assigned as normal FS axis

That will likely be interecpted by PMDG's code before FSUIPC gets to see it.

17 minutes ago, Tom_L said:

Anyway - problem solved, thank you

Good.

Pete