TRU TRAK Vision 385 Garmin 430 GRT HXr

[Canadian_JOY]

Originally Posted by catmandu

I agree it would be nice to have the Vizion capture altitude right off the bat.

My current technique is to set the initial altitude in the EFIS and control initial rate of climb with the Vizion (typically 800fpm). 200 feet shy of your initial target altitude set in the EFIS, roll the rate of climb to zero on the Vizion. It then captures and holds the target altitude. After that, all changes can be made solely with the EFIS.

I think it's this last bit that makes me prefer flying with the EFIS/GPS switch in the GPS position. Setting altitude / climb rate through the autopilot's own buttons results in perfect altitude capture.

[Toobuilder]

The last few posts have me confused. The 430, GRT WS and Digiflight II I've been flying for years provided flawless altitude capture from the EFIS. Once the AP was engaged, all commands were from the legacy WS screen. Is the need to drive vertical guidance from the AP head a Vision 385 specific issue? Seems like a step back if so.

[davevon]

Originally Posted by Toobuilder

The last few posts have me confused. The 430, GRT WS and Digiflight II I've been flying for years provided flawless altitude capture from the EFIS. Once the AP was engaged, all commands were from the legacy WS screen. Is the need to drive vertical guidance from the AP head a Vision 385 specific issue? Seems like a step back if so.

Micheal, Does your Digiflight II have vertical steering? The one I had didn't. If I remember correctly it was an option.

My initial setup was the same as yours, my AP had altitude hold and vertical rate, but no altitude input or capture from the EFIS that I remember. At the time it was easier to just fly off the AP head with guidance from the non-WAAS 430.

The airplane has returned after 12 years and I've upgraded the AP to the TruTrak Vizion with altitude steering. All else is the same for the time being, upgrade coming soon. Now I use the EFIS to control the AP and I can vertically steer the AP through the EFIS, but only after it captures the altitude in level flight. Like in the other posts, if the AP is engaged during a climb I have to disengage at the programmed altitude, level off and re-engage the AP. Once vertically captured I can dial in altitudes or have it follow a synthetic approach.

I engage the AP by pushing the left "Mode" button. It comes up GPSS and the vertical side will display the vertical speed if engaged in a climb or VS if I'm level. At SnF I asked about not capturing the preset altitude and the guy at TT said you just push this and that and it works. Sounded easy and I should have wrote it down... I tried it and so many other combinations that I don't remember what the original one was.

I just checked and the AP does gather baro info from the EFIS. Although it takes more than a few seconds scroll to the new elevation. The EFIS preset altitude does not show up in the Sel Alt window. Maybe that is supposed to happen and that's why my AP isn't capturing the EFIS preset altitude from a climb engagement.

Regards,

Dave

[Bavafa]

Originally Posted by Toobuilder

The last few posts have me confused. The 430, GRT WS and Digiflight II I've been flying for years provided flawless altitude capture from the EFIS. Once the AP was engaged, all commands were from the legacy WS screen. Is the need to drive vertical guidance from the AP head a Vision 385 specific issue? Seems like a step back if so.

The same for me, though it was a 430, HX/HS and TT on GPSS mode. I always left the switch to the EIFS and the GPS was just in case my EIFS had died which was never the case. The altitude capture was always flawless and exact.

[catmandu]

From the Vizion Operating Manual, and why I use the procedure I do:

6.4.5. GPSV Mode (Vizion 385 ONLY)

The vertical GPS Steering mode or GPSV mode is engaged automatically with GPSS mode if the vertical steering signal is present. This mode is displayed with the addition of VS to the GPSS that appears in the lower left of the autopilot display bar. If the autopilot is engaged during a climb or descent, the vertical speed must be zeroed (see section 6.4.1) or ALT HOLD (see section 6.4.2) engaged to engage GPSV. The only exception is if the autopilot is engaged remotely from an EFIS.


I don't know how to engage the autopilot remotely from the HXr.

[Skid]

Originally Posted by catmandu

From the Vizion Operating Manual, and why I use the procedure I do:

6.4.5. GPSV Mode (Vizion 385 ONLY)

The vertical GPS Steering mode or GPSV mode is engaged automatically with GPSS mode if the vertical steering signal is present. This mode is displayed with the addition of VS to the GPSS that appears in the lower left of the autopilot display bar. If the autopilot is engaged during a climb or descent, the vertical speed must be zeroed (see section 6.4.1) or ALT HOLD (see section 6.4.2) engaged to engage GPSV. The only exception is if the autopilot is engaged remotely from an EFIS.


I don't know how to engage the autopilot remotely from the HXr.

Yep. That?s what it states, but it still stinks. Had I known that I likely would not have upgraded from my old A/P.
My process is: engage the A/P after T/O and let it climb to altitude, disengage it, level off and engage the A/P again, after that it works great.
I was told by GRT support there is no way to engage a TruTrak from the EFIS.

[Deweyclawson]

I put a GRT auto pilot in my RV6. Now have a 10 with a TT. The GRT servos will be here with the new GRT screens by Christmas. Replacing 3, 6in Hx asreens with 2 10in..