Missing callsigns

News and information about what new functionality and developments lie ahead for SBS systems and BaseStation.

Moderators: admin, KineticChris, KineticDavid, Moderators

micione1941
Posts: 2
Joined: November 22nd, 2012, 8:55 am

Missing callsigns

Postby micione1941 » December 7th, 2012, 8:52 am

I was running BS v175 and I noticed that many callsignn of non-ADS-B
aircraft were missing.

I did not pick up responses because non-ADS-B aircraft do not send
aircraft ID (callsign) squitters, so they need to receive an ELS
interrogation from a ground radar to send their callsign and
interrogations are not frequent.

Now I run BS V146 and I notice that the chances of missing callsigns are
much lower compared to newer BS versions.

RELEASE NOTES of BS v159 report:
Improved the handling of squawk codes and callsigns for non-ADS-B
aircraft to reduce the likelyhood of assigning a code to the wrong
aircraft.
This is because these codes are obtained from Mode-S radar surveillance
replies which have less built-in error checking than ADS-B messages.

For squawk codes and call-signs of non-ADS-B aircraft, BaseStation waits
until three identical values are received within a 30-second period.

It will take longer for call-signs to appear for non-ADSB aircraft,
especially at the limits of coverage.

The 30 seconds period seems too short to me, and I think that it would be
better let the user choose that timeout.

Regards
Roberto

User avatar
bones
Posts: 9737
Joined: August 8th, 2005, 4:44 am
Location: Isle of Man
Contact:

Re: Missing callsigns

Postby bones » December 7th, 2012, 9:33 am

Likewise I have gone back to using Basestation 155 because later versions record no value for First Squawk.

The fix was an attempt to cure the transposed callsigns problem - callsigns for one aircraft being recorded in another aircraft's record. This was bad and needed fixing but the solution has its drawbacks too.

micione1941
Posts: 2
Joined: November 22nd, 2012, 8:55 am

Re: Missing callsigns

Postby micione1941 » December 10th, 2012, 1:20 pm

I agree that a fix to cure the transposed callsigns problem was needed,
but only to be used in areas where the problem exists.
In year 2012 I have been running BS v146 in two locations:
45.85N 9.40E - 50km NE of LIN
44.18N 9.58E - 50km SE of GOA
where many CRJ of Air France and Lufthansa are overflying and I never
found callsigns for one aircraft being recorded in another aircraft's
record.
That being stated I am convinced that it would be better let the user
choose the timeout according to his needs.
Roberto


Return to “News / Announcements”

Who is online

Users browsing this forum: No registered users and 2 guests