MediaWiki has been updated to version 1.35.1. Please report any problems here.

Difference between revisions of "ATC-pie"

From FlightGear wiki
Jump to navigation Jump to search
m (Infobox software: Switch the 3 in Python3 from the 'writtenin' parameter to the 'writteninversion' parameter.)
(v1.8.0)
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.0 (Jan. 17, 2021)
 
| writtenin              = Python
 
| writtenin              = Python
 
| writteninversion      = 3
 
| writteninversion      = 3
Line 29: Line 29:
 
* strip rack and sequence management;
 
* strip rack and sequence management;
 
* radar monitoring and transponder identification;
 
* radar monitoring and transponder identification;
* handovers to/from neighbouring controllers;
+
* coordination with neighbouring controllers (strip handovers, voice phone calls...);
* routing and conflict anticipation;
+
* en-route vectoring and path/level conflict anticipation;
 
* flight plan filing and editing...
 
* flight plan filing and editing...
  
Line 84: Line 84:
 
=== General ===
 
=== General ===
 
Available session types:
 
Available session types:
* Solo simulation (AI IFR traffic)
+
* Solo simulation (AI traffic)
 
* FlightGear networks (FGMS protocol)
 
* FlightGear networks (FGMS protocol)
* FSD connections (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in April 2020)
+
* FSD networks (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in April 2020)
 
* Teacher–student tutoring (teacher spawns and runs the traffic visible to the student)
 
* Teacher–student tutoring (teacher spawns and runs the traffic visible to the student)
  
Line 92: Line 92:
 
* Airport (for ATC positions such as TWR, GND, APP, DEP at a selected airfiled)
 
* Airport (for ATC positions such as TWR, GND, APP, DEP at a selected airfiled)
 
* En-route centre (free positioning of radar, no base airport or runway-related options)
 
* En-route centre (free positioning of radar, no base airport or runway-related options)
 
Common data sources:
 
* Airport and navigation data sourced in the [http://data.x-plane.com X-Plane] format (old world-wide default file set included)
 
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
 
* 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)
 
* Real world magnetic declination lookup
 
  
 
=== ATC surveillance ===
 
=== ATC surveillance ===
Radar and transponders:
+
Radars and tracking:
* SSR mode selection and primary radar activation
+
* SSR mode selection (none/A/C/S)
* Full transponder support and mode-dependant radar behaviour
+
* Primary radar option
 +
* Current leg and next waypoint display with geodesic calculations of headings and distances
 +
* Anticipated route/vector conflict warnings and separation incident alarm
 +
* Position/track vs. strip assignment mismatch warning system
 
* Traffic identification assistant
 
* Traffic identification assistant
 
* Runway occupation/incursion detection
 
* Runway occupation/incursion detection
* Position/track vs. assignment mismatch warning system
 
  
Tower viewing for airport mode (requires FlightGear):
+
Tower view in airport mode (rendered by FlightGear):
* Renders view of airport, aircraft, weather, time of day
+
* View of airport, aircraft, weather, time of day
* Internally started or through an externally running instance
+
* Through internally started process or externally running instance
 
* Control panel to orient/zoom view or follow aircraft
 
* Control panel to orient/zoom view or follow aircraft
 
* Additional views can be connected (for multiple camera angles)
 
* 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 ===
 
=== 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
  
Routes, vectors, conflicts:
+
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
 
* World route suggestions, presets, analysis, radar drawing and world map view
 +
* Automatic strip printing for expected departures or arrivals (from FPLs)
 +
 +
Radar tools:
 
* Convenient mouse input for vectors, taxi instructions and waypoint changes
 
* Convenient mouse input for vectors, taxi instructions and waypoint changes
* Current leg and next waypoint display with geodesic calculations of headings and distances
+
* Approach spacing hints for inbound sequencing (estimated touch-down time difference)
* Route/vector conflict anticipation and separation incident alarm
+
* Quick point-to-point heading and distance measuring tool
* Approach spacing hints for inbound sequences
+
* Direct text annotation of radar screen
 +
* Flag/unflag (highlight) radar targets
  
 
=== Communications ===
 
=== Communications ===
 
With aircraft:
 
With aircraft:
* [[FGCom]] radio integration for FlightGear sessions (stand-alone processes and Mumble plug-in)
+
* Multiple 8.33 radio support with simultaneous frequency/channel transmissions and monitoring
* Multiple frequency transmissions and monitoring
 
* Radio direction finding (RDF) and integration to radar
 
* Controller-pilot data link communication (CPDLC)
 
* 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)
 
* ATIS recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)
 +
* [[Controller-pilot data link communication]] (CPDLC)
 +
* Text radio chat with preset messages, auto-completion, predefined and custom aliases for context-sensitive replacements, sender blacklist to filter out trolls
  
 
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 land lines (direct voice communication)
* General ATC chat room
+
* Text messaging (private channels and general ATC chat room)
 
* "Who has?" requests
 
* "Who has?" requests
  
Line 147: Line 148:
 
Solo sessions (AI traffic):
 
Solo sessions (AI traffic):
 
* Strip exchange: handovers to/from virtual ATCs
 
* Strip exchange: handovers to/from virtual ATCs
* CPDLC: transfers with ATCs and instructions/requests with ACFT
+
* Voice radio: instruction recognition (with Sphinx) and pilot read-back synthesis (with pyttsx)
* Weather: randomised and progressively changing
+
* Weather: randomised and evolving
* Voice instruction recognition (with Sphinx)
+
* Aircraft type and airline choice with custom appearence in tower view
* Pilot read-back speech synthesis (with pyttsx)
+
* Configurable airspace rules and traffic density
* Airline choice and custom aircraft appearence in tower view
 
* Configurable airspace rules
 
* Adjustable difficulty (traffic density)
 
  
 
FlightGear network sessions:
 
FlightGear network sessions:
 
* Strip exchange: full handover support with ATC-pie, compatible with [[OpenRadar]]
 
* Strip exchange: full handover support with ATC-pie, compatible with [[OpenRadar]]
* CPDLC: supported but no ACFT capable of connection yet
+
* Voice radio: [[FGCom]] integration (using stand-alone processes or through Mumble plug-in)
 
* Weather: real world METAR retrieval
 
* Weather: real world METAR retrieval
 
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. filing, editing, opening and closing
 
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. filing, editing, opening and closing
Line 164: Line 162:
  
 
FSD network sessions:
 
FSD network sessions:
* Strip exchange: handovers with other clients (although lossy if not ATC-pie)
+
* Strip exchange: handovers with other clients (lossy if not ATC-pie)
* CPDLC: not supported by FSD
 
 
* Weather: fetch from server or retrieve real world METAR
 
* Weather: fetch from server or retrieve real world METAR
 
* Flight plans: available from the network (although only editable by the pilots, and open/close not supported by FSD)
 
* Flight plans: available from the network (although only editable by the pilots, and open/close not supported by FSD)
Line 172: Line 169:
 
Tutoring sessions (teacher with student):
 
Tutoring sessions (teacher with student):
 
* Strip exchange: configurable ATC neighbours and handover supervision by teacher
 
* Strip exchange: configurable ATC neighbours and handover supervision by teacher
* CPDLC: fully supported, incl. transfers to/from student and dialogues with teacher ACFT
 
 
* Weather: controlled by teacher
 
* Weather: controlled by teacher
 
* Traffic snapshots and recall to repeat situations with the student
 
* Traffic snapshots and recall to repeat situations with the student
  
=== Misc. ===
+
=== Other ===
GUI features:
+
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
 
* 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
 
* 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
 
* 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
+
* Customisable style and colours
  
Convenience tools:
+
Common data sources:
* Quick point-to-point heading and distance measuring tool
+
* Airport and navigation data sourced in the [http://data.x-plane.com X-Plane] format (old world-wide default file set provided but custom imports recommended)
* Multiple weather station monitor
+
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
* Direct text annotation of radar screen
+
* Custom radar background images and hand drawings (EuroScope/[http://www.vatsim.net VATSIM]/IVAO "sector file" conversion tool included)
* World airport, map navpoint and AD parking position browsing/indicating
+
* Ground elevation maps (can be generated automatically with a provided script if FlightGear terrain data available)
* Aeronautical unit conversion calculator
+
* Real world magnetic declination lookup
* 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]]

Revision as of 21:13, 17 January 2021

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.0 (Jan. 17, 2021)
Written in Python (Version 3)
OS Any
Platform Qt5
Development status Active
Type ATC client
License GNU GPL v3
Website

ATC-pie is an air traffic control simulation program featuring:

  • solo sessions, incl. voice instruction recognition and pilot speech synthesis;
  • network sessions through FGMS and FSD;
  • 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:

  • strip rack and sequence management;
  • radar monitoring and transponder identification;
  • coordination with neighbouring controllers (strip handovers, voice phone calls...);
  • en-route vectoring and path/level conflict anticipation;
  • flight plan filing and editing...

To download the program and learn more about how to use it, read the ATC-pie installation and user guides. If you have a question, check the FAQ first, or try the forum for help.

Screenshots

Visit the ATC-pie screenshot category for more.

Working principles

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

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 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

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

General

Available session types:

  • Solo simulation (AI traffic)
  • FlightGear networks (FGMS protocol)
  • FSD networks (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in April 2020)
  • Teacher–student tutoring (teacher spawns and runs the traffic visible to the student)

Available modes for all session types:

  • Airport (for ATC positions such as TWR, GND, APP, DEP at a selected airfiled)
  • En-route centre (free positioning of radar, no base airport or runway-related options)

ATC surveillance

Radars and tracking:

  • SSR mode selection (none/A/C/S)
  • Primary radar option
  • Current leg and next waypoint display with geodesic calculations of headings and distances
  • Anticipated route/vector conflict warnings and separation incident alarm
  • Position/track vs. strip assignment mismatch warning system
  • Traffic identification assistant
  • Runway occupation/incursion detection

Tower view in airport mode (rendered by FlightGear):

  • View of airport, aircraft, weather, time of day
  • Through internally started process or 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
  • Automatic strip printing for expected departures or arrivals (from FPLs)

Radar tools:

  • Convenient mouse input for vectors, taxi instructions and waypoint changes
  • Approach spacing hints for inbound sequencing (estimated touch-down time difference)
  • Quick point-to-point heading and distance measuring tool
  • Direct text annotation of radar screen
  • Flag/unflag (highlight) radar targets

Communications

With aircraft:

  • Multiple 8.33 radio support with simultaneous frequency/channel transmissions and monitoring
  • ATIS recording and reminder alarm (see dialog with pre-filled notepad)
  • Controller-pilot data link communication (CPDLC)
  • Text radio chat with preset messages, auto-completion, predefined and custom aliases for context-sensitive replacements, sender blacklist to filter out trolls

ATC coordination:

  • Strip exchange (handovers)
  • CPDLC authority transfers
  • Telephone land lines (direct voice communication)
  • Text messaging (private channels and general ATC chat room)
  • "Who has?" requests

Session environments

Solo sessions (AI traffic):

  • Strip exchange: handovers to/from virtual ATCs
  • Voice radio: instruction recognition (with Sphinx) and pilot read-back synthesis (with pyttsx)
  • Weather: randomised and evolving
  • Aircraft type and airline choice with custom appearence in tower view
  • Configurable airspace rules and traffic density

FlightGear network sessions:

  • Strip exchange: full handover support with ATC-pie, compatible with OpenRadar
  • Voice radio: FGCom integration (using stand-alone processes or through Mumble plug-in)
  • Weather: real world METAR retrieval
  • Flight plans: interface with Lenny64's data base (the de facto FG standard), incl. filing, editing, opening and closing
  • ATIS: voice recording through FGCom
  • In-app announcement of ATC sessions on Lenny64's event page

FSD network sessions:

  • Strip exchange: handovers with other clients (lossy if not ATC-pie)
  • Weather: fetch from server or retrieve real world METAR
  • 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):

  • Strip exchange: configurable ATC neighbours and handover supervision by teacher
  • Weather: controlled by teacher
  • Traffic snapshots and recall to repeat situations with the student

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

Common 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)
  • Real world magnetic declination lookup