Hi Julian
Just on another fairly obvious point if the PAW user has ADS-B out (which is good!) the PAW transmissions should be disabled so that two planes don't show up on SD.
I am not sure where you got this information ?
It is perfectly OK to be transmitting continuously on P3I and ADS-B.
Two planes will not show up because the software keeps a single record based upon the ICAO identifier.
The same ICAO identifier is used in PilotAware as is used to configure your transponder, so the receiving PilotAware knows internally this is the same Aircraft, and only sends one traffic record to the navigation device.
I am wondering if you were confusing this with LPAT, in which case you are correct, LPAT cannot be setup to transmit in an Aircraft which is also Transmitting on a transponder Mode-A/C/S or ADS-B
Which is a bit of a system design flaw, if you have a Mode-A, Mode-AC or Mode-ACS transponder (which is the vast majority for GA), because it is
forbidden to use your transponder whilst LPAT is transmitting, due to the ICAO conflict
I'm planning to have both systems available in the plane (both interfaced to SD via WiFi - but only one at a time of course) but as I mentioned in a previous post this set up needs the PAW transmission switched off (which I understand is possible) as I will have ADS-B out from the TRT800H and the position data from FLARM. Interesting to see which system performs the best PAW or FLARM.
As I mentioned, this is not an issue, it is perfectly OK to have PAW transmitting in conjunction with the ADS-B out to the transponder. So you can be sending your ADS-B and P3I data concurrently, or indeed if your existing transponder is Mode-A, Mode-AC or Mode-ACS (Without Extended Squitter, or the ability to configure the SIL/SDA bits for non-certified GPS Status)
In which case PilotAware is highly complimentary to the existing GA Fleet of transponder equipment.
Thx
Lee