Big WT G1000 NXi Update

[Bunchy 222]

On 9/3/2021 at 8:15 AM, Alvega said:

It's working ok here.

 

 

I believe that's what they said will happen.

I can confirm this as well. I have to set departure and arrival airports in the world map screen and then I can enter the flightplan manually in the NXI

Other mods installed are FBW A20 Experimental and CJ4 12.7

[JRBarrett 3,034]

2 hours ago, Bunchy said:

I can confirm this as well. I have to set departure and arrival airports in the world map screen and then I can enter the flightplan manually in the NXI

Other mods installed are FBW A20 Experimental and CJ4 12.7

You have to set the departure airport in the world map with any MSFS aircraft in order to spawn at a particular airport, but I never enter the destination airport on the map and have no problem entering a full manual flight plan in the NXi

[JSmith2112 317]

2 hours ago, Bunchy said:

I can confirm this as well. I have to set departure and arrival airports in the world map screen and then I can enter the flightplan manually in the NXI

Other mods installed are FBW A20 Experimental and CJ4 12.7

Same here. I also have those mods installed.

[Alvega 2,119]

4 hours ago, Bunchy said:

I can confirm this as well. I have to set departure and arrival airports in the world map screen and then I can enter the flightplan manually in the NXI

Other mods installed are FBW A20 Experimental and CJ4 12.7

You don't have to set an arrival airport in the world screen map to be able to enter a flight plan manually on the NXi, like @JRBarrett said. I usually just set the departure airport so I can spawn there.

[ark 1,288]

On 9/5/2021 at 12:43 PM, cwburnett said:

then once armed it will 100% activate when you meet the activation criteria - be less than half scale deflection on the CDI and be on an intercept (converging) track to the magenta line.

Once activated, what is the criteria for deactivation and dropping back to arm mode -- perhaps CDI full scale deflection, or a set cross-track error? 

My understanding is the GPS CDI sensitivity may increase depending if the aircraft is enroute, in a terminal area, or on approach (2NM, 1NM and 1/3NM full scale, respectively). If that is generally true (I don't know if it is), then the half full scale course capture criteria represents different off-course NM distances depending on which phase of the flight plan the a/c is in.

If when using the G1000NXi this 1/2 full scale CDI deviation capture criteria also applies to VHF nav signals, then to capture a VOR course you need to be within 5 degrees, and within 1.25 degrees for the Localizer. And the capture criteria in NM varies depending on how far you are from the Navaid since the capture criteria is angular. 

Thx,

Al

 

Edited September 6, 2021 by ark

[Bunchy 222]

6 hours ago, JRBarrett said:

You have to set the departure airport in the world map with any MSFS aircraft in order to spawn at a particular airport, but I never enter the destination airport on the map and have no problem entering a full manual flight plan in the NXi

That's what I originally did.

I set EGBO parking ramp 39 in the world map. I was going to manually plan a flight to Southamptom EGHI. When in the cockpit (Baron) I hit the FLP button but I could not set any data in the departure field (and it was not already populated)

I had to go back to world map and enter EGBO ramp 39 again in departure and EGHI in arrival. I could then fill in the flightplan in the NXI.

Stu

[fppilot 4,336]

18 hours ago, JHaas said:

My Honeycomb Bravo autopilot functionality is inoperable even with this hotfix  after the latest release.

I just completed a flight and my Honeycomb Bravo and the NXi did not present any issues.  I had full functionality of the AP functions of the Bravo.

[fppilot 4,336]

Is it possible that working with the NXi FD and with some of the AP functions prior to taking off might be affecting entries in the logbook?  I completed two flights today and both were logged as 0 zero hours.  Since I removed and then reinstalled MSFS after SU5 and the resulting hotfixes, I have now completed twelve different flights, starting all of them from the runway instead of cold and dark in order to get them logged.  The first ten flights logged accurately.  The two today did not.  I started the flights already running on the runway.  My only difference was working in the NXi before takeoff.  Activating FD, setting up a climb or pitch rate, etc. Wondering if those steps might interfere like what happens when starting cold and dark.

I routinely for all my flights set up an initial target altitude and preset the runway HDG, so those two elements should be no factor.  But turning on the FD and presetting a pitch or climb rate was a new step for me.  Just wondering why the flights did not log like they should. 

I am well aware of inherent issues with the logbook, but I also with the help of others learned what to do and not do in order for the logbook to work.  So ten in a row good, and then today's two not.  And steps in the NXi are the only difference I can cite.

Edited September 6, 2021 by fppilot

[dga711 95]

1 hour ago, Bunchy said:

I set EGBO parking ramp 39 in the world map. I was going to manually plan a flight to Southamptom EGHI. When in the cockpit (Baron) I hit the FLP button but I could not set any data in the departure field (and it was not already populated)

Make sure that you highlight the blank "_____" line below the header and then turn the inner FMS knob. Not the ORIGIN header itself.

[JHaas 27]

15 hours ago, cwburnett said:

Can you share how you have your bravo configured? That would help us track it down and fix it. Thanks!

Ok I have spent a bunch of time testing things. I have only used the default asobo/honeycomb key bindings for the autopilot portion of the Bravo. It turns out that there is a bug with a double binding for the VS button that was causing my problems. I had to delete the "set autopilot vs hold" key binding and now everything works fine. I really don't understand why this caused a problem with the new updated Nxi and not the original nor the old G1000. Clearly things weren't working correct before but I only used minimal functions and I had no problem setting a VS.  Out of this I have learned how to use and set the IAS mode so that is progress!

I hope the default bindings for the VS mode button on the Bravo get updated so new users of that hardware don't end up scratching their heads.

Thanks for all who responded.

[JSmith2112 317]

46 minutes ago, dga711 said:

Make sure that you highlight the blank "_____" line below the header and then turn the inner FMS knob. Not the ORIGIN header itself.

That did it, thanks.

[cwburnett 1,809]

3 hours ago, ark said:

Once activated, what is the criteria for deactivation and dropping back to arm mode -- perhaps CDI full scale deflection, or a set cross-track error? 

Once a lateral mode is active (tracking) it will continue to do so unless there is no longer signal/data. For VOR/LOC, that means that it will deactivate (and flash yellow) if the signal changes - this can happen if you go out of range, change the frequency, swap CDI sources. For GPS this is more rare, because it would require deleting the plan, except that the FMS will automatically create a direct to random your current to waypoint if you delete the plan to protect guidance, so it would be very rare to encounter this on GPS, unless you change CDI source.

3 hours ago, ark said:

My understanding is the GPS CDI sensitivity may increase depending if the aircraft is enroute, in a terminal area, or on approach (2NM, 1NM and 1/3NM full scale, respectively). If that is generally true (I don't know if it is), then the half full scale course capture criteria represents different off-course NM distances depending on which phase of the flight plan the a/c is in.

This is correct. Just like with a VOR or LOC signal, the increased sensitivity as we get into TERM or LPV sensitivity means that the closer you are to the target, the more sensitive and the less true XTK is permitted for activation.

3 hours ago, ark said:

If when using the G1000NXi this 1/2 full scale CDI deviation capture criteria also applies to VHF nav signals, then to capture a VOR course you need to be within 5 degrees, and within 1.25 degrees for the Localizer. And the capture criteria in NM varies depending on how far you are from the Navaid since the capture criteria is angular. 

Correct. A LOC signal is generally 5 degrees wide, so the inner 2.5 degrees represents, roughly, the capture range - 1.25 degrees on either side of the LOC course. For VOR, we used the most common 24 degree beam, so full scale deflection would be 12 degrees off course and half scale would represent about 6 degrees.

[cwburnett 1,809]

18 minutes ago, JHaas said:

It turns out that there is a bug with a double binding for the VS button that was causing my problems

Good catch, we can try to get this fixed in one of the upcoming sim updates.

[cwburnett 1,809]

For those of you having trouble setting airports/vfr runways, remember you need to highlight the row below the header for origin/destination, not the header itself. So highlight the empty row below origin, then turn the inner knob to the right to start entering your origin airport ident.

[Matchstick 1,876]

1 hour ago, fppilot said:

I just completed a flight and my Honeycomb Bravo and the NXi did not present any issues.  I had full functionality of the AP functions of the Bravo.

Are lights for NAV and APR mode working correctly on the Bravo with the new NXi ? the changes to the LVARs seem to have really complicated working out what vertical mode is armed and/or active