AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: tarbat on February 13, 2008, 02:42:04 PM
-
I've noticed that several aircraft are displayed in Radarbox with only a 7 character Flight ID, when in fact they're transmitting an 8 character Flight ID (confirmed in SBS-1 Basestation).
A couple of examples:
ZH868 transmitting TESTID02 is displayed as TESTID0
G-LGNF transmitting LOG89150 is displayed as LOG8915
Is this fixed in v1.4?
-
I've noticed that several aircraft are displayed in Radarbox with only a 7 character Flight ID, when in fact they're transmitting an 8 character Flight ID (confirmed in SBS-1 Basestation).
A couple of examples:
ZH868 transmitting TESTID02 is displayed as TESTID0
G-LGNF transmitting LOG89150 is displayed as LOG8915
Is this fixed in v1.4?
I haven't noticed this, then I haven't been looking for it.
Does this happen in the aircraft list, on the map and in the ac details to the right of the photo?
-
It happens in the aircraft list and the details to the right of the photo. Also in MyLog. I can't remember if it happens on the map, but I'll check next time there's an aircraft with >7 characters in the Flight ID.
-
This hasn't been brought up before. Will see if we can fit it into version 1.4.
Does it appear ok in the data on port 7879?
-
Does it appear ok in the data on port 7879?
I'll check next time one appears with >7 chars.
-
Does it appear ok in the data on port 7879?
No, it appears as 7 characters on port 7879, and also 7 chars in the recorder file (.rbl).
Two aircraft transmitting 8 character Flight IDs this morning - LOG8894K and LOG8912L (confirmed in Basestation). Both are Loganair flights (our local regional airline). These appear on port 7879 as:
<MODESMESSAGE>
<DATETIME>20080214120637</DATETIME>
<MODES>400722</MODES>
<CALLSIGN>LOG8894</CALLSIGN>
<ALTITUDE>11875</ALTITUDE>
<VRATE>0</VRATE>
<LATITUDE>0</LATITUDE>
<LONGITUDE>0</LONGITUDE>
</MODESMESSAGE>
This isn't a major problem, so could probably be fixed in the version AFTER v1.4
-
I've been intending to mention this for a while so thanks for starting the thread.
It happens both on screen from my data and network data but also in the my log data.
Good example up now on the network,code AE040E 162783 E6 with callsign GOTO FM.
These E6's always(well nearly) use the callsign GOTO FMS ie 8 digits.
If this can be fixed it will clear up a bug and leave the box with one less item to revisit in the next upgrade session.
Thanks
-
This will make you happy!
(http://farm4.static.flickr.com/3138/2283848883_14900b464a_o.jpg)
(http://farm3.static.flickr.com/2131/2283848933_a500d1c3d7_o.jpg)
(http://farm3.static.flickr.com/2060/2284645408_ae57f7a8d8_o.jpg)
-
Thanks for that Allocator, good to see it's fixed in v1.4. I so want v1.4 now!!!!!
(http://img87.imageshack.us/img87/7200/pp2rs2.jpg) (http://imageshack.us)
By tarbat (http://profile.imageshack.us/user/tarbat)
-
tarbat, I thought that it might be one of yours up in that part of the world :-)
-
Yes, US military very active today:
(http://img505.imageshack.us/img505/4291/ppbv0.jpg) (http://imageshack.us)
By tarbat (http://profile.imageshack.us/user/tarbat)
-
Another 8 chr callsign! I've no idea why sometimes these show up and sometimes they are limited to 7 characters.
(http://farm3.static.flickr.com/2246/2365347536_283f0de5f9.jpg)
-
Another 8 chr callsign! I've no idea why sometimes these show up and sometimes they are limited to 7 characters.
(http://farm3.static.flickr.com/2246/2365347536_283f0de5f9.jpg)
Allocator,
Found this in a transponder operating manual....and we all know noone ever reads the instructions !!
3.1.4 Flight Identification (FID)
ICAO Document “8168-OPS/611 Volume I (Procedures for Air
Navigation Services)” requires that flight crews of aircraft equipped with
Mode S shall set the flight identification (FID) into the transponder to
ensure that the correlation between flight plan and radar data will work
automatically.
FID setting is required to correspond to the aircraft identification that has
been (correctly!) specified at item 7 of the ICAO flight plan:
· seven characters maximum, left-aligned, no additional zeros,
dashes or spaces
For an aircraft using a company call sign, the Flight-ID consists of the
ICAO three-letter designator for the aircraft operator, followed by an
identification code, e.g. KLM511, BAW213, JTR25.
If no company call sign is used or no flight plan is filed, the default FID to
be set consists of the registration marking of the aircraft (e.g. GXXXX,
DEABC) with no dashes, spaces or additional zeros, even if they are
included in the registration marking on the aircraft (tail number).
The ICAO Flight Plan only specifies 7 characters for FID.
Filser reserves 8 characters as stated in ED-73B for further
expansion of the flight plan.
The user shall only program 7 characters for FID.
-
Even an Easyjet can have an 8-character Flight ID - a bit of finger-trouble by the flight crew I guess!!! It does go to show that equipment in commercial airliners is capable of 8-characters.
(http://farm4.static.flickr.com/3026/2816742991_860707f5d7_o.jpg)
-
Even an Easyjet can have an 8-character Flight ID - a bit of finger-trouble by the flight crew I guess!!! It does go to show that equipment in commercial airliners is capable of 8-characters.
Yes, the 56-bit Extended Squitter has capacity for 8-character callsigns from the appropriate transponder data register (at 6 bits per character, plus the 8-bit header).
-
As I am a flight planner, I can confirm that the maximum number of characters on the Flight ID is 7, anymore and it is either rejected by the ATC computers or it misses off the last character. If more are shown by an acft on RB then I am sure this an error but will not affect the filed plan.