From here : https://siminnovations.com/forums/posting.php?mode=quote&f=35&p=18109 Gilles function set_panel_states(status,is_overspd,is_underspd) if is_overspd == 1 then str_speed_status = "8" elseif is_underspd == 1 then str_speed_status = "A" else str_speed_status = &qu...

Ralph wrote: ↑Sat Jun 22, 2019 7:01 pm Isn't the blink in the MCP done with a visible function? That does not work with a hardware display.

No, it's done by blanking the value = " " and when blink == 1, then setting the proper value "A" or "8"

Gilles

baranismen wrote: ↑Sat Jun 22, 2019 4:00 pm Nah, I couldn't handle it mate.

Again watch the coding to fully understand, I've already post the related part of the function in which it's handled

Gilles

For some encoders I use I'm having such a similar problem; when I turn them rapidly in one direction (altitude, let's say) commands tend to go otherwise and the changing process isn't stable. I tried this acceleration code but seems like it doesn't have any effect because in coding screen it does n...

pfactor, The debouncing is set in the add function. See here https://siminnovations.com/wiki/index.php?title=Air_Manager_Instrument_Logic_API#Rotary_encoder For some encoders I use I'm having such a similar problem; when I turn them rapidly in one direction (altitude, let's say) commands tend to go...

I ran the Arduino installer again just for good measure, and it is "partially" working now. Turning the knobs right or left yields the proper result in the sim. However, it is now taking two clicks of the knob to yield a result, where before each click yielded a result. For example when t...

Read carrefully,
as said previously, it blinks with the "status" value which is the first value forwarded to the "set_panel_states" callback function ("laminar/B738/autopilot/blink")

Have good coding
Gilles

Here's what we get,
I'm not sure for the option though, best to refer to those having already done this work

Gilles

I'm using a specific txt_add for either "A" or "8" (txt_leds_warn_spd) which is displayed only with overspeed or underspeed condition outside this, I also manage instrument power state and additionally if the LEDs should be displayed or not but to make it simple, here's the main ...

Not sure how i should introduce the "." to the Mach section, as add_text or modifying the string. Also using digit 8 or A on display overrides the IAS display, when the overspeed blink is going on, the whole display blinks. I'll keep working on it. Again, did you parse my coding in Z2DXP ...