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

    • James Brierley
      By James Brierley
      Dear all,
      I am pleased to announce we have made a new Stand Allocation Sheet.
      https://community.vatsim.uk/files/downloads/file/163-manchester-egcc-crib-sheet/
      With thanks to Leon Grant and Matthew Moy for their contribution in this - any questions, please don't hesitate to email us.
      Many thanks,
      James
    • James Gibson
      By James Gibson
      Please see information on LARS in the UK (particularly Farnborough LARS) in advance of the FIS Afternoon event but also because recently Farnborough LARS is opened much more frequently on the network. I am not a real world controller and so I do not claim to be 100%, but with my personal experiences as a pilot, I have tried to make this information as accurate as possible.
      What is a LARS (Lower Airspace Radar Service)?
      A Lower Airspace Radar Service (LARS) is a free service available to all aircraft for the provision of the radar element of UK Flight Information Services (UK FIS). This is usually available within approximately 30 nm of each participating Air Traffic Service (ATS) Unit to all aircraft flying outside controlled airspace up to FL100, within the limits of radar/radio cover. (ref. CAA website)
      Simply put:
      "Farnborough Radar" (LARS) provides non-radar (i.e. a basic service(VFR or IFR)) and radar services (e.g. traffic (VFR or IFR)/deconfliction (IFR only) services) outside of controlled airspace within the diagram Ben has posted above, usually up to about FL100. 
      Farnborough Radar is responsible for the EGLF (the aerodrome itself) and can provide a MATZ crossing clearance for RAF Odiham.
      General Information
      The ATS unit's callsign is "Farnborough Radar" and covers all three LARS sectors (W, N and E) in the south-east on VATSIM using the frequency 125.250 MHz. See diagram below:
       
      1. PILOTS
      Passing VFR details:
      Pilots of aircraft inbound or outbound to an aerodrome, or which to obtain a flight information service, when instructed to pass their message details, should respond in the manner described as follows below.
      The first call should be: "Farnborough Radar, [CALLSIGN], request [BASIC/TRAFFIC] service."
      Then wait for a response: for example, "[CALLSIGN], Farnborough Radar, pass your message. "
      Generally, this format can be applied to visual flight rules (VFR) and instrument flight rules (IFR) aircraft.
      Aircraft Callsign and type Departure point and destination Present position Level/Altitude Additional details/Intention (e.g. flight rules, next route point) Request (What service are you requesting?) General Information
      The ATS unit's callsign is "Farnborough Radar" and covers all three LARS sectors (W, N and E) in the south-east on VATSIM using the frequency 125.250 MHz. See diagram below:

       
      What is a basic service?

       
      What is a traffic service?

      What is a deconfliction service (IFR only)?

       
      2. CONTROLLERS
      This is particularly aimed at all A/G, AFIS and tower positions that are controlling adjacent/beneath Farnborough Radar. 
      VFR aircraft do not need to be coordinated if they are to remain outside of controlled airspace and clear of any airspace that is not Farnborough's interest IFR aircraft should be coordinated The majority of uncoordinated aircraft should be handed off to the radar position as "Free-call" where details of the flight must be passed to the controller over R/T again by the pilot.  
      References:
      AIP (See textual information for information on LARS)
      CAP 413
      CAP 774
      LARS Frequencies
       
      Recommended Read: Farnborough LARS Guide
      Any questions please do ask below (happy to discuss!) but I thought this may help and encourage pilots to start trying new things (which actually tend to be easier than your typical Airbus/Boeing flight)!
      I hope this helps.
      James
    • Harry Sugden
      By Harry Sugden
      Oooo, "cleared RNP approach runway 26L" soon come! 😎
      rnav to rnp.pdf
    • Sebastian Wheeler
      By Sebastian Wheeler
      Just a slight query related to the above:
      I was fortunate enough to partake in a weeks worth of work experience with NATS recently, and while at whitely on the ADC sims, I heard the following phraseology being used "G-ABCD, Cleared to enter controlled airspace via Route A, at or below altitude 2000 feet, QNH 1014."
      Upon asking one of the pseudo-pilots about the change, I was told it is "new phraseology" can anyone else confirm whether this is the case? Apparently, it was put in place after some confusion from pilots after receiving a "not above" clearance.
    • Steve Riley
      By Steve Riley
      Just reading the new sid charts , am I right in saying hand offs are going to LONDON or SCOTTISH  and not radar as no mention of Radar on the charts.
      2. After departure, aircraft shall remain on the Tower frequency until instructed. 3. En-route cruising levels will be issued after take-off by 'London Control'. 4. Report callsign, SID designator, current altitude and cleared level on first contact with 'London Control'.
      I have not got the old charts to confirm this as I take them straight from NATS web site. 
      Also frequencies have changed are we changing them within ES ?
        123.980, 131.005  BIRMINGHAM APPROACH/RADAR
        118.305  BIRMINGHAM TOWER
      121.805  BIRMINGHAM GROUND 
       

       
       
×
×
  • Create New...