Euroscope not determining Squawk Ranges from ESE File

[Shujaa Imran]

Hi,

 

I'm facing a problem in my latest ESE file update for my vACC's sector file, Euroscope does not determine the squawk range of different ATC Facilities as defined in the ESE file, and uses the default range (2600 - 2677), the squawk range in the [POSITIONS] section is defined as below:

 

 

Euroscope is reading SIDs/STARs normally from the same ESE file. Any idea guys what is the issue is?

 

Thanks

[Jonas Kuster]

Is this a problem in general or only for certain positions (like when you are on radar and covering different airports and squawk ranges)?

The ES wiki (http://www.euroscope.hu/mediawiki/index.php?title=ESE_Files_Description#The_Positions_Section) also says that the items 8 and 9 are not used, so no data is required there.

What did you change since your last version? Did the squawk ranges work before?

[Shujaa Imran]

Is this a problem in general or only for certain positions (like when you are on radar and covering different airports and squawk ranges)?

The ES wiki (http://www.euroscope.hu/mediawiki/index.php?title=ESE_Files_Description#The_Positions_Section) also says that the items 8 and 9 are not used, so no data is required there.

What did you change since your last version? Did the squawk ranges work before?

 

It's a problem for each ATC facility in the ESE file. We only have 2 Radars in the airspace, and all the airports under each radar have the same squawk range.

 

Will remove those. Nothing was changed in the Positions section since the last update, but in this latest update, the visibility centres also aren't being picked up from the ESE file.

 

And yes, both the squawk ranges and visibility centres worked in the previous update. The only difference b/w the two is that we had a long intro in the previous file, which we removed in the latest update (i.e the file starts directly from the [POSITIONS] tag as in the screenshot above)

 

Any help?

[Sachin Gnath]

Hello Shujaa,

 

Could you try by replacing in this format. Hope this works.

 

OPKR_CTR:Karachi Control:123.900:KC:C:OPKR:CTR:OPKR:CTR:7400:7477

[Shujaa Imran]

Hi Sachin,

 

Tried, no luck.

[Gergely Csernak]

Was your position successfully identified? Did you see your sectors allocated?

[Shujaa Imran]

Was your position successfully identified? Did you see your sectors allocated?

 

Unfortunately no, it isn't identifying the sectors as it did in the last version. And the thing is, we didn't touch this part a bit, surprised why it isn't working.

[Gergely Csernak]

Someone just sent me his ESE file with the same kind of problem: No position was identified. I figured out the he saved his ESE file with encoding: UTF-8 with BOM. That adds some 4 special character to the beginning of the file. As ES opens the ESE file as plain ANSI file it does not recognize the [POSITION] entry, and the whole section is ignored.

 

So try saving as ANSI or add an empty first line that can be discarded.

[Shujaa Imran]

That seemed to be the issue, fixed now, working perfectly. Thanks