2,220
edits
IT Autoflight: Difference between revisions
Jump to navigation
Jump to search
→CMD and Autoland
| Line 187: | Line 187: | ||
Important Note: Most of the time, CMD tuning is not required to be changed. Only adjust CMD if the controllers do not work optimally. | Important Note: Most of the time, CMD tuning is not required to be changed. Only adjust CMD if the controllers do not work optimally. | ||
* Adjust the values in cmd Next. To see what each value does, see Tuning and Configuration above. | * Adjust the values in cmd Next. To see what each value does, see Tuning and Configuration above. | ||
* Tune V/S First | * Tune V/S First! This is very important! Once V/S is stable, you can tune the other modes. | ||
* Once those are all working, tune LOC and G/S. Easy way to test: KNUQ RW32R, takeoff runway hdg, climb 2000ft. ILS: 109.55. ARM ILS once above 250ft. Aircraft should intercept ILS. | * Once those are all working, tune LOC and G/S. Easy way to test: KNUQ RW32R, takeoff runway hdg, climb 2000ft. ILS: 109.55. ARM ILS once above 250ft. Aircraft should intercept ILS. | ||
* Once LOC and G/S are working, tune the Autoland. Most of the time, you can just use the "roll/kp", for "autoland/roll-kp". The "autoland/pitch-kp" is for the LAND/FLARE modes. Lastly, "autoland/rudder-kp" is for the Rudder LOC track. | * Once LOC and G/S are working, tune the Autoland. Most of the time, you can just use the "roll/kp", for "autoland/roll-kp". The "autoland/pitch-kp" is for the LAND/FLARE modes. Lastly, "autoland/rudder-kp" is for the Rudder LOC track. | ||