#Electronic Checklist configurations

1 messages · Page 1 of 1 (latest)

fallow arrow
#

I have built a switch panel that has a master switch, two green and one Red LED alongside 8 SPDT toggle switches.
When the left hand master switch is in the down position (LDG_Master), the lower red Led should turn on, indicating that the Landing Checklist is not completed yet. After all 8 switches are down, the red LED should turn off and the green LED should turn on.
The same thing should happen when the Master switch is put in the upper position (TO_Master), except it's the upper green LED that turns on when all 8 toggle switches are up, indicating that the Take-Off checklist is complete.

I've started by creating 3 output configs for the LEDs and two input configs called "LDG_Master_State" and "TO_Master_State". In each config I have associated a similarly named MobiFlight variable (these will respond to the button devices added to the Arduino Mega MobiFlight module from the "MF Settings" window).

Now I am hesitating and a bit uncertain so just seeking reassurance that I'm on the right track with my methodology.

I am planning to enter 16 more input configs for all the 8 toggle switches and associate each one with an appropriately named MobiFlight variable (8 TO check items and 8 LDG check items). Having done that I think I should be able to control the LEDs via the "Output Config Wizard" interface.
Here's a specific question that is part of my hesitancy.
For "LED_LDGChksCompleted" to light up I need to have all 8 of the LDG Chk switches down (each of their MF variables =1) so that I can add up all their values to a grand total 8. Therefore I will have to add 8 "References". To carry these values in to the "Modifier" window I will need 8 placeholders.
The same thing applies for "LED_TOChksCompleted" which will require 8 more references.
What can I use for these? I have two so far. That's # and ? I will use ! @ $ % and & That leaves me needing 9 more.
Any suggestions?

onyx turtle
#

Placeholder characters scope is limited to the output config where they are defined.
They can be reused in any other output config that requires them.

#

I don't think you need two sets of MF variables since the same switch status can be used for the two inverse verifications.