Results 1 to 3 of 3

Thread: ADS-B barometric altitude encoding problem

  1. #1

    ADS-B barometric altitude encoding problem

    Six months ago, I replaced my AFS4500 EFIS with an AFS 5400. After doing that, my avionics A&P noted a small static leak..OK for VFR, not IFR, he said. I then ran a PAPR and it showed a failure in ADS-B barometric altitude reporting (previous PAPR's were fine). Transponder is a GTX327 and the ADS-B is an EchoUAT. Navigator was a 430W, now is an IFD440. Switching the GPS navigator didn't make the problem worse or better.

    Thoughts on why this might be happening? Is the static leak part of the problem? Or is it more likely that I've mis-configured the serial ports from the 5400? (I have the 5400 as the PFD and a second 3500 attached to the 5400 via ethernet cable). FWIW, the ADS-B IN trf/wx function of the EchoUAT works fine and displays on the 3500. The only part of the ADS-B OUT that fails is the barometric altitude reporting, and it only fails a percentage of the time, not 100% of the time.

    Attached Images Attached Images  

  2. #2
    OK, no-joy. Let me ask it this way... my ADS-B out was working fine with the old AFS 4500/Crossbow. When I switched it out for the 5400 with SV network, the ADS-B is no longer getting barometric altitude encoding from the new EFIS . Why might that be? The serial port setup, 4500 vs 5400 is the same.
    Attached Images Attached Images   
    Last edited by MacCool; 01-04-2022 at 06:50 AM.

  3. #3
    Could be the static leak, could be altitude encoding. You don't have a single serial port on your 5400 assigned to TRFC/ICARUS so as to send altitude encoding to your GTX 327, which means

    1) you either have a hardware encoder, or
    2) you have a serial port on your 3500 MFD assigned to TRFC/ICARUS and connected to your GTX327. In such case your 3500 must either have its own internal AHRS and air data, or otherwise be properly set up to receive data from the 5400's SV-ADAHRS-200 by way of the Air Module Config and AHRS Module Config both being set to HW:OFF, NET:RXD, or
    3) your transponder just isn't getting encoding at all.

    The ADS-B in from your echo working properly is immaterial to the functioning of your ADS-B out, so there is nothing about that which merits further inquiry.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts