ATC-pie: Difference between revisions
Mickybadia (talk | contribs) (v1.4.3) |
Mickybadia (talk | contribs) (v 1.5.0) |
||
Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = 1. | | latestrelease = 1.5.0 (June 5, 2018) | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| os = Any | | os = Any | ||
Line 20: | Line 20: | ||
}} | }} | ||
'''ATC-pie''' is an [[air traffic control]] simulation program allowing to play solo | '''ATC-pie''' is an [[air traffic control]] simulation program allowing to play solo, connect to [[FlightGear]] multi-player networks and set up tutorial sessions for teacher supervision of an ATC student. It enables en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...), and features 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 essentially designed for realism and simulates many tasks and situations of real-life ATC such as: | ||
Line 28: | Line 28: | ||
* ATIS recording; | * ATIS recording; | ||
* flight plan filing and editing; | * flight plan filing and editing; | ||
* routing and conflict anticipation. | * routing and conflict anticipation; | ||
* voice instruction recognition and pilot speech synthesis in solo sessions. | |||
The program is free and open source, and programmed in Python3 for Qt5 hence system-independant. Only Python3 and its Qt5 bindings must be installed. That done, it is meant to work straight away, with no make/compile command to run or external resource to install. The whole world is immediately available on radar. Tower viewing requires the appropriate FlightGear aircraft and scenery. | The program is free and open source, and programmed in Python3 for Qt5 hence system-independant. Only Python3 and its Qt5 bindings must be installed. That done, it is meant to work straight away, with no make/compile command to run or external resource to install. The whole world is immediately available on radar. Tower viewing requires the appropriate FlightGear aircraft and scenery. | ||
Line 69: | Line 70: | ||
=== Radar identification === | === Radar identification === | ||
[[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]] | [[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]] | ||
To ''identify'' an aircraft and link the right radar contact to a strip, | To ''identify'' an aircraft and link the right radar contact to a strip, ATCs can rely on different things. They can read an aircraft's callsign straight away if its transponder has mode S turned on, tell from reported positions and altitudes, or use a transponder code. | ||
For instance, say a VFR traffic makes | 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; | * the strip is assigned a transponder code; | ||
* no other strip is assigned the same code; | * no other strip is assigned the same code; | ||
Line 80: | Line 81: | ||
== Detailed feature list == | == Detailed feature list == | ||
Available modes and session types: | |||
Available modes and | |||
* FlightGear multi-player connections ([[FGMS]]) | * FlightGear multi-player connections ([[FGMS]]) | ||
* Solo | * Solo sessions with simulated IFR traffic | ||
* Teacher–student tutoring sessions | * Teacher–student tutoring sessions | ||
* For all session types: en-route centre or airport control mode | * For all session types: en-route centre or airport control mode | ||
* For all airport sessions: 3D tower view available | * For all airport sessions: 3D tower view available | ||
=== Session environments === | |||
Common data sources: | |||
* Airport and navigation data retrieved from [http://data.x-plane.com X-Plane] file sets (whole world base set included, custom files accepted) | |||
* 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) | |||
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.) | |||
* Online real world declination lookup for true/magnetic distinction | |||
FlightGear multi-player sessions: | |||
* Weather: real world METAR retrieval | * Weather: real world METAR retrieval | ||
* Strip exchange: handovers with other ATC-pie and [[OpenRadar]] instances in range | * Strip exchange: handovers with other ATC-pie and [[OpenRadar]] instances in range | ||
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. | * Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. run-time retrieval, opening, closing, filing and editing (work on local copies and manage sync with online status) | ||
* In-app announcement of ATC sessions on Lenny64's event page | * In-app announcement of ATC sessions on Lenny64's event page | ||
Solo sessions (AI traffic): | |||
* CTR control mode, or configurable combination of TWR, GND, APP and DEP positions in airport mode | * CTR control mode, or configurable combination of TWR, GND, APP and DEP positions in airport mode | ||
* Voice instruction recognition (with Sphinx) | * Voice instruction recognition (with Sphinx) | ||
Line 105: | Line 112: | ||
* Adjustable difficulty (traffic density) | * Adjustable difficulty (traffic density) | ||
Tutoring sessions (teacher with student): | |||
* Teacher spawns and manipulates traffic visible to student (flight and transponder settings) | * Teacher spawns and manipulates traffic visible to student (flight and transponder settings) | ||
* Weather: wind control by teacher | * Weather: wind control by teacher | ||
Line 112: | Line 119: | ||
=== General === | === General === | ||
GUI features: | GUI features: | ||
* Graphical launcher at start to select mode and location | |||
* 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 | * 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 | ||
Misc. tools: | Misc. tools: | ||
Line 133: | Line 132: | ||
* AD/nav/parking point browser and indicator | * AD/nav/parking point browser and indicator | ||
* Custom alarm clocks with quick keyboard timer start | * Custom alarm clocks with quick keyboard timer start | ||
* General and location-specific notes and settings saved on close and restored on restart | |||
=== ATC surveillance === | === ATC surveillance === | ||
Radar and transponders: | Radar and transponders: | ||
* SSR and primary radar activation | * SSR and primary radar activation | ||
* Full transponder support and mode-dependant radar behaviour (off, A, C, S | * Full transponder support and mode-dependant radar behaviour (off, A, C, S) | ||
* Radar identification assistant (detects unique matches between strip info and radar contacts) | * Radar identification assistant (detects unique matches between strip info and radar contacts) | ||
* Runway occupation/incursion detection | * Runway occupation/incursion detection | ||
Line 152: | Line 152: | ||
Strips and racks: | Strips and racks: | ||
* User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from | * User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from | ||
* Strip auto-print for expected departures | |||
* Runway boxes with automatic WTC timers when freed | * Runway boxes with automatic WTC timers when freed | ||
* Loose strip bays with customisable backgrounds | * Loose strip bays with customisable backgrounds | ||
Line 166: | Line 167: | ||
* Multiple frequency transmissions and monitoring, frequency-specific sound level selection | * Multiple frequency transmissions and monitoring, frequency-specific sound level selection | ||
ATC coordination: | |||
* General ATC chat room | |||
* Private messaging ("landlines") | |||
* "Who has" requests | |||
Public text chat: | |||
* Preset messages and auto-completion | * Preset messages and auto-completion | ||
* Predefined and custom aliases for context-sensitive replacements (general, location- and ACFT-specific) | * Predefined and custom aliases for context-sensitive replacements (general, location- and ACFT-specific) |
Revision as of 21:20, 5 June 2018
The FlightGear forum has a subforum related to: ATC-Pie support & development |
Tower viewing, following a departing aircraft | |
Developed by | Michael Filhol |
---|---|
Initial release | February 1, 2015 |
Latest release | 1.5.0 (June 5, 2018) |
Written in | Python3 |
OS | Any |
Platform | Qt5 |
Development status | Active |
Type | ATC client |
License | GNU GPL v3 |
Website |
ATC-pie is an air traffic control simulation program allowing to play solo, connect to FlightGear multi-player networks and set up tutorial sessions for teacher supervision of an ATC student. It enables en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...), and features 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;
- handovers to/from neighbouring controllers;
- ATIS recording;
- flight plan filing and editing;
- routing and conflict anticipation;
- voice instruction recognition and pilot speech synthesis in solo sessions.
The program is free and open source, and programmed in Python3 for Qt5 hence system-independant. Only Python3 and its Qt5 bindings must be installed. That done, it is meant to work straight away, with no make/compile command to run or external resource to install. The whole world is immediately available on radar. Tower viewing requires the appropriate FlightGear aircraft and scenery.
Screenshots
Visit the ATC-pie screenshot wiki category for more
Working principles
General
You are the air traffic controller, working with or without a tower window or radar scope, depending on your position and local facility. Players will connect to the network (multi-player), AI traffic be simulated (solo), or teacher traffic generated (tutorial session), with different types of aircraft and transponder equipment.
As in real life, your main radar technology is SSR, hence unless you cheat or activate the primary radar, will show you only what you pick up from on-board transponders in its range. This means:
- if a transponder is off, 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. Strip details include:
- most importantly, the aircraft's callsign, to be used on the radio;
- information like aircraft type, airspeed, route... that can be specified by the pilots themselves when filing flight plans;
- transponder code and flight parameter assignments (or vectors: heading, altitude/FL, speed).
Linking strips
Strip details can be manually edited, but every strip can also be linked to a flight plan and/or a radar contact. Linking to a strip will automatically:
- make the strip display the missing elements available from the linked aircraft transponder or flight plan;
- if you use radar, inform the contact label with useful details provided on the strip, 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.
Radar identification
To identify an aircraft and link the right radar contact to a strip, ATCs can rely on different things. They can read an aircraft's callsign straight away if its transponder has mode S turned on, tell from reported positions and altitudes, 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
Available modes and session types:
- FlightGear multi-player connections (FGMS)
- Solo sessions with simulated IFR traffic
- Teacher–student tutoring sessions
- For all session types: en-route centre or airport control mode
- For all airport sessions: 3D tower view available
Session environments
Common data sources:
- Airport and navigation data retrieved from X-Plane file sets (whole world base set included, custom files accepted)
- Radar background images and hand drawings (integrated EuroScope/VATSIM/IVAO .sct sector file import)
- Ground elevation maps (can be generated automatically with a provided script)
- Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
- Online real world declination lookup for true/magnetic distinction
FlightGear multi-player sessions:
- Weather: real world METAR retrieval
- Strip exchange: handovers with other ATC-pie and OpenRadar instances in range
- Flight plans: interface with Lenny64's data base (the de facto FG standard), incl. run-time retrieval, opening, closing, filing and editing (work on local copies and manage sync with online status)
- In-app announcement of ATC sessions on Lenny64's event page
Solo sessions (AI traffic):
- CTR control mode, or configurable combination of TWR, GND, APP and DEP positions in airport mode
- Voice instruction recognition (with Sphinx)
- Pilot read-back speech synthesis (with pyttsx)
- Weather: randomised
- Strip exchange: handovers to/from virtual ATCs
- Airline choice and custom aircraft appearence
- Configurable airspace rules and entry/exit/routing points
- Adjustable difficulty (traffic density)
Tutoring sessions (teacher with student):
- Teacher spawns and manipulates traffic visible to student (flight and transponder settings)
- Weather: wind control by teacher
- Strip exchange: configurable ATC neighbours and handover supervision by teacher
- Traffic snapshots and recall to repeat situations with the student
General
GUI features:
- Graphical launcher at start to select mode and location
- Multiple window workspace (radar screens, strip racks and bays) saved by location
- Floatable/dockable panels and toolbars (see screenshot) and layout save/restore
- Customisable colours
- Notification system combining selectable sounds, status bar messages and time-tagged history
Misc. tools:
- Quick point-to-point heading and distance measuring tool and access to Earth coordinates
- Multiple weather station monitor
- Direct text annotation of radar screen with mouse
- AD/nav/parking point browser and indicator
- Custom alarm clocks with quick keyboard timer start
- General and location-specific notes and settings saved on close and restored on restart
ATC surveillance
Radar and transponders:
- SSR and primary radar activation
- Full transponder support and mode-dependant radar behaviour (off, A, C, S)
- Radar identification assistant (detects unique matches between strip info and radar contacts)
- Runway occupation/incursion detection
- Visible mismatches between assigned vectors and picked up positions (see all-in-one graphics)
- Route/vector conflict anticipation and separation incident alarm
- Approach spacing hints for inbound sequences
Tower viewing (airport mode, requires FlightGear):
- Internally started or through connection to an external instance
- Controller pane to orient/zoom view or follow aircraft
- Additional views can be connected (for multiple camera angles)
Traffic management
Strips and racks:
- User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from
- Strip auto-print for expected departures
- Runway boxes with automatic WTC timers when freed
- Loose strip bays with customisable backgrounds
Routes, vectors, conflicts:
- Convenient mouse input for vectors, taxi instructions and route/waypoint changes
- Route presets, analysis, drawing and world map view
- Current leg and next waypoint display with geodesic calculations of headings and distances
Communications
Radio:
- FGCom integration, incl. echo test and possible use of externally running client
- ATIS recording with pre-filled preparation notepad (see feature dialog)
- Multiple frequency transmissions and monitoring, frequency-specific sound level selection
ATC coordination:
- General ATC chat room
- Private messaging ("landlines")
- "Who has" requests
Public text chat:
- Preset messages and auto-completion
- Predefined and custom aliases for context-sensitive replacements (general, location- and ACFT-specific)
- Sender blacklist management (filter out trolls)
Using ATC-pie
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 for help or try the forum.