ATC-pie: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(v1.7.1)
(v1.8.8)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{forum|83|ATC-Pie support & development}}
{{forum|83|ATC-Pie support & development}}


{{about|the software in general|a manual on how to use it|ATC-pie user guide}}
{{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
Line 10: Line 10:
| developedby            = Michael Filhol
| developedby            = Michael Filhol
| initialrelease        = February 1, 2015
| initialrelease        = February 1, 2015
| latestrelease          = 1.7.1 (Sept. 1, 2020)
| latestrelease          = 1.8.8 (April 1, 2023)
| writtenin              = Python3
| writtenin              = Python
| writteninversion      = 3
| os                    = Any
| os                    = Any
| platform              = Qt5
| platform              = Qt5
Line 20: Line 21:
}}
}}


'''ATC-pie''' is an [[air traffic control]] simulation program featuring:
'''ATC-pie''' is a free (libre) [[air traffic control]] simulation program with strong ties to [[FlightGear]]. It features:
* solo sessions, incl. voice instruction recognition and pilot speech synthesis;
* solo sessions with AI traffic (incl. voice instruction recognition and pilot read-back);
* network sessions through [[FGMS]] and FSD;
* "multi-player" network sessions (FlightGear and FSD protocols supported);
* tutorial sessions for teacher supervision of an ATC student.
* tutorial sessions for teacher supervision of an ATC student.


It can simulate en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...), and allows 3D tower viewing through [[FlightGear]]. It is essentially designed for realism and simulates many tasks and situations of real-life ATC such as:
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.
* strip rack and sequence management;
* radar monitoring and transponder identification;
* handovers to/from neighbouring controllers;
* routing and conflict anticipation;
* flight plan filing and editing...


To download the program and learn more about how to use it, read the ATC-pie [[ATC-pie installation guide|installation]] and [[ATC-pie user guide|user]] guides. If you have a question, check the [[ATC-pie FAQ|FAQ]] first, or try the forum for help.
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 ==
== Screenshots ==
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.


<gallery mode="packed">
<gallery mode="packed">
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
ATC-pie-screenshot-soloMode.png|Playing solo with three coloured racks
ATC-pie-screenshot-soloMode.png|Solo session with three coloured racks
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
Line 47: Line 47:
</gallery>
</gallery>


== Working principles ==
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.
 
You are the air traffic controller, working with equipment depending on your position and local facility. This may include a tower view, radar scopes, data links, etc. Your traffic is the aircraft connected by human pilots (FlightGear, FSD), or simulated with AI (solo) or by a teacher (student). They all contact you with different types of aircraft, [[transponder]] equipment and intentions.
 
=== Strips ===
[[File:ATC-pie-screenshot-stripDetailSheet.png|thumbnail|The ATC-pie strip detail sheet]]
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 across ''racks'' and ''bays'' until handed over to a different controller or shelved. Strip details can all be manually edited, and include:
* most importantly, the aircraft's ''callsign'', to be used on the radio;
* information like aircraft type, airspeed, route... that can be provided by the pilots themselves when filing ''flight plans'';
* transponder code and flight parameter assignments (heading, altitude/FL, air speed).
 
=== Radar ===
As in real life, the main radar technology is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], which only shows what is picked up from on-board transponders in its range. This means that:
* if a transponder is off or out of range, you will not see the aircraft on your radar screen;
* if a transponder is on and in range, you will at least be able to see its position and read a transponder code, and possibly its altitude, type, callsign... depending on the transponder mode and your radar capabilities.
 
=== Linking strips ===
Every strip can be '''linked''' to a flight plan and to a transponder contact on radar. A linked strip will automatically:
* display its missing elements when available from the linked flight plan or aircraft transponder;
* populate the information in the radar tag of the linked aircraft with useful details, e.g. assigned altitude.
 
=== Radar identification ===
[[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]]
When using radar, ATCs use different methods to ''identify'' an aircraft and link the right contact to its strip. They can read an aircraft's callsign straight away if its transponder is squawking mode S, tell from reported positions, or use a transponder code.
 
For instance, say a transponder-equipped VFR traffic makes radio contact giving their 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 '''radar identification''' of aircraft–strip pairs such that:
* the strip is assigned a transponder code;
* no other strip is assigned the same code;
* the aircraft is the only unidentified traffic squawking that code in radar range.
 
ATC-pie identifies such pairs automatically and reports them to you so you can properly link the two and get back to the pilot: "radar identified".


== Detailed feature list ==
== Detailed feature list ==


=== General ===
=== Sessions and environments ===
Available session types:
Session/connection types:
* Solo simulation (AI IFR traffic)
* solo simulation (AI traffic)
* FlightGear networks (FGMS protocol)
* FlightGear network connection ([[FGMS]] protocol)
* FSD connections (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in April 2020)
* FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
* Teacher–student tutoring (teacher spawns and runs the traffic visible to the student)
* teaching service (spawn and simulate traffic visible to a connected student)
* student session (control traffic simulated by teacher)


Available modes for all session types:
Location modes (available for all sessions):
* Airport (for ATC positions such as TWR, GND, APP, DEP at a selected airfiled)
* airport (AD): positions such as TWR, GND, APP, DEP at a selected airfield
* En-route centre (free positioning of radar, no base airport or runway-related options)
* en-route centre (CTR): free positioning of radar, no base airport or runway-related options


Common data sources:
{| class="wikitable" style="text-align:center"
* Airport and navigation data sourced in the [http://data.x-plane.com X-Plane] format (old world-wide default file set included)
|+ Feature support by session type
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
! || Solo || FlightGear || FSD || Tutoring (teacher/student)
* Radar background images and hand drawings (integrated EuroScope/[http://www.vatsim.net VATSIM]/IVAO .sct sector file import)
|-
* Ground elevation maps (can be generated automatically with a provided script)
! ACFT traffic
* Real world magnetic declination lookup
| 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
|}


=== ATC surveillance ===
=== ATC surveillance ===
Radar and transponders:
Radars and tracking:
* SSR mode selection and primary radar activation
* SSR mode capability selection (none/A/C/S)
* Full transponder support and mode-dependant radar behaviour
* primary radar toggle
* Traffic identification assistant
* traffic identification assistant
* Runway occupation/incursion detection
* position/track vs. strip assignment mismatch warning system
* Position/track vs. 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)


Tower viewing for airport mode (requires FlightGear):
Other:
* Renders view of airport, aircraft, weather, time of day
* radio direction finding (RDF) and integration to radar
* Internally started or through an externally running instance
* multiple weather (METAR) station monitor
* Control panel to orient/zoom view or follow aircraft
* Additional views can be connected (for multiple camera angles)


=== Traffic management ===
=== Traffic management ===
Strips and racks:
Strips and racks:
* User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from
* user-defined strip racks with configurable colours (for linked radar contacts) and ATCs to receive from
* Strip auto-print for expected departures or arrivals
* runway boxes with automatic RWY separation timers
* Runway boxes with automatic RWY separation timers
* loose strip bays with customisable backgrounds
* 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)


Routes, vectors, conflicts:
Radar tools:
* World route suggestions, presets, analysis, radar drawing and world map view
* convenient mouse input for instructions (vectors, taxi...) and CPDLC integration
* Convenient mouse input for vectors, taxi instructions and waypoint changes
* approach spacing hints (estimated touch-down time difference, sequence optimisation suggestions)
* Current leg and next waypoint display with geodesic calculations of headings and distances
* quick point-to-point heading and distance measuring tool
* Route/vector conflict anticipation and separation incident alarm
* direct text annotation of radar screen
* Approach spacing hints for inbound sequences
* flag/unflag (highlight) radar targets


=== Communications ===
=== Communications ===
With aircraft:
With aircraft:
* [[FGCom]] radio integration for FlightGear sessions (stand-alone processes and Mumble plug-in)
* voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
* Multiple frequency transmissions and monitoring
* [[ATIS]] recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)
* Radio direction finding (RDF) and integration to radar
* [[controller-pilot data link communication]] (CPDLC), incl. DEP clearance delivery, multi-element messages...
* Controller-pilot data link communication (CPDLC)
* text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist
* Text radio chat in network sessions, with preset messages, auto-completion, predefined and custom aliases for context-sensitive replacements, sender blacklist to filter out trolls
* ATIS recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)


ATC coordination:
ATC coordination:
* Strip exchange with known ATCs (handovers)
* strip exchange (handovers)
* CPDLC authority transfers
* CPDLC authority transfers
* Private messaging with other ATCs (text "landlines")
* telephone lines and switchboard (direct voice communication)
* General ATC chat room
* text messaging (private channels and general ATC chat room)
* "Who has?" requests
* "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 [[:File:ATC-pie-screenshot-toolbars.png|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 [http://developer.x-plane.com/docs/specs 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/[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
 
== Interoperability with other software ==


=== Session environments ===
=== OpenRadar ===
Solo sessions (AI traffic):
[[OpenRadar]] is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways:
* Strip exchange: handovers to/from virtual ATCs
* OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip;
* CPDLC: transfers with ATCs and instructions/requests with ACFT
* 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;
* Weather: randomised and progressively changing
* 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.
* Voice instruction recognition (with Sphinx)
* Pilot read-back speech synthesis (with pyttsx)
* Airline choice and custom aircraft appearence in tower view
* Configurable airspace rules
* Adjustable difficulty (traffic density)


FlightGear network sessions:
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:
* Strip exchange: full handover support with ATC-pie, compatible with [[OpenRadar]]
* ATC-pie users can only hand over strips to OpenRadar that are linked to a radar contact;
* CPDLC: supported but no ACFT capable of connection yet
* aircraft under ATC-pie control are not shown as "owned" to OpenRadar users;
* Weather: real world METAR retrieval
* handovers from ATC-pie will fail if an OpenRadar user is claiming ownership on the linked radar contact;
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. filing, editing, opening and closing
* when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally.
* ATIS: voice recording through FGCom
* In-app announcement of ATC sessions on Lenny64's event page


FSD network sessions:
Callsign handover policy:
* Strip exchange: handovers with other clients (although lossy if not ATC-pie)
* OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
* CPDLC: not supported by FSD
* ATC-pie to OpenRadar: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
* Weather: fetch from server or retrieve real world METAR
* pie-to-pie handovers through OpenRadar's service: strip detail preserved, whether present or absent.
* Flight plans: available from the network (although only editable by the pilots, and open/close not supported by FSD)
* ATIS: recorded as text only (sent through chat system)


Tutoring sessions (teacher with student):
Features not supported by OpenRadar:
* Strip exchange: configurable ATC neighbours and handover supervision by teacher
* wake turbulance category on strips (but detail preserved for ATC-pie clients later receiving the strip);
* CPDLC: fully supported, incl. transfers to/from student and dialogues with teacher ACFT
* ATC text messaging;
* Weather: controlled by teacher
* ATC phone lines;
* Traffic snapshots and recall to repeat situations with the student
* CPDLC transfers.


=== Misc. ===
Who-has requests are fully supported.
GUI features:
* Multiple window workspace (radar screens, strip racks and bays) saved by location
* Floatable/dockable panels and toolbars (see [[:File:ATC-pie-screenshot-toolbars.png|screenshot]]) and layout save/restore
* Customisable colours
* Notification system combining selectable sounds, status bar messages and time-tagged history
* General and location-specific notes and settings saved on close and restored on restart


Convenience tools:
=== Euroscope ===
* Quick point-to-point heading and distance measuring tool
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:
* Multiple weather station monitor
* 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);
* Direct text annotation of radar screen
* receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed");
* World airport, map navpoint and AD parking position browsing/indicating
* who-has requests will remain unanswered by Euroscope;
* Aeronautical unit conversion calculator
* there are no integrated phone lines to Euroscope clients.
* Custom alarm clocks with quick keyboard timer start


[[Category:ATC-pie]]
[[Category:ATC-pie]]
[[Category:ATC clients]]
[[Category:ATC clients]]
[[Category:Air Traffic Control]]
[[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"