Avionics Fault light on the enunceator panel
-
I know it would be very difficult to help with this problem but thought I would throw it out there anyway, just recently I have been getting an Avionics Fault light on the Enunceator panel as soon as I click the MMC switch on the Avioics Power panel. This happens even when I follow the long version of startup. I am wondering if any one else was having the same problem. Can’t navigate with this issue so I hope I can get it fixed soon.
-
Normal error for BMS. BMS models the error systems better than before but not so great that the MCC “suppress normal errors on startup” routines aren’t there. So expect a half dozen or so errors and clear them on the TEST page (PFL, CAP, and MC should extinguish when you clear the "root cause).
-
I know it would be very difficult to help with this problem but thought I would throw it out there anyway, just recently I have been getting an Avionics Fault light on the Enunceator panel as soon as I click the MMC switch on the Avioics Power panel. This happens even when I follow the long version of startup. I am wondering if any one else was having the same problem. Can’t navigate with this issue so I hope I can get it fixed soon.
I think you’re referring to the avionics and IFF faults on the caution panel that are present on start-up? If so clicking on the F-ACK button twice will clear that fault
-
I think you’re referring to the avionics and IFF faults on the caution panel that are present on start-up? If so clicking on the F-ACK button twice will clear that fault
OMG I can’t believe how many times I am seeing this mistake of knowledge of the F-16. The Fault Acknowledge button doesn’t CLEAR anything. It, as it’s name implies, ACKNOWLEDGES the errors that exit. They are still there waiting to be properly cleared which is done just as Frederf mentions above through the test page and hitting the clear button (OSB 3). This is exactly how the real aircraft itself works.
If you hit the FACK button and remove the caution indication go ahead and hit that FACK again and watch the PFL show the same errors all over again.
-
OMG I can’t believe how many times I am seeing this mistake of knowledge of the F-16. The Fault Acknowledge button doesn’t CLEAR anything. It, as it’s name implies, ACKNOWLEDGES the errors that exit. They are still there waiting to be properly cleared which is done just as Frederf mentions above through the test page and hitting the clear button (OSB 3). This is exactly how the real aircraft itself works.
If you hit the FACK button and remove the caution indication go ahead and hit that FACK again and watch the PFL show the same errors all over again.
No need to blast your top off.
For so many years, Falcon 4 users have been accustomed to a ridiculous fault system reporting procedure. Remember the “all systems ok “ message ?
This is something new for them and in their defens it is not acting 100% as it is supposed to. They are simply reporting what they are observing, which is correct in a sense.
The F-ACK, ( as it is now coded ) dose clear the startup faults. We know it should not. We will try to address this issue and make the F-ACK acknowledged and recall faults until the fault is corrected AND the clear button on the test page is pushed.
What happens instead in BMS is that the fault memory will clear immediately if the fault is corrected.
I will give you an example that can be easily obseverd by all users.
A failed AGM-65 handoff wil procedure a HNDF FAIL. Pressing the F-CAK will acknowledge the fault. The PFLD is blanked but the AV mnemonic remains on the PFL as a reminder that a avionics fault is acknowledged butstill exists. A 2nd press will recall the fault, a 3rd will acknowledge and blank the PFLD and so on.
Once you have completed the bore sight and command a handoff that is successful, the PFL’s that’s where associated with the AGM-65 handoff fail will clear completely and immediately from the fault memory. This can be seen clearly by the AV mnemonic blank out for the top right corner of the PFLD, without a test page “CLEAR”
This is how it is working now.
What we need to do is clear the PFL’s and PLFD ONLY if the fault is fixed or the systems power is shutoff ,AND the CLEAR button is pushed. -
No need to blast your top off.
For so many years, Falcon 4 users have been accustomed to a ridiculous fault system reporting procedure. Remember the “all systems ok “ message ?
This is something new for them and in their defense, it is not acting 100% as it is supposed to. They are simply reporting what they are observing, which is correct in a sense.
The F-ACK, ( as it is now coded ) dose clear the startup faults. We know it should not. We will try to address this issue and make the F-ACK acknowledged and recall faults until the fault is corrected AND the clear button on the test page is pushed.
What happens instead in BMS is that the fault memory will clear immediately if the fault is corrected.
I will give you an example that can be easily obseverd by all users.
A failed AGM-65 handoff wil procedure a HNDF FAIL. Pressing the F-CAK will acknowledge the fault. The PFLD is blanked but the AV mnemonic remains on the PFL as a reminder that a avionics fault is acknowledged butstill exists. A 2nd press will recall the fault, a 3rd will acknowledge and blank the PFLD and so on.
Once you have completed the bore sight and command a handoff that is successful, the PFL’s that’s where associated with the AGM-65 handoff fail will clear completely and immediately from the fault memory. This can be seen clearly by the AV mnemonic blank out for the top right corner of the PFLD, without a test page “CLEAR”
This is how it is working now.
What we need to do is clear the PFL’s and PLFD ONLY if the fault is fixed or the systems power is shutoff ,AND the CLEAR button is pushed.Yeap that is not how the system works for sure. Even if a fault was transitional the fault remains in the real A/C till the clear on the test page is pushed to attempt to clear it. So if BMS sees a correct response from the A/C and automatically clears the fault for you that is enhanced over the real deal.
-
Yeap that is not how the system works for sure. Even if a fault was transitional the fault remains in the real A/C till the clear on the test page is pushed to attempt to clear it. So if BMS sees a correct response from the A/C and automatically clears the fault for you that is enhanced over the real deal.
Noted.
-
OMG I can’t believe how many times I am seeing this mistake of knowledge of the F-16. The Fault Acknowledge button doesn’t CLEAR anything. It, as it’s name implies, ACKNOWLEDGES the errors that exit. They are still there waiting to be properly cleared which is done just as Frederf mentions above through the test page and hitting the clear button (OSB 3). This is exactly how the real aircraft itself works.
If you hit the FACK button and remove the caution indication go ahead and hit that FACK again and watch the PFL show the same errors all over again.
I had a feeling someone would go ballistic. Its a video game dude relax.
-
I had a feeling someone would go ballistic. Its a video game dude relax.
You have good reason to think someone will go ballistic, if you go around referring to Falcon as a video game.
You realise starting flame wars is against the forum rules, right?
-
You have good reason to think someone will go ballistic, if you go around referring to Falcon as a video game.
You realise starting flame wars is against the forum rules, right?
Im not going to get banned or an infraction for telling a guy to relax after he tells me that do not understand how the systems in the F-16 function.
And yes its a game.
-
I did not say you were. I am simply bringing a pertinent item to your attention.
-
I did not say you were. I am simply bringing a pertinent item to your attention.
Im fine.
-
There is a small crime in obscuring the underlying truth of the situation, even by mistake. Just ask Dee Jay about Channel 15 and tower control frequency.
The fault and warning system in the F-16 consists of layers. There are individual systems monitored by primary warning systems. Secondary warning systems summarize, centralize, and alert the pilot to a fault condition. The Master Caution light illuminates when a new warning or caution event occurs. It’s a secondary indicator and can be cleared to allow more events to be alerted but doesn’t address the reason for the Master Caution.
The Master Caution is the central alert for conditions on the Caution Panel mostly for “hardware” things. Similarly and semi-parallel is the Fault Acknowledge button (F-ACK) and the Pilot Fault List (PFL) for “software” things like avionics problems, FLCS errors, etc. The HUD WARN and WARN RESET are the display and reset for the warning system which are similar to caution but much more serious. The Elec Sys warning is a subsystem of the caution system and has its own reset button. Lastly there is the TEST MFD page and the FLCS page. The TEST page has an OSB clear button and the FLCS has the FLCS panel for resetting. That’s 5 similar alert systems with 5 distinct central indicators and 5 distinct acknowledge/reset controls. And they may link into each other and appear in multiple alert systems.
Much like putting a sticker over the low oil light in a car, the F-ACK button may make the problem less visible but doesn’t address the issue. It is the single-button interface for the PFD useful to cycle through messages. I believe all PFL entries are of one of three categories Engine, FLCS, or Avionics and to really address them you want to cause that fault to stop which the F-ACK button simply does not do.
-
Im not going to get banned or an infraction for telling a guy to relax after he tells me that do not understand how the systems in the F-16 function.
And yes its a game.Maybe not, but Frederf summed up pretty well the situation. With a little open mindness, one will realize that the false information on the forum don’t help in the long run because communities tends to remember easily the wrong from the right
(human behaviour)
So we track these and correct them.
So whenever you post false or erroneous information, be ready to be corrected and assume your mistakes!
Best practice is to check before posting just like IRL btwWe want this place to be sane and not full of wrong information - for the benefit of our present and future members.
-
Im not going to get banned or an infraction for telling a guy to relax after he tells me that do not understand how the systems in the F-16 function.
And yes its a game.
Everyone can see this sim how they want but my suggestion is if you want to treat it like a game and not get into the nuts and bolts of it that is fine but do NOT go trying to give advice to someone about something you take light heartedly. It is easy for you to be wrong and the last thing people need around here is another person throwing around incorrect information. See Frederf’s in depth post as to how it works.
