ATC-pie: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
mNo edit summary
(v1.8.8)
 
(84 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{forum|83|ATC-Pie support & development}}
{{about|the software and its features|help with installation or configuration|ATC-pie installation guide|a manual on how to use it|ATC-pie user guide}}
{{Infobox Software
{{Infobox Software
| title                  = ATC-pie
| title                  = ATC-pie
| logo                  = ATC-pie-logo.png
| logo                  = ATC-pie-logo.png
| image                  = ATC-pie-screenshot-KSFOmess.png
| image                  = ATC-pie-screenshot-towerViewing.png
| alt                    = ATC-pie at the KSFO mess
| alt                    = Tower viewing, following a departing aircraft
| developedby            = Michael Filhol
| developedby            = Michael Filhol
| initialrelease        = Febuary 1, 2015
| initialrelease        = February 1, 2015
| latestrelease          = Febuary 1, 2015
| latestrelease          = 1.8.8 (April 1, 2023)
| writtenin              = Python3
| writtenin              = Python
| writteninversion      = 3
| os                    = Any
| os                    = Any
| platform              = Qt5
| platform              = Qt5
Line 13: Line 18:
| type                  = ATC client
| type                  = ATC client
| license                = GNU GPL v3
| license                = GNU GPL v3
| website                = https://gitorious.org/atc-pie
| website                = http://mickybadia.free.fr/atcpie
}}
}}


'''ATC-pie''' is a radar [[air traffic control]] simulation program for the [[FlightGear]] multi-player network, initially released Febuary 2015. It is comparable to [[OpenRadar]], but essentially designed for realism.
'''ATC-pie''' is a free (libre) [[air traffic control]] simulation program with strong ties to [[FlightGear]]. It features:
* solo sessions with AI traffic (incl. voice instruction recognition and pilot read-back);
* "multi-player" network sessions (FlightGear and FSD protocols supported);
* tutorial sessions for teacher supervision of an ATC student.


It is programmed in Python3 for Qt5, hence system-independant, only both must be installed as well as the python3-qt5 bindings. That done, it is meant to work straight away, with no other resource to install or make/compile command to run. No need to install or update FlightGear, download scenery or fetch any external resource before it can run.
It is designed to support a maximum range of ATC situations (roles, equipment...), at any world location and for every session type above. All control positions are possible, whether airport-based (TWR, APP, GND...) or en-route (CTR). Equipment may include radar screens, data link, etc. or be limited to binoculars and a view of the airfield.


== Features ==
Its essential goal is realism. It simulates many tasks of real-life ATC such as:
* strip racks and sequence management;
* coordination with neighbouring controllers (handovers, voice phone calls...);
* radar monitoring and identification of traffic;
* vectoring and course/level conflict anticipation;
* flight plan operations;
* CPDLC...


Features listed below are already implemented and supposedly stable. Tested on Linux and Windows; still waiting for Mac users to report.
== Screenshots ==
 
=== General ===
* Floatable/dockable GUI panes: strips, radios, text chat, etc.
* Real METAR updates with selectable weather station
* Real declination lookup and true/magnetic distinction
* Data retrieved from the latest [http://data.x-plane.com X-Plane] file set
* In-app announcement of ATC session on Lenny64's popular [http://flightgear-atc.alwaysdata.net ATC event page]
* General and airport-specific settings saved on close and restored on restart
* Notification system combining sounds and a time-tagged list
* Network text chat system
* Strip route management
* Manage ignored contacts
* Personal notepads (general and airport-specific) saved across sessions
 
=== Transponder support ===
* Realistic mode-dependant behaviour (modes 0, A, C, S)
* Choice for default mode for the many FlightGear aircraft models still not equipped
* Individual and general cheat modes to "see all" (override XPDR settings)
* Radar identification assistant (unique squawk link between radar pick-up and strip assignment detection)
 
=== Radar scope ===
* Variety of show/hide options: navigation points and fixes, aircraft info boxes, vectoring assignments...
* Directly assign headings, altitudes/FLs and speeds by click&drag on radar contacts
* All-in-one display of aircraft course, vector assignments and conflict warning
* Measuring tool for quick point-to-point heading & distance checks
* In-game custom text labels to annotate radar background (saved across sessions)


=== Radio ===
<gallery mode="packed">
* [[FGCom 3.0|FGCom 3]] integration
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
* ATIS recording with information letter and pre-filled preparation notepad
ATC-pie-screenshot-soloMode.png|Solo session with three coloured racks
* Multiple radio management enabling simultaneous transmission on different frequencies
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
* Frequency-specific sound level selection enabling efficient monitoring
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
* Mouse and keyboard PTT
ATC-pie-screenshot-runwayIncursion.png|Runway incursion detected and highlighted in red
* Integrated echo test
ATC-pie-screenshot-flightPlans.png|Flight plan editor
* Use of separate (externally running) FGCom possible
 
=== Strip management ===
* User-defined strip racks
* Strip drag&drop along and across racks
* Link strips to flight plans and radar contacts to merge editable details and inform radar display
* FPL, transponder and vectoring assignment conflicts reported
 
=== Flight plans ===
* Interface with Lenny64's [http://flightgear-atc.alwaysdata.net flight plan data base] including in-game FPL retrieval, filing and editing
* Work with local FPL copies and manage sync with online publication
 
<!--
== Screenshots ==
<gallery>
</gallery>
</gallery>
-->
== Working principles ==
=== General ===
You are the air traffic controller, and players will connect to the network with different types of aircraft and transponder equipment. As in real-life, the radar is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], hence will show you only (unless you cheat) what you pick up from on-board ''transponders'' in your range. That means:
* If a transponder is off or on standby, you will not see the aircraft on your radar screen.
* If a transponder is on, you will at least be able to see its position and read the transponder code, possibly its altitude and even its type and callsign, depending on the mode set by the pilot.
=== Strips ===
Your basic traffic flow and sequence working unit is the '''strip''', each representing a controlled (or soon expected) aircraft. Strips are created, filled with details and moved along and across ''racks'' until handed over to a different controller or discarded. Details written on strips include:
* most importantly, the aircraft's ''callsign'', to be used on the radio;
* details like aircraft type, airspeed, route... that can be specified by the pilots themselves when filing ''flight plans''; and
* transponder code and flight parameter assignments (or vectors: heading, altitude/FL, speed).
=== Linking strips ===
Double-clicking on a strip will open a strip detail sheet where those details can be manually edited, but each strip can also be '''linked''' to a flight plan and/or a visible radar contact on the scope screen—a strip can only be linked to one flight plan and to one radar contact. Linking to a strip will automatically:
* make the strip display the missing elements made available by the linked aircraft transponder or flight plan;
* label the radar contact dot with the more informed linked details (e.g. assigned altitude).
Any detail mismatch between a strip and its linked flight plan or radar contact will be reported for you to resolve.
To ''identify'' an aircraft and link the right radar contact to a strip, an ATC can rely on different things. He can read an aircraft's callsign straight away if it is visible (or cheated), tell from reported positions and altitudes, or use a transponder code. For instance, say a VFR traffic makes an initial radio contact giving his callsign and approximate position. ATC will typically pull out a new blank strip and give the pilot a unique transponder code to squawk, writing it on the strip alongside the announced callsign, then wait for it to appear on the radar. This allows for what ATC-pie calls ''soft links'', in essence radar identification of an aircraft–strip pair such that:
* the strip is assigned a transponder code;
* no other strip is assigned the same code;
* the aircraft is the only one squawking that code in radar range.
Soft links are reported to you so you can properly link the two and consider the aircraft identified, before getting back to the pilot with subsequent instructions.
== User guide ==
This section is pretty much the only documentation there is for now. A better one might come one day, but there should be enough here to get anyone started.
=== Getting it to run ===
==== Downloading ====
There are essentially two ways of downloading ATC-pie: one is to download a '''tarball''' to extract locally; the other is to clone the '''Git repository'''. The latter requires Git, but will keep you in sync with updates more easily. Your choice. In either case, you will have no compiling to do (make, etc.), but do make sure you have the few dependencies installed (e.g. Qt5), listed in the <code>README</code> file.


Downloading the '''tarball''' requires nothing but the standard tar+gzip combo:
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.
# download the [https://gitorious.org/atc-pie/atc-pie/archive/master.tar.gz compressed archive];
# extract the files in the directory of your choice.


To clone the '''repository''', from the directory of your choice:
== Detailed feature list ==
: <code>git clone https://gitorious.org/atc-pie/atc-pie.git</code>


==== Starting the program ====
=== Sessions and environments ===
Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you need to start the program is to run a Python3 interpreter on the <code>ATC-pie.py</code> file in the top-level directory. To start at a chosen airport location, say with code ICAO, use a system command-line argument, which may look as simple as:
Session/connection types:
: <code>./ATC-pie.py ICAO</code>
* solo simulation (AI traffic)
* FlightGear network connection ([[FGMS]] protocol)
* FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
* teaching service (spawn and simulate traffic visible to a connected student)
* student session (control traffic simulated by teacher)


After a few seconds, you should see the main window appear with a radar scope and a depiction of your airport in the centre.
Location modes (available for all sessions):
* airport (AD): positions such as TWR, GND, APP, DEP at a selected airfield
* en-route centre (CTR): free positioning of radar, no base airport or runway-related options


=== Tips ===
{| class="wikitable" style="text-align:center"
|+ Feature support by session type
! || Solo || FlightGear || FSD || Tutoring (teacher/student)
|-
! ACFT traffic
| AI aircraft generated according to RWY capacities, ACFT equipment, intentions...
| colspan="2" | connected flight sim pilots
| created and simulated by teacher
|-
! ATCs and coordination
| virtual ATCs depending on assumed positions
| colspan="2" | connected ATC clients (full ATC-pie interaction, [[#Interoperability with other software|interoperability with other software]])
| teacher-configured ATCs
|-
! Voice radio
| voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back
| colspan="2" | [[FGCom-mumble]] integration
| teacher simulates pilots
|-
! ATC phone lines
| N/A
| colspan="2" | integrated Mumble connection
| teacher simulates ATCs
|-
! Flight plans
| local entries only
| interface with the FlightGear ''de facto'' [http://flightgear-atc.alwaysdata.net data base by Lenny64]
| available from network (NB: protocol does not support open/close and only pilots can file/amend FPLs)
| shared virtual online system
|-
! CPDLC
| interpreted subset of instruction messages
| integrated (supported by MP IRC)
| integrated interface with [https://www.hoppie.nl/acars/ Hoppie's ACARS network]
| full simulation by teacher (with WILCO assistance to execute instructions)
|-
! Weather
| randomised and evolving
| real world METAR retrieval
| fetch from server or retrieve real world METAR
| controlled by teacher
|-
! Other specific features
| style="text-align:left" |
* aircraft type and airline choice with custom appearence in tower view
* configurable airspace rules and traffic density, incl. uncontrolled distractors
| style="text-align:left" |
* exact aircraft rendering in views (incl. control surfaces, etc.)
* legacy [[FGCom_3.0|stand-alone FGCom]] alternate possible (although deprecated)
| style="text-align:left" |
* frequency tuning system for radio text chat
* text ATIS repeatedly sent through radio chat on recorded frequency
| style="text-align:left" |
* traffic snapshots and recall to repeat situations with the student
* individual aircraft freeze
|}


Here are a few unsorted tips to help you navigate the program...
=== ATC surveillance ===
* '''Callsigns''' typically start with the ICAO code of a controlled airport, and end with a hint on the provided service: twr, gnd... With no callsign given, you will appear as "ICAOobs" on network connect. Note that FGMS restricts callsigns lengths to 7 characters. :-(
Radars and tracking:
* For more efficient text chat, a growing list of '''text aliases''' exist (<code>$wind</code>, <code>$qnh</code>, <code>$icao</code>...), which you can use in instant and preset chat messages. They expand to the current value on message send.
* SSR mode capability selection (none/A/C/S)
* '''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exception perhaps are the navigator tooltips, for easier identification on the scope.
* primary radar toggle
* The '''transition level''' is by definition the lowest flight level that is still above the transition altitude. This does not mean the lowest assignable FL, which may take more vertical separation.
* traffic identification assistant
* The grouped '''tick marks along the localiser line''' (when shown) indicate best altitudes AMSL for final approach along the defined slope rate. Every mark in a group is 1,000 ft.
* position/track vs. strip assignment mismatch warning system
* The '''FGCom version setting''' is the name of a subdirectory in <code>resources/fgcom</code>. See <code>Notice</code> file there.
* route/vector conflict anticipation
* "OK" near the "route" field on the strip detail sheet means that the route could be parsed correctly; otherwise "!!" is displayed. This does not matter, only the info boxes will be showing destination (or nothing if unknown) instead of next waypoint.
* separation incident alarm
* runway occupation/incursion detection


Say you are TWR coordinating with GND at an airport and you want to '''monitor both radio frequencies''' while you are only in charge of one. You can set this up by starting your own radio box on TWR frequency, and turn on a second one to monitor GND, setting the volume to "soft" on the latter so that you can always tell if a message is for you to answer or not.
Tower view in airport mode (rendered by FlightGear):
* view of airport, aircraft, weather, time of day
* start internal process or use externally running instance
* control panel to orient/zoom view or follow aircraft
* additional views can be connected (for multiple camera angles)


Resolving '''strip–FPL conflicts''':
Other:
* to confirm all strip details: open the strip detail sheet, tick the "push details to FPL" box and save to propagate the strip details;
* radio direction finding (RDF) and integration to radar
* to confirm all FPL details: reset the strip to overwrite its details with those of the linked flight plan;
* multiple weather (METAR) station monitor
* to confirm some details of each source:
*# open the strip detail sheet;
*# get rid of the bad details and save without pushing to the flight plan;
*# you are back to the first case where you can confirm all strip details.


Resolving '''FPL local–online conflicts''':
=== Traffic management ===
* to update the online version with your local modifications, double-click the flight plan and tick the "publish" box before saving (if still decorated red, there was a network problem or the change was rejected by the server);
Strips and racks:
* to discard all local modifications of an online FPL, remove the FPL from the list and check for new flight plans again (the deleted entry should be retrieved with online state).
* user-defined strip racks with configurable colours (for linked radar contacts) and ATCs to receive from
* runway boxes with automatic RWY separation timers
* loose strip bays with customisable backgrounds


=== Quick reference ===
Flight plans and routes:
* flight plan system (file, edit, open, close, publish/retrieve online)
* world route suggestions, presets, analysis, radar drawing and world map view
* departure clearance assistant
* automatic strip printing for expected departures or arrivals (from FPLs)


==== Display conventions and colour codes ====
Radar tools:
* convenient mouse input for instructions (vectors, taxi...) and CPDLC integration
* approach spacing hints (estimated touch-down time difference, sequence optimisation suggestions)
* quick point-to-point heading and distance measuring tool
* direct text annotation of radar screen
* flag/unflag (highlight) radar targets


Aircraft body:
=== Communications ===
* square: aircraft is properly equipped with a transponder (properties are found in FGMS packets received)
With aircraft:
* circle: no transponder on board (no point instructing to squawk)---warning: if reported, alt./FL value in this case is a geometric distance, not a pressure-altitude, hence approximate when comparing to other aircrafts' values
* voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
* solid shape: contact is linked to a strip (you control it)
* [[ATIS]] recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)
* outlined only: unlinked contact (somebody else might be)
* [[controller-pilot data link communication]] (CPDLC), incl. DEP clearance delivery, multi-element messages...
* "X": ignored contact
* text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist
* "?": contact has timed out (gone or having network problems)


Info box (radar tags):
ATC coordination:
* First line: callsign or "?" if unknown; aircraft type/model if known
* strip exchange (handovers)
* Second line:
* CPDLC authority transfers
** if contact is linked to a strip: next known waypoint on route or destination
* telephone lines and switchboard (direct voice communication)
** otherwise: transponder code (empty if not equipped or off and cheating)
* text messaging (private channels and general ATC chat room)
* Third line: reported altitude or "alt?" if none; vario char ('^' climbing, 'v' descending, '=' neither, '-' N/A); assigned alt. if any; assigned or current ground speed
* "who has?" requests


Courses and assignments:
=== Other ===
* course line: solid if heading assigned, dotted otherwise; red if flying off assigned course, grey otherwise
Misc. tools:
* altitude arc (drawn if alt./FL too different from assigned): solid arc shows point at which assignment will be reached assuming vertical speed of 500 ft/min, dotted if reach point is beyond arc
* world airport, map navpoint and AD parking position browsing/indicating
* speed marks: each mark shows distance flown in 1 minute at assigned speed, current speed or TAS (first available); grey if correct speed or none assigned, red otherwise (marks then point to either accelerate or decelerate to reach assignment)
* aeronautical unit conversion calculator
* custom alarm clocks with quick keyboard timer start
* general and location-specific notepads restored between sessions


Strips:
GUI:
* black: unlinked strip
* multiple window workspace (radar screens, strip racks and bays) saved by location
* blue: soft link detected, matching aircraft marked as well
* floatable/dockable panels and toolbars (see [[:File:ATC-pie-screenshot-toolbars.png|screenshot]]) and layout save/restore
* green: linked strip with no conflicts
* notification system combining selectable sounds, status bar messages and time-tagged history
* red: linked strip with unfollowed vector assignments ("!!vect", see ''courses and assignments'' above) or transponder conflicts to resolve ("!!XPDR", open detail sheet for more info)
* customisable style and colours
* "!!FPL": conflicts with flight plan


FPLs:
Data sources:
* black: local (not published) flight plan
* airport and navigation data sourced in the [http://developer.x-plane.com/docs/specs X-Plane] format (old world-wide default file set provided but custom imports recommended)
* green: FPL is online, and in sync unless modified by somebody else online
* editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
* red: FPL exists online, but local modifications have been made
* custom radar background images and hand drawings (EuroScope/[http://www.vatsim.net VATSIM]/IVAO "sector file" conversion tool included)
* ground elevation maps (can be generated automatically with a provided script if FlightGear terrain data available)
* manual magnetic declination input


==== GUI gestures and key strokes ====
== Interoperability with other software ==


Keyboard:
=== OpenRadar ===
* CTRL: ''PTT'' all radios whose "kbd PTT" boxes are ticked (works within major dialogs too)
[[OpenRadar]] is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways:
* F2: create ''new blank strip''
* OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip;
* SHIFT+F2: create ''new strip linked'' to selection
* OpenRadar's concept of handover is based on a shared notion of aircraft ownership, whereas ATC-pie allows any controller to pull out a strip and write a callsign on it;
* in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring users to see it complete, whereas ATC-pie considers that a strip sent is gone and assumed to land on the receiver's rack, without anybody else necessarily to know.


Mouse hover:
For most interactions to work in FlightGear sessions while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange between the two programs:
* entry in navigator pane: ''show'' a tool tip with true heading and distance from radar
* ATC-pie users can only hand over strips to OpenRadar that are linked to a radar contact;
* unpinned navpoint on radar scope: ''show'' short name, and frequency/channel if navaid
* aircraft under ATC-pie control are not shown as "owned" to OpenRadar users;
* handovers from ATC-pie will fail if an OpenRadar user is claiming ownership on the linked radar contact;
* when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally.


Left mouse button alone:
Callsign handover policy:
* click on aircraft body, info box, strip or FPL: ''select''
* OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
* click on navpoint: ''set filter'' in navigator
* ATC-pie to OpenRadar: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
* click on radar background: ''deselect''
* pie-to-pie handovers through OpenRadar's service: strip detail preserved, whether present or absent.
* click on text chat message: ''recall'' dest./message in entry line
** own message: recalls both
** other: fill dest. and focus message field
* click&drag info box: ''move box''
* click&drag aircraft body if a strip is linked: ''assign heading'' to aircraft
* double-click on aircraft body or info box: ''edit linked strip'' if any
* double-click on navpoint: ''pin/unpin'' label
* double-click on notification: notification-dependant


Left mouse button with modifier key:
Features not supported by OpenRadar:
* SHIFT+click strip with linked radar contact: ''indicate aircraft'' location
* wake turbulance category on strips (but detail preserved for ATC-pie clients later receiving the strip);
* SHIFT+click&drag aircraft body if a strip is linked: ''assign alt/FL or speed'' to aircraft
* ATC text messaging;
* SHIFT+double-click on aircraft body: ''remove hdg/alt./FL/speed assignments''
* ATC phone lines;
* SHIFT+double-click on info box: ''reset'' box position
* CPDLC transfers.
* SHIFT+double-click on radar background: ''add'' custom text label
* SHIFT+double-click on custom text label: ''remove'' label


Middle mouse button:
Who-has requests are fully supported.
* click on aircraft body, info box, strip or FPL: ''link'' to current selection if any and if possible
* SHIFT+click on aircraft body, info box or FPL (if selected and linked): ''unlink'' from strip


Right mouse button:
=== Euroscope ===
* click&drag anywhere on radar scope: ''pan'' view
Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD. It has been increasingly tailored for VATSIM, although for a long time it allowed also to connect to "plain" (non-VATSIM) FSD servers. Operability outside of VATSIM is now discontinued all together, but older versions of Euroscope are still around and connecting to FSD networks. ATC-pie is able to interact with them in FSD sessions, but only to a limited extent:
* SHIFT+click&drag anywhere on radar scope: heading and distance ''measuring tool''
* sending a strip to Euroscope will result in a loss of all strip details but the callsign (which must be connected), the only information left to the recipient being the FPL details for that callsign if any (strip changes made after FPL data retrieval are therefore lost);
* receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed");
* who-has requests will remain unanswered by Euroscope;
* there are no integrated phone lines to Euroscope clients.


[[Category:ATC-pie]]
[[Category:ATC clients]]
[[Category:ATC clients]]
[[Category:Air Traffic Control]]

Latest revision as of 08:27, 2 April 2023

FlightGear logo.png The FlightGear forum has a
subforum related to: ATC-Pie support & development
This article is about the software and its features. For help with installation or configuration, see ATC-pie installation guide. For a manual on how to use it, see ATC-pie user guide.
ATC-pie
ATC-pie logo
Tower viewing, following a departing aircraft
Tower viewing, following a departing aircraft
Developed by Michael Filhol
Initial release February 1, 2015
Latest release 1.8.8 (April 1, 2023)
Written in Python (Version 3)
OS Any
Platform Qt5
Development status Active
Type ATC client
License GNU GPL v3
Website

ATC-pie is a free (libre) air traffic control simulation program with strong ties to FlightGear. It features:

  • solo sessions with AI traffic (incl. voice instruction recognition and pilot read-back);
  • "multi-player" network sessions (FlightGear and FSD protocols supported);
  • tutorial sessions for teacher supervision of an ATC student.

It is designed to support a maximum range of ATC situations (roles, equipment...), at any world location and for every session type above. All control positions are possible, whether airport-based (TWR, APP, GND...) or en-route (CTR). Equipment may include radar screens, data link, etc. or be limited to binoculars and a view of the airfield.

Its essential goal is realism. It simulates many tasks of real-life ATC such as:

  • strip racks and sequence management;
  • coordination with neighbouring controllers (handovers, voice phone calls...);
  • radar monitoring and identification of traffic;
  • vectoring and course/level conflict anticipation;
  • flight plan operations;
  • CPDLC...

Screenshots

  • Sector view around Geneva

    Sector view around Geneva

  • Solo session with three coloured racks

    Solo session with three coloured racks

  • Background image display

    Background image display

  • Depiction of airport tarmac and objects

    Depiction of airport tarmac and objects

  • Runway incursion detected and highlighted in red

    Runway incursion detected and highlighted in red

  • Flight plan editor

    Flight plan editor

Visit the ATC-pie screenshot category for more.

Detailed feature list

Sessions and environments

Session/connection types:

  • solo simulation (AI traffic)
  • FlightGear network connection (FGMS protocol)
  • FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
  • teaching service (spawn and simulate traffic visible to a connected student)
  • student session (control traffic simulated by teacher)

Location modes (available for all sessions):

  • airport (AD): positions such as TWR, GND, APP, DEP at a selected airfield
  • en-route centre (CTR): free positioning of radar, no base airport or runway-related options
Feature support by session type
Solo FlightGear FSD Tutoring (teacher/student)
ACFT traffic AI aircraft generated according to RWY capacities, ACFT equipment, intentions... connected flight sim pilots created and simulated by teacher
ATCs and coordination virtual ATCs depending on assumed positions connected ATC clients (full ATC-pie interaction, interoperability with other software) teacher-configured ATCs
Voice radio voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back FGCom-mumble integration teacher simulates pilots
ATC phone lines N/A integrated Mumble connection teacher simulates ATCs
Flight plans local entries only interface with the FlightGear de facto data base by Lenny64 available from network (NB: protocol does not support open/close and only pilots can file/amend FPLs) shared virtual online system
CPDLC interpreted subset of instruction messages integrated (supported by MP IRC) integrated interface with Hoppie's ACARS network full simulation by teacher (with WILCO assistance to execute instructions)
Weather randomised and evolving real world METAR retrieval fetch from server or retrieve real world METAR controlled by teacher
Other specific features
  • aircraft type and airline choice with custom appearence in tower view
  • configurable airspace rules and traffic density, incl. uncontrolled distractors
  • exact aircraft rendering in views (incl. control surfaces, etc.)
  • legacy stand-alone FGCom alternate possible (although deprecated)
  • frequency tuning system for radio text chat
  • text ATIS repeatedly sent through radio chat on recorded frequency
  • traffic snapshots and recall to repeat situations with the student
  • individual aircraft freeze

ATC surveillance

Radars and tracking:

  • SSR mode capability selection (none/A/C/S)
  • primary radar toggle
  • traffic identification assistant
  • position/track vs. strip assignment mismatch warning system
  • route/vector conflict anticipation
  • separation incident alarm
  • runway occupation/incursion detection

Tower view in airport mode (rendered by FlightGear):

  • view of airport, aircraft, weather, time of day
  • start internal process or use externally running instance
  • control panel to orient/zoom view or follow aircraft
  • additional views can be connected (for multiple camera angles)

Other:

  • radio direction finding (RDF) and integration to radar
  • multiple weather (METAR) station monitor

Traffic management

Strips and racks:

  • user-defined strip racks with configurable colours (for linked radar contacts) and ATCs to receive from
  • runway boxes with automatic RWY separation timers
  • loose strip bays with customisable backgrounds

Flight plans and routes:

  • flight plan system (file, edit, open, close, publish/retrieve online)
  • world route suggestions, presets, analysis, radar drawing and world map view
  • departure clearance assistant
  • automatic strip printing for expected departures or arrivals (from FPLs)

Radar tools:

  • convenient mouse input for instructions (vectors, taxi...) and CPDLC integration
  • approach spacing hints (estimated touch-down time difference, sequence optimisation suggestions)
  • quick point-to-point heading and distance measuring tool
  • direct text annotation of radar screen
  • flag/unflag (highlight) radar targets

Communications

With aircraft:

  • voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
  • ATIS recording and reminder alarm (see dialog with pre-filled notepad)
  • controller-pilot data link communication (CPDLC), incl. DEP clearance delivery, multi-element messages...
  • text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist

ATC coordination:

  • strip exchange (handovers)
  • CPDLC authority transfers
  • telephone lines and switchboard (direct voice communication)
  • text messaging (private channels and general ATC chat room)
  • "who has?" requests

Other

Misc. tools:

  • world airport, map navpoint and AD parking position browsing/indicating
  • aeronautical unit conversion calculator
  • custom alarm clocks with quick keyboard timer start
  • general and location-specific notepads restored between sessions

GUI:

  • multiple window workspace (radar screens, strip racks and bays) saved by location
  • floatable/dockable panels and toolbars (see screenshot) and layout save/restore
  • notification system combining selectable sounds, status bar messages and time-tagged history
  • customisable style and colours

Data sources:

  • airport and navigation data sourced in the X-Plane format (old world-wide default file set provided but custom imports recommended)
  • editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
  • custom radar background images and hand drawings (EuroScope/VATSIM/IVAO "sector file" conversion tool included)
  • ground elevation maps (can be generated automatically with a provided script if FlightGear terrain data available)
  • manual magnetic declination input

Interoperability with other software

OpenRadar

OpenRadar is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways:

  • OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip;
  • OpenRadar's concept of handover is based on a shared notion of aircraft ownership, whereas ATC-pie allows any controller to pull out a strip and write a callsign on it;
  • in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring users to see it complete, whereas ATC-pie considers that a strip sent is gone and assumed to land on the receiver's rack, without anybody else necessarily to know.

For most interactions to work in FlightGear sessions while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange between the two programs:

  • ATC-pie users can only hand over strips to OpenRadar that are linked to a radar contact;
  • aircraft under ATC-pie control are not shown as "owned" to OpenRadar users;
  • handovers from ATC-pie will fail if an OpenRadar user is claiming ownership on the linked radar contact;
  • when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally.

Callsign handover policy:

  • OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
  • ATC-pie to OpenRadar: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
  • pie-to-pie handovers through OpenRadar's service: strip detail preserved, whether present or absent.

Features not supported by OpenRadar:

  • wake turbulance category on strips (but detail preserved for ATC-pie clients later receiving the strip);
  • ATC text messaging;
  • ATC phone lines;
  • CPDLC transfers.

Who-has requests are fully supported.

Euroscope

Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD. It has been increasingly tailored for VATSIM, although for a long time it allowed also to connect to "plain" (non-VATSIM) FSD servers. Operability outside of VATSIM is now discontinued all together, but older versions of Euroscope are still around and connecting to FSD networks. ATC-pie is able to interact with them in FSD sessions, but only to a limited extent:

  • sending a strip to Euroscope will result in a loss of all strip details but the callsign (which must be connected), the only information left to the recipient being the FPL details for that callsign if any (strip changes made after FPL data retrieval are therefore lost);
  • receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed");
  • who-has requests will remain unanswered by Euroscope;
  • there are no integrated phone lines to Euroscope clients.
Retrieved from "https://wiki.flightgear.org/w/index.php?title=ATC-pie&oldid=137480"