CL650/Frequently Asked Questions: Difference between revisions
(13 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
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: <code>CL650/galley_ctrl_panel/popup</code>. | 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: <code>CL650/galley_ctrl_panel/popup</code>. | ||
== What does it mean when the CDU message | == What does it mean when the CDU message <code>FPLN FULL</code> 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 <code>DIRECT-TO HISTORY</code>. 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 <code>SEC FPLN</code>, enter the destination and remaining legs, then activate the secondary flight plan. | 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 <code>DIRECT-TO HISTORY</code>. 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 <code>SEC FPLN</code>, 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 <code>ATS FAIL</code> on the ATS mode status display is the active N<sub>1</sub>% limit in the FMS has been removed or deselected. For more information please watch this video: [https://www.youtube.com/watch?v=3k9yoFNvnOE Hot Start 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. | |||
* <code>CL650/pedestal/throttle/ats_disc_L</code> | |||
* <code>CL650/pedestal/throttle/ats_disc_R</code> | |||
== 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 <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 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), 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 properly configured is part of the [[CL650/Checklists#FLIGHT COMPARTMENT CHECKLIST|flight compartment checklist]], but sometimes overlooked. | |||
== Why do I get <code>XTALK FAIL</code> or <code>SEND NA-NOT IN SYNC</code> on the CDU? == | |||
[https://www.youtube.com/shorts/upExdOVD0eY Watch this ''short'' video to find out!] | |||
== Why is the cabin altitude showing as negative? == | |||
The <code>CABIN ALT</code> read out is like a barometric altimeter inside of the cabin, but one which has its subscale always set to the standard atmospheric value of 1013 hPa. If the Pilot's "baro" is set to a QNH of 1013 hPa also then the PFD altimeter will match the cabin altitude read out. In other words, they're both reading the same air pressure, just that the altimeter on the PFD is applying a QNH correction, whereas the <code>CABIN ALT</code> read out isn't. | |||
== How to execute a go-around with the Virtual First Officer? == | |||
After pushing TO/GA button (to activate the avionics' go-around mode), the "Confirm checklist item" command (<code>CL650/checklist/check_item</code>) changes function to prompting the Virtual First Officer (VFO) to perform the go-around actions in sequence (see below). Only once the VFO says "ready for immediate return checklist" does the function revert back to handling the on-board electronic checklist. After the "immediate return" checklist is completed, it continues to the "before landing" checklist. If one does not want to perform an immediate return to the same airport, but rather one wants to divert, then once the VFO says "ready for immediate return checklist," one will command "Go to previous checklist" (either using the Checklist top menu, or using a joystick/keyboard binding: <code>CL650/checklist/prev_checklist</code>). This will direct the VFO to the "after takeoff" checklist, which means the aircraft will be made ready for another climb and cruise phase towards the diversion airport of your choosing, and thence normal operation resumes. | |||
A video demonstrating this procedure can be watched [https://youtu.be/7NMaE92hYqI?si=xnUmM1COiTIsJ1ZS&t=1014 HERE]. For reference the automated VFO go-around actions sequence is as follows: | |||
# Set go-around thrust | |||
# Flaps 20 | |||
# Gear up | |||
# Set FMS as nav source | |||
# Set FLC speed 200 kts | |||
== How to calculate [[wikipedia:Center_of_mass#Center_of_gravity|Center of Gravity]] (CG) % for TAKEOFF REF page? == | |||
At this time we do not provide an official "weight and balance" calculator, however a community member provided these (unvalidated) rules-of-thumb: | |||
{| class="wikitable" | |||
!Load | |||
!CG% | |||
|- | |||
|[[wikipedia:Operating_empty_weight|OEW]] | |||
|29.3 | |||
|- | |||
|(+ 1 passenger) | |||
|(−0.34) | |||
|- | |||
| + 5 passengers | |||
|27.6 | |||
|- | |||
|(+ 4,860 lb fuel in main) | |||
|(−1.0) | |||
|- | |||
| + full main fuel tanks | |||
|25.6 | |||
|- | |||
|(+ 72 lb fuel in aux) | |||
|(−0.1) | |||
|- | |||
| + full aux fuel tanks | |||
|15.6 | |||
|- | |||
|(+ 31 lb fuel in tail) | |||
|(+0.184) | |||
|- | |||
| + full tail fuel tanks | |||
|34.0 | |||
|} |
Latest revision as of 11:40, 8 August 2025
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: Hot Start 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_L
CL650/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), 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 properly configured is part of the flight compartment checklist, but sometimes overlooked.
Why do I get XTALK FAIL
or SEND NA-NOT IN SYNC
on the CDU?
Watch this short video to find out!
Why is the cabin altitude showing as negative?
The CABIN ALT
read out is like a barometric altimeter inside of the cabin, but one which has its subscale always set to the standard atmospheric value of 1013 hPa. If the Pilot's "baro" is set to a QNH of 1013 hPa also then the PFD altimeter will match the cabin altitude read out. In other words, they're both reading the same air pressure, just that the altimeter on the PFD is applying a QNH correction, whereas the CABIN ALT
read out isn't.
How to execute a go-around with the Virtual First Officer?
After pushing TO/GA button (to activate the avionics' go-around mode), the "Confirm checklist item" command (CL650/checklist/check_item
) changes function to prompting the Virtual First Officer (VFO) to perform the go-around actions in sequence (see below). Only once the VFO says "ready for immediate return checklist" does the function revert back to handling the on-board electronic checklist. After the "immediate return" checklist is completed, it continues to the "before landing" checklist. If one does not want to perform an immediate return to the same airport, but rather one wants to divert, then once the VFO says "ready for immediate return checklist," one will command "Go to previous checklist" (either using the Checklist top menu, or using a joystick/keyboard binding: CL650/checklist/prev_checklist
). This will direct the VFO to the "after takeoff" checklist, which means the aircraft will be made ready for another climb and cruise phase towards the diversion airport of your choosing, and thence normal operation resumes.
A video demonstrating this procedure can be watched HERE. For reference the automated VFO go-around actions sequence is as follows:
- Set go-around thrust
- Flaps 20
- Gear up
- Set FMS as nav source
- Set FLC speed 200 kts
How to calculate Center of Gravity (CG) % for TAKEOFF REF page?
At this time we do not provide an official "weight and balance" calculator, however a community member provided these (unvalidated) rules-of-thumb:
Load | CG% |
---|---|
OEW | 29.3 |
(+ 1 passenger) | (−0.34) |
+ 5 passengers | 27.6 |
(+ 4,860 lb fuel in main) | (−1.0) |
+ full main fuel tanks | 25.6 |
(+ 72 lb fuel in aux) | (−0.1) |
+ full aux fuel tanks | 15.6 |
(+ 31 lb fuel in tail) | (+0.184) |
+ full tail fuel tanks | 34.0 |