kusterjs / ccams Goto Github PK

Hi.
I'd like to ask to include EPWW FIR squawk code ranges for airports. That will allow Polish vACC to implement this plugin.

Our current assigned squawks are:

• TMA Warszawa (EPWA, EPMO, EPLL): 4550 - 4577
• TMA Gdansk (EPGD, EPBY): 4530 - 4537
• TMA Poznan (EPPO, EPWR, EPZG): 4520 - 4527
• TMA Krakow (EPKK, EPKT): 4540-4547
• Other procedural TMAs (EPLB, EPRA, EPRZ, EPSC, EPSY): 4500-4517

If the TMA runs out of its own pool it can get a free valid code from FIR pool (4500-4577).
We also use a reserve pool of 4000 - 4077 but now with Mode S we haven't seen it used in a long time.

Description: Incorrect squawks generation for SARR

Position: SARR_CTR

Actual behavior

• For a SARE/SABE flight, it generated 2050
• For a SARE/SCEL flight, it generated 2701

Expected behavior

• For a SARE/SABE flight, it should generate squawks between 2100/2137
• For a SARE/SCEL flight, it should generate squawks between 0600/0677

Version: 1.7.0

Extra information
The SSRs that its generating right now are from SAMF, maybe there was a confusion while setting the ranges?

Add a new routine to check for new version and inform the user accordingly, recommending to update his plugin version (before it is disabled).

Hi Jonas,

I would like to add in VCL vACC to use CCAMS.
Following are the Squawk Codes we use:
FIR squawk codes(used by CTR and other positions within the FIR not assigned a squawk code range)
VDPF FIR: 16xx
VLVT FIR: 02xx
VVHN FIR: 17xx
VVHM FIR: 56xx

Aerodrome squawk codes(used by positions up to APP):
VVNB: 46xx
VVTS: 57xx

VCL_CTR (special bandbox covers all 4 FIRs top down):
33xx

Do let me know if the above is feasible, or if there are anything else I should know about. Thank you!

So... maybe other way round.
Is it possible to have another function in the menu to assign a discrete code no matter the Mode-S status of the flight (just like we assign VFR codes)?

Originally posted by @laxentis in #23 (comment)

Right now, CCAMS would generate a completely random squawk for an international arriving traffic since it doesn't match with any of the provided ranges.

It would be great to select a squawk from the arriving FIR's international range.

Non show stopper at all!

Hi!

Something similar to the TopSky area-assignment rule would be nice to have for us in Germany. We would use it to assign non-discrete Squawks to VFR traffic using FIS service in specific areas. As every FIS sector is assigning a specific Squawk the area definitions would be bound to the FIS sectors. Plugin would have to check whether Traffic is VFR and within that area, then assign the correct FIS squawk. Also the FIS squawks are not used for radar identification normally, but to make clear that traffic is under "control" of the FIS operator - so they would be given to all VFR traffic within the area despite of the Mode S capabilities.

Would something like this be implementable?

Hello,

I would like to implement the Airport codes of RG Bremen (EDWW)

Our Ranges:

EDDH: 2500 - 2527
EDDW: 2430 - 2447
EDDV: 2420 - 2427
EDXW, EDHL, EDVE: 2530 - 2536
EDHI, EDVK: 2546 - 2554

Thank you for your work!

Kind regards
Chris Gutierrez NAV RG Bremen

Hi,

Can you please consider removing the check of equipent filed by the pilot.
A lot of pilots have no clue what the equipment field is and a lot of them just leave it empty. Due to the fact that ModeS transponder is mandatory almost everywhere in the CCAMS area it's maybe not a bad idea to just remove that check on EQ.
An other idea is that you do a check on Requested FL. If the RFL is above FL195 you can be sure that the airplane is ModeS capable even if the equipment is empty or wrong.

Thanks!

Erik

Request by Teodor-Gabriel Petrica

LRBB: 5401-5477
LUUU: 2270-2277

Awaiting VATEUD confirmation.

All of Italy is squawk 1000 capable. That includes LIMM, LIPP, LIRR and LIBB. To generalise, you can edit the compatible ICAOs to 'LI' so that every italian airport is compatible. Thanks!

Auto assignment of codes should be limited to clients where the active controller is identified to be the next controller (or latest when a controller starts tracking an aircraft).
In return, also non-1000 squawks may be assigned this way.

Hey,
would it be possible to have the server return a random available squawk from the range rather than the (numerically) first one available?

Would like capility for norwegian airports please

Getting ERROR E411 with latest version 2.3.0

Hi!

Would it be possible to add an extra squawk code retention error indicator to the plugin?

The plugin would check if a modeS squawk has been falsely (not capable, not fully through modeS area) given by a controller not using the plugin. In EBBU airspace we are required to change transponders with squawk 1000 going to London (misuse of modeS). For us, they are well correlated and thus we don't notice anything wrong with the track, however for London these aircraft are not correlated and this creates issues.

An error indicator, similar to the well known DUPE error, would allow us to notice misusue and reclycle to a new, valid squawk.

Obviously such error would not exist in real live as squawks are centrally managed by Eurocontrol, and most importantly, because everyone uses said system. Therefore, you could reuse the DUPE error to maintain a certain level of realism or create a different error indicator to easily distinguish the two.

Hey Jonas! Thank you for your amazing work with CCAMS.
We are looking to extend it so it works with our rules of transponders. Those are:

• Range per FIR (we have 5 of them)
• Range per type of flight (national, international or VFR)

It would be something like this:

Even if it requires some coding, what are your thoughts on this? How could we manage to implement that logic to generate a ssr that correctly corresponds to the flight?

Thank you so much in advance!

LTAA & LTBB FIR callsigns changed and my contrellers report CCAMS not assigning from the ranges.

Callsigns are now

Prefix: ANK
ML:
LTBB;

• 1, 2, 3, 4, 5, 6
• W, WN, WS

LTAA:

• 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19
• N, C, S, E, EN, ES, A

Probably due to prefix CCAMS not assign squawks from the predifined ranges.

Handle the case when a code cannot be assigned because the aircraft is tracked by another controller. Check possible alternates and behaviours.

Hi

I only just recently noticed the plugin does not write the whole "Set squawk 1000" when dealing with text pilots. I assume you are aware of it and think there's no way around it.

The UAC Plugin, also from Pierre F., provides this functionality. Perhaps it's a good idea to have a look there. It is possible one way or another.

Kind regards

EFPS and EFES have been replaced by EFIN

0500-0577

Hello,

I have conducted a Sweatbox session and the student assigned four different squawk codes which I can find now as used in the reserved codes list.

The data below is taken from the reserved codes list.

1454	2023-08-24 17:15:50
4066	2023-08-24 17:31:26
1215	2023-08-24 17:32:17
7710	2023-08-24 17:39:28

All these squawk codes were assigned on Sweatbox, but they are also reserved for VATSIM servers.

Previously, we had a similar situation, in the Sweatbox session there were assigned squawk codes in range 1701-1711, and online, the first code available was 1712.

Any advice on this?

Regards,
Teodor G Petrică

Euroscope currently supports assigning squawks with F9. It places the ".QB" command on the command line and you can either manually input a squawk, or if you just hit enter it will auto assign a squawk according to the range set in the general settings.

Link to documentation; https://www.euroscope.hu/wp/editing-and-function-keys/

As this plugin has an overview of all assigned SQ codes, would it be possible to assign a code based on the real world codes depending on departure and destination aerodrome? For sure that should be in coordination with VATEUD.

Maybe with some priorities for the different ranges there could be a way how both ways of SQ assignment (with and without this plugin) could be used, as there are several area that would not interfer with each other at all (e.g. europe and america as you need to set SQ 2000 over the atlantic anyway).

Maybe that could bring the next small step of realism into the Vatsim world.

These codes are available on the eurocontrol website here: https://www.eurocontrol.int/publication/secondary-surveillance-radar-code-allocation-list-icao-eur-region-cal

Can we exclude an airport in FIR from being mode S capable?
Our military fields do not support mode S (yet, and are not planned in near future) so any flight going to EPCE, EPDA, EPDE, EPIR, EPKS, EPLK, EPLY, EPMB, EPMI, EPMM, EPOK, EPPR, EPPW, EPSN, EPTM should be given discrete SSR.
Our FIR is included as per #15

Hi Jonas,

as we like to use your plugin for squawk assignment, could you please add the airport-ranges of RG München (EDMM):

EDDM: 2300 - 2337
EDDN: 2340 - 2353
EDMA EDMO: 2370 - 2377

Thanks!

Jannik

• NAV-Team RG München

Upon starting tracking an aircraft with a squawk code marked as DUPE, a new code request should be created to replace the assigned code with a unique code.

The VATEUD squawk range for Germany is 2001 to 2577. In my understanding these should be assigned first, before other squawks are assigned. However the plugin assigns just random free squawks (that are correctly entered into the list of used squawks).

Hi!
Is it possible you forgot to update the version number?
I'm pretty sure I downloaded version 2.3.1 but it still shows 2.3.0 in the plugin screen and in the message box.

Thx, Erik

Re-check squawks already assigned but not yet set and request new ones when a duplicate has already been created (by another controller now aware of the already assigned code).

Description: Incorrect squawks generation for SAMF

Position: SAMF_CTR

Actual behavior

• For a SAME/SABE flight, it generated 2045
• For a SAME/SCEL flight, it generated 2501

Expected behavior

• For a SAME/SABE flight, it should generate squawks between 2050/2077
• For a SAME/SCEL flight, it should generate squawks between 2700/2777

Version: 1.7.0

Extra information
The SSRs that its generating right now are from SACF, maybe there was a confusion while setting the ranges?

The departure airport should also be considered when determining whether code 1000 shall be assigned. If the controller does not wish to overwrite the "global" definitions of regions that are mode S capable, this would then make the options "acceptFPLformatXXX" superfluous.

Hi,

in vACC-CZ (LKAA) we use following squawk ranges:

LKPR: 1420 - 1447
LKAA (used by CTR for overflights without assigned squawk): 1450 - 1467
LKCV, LKKU, LKKV, LKMT, LKNA, LKPD and LKTB all share 1470 - 1477

Can you please add those to Airport code ranges?

Thank you

Find a way to link the fancy 3-letter codes used in certain FIRs to FIR code ranges. Similar support might be necessary on the airport level.

Hello,
Could you update our squawk range as described below?

Most important:
LRxx international IFR departures: 5401-5477 and 2640-2677
LRxx domestic IFR departures: 4001-4077

Less important:
LRxx domestic VFR departures: 6701-6777 and 0001-0017
LRxx domestic OAT: 3601-3677 and 7401-7477

Thank you,
Teodor [ACCRO7]

Description: Incorrect squawks generation for SACF

Position: SACO_APP

Actual behavior

• For a SACO/SABE flight, it generated 2104
• For a SACO/SLVR flight, it generated 0607

Expected behavior

• For a SACO/SABE flight, it should generate squawks between 2001/2047
• For a SACO/SLVR flight, it should generate squawks between 2500/2577

Version: 1.7.0

Extra information
The SSRs that its generating right now are from SARR, maybe there was a confusion while setting the ranges?

We found 2 issues while testing this plugin:

1. SSRs around Ezeiza FIR (SAEF) seems to be working fine, but Mendoza FIR is not generating the correct transponders for all departures and the same happens with international departures from Cordoba FIR. Comodoro (SAVF) and Resistencia (SARR) are having problemas as well.
2. International arrivals would generate a random SSR - is there any chance of assigning a squawk from the arrival FIR's international range?

And also, kind of a feature request, it would be great to have the possibility of generating the squawk with F9 (it would need to override Euroscope's default functionality).

Again, thank you so much for your hard work! This is incredibly great for our division, we really appreciate your effort.

Hello,
I tested the new version yesterday but it doesn't seem to work as it should.
I controled the EBBU EAST sectors so I was completely surrounded by ModeS 1000 area. Every time I got a flight which didn't leave in a sq1000 area from one of the neighbors I got an MSSQ warning to set a local SQ. Actually, this was not necessary as the 1000 had already been given by an upstream sector that knew that the flight from him would turn out to be in 1000 area.
ex: flight KJFK to ELLX. The flight departed NON SQ1000 area but a 1000 was assigned by EBBU WEST (which is sq1000 area). When the flight came with me I got the MSSQ warning to set a local SQ altough the flight was never to leave SQ1000 area again.
Normal behaviour should be that if the flight has 1000 and it comes from and goes to SQ1000 area, it should keep 1000.

Thank you for the great work!

E.

0700-0777

Hello,

From yesterday, problem when french ATC requesting a squawk code

On website, only NIL
https://ccams.kilojuliett.ch/