##PMDG777 Baro Event

1 messages · Page 1 of 1 (latest)

native compass
#

@pale tulip
I'm struggling to use your "PMDG B777 Baro Timer Handler" for the Baro setting with an encoder.
Added the Input, Baro inc/dec and then, as Baro output, your Timer Handler which gave me just strange outputs on display and those during encoder use only. As soon as i stop the encoder, output goes 0
What am i missing? Don't get it.
Anyway, the Baro inc/dec works so far, but very slow.

pale tulip
#

The baro inc and dec require the Lvar to be reset to 0. That is what the timer handler does.

#

The output timer handler is just to reset the Lvar to 0. It just outputs the Lvar value, which can be 0 to 50 while the encoder is turned and reset back to 0.

#

The baro value setting is another totally different variable.

native compass
# pale tulip The baro inc and dec require the Lvar to be reset to 0. That is what the timer h...

I didn't got the reason for it. Guess because of the strange output. But now i activated it and set the output to "none" and now it seems working. Thought it would work without it, but then i saw the baro turning until the very last end....anyway its not an encoder in the 777, so using with an encoder could be quite difficult.
Any idea how to read out the in/hpa position? I didn't found it in hubhop so far...

pale tulip
#

Look for kohlsman

pale tulip
native compass
native compass
pale tulip
#

Ohh you use the switch lvar of the same code 0=inches 100=hpa

#

Try (L:switch_190_a)

native compass
pale tulip
native compass
pale tulip
#

STD mode should have a status variable

native compass
#

It’s not in yet.Maybe I can find it later on.

strong scaffold
#

I read this, but still not getting it. What do you exactly do with the timer handlers?

pale tulip
#

The knob in the sim is like a spring loaded three position switch. The longer you turn in one direction, the faster the setting changes in either way, up to a set max speed.

#

As explained before, the event requires a button release that an encoder cannot provide. This event assumes use of an encoder. The timer handlers checks how long it's been since the last click and resets back to 0.
When you turn the encoder, each click within the timer window adds to the speed. As soon as you stop, it resets to 0.

strong scaffold
#

yes i get that bit, but how to configure the timer handler within mobiflight then? do you configure the timer handler under the same action (button press) as the inc / dec itself? or do you configure it as a release action?

pale tulip
#

The description text on the Baro knob dec event says: For encoder. Requires using an output PMDG B777 Baro Timer Handler.

#

It is an output, so it should go to a Mobiflight output config.

strong scaffold
#

aha, just setting it as an output event, not necessarily outputting it to something, and now the encoder behaves normally yes. Ok, awesome. thank you for your help 🙂

pale tulip
#

Maybe an explanation would be good here. All inputs to the Sim are do-once code. When you press a button, Mobiflight sends the code to the Sim, the Sim executes the command, end of story.

#

Output is different.

#

With output, Mobiflight has to register each output config code with the Sim, so that the Sim can send it's value back to Mobiflight.

#

We can take advantage of this mechanism to have the Sim execute custom code with every Sim frame.

#

Care must be taken, as this hacking can easily hang up the Sim.