F-16 Cold and Dark Engine Start-Up - Falcon BMS 4.35 - 3 Sweep Method
Вставка
- Опубліковано 28 тра 2021
- (RE-UPLOAD: Fixed a resolution issue) Hello everyone! Have been practicing my engine start-up procedures in Falcon BMS 4.35 and wanted to share as it may be useful for you! Also, here is the checklist I made for my self that may aid you:
---------
BMS F16 START-UP - 3 SWEEP METHOD
1ST SWEEP : BEFORE ENGINE START-UP (LEFT-TO-RIGHT)
1. EXT LIGHTS: As required.
2. FUEL: ENG FEED to NORM. *Failure to do so will feed engine with gravity only.
3. ELEC: MAIN PWR to BATT (BATT TEST EYECANDY) *Do not rest feet in rudder pedals as braking can deplete the JFS (jet fuel starter) accumulators, new 4.35.
4. AUDIO: COMM1, 2, MSL, THREAT, INTERCOM and ILS volume FULL CW.
5. BACKUP UHF: Left knob to BOTH, right knob as required.
6. CLOSE CANOPY AND LOCK SPIDER *Doing so during JFS operation may result in a failed JFS start.
7. LIGHTING: As required.
8. AIR COND: AIR SOURCE to NORM *Failure to do so may result in EQUIP HOT caution and equipment damage and malfunction.
9. ANTI ICE: Set to ON *Must be in ON for a later test, new 4.35.
2ND SWEEP: ENGINE START-UP (LEFT-TO-RIGHT-AND-BACK)
1. ELEC: MAIN PWR to MAIN PWR (Enables the generator)
2. START-UP: Confirm throttle is in cut-off position. JFS to START 2. At 25% RPM set throttle to IDLE. *2 JFS accumulators are available, start 1 uses 1 each start-up attempt (50/50 chance of engine start), start 2 uses both. If JFS ACC are depleted and start-up is unsuccessful, they must be recharged by the ground crew.
KEEP AN EYE ON:
- HYD/OIL PRESS Light off between 30-35% RPM *If not, and pressure below 15 psi, fault is present, throttle to cut-off
- FTIT should increase proportional to RPM. Not go above 700C, if above 750C, Hot Start is present, set throttle to cut-off
- CONFIRM GOOD START-UP: Fuel Flow Between 700-1700. Oil Press above 15. Nozzle position above 94%. FTIT Never above 800. Hydraulics at 12 o Clock Position and 3 gear green lights.
3. TEST PANEL: EYE CANDY MOSTLY, PROBE HEAT ONLY SYSTEM THAT MAY FAIL
4. EPU: Remove EPU Safety Pin (Ground Crew) *EPU Check can be skipped. PROBE HEAT to ON, failing to do so may result in in-flight issues
5. AVIONICS POWER: All switches on. When DED alive, EGI to ALIGN NORM
6. SNSR PWR: RDR ALT to STBY, FCR to ON, left and right chin hardpoints as required.
7. DED: Confirm EGI Alignments has commenced.
8. HUD: Switch ON via the ICP SYM thumbwheel. Reset FLCS to clear Faults. Clear the MFL on MFD TEST page via OSB 3.
9. IFF: CNI to UFC. IFF MASTER to STBY.
10. Load Data Cartridge on DTE Page via OSB 3.
11. Set up radios as required.
3RD SWEEP: AFTER ENGINE START (LEFT-TO-RIGHT)
1. FLCS BIT *Test is eye candy.
2. MANUAL TRIM Panel: Check all needles are centered.
3. AIR REFUEL CHECK *System rarely fails so check can be skipped.
4. ECM to OPR.
5. SEC Check: Not mandatory for a ready-to-go jet.
6. TWA: Power On. CMDS: RWR, JAM, Chaff, Flare set to ON. Mode as required.
7. Set Stores Config as required
8. RWR: Test and handoff, failure to handoff will prevent system to warn from threats.
9. Use this time to configure mission settings such as navigation aids, weapons settings, pre-briefed joker, get ATIS info, etc.
10. Confirm no faults remaining, if so, do as required. Depress F-ACK.
11. Confirm alignment is complete and set EGI to NAV.
12. ANTI-ICE: Turn OFF and confirm FTIT dips at least 10C. Set Anti-Ice to Auto.
13. Test and activate oxygen.
14. Set parking break, remove wheel chokes, activate NWS, arm seat when not having a obstacle over your head.
15. You are ready to taxi.
On Runway: Landing lights, IFF Knob to NORM, RADAR ALT to ON, NWS OFF
---------
Current Specs:
R9 3900X
32GB RAM @ 3200Mhz
RTX 3090
3 Monitor set-up @1440p
Reverb G2
Track-IR 5 + PRO Clip
T16000M Hotas + Rudders
You can support this channel by becoming a patron here: / xcheck or becoming a member here: ua-cam.com/channels/tk1.html... - Ігри
![Falcon BMS 4.35 Campaign Tutorial [ Part 1 ]](http://i.ytimg.com/vi/e32U40K6lYs/mqdefault.jpg)
I still love falcon BMS. DCS might have a campaign engine in, uhh, let's say, 15 years from now. By then it might have a fully functional Viper. In BMS I love the campaign engine and intricate setup options we have for the campaigns. There's still VFW's who love flying BMS. I encourage all to join one.
Had no idea Falcon 4 was still being used. My boxed program has been in file for many years. Enjoyed your video!! Worked the block 50 GE F110 engine program when it was first fielded.
I worked on the software for the HUD for Block 50 - for my sins, LOL 😉
Nice, hope more to come.
In love with Spanish words!! Spanish follower here. Nice videos and very good content!!
I really appreciate this video! Thank you!
I'm coming to BMS from DCS, since they added VR support. I wanted to know why I was getting warnings during startup, and the manuals are not concise at all and so was having a hard time. Nice to know they're nothing to worry about!
Also, I *really* appreciate that your vid is just the concrete steps to actually start the thing up, and cuts out the silly roleplaying that the manuals seem obsessed with (eg, no useless tests). Thank you!
MIDS LVT is also a good one to make certain is on ;) given that it's required for your tacan, AS WELL AS THE link16 ijms.
@X-CHECK Not sure if this was a recent development, but the dash 1 manual seems to contradict itself about the FLCS BIT being eye candy. You're right that page 174 still has the eye-candy statement, but note that LATER, on page 215, it says "With 4.35, a new FLCS fault will happen at ramp and if not cleared accordingly may induce
repeated FLCS BIT FAIL." I'm assuming they didn't go back and remove the eye-candy line after writing this.
You must reset the FLCS! Or serious issues will occur. But the bit it self is eye candy for the time being.
4:30 how did you move the camera like that?
4:09 how did you move your head?
Do you use hotas or no hotas?
Hey guys, Cant use mouse looking inside 3d view, works middle button to move foward and to sides, wheel works to zoom, but cant look around. only outside the plane. I have the Opentrack installed and notice on some places that a NPClient64.dll file do that. Anyone nows how to solve that using the opentrack too?
I have a problem: when I start the engine on F16, the engine rpm goes to 70 instead of 60, even when the throttle is fully back. I check the throttle axis settings both on windows and game settings but they look fine. I have this weird issue on BMS only. do you have any idea about this?
You might be using a different block of aircraft or maybe your throttle detent isn't registering idle cutoff zone
help my MFD is green
followed every instruction and im not getting any RPM increase
Figured it out. My idle cutoff wasn't set properly in my axis mapping. Once I fixed that, all systems were go!
02:30 "I don't want noise from the radios be messing things up" yet you have a loud background music!!!!
FLCS BIT is not an eye candy. Read the manual.
BMS 4.35 -1 manual, change 3.00, page 174, it reads: "Both the FLCS bit & DBU are eye candy in BMS and have no consequences if you skip them."
So, this may be awkward for you but... Read the manual. Before you tell someone to read the manual lol.
@@XCHECK 1.12.8. FLCS BIT
The FLCS should be tested at ramp start by using the FLCS BIT switch. In real-life it is a magnetic spring-loaded 2-position switch. When engaging the FLCS BIT a green RUN light comes on and the FLCS goes through a full series of tests lasting approximately 45 seconds. During the tests the flight controls will move and this movement will be visible over the multiplayer network. Warning light and HUD messages will be displayed during the BIT.
The test can fail and failure is indicated by the illumination of the FAIL light on the FLT CONTROL panel. A FLCS warning light, HUD WARN message and corresponding PFL will also be displayed. A failed test can only be reset by rerunning the test again until successful completion.
A successful test is indicated by the green RUN light going off and the FLCS BIT switch snapping back to the OFF position. The FLCS bit progress can also be followed on the MFD FLCS page. The BIT in progress and BIT status messages are displayed.
This info is in the TO-BMS1F-16CM-1.pdf manual
Meabe you are talking about the DBU
@@Altrote100 Key word "in real-life". TO-BMS1F-16CM-1.pdf (BMS 4.35 Change 3.00), Page 174: "Both the FLCS bit & DBU are eye candy in BMS and have no consequences if you skip them." Go ahead, check it out, its right there in the manual. You claimed I did not read the manual because I called it eye candy, but I read the manual , and the manual clearly says it is eye candy, what do you want me to tell you man? Now the manual is wrong?
@@XCHECK "Both the FLCS bit & DBU are eye candy in BMS and have no consequences if you skip them".Yes, you are right but it is rare that it says that it is an eye candy because if you do not run the flcs bit the autopilot does not work and you would have problems controlling the plane, I say this because it happened to me.
Well that definetly puzzles me. But for this video in particular I wanted to stick to the manual lol
RE: "1. FLCS BIT *Test is eye candy" - Eye Candy!!! If you know the pain in the arse that BIT can be to write you would certainly NOT refer to it as "eye candy", blasphemer 😉
lol! "Eye Candy" is a direct quote from the BMS Manual, not my words! :P (BMS 4.35 -1 manual, change 3.00, page 174)