Autopilot, flight plan and connected devices
This chapter covers what the mod changes in the GFC 700 autopilot and the G1000 flight plan functions compared with the stock sim SR22T, how an autopilot disconnect is shown, the Navigraph chart softkey, the iPad and ForeFlight link, and the force feel on the RealSimGear Cirrus yoke.
The numbers and behaviours come from the Garmin Perspective+ Pilot's Guide (190-02183-03) and the GFC 700 AFM supplement for the SR20 (11934-S57).
Autopilot and G1000 behaviour
What it does. The stock sim SR22T differs from a real Perspective+ in a number of autopilot and flight plan details. The mod corrects the ones below. All of them are always on. There is nothing to switch.
Go-around (TO/GA)
What it does. In the stock sim, pressing TO/GA in the air switches the autopilot off, commands 7.5° nose up and presses NAV for you. In the mod the autopilot stays engaged, the go-around pitch is 7°, and NAV is left to you, as in the aircraft.
What you do and see.
- On the approach, at the missed approach point or when you decide to go around, press TO/GA.
TO/GA is the go-around button on the throttle lever. If you have no hardware button for it, assign a key or
button to the sim's takeoff / go-around control (the sim event is
AUTO_THROTTLE_TO_GA) in the sim's controls settings. - The flight director goes to go-around mode: wings level, 7° nose up. The autopilot stays on and follows it. Add power and clean up as usual.
- With an approach in the flight plan, the missed approach is activated and the CDI goes to GPS. Waypoint sequencing continues into the missed approach legs.
- Press NAV once. The autopilot engages GPS and flies the missed approach course.
- Select a climb mode (for example FLC or VS) and set the Selected Altitude for the missed approach altitude.
A second TO/GA press cancels go-around mode.
Differences from the real aircraft / limits.
- Takeoff mode (TO/GA on the ground) is unchanged from the stock sim.
- The autopilot does not fly the missed approach laterally by itself. Until you press NAV it stays wings level.
LVL key
What it does. In the stock sim the LVL key only puts the flight director in lateral level mode and leaves the autopilot off. In the mod it does what the Pilot's Guide describes: it engages the autopilot if it is off, selects level mode laterally and vertically (wings level, zero vertical speed), and cancels every armed mode.
Where to find it. The LVL key on the autopilot controller. A hardware LVL button (for example on a RealSimGear GFC 500) works the same way.
What you see. Green AP, with LVL as the active lateral and vertical mode. Armed modes such as an approach or
VPTH disappear. The same action is used by ESP when it levels the aircraft by itself (see
Terrain, surface and protection systems).
Direct-To from present position
What it does. A Direct-To now draws and flies a straight great-circle line from where you are to the waypoint, and the CDI is referenced to that line. In the stock sim the leg starts on your current heading and curves toward the waypoint first.
What you do. Press Direct-To, choose the waypoint, ENT, ENT. A Direct-To with a course that you enter yourself is unchanged.
Activate Missed Approach past the FAF
What it does. In the stock sim the Activate Missed Approach item on the PROC page stays grey with current navigation data. The mod makes it selectable when these are all true:
- the CDI source is GPS,
- the active leg is in an approach that has missed approach legs,
- you are at or past the final approach fix,
- the missed approach is not already active and you are not on a Direct-To to a waypoint outside the plan.
What you do. Press PROC, select Activate Missed Approach, ENT.
Limits. With LOC or VOR as the nav source the item stays grey. Use TO/GA, which activates the missed approach as well.
Approach "Load?" with an empty or Direct-To-only plan
What it does. The stock sim only offers Activate? when you pick an approach with fewer than two legs in the flight plan. The mod also offers Load?, as the Pilot's Guide describes: no waypoints are needed in the active flight plan to load a procedure.
What you do. Press PROC, select the approach, choose the airport, approach and transition, then Load? to put it in the plan without flying it yet, or Activate? to fly it now.
Limits. Load? is not offered while the active leg is already inside an approach. On a plan that holds only a destination, loading one approach makes its leg active, so a second approach pick then offers Activate? only.
Heading bug sync mode
What it does. Pushing the HDG knob normally moves the heading bug to the current heading once. With sync mode, pushed while the autopilot is flying a coupled NAV or approach course, the bug keeps following your heading. When you later switch to HDG mode, the aircraft does not turn away.
What you do.
- In a coupled NAV, GPS or approach mode: push the HDG knob. The bug follows the heading until the mode uncouples, you push the knob again, or you turn it.
- In HDG mode while banked: push the HDG knob. The bug syncs briefly so the aircraft rolls out cleanly.
Differences from the real aircraft / limits. There is no annunciation on the PFD while sync mode is active. This function has not yet been fully flight-tested.
VPTH acknowledgement before descent
What it does. In the stock sim, an armed VNAV path captures at the top of descent with no action from you. In the aircraft, when you are in Altitude Hold, the descent only captures if you acknowledge it. The mod adds that rule.
What you do and see.
- You are level in
ALTwithVPTHarmed (white) and the Selected Altitude set at least 75 ft below your altitude. - Within 5 minutes of the top of descent, acknowledge the descent in one of two ways: - turn the ALT SEL knob to change the Selected Altitude, or - press the VNV key on the autopilot controller, or the Cncl VNV softkey on the MFD flight plan page. During this window the key acknowledges. It does not cancel VNAV.
- From 1 minute before the top of descent, the white
VPTHflashes on the PFD until you acknowledge. - Acknowledged: the path captures at the top of descent and
VPTHgoes green. - Not acknowledged: the aircraft stays in
ALT,VPTHstays armed and this descent is not captured.
From PIT, VS or FLC the path captures by itself, as in the aircraft.
Related messages. TOD within 1 minute appears on the PFD with the "Vertical track" voice (see the next
feature). The advisories VNAV ALT SEL and VNAV NOT ARMED are described in
Aircraft and systems.
Limits. Outside the 5 minute window the VNV key works as usual: it switches VNAV on and off.
PFD navigation status messages
What it does. The stock sim shows only "Next DTK" five seconds before a waypoint. The mod shows the full set of flight plan annunciations in the navigation status box at the top of the PFD, starting 10 seconds ahead.
| Message | When |
|---|---|
Turn left to 021° in 8 seconds / Turn right to 021° in 8 seconds |
A turn at the next waypoint, counting down. The text flashes. |
Turn left to 021° now / Turn right to 021° now |
Time to start the turn. |
Next DTK 021° in 8 seconds |
A small course change at the next waypoint, counting down. The text flashes. |
Next DTK 021° now |
The new desired track applies now. |
Hold direct / Hold parallel / Hold teardrop |
Approaching a holding fix: the entry to fly. |
Arriving at waypoint |
Approaching the last waypoint. |
TOD within 1 minute |
One minute before the top of descent. Shown for 10 seconds in the DIS / BRG field, with the "Vertical track" voice. |
BOD within 1 minute, TOC within 1 minute, BOC within 1 minute |
The same for bottom of descent, top of climb and bottom of climb. Shown for 10 seconds, no voice. |
Courses are magnetic. The four vertical messages appear only with GPS as the nav source.
Altitude alerting
What it does. The stock sim gives no sound when you approach or leave the Selected Altitude. The mod adds both sounds from the Pilot's Guide.
| You | You hear |
|---|---|
| Climb or descend to within 200 ft of the Selected Altitude | A single chime |
| Have captured the Selected Altitude, then drift more than 200 ft from it | The voice "Altitude" |
The visual altitude alerting on the PFD is the stock one.
Limits. The sounds are about flying into or out of the band. They are held back for 3 seconds after you change the Selected Altitude, for 10 seconds after the aircraft is repositioned (for example by the Instructor Station's approach setup), and for 10 seconds after the PFD starts. They are silent while the PFD has no power.
Keypad-entered minimums
What it does. In the stock sim, minimums typed with the number keys show on the display but never reach the system: only a value set with the FMS knob works. The mod fixes this, so typed minimums arm the minimums alert and the "Minimums" voice.
What you do.
- Open the minimums field: PFD TMR/REF window, or the approach selection on the MFD PROC page.
- Type the altitude with the keypad.
- Press ENT, or move the cursor off the field. The value is rounded to the nearest 10 ft and takes effect.
Limits. Barometric minimums only. The aircraft has no radar altimeter.
MFD HOME key
What it does. The HOME key on the MFD keypad always returns to the Navigation Map page, whatever is open. In the stock sim it does nothing while a page menu or most pop-up windows are open.
Stabilized Approach alerts
What it does. The stock SR22T shows the Stabilized Approach annunciations to the right of the altitude tape with no voice, and some of them stay on or appear when they should not. The mod adds the voices and fixes these cases:
| Alert | Voice | Changed behaviour |
|---|---|---|
COURSE |
"Course, course" | Not given on the ground (the stock one appears on the taxiway after landing). Cleared when the navigation signal is lost. |
GLIDEPATH |
"Glidepath, glidepath" | Not given on the ground or below 200 ft AGL. Cleared when the nav source changes or VNAV takes over. |
GLIDESLOPE |
"Glideslope, glideslope" | Same as GLIDEPATH. |
FLAPS |
"Flaps" | Voice added. |
TAILWIND |
"Tailwind" | Voice added. |
CROSSWIND |
"Crosswind" | Voice added. |
BARO |
"Baro, baro" | Voice added. |
Each voice plays once when its annunciation appears, or when the text changes while one is shown.
Limits. The 200 ft floor for GLIDEPATH and GLIDESLOPE is the mod's choice. The Pilot's Guide gives no number. It stops the false alert in a normal flare, where the angular deviation grows quickly close to the antenna.
No yaw damper
What it does. The SR20 has no yaw damper. The stock SR22T engages one with the autopilot and above 200 ft AGL. The mod removes it:
YDnever shows in the AFCS status box.- If a hardware YD button or a key binding turns the sim's yaw damper on, the mod turns it off again at once.
What it means for you. Keep the ball centred with rudder in climbs and in autopilot turns, as in the aircraft.
Autopilot disconnect
What it does. The mod tells a disconnect you made from one the system made, and shows each the way the Perspective+ does. It also makes the electric pitch trim switch disconnect the autopilot, which the stock sim does not do.
Manual and automatic disconnects
| Manual disconnect | Automatic disconnect | |
|---|---|---|
| Caused by | AP DISC, the AP key, the pitch trim switch (MEPT), pulling the AP SERVOS breaker by hand, overpowering the yoke (see the yoke section) | An autopilot or sensor failure, a failure armed on the Instructor Station, ESP or underspeed protection dropping the autopilot, anything else the system does by itself |
AP annunciation |
Flashes yellow for 5 seconds, then goes out | Flashes red and white until you acknowledge it |
| Sound | The sim's autopilot disconnect tone | The sim's autopilot disconnect tone |
| To acknowledge | Nothing needed | Press AP DISC or the pitch trim switch |
The tone is the sim's own. The mod does not add a second one.
A mod function that moves the aircraft and has to drop the autopilot, such as the Instructor Station's approach setup, does it silently: no flash.
MEPT switch
What it does. With the autopilot engaged, any electric pitch trim input disconnects it. This is a manual
disconnect: yellow flashing AP.
Where to find it. In the sim this is whatever you have bound to the sim's elevator trim up and trim down commands, typically the trim hat on your yoke or stick.
How to acknowledge an automatic disconnect
- Fly the aircraft by hand.
- Press AP DISC once, or press the pitch trim switch once. It has to be a new press made after the alert started. Holding the trim switch from before does not count.
- The red and white
APgoes out.
Re-engaging the autopilot also ends the alert.
Differences from the real aircraft / limits.
- The mod plays no disconnect tone of its own. The tone you hear is the sim's.
- If your AP DISC button is bound to the sim's "toggle autopilot disengage" command and the Companion's yoke helper is running, the helper releases the sim's disengage latch for you, so the AP key works again without a second AP DISC press.
Navigraph charts
Navigraph's own G1000 plugin shows charts on the MFD. The mod does not include charts and does not replace that plugin. It repairs one thing in it.
What it does. The Navigraph plugin has a Full SCN softkey in its chart options menu that does nothing. The mod gives it a function: the chart takes the whole MFD page and the airport and procedure list on the right is hidden, as on a Perspective+.
Requirements. Your own install of the Navigraph avionics plugin for the MSFS 2024 G1000 and a Navigraph subscription. Without the plugin the softkey does not exist and nothing else changes.
Turning it on and off.
- Open a chart on the MFD with the Navigraph plugin.
- Open the chart options softkeys and press Full SCN. The chart fills the page and refits to the width.
- Press Full SCN again to return to the normal layout. Switching the chart page back to the map also returns to normal.
Limits. The function was written against Navigraph plugin version 2.2.0. If a Navigraph update renames its parts, the softkey goes back to doing nothing. Nothing else is affected.
iPad and ForeFlight link
The iPad link (needs the Companion) connects ForeFlight on an iPad to the sim over your home Wi-Fi, the way a FlightStream does in the aircraft.
What it does.
- Flight plan to the G1000. You build a route in ForeFlight and send it. It appears on the MFD as a pending flight plan that you preview and activate.
- Moving map. ForeFlight shows the sim aircraft's position, track, speed and attitude as its own position.
Nothing goes from the G1000 back to ForeFlight.
Requirements.
- The SR20 Companion running on the sim PC.
- The iPad and the PC on the same home Wi-Fi or home network. Guest networks keep devices apart and do not work.
- ForeFlight on the iPad. For sending plans, the Shortcuts app, which is part of iPadOS.
- No account, no extra app, nothing to type.
One-time setup
Do this once on each iPad. It takes about a minute.
- On the PC, open the setup page: right-click the Companion's tray icon and choose iPad setup…, or use the
SR20 iPad setup shortcut in the Start menu, or open
http://127.0.0.1:47822/setupin a browser. The page is titled "Send flight plans from your iPad" and shows two QR codes. - On the iPad, open the Camera app and point it at code 1 (Add the Shortcut). Tap the link that appears, then tap Add Shortcut. This installs a Shortcut named Send to SR20.
- Point the Camera at code 2 (Connect it to this PC). Tap the link. A page titled "Connect this iPad" opens.
- Tap Connect. When the iPad asks, open it in Shortcuts and tap Allow.
- The iPad shows SR20 is set up.
Code 2 gives the Shortcut this PC's send address. If the PC's network address changes later, for example after a router change, scan code 2 again.
If the setup page cannot be opened because the Companion is not running, the browser shows "Start the SR20 Companion first". Start SR20Companion.exe, wait a few seconds and open the setup page again.
Sending a flight plan
- In ForeFlight, open your route and tap the share button, then Share FPL File.
- Tap Send to SR20. If it is not in the list, see the troubleshooting table.
- The iPad answers, for example:
-
Flight plan received: KSNA SLI KLGB. Press ENT on the MFD.-Flight plan received: KSNA SLI KLGB. It will appear on the MFD once the sim is running.
You can send a plan before the sim is started. It waits for up to an hour. A newer plan replaces one that has not been answered.
On the MFD
The pending-plan pop-up. A window titled 1 PENDING FLIGHT PLAN appears at the lower right of the MFD, with
the lines Press "ENT" to preview and Press "CLR" to ignore. If another window or menu is open on the MFD, the
pop-up waits until you close it.
| Key | Action |
|---|---|
| ENT or the Preview softkey | Opens the preview page |
| CLR or the Ignore softkey | Ignores the plan. It is gone: send it again if you want it. |
The preview page. The page is titled FPL - Preview Flight Plan. The map is on the left. On the right:
- Preview Flight Plan, the plan number
1, the plan name as origin / destination (for exampleKSNA / KLGB) and Pending. - The waypoints under the headings Origin, Enroute and Destination, with DTK and DIS. The ALT column is blank.
- A waypoint made as a user waypoint is marked
USER. A waypoint that could not be found is markedNOT FOUND. - If something was left out, a line such as
Not loaded: procedure fixes ... . Load procedures on PROC. - At the bottom, Store? or Activate?. Store? is grey.
| Key | Action |
|---|---|
| ENT, or the Activate softkey | Asks Activate Flight Plan? with OK or Cancel |
| FMS knob in the question | Moves between OK and Cancel |
| ENT in the question | Chooses the highlighted answer |
| CLR in the question | Cancels the question |
| Delete softkey | Asks Delete Flight Plan ...? OK removes the pending plan. |
| CLR on the page | Goes back to the page you were on. The pending plan is discarded. |
| Store softkey | Not available |
Activating.
- Wait for
Checking waypoints...to clear. - Press ENT (or Activate), then ENT on OK.
Activating...shows briefly. The plan becomes the active flight plan and the MFD opens the flight plan page.
On the ground the first leg is active. In the air the leg nearest to the aircraft becomes active.
If the load fails.
| What you see | Meaning | What to do |
|---|---|---|
Cannot activate: not found: ... |
A waypoint is not in the G1000 database and the file gave no position for it | Fix the route in ForeFlight and send it again |
Not activated: an approach is active. Previous plan kept. |
You are airborne and flying an approach. Activation is refused. | Finish or leave the approach, then press ENT again |
Not activated: ... . Previous plan kept. |
A step of building the plan failed. Your previous flight plan has been put back. | Press ENT to try again, or CLR to leave |
Pop-up FLIGHT PLAN NOT READ with a reason and Press "CLR" to dismiss |
A file in the Downloads folder could not be read as a flight plan | Press CLR. Share the plan again from ForeFlight. |
What a route can contain
The link carries the enroute route: airports, VORs, NDBs, intersections and user waypoints, at least two points.
- Each waypoint is looked up in the G1000 database by name and type. The one nearest to ForeFlight's position for it is used, if it is within 2 NM.
- A point the database does not have becomes a user waypoint at ForeFlight's position. If you already have a user waypoint of that name, the new one gets a number on the end.
Not carried:
| Item | What happens |
|---|---|
| Approaches, departures and arrivals | ForeFlight writes them fix by fix. Those fixes, runway points and hold points are left out, and the preview page says which. Load procedures on the PROC page, as in the aircraft. |
| Airways | ForeFlight's file has the waypoints only |
| Altitudes | Not loaded |
Moving map on ForeFlight
Turning it on. Nothing to do on the PC. Open ForeFlight on the iPad while the sim is running. The Companion hears ForeFlight on the network and sends it the sim's position. In ForeFlight it appears under More > Devices as SR20 Sim. If the device has an Enabled switch, turn it on once.
Good to know.
- ForeFlight has to be in the foreground now and then for the PC to hear it. The PC keeps sending to an iPad for 10 minutes after it last heard it.
- When the GPS is failed on the Instructor Station, no position is sent, as in the aircraft.
- The setup page's Status section shows "ForeFlight's moving map is getting the sim's position" with the iPad's address when it is working.
Turning it off. Create the file %LOCALAPPDATA%\SR20Companion\data\efb\efb.json containing {"map": false}
and restart the Companion (tray icon > Restart all).
Forgetting iPads and new codes
- Lost or sold an iPad. On the setup page, under More, click Disconnect all iPads, then click again when the button reads "Click again to disconnect all iPads". Every iPad then needs code 2 scanned again before it can send.
- Code for the Safari page. The code under "Send without the Shortcut (Safari)" works for 30 minutes. The page says how many minutes are left. Make a new one replaces it at once.
- Codes 1 and 2 do not expire. Code 2 changes after Disconnect all iPads.
Sending without the Shortcut
Two other routes work.
Safari upload page.
- On the setup page, open More > Send without the Shortcut (Safari).
- Point the iPad's Camera at the small code and open the page. It is titled "Send to SR20" and shows
Ready. - In ForeFlight: Share FPL File > Save to Files.
- On the page, choose that file and tap Send.
The Downloads folder. The Companion watches the PC's Downloads folder for files named ForeFlight*.fpl. Any way
of getting ForeFlight's shared file into that folder works: a cloud drive, a file-sharing tool, email. A new file is
picked up within a few seconds and offered on the MFD like a sent plan.
Windows firewall
The iPad link is the only part of the mod that listens on your home network. It uses TCP port 47823 for flight plans and UDP port 63093 to hear ForeFlight for the moving map. It answers only devices with home-network addresses.
The Windows prompt. The first time the Companion runs, Windows may ask "Allow public and private networks to access this app?". Click Show more, leave only Private networks ticked (untick Public), then Allow.
The setup page's firewall check. The Windows firewall section of the setup page checks the network type and the firewall rules and shows one of these:
| Message | What to do |
|---|---|
OK: Windows lets the SR20 Companion receive on your home network. |
Nothing |
Windows hasn't been told to allow the SR20 Companion yet. If your iPad can't connect, use the button below. |
Click the button if the iPad cannot connect |
A Windows Firewall rule is blocking the SR20 Companion. Use the button below to allow it on your home network only. |
Click the button |
Windows treats this network ("name") as a Public network, which blocks the iPad. To fix it: Windows Settings > Network & internet > open this network > choose Private network. |
Change the network to Private in Windows Settings |
This PC is on a work (Domain) network. Ask whoever manages it to allow the SR20 Companion. |
Ask your network administrator |
Couldn't read the firewall. or Could not read the firewall. |
If the iPad cannot connect, use the button |
The one-click fix. The button Let the SR20 Companion receive on my home network shows while Windows has no rule or a blocking rule. Click it and answer the Windows administrator prompt. It adds two inbound rules for the Companion, for Private networks and your local subnet only: "SR20 Companion - iPad flight plans (TCP 47823)" and "SR20 Companion - ForeFlight discovery (UDP 63093)". The page then reports:
| Result | Meaning |
|---|---|
Done: the SR20 Companion may now receive from your home network. |
Fixed |
Not changed (the Windows prompt was cancelled). |
You cancelled the administrator prompt |
Windows refused one of the rules. Try again, or allow it in Windows Security. |
A rule could not be added |
Troubleshooting
The setup page's Status section.
| Line | Meaning |
|---|---|
Ready to receive flight plans from your iPad. |
The network listener is running |
Can't receive flight plans: ... . Restart the SR20 Companion. |
The listener did not start. The reason is in the line. Tray icon > Restart all. |
Last flight plan received at 3:42 PM: KSNA SLI KLGB. |
The last plan an iPad sent |
No flight plan received yet. |
Nothing has arrived since the Companion started |
The sim is running and the MFD is ready. |
The MFD is asking for plans |
The sim isn't running. Plans you send will wait and pop up once it is. |
Start the sim and load the SR20 |
This PC isn't on a network. Connect it to your home Wi-Fi or router, then reload this page. |
Shown in place of code 2 |
Something went wrong. Restart the SR20 Companion, then reload this page. |
Shown in place of code 2 |
Messages on the iPad.
| Message | Meaning and fix |
|---|---|
The request timed out |
The iPad cannot reach the PC. Check that the Companion is running and that both are on the same Wi-Fi. If you changed routers, the PC may have a new address: scan code 2 again. Check the firewall section. |
This iPad isn't connected to this PC. On the PC, open SR20 iPad setup and scan code 2 again. |
The iPad's send address is not known to this PC, for example after Disconnect all iPads. Scan code 2 again. |
That code has expired. On the PC, reload SR20 iPad setup and scan the new code. |
The Safari page's code is older than 30 minutes |
Not set up yet: on the PC, open SR20 iPad setup and point this iPad's camera at the code. |
The Safari upload page was opened without its code |
This link is incomplete. Scan code 2 on the PC's SR20 iPad setup page again. |
The Connect page was opened without its key |
That file couldn't be read as a flight plan (...). |
The file is not a ForeFlight FPL file, or the route has fewer than two usable points. The reason is in the brackets. |
That file is too large to be a flight plan. |
Send the FPL file, not another document |
Only devices on your home network can send to the SR20. |
The request came from an address outside your home network |
Use the PC's address, as the setup page shows it. |
The page was opened by a name. Use the code on the setup page. |
Too many tries. Wait n seconds and try again. |
Several wrong codes or addresses in a row from this iPad. Wait, then scan code 2 again. |
This PC couldn't save the setup. Try again; if it keeps failing, restart the SR20 Companion. |
The PC could not write its pairing file |
Choose the flight plan file first. / Not sent: ... |
Safari upload page: no file chosen, or the upload failed |
Other problems.
| Problem | Fix |
|---|---|
| Send to SR20 is not in ForeFlight's share list | Scroll the list of apps to the end, tap More, and turn on Send to SR20. Or scan code 1 again. |
| Nothing pops up on the MFD | The plan waits until the sim is running. If a window or menu is open on the MFD, the pop-up appears when you close it. |
| The setup page lists other network addresses | The PC has more than one network (VPN, virtual networks). The codes use the first home-network address. The iPad must be on that network. |
Differences from the real aircraft / limits.
- There is no flight plan catalog. Store is not available, and an ignored or deleted plan is gone.
- There is no Connext annunciation on the MFD.
- Flight plans go from the iPad to the panel only.
- Works with ForeFlight. The mod is not affiliated with ForeFlight or Garmin.
RealSimGear Cirrus yoke force feel
The yoke force feel (needs the Companion and the RealSimGear Cirrus yoke) drives the motorised yoke from the sim so that it behaves like the side yoke in the aircraft.
What it does.
| Function | What you feel |
|---|---|
| Trim-following centring | The yoke's spring centre moves with the aircraft's pitch and roll trim. When you trim, the yoke moves to the trimmed position and stays there hands-off. |
| Feel with the autopilot | Loose springs when you fly by hand. Stiff springs while the autopilot is engaged, like servos holding the controls. |
| Override break-out | With the autopilot on, push or roll the yoke past the break-out point and hold it there for a moment. The autopilot disconnects, the yoke goes loose, and your input is blended in over about one second so the aircraft does not jump. |
| ESP push | When ESP is correcting bank, pitch or speed, the yoke's centre moves in the direction of the correction and the springs go stiff, so you feel it pushing back toward the normal envelope. The push builds up and lets go gradually. The stiff feel stays for 3 seconds after the push ends. |
| Motor temperature watch | The Companion reads the yoke motor's temperature and writes it to its log, with a note when the motor is warm (50 °C) and when it reaches the range where the yoke's own firmware reduces force (60 to 70 °C). |
| Freeze detection | If the yoke stops responding for 6 seconds, the Companion pauses the sim when you are airborne, shows a warning window, and keeps trying to wake the yoke. |
The override break-out in detail
- While the autopilot is engaged, your pitch and roll inputs do not move the control surfaces. The autopilot has them.
- The break-out point is 45 % of the yoke's travel from centre, in pitch or in roll, held for 0.3 seconds.
- The break-out arms once the yoke has been near centre for a moment after the autopilot engaged. If you engage the autopilot while holding a large deflection, relax the yoke first.
- A break-out counts as a manual disconnect: yellow flashing
APfor 5 seconds. See Autopilot disconnect.
If the yoke freezes
The warning window is titled "SR20 yoke helper" and reads: "The RealSimGear yoke has stopped responding (its firmware went silent)." When you were airborne it adds "The sim has been PAUSED."
- Wait about 30 seconds. The Companion reopens the yoke's port every few seconds, which often wakes it.
- If the controls do not come back, power-cycle the yoke: unplug its power or USB for a few seconds.
- Unpause the sim.
Turning it on and off
In the installer. The component RealSimGear Cirrus yoke force feel (only matters with that yoke) is ticked by default under the SR20 Companion. Untick it to install without the force feel.
Afterwards.
- Open or create the file
%LOCALAPPDATA%\SR20Companion\settings.json. - To turn the force feel off, it must contain
"yoke_feel": false. For example:{"yoke_feel": false}. To turn it on, change the value totrue. If the file has other entries, keep them. - Restart the Companion: tray icon > Quit SR20 Companion, then start it again.
Running the installer again and changing the component does the same.
Checking the state. Right-click the Companion's tray icon. The line RealSimGear yoke feel shows a tick when it is working, "(no yoke connected)" when the yoke is not found, "(starting)" while it starts, and "(off)" when you turned it off.
Start order matters. The Companion has to take the yoke's connection before the sim starts the RealSimGear Device Interface. Leave Start with Windows ticked in the tray menu, or start the Companion before the sim. If the sim was started first, quit the sim, check the tray line, and start the sim again. Your other RealSimGear panels keep working through RealSimGear's own software.
When the Companion stops. On Quit, or when the sim is not running, the yoke is left loose with its centre held where it was.
Adjusting the feel. The spring settings are in %LOCALAPPDATA%\SR20Companion\data\yoke_feel.json: a force
preset (1 to 3) and two spring scalings (0.8 to 1.5) for loose and for stiff. The file is read again whenever it
changes, so no restart is needed. As shipped, loose is preset 1 with 0.8 / 0.8 and stiff is preset 3 with 1.2 / 1.5.
If you do not have this yoke
- The force feel does nothing without the yoke. The tray line reads "RealSimGear yoke feel (no yoke connected)" and the tray icon stays green. You can leave the option on or turn it off.
- The override break-out is part of the aircraft, not of the Companion, so it works with any yoke or joystick. With the autopilot engaged, your pitch and roll inputs are held back, and holding the control past 45 % of its travel for 0.3 seconds disconnects the autopilot. To override the autopilot on purpose, do that, or press AP DISC.
- A controller that does not rest near its centre can therefore disconnect the autopilot by itself. Check its
calibration and dead zone if the autopilot drops out with a yellow flashing
APand you did not touch anything.
Differences from the real aircraft / limits.
- The forces are tuned by feel against a real SR20 G6. They are not measured values.
- The yoke has no stall shaker in the mod. The SR20 has a stall horn.
- ESP itself, with its limits and settings, is described in Terrain, surface and protection systems.
Quick reference
| Control | Where | What it does |
|---|---|---|
| TO/GA in the air | Cockpit TO/GA button or your binding | Go-around mode, 7° nose up, wings level. Autopilot stays on. Activates the missed approach. |
| NAV after TO/GA | Autopilot controller | One press engages GPS to fly the missed approach |
| LVL | Autopilot controller | Autopilot on, level laterally and vertically, armed modes cleared |
| Direct-To | PFD / MFD / keypad | Straight great-circle line from present position |
| PROC > Activate Missed Approach | PFD / MFD | Selectable at or past the FAF with GPS as nav source |
| PROC > approach > Load? | PFD / MFD | Offered with an empty or Direct-To-only plan |
| HDG knob push | Autopilot controller / PFD | In a coupled NAV or approach mode: heading bug follows the heading until pushed again or turned |
| ALT SEL knob or VNV key near top of descent | Autopilot controller | Acknowledges the VPTH descent when in ALT (within 5 minutes of TOD; VPTH flashes from 1 minute) |
| Navigation status box | Top of the PFD | Turn, Next DTK, hold entry, arriving and TOD / BOD / TOC / BOC messages |
| Selected Altitude | PFD | Chime within 200 ft; "Altitude" voice more than 200 ft off after capture |
| Minimums by keypad | PFD TMR/REF, MFD PROC page | Typed value takes effect on ENT or when leaving the field, rounded to 10 ft |
| HOME | MFD keypad | Always opens the Navigation Map |
| Stabilized Approach annunciation | PFD, right of the altitude tape | COURSE, GLIDEPATH, GLIDESLOPE, FLAPS, TAILWIND, CROSSWIND, BARO, each with a voice |
| AP DISC | Your binding | Manual disconnect (yellow AP, 5 s). Acknowledges an automatic disconnect (red and white AP). |
| Pitch trim switch (MEPT) | Your trim up / down binding | Disconnects the autopilot. Acknowledges an automatic disconnect. |
| Full SCN | MFD, Navigraph chart options softkeys | Chart full screen on and off (needs the Navigraph plugin) |
| iPad setup… | Companion tray icon, or http://127.0.0.1:47822/setup |
Setup page: QR codes 1 and 2, status, firewall check and fix, Disconnect all iPads |
| Share FPL File > Send to SR20 | ForeFlight on the iPad | Sends the route to the MFD |
| 1 PENDING FLIGHT PLAN pop-up | MFD, lower right | ENT / Preview to preview, CLR / Ignore to ignore |
| FPL - Preview Flight Plan page | MFD | ENT / Activate then OK to activate, Delete to delete, CLR to leave |
ForeFlight*.fpl in Downloads |
PC | Offered on the MFD like a sent plan |
| RealSimGear yoke feel line | Companion tray menu | Status of the yoke force feel |
"yoke_feel": false |
%LOCALAPPDATA%\SR20Companion\settings.json |
Turns the yoke force feel off (restart the Companion) |
| Yoke past 45 % travel for 0.3 s with the autopilot on | Yoke or joystick | Override break-out: autopilot disconnects |