MobiFlight Community Support

Anyone know how to write to the MSFS PMDG 737-700 Autobrake switch?

I figured out how to Inc and Dec the ROTOR_BRAKE by using a custom command, but I need to specifically set it to RTO/OFF/1/2/3 or MAX.

I guess I need to set EVT_MPM_AUTOBRAKE_SELECTOR with a value 0 to 5 , but cannot find this event in the Mapping dialogs.

I would add it to Hubhop, but don't have a clue how to do it.

Hi

Please stay a little calm.
The community working hard to implement the PMDG as soon as possible.

The "rotor brake" provisional stuff was the first idea.... And work already for some things.
Use a Position is here currently not possible or only with a special logic and Condition Script.

But since yesterday we also think the SDK can be working. So we have access to PMDG same way as in the past (Own events, also with SET to Position, like in P3D)
And own Variables for every single LED and Value.

Please give us some days to figure out !

Hi.

Did you find a solution?

Regards.

Hi

Looks like this all take a lot of time. Confusing in case SpadNext solve it within one day.

Current State:
We solve all Outputs as i know (except VS Speed) in a good way. For Inputs the workaround with the script logic is also implement in lots of configs.
( E.g. in those Multi Rotary) we do something like "Check if Target Position and current Position in sim is equal. If Greater as make a right click command and loop again for another check ..... If less then make a left click command and loop..... If equal End.
Another Idea that was used is sending in the dark for e.g. a 4 Position Switch 4 times a right click .... So we know garantee switch is now in most left position. So whatever switch is already in pos 0 or it is in 1 2 or 3 .... By 4 time sending the left turn command it will be most left! And then e.g. for pos 2 we additional send 2 Right Turn Commands at the end.

About SDK:
Meanewhile there is a first version of it by PMDG and also FSUIPC build a BETA. As i know the Beta fully support outputs but the Inputs was not working in our Test last week.

About MF Interface.
We say we like to wait for FSUIPC. If they have it running we know garantee that the SDK is working fine and then we can think about a own interface.
Here factor will be.... "Do we need it anymore??"
Here we must wait for user replys.... If everybody is happy with the current Presets and/or the useage of FSUIPC then we not need spent time to build our own system.

I think the problem is already solved, because Antiskid / Autobrake is now implemented.

Rgds Hermann