"John R. Copeland" wrote in message =
...
"Ron Rosenfeld" wrote in message =
...
=20
=20
Perhaps something has changed since that document was written; or =
perhaps
there's a glitch in your wiring.
=20
--ron

Ron, I no longer have newsletter 5, but I can't fault the newsletter =
announcing=20
availability of the version 2 upgrade, because the new NAV display in =
the
CNX-80 performs as the attachment to that newsletter described.
For LNAV approaches, I have not found where that attachment promised
glide-path guidance on an external indicator, only on the internal NAV =
display.

The undocumented part concerns the drive to the external VDI in my =
flight director.
Wiring can't be faulty, because it works flawlessly on ILS and VNAV =
approaches.
My avionics installer promised today to inquire about that with his =
factory rep.
If I get clarification, I'll share it here.
---JRC---

So here's the clarification as it's been relayed to me.
As I speculated earlier, the external VDI is purposely not driven unless =
VNAV
minima are published for the approach, and the reason is exactly to =
prevent
coupling the autopilot to the computed glide slope on LNAV-only =
approaches.

This affects only the external VDI.
The NAV display page in the CNX-80 remains useful for stabilized =
descent,
but only under manual control, not by the autopilot.

In addition, there has been at least one malfunction report of an =
external
VDI presentation anomaly at the published DH in a coupled approach.
I do not yet know any details about what happened at DH in that report,
so be careful out there, y'all hear?
---JRC---