CL650/Frequently Asked Questions: Difference between revisions
mNo edit summary |
|||
| Line 17: | Line 17: | ||
Most likely one of the default X-Plane auto-throttle commands have been used on keyboard or controller. This interferes with the CL650's custom throttle system. To resolve this situation find/assign a binding for <code>sim/autopilot/autothrottle_off</code> and actuate it (it can be removed afterward if desired), then find any similarly named control assignments and remove them. (It is highly recommended to use X-Plane's [https://www.x-plane.com/manuals/desktop/#joystickandkeyboardprofiles control profile feature].) | Most likely one of the default X-Plane auto-throttle commands have been used on keyboard or controller. This interferes with the CL650's custom throttle system. To resolve this situation find/assign a binding for <code>sim/autopilot/autothrottle_off</code> and actuate it (it can be removed afterward if desired), then find any similarly named control assignments and remove them. (It is highly recommended to use X-Plane's [https://www.x-plane.com/manuals/desktop/#joystickandkeyboardprofiles control profile feature].) | ||
== Why doesn't | == Why doesn't navigation source automatically switch to LOC? == | ||
The automatic nav source switch, known as Nav-to-Nav transfer, won't occur if the Pilot and Co-pilot's nav sources aren't both set to FMS when entering the terminal area (31 nm from the airport reference point), and hence the Nav-to-Nav setup did not occur. This scenario usually results from the Pilot's nav source being reset from LOC to FMS during post- or pre-flight setup after completing an ILS approach, but the Co-pilot's was not. Ensuring both sides' avionics are configured properly is part of the [[CL650/Checklists#FLIGHT COMPARTMENT CHECKLIST|flight compartment checklist]]. | |||
Revision as of 16:43, 11 March 2024
How to use the galley touchscreen from the cockpit?
The galley control panel is primarily used to control cabin lighting and recorded announcements. There is a command available to bring the galley control panel up as a popup window: CL650/galley_ctrl_panel/popup.
What does it mean when the CDU message "FPLN FULL" is shown?
This shows when an attempt is made to add waypoints to the flight plan when it already has the maximum 100 legs. This leg count includes previously flown legs, e.g. those available in DIRECT-TO HISTORY. To resolve this condition on the ground, consider shortening the flight plan by reducing the number of airways used, or entering only part of the flight plan and then updating it in flight using the procedure that follows. In flight, the simplest way to resolve this is to go to SEC FPLN, enter the destination and remaining legs, then activate the secondary flight plan.
Why does the auto-throttle stop working in flight?
The most common cause of ATS FAIL on the ATS mode status display is the active N1% limit in the FMS has been removed or deselected. For more information please watch this video: Hotstart Challenger 650 AutoThrottle Help.
How to disconnect the auto-throttle?
There are two commands available to disconnect the auto-throttle system (ATS), one for each physical button on the left and right throttle levers, respectively. Other than physical position, their function is identical.
CL650/pedestal/throttle/ats_disc_LCL650/pedestal/throttle/ats_disc_R
Why do my hardware throttle levers not work anymore?
Most likely one of the default X-Plane auto-throttle commands have been used on keyboard or controller. This interferes with the CL650's custom throttle system. To resolve this situation find/assign a binding for sim/autopilot/autothrottle_off and actuate it (it can be removed afterward if desired), then find any similarly named control assignments and remove them. (It is highly recommended to use X-Plane's control profile feature.)
The automatic nav source switch, known as Nav-to-Nav transfer, won't occur if the Pilot and Co-pilot's nav sources aren't both set to FMS when entering the terminal area (31 nm from the airport reference point), and hence the Nav-to-Nav setup did not occur. This scenario usually results from the Pilot's nav source being reset from LOC to FMS during post- or pre-flight setup after completing an ILS approach, but the Co-pilot's was not. Ensuring both sides' avionics are configured properly is part of the flight compartment checklist.