So, for some reason Radarbox is not detecting the callsigns on these aircraft, where the SBS-1 does. Are callsigns transmitted on different message types, and is Radarbox maybe missing callsigns on a particular message type?
Can this bug be investigated and fixed please. Not being able to see a callsign also means I no longer see the route details, which is a real pain.
EDIT: Looks like this bug may have been introduced in v2.0. Looking back at my ANRB2008 MyLog, I've got over 400 Loganair Flight IDs in my Flights table. I haven't got ANY in my ANRB2009 MyLog.
So, for some reason Radarbox is not detecting the callsigns on these aircraft, where the SBS-1 does. Are callsigns transmitted on different message types, and is Radarbox maybe missing callsigns on a particular message type?
Can this bug be investigated and fixed please. Not being able to see a callsign also means I no longer see the route details, which is a real pain.
EDIT: Looks like this bug may have been introduced in v2.0. Looking back at my ANRB2008 MyLog, I've got over 400 Loganair Flight IDs in my Flights table. I haven't got ANY in my ANRB2009 MyLog.
Looking at your logs it is not a ADS-B enabled aircraft. In this case the flightid is received when a Mode-S Radar bounces of the aircraft. So there won't be a special message type that we can get its could either be the reception of the aircraft was not close enough to pick up the FlightID or maybe some interference.
RadarBox 2009 has not affected the decoding algorithm (firmware) so we are not 100% sure of this.
Keep us posted and we will see whether there is an issue or something else.
We assumed this aircraft does not have ADS-B from the log you showed us hence the "1090 Extended Squitter, i.e. it's broadcast whether or not there's a Mode S radar interrogating the aircraft" which is ADS-B messages won't apply here.
I understand the format of an Extended Squitter message is:
- 5 bits for the "Format Type Code"
- 51 bits for the data (eg 3 bits for category, 48 bits for callsign).
Is there a list somewhere of the various 5-bit Format Type Codes? I understand which BDS's are used in the transponder, so are the BDS numbers then used as the 5-bit code on the message?
Thanks Dave, that helps. Just one more question, to help my understanding.
So, these Loganair aircraft are transmitting "Identification & Category" messages, and for whatever reason, ANRB doesn't process these.
But what type of message are military aircraft putting out that do get processed by ANRB? I'm trying to understand why all the military aircraft display callsigns okay, whereas these Loganair aircraft don't. Do the military aircraft transmit a different type of callsign message?
We hope to have a patch release out for the end of the year or a beta.
We hope to have a patch release out for the end of the year or a beta.
Could it be a useful suggestion to let tarbat beta test (if willing) these patches.........?
Ready and willing!! I just wish I'd spotted this bug in previous beta-testing, I've really only got myself to blame :(
Reg FlightIDJust trying to help Airnav diagnose the problem.
F-HBXA RAE557
G-LGNH LOG83LP
G-JEDL BEE332
G-SASC GMA091
G-JECI BEE324V
G-LGNA LOG60HE
G-LGNK LOG24FJ
G-CDKB EZE64Y
G-ECOP BEE118
It does seem airframe specific in many cases.
Interesting complication on the decode front:-
2 Jetstream 41's showing on box, with same Squawk difference in Mode-S is 8 ie 1 bit looks from the timestamps as though the Mode-S is being decoded differently at different times. - wonder if this could be an indication of other decode problems, including with the FlightID?? - Airnav?
Worth keeping an eye on the Saabs? Don't see that many pop up down here, maybe a couple a day of those Eastern Airways ones.
Tarbat is that a beta version of v2.1?No, just a version for getting FlightIDs working.