[POSITIONS] in .ESE

[Emiliano Ferraco]

Hi, I´ve a doubt concerning positions in the .ese file.

 

We have 5 FIRs, each one with differents range of transponder codes, of course, but at the same time, each one has 3 variables: for international flights, local flights and VFR flights. Like this:

 

 

ACC INTERNATIONAL LOCAL VFR

EZEIZA 0300 - 0377 1500 - 1577 0030 - 0037

0400 - 0477 1600 - 1677

0500 - 0577 1700 - 1777

CORDOBA 2500 - 2577 2001 - 2047 0050 - 0057

MENDOZA 2700 - 2777 2050 - 2077 0040 - 0047

RESISTENCIA 0600 - 0677 2100 - 2137 0060 - 0067

COMODORO 0700 - 0777 2140 - 2177 0070 - 0077

 

 

 

So, my Positions section is like this

 

SAVF_N_CTR:Comodoro Centro:125.500:CMN:C:SAVF:CTR:-:-:2140:2177

SAVF_S_CTR:Comodoro Centro:125.700:CMS:C:SAVF:CTR:-:-:2140:2177

SAMF_CTR:Mendoza Centro:126.600:MEC:M:SAMF:CTR:-:-:2050:2077

SARR_CTR:Resistencia Centro:124.300:REC:R:SARR:CTR:-:-:2100:2137

SACF_N_CTR:Cordoba Centro:125.100:CON:O:SACF:CTR:-:-:2011:2047

SACF_S_CTR:Cordoba Centro:126.500:COS:O:SACF:CTR:-:-:2011:2047

SAEF_N_CTR:Ezeiza Centro Norte:125.600:EZN:E:SAEF:CTR:-:-:1500:1577

SAEF_S_CTR:Ezeiza Centro Sur:124.100:EZS:E:SAEF:CTR:-:-:1500:1577

SAEF_R_N_CTR:Ezeiza Radar Norte:124.500:ERN:E:SAEF:CTR:-:-:1500:1577

SAEF_R_S_CTR:Ezeiza Radar Sur:125.200:ERS:E:SAEF:CTR:-:-:1500:1577

 

Thats define with local flights range of code. So, I need to define again each FIR with international range of codes?

[Stephan Boerner 945550]

No, without a plugin ES only supports one squawk range, and ES will always pick the first matching entry in the file.

 

There is the UK [Mod - Happy Thoughts]istant plugin that deals with squawk [Mod - Happy Thoughts]ignments based on routings. Maybe you can have a look at it if you can use that for your purpose. Not sure if it can be customized for areas outside of UK.

[Emiliano Ferraco]

Thank you Stephan. I´ll have a look to it.

[Emiliano Ferraco]

Hi, another question from the positions section: if a position (for example SABE_TWR) use to use more than one frequency, it is possible to define it twice, with exactly the same parameters but differente freq.? So that in case ATC use either one of them, the position will always be recognized...

 

SABE_TWR:Aeroparque Torre:118.850:AET:T:SABE:TWR:-:-:1500:1577 -->normal operations

SABE_TWR:Aeroparque Torre:128.850:AET:T:SABE:TWR:-:-:1500:1577 -->auxiliary1

--> auxiliary2

[Kent Dong 1191810]

I think you should use a different position identifier (e.g. "AET2") for the secondary frequency.

[Emiliano Ferraco]

I think you should use a different position identifier (e.g. "AET2") for the secondary frequency.

 

Yes.. I thought that, but I wonder if there would be any conflict if I define them with different freq but the same ID... because, defining them with the same ID may simplify things with the OWNER [Mod - Happy Thoughts]ignments priorities.

[Miguel Frias]

Hi, another question from the positions section: if a position (for example SABE_TWR) use to use more than one frequency, it is possible to define it twice, with exactly the same parameters but differente freq.? So that in case ATC use either one of them, the position will always be recognized...

 

SABE_TWR:Aeroparque Torre:118.850:AET:T:SABE:TWR:-:-:1500:1577 -->normal operations

SABE_TWR:Aeroparque Torre:128.850:AET:T:SABE:TWR:-:-:1500:1577 -->auxiliary1

--> auxiliary2

 

 

Emiliano I would suggest using:

 

SABE_TWR:Aeroparque Torre:118.850:AET:T:SABE:TWR:-:-:1500:1577

SABE_1_TWR:Aeroparque Torre:128.850:AE1:T:SABE:TWR:-:-:1500:1577

 

In the owner do something like:

 

SABE_TWR:AET:AE1:...