Hi Faulknem,
Thanks for the feedback. As you have discovered, the traffic you previously reported as showing on FR24 but not on SD was just too high for SD to display on its previous settings.
Most of your PAW settings look fine, though I would make the following suggestions.
1. In general, leave all range and altitude settings as wide as possible in PAW configure, and set your chosen ranges in your display software. With SkyDemon, however, you need to choose your vertical and horizontal reporting range for
Bearingless Traffic (Mode C and S Transponders) in PilotAware as SD doesn’t have appropriate settings. I normally run mine on Medium Range and +/- 2000 ft, though it is useful to have both wide open initially so you get used to seeing (and hearing) the reports. SkyDemon BTW normally has ‘Show Bearingless Targets’ Disabled by default so you need to check this in SD/Navigation Options, or the Mode C / S target warning rings won’t be displayed.
2. You have ‘Mode CS’ selected (without filter) so you presumably have no transponder (or you would need to use the ‘+ filter’ setting).
3. The +/- 50,000 ft vertical display range you have set in ‘Configure’ only applies to Bearingless Mode C or S Aircraft. Height Settings for known position aircraft (P3i, ADSB, FLARM and Mode S/3D) are determined in SkyDemon Navigation Options, as we have already shown, NOT in PilotAware.
4. I would also suggest enabling ‘Mode S /3D if you want to see Positional reports for Mode S Aircraft via your local ATOM GRID Ground Stations - a fantastic improvement IMHO.
5. If enabling Mode S/3D, you should also change your ‘Display Traffic Info’ setting to ‘Alternate’ as this then alternates between the aircraft Reg and ‘M’ to confirm it is an MLAT position. Rebroadcast FLARM targets will also alternate between their own ID and ‘G’, so you are aware that they are rebroadcast not direct reports.
6. I notice you have ‘Group ID’ set to you own Reg. This will achieve absolutely nothing as your own aircraft Reg is never displayed. This setting is intended to identify other PilotAware-equipped aircraft if left on the default ‘PAWGRP’ or colleagues with PilotAware from you own Club or Flyout Group if you all set the same agreed ‘Group ID’ (see the full setup instructions on
www.pilotaware.com ).
Making these changes should significantly improve the usefulness and effectiveness of your unit. Don’t forget to ‘Save’ the changes for them to take effect.
Finally, there is an obvious ‘voltage’ and ‘throttling’ warning in the Status Line on the Home Screen, which indicates a power supply issue of some sort. This needs addressing. The ‘Warning’ reports indicate that this is ‘historic’, i.e. not happening when the screenshot was taken. What sort of power supply are you using? It is essential that the supply voltage never drops below 5 Volts at any time. Other potential check points are poor quality supply cable or a loose connection - possibly at the Rosetta end. If not tracked down and addressed, this is likely to cause poor performance or failure at a critical point.
Hope this all helps clarify the setup, both for yourself and for others reading this thread.
Best Regards
Peter
p.s. please do come back to us re the Voltage warning issue - it is very important that this is resolved.
