2
« Last Post by exfirepro on January 24, 2022, 09:26:57 pm »
Hi Gary,
The reason for no Mode-S reports on Vector is the easy bit and has been publicised several times here and elsewhere since shortly after the Vector Tool was first introduced.
Mode S reports were available in the early days of Vector development and worked extremely well (I have several examples on file). The problem was that when the Tool was released and made freely available to all (not just PilotAware Users) on the PilotAware website, we rapidly found that we were having to store ever increasing amounts of Mode-S data on the servers to meet the demand and that the processing and levels of data required to create and display Mode S reports was significantly affecting other more important functions. The decision was therefore taken to suspend the provision of Mode S reports, but to leave the option in place so it can be easily reactivated if/when the problem is resolved. Reports on your ADSB, Flarm and PilotAware transmissions should however be available.
OK, I have just looked up your ICAO Hex from previous posts and checking the PilotAware Database (from which the Vector reports are compiled), I can find plenty of recent ADSB and FLARM reports, but no PilotAware reports under your official ICAO Hex since 23 September last year - which explains why there are no PilotAware Reports on Vector as they are based on something like the last 30 days of data.
For some reason your PilotAware stopped transmitting using your ICAO Hex Code after 23rd September. This could be because the licence key for your unit expired, or the previously correctly set Hex ID for some reason reverted to the initially allocated ‘MAC based’ default instead of your correct ICAO Hex. Unfortunately I can’t check for reports under the MAC derived Hex is as I don’t have access to the section of the database containing your MAC address. You can, however, get it from your PilotAware or from your last licensing renewal paperwork (I need the last 5 figures from the 12 digit MAC starting B827EB... to recheck the database).
This could also (at least in part) explain the presence of your ‘duplicate aircraft’, though there are a number of other areas which we may also need to investigate.
Firstly, you need to check that all of your devices are set to transmit the same identifier - namely your officially allocated ICAO Hex code.
Secondly, can you confirm that you have updated your PilotAware software to the latest (20220101) release? (which contains a number improvements designed to minimise the possibility of this type of problem).
If neither of these resolves the issue we will need to investigate further.
Please let me know how you get on.
Best Regards
Peter
Recent Posts