Group: Forum Members
You should also check the ‘Positional Contact Settings’ Filters in your PAW / Configure Screen. These were added at the request of users of systems like XC Soar which don’t have their own vertical/horizontal filters - and limit traffic passed to the Nav App but still allow the aircraft to be shown in PAW Radar (which has its own Vertical and Horizontal Range Controls). If you have this filter set to say +/- 1000ft, the traffic at +1200ft (or above) simply wouldn’t be passed to SD and hence not displayed.
You can see this effect by setting a tight vertical range then looking at the PAW ‘Traffic’ Screen (preferably on the ground), which will show high level traffic ‘greyed out’.
When using Nav System Displays (such as SD) with their own built-in Positional Contact Filters, you are probably best to leave the PAW Positional Contact Settings at ‘Display All’ and set your desired limits in the Nav System, though you can of course set the ‘pre-filters’ in PAW but don’t forget you have done so.
The ‘Bearingless Contact Settings’ in PAW BTW work differently as they are ‘signal strength’ not ‘distance based’, and are in essence a ‘sensitivity control’ used to adjust the nominal range at which PilotAware audio (SD doesn’t give audio alerts for Bearingless targets) and PAW (and SD where selected) visual alerts are triggered.
Hope this helps.
(PAW Development Team)