Gring,
Thank you for responding. This unit is new to me, and I'm actually waiting for my hard copy Pilot manual to come in the mail - I've been reading the CD version at home and playing with the unit at the airport. I am by far not an expert and will confess that my ignorance of its operation may be a contributor!
So, a couple of things going on here.
1) I assume you know that you can designate a user waypoint as an airport so you can name your grass strips not in the database and have them act in similar fashion as an airport in the database. Page 2-36 of the user's guide spells out how to accomplish this.
I did not know this. I will review the user guide and make sure that I use this feature. Cool!
2) You can set up a vertical constraint on any of the waypoints and you do this in the FMS by using the small knob to move the cursor to the bottom row of the waypoint and entering the appropriate information ie distance from the waypoint, crossing type (at or below, at, at or above) and the altitude. If you do not set the altitude, it defaults to 1000ft above the airport elevation from the database. I have not tried this from a user defined airport waypoint, so I'm not sure if this holds true for that specific type, but you can certainly define the crossing information. Page 2-11 of the user's guide spells out this function.
I have read the book on the VNAV, page 2-11 but I can't get it to work as described. Yesterday, for example, I flew direct to KELM. This is an airport, not a waypoint, which according to 2-11, I should be able to add a vertical constraint. However, when I selected the waypoint (KELM) it would only allow me to select an approach - not to add a vertical constraint. I did not see a TOD in the map page for a descent to 1000 above the airport either. I was able to set a vertical constraint for another waypoint, but it didn't populate the VSR. I guess I don't recall seeing a TOD on the map page for that waypoint constraint either, but will look more closely.
3) If your setup does not have a baro input (basically an EFIS of some sort or Air Data Computer), then the current release of the software 10.0.2.0 will not update the VNAV datablock and display the vertical speed required (VSR) like you are use to. If you have an EFIS (Aspen/G500/600, etc.) it will populate the VSR block
I actually do have an Aspen PFD. So does that mean 10.0.2.0 will populate the VSR? I didn't see it in the release notes, but will look again. 4) However, on any or all airport waypoints that you have defined a constraint on, and the next waypoint on an approach that has been loaded, you will see on the MAP the TOD marker. Once reaching it, you will hear the "doorbell" chime if you have wired the IFD540 audio output and see the CAS message indicating you need to descend.
I do not have the audio feature yet, but it is getting added this week with the addition of the new software. My installation was a slide in 530W replacement, which didn't have this feature.
I have a standard 6 pack with no EFIS and use this feature all the time and while I would like to see the VSR datablock populated, it really hasn't been an issue. I do know the VSR function is a planned upgrade for a future release.
So basically, you're suggesting that if I set it up correctly, I should just have a TOD marker on the map (and a chime, when wired). I still have yet to see the TOD and will play with this feature more and watch for it. If it works for you, I imagine I am doing something wrong. I probably use the VSR more than anything as I'm not flying approaches all the time. And I'm actually a little leery of doing very many approaches until I get a few more hours behind it!
I hope this helps.
Thank you again for your help!
|