You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, when you first start Airbus, first power up test is performed of different systems, on some aircrafts ENG FIRE selftest of both engine one by one, on some not, but on all of them is FWC are in fault for about 30 seconds,
i could tell you exact time but lets say 30sec, then when power up of FWCs is finished with 3ple click, following indications are shown on status, under inop systems and under maintenance you can check exactly, but flight controls, ap1 +2 etc, i will photo you later, im not on work until 2 days,. But Until IRS are aligned, fctl, ap etc are inopp systems
will send you photo. And that doesnt happens on FBW
Expected behavior
.
Steps to reproduce
.
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
No response
The text was updated successfully, but these errors were encountered:
Aircraft Version
Stable
Build info
-
Describe the bug
So, when you first start Airbus, first power up test is performed of different systems, on some aircrafts ENG FIRE selftest of both engine one by one, on some not, but on all of them is FWC are in fault for about 30 seconds,
https://docs.flybywiresim.com/pilots-corner/beginner-guide/starting-the-aircraft/
i could tell you exact time but lets say 30sec, then when power up of FWCs is finished with 3ple click, following indications are shown on status, under inop systems and under maintenance you can check exactly, but flight controls, ap1 +2 etc, i will photo you later, im not on work until 2 days,. But Until IRS are aligned, fctl, ap etc are inopp systems
will send you photo. And that doesnt happens on FBW
Expected behavior
.
Steps to reproduce
.
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
No response
The text was updated successfully, but these errors were encountered: