January 18, 201412 yr Hi all, I'm definitely not new to the NGX and have flown many perfect hours with it. However I recently upgraded my PC (completely new PC) and reinstalled everything from scratch. All has been going well except for a problem with my NGX autopilot. Not sure if it is me doing something wrong but I never had this previously: With the FMS set up and a route programmed, I get airborne and shortly thereafter switch on the AP. Flying LNAV and VNAV and all is perfect for a while for 15 to 20 minutes perhaps. The aircraft tracks the lateral and vertical path, speed is correct and all is good. Then passing thru 27000 feet (or somewhere in that region) the Master Caution illuminates and I notice that the aircraft has started to decent and then very quickly over speeds. No message in the FMC. At this point 33,000 is set in the altitude window on the glare shield and also in the FMC. I must stress that I have not touched the controls or mouse/keyboard for at least a minute or two prior to this event. I disengage the AP and AT to regain control but following that, nothing I do can restore normal Auto Pilot. Even switching to Speed, VS, Heading etc - nothing works. The AP does arm but does it's own thing, disregarding anything set in the autopilot setting panel and arming it invokes a quite violent flight control movement causing the aircraft to bank or pitch at a high rate, out of control. AT also does not work when this happens, engines just stay stuck at one setting. I have to disarm AP and AT immediately to regain manual control. There is no choice but to terminate the flight or fly manually. I do not have failures set up on the aircraft. I do have SP1C installed. Any ideas on this and how to fix it greatly appreciated. Thanks. GregH Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor
January 18, 201412 yr Author Further on my post above, just wondering - my Motherboard (Asus Maximus Hero) has a known bug in that it fails to keep time properly. This in turn affects Windows time also. It is often quite far out. Could this be the source of my problem above? GregH Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor
January 18, 201412 yr Do you use FSUIPC.or any other modules in your current build? Not a lot to go on at the moment. It doesn't sound like your flying wrong. J u l ia n D i a m a n d i s
January 18, 201412 yr Author Yes, I have a registered copy of FSUIPC. I fly with CH Products yoke, throttle Quadrant and pedals. Most of it is set up in FSUIPC. I am leaning to believe the issue is related to the time problem on my motherboard boards BIOS. A common issue on the Asus forums right now. When I apply the interim solution to that problem ( which can work from a few hours to a few weeks before things go haywire again) I don't experience the autopilot problem. Might just be coincidence to though. GregH Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor
January 18, 201412 yr Yes, I have a registered copy of FSUIPC. I fly with CH Products yoke, throttle Quadrant and pedals. Most of it is set up in FSUIPC. I am leaning to believe the issue is related to the time problem on my motherboard It might be worth checking the weather settings in FSUIPC, I don't know about the mother board problems. J u l ia n D i a m a n d i s
January 20, 201412 yr I am leaning to believe the issue is related to the time problem on my motherboardboards BIOS. A common issue on the Asus forums right now. When I apply the interim solution to that problem ( which can work from a few hours to a few weeks before things go haywire again) I don't experience the autopilot problem. Might just be coincidence to though. I think it might be the thing. Having significantly different system time might make problems with licensing module. Try using internet time functionality in windows, it might help. --Peter Fabian
January 20, 201412 yr Further on my post above, just wondering - my Motherboard (Asus Maximus Hero) has a known bug in that it fails to keep time properly. This in turn affects Windows time also. It is often quite far out. Could this be the source of my problem above? Yes. You need to repair or replace your motherboard. More info about this problem here: http://forum.avsim.net/topic/412676-ngx-auto-fail/
January 22, 201412 yr Author Thanks, yes this is definitely the culprit. Applied the temp fix on the Asus website again and touch wood, the BIOS clock has kept time and NGX has logged around 10 problem free sectors. GregH Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor
January 23, 201412 yr Thanks, yes this is definitely the culprit. Applied the temp fix on the Asus website again and touch wood, the BIOS clock has kept time and NGX has logged around 10 problem free sectors. Huh, :blink2: never knew this kind of hardware problem could mess up the NGX. It'd be one thing to look for when I build a new rig. Thoriq Kamaruszaman, Potato Flier READ THE MANUALS.
Create an account or sign in to comment