- Joined
- Feb 15, 2012
- Messages
- 9,567
- Reaction score
- 4,408
It a word, it is WONDERFUL. Maybe having waited as long as I have, has sweetened it more, but you don't have to wait for it now, it is one week shipping.
Hard to know where to start to try to describe it all.
First out with the old (430W & GTX330):
Then IN with the new, The Avidyne IFD540 GPS/COM and APX340 ADS-B transponder, here is the whole center stack:
This is a screen capture from the simulator, for a crisp view of the main screen.
The screen is a page and tab, plus side tab construct. The bottom buttons are rockers, you can move through tabs, or you can direct touch tabs on the screen. The side tabs can be slid out, or in, and some will pull out across the screen to fill it. (eg. Flight Plan tab) Either the bezel buttons, or the touchscreen can be used to access the button pushes. (eg. Wx Overlay)
With the Hybrid Touch interface, you can do most anything with either bezel controls or the touch interface. I kind of like holding onto the knobs and turning, but some functions the touchscreen makes more sense. Nice to be able to use both, everyone will have their preference.
You can have up to four preselect frequencies, here I've configured for three. In this config you toggle between COM & NAV frequencies with the bottom left knob. All frequencies, including active and the presets for both COM & NAV are auto-id.
On the above screen configuration there is a traffic thumbnail, and the separate land and nav feature declutter buttons. The 540 will also declutter on the basis of altitude. All of this is user configurable.
Both the right and left datablock areas you can populate with data fields as you like. In the 10.1 release the entire datablock area on the right will scroll up & down, letting you define and view a relatively unlimited number of fields. That is a key feature to help the smaller screened 440.
There is a terrain/obstacle height key in the top left of the map. This shows three values, the lowest terrain in the displayed map (within the outer range ring), the highest, and if higher, the highest obstacle height. The Min Safe Alt is different, it is the conventional grid square value, doesn't key to the range of the map.
The GPS AGL at the top, is a poor man's radar altimeter, gives the GPS height above the terrain database elevation for your current point.
You can select a North up, track up or heading up view, and there is also a 240 degree (partial arc) track up and heading up view. If you have a track up setting, then your own ship will cant as according to the winds, to show your crab angle. The next active leg is shown as a barber pole.
QWERTY, together with "geo-fill" auto filling of text fields, lets you zip through selections. Geo-fill will fill the rest of text entry fields with a logical entry, saving you keystrokes. Entering COM frequencies you can use 197 for 119.70, or for VORs you can use the VOR ID, for example YQO for 114.2. Incidentally, the IFD440 due out this Spring, the IFD540's smaller cousin (430 size) will also have a full QWERTY screen, and the same quick entry methods. In fact it will have everything the 540 has, feature-wise, except those things specific to a larger screen.
Building a route.
Of course you have full airway support, but with a really cool twist. As you build your route, you get a full dynamic display of the proposed route (auto-zoomed for you), with all the waypoints listed geographically, right on your main map page. As you select one of them, the map rezooms, and redraws the proposed route. When happy with the exit point, you select it again and all the waypoints are added.
The same method is used for adding a procedure, together with its transition. never need to wonder which transition goes where.
You can add any number of airports (duplicating them in a row as well) in your route, and an arrival and or approach for each. It is all reflected in one long flight strip. Handy when doing IFR practice approaches.
OK, back to the "real" in cockpit pics.
There is a bewildering number of data fields that you can add.
There are three custom configurations now, you can populate as you like. There will five more for the 10.1 release. In the following release, you will be able to set various screen configurations to auto-transition, depending on the phase of flight!! That is actually one of the suggestions I made to development team. The openness of Avidyne to customer interaction is remarkable, and it will result in a stronger product. They have public forums at http://forums.avidyne.com
I've pulled the scale way back here to show a very cool feature. The IFD gets airdata from the ASPEN, and fuel data from the EDM830. Here, based on current GS, fuel burn and capacity available it shows two range rings (red arrows), the dashed is distance to 45 min reserve, the solid is the distance to "empty".
The flight plan track is not really visible in this pic, because it is so short at this scale, it was just a local flight. But, YQO (Aylmer VOR) is the next waypoint. it auto-loads as the active frequency when its leg becomes active, and I've placed the VOR/LOC info datafield just below the freq. That gives your current bearing and distance, like having DME back.
I added waypoint datafields on the right, and you can see the expected fuel remaining at the next & final waypoints is also included here. I've also chosen to have the direct to destination distance (as the crow flies) shown.
Next is the Nav Mode, and below that an extremely powerful field, the VSR, the vertical speed required. What makes this so powerful is that you can define an altitude constraint relative to every waypoint in the flight plan. Even cooler, the IFD will populate the minimum altitudes for a approach automatically, showing this on the flight plan and on the screen, and the VSR field will reflect these. More in the pics below.
I also have our Jepp plate subscription installed, so you can toggle to the plates. These are geo-referenced, and the rectangles draw on the main map screen. They are a little small, but the pinch to zoom and flick interface lets you use them effectively. They also have a quick header, plan and minimums view selection.
OK, on the approach into my home airport, RNav 05.
You can see on the scrunched flight plan strip on the right I'm heading for OVUTU (IF/IAF), and there is a listed minimum altitude of 3000ft. That is also depicted on the map. There is no hold on this approach, I have added a custom hold at OVUTU, holding north. The IFD auto configures the entry with the least amount of turn, here you can see the parallel leg as a barber pole. I can delete this hold, or change it (leg length or time, and inbound course) by clicking on the descriptor in the flight plan strip. Bottom left is a DELETE HOLD button. Once you are in the hold, it changes to EXIT HOLD. Holds are done, just like the big boy's FMS.
You can also see the SEKIL waypoint, the FAF, with the FAF minimum right on the strip. When it become the active leg, the minimum is drawn on the map.
The IFD has another very cool safety feature. With an approach active, if you go below the FAF minimum, before reaching the FAF, it will show you a CAS (crew alerting system) caution notice - "check altitude, too low". Hope i never commit that, but if I did ...
OK, past the FAF, inbound.
I'm in track UP, 240* view. Note that the own ship image is canted to the left to represent my crabbing due to the crosswind.
Also note the green TOD marking, that is where you should start down. You get a nice Ding-Dong tone to remind you 10 secs before. The TOD is calculated for any segment (ascent, cruise or approach) where you have an altitude restriction ahead, and you reach your target required vertical ascent/descent rate. The default is 500 fpm, you can set it to whatever you like.
OK, approach into CYHM, a neighboring controlled airport, here on the LOC30 approach.
There is no vertical guidance on the LOC of course, but no worries, the VSR field shows you the current required VS to make the minimums at the MAP, making a constant descent approach real easy. You can dive and drive if you wish, but even then you can use that to ensure you are too late in your descent. To set that up all I had to do was - nothing. The numbers populate when you select the approach, you just fly it.
Note the oversized yellow obstacle indication. That is part of the Forward Looking Terrain Avoidance (FLTA) available in the base configuration of the IFD, normally you have to get full TAWS to see that, the IFDs include it in the base units.
For more on the FLTA feature, see this thread:
http://www.piperforum.com/showthread.php?t=5841&highlight=flta
Yup, the IFD540 has it! Nothing else to buy or add. A software update will liven it up. The possibilities are tantalizing, from ADS-B and GPS data out, to things like keyboard support!
There are some short youtube videos here, showing common tasks:
http://www.ifd540.com
Avidyne's main site is just the obvious www.avidyne.com
OK, that's enough for now, BACK TO FLYING.
Any questions, just shoot.
* Orest
Hard to know where to start to try to describe it all.
First out with the old (430W & GTX330):
Then IN with the new, The Avidyne IFD540 GPS/COM and APX340 ADS-B transponder, here is the whole center stack:
This is a screen capture from the simulator, for a crisp view of the main screen.
The screen is a page and tab, plus side tab construct. The bottom buttons are rockers, you can move through tabs, or you can direct touch tabs on the screen. The side tabs can be slid out, or in, and some will pull out across the screen to fill it. (eg. Flight Plan tab) Either the bezel buttons, or the touchscreen can be used to access the button pushes. (eg. Wx Overlay)
With the Hybrid Touch interface, you can do most anything with either bezel controls or the touch interface. I kind of like holding onto the knobs and turning, but some functions the touchscreen makes more sense. Nice to be able to use both, everyone will have their preference.
You can have up to four preselect frequencies, here I've configured for three. In this config you toggle between COM & NAV frequencies with the bottom left knob. All frequencies, including active and the presets for both COM & NAV are auto-id.
On the above screen configuration there is a traffic thumbnail, and the separate land and nav feature declutter buttons. The 540 will also declutter on the basis of altitude. All of this is user configurable.
Both the right and left datablock areas you can populate with data fields as you like. In the 10.1 release the entire datablock area on the right will scroll up & down, letting you define and view a relatively unlimited number of fields. That is a key feature to help the smaller screened 440.
There is a terrain/obstacle height key in the top left of the map. This shows three values, the lowest terrain in the displayed map (within the outer range ring), the highest, and if higher, the highest obstacle height. The Min Safe Alt is different, it is the conventional grid square value, doesn't key to the range of the map.
The GPS AGL at the top, is a poor man's radar altimeter, gives the GPS height above the terrain database elevation for your current point.
You can select a North up, track up or heading up view, and there is also a 240 degree (partial arc) track up and heading up view. If you have a track up setting, then your own ship will cant as according to the winds, to show your crab angle. The next active leg is shown as a barber pole.
QWERTY, together with "geo-fill" auto filling of text fields, lets you zip through selections. Geo-fill will fill the rest of text entry fields with a logical entry, saving you keystrokes. Entering COM frequencies you can use 197 for 119.70, or for VORs you can use the VOR ID, for example YQO for 114.2. Incidentally, the IFD440 due out this Spring, the IFD540's smaller cousin (430 size) will also have a full QWERTY screen, and the same quick entry methods. In fact it will have everything the 540 has, feature-wise, except those things specific to a larger screen.
Building a route.
Of course you have full airway support, but with a really cool twist. As you build your route, you get a full dynamic display of the proposed route (auto-zoomed for you), with all the waypoints listed geographically, right on your main map page. As you select one of them, the map rezooms, and redraws the proposed route. When happy with the exit point, you select it again and all the waypoints are added.
The same method is used for adding a procedure, together with its transition. never need to wonder which transition goes where.
You can add any number of airports (duplicating them in a row as well) in your route, and an arrival and or approach for each. It is all reflected in one long flight strip. Handy when doing IFR practice approaches.
OK, back to the "real" in cockpit pics.
There is a bewildering number of data fields that you can add.
There are three custom configurations now, you can populate as you like. There will five more for the 10.1 release. In the following release, you will be able to set various screen configurations to auto-transition, depending on the phase of flight!! That is actually one of the suggestions I made to development team. The openness of Avidyne to customer interaction is remarkable, and it will result in a stronger product. They have public forums at http://forums.avidyne.com
I've pulled the scale way back here to show a very cool feature. The IFD gets airdata from the ASPEN, and fuel data from the EDM830. Here, based on current GS, fuel burn and capacity available it shows two range rings (red arrows), the dashed is distance to 45 min reserve, the solid is the distance to "empty".
The flight plan track is not really visible in this pic, because it is so short at this scale, it was just a local flight. But, YQO (Aylmer VOR) is the next waypoint. it auto-loads as the active frequency when its leg becomes active, and I've placed the VOR/LOC info datafield just below the freq. That gives your current bearing and distance, like having DME back.
I added waypoint datafields on the right, and you can see the expected fuel remaining at the next & final waypoints is also included here. I've also chosen to have the direct to destination distance (as the crow flies) shown.
Next is the Nav Mode, and below that an extremely powerful field, the VSR, the vertical speed required. What makes this so powerful is that you can define an altitude constraint relative to every waypoint in the flight plan. Even cooler, the IFD will populate the minimum altitudes for a approach automatically, showing this on the flight plan and on the screen, and the VSR field will reflect these. More in the pics below.
I also have our Jepp plate subscription installed, so you can toggle to the plates. These are geo-referenced, and the rectangles draw on the main map screen. They are a little small, but the pinch to zoom and flick interface lets you use them effectively. They also have a quick header, plan and minimums view selection.
OK, on the approach into my home airport, RNav 05.
You can see on the scrunched flight plan strip on the right I'm heading for OVUTU (IF/IAF), and there is a listed minimum altitude of 3000ft. That is also depicted on the map. There is no hold on this approach, I have added a custom hold at OVUTU, holding north. The IFD auto configures the entry with the least amount of turn, here you can see the parallel leg as a barber pole. I can delete this hold, or change it (leg length or time, and inbound course) by clicking on the descriptor in the flight plan strip. Bottom left is a DELETE HOLD button. Once you are in the hold, it changes to EXIT HOLD. Holds are done, just like the big boy's FMS.
You can also see the SEKIL waypoint, the FAF, with the FAF minimum right on the strip. When it become the active leg, the minimum is drawn on the map.
The IFD has another very cool safety feature. With an approach active, if you go below the FAF minimum, before reaching the FAF, it will show you a CAS (crew alerting system) caution notice - "check altitude, too low". Hope i never commit that, but if I did ...
OK, past the FAF, inbound.
I'm in track UP, 240* view. Note that the own ship image is canted to the left to represent my crabbing due to the crosswind.
Also note the green TOD marking, that is where you should start down. You get a nice Ding-Dong tone to remind you 10 secs before. The TOD is calculated for any segment (ascent, cruise or approach) where you have an altitude restriction ahead, and you reach your target required vertical ascent/descent rate. The default is 500 fpm, you can set it to whatever you like.
OK, approach into CYHM, a neighboring controlled airport, here on the LOC30 approach.
There is no vertical guidance on the LOC of course, but no worries, the VSR field shows you the current required VS to make the minimums at the MAP, making a constant descent approach real easy. You can dive and drive if you wish, but even then you can use that to ensure you are too late in your descent. To set that up all I had to do was - nothing. The numbers populate when you select the approach, you just fly it.
Note the oversized yellow obstacle indication. That is part of the Forward Looking Terrain Avoidance (FLTA) available in the base configuration of the IFD, normally you have to get full TAWS to see that, the IFDs include it in the base units.
For more on the FLTA feature, see this thread:
http://www.piperforum.com/showthread.php?t=5841&highlight=flta
Yup, the IFD540 has it! Nothing else to buy or add. A software update will liven it up. The possibilities are tantalizing, from ADS-B and GPS data out, to things like keyboard support!
There are some short youtube videos here, showing common tasks:
http://www.ifd540.com
Avidyne's main site is just the obvious www.avidyne.com
OK, that's enough for now, BACK TO FLYING.
Any questions, just shoot.
* Orest
Last edited:
