Ivor,
Sorry, I didn't realise that's what was worrying you. I obviously misunderstood that your original concern was that your
aircraft registration no longer appears on
SkyDemon, when you obviously meant 'no longer appears in your
'PilotAware Traffic Display'.
Your Aircraft Reg could only ever have appeared
on SkyDemon if your PilotAware was running with a
different hex code from your transponder - e.g. the original randomly generated PilotAware Code. This would result in PilotAware seeing your ADSB transmission as a threat and displaying its details (including your Reg) on SkyDemon as a small (probably red) aircraft right on top of your own aircraft symbol at the centre of the screen, which would have explained the initial description you gave.
The screen grab you posted....
'a picture of when it worked last week,'
...clearly shows that your transponder was transmitting ADSB Out (Mode = CSA - -), and the 3rd and 5th entries in the ADSB Status column of the Traffic Screen clearly indicate that it was transmitting the correct SDA and SIL codes as '0', which are required for ADSB out transmission using a non-certified GPS source, so you must have had your PilotAware connected to the transponder and correctly configured for ADSB transmission at the time that screen grab was taken.
Changing PilotAware to the
correct ICAO Hex Code for your aircraft 'later on' to match the one in your transponder, would stop this 'rogue' aircraft (and associated Reg) appearing on your Navigation Screen as it would then be correctly filtered out by PilotAware, though it would normally still show at the top of your Traffic Table. I have to say that although my ADSB Transmission
is usually visible at the top of the Traffic Table, it does occasionally disappear and I'm afraid I have no idea why.
It may of course be that there is a fault with your setup or wiring, stopping the data from PAW reaching the transponder. Double-check you have the
CORRECT USB port configured for the ADSB out lead to your Transponder (if this is the 'top left' port with the Ethernet port to its immediate left, this is
PORT 1) - that you have correctly saved the settings (screen grabs of appropriate screens would help here) and that there is no problem with the connecting cable.
Turning off 'Mode S' by the way doesn't turn off the filtering, it turns Mode S Detection off completely, so that won't help.
With regard to your most recent post....
how will i show my inspector that it is showing in traffic to get it ok'd by the LAA?
does it mean i will need another PI unit to document what mine is doing?
If I recall correctly, the LAA mod procedure actually requires that a
separate PilotAware is used to show your ADSB data transmission and in particular the SDA and SIL coding of your installation, (the 3rd and 5th entries in the ADSB Status column of the Traffic Screen), presumably to ensure that the data is genuine. You could show the screen grab which already shows this data, confirms your transmitted Latitude, Longitude and Altitude and is time and date stamped, to your LAA Inspector and ask them if they would accept this as sufficient evidence to support your ADSB Mod application. They may however insist that this is repeated using a separate PilotAware so they can see for themself that the data is genuine before signing off your Mod. In this case you might need to elicit the assistance of another PAW user, which you could do through this forum. Unfortunately Kent is a bit too far away for me I'm afraid, but I know there will be other local users. They do not need to be connected for ADSB Out themselves, just able to provide a screen grab of
your aircraft data from their Traffic Screen
Hope this helps clarify the situation. Sorry again for the earlier confusion.
Regards
Peter
