September 11, 20205 yr Commercial Member Let me explain my question a little further. Currently, when I start in my P3D Project Airbus Airbus 318/319/320 I will see a solid yellow Master Caution light on and a Master Warning light flashing. I click on them and they go off. I am trying to recreate the lights with my Saitek BIP panel so my question is more related to what system failure (or combination) causes these to illuminate? I am not a systems guy - just trying to recreate. These are not "study level" aircraft so I know not all systems are even close to being modeled. But something is triggering these on/off. If anyone who knows about this, appreciate any input. Clutch Intel i9-12900KF, Asus Prime Z690-A MB, 64GB DDR5 6000 RAM, (3) SK hynix M.2 SSD (2TB ea.), 16TB Seagate HDD, Gigabyte GeForce 5080 RTX, Corsair iCUE H70i AIO Liquid Cooler, UHD/Blu-ray Player/Burner (still have lots of CDs, DVDs!) Windows 10, (hold off for now on Win11), EVGA 1300W PSUNetgear 1Gbps modem & router, (3) 27" 1440 wrap-around displaysFull array of Bravo, Saitek and GoFlight hardware for the cockpit. Varjo and HP VR headsets for mixed reality.
September 11, 20205 yr Any number of causes could illuminate those lights. I'm not Airbus expert but if you enter the sim with started engines on at the runway it's possible the lights are on because takeoff configuration isn't properly set (flaps, trim, etc.). I don't know to what detail the Project Airbus is simulated but that's just the first thing that popped into my head that can illuminate the warning lights. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
September 12, 20205 yr Clutch, huh....your question can´t be answered in detail here easy, because there are so many many combinations of conditions where the master warning or caution is triggered. Generally speaking, depending on the specific flightphase, these warnings coming up where a condition isn´t set as it should be or to just inform about an immanent conditon has changed. Like if you deactivate Autothrust in flight or the Autopilot and and and... May you could try a different approach. The lights are only results from the systemlogic behind. So figure out which parameter is set the light to on and which to off, then your hardware should illuminate at same point where the software panel does. Bernd P3D V6 - PC spec: Intel i9-9900 overclocked 5 GHz HT off, 32 GB RAM, GPU Nvidia RTX3090 24GB, 2xM2 SSD, Skalarki HomeCockpit and Jeehell FMGS on a dedicated Server, PF3 for ATC, MCE, GSX, EFB, AS+ASCA+ENV and OrbX
September 12, 20205 yr Author Commercial Member Thx for the replies. Yea, figured truly the combination of issues all during the flight could trigger one of these. Was basing the question on more of a simple aircraft. Anywho, it looks like LVAR has some intelligence that detects any master cautions or warnings so I may try to take that route. Intel i9-12900KF, Asus Prime Z690-A MB, 64GB DDR5 6000 RAM, (3) SK hynix M.2 SSD (2TB ea.), 16TB Seagate HDD, Gigabyte GeForce 5080 RTX, Corsair iCUE H70i AIO Liquid Cooler, UHD/Blu-ray Player/Burner (still have lots of CDs, DVDs!) Windows 10, (hold off for now on Win11), EVGA 1300W PSUNetgear 1Gbps modem & router, (3) 27" 1440 wrap-around displaysFull array of Bravo, Saitek and GoFlight hardware for the cockpit. Varjo and HP VR headsets for mixed reality.
September 12, 20205 yr 35 minutes ago, Clutch Cargo said: Anywho, it looks like LVAR has some intelligence that detects any master cautions or warnings so I may try to take that route. Take a look at XMLTOOLS for P3D over at FSDeveloper. (You can download for different sims) It has popup gauge/window that shows You all LVAR's in use, and You can even trigger or change their value. // gauge00=XMLTools!LocalVarsLogger, 0,0,400,400 // For FSX or P3D x86 // gauge00=XMLTools64!LocalVarsLogger, 0,0,400,400 // For P3D v4 or v5 x64 Edited September 12, 20205 yr by RamonB Ramón. Time, is the one thing no one can buy.
September 12, 20205 yr The master warnings/cautions coding act something like an electronic JK flip-flop w/ reset. When the gauge is first energized / populated with the current status of some variable, it will always trip. (something I could never get rid of) It does not necessarily means there is a problem. After the first reset it all works as it should. Here is a cut down version of our F-111 master caution. Does anyone have some Ibuprofen? 😷😭😂 <Gauge Name="SHRS master caution" Version="1.0"> <Update Frequency="3"> (A:CIRCUIT GENERAL PANEL ON, bool) ! if{ 3 (>L:master caution,number) 0 (>L:MC_Latch, bool) } (L:master caution,number) 1 > if{ (L:master caution,number) -- (>L:master caution,number) } (L:ann_oil_low,bool) if{ (A:Warning oil pressure,bool) ! if{ 0 (>L:ann_oil_low,bool) } } els{ (A:Warning oil pressure,bool) if{ 1 (>L:ann_oil_low,bool) 3 (>L:master caution,number) } } (L:MC_Latch, bool) 0 == (L:master caution,number) 1 == (L:BAT_INI, bool) 1 == and and if{ 1 (>L:Sound_MasterCaution, number) 1 (>L:MC_Latch, bool) } els{ (L:master caution,number) 0 == if{ 0 (>L:MC_Latch, bool) } } </Update> <Element> <Select> <Value>(L:MC_Latch, bool) 1 == (L:master caution,number) 1 == (L:LAMP_TEST, bool) || || (A:CIRCUIT GENERAL PANEL ON, bool) and</Value> <Case Value="0"> <Image Name="master_caution_off.bmp"/> </Case> <Case Value="1"> <Image Name="master_caution_on.bmp" Bright="Yes"/> </Case> </Select> </Element> <Mouse> <Cursor Type="Hand"/> <Click>(L:MC_Latch, bool) 1 == (L:master caution,number) 1 == (L:LAMP_TEST, bool) || || (A:CIRCUIT GENERAL PANEL ON, bool) and if{ 0 (>L:master caution,number) 1 (>L:Sound_Click, number)</Click> </Mouse> </Gauge> FS RTWR SHRS F-111 JoinFS Little Navmap
Archived
This topic is now archived and is closed to further replies.