August 26, 20223 yr Today I had 3 flights from PAYA to PANC.. On all three flights when I got within about 15 miles from PANC at around 10,000 FT, when I selected a lower altitude, the Autopilot disconnected with the associated alarm signal telling me the AP was off. Then the TOGA/Lock kicked in and the aircraft started climbing. I could not stop the climb, couldn't reengage the AP no matter what I did. Now yesterday I purchased the ORBX Alaska Mesh, so I figured maybe that was the problem, so I uninstalled it, in between the failed flights. same problem, so it wasn't the mesh. Now I am thinking the Fenix is all of a sudden hosed for some reason, so I took the Fenix on a short flight from Salt Lake City to Jackson Hole Wyoming, and everything worked fine. It just seem that this one are of the approach to Anchorage is like the Devils Triangle for the Fenix Autopilot. Now I got out the Cessna, 310, and flew the same approach into Anchorage, and no problem at all. So it seems to be that approach with the Fenix only. Anyone else have a similar problem?
August 26, 20223 yr 53 minutes ago, Bobsk8 said: Today I had 3 flights from PAYA to PANC.. On all three flights when I got within about 15 miles from PANC at around 10,000 FT, when I selected a lower altitude, the Autopilot disconnected with the associated alarm signal telling me the AP was off. Then the TOGA/Lock kicked in and the aircraft started climbing. I could not stop the climb, couldn't reengage the AP no matter what I did. Now yesterday I purchased the ORBX Alaska Mesh, so I figured maybe that was the problem, so I uninstalled it, in between the failed flights. same problem, so it wasn't the mesh. Now I am thinking the Fenix is all of a sudden hosed for some reason, so I took the Fenix on a short flight from Salt Lake City to Jackson Hole Wyoming, and everything worked fine. It just seem that this one are of the approach to Anchorage is like the Devils Triangle for the Fenix Autopilot. Now I got out the Cessna, 310, and flew the same approach into Anchorage, and no problem at all. So it seems to be that approach with the Fenix only. Anyone else have a similar problem? It sounds repeatable. Take it to Aamir and the Fenix Discord. You’ll get a solution there much quicker I bet -B
August 26, 20223 yr 59 minutes ago, Bobsk8 said: Today I had 3 flights from PAYA to PANC.. On all three flights when I got within about 15 miles from PANC at around 10,000 FT, when I selected a lower altitude, the Autopilot disconnected with the associated alarm signal telling me the AP was off. Then the TOGA/Lock kicked in and the aircraft started climbing. I could not stop the climb, couldn't reengage the AP no matter what I did. Now yesterday I purchased the ORBX Alaska Mesh, so I figured maybe that was the problem, so I uninstalled it, in between the failed flights. same problem, so it wasn't the mesh. Now I am thinking the Fenix is all of a sudden hosed for some reason, so I took the Fenix on a short flight from Salt Lake City to Jackson Hole Wyoming, and everything worked fine. It just seem that this one are of the approach to Anchorage is like the Devils Triangle for the Fenix Autopilot. Now I got out the Cessna, 310, and flew the same approach into Anchorage, and no problem at all. So it seems to be that approach with the Fenix only. Anyone else have a similar problem? To get out of TOGA/Lock you have to disconnect A/THR. And obviously you cannot engage AP with TOGA locked. So it was a user error mostly. As for the AP disconnect, yeah that happens every once in a while on the Fenix for no obvious reasons, so that's the buggy part. For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
August 27, 20223 yr 3 hours ago, Bobsk8 said: Today I had 3 flights from PAYA to PANC.. On all three flights when I got within about 15 miles from PANC at around 10,000 FT, when I selected a lower altitude, the Autopilot disconnected with the associated alarm signal telling me the AP was off. Then the TOGA/Lock kicked in and the aircraft started climbing. I could not stop the climb, couldn't reengage the AP no matter what I did. Now yesterday I purchased the ORBX Alaska Mesh, so I figured maybe that was the problem, so I uninstalled it, in between the failed flights. same problem, so it wasn't the mesh. Now I am thinking the Fenix is all of a sudden hosed for some reason, so I took the Fenix on a short flight from Salt Lake City to Jackson Hole Wyoming, and everything worked fine. It just seem that this one are of the approach to Anchorage is like the Devils Triangle for the Fenix Autopilot. Now I got out the Cessna, 310, and flew the same approach into Anchorage, and no problem at all. So it seems to be that approach with the Fenix only. Anyone else have a similar problem? I occasionally had AP disconnects with the FBW A320 and the Fenix A320. It turned out that turbulence could sometimes disconnect the autopilot. Then I read in some simmers blog that having a small null zone in the sensitivity area of the joystick controller could help. I put in a 2% null zone and it has not happened since. Just a thought. Lee Lee H i9 13900KF 64GB Ram 24GB RTX 4090
August 27, 20223 yr I've had a few autopilot disconnect issues due to turbulence but those have mostly been in cruise, I haven't seen any in descent myself. I had issues with the aircraft overspeeding, disconnecting the autopilot and causing other issues in the SU10 beta, the fix is noted in this thread: https://forums.flightsimulator.com/t/fenix-a320-overspeed-ap-issues-with-su10-fixed/529138 Edited August 27, 20223 yr by regis9 Dave Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU
August 27, 20223 yr Author These disconnects were weird because they happened at the same place in the flight path each time, within a mile or two.
August 27, 20223 yr Author 3 hours ago, btacon said: It sounds repeatable. Take it to Aamir and the Fenix Discord. You’ll get a solution there much quicker I bet -B I submitted a ticket today.
August 27, 20223 yr Happened to me as well just now at FL35. I can‘t say if it was due to turbulence (I wasn’t at the computer when it happened). Winds are 85kt so it’s possible. I only had this once before, in the first week after release. i9-11900K, RTX 4090, 32 GB ram, Honeycomb Alpha and Bravo, TCA Airbus sidestick and quadrant, Reverb G2
August 28, 20223 yr Author I think I may have discovered the problem yesterday with the Fenix autopilot disconnect I flew from the South of Mexico into Mexico City, ( MMBT to MMMX) and the approach to Mexico City goes over a mountain range and then descends on a Sid into 5L at Mexico City. About 10 miles out, I went to full flaps and V ref at around 137 knots, and was approaching the the glide slope, and I got a warning about speed which repeated a couple of times, and then the AP disconnected. Apparently I was getting turbulence from the low altitude next to the mountains, and the autothrottle didn't respond in time, speed dropped too low and autopilot disconnected, and switched to TOGA. This was the same basic approach into Anchorage were I crossed the mountains, and the AP disconnected when I got some turbulence. I remember the airspeed was varying all over when the AP disconnected. I am going to try the same approach again this morning and keep my speed up to around 200 knots until actually on the glide slope, and see if that makes a difference. Edited August 28, 20223 yr by Bobsk8
Archived
This topic is now archived and is closed to further replies.