Just now, ark said:

Rob,

Tried the FP you posted with the DA-62 and G1000NXi mods, worked fine as far as I could tell.

Al

Hey Al, thanks for testing. Can you give me a high level step by step that you tested so I can confirm it is not user error? Because I set the altimeter and altitude (to 7000) then take off with AI pilot. Get in air, then switch off AI pilot, turn on AP, and then pretty much nothing else works. Just want to make sure I have the steps down. BTW, right now I use without my CH yoke which is why using AI pilot.

37 minutes ago, RobJC said:

Can you give me a high level step by step that you tested so I can confirm it is not user error?

Hi Rob,

I loaded your FP using the World map screen (which I usually don't do) and then checked it was correct in the G1000NXi. Took off in GPS mode (AP off),  climbed to 4000 or so, selected NAV on the AP (AP still off), turned left (as I recall ) until the G1000NXi CDI was active (started moving in), then turned on the AP and VS to capture the GPS course and complete the climb to 8000ft. From there the AP flew the FP, I just had to manage altitude changes in accordance with the approach plate. Once inside the AFOXY IAF I selected APR on the AP.

My guess is the major difference between what we each did is you using AI pilot, which I have never used (had to look up what it was). Might be worth trying without AI pilot if you have a way to do that.

Al

 

 

Edited September 27, 20214 yr by ark

24 minutes ago, ark said:

Hi Rob,

I loaded your FP using the World map screen (which I usually don't do) and then checked it was correct in the G1000NXi. Took off in GPS mode (AP off),  climbed to 4000 or so, selected NAV on the AP (AP still off), turned left (as I recall ) until the G1000NXi CDI was active (started moving in), then turned on the AP and VS to capture the GPS course and complete the climb to 8000ft. From there the AP flew the FP, I just had to manage altitude changes in accordance with the approach plate. Once inside the AFOXY IAF I selected APR on the AP.

My guess is the major difference between what we each did is you using AI pilot, which I have never used (had to look up what it was). Might be worth trying without AI pilot if you have a way to do that.

Al

Thanks Al. Let me test this again using your steps. Maybe the AI pilot is screwing everything up? 

Hotfix 0.7.1 for the NXi just came out. Fixes bug preventing automatic  transfer from VNV mode to GP approach mode in RNAV plans. Among other fixes.

 

Edited September 27, 20214 yr by Eclex

50 minutes ago, RobJC said:

Let me test this again using your steps. Maybe the AI pilot is screwing everything up?

After entering the FP, suggest you set a target altitude on top of the altitude tape, take off with the G1000NXi CDI in GPS mode, climb and turn towards the FP course, and when the CDI becomes active turn on NAV, VS  (the G1000NXi should capture your current VS), and turn on the AP. The G1000NXi should capture the FP course and level you off at the target altitude.

Al

21 hours ago, ark said:

What's interesting is, if once GPS Nav has captured, if you were to disconnect the AP and fly 10 or 20 miles directly off course (say to deviate around a storm), if you then re-engage the AP, it will fly you back to the original course or to the waypoint at the end of that course leg. So as always, the pilot is responsible to maintain a safe altitude.

Al

I suspect that is actually a bug..

Generally, ATC will instruct one to flt DTO a way point not a course line.

2 minutes ago, Bert Pieke said:

I suspect that is actually a bug..

It's not, this has been demonstrated a few times in the trainer. Once GPS is tracking it will keep tracking no matter what your XTK is.

24 minutes ago, cwburnett said:

It's not, this has been demonstrated a few times in the trainer. Once GPS is tracking it will keep tracking no matter what your XTK is.

OK, I stand corrected.. 🙂

46 minutes ago, cwburnett said:

It's not, this has been demonstrated a few times in the trainer. Once GPS is tracking it will keep tracking no matter what your XTK is.

While I understand that is how it works, it is not obvious to me WHY it was designed to work that way. If you have to get within a specified distance to initially capture a GPS course, if you then deviate substantially outside that distance, why would it not make sense for the system to drop back from a GPS course captured to a GPS course armed state?

Al

Edited September 27, 20214 yr by ark

Quote

Working Title G1000NXi 0.7.1

Issues Resolved

Fixes bug with APR button press not sending the correct input value to the approachPressed method in AP with certain key events.

Fixes bug where in a climb the current altitude, and not the selected altitude, was displayed in the MFD FPL page for cruise advisory altitudes.

Fixes bug with GS/GP activation causing VNAV to set alt hold when VNAV remained on or armed.

Fixes bug with Vertical Deviation Indicator showing VNAV deviation even when GP is active.

Fixes bug where VNAV would not descend to a constraint if the next constraint was only 100 feet below the current constraint.

Fixes bug where VNAV would remain armed after the LOC autoswitch.

Fixes bug with Altitude Capture when capture is activated when level or near level

Fixes bug where after a missed approach from an ILS/LOC approach and resequencing to an RNAV approach for the same runway would incorrectly switch to LOC again.

Fixes calculation and display of vertical direct FPA and advisory altitudes when constraint is not the direct-to target, but is in the current constraint segment.

DA40NG system page now shows engine load gauge instead of manifold pressure.

Adjusted display of EGT gauge on DA40NG, SR22, G36 to show the EGT range better since these 3 aircraft strangely max out at 1200F compared to the normal 1600 of the other piston aircraft.

Fix DA62 aux tank display to show the level instead of the capacity.

Working Title G1000NXi 0.7.0

New Features

PFD

VSI shows correct Required VS for the active VNAV or LPV path data source, with correct source switching based on mode.

FMA correctly displays MANSEQ legs depicting the heading for the manual sequence.

Vertical Deviation window is displayed starting 1 minute prior to TOD whenever VNAV path is available.

Vertical deviation window displays whenever either a valid VNAV path or LPV GP path is available.

Timer/Ref Page now has a contextual page menu that allows v-speed depiction on the airspeed tape to be hidden or shown in bulk, along with adding a menu item to reset all VSpeeds.

Timer/Ref Page now correctly depicts a speed that has been changed from the airframe default with a (*).

Altimeter now correctly depicts the current VNAV constraint, rather than the VNAV target; this includes showing the last constraint, even after passing it, when it was an end-of-path and there’s not currently a valid VNAV path.

MFD

VNAV profile view enhancements:

Adds time to TOD/BOD (bod calculates against vnav target, not next constraint)

Displays next constraint (shows leg and altitude for next constraint, not BOD target)

Shows Required VS and Deviation only beginning 1 minute before TOD and thereafter.

Hides data when in VNAV suspended state prior to VNAV ineligible leg.

EIS system enhancements:

Adds support for the definition of additional System and Lean engine pages.

Adds default engine page configurations for every stock plane with a G1000.

Adds new EGT/CHT gauge type with configurable differences in cylinder temps.

Adds fully functional cylinder select and lean assist mode.

Adds fuel totalizer with realistic manual adjustments to fuel remaining.

FPL Pages

Hides DTK, DIS, and ALT data on waypoints behind the aircraft.

Properly shows heading for MANSEQ legs.

Adds advisory (white) and target (cyan) altitudes on MFD FPL pages.

Entire plan now drawn on MFD when FPL is selected.

Miscellaneous

VNAV now properly suspends when the last constraint prior to a VNAV ineligible leg. Examples include MANSEQ legs, proc turns and holds. VNAV will level at the prior constraint and deactivate until passing the ineligible leg, at which point the user may re-arm VNAV.

VNAV now attempts to calculate a valid path, up to 6 degrees, from the present position to the direct-to target when a direct to or activate approach is executed.

Traffic advisory mode now automatically switches with takeoff and landing.

Corrected and restored the option to invert the loaded flight plan.

Issues Resolved

Fixes incorrect display of direction in hold menu.

Fixes non-normalized bearings in the nearest airport list.

Fixes non-normalized bearings in the direct to menu.

Fixes problems with deletion of active leg on the ground.

Fixes distances not counting down when OBS is active.

Fixes disappearing cursor when deleting flight plan.

Fixes various display issues in scrolling selectors.

Fixes duplicate legs when selecting a different approach.

Fixes mismatched colors on some section titles.

Fixes a handful of EIS alignment/display issues.

Fixes bug displaying target altitude when direct to a VNAV constraint.

Fixes bug displaying active leg arrow when a direct to is complete.

Fixes bug causing incorrect coloring of PFD VDEV diamond.

Fixes bug displaying incorrect transition names in procedure selection.

Fixes issue with ‘or’ appearing in Select Approach even when an approach can’t load

Fixes issue with PFD FPL page showing a blank line when a DIRECT TO EXISTING was executed

Fixes issue with VNAV DIRECT FPA being constantly incorrectly calculated.

Fixes bugs with display of vertical deviation and required VS values.

Fixes bug with properly capturing the selected altitude when above the vnav target altitude.

Improves display of VSpeed values in menu and on tape.

Improves display of softkey gradients and borders.

Heads Up!

VNAV now deactivates upon reaching the last constraint (cyan altitude in FPL) prior to a VNAV ineligible leg, such as a MANSEQ, Procedure Turn or Hold. Be aware that if you have a MANSEQ leg at the end of your arrival procedure, without manual intervention, you can (and likely will) end up too high to reasonable descend for the approach. You have three options to navigate this: (1) Manually descend as is reasonable at your discretion; (2) delete the MANSEQ leg to allow VNAV to recalculate by directly connecting the end of the arrival with the beginning of the approach or (3) activate the approach (or proceed direct to the IAF) and VNAV will attempt to calculate a path up to 6 degrees from your current position to the next constraint.

GPS, LOC, and VOR modes now ARM! Be aware that you will need to be on an intercept course and within capture distance of the desired flight path before those modes will become active.

The GPS flight plan sequencing will enter SUSP under the following conditions: when reaching a manual termination leg (holds, manual sequence) and when reaching the final leg of the plan. This is actually correct behavior. To exit out of SUSP (for example, if you got to the end of a plan and then loaded more waypoints), hit the SUSP softkey in the middle of the PFD.

Changing the CDI source drops the autopilot into ROL mode. This is the correct behavior, intended to keep the airplane held in the same attitude until the pilot reselects appropriate guidance.

When exiting a hold, do not delete the HOLD as it will cause flight plan issues. Press the SUSP key to continue with the flight plan sequence or go direct to another fix.

The NXi’s traffic advisory system (TAS) will now start in STANDBY mode by default. While in this mode it will not issue any advisories nor will traffic be displayed on any maps. The system will automatically switch from STANDBY to OPERATING mode after takeoff (and back to STANDBY after landing). You can also manually switch TAS to OPERATING mode through the MFD Traffic Map page (use the MFD FMS knobs to change the open MFD page).

The fuel quantity information on the MFD’s sytem page simulates an authentic totalizer. This means it does not actually track the fuel in your tanks, it simply counts how much has been burned and relies on you to tell it what the original quantity was. This means if you add or remove fuel in flight you’ll need to manually adjust the starting quantity in the tanks with the buttons on the GAL REM submenu.

Known Issues

Outer large COM knob only reduces frequency no matter the direction the knob is turned. This is an issue with the cockpit panel behaviors in the sim and has been logged with the MSFS team, but will not be able to be addressed in the NXi package as it is an issue with the base planes.

Sometimes the flight plan loading from the world map screen is loaded incompletely; this can usually be solved by restarting the flight - we are working on nailing this down.

World Map imports from Navigraph and Simbrief do not include airways, so airways will not be added to the G1000 NXi flight plan when the plan was imported to the World Map from one of these sources.

External camera view HUD does not sync properly with the NXi and may show strange or incorrect data. We expect to be able to resolve this after Sim Update 6.

Hardware autopilot peripherals may display the selected altitude as 99000. If you can configure it, you must set the altitude to read from index/slot 1 instead of index/slot 0. If it is not possible to configure using the manufacturer software, you may be able to configure it using third party software such as AxisAndOhs, Mobiflight, or spad.next. We expect to be able to remove this workaround after Sim Update 6.

Autopilot Hardware

The autopilot has been completely overhauled with 0.5.0, which includes some workarounds for altitude capture until such time that the sim supports the disabling of it’s own capture. This includes setting the altitude slot to slot 3 and setting the selected altitude to 99000 so it will never be captured, and using slot 1 as it should be for the preselector.

For hardware controls that control the altitude preselector, they must be configured to read and write to altitude slot 1, not altitude slot 0 (which really just reads/writes to them all, and will override all the custom AP altitude selections). If it is not possible to configure your hardware in this way, you will unfortunately have to either remove the hardware or remove the NXi. The are also third party softwares like AxisAndOhs, Mobiflight, and spad.Next that can allow you to bridge this gap if the manufacturer default software cannot.

We expect this workaround will no longer be necessary after Sim Update 6.

 

2 hours ago, ark said:

Hi Rob,

I loaded your FP using the World map screen (which I usually don't do) and then checked it was correct in the G1000NXi. Took off in GPS mode (AP off),  climbed to 4000 or so, selected NAV on the AP (AP still off), turned left (as I recall ) until the G1000NXi CDI was active (started moving in), then turned on the AP and VS to capture the GPS course and complete the climb to 8000ft. From there the AP flew the FP, I just had to manage altitude changes in accordance with the approach plate. Once inside the AFOXY IAF I selected APR on the AP.

My guess is the major difference between what we each did is you using AI pilot, which I have never used (had to look up what it was). Might be worth trying without AI pilot if you have a way to do that.

Al

It worked Al! Thank you for the help! 

19 minutes ago, RobJC said:

It worked Al! Thank you for the help! 

Rob,

Glad to 'hear' that! I'm curious, did it work while still using AI Pilot, or did you not use that?

Al

Edited September 27, 20214 yr by ark

1 minute ago, ark said:

Rob,

Glad to 'hear' that! I'm curious, did it work while still using AI Pilot, or did you not use that?

Al

Retesting right now to confirm that. I have a few things i was checking at the same time. So now i am isolating the cause. Two perfect flights (Caravan and Baron) so now rechecking.

2 minutes ago, RobJC said:

Retesting right now to confirm that. I have a few things i was checking at the same time. So now i am isolating the cause. Two perfect flights (Caravan and Baron) so now rechecking.

OK, great.  If you can identify what the original problem was it would be good to pass the info on here in case others have a similar issue.

Al