Maddog 100 feet Autopilot inc dec

[broken rampart]

I read @gusty egret request at link:

#1123317168000475246 message

to increase or decrease the autopilot altitude in steps of 100 feets you must rotate the knob while holding down the TAB key on the keyboard and right now I can't think of anything about how to "pass" this TAB via Mobiflight (i.e. by pressing long or short the encoder button).

Good luck

[gusty egret]

Brilliant 🔥

[broken rampart]

Hi @gusty egret

after having "played" a bit with the configuration of the Maddog Leonardo I managed to find the functions to simulate the behavior of the knob-button of the Maddog as present in the simulator and in reality.

By updating Hubhop Events you can find this two new events:

MD82_FGCP_ALT_KNOB_PUSH_100_FEET_STEPS_ON_PRESS
and
MD82_FGCP_ALT_KNOB_PUSH_100_FEET_STEPS_ON_RELEASE

to be applied to a button (i.e. that of the Altitude Autopilot Encoder switch).

Rotating the encoder while holding down the button will change the value by 100 feet. releasing it will return you to the 1000 feet variations.

This replaces my previous solution (using the Keyboard TAB key...bad 😎 )

Ciao and let me know if you encounter any problems.

[gusty egret]

I also add events today - baro knob

[gusty egret]

Today I encountered a problem when I created two parameters for the same button, and they did not want to work, only separately

I can't understand why this happens

[broken rampart]

I seem to remember that a long time ago we encountered this difficulty even when we wanted to operate the two APU buses and/or the External Power or fuel pump buses with a single switch.

Unfortunately the Maddog code is not in line with the MSFS standard.

I'll see if I can remember if we had found a solution.

[gusty egret]

I noticed that the code here is really specific, ported, challenge accepted)

I use button hold event for second event

[broken rampart]

Ok...now I remember: together with @inland pewter we had "created" a timer in Output that sent the two BUS events via a single switch, staggering the two L and R lines.

I seem to remember it working.

The frametime of the Leonardo code does not accept two simultaneous events.

If I find the configuration I will send it to you.

[gusty egret]

it will be excellent

[broken rampart]

Ok... below are the events that allow you to control the two Maddog switches of the APU Bus with a single physical switch:

An Output with Timer:

(L:ApuBusSwitches) if{ (L:MyTimer) 0 == if{ (E:SIMULATION TIME, second) (>L:MyTimer) 536870912 34 + (>L:overhead_event,number) } els{ (E:SIMULATION TIME , second) (L:MyTimer) - 0.1 > if{ 536870912 35 + (>L:overhead_event,number) 0 (>L:ApuBusSwitches) 0 (>L:MyTimer) }

An Input with the physical Switch to operate:

(L:ApuBusSwitches) ! (>L:ApuBusSwitches)

(I tried it now and it works even after years 😉 (thanks to @inland pewter))

At this point just replace the code with the parameters of the devices to be driven:
instead "L:ApuBusSwitches" create a new your Lvar: "L:ExternalLightsSwitches"
instead L:MyTimer create a new Lvar like L:MyTimer2
This to avoid to have two vars with the same name
and change 536870912 34 to ...Lights operating numbers...

Unfortunately it's dinner time here soon and I have to give up.
Let me know if you can configure it or I'll try to do it as soon as possible.