1. Superfluous Waypoints on Airway:  When I load an airway into my flight plan, a number of waypoints along the airway are also loaded.  Is there any way to direct the IFD540 to load only those waypoints at which the airway bends?
2. No Winds Aloft Display:  My IFD540 is connected to my Aspen EFD1000 Pro, which contains an internal airdata computer that calculates and displays the winds aloft.  However, the winds aloft display on my IFD540 is blank.  How can I get the Aspen winds aloft to display on my IFD540?
3. ETA at Destination:  The ETA at Destination data block is way off, by many hours.  The ETE to Destination is working fine.  This seems like a software bug; has anyone else seen it?
4. VSR Not Displaying:  The Vertical Speed Required data block is blank, even when I've entered a crossing restriction in my flight plan.  How do I activate the data block?

< ="cosymantecnisbfw" co="cs" id="SILOBFWID" style="width: 0px; height: 0px; display: block;">

Steve, if you read this:  The box, by definition, knows where it is.  It is possible to code the time zones and local laws regarding daylight savings time, etc.  Can you add a feature candidate to the list for the user to choose to let the IFD automatically determine the local time?

2.  Not sure exactly what you are looking for here.  Are you talking about the Wx Overlay button on the map (see page 3-16 of the pilot guide) and the ability to show wind vector barbs on the map or are you  talking about using the air data calculator (see page 4-9 of the pilot guide) to compute winds at a given point or are you talking about the Wind Vector datablock option (see page 4-26 of the pilot guide)?  The first will not work without a GDL-69 or MLB700 datalink device but the second will work.  Depending on the nature of the Aspen integration, some fields on air data calculator will pre-populate with green data if it's talking to the Aspen. If it were the wind vector datablock, see that little note in the box on page 4-26 that says you need baro input.  If that wind vector datablock is dashed, you are not getting baro from the Aspen and that implies you don't have an Aspen ACU of the right flavor pumping that data out.  I do plan on adding a table in the Release 10.1 Installation Manual that shows what data comes from Aspen depending on the flavor of Aspen gear.

3.  The guys above are all correct.  See the bottom of page 4-35 of the pilot guide for how to set in the local time offset.

4.  Teeth6 is correct again.

As for MysticCobra's time question, we do have it as a candidate in the future feature database but it hasn't bubbled up high enough in the priority queue yet.

Can you say more about the "nature of the Aspen integration"?  The Wind Vector datablock on my IFD540 is currently dashed, so it must not be getting the necessary input from the Aspen.  What do I need to make this happen?  Another box from Aspen or perhaps a software update for the Aspen EFD 1000 Pro?  Or is it possible to manually enter the necessary barometric information in the Air Data calculator?

including VSR and wind vector not requiring baro alt.

Would be very helpful.  

It seems like 10.1.0.0 will make an ACU2 irrelevant where an ACU1 is already present, but maybe I am missing something.

Thanks.

David

But, the ACU2 solved another problem for us, in my install, so I'm glad I have it.

* Orest

OK I'll bite, what was the other problem solved by the ACU2?

Jack

I had to do with the JPI 830, and getting it and the ASPEN properly talking to the 540 (and 430W before it), with full interchange of fuel flow and locations and allowing computation of fuel remaining at destination by the 830. It relates to the limitation in the GNS (and IFD) that you can only have one airdata input on the RS232 and the config settings in the 830. But the ACU2 allowed us to use 429 instead, or something like that. I can query the avionics guys and refresh my memory if you share a similar config and wish the details.

* Orest

Can you develop further information on that topic?  I have dual IFDs, a JPI 700, and an AXP 340.

The shop can't get the JPI to talk to the 540 in terms of fuel flow, etc.

Maybe your issue was same as what I have now?

Thanks

David

Geoff:

Are you sure?  The IM says for the JPI 700:

Mike
< ="cosymantecnisbfw" co="cs" id="SILOBFWID" style="width: 0px; height: 0px; display: block;">

Doesn't apply to a 700. The setup issue is particular to the 830.

To obtain and display the fuel at destination (and simultaneously transmit fuel flow to the GPS), for the 830, the 540 (or GNS) needs to be set to airdata on the 232 inbound. The 540 (and GNS) can only have one airdata input on 232, and as I have an ASPEN, that is needed for it.

The original ACU cannot send airdata on 429. An ACU2 can. A 540 (or GNS) can accept airdata on 232, but also multiple airdata inputs on 429. That solved our issue. Of course the ACU2 also provides BARO ALT.

* Orest

Ah, congrats! You'll love it.

* Orest

 There are some eight different formats you can specify in the 830 for communication. Each will require a certain protocol in the 540. (or any other GPS/COM you are using)