Recent Posts

81

OGN-R PilotAware / Re: FLARM to change protocol

« Last Post by steveu on March 21, 2024, 07:54:54 pm »

gliders were available with safesky

SafeSky directly or via the OGN?

FLARM is a bit banjaxed... more here:

https://xcmag.com/news/xc-tracer-flarm-collide-over-software-update/

82

Technical Support / Re: adsb (out) not showing on Vector

« Last Post by JCurtis on March 21, 2024, 05:58:03 pm »

I picked an aircraft at random (a PA28) that was live and showing MLAT. Then went back to look at previous flights for the same aircraft and they showed as MLAT too. Just to see what ADSBExchage recorded for historical flights.

So isn’t Mode-S shown as MLAT and with added ES becomes ADSB. If so it looks like things are working on the aircraft in question.

83

Technical Support / Re: adsb (out) not showing on Vector

« Last Post by exfirepro on March 21, 2024, 05:33:27 pm »

Just to keep Peter on his toes, I'll also throw this into the mix...

I picked a different aircraft on ADSBExchange that was showing as MLAT (a PA28).  I went back to find another flight, and it shows as MALT in the history.  So I think the transponder is doing its job correctly....

When you say ‘I went back to find another flight, and it shows as MLAT in the history’ do you mean another G-RUVE flight? If so, that would certainly confirm that the transponder was transmitting Mode-S at that time, but would also confirm that it wasn’t transmitting ADSB.

Unfortunately we had to stop recording Mode-S data as there was so much of it that the servers couldn’t cope, so I can’t verify that from the database.

However, for MLAT to work, the transponder and antenna must be operational, at least outputting Mode-S, which would be the same carrier as if it were also doing Extended Squitter from the GPS reference.  So perhaps the GPS -> Transponder link isn't running, but surly the Transponder would indicate if the data is there or not?

Defiantly weird.

I fully agree, but there is no easy way to check that remotely. John did say he checked the transponder settings and GPS position a month ago, but he is using a Funke TRT800H, fed GPS data from a Trig TN72 and I’m not sure how that displays, or if (and how) it gives warnings if it loses the GPS feed. I know my Trig produces an ADSB Fail Alert on the control head, but it’s not particularly prominent.

I’ll keep on the case.

Peter

84

Technical Support / Re: adsb (out) not showing on Vector

« Last Post by JCurtis on March 21, 2024, 04:58:26 pm »

Just to keep Peter on his toes, I'll also throw this into the mix...

I picked a different aircraft on ADSBExchange that was showing as MLAT (a PA28).  I went back to find another flight, and it shows as MALT in the history.  So I think the transponder is doing its job correctly....

85

Technical Support / Re: adsb (out) not showing on Vector

« Last Post by JCurtis on March 21, 2024, 04:43:53 pm »

However, for MLAT to work, the transponder and antenna must be operational, at least outputting Mode-S, which would be the same carrier as if it were also doing Extended Squitter from the GPS reference.  So perhaps the GPS -> Transponder link isn't running, but surly the Transponder would indicate if the data is there or not?

Defiantly weird.

86

Technical Support / Re: adsb (out) not showing on Vector

« Last Post by exfirepro on March 21, 2024, 04:31:55 pm »

Hi again All,

Ok, so I have now had a chance to look at the FR24 and ADSBExchange Reports. I certainly can’t deny that they are both reporting G-RUVE’s flights on the dates in question.

Unfortunately, although ADSBExchange ‘seems’ to be reporting the flight as ADSB, we know that aircraft tracking sites (including FR24) use a combination of ADSB data from ground and satellite sources, plus MLAT from Mode-S as well as FLARM data (probably from the OGN Network - which also reports PilotAware), and data from goodness knows what other sources, when compiling their reports.
 
That’s the only realistic explanation I can think of for the virtually complete track reports from these sites, bearing in mind the paucity of ADSB data from G-RUVE on our database for 3rd March and the complete lack of ADSB data for 13th March. I’m pretty sure I could get a similar track report from just the PAW and FLARM data on our site, but unfortunately the PilotAware Playback tools are down at the moment (server maintenance apparently).

I will give it a try later and let you all know what I find.

In the meantime, I stand by my previous comments and suggestions to John for further investigation.

Best Regards

Peter

87

Technical Support / Re: adsb (out) not showing on Vector

« Last Post by exfirepro on March 21, 2024, 01:18:52 pm »

Hi Jeremy,

Thanks for that.

405F9B is certainly the correct HexID for Vans RV8 G-RUVE and the ADSBExchange link certainly seems to be reporting the flight as ADSB.

I need to look into this further, but have to go out this afternoon. I will take a look later when I get back.

Peter

88

Technical Support / Re: adsb (out) not showing on Vector

« Last Post by JCurtis on March 21, 2024, 12:02:17 pm »

One for Peter really....

FlightRadar24 shows several flights for HEX 405F9B, including the 13 March. It is presumed to be ADSB, but FR24 doesn't say.

ADSBExchange shows the flights too, and reporting as ADSB data, this is from the 13 March ->  https://globe.adsbexchange.com/?icao=405f9b&lat=51.738&lon=-1.261&zoom=9.5&showTrace=2024-03-13&timestamp=1710334942

So it looks like the larger networks are picking up ADSB from an aircraft broadcasting HEX 405F9B. 

Do they look like the correct flights?

89

OGN-R PilotAware / Re: FLARM to change protocol

« Last Post by exfirepro on March 21, 2024, 11:32:21 am »

Hi Lee,

Does that only affect the Network, or do individual PilotAwares all need software updates too (bearing in mind that some might still be running ‘pre-auto update’ software)?

Regards

Peter

90

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