Eivind Fosse 818131 Posted April 22, 2011 at 04:39 PM Posted April 22, 2011 at 04:39 PM Hi, I have a problem programing the correct COPX lines in the ESE file. Please take a look at the attached picture: LTR01, a B737 from Sweden is inbound Gardermoen, ENGM. Sweden Control (ESOS3) is online, the same is Gardermoen APP (ENOSTE). I control Oslo control sector 2 (ENOS2). LTR01 is currently in Sweden Sector 3. On his way to ENGM he will enter Area TEKVA, a small airspace Sweden control, but what can be delegated to Oslo sector 2 if needed. After Area TEKVA LTR01 will briefly enter ENOS2 before finally arriving in ENOSTE sector controlled by Oslo APP. The LoA between Norway and Sweden instructs Sweden sector 3 to descend traffic inbound ENGM to FL250. The LoA between Oslo sector 2 and Oslo APP instructs Oslo sector 2 to clear flight inbound from east to FL110 and ESEBA1M arrival. To make the story short I would like to enter these two LoAs in the ESE so that I, the Oslo sector 2 controller, will see LTR01 as PEL 250, COPN ESEBA, COPX EPAPI, XFL 110. This is what I currently have in the ESE file: COPX:*:*:EPAPI:ENGM:*:ENOS2:ENOSTE:*:11000:EPAPI COPX:*:*:ESEBA:ENGM:*:Area TEKVA:ENOS2:*:25000:ESEBA The 2nd line works fine actually. I see LTR01 as PEL 250 and COPN ESEBA, however nothing is written in COPX and XFL has the requested FL, 360. As LTR descends towards EPAPI (the border between ENOS2 and ENOSTE), I can briefly see EPAPI as COPX and 110 as XFL. This will last for a few seconds before returning to COPX 360 again. Some time later it will return with correct COPX and XFL for a few seconds. For some reason the LoA information will not stay. Any ideas? Thanks Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted April 22, 2011 at 04:54 PM Posted April 22, 2011 at 04:54 PM Shouldn't ESEBA been COPN, not COPX, as it is a entry point for you. Also does your tag have both the COPN/PEL and COPX/XFL items separately? EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Eivind Fosse 818131 Posted April 22, 2011 at 05:36 PM Author Posted April 22, 2011 at 05:36 PM Todor, The tag has the Sector Entry/Exit Point Name and Sector Entry/Exit Altitude items. As you can see in the picture both on the tag and the Sector Inbound List, ESEBA is actually COPN as is correct and expected. The entry altitude FL250 is also displayed (both in the list and to the very right in the tag's 3rd line). This is also correct. However. As you can see in the Sector Inbound List, the COPX nor XFL is displayed correctly... Eivind Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted April 22, 2011 at 06:59 PM Posted April 22, 2011 at 06:59 PM Is the COPX shown when the track is inside of ENOS ? EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Eivind Fosse 818131 Posted April 22, 2011 at 08:41 PM Author Posted April 22, 2011 at 08:41 PM Is the COPX shown when the track is inside of ENOS ? Both yes and no. It may appear for a few seconds, but then disappears again Just like it happens in both ESOS3 and Area TEKVA sectors... Please take a look at the pictures below (taken from a sim session I've made to illustrate the problem). Still inside ESOS3 sector, handed over to me ENOS2. Displays correct COPX EPAPI and XFL 110 Seconds later the COPX and XFL disappears as shown in this picture when the aircraft is inside Area TEKVA. A few moments later, still inside Area TEKVA, the correct COPX and XFL appears again: And disappears again... After entering ENOS2 sector, the correct COPX and XFL is displayed the last time for a few seconds again Before disappearing for good moments later: When inside ENOSTE sector the correct COPX and XFL is never displayed again: Thanks for watching. Link to comment Share on other sites More sharing options...
Eivind Fosse 818131 Posted April 24, 2011 at 07:39 AM Author Posted April 24, 2011 at 07:39 AM Any ideas please..? Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted April 24, 2011 at 07:55 AM Posted April 24, 2011 at 07:55 AM Sorry Eivind I was away for one month, send me the sector file, asr and if you have a a scenario file to test it. EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Eivind Fosse 818131 Posted April 24, 2011 at 08:58 AM Author Posted April 24, 2011 at 08:58 AM Thanks, Mail sent Link to comment Share on other sites More sharing options...
Ervins Reinverts Posted December 19, 2011 at 09:23 AM Posted December 19, 2011 at 09:23 AM Hi all, I am wondering if this got sorted out, as I recently saw something that I feel *MIGHT* be related. I was controlling Baltic sector (BALT_CTR) during Fly and see Santa 2011 and next sector was Tampere Radar (EFES_2_CTR). Most of the traffic went to Finland through the INTOR intersection and in our case, it is not defined in our sector file as COPX point, as there are no specific rules to apply. Still, the tag alternatively show me that the next controller would be EFES_2 (or relevant frequency if close enough) and after some time switches to -- and unicom frequency respectively, then it switches back to EFES_2 and then again to unicom. Looks like a pretty similar behaviour, so it might be something not related to COPX definitions in particular, but something a bit more general. Ervins C1 controller EVRR & EETT FIR; BALT, EURN & EURE UIRs Follow EVRR_FIR on Twitter at http://twitter.com/evrr_fir Link to comment Share on other sites More sharing options...
Eivind Fosse 818131 Posted December 19, 2011 at 12:39 PM Author Posted December 19, 2011 at 12:39 PM No... Unfortunately the issue has not been resolved. At least I'm not aware of any solution to the problem... Link to comment Share on other sites More sharing options...
Gergely Csernak Posted December 21, 2011 at 08:08 PM Posted December 21, 2011 at 08:08 PM Next time you see something similar, please use the position prediction tool to understand what is going on. Press the current altitude TAG item with left button twice (not doubleclick!). Then all predicted points with calculated controller and profile altitude is displayed along the route. I guess you will see why and how ES decides the next controller. The flickering behavior is common when there is a small niche between sectors and accidentally ES uses a prediction point that is not inside any sector. Gergely. EuroScope developer Link to comment Share on other sites More sharing options...
Recommended Posts