Question about squawk (SSR) in tag, since V2.5

Marcel Ritzema (810369)

Hello,

Have a question, noticed since we (Dutch VACC) started using V2.5 instead of V2.4 there i looks like there is a different behaviour of the SSR code show in the TAG. Note i'm a military controller and use the tag's a little bit different then the civil controller so they do not notice it so far.

On the ground i now always see the assigned SSR code in the top of the TAG.

As soon they are airborn it goes away, if the pilot has the correct SSR dailed in.
If the pilot has the wrong SSR dailed in, the "D" of disagree start to show (yet it did not show on the ground).

Lands the plane again, the SSR pop's up again.

Example 2 aircraft:

DIAMO05 has correct 3705 (SSR shows in tag)
GRIZLY has assigned SSR 3601 in the tag, you still on 1200 (D is not shown)
As soon as both are airborne:
DIAMO05, the 3705 goes away
GRIZLY, the "D" shows up and 3601 stays.

Reference, same situation with "non-topsky tag":

Is this behaviour new in V2.5, or am i image things and was this already there in V2.4?

Kind regards,

Marcel

Juha Holopainen (839337)

I don't remember whether there was a change in this behavior, but the observed results seem reasonable - the label item displays the assigned SSR code for tracks not observed to be squawking the correct code. "D" is the duplicated SSR code warning.

Marcel Ritzema (810369)

Juha Holopainen (839337)

D of duplicate makes sense, think there where more aircraft swk'ing 1200 around that time.

Again the DIAMO05 has his correct swk tuned (see the non-topsky screenshot).
The label-item SSR on the TAG seems now only being triggered that the aircraft is on the ground?

Marcel

Juha Holopainen (839337)

The plugin does not know if the aircraft is on the ground or not. It only checks if the flight plan has an assigned squawk, and a transponder reply with the same code is received from the correlated radar track. If that is not the case (either some other code is received, the flight plan is correlated to a primary radar track, or not correlated to a radar track at all), the label field displays the assigned code. Should you not want to see the field in the primary and/or flight plan track labels, you'll need to edit the tag family accordingly.