Recent Posts91
Technical Support / Re: adsb (out) not showing on Vector
« Last Post by exfirepro on March 21, 2024, 11:28:37 am »Hi again John,
Thank you for responding to my earlier post.
So we have established that your PilotAware/Flarm and Transponder/ADSB-Out installations are operating as two completely independent setups (similar to my own setup, though I use different hardware). This narrows down the possibilities to your Funke / TN72 installation or their associated wiring/antennae.
Looking at the secure PilotAware Database, I now see lots of additional PAW and FLARM reports from 405F9B from 13th March (from multiple ATOM sites) but no ADSB reports whatsoever from that date.
I have, however, now found a few random ADSB data packets received by the ATOM sites at Blackbushe, Kiddlington, (Abingdon), Thame (east of Oxford) and Woodcote from your flight on 3rd March, though all extremely intermittent and at varying ranges - only 2 or 4 data packets (which represents only a few seconds worth of transmissions) at any individual site.
The last ADSB report recorded on the database prior to 3rd March is one single data packet at 15Km from PWUKEdge (near Banbury) from 15th February, despite the fact that there are PAW and FLARM reports from multiple ATOM sites on that same date.
Prior to 15th February, there are multiple ADSB reports from flight(s) on 15th December 2023, from Ampney, Caldwell, EGBS, EGHP, EGLK, EGLM, EGTK, Kemble, Pidding, Radley, and including a single data packet received by PWUKEdge at 59Km and a few from PWThame (nr Oxford) at 8Km plus others from other local sites, all at varying ranges, so the ADSB was definitely transmitting at that time, though not necessarily reliably.
Points to check:
1. Anything that has changed since 15th December.
2. That you still have the correct Hex ID programmed in your transponder (unlikely to have
changed unless anyone has attempted to check and accidentally changed something, but if it is
incorrect, it ‘could’ still be transmitting, but won’t appear under 405F9B on the database - or on
Vector. (If you do find it has a different HexID, please let me know what this is and I will recheck
the database.
3. Your transponder antenna connections and cables as mentioned by the others above (this is IMO
the most likely cause of poor transmissions. Remember to check for ‘short’ as well as ‘open’
circuits. I have seen poor results caused by a build up of mud around the base of a TED antenna
resulting in loss of signal at that point).
4. That your wiring (and settings) are correct between your TN72 and transponder.
5. If none of those provide a solution, you need to check the transponder itself.
Please let us know how you get on.
Best Regards
Peter
Thank you for responding to my earlier post.
So we have established that your PilotAware/Flarm and Transponder/ADSB-Out installations are operating as two completely independent setups (similar to my own setup, though I use different hardware). This narrows down the possibilities to your Funke / TN72 installation or their associated wiring/antennae.
Looking at the secure PilotAware Database, I now see lots of additional PAW and FLARM reports from 405F9B from 13th March (from multiple ATOM sites) but no ADSB reports whatsoever from that date.
I have, however, now found a few random ADSB data packets received by the ATOM sites at Blackbushe, Kiddlington, (Abingdon), Thame (east of Oxford) and Woodcote from your flight on 3rd March, though all extremely intermittent and at varying ranges - only 2 or 4 data packets (which represents only a few seconds worth of transmissions) at any individual site.
The last ADSB report recorded on the database prior to 3rd March is one single data packet at 15Km from PWUKEdge (near Banbury) from 15th February, despite the fact that there are PAW and FLARM reports from multiple ATOM sites on that same date.
Prior to 15th February, there are multiple ADSB reports from flight(s) on 15th December 2023, from Ampney, Caldwell, EGBS, EGHP, EGLK, EGLM, EGTK, Kemble, Pidding, Radley, and including a single data packet received by PWUKEdge at 59Km and a few from PWThame (nr Oxford) at 8Km plus others from other local sites, all at varying ranges, so the ADSB was definitely transmitting at that time, though not necessarily reliably.
Points to check:
1. Anything that has changed since 15th December.
2. That you still have the correct Hex ID programmed in your transponder (unlikely to have
changed unless anyone has attempted to check and accidentally changed something, but if it is
incorrect, it ‘could’ still be transmitting, but won’t appear under 405F9B on the database - or on
Vector. (If you do find it has a different HexID, please let me know what this is and I will recheck
the database.
3. Your transponder antenna connections and cables as mentioned by the others above (this is IMO
the most likely cause of poor transmissions. Remember to check for ‘short’ as well as ‘open’
circuits. I have seen poor results caused by a build up of mud around the base of a TED antenna
resulting in loss of signal at that point).
4. That your wiring (and settings) are correct between your TN72 and transponder.
5. If none of those provide a solution, you need to check the transponder itself.
Please let us know how you get on.
Best Regards
Peter
