PS - incidentally, on Ian's config settings, I'm not quite clear why in PAW the vertical separation range for both bearingless and positional contacts is +/- 2000 ft but in SD the vertical display range is +/- 50,000 ft?
Or maybe it doesn't matter what the SD figure is if the target ranges are filtered initially by PAW?
You have got it in one, the PilotAware filters are applied
before data is sent to the Nav Device, so they take precedence over any filter in the Nav Device itself - unless of course you set the Nav Device filter
narrower than the PAW one, when it would then simply act as a further (unnecessary) restriction.
On the Audio Alerts, Ian is correct, the PAW Audio alert
for Bearingless targets gives a report of ‘Level’, or the height in hundreds (or a combination of thousands and hundreds) of feet Above or Below up to a maximum of
10,000ft (not 1000ft)
Above You, e.g.
‘Traffic - Alert - One Thousand Seven Hundred Feet - Above’.
Over 10,000 ft Above you (or in theory Below you), Paw will simply report
’Traffic - Notice - Above’. In practice of course, this only happens with wide open PAW filters (i.e. Long Range and +/- 50,000 feet Altitude Setting)
and high power transponders (usually high-level CAT traffic passing overhead).
Positional Alerts, by the way, can report much smaller relative altitudes, depending on how each aircraft breaches one of the ‘cylinders’ around the other aircraft. When following another aircraft, for example, it is perfectly ‘normal’ to hear an alert in the form ‘Traffic - 12 o’clock - 3 Kilometres - 50 feet above’ if the fact that you are closing with them causes them to ‘enter’ through the front of your 3Km radius ‘cylinder’ when you are flying 50 feet below their altitude. If that’s not clear have a good read at the Manual. I must admit it took me a while to get my head round that bit, but it’s a fact - and perfectly logical ....once you get your head round it!
So to summarise, the reason you didn’t get Bearingless Visual Alerts was because of GDL90 and the reason you heard no Bearingless Audio Alerts is simply because you were running ‘Short Range’ and the other traffic either wasn’t transponding or was outside the range of the ‘Short’ filter.
Best Regards
Peter