On Day 2 I was out all day and it has been cloudy most of the time. It was good though to see a turn in the sky being replicated on the screen earlier today.
Within a couple of hours of setting up I had picked up 2 AWACS and I can now identify some of the non-passenger aircraft up there.
I'm finding that not all flights are being displayed. I've had a couple of BA planes pass within line of sight of the antenna but were certainly not displayed and possibly not detected.
I guess that the central server uses the same database of aircraft but I have found aircraft to be unidentified in Network view when they have been identified by my box. In Network view, when I have cancelled Hardware flights, only the Mode S code is shown. I assume that when I tracked a particular Virgin Atlantic flight that the data had been supplied by my unit, but the full details that I could see direct were not being displayed on the Network.
The route details and callsigns database is a big help and I'm sure that alphanumeric callsigns are a major headache. For example, flight BAW299 EGLL KORD is listed in the database as such, but the callsign used by ATC and picked up by the RB is BAW2H. I'm just looking at a plane that is due to land at my local airport where the route is not displayed due to a letter Q suffix that has been added to the callsign.
I think that this has been mentioned but I have also encountered a case of flight duplication. Please see the attached screenshot.
The RB is a great product and is something that I have been aiting for for years.
[attachment deleted by admin]