AFS and IFD540 working together with Jeppesen and Seattle Avionics Databases

[Flyxaos]

Thank you.

I see the Seattle Avionics package has a AF2MAPUS_V16_2502_MAP.afz in it.

But your data from your site is AF2MAPUS.AFM

There is no .AFM in the Seattle Avionics package. Is that the same file? Accomplishing the same thing?

Thank you for the answers.

James

[Jonathon]

The .afz extension is just a renamed .zip file. If you extract the zip file, you will see that the AF2MAPUS.AFM file is what is packaged inside.

[Flyxaos]

I think I'm good, the panel never complains when i load the usb from SA but to clarify...

The. Afz file goes on to the usb stick from the Seattle Avionics data manger as an afz, not an afm. That means the panel can unpack and read it straight from the afz then, correct?

Before i bought the Seattle Avionics package I got your file as a .zip, unzipped then installed as the .afm.

[Jonathon]

I think I'm good, the panel never complains when i load the usb from SA

It should complain; you should get a pop up message on the EFIS that says "LOAD NEW MAP CYCLE?" with yes or no buttons on the bottom of the screen. Pressing YES will initiate the install of the AFS map onto the EFIS internal memory. The Seattle Avionics maps do not install to the EFIS internal memory, and are unaffected by this operation.

You should verify the version of the AFS map that you have installed, from the CHECK --> ABOUT --> MAP page. The current map data is cycle 2502, valid 02-20 through 03-19.

The. Afz file goes on to the usb stick from the Seattle Avionics data manger as an afz, not an afm. That means the panel can unpack and read it straight from the afz then, correct?

Correct, but this only works on AF-5000 software V16 and later. V15 and earlier software cannot read the .afz file extension.

[Flyxaos]

Perfect, it is working properly then.

I started looking at this because I was getting 0 AGL while in flight, and thought this may be related. It isn't. I figured that issue out yesterday. The IFD540 knows it's AGL, but is not giving AGL to the EFIS. That I don't know why yet, so please advise if you know.

If I set the source to AGL(B1) or (G2) I get AGL and don't fly through SVN mountains at 5,000 feet.

Thanks again. I enjoy the panel.

[Jonathon]

GPS altitude only comes over the serial port connection from the navigator in aviation data format.

- Verify that your SET --> CAL --> Admin Settings GPS/NAV1 assignment doesn't say "NO AVTN" in the selected option name. The SV-ARINC NO AVTN and AF-ACM NO AVTN choices disable GPS altitude for legacy compatibility with CNX80/GNS480 navigators which never supported it.
- Verify IFD configuration is properly set to send aviation format data out the serial port which is wired to the Advanced Control Module, or to the SkyView ARINC 429 (or directly to a free serial port on the EFIS, should you have the older AF-ARINC adapter instead).
- Verify that the wiring between this serial port on the IFD and the serial port on the ACM, or the SV-ARINC, or the EFIS, is intact.

[Flyxaos]

Awesome. I will check.