Annunciator Panel on the HC Bravo for Baron & Bonanza
-
Would like to invite for a small brain storm, before mapping the LED Annunciator Panel for the HC Bravo.
● Landing gear is up when flaps are fully extended or throttle is retarded
->Master Warning
● Bus voltage is below 24 VDC
->Low Volts
● Left or Right Alternator rectified voltage is below ~26VDC
->Low Volts
● Left or Right Cowl Flaps are extended
-> Master Caution
● Air conditioning condenser door in fully extended (ground) position
-> Door
● Gyro suction below 3.0 inHg
-> Vacuum?
● Starter is engaged
-> Starter Engaged
● Aft door is unlocked
-> Door
● Deicing boot manifold is pressurized
-> Anti Ice?
● Left or Right pitot probe is receiving current
-> Anti Ice or Master Caution?
● Windshield heating pane is receiving current
-> Anti Ice?
● Standby electric vacuum pump activated
-> Vacuum
● Standby alternator is providing power (steady), and load is greater than 20A (blinking)
-> Master Caution?● “ENGINE MONITOR ALARM”
-> Master WarningThanks for any feedback.
-
@GunStrauss said in Annunciator Panel on the HC Bravo for Baron & Bonanza:
● Left or Right pitot probe is receiving current
-> Anti Ice or Master Caution?Anti Ice would be my vote.
The rest all seem logical to me.
-
Thanks,
and then finding the right conditions - that actually match, is not a trivial task.
Is it possible to map the lights directly from the panel somehow?
-
Each annunciator's conditions should be pretty straightforward, actually. I could also make an addition to the code to output their state. I was weary to do this early on, because I didn't know just how much performance I had to work with, but that's a relatively trivial amount of computation at this point.
If you want to try the edit I would make, and let me know how it works, here's all your have to do: Search for the first occurrence of "#TEST_CODE#" in AnalogBonanza_Templates.XML, and add the following line after the "or" immediately following it:
d (>L:var_#NODE_ID#_readonly, bool)That will store the boolean state of all annunciators (even for autopilots, and such) in an L:Var, which you can access using the name of the annunciator from AnalogBonanza.XML. For instance, the low voltage annunciator will be stored in (L:var_GSA_LowBusVolts_readonly, bool). Let me know how it goes!
-
Thanks, will give it a try. Initially I would like to add the conditions directly, but lost a bit of motivation on the first attempt, as I only found two 'volt-data' in use. Electrical Battery Bus Voltage and Electrical Battery Voltage, and the synchronised number they use, although it's close, is not the same number that triggers "Bus voltage is below 24 VDC" in the virtual cockpit, as the value is 25 or more when the Low Bus Volt lamp ignite on the panel inside MSFS.
If you had a list of the datas I needed to use, it would be interesting to try to make the conditions, but if I get the other solution to work and there is no performance hit, then maybe it´s not with it.
-
I could generate the list for you pretty easily, because they are all next to each other in the file. Some of them are simple, but others are a small block of code. There's no way you will see a performance hit with the other method, and it's obviously much easier, and future proof. I just have to be careful with how many of those kinds of features I add, since they all add up after a while. Hopefully our hardware will grow with the complexity of MSFS addons, or FS2024's multithreading will help with animation and Javascript execution times.
-
If it's easy for you to post the list here, then I would very much appreciate it! (Maybe someone else would need it in the future for something else?)
But I'm going to make a cup of coffee now, and try the method you suggested in the previous post :)
-
Seems to work perfectly in both the Bonanza and the Baron. Just need to test and provoke the different alarms, especially "standby alternator is providing power (steady), and load is greater than 20A (blinking)" will be interesting to see.
To perfect the setup, any idea how to find the engine alarm?
-
Glad to hear it's working. That should be very robust, so I don't think you will find any problems.
Unfortunately, the engine monitor alarm must be the only annunciator in that aircraft that does not using my annunciator template, haha. If you want to see the full condition, you can search for "JpiWarning_EM" in the XML file. As you will see, (L:var_JpiAlarm_1, bool) is the variable output by the engine monitor whenever there is an active alarm.
-
Engine alarms also working. This is starting to become everything I dreamed of in MSFS, when I bought these controllers. Analog Baron cross-country with throttles, radio and a nice yoke. Looking forward to go through your RNAV tutorial one of the days!
-
G GunStrauss referenced this topic on
