Altitude and the Aerocruze 100 (TruTrak) Autopilot

SoCal 182 Driver

SoCal 182 Driver

Cleared for Takeoff
Joined
Sep 11, 2019
Messages
1,053
Display Name
Display name:
SoCal 182 Driver
This probably an Avidyne IFD 540 and/or TruTrak (Aerocruze 100) question.

Let's say I'm 20 miles from an initial approach fix (IAF), and that the altitude I need to be at is 4,000 at the IAF. I'm flying the magenta line to the IAF with GPSS. My current altitude is 10,000. Is there a way I can program either the IFD 540 or the Aerocruze 100 to automatically start a descent so that I am at 4,000 at or before the IAF? I understand I can manually take the AP out of altitude hold and start a descent, but I'm wondering if there's a way to have the AP or the IFD do it without me having to intervene (other than to do some initial set-up/programing).

Thanks!
 
Sure sounds like something the manual would be able to answer
 
That’s called VNAV, definitely possible with GFC 500 and GTNs, don’t know about IFD and TT.
 
eman1200 said:
I think a manual tells you what it CAN DO. If it’s not in the manual or u don’t have some kind of VNAV equivalent button, then it prob doesn’t do it.
Click to expand...

You are likely correct, but I was hoping some smart pilot would have figured it out...if it was somehow possible.
 
I've never flown with a IFD 540 - but what you're basically asking for is VNAV guidance to a custom crossing restriction. FWIW, I've only seen capability like that with airline FMS systems, Airbus being the most intuitive at it IMO.

If the IFD 540 is anything like the Garmin's it copied, it will let you program in a descent timer that will do some maths for you. However, AFAIK, it does not cause the Vnav needle to come-alive and guide you. It is way more work than doing it in your head and I've never seen anyone use it in the real world.

AFAIK, on most of this GA stuff, the only time the VNAV needle is going to come-alive and provide vertical guidance is if you are on the published portion of an appropriate approach that has been loaded/activated.
 
Last edited:
jesse said:
've never flown with a IFD 540 - but what you're basically asking for is VNAV guidance to a custom crossing restriction. FWIW, I've only seen capability like that with airline FMS systems, Airbus being the most intuitive at it IMO.
Click to expand...
Can do that with a Garmin GTN6/750 no problem at all. With a GFC500 or similar, it will fly the vertical with no pilot input once the crossing restriction is put in and VNAV is active.
 
Search for "Enroute Descents" in the manual, think that's the Avidyne term for it. From what I read, it's a bit behind the Garmin VNAV, more like the VCALC it had previously.
 
Hang 4 said:
Can do that with a Garmin GTN6/750 no problem at all. With a GFC500 or similar, it will fly the vertical with no pilot input once the crossing restriction is put in and VNAV is active.
Click to expand...
Good to know. I've had a lot more time behind the 430/530 series.
 
Yes, I know this is old, but the latest Avidyne firmware update gives us enroute VNAV.

The autopilot will fly an Enroute VNAV profile when all of the following are true:
• The Aerocruze is in GPSS Mode and ALT HOLD or VS 0 mode
• The upcoming IFD540 FMS waypoint contains an altitude
• The IFD540 is configured (in its settings) to allow Enroute VNAV
 
SoCal 182 Driver said:
Which version?

I've been holding off updating because of all the reports of bugs. Has Avidyne worked the bugs out?
Click to expand...

The 10.3 update enabled Enroute VNAV, but you are right. The initial release, 10.3.0.2 had a bug or two, and 10.3.1.2 fixed them within a couple of weeks, and has been solid at least for me for a year. Here's the Applicable-to-Enroute-VNAV release notes:

Release 10.3.1.2 is primarily a bug fix release for 10.3.0.2. Here are the release notes:

- Fixed issue regarding VHF frequencies not persisting across power cycles
- Fixed issue with secondary standby frequency selection timing out after 20 seconds, reverting back to the #1 standby
- Fixed issue that caused an IFD reset when RF legs are disabled, an approach is selected in the dropdown, and every enroute transition to that approach contains an RF leg
- Fixed issue that caused visual approach extended runway centerline to not be displayed on devices driven by GAMA 429 (e.g. EX5000, Aspen)
- Fixed Exit Hold button so that it will appear when a hold immediately precedes an arrival or approach starting at the hold fix
- Fixed issue that caused VSR to not be computed when the next altitude constraint is on a leg that is part of a departure
- Fixed issue where the IFD outputs the selected altitude label even if enroute VNAV is disabled. With this fix, disabling enroute VNAV will prevent the IFD from overriding the selected altitude on some autopilots (e.g. TruTrak).
- Fixed enroute VNAV deviation scaling issues for display on a G5 (see SIL 606-00192-000).
- Fixed issue that caused Direct-to entry to be cancelled when using keyboard convenience mode.
- Fixed issue that caused some IFDs with multi-engines enabled to continue to show fuel flow / quantity in single engine format


10.3.0.2 Release Notes:

This is a huge release, so I've tried to categorize the changes. The changes that have a * next to them were driven by customer input through either in-person suggestion, AvidyneLive, or the Avidyne Pilot's Club Facebook group. Thanks for the help and keep the suggestions coming!

FMS
- Add support for non-AR procedures containing RF legs *
- Add visual approaches *
- Add support for oceanic navigation mode
- Add Enroute VNAV *
- Add aural alert for waypoint passage *
- Add ability to set OBS on IFDs without a radio
- Add OBS selected course digital readout
- Allow window constraints to be edited *
- Fix virtual keyboard display when editing user waypoints
- Allow uploading/downloading user waypoints from/to CSV file (via Mx Mode) *
Click to expand...
 
You must log in or register to reply here.
Back
Top