Hollister56 Posted September 16, 2024 Posted September 16, 2024 Does anyone know how to reset the VDI amber warning lights after landing? Thanks
RustBelt Posted September 17, 2024 Posted September 17, 2024 I mean, don’t be on fire maybe? If pinkey paddle and Autopilot/Stab awg off aren’t doing it. Try a master reset or a full generator reset (L,R and Emerg off then on) But also be less on fire. 2
Hollister56 Posted September 17, 2024 Author Posted September 17, 2024 (edited) I'm referring to the amber caution lights after a ALCS approach, and shutting down the jet with only external power connected. Everything is off, all switches you mentioned. I said AMBER not Red lights, but I did confuse Amber caution lights with Red warning lights in my original post. That's actually pretty funny, but also be less on fire......... Edited September 17, 2024 by Hollister56
RustBelt Posted September 17, 2024 Posted September 17, 2024 Yes I know you meant the left side lights. But your ship is out of shape. Why are you shutting down with external power? That’s a fairly irregular behavior following a landing. Do the lights stay out with a FULL dark shutdown then restart? Because you may just be in a system dead end because it doesn’t expect to keep running once you park it. It may be reliant on a power down or some diagnostic level test/reset. And seriously, why are your fire lights on? 1
Hollister56 Posted September 17, 2024 Author Posted September 17, 2024 Rustbelt, Are you from Steel Country? Anyway, the solution was to move the autopilot ACL switch to VEL/PCD then to OFF. Just moving the ACL switch to OFF didn't extinguish the amber caution lights. The Fire lights came on when shutting down the engines, and doing a Fire Test put out those lights. I will fly a few more flights to verify. BTW, I did a complete shutdown to a cold dark airplane. Then requested external power, which the ground crew won't connect unless the canopy is open, took me a while to figure that one out. After power up the lights were still on, Engine Fire and VDI Caution lights. So, then I tried the above and it worked, no lights.
RustBelt Posted September 17, 2024 Posted September 17, 2024 Yea trapped n the heart of North East Ohio. Where every car I’ve ever loved has been consumed by the orange and crunchy menace well before any significant drivetrain failure. Sounds like a stuck switch state in the cockpit controls. ACL to OFF must not register, but VEL/PCD to OFF does. Are you clicking it, or is it tied to a bound switch? Sometimes bound switches move the cockpit switch, but don’t actually cause the action. Typically more in the Goshawk than the Tomcat. Weird the fire lights come on with engine shutdown. That’s really not how any of the typical fire loop detection systems work in real life as it’s a purely destruction based detection or a test shunt circuit.
draconus Posted September 17, 2024 Posted September 17, 2024 13 hours ago, Hollister56 said: Does anyone know how to reset the VDI amber warning lights after landing? They should be off at touch down. Is it some modded cockpit? If yes, that's your answer. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Hollister56 Posted September 18, 2024 Author Posted September 18, 2024 (edited) It appears that if you let the F14 autoland the lights go out at touchdown. If you take over, disconnect the autoland and hand fly it to landing, the lights stay illuminated and will not go out. Even after shutting down the jet and then starting from a cold and dark restart, not exiting the mission. Maybe some one else can try this and see what happens are report back. The VEL/PCD didn't work. No cockpit mods.......... Edited September 18, 2024 by Hollister56
draconus Posted September 18, 2024 Posted September 18, 2024 3 hours ago, Hollister56 said: VEL/PCD It's VEC (like Vector) btw. I'll check the ACLS when I have a time. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
scommander2 Posted September 19, 2024 Posted September 19, 2024 I had tried ACLS few times, yes, they were off as soon as I touched down. Is it a bug? Spoiler Dell XPS 9730, i9-13900H, DDR5 64GB, Discrete GPU: NVIDIA GeForce RTX 4080, 1+2TB M.2 SSD | Thrustmaster Warthog HOTAS + TPR | TKIR5/TrackClipPro | Total Controls Multi-Function Button Box | Win 11 Pro
draconus Posted September 22, 2024 Posted September 22, 2024 I just made two ACLS approaches. First one was full ACLS up to touchdown - amber lights went off then - this is correct. Second one I let ACLS drive but disconnected the AP just before touchdown - amber lights stayed on and this is a bug. Can also confirm they go out when there is no power but if you ask for ground power they will be back, still a bug. Can we get this reported @Silhou? On 9/17/2024 at 6:03 AM, Hollister56 said: Then requested external power, which the ground crew won't connect unless the canopy is open, took me a while to figure that one out. Yes, they can't hear you when the canopy is closed. But if you have the power and ICS Hot Mic then you can talk to ground crew with canopy closed. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Silhou Posted September 23, 2024 Posted September 23, 2024 14 hours ago, draconus said: I just made two ACLS approaches. First one was full ACLS up to touchdown - amber lights went off then - this is correct. Second one I let ACLS drive but disconnected the AP just before touchdown - amber lights stayed on and this is a bug. Can also confirm they go out when there is no power but if you ask for ground power they will be back, still a bug. Can we get this reported @Silhou? Yes, they can't hear you when the canopy is closed. But if you have the power and ICS Hot Mic then you can talk to ground crew with canopy closed. Hey! Thank you for the report. I tarcked it internally for further investigation. 1 1
Recommended Posts