Jump to content
Stephan Boerner

atc-discussion EuroScope S/GAATS configuration

Recommended Posts

Stephan Boerner

We have created an initial version of a SAATS/GAATS configuration. I have been using a similar setup for some Cross the Ponds now.

There are still some improvements planned, but it is yet too early to tell when they will be available. A PDF documentation is insider the .rar.

Share this post


Link to post
Share on other sites
Luke Cunningham

Looks fantastic! Thanks for that pal!

I'm sure you can utilise it well Robbie!

Share this post


Link to post
Share on other sites
Chris Pawley

This looks very nice Stephan,

Thanks for sharing - well done to all involved.

I might dust off my Shanwick validation and come out to play with this.

Chris

Share this post


Link to post
Share on other sites
Gunnar Lindahl

Looks great Stephan, thanks!

I might dust off my Shanwick validation and come out to play with this.

Excellent, thanks for volunteering Chris. We'll be seeing you bright and early on CTP day! :connie_08:

Share this post


Link to post
Share on other sites
Stephan Boerner

Just let me point out that it may take some time to getting used to no longer seeing the actual traffic, so if you are heading towards CTP, CTP probably should not be the first time to test this :no: But there are still some weekends to practice :thumbsup:

If you have any questions, feel free to ask.

Oh, and by the way: this package is probably going to replace the current GAATS configuration in CANscope, so after some time this should be used by Gander as well.

Edited by Stephan Boerner

Share this post


Link to post
Share on other sites
Stephan Boerner

Can someone else confirm this problem with a yellow screen? https://files.me.com/boerner/fre5u5

Share this post


Link to post
Share on other sites
Chris Pawley

Stephan,

Exactly the same happens for me...when connecting as CJP_INS with no primary frequency set (haven't tested any other combinations)

The yellow screen seems to disappear after a few seconds/minutes. Not sure how consistently.

Chris.

Share this post


Link to post
Share on other sites
Guest Michael Benson

Hello,

Is it possible to speak to the Aussies and incorporate their plug in so OCA controllers can use hoppies datalink?

Share this post


Link to post
Share on other sites
Scott Diamond

Can someone else confirm this problem with a yellow screen? https://files.me.com/boerner/fre5u5

Stephan, I believe if you click 'Symbology Settings' then 'Apply' when such a screen appears it goes back to normal. Not Shanwick rated so can't test that fix out.

Share this post


Link to post
Share on other sites
Stephan Boerner

Hello,

Is it possible to speak to the Aussies and incorporate their plug in so OCA controllers can use hoppies datalink?

Their plugin? Please specify :yes5:

There is another CPDLC plugin in development, so datalink will eventually be available, yes.

Stephan,

Exactly the same happens for me...when connecting as CJP_INS with no primary frequency set (haven't tested any other combinations)

The yellow screen seems to disappear after a few seconds/minutes. Not sure how consistently.

Chris.

Can someone else confirm this problem with a yellow screen? https://files.me.com/boerner/fre5u5

Stephan, I believe if you click 'Symbology Settings' then 'Apply' when such a screen appears it goes back to normal. Not Shanwick rated so can't test that fix out.

Can you say what vis range you were using?

Edit: the problem might be identified. Hopefully there will be a fixed version by the end of next week. It should definitrly be fixed until CTP.

Edited by Stephan Boerner

Share this post


Link to post
Share on other sites
Stephan Boerner

The package is updated. Please test it again, if everything is fixed now.

Share this post


Link to post
Share on other sites
Chris Pawley

Stephan,

Many thanks for the update.

No problems while observing with 1000nm range.

I'll try controlling tomorrow and report back any anomolies.

C

Share this post


Link to post
Share on other sites
Chris Pawley

A couple of hours this morning.

I think you raised this problem in the docs...estimates don't really work in 3.1d.....I can put them in via the flightplan...and that's fine but not via the list 5220N/1330z for example. Sometimes even in the flightplan ES doesn't like them and reverts back to it's own times...(could be when they're close to the edge...and correlated still.)

Works well though - really nice job.

Thanks again

Chris.

Share this post


Link to post
Share on other sites
Stephan Boerner

Entering them via the list doesn't work either? Hm, thought it was just not displayed ... have to test this again, but maybe then that's something else that will be just available with v3.2. I'll check it again.

Yes, the correlation at the edge is a problem. Estimates currently only work without correlation or a radar position, so for example you can not add an estimate while the aircraft is still under radar coverage, even though the estimated waypoint will be in an uncovered area; hopefully this can be changed for v3.2. Until then I plan to either add radar holes to the sectorfile or reduce the coverage information. Just haven't had time to change it yet, but it will be in the SCT update for CTP at latest.

Thanks for the test so far.

Edited by Stephan Boerner

Share this post


Link to post
Share on other sites
Stephan Boerner

I've just uploaded an update to the ESE. I replaced the complete eastern part of the sector data starting with EGGX, so if you find anything strange let me know.

Share this post


Link to post
Share on other sites
Stephan Boerner

I think you raised this problem in the docs...estimates don't really work in 3.1d.....I can put them in via the flightplan...and that's fine but not via the list 5220N/1330z for example. Sometimes even in the flightplan ES doesn't like them and reverts back to it's own times...(could be when they're close to the edge...and correlated still.)

I just tested this again with 3.1d and entering the estimates via the list item seems to work for me, they are just not displayed in the list, so as far as I can tell, it should work as described.

Concerning the reverting back to calculated times, I will do some more tests comparing 3.1d to the last beta, and I will provide another update to the setup probably tomorrow. But until ES v3.2 (or unless someone is using the beta), SAATS won't be fully functional, that is certain.

Edited by Stephan Boerner

Share this post


Link to post
Share on other sites
Stephan Boerner

The package is updated. This will be the final version for v3.1d. Every future changes and features that are not available in the current setup will just be available for the beta/v3.2 from now on. Of course SCT/ESE updates will be available via the automatic download.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

  • Similar Content

    • Paul McHutchison
      By Paul McHutchison
      Hello!
      It's been a very long time since I've been active on the controlling side (I'm pretty sure I was still a kid when I was most active, and I'm 26 now!) and I've been thinking recently that I'd like to get back into the swing of things. I had validations for Jersey Control and Heathrow Tower back in 2010, and though I'm sure the Heathrow one is useless these days, the Channel Islands are fairly straightforward and probably a good way for me to get back into it. I've just got a couple of questions which I searched for but had no luck:
      1) Am I allowed to just jump straight back in on Jersey or do I have to be revalidated?
      2) Is there an idiot's guide to setting up EuroScope from scratch anywhere? I resisted switching to it back in the day, and somebody set up my Heathrow profile for me so I'm really not sure of what I'm doing.
      3) (this is where I really show how hopelessly out of the loop I am) While I figure out how to get myself up and running on ES, am I allowed to use VRC as a stop gap? I would worry that its lack of tag features would maybe cause issues for coordination with LON_CTR.
       
      Thanks in advance for your help! I'm looking forward to getting some ATC time in, I've been flying again for the last 18 months or so and it's great to see such a high standard of ATC in the UK.
    • Dan Bishop-Adams
      By Dan Bishop-Adams
      Hi All,
      Following today's release of UK2000 Bristol 2019 HD, I thought I'd provide an update on the latest parking stand limitations - as this scenery includes some apron extensions and stand changes that won't be covered in the existing vMATS or indeed the sector file to an extent. This will also be useful for pilots choosing their stand when setting up for departure (or indeed arriving without ATC). 
      The aircraft type shown is the maximum type that can use that stand:
      Stands 1-3 - A321
      Stand 3R & 4 - B752
      Stands 5 & 6 - B738/A320
      Stands 7-9 - A320
      Stands 10-15 - A319
      Stands 19 & 20 - B738 
      Stand 21 - B733/F100/E190
      Stand 22 - B738/A320
      Stands 23-25 - A321*
      Stand 26 - B789/A333
      Stand 26S - B738/A320 (Cannot be used at same time as 26)
      Stands 28 & 30 - A321
      Stand 29 - B752
      Stand 31R - E145
      Stand 31 - A321
      Stand 32R - E145/AT72
      Stand 32 - B752
      Stand 32L - E195
      Stand 33 - B752
      Stand 33L - E195
      Stand 34 - A321
      Stand 35 - B738/A320
      Stand 36 - E145
      Stands 37-39 - A321
      (Bear in mind the multi-use of these stands, and which ones may block others)
      Overflow Stands (These are not to be used routinely, though some of them [Such as E2/W3/W5] could be used for additional heavy parking if 26 is occupied, but at the expense of blocking other stands):
      Stands E1-E3 - A321**
      Stands W1 & W2 - E145
      Stands W3-W7 - A321**
      *I have some conflicting information about stands 23-25, they used to be max B752 but the latest information I have states A321. I will check and update ASAP, as the documentation I am using has been misprinted before!
      **Stands E1/E2 & W4/W6 are used even more infrequently - in the real world, these are for departure only in very busy times and a/c are towed onto these stands. 
      Hope this is useful!
      Regards,
       
    • Chris Pawley
      By Chris Pawley
      Traffic Flow
      Traffic entering in the South West of the FIR will route towards Heathrow and Munich via the South coast and to Copenhagen and Warsaw via CPT and onwards.
      AC West is expected to see a large amount of inbound and overflying non-event traffic - for this reason - no inbound event traffic is routing via the BEDEK/KENET area.
       
      Traffic inbound at LIFFY and DEXEN will route to BNN for Heathrow, as well as to Amsterdam and Warsaw via LAMSO and into Scottish for Copenhagen. Some Copenhagen (via BPK) traffic will cross the Warsaw stream to LAMSO in the North Sea sector.
      Finally, traffic inbound to Heathrow will arrive via BEL & KELLY. This can be descended beneath the other streams.
      Daventry has mostly the responsibility to sequence for Heathrow arrivals. Clacton is staffed mostly for AMS <-> LHR city shuttlers
       
      Event Sectors
      Currently we plan to use the event split of AC West into North and South and AC North into Lakes and North Sea
       
      Neighbours
      Shannon is operating using this configuration: https://docs.google.com/drawings/d/1fQU_ksQkb-jAlJ6fOQlp7JxAYI0uajPSc1v9Ii8mITI/edit?
      Amsterdam plans to use an East/West split (no Maastricht Delta online)
      Brussels may be covered by Eurocenter vACC
    • Chris Pawley
      By Chris Pawley
      Traffic Flow
      Traffic entering in at MOLAK will split into three - one section to Copenhagen, one to Munich at LONAM and one to Amsterdam at TOPPA
      Traffic entering at NIPIT routes via BEL and KELLY into AC Lakes. This might need to be descended slightly early to go beneath traffic in their sector.
      Traffic routing towards Copenhagen from AC North will cross both Amsterdam and Munich inbounds, hopefully with Amsterdam traffic already descending towards TOPPA.
       
      Event Sectors
      Currently we plan to use the event split of Scottish East into North and South
      We will open West+Deancross combined and East.
       
      Neighbours
      Shannon is operating using this configuration: https://docs.google.com/drawings/d/1fQU_ksQkb-jAlJ6fOQlp7JxAYI0uajPSc1v9Ii8mITI/edit?
      Amsterdam plans to use an East/West split (no Maastricht Delta online)
      Copenhagen will use EKDK_N EKDK_V and EKDK_B
       

    • Martin Killner
      By Martin Killner
      Good Afternoon 
      Firstly, apologies if this topic is covered in other areas of the forum....I have carried out a search without a great deal of success. Secondly, this question has arisen after my inaugural full flight on VATSIM, from EGKK to EDDH on XP 11 with the FF A320, which was hugely enjoyable and fretful all at once.
      The majority of learning has been gained from "apron listening" to the various procedures. The one item I faced without any prior experience was the descent procedure. 
      As you know, the MCDU will give me a TOD point. I am happy that a radar or director controller will probably not be aware of this point and I will need to request it. This first flight resulted in a late descent pattern resulting in vectors to shed altitude, which I achieved readily enough. I was helped enormously by a very patient and understanding director and tower controller at EDDH...(Flight taken on 24/10/19 at about 1700Z. Thank you, by the way). 
      The question is: How far in advance of TOD should I carry out initial call up, (I am using the VATSIM P1 phraseology guide), to radar to assist in my calculated descent path, and is it acceptable to inform a controller if I anticipate a too steep a path due to control lags, (or most likely my incompetence)?
      p.s. Happy with the concept of track miles btw....
       
×
×
  • Create New...