[4.3.3] Can't make a perfect ramp start!
-
-
Is it possible (or even correct idea) to start systems in a specific order to avoid some/all of the warnings and cautions (e.g. starting RWR before MMC)?
No
Actually not totally correct. You want to start up the FCC/MMC first as it or the SMS are the traffic cops of the communication buses.
Also if you are doing a full up ramp start I’d be waiting until after the SEC check to spin up the INS. No need to test out the INS battery on the ground.
-
No I am correct
In BMS, no matter what you do ,as soon as you flick the MMC/FFC on at any time, you will get the cautions. -
've made it…clean! I’m not sure, but I think MFD->TEST (page)->CLEAR (OSB-3) made the day…
Greeting
Earlybite -
yup
and don’t forget the FLCS BIT. skipping that might come back and bite you in the butt… -
yup
and don’t forget the FLCS BIT. skipping that might come back and bite you in the butt…2nd yup.
-
No I am correct
In BMS, no matter what you do ,as soon as you flick the MMC/FFC on at any time, you will get the cautions.Because besides being the traffic cop for the buses the MMC/FCC also manages almost all of the failure reporting. One thing that isn’t very realistic though is getting MFLs on turn on for systems that haven’t been turned on yet. In 19 years of working the aircraft I never saw that happen once. The one I have seen so far is RTWS faults on start up when I haven’t turned that system on yet.
-
Is there really a new procedure in 4.3.3?
Nope. If you learned the real checklists and used them in 4.32, they still work just fine in 4.33 - granted, some of the steps were pointless in 4.32, but I am glad to have learned to clear the MFL table as part of a ramp start!
-
Because besides being the traffic cop for the buses the MMC/FCC also manages almost all of the failure reporting. One thing that isn’t very realistic though is getting MFLs on turn on for systems that haven’t been turned on yet. In 19 years of working the aircraft I never saw that happen once. The one I have seen so far is RTWS faults on start up when I haven’t turned that system on yet.
All that means to me is that we still have work to do in getting the BMS code right Leech is right about how that code presently works though…an opportunity for improvement perhaps.
-
All that means to me is that we still have work to do in getting the BMS code right Leech is right about how that code presently works though…an opportunity for improvement perhaps.
exactly
-
One thing that isn’t very realistic though is getting MFLs on turn on for systems that haven’t been turned on yet. .
The BMS fault system dose work like that. If a system faults ( RALT BUS FAIL for example) and you switch the radar altimeter off, the fault will be cleared if a test page MFL clear is commanded since that system is shut down and has no power.
Switch the radar altimeter on again and a RALT BUS FAIL along with all the bells and whistles will reappear.
This is not the case though with the “startup faults” you see in BMS. They are only “eye candy”. As Boxer said, it can be improved. -
Oh BTW Stubbies2003
Didn’t know your a F16- techrespect…
-
The BMS fault system dose work like that. If a system faults ( RALT BUS FAIL for example) and you switch the radar altimeter off, the fault will be cleared if a test page MFL clear is commanded since that system is shut down and has no power.
Switch the radar altimeter on again and a RALT BUS FAIL along with all the bells and whistles will reappear.Absolutely true.
This is not the case though with the “startup faults” you see in BMS. They are only “eye candy”. As Boxer said, it can be improved.
My suggestion would that they be swapped to something that gets turned on with main system power without a separate switch. Say the AIBU perhaps. There are options.
-
Oh BTW Stubbies2003
Didn’t know your a F16- techrespect…
Aye 19 of my 25 years in the USAF was spent fixing the Avionics systems between blocks 20-42. Some things like the EGI/Link 16 I have no experience with as they were not implemented until after I left the F-16 community and was fixing the Osprey but the vast majority of these Avionics being simulated I have a pretty good amount of experience with the real deal.
-
My suggestion would that they be swapped to something that gets turned on with main system power without a separate switch. Say the AIBU perhaps. There are options.
Noted
We always appreciate constructive help from knowledgeable sources
-
Bah, no please no, no another “picky-this-bulb-lights-wrong” Leech! We just finished this Fault System Train-Wreck…
On the serious note as Leech said ramp start faults are pure eyecandy to “animate” ramp start a bit ber RL start videos.
Normal fault system follow rules that you mentioned and Leech explained. If system is off you will not get fault message from it till you try power it on. BMS Fault System just “note” its damaged internally and announce fault message as soon as you try use/power up that faulty system.
Please understand that this work on this was mostly guess as that so in-deep documentation is impossible to find or even not exists so behavior is based on our knowledge and bit guessing.
We tried model fault system as best as we can, still we hope its step forward from previous Falcon versions “ALL OK NO FAULTS” on PFL
As Boxer said, it can improve on feedback. This ramp start transient faults can be first candidate.
If I can suggest Stubbies2003, get in touch with Leech about this and I will see what can be done then for future versions.
-
Bah, no please no, no another “picky-this-bulb-lights-wrong” Leech!
That cannot possibly be me.
-
Hehe
-
If I can suggest Stubbies2003, get in touch with Leech about this and I will see what can be done then for future versions.
I’m just quoting this for reference when you have a nervous breakdown with the amount of new code they will want you to write.
I’m shaking my head in disbelief that you even suggested this, they’ll just egg each other on :mrgreen:
-
Indeed Ataribaby. you just shot yourself in the foot
Run mate, run