ATC-pie: Difference between revisions

Jump to navigation Jump to search

ATC-pie (view source)

Revision as of 18:10, 19 December 2021

622 bytes added ,  19 December 2021
v1.8.5
(v1.8.4)
(v1.8.5)
Line 10: Line 10:
| developedby            = Michael Filhol
| developedby            = Michael Filhol
| initialrelease        = February 1, 2015
| initialrelease        = February 1, 2015
| latestrelease          = 1.8.4 (Aug. 14, 2021)
| latestrelease          = 1.8.5 (Dec. 19, 2021)
| writtenin              = Python
| writtenin              = Python
| writteninversion      = 3
| writteninversion      = 3
Line 23: Line 23:
'''ATC-pie''' is a free (libre) [[air traffic control]] simulation program featuring:
'''ATC-pie''' is a free (libre) [[air traffic control]] simulation program featuring:
* solo sessions, incl. voice instruction recognition and pilot speech synthesis;
* solo sessions, incl. voice instruction recognition and pilot speech synthesis;
* network sessions ("multi-player"), through [[FGMS]] and FSD;
* "multi-player" network sessions ([[FGMS]] and FSD protocols supported);
* tutorial sessions for teacher supervision of an ATC student.
* tutorial sessions for teacher supervision of an ATC student.


It allows en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...), including 3D tower viewing through [[FlightGear]]. It is essentially designed for realism and simulates many tasks and situations of real-life ATC such as:
It allows en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...) with 3D tower viewing through [[FlightGear]]. It is essentially designed for realism, simulates many tasks and situations of real-life ATC such as:
* strip rack and sequence management;
* strip rack and sequence management;
* radar monitoring and transponder identification;
* radar monitoring and transponder identification;
Line 34: Line 34:


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.
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.
== Screenshots ==
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.
<gallery mode="packed">
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
ATC-pie-screenshot-soloMode.png|Solo session with three coloured racks
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
ATC-pie-screenshot-runwayIncursion.png|Runway incursion detected and highlighted in red
ATC-pie-screenshot-flightPlans.png|Flight plan editor
</gallery>


== Working principles ==
== Working principles ==
Line 79: Line 66:


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".
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".
== Screenshots ==
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.
<gallery mode="packed">
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
ATC-pie-screenshot-soloMode.png|Solo session with three coloured racks
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
ATC-pie-screenshot-runwayIncursion.png|Runway incursion detected and highlighted in red
ATC-pie-screenshot-flightPlans.png|Flight plan editor
</gallery>


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


=== Sessions ===
=== Sessions ===
Available session/connection types:
Available session types:
* Solo simulation (AI traffic)
* Solo simulation (AI traffic)
* FlightGear networks (FGMS protocol)
* FlightGear network connection (FGMS protocol)
* FSD networks (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 April 2020)
* 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)


Location modes:
Location modes:
Line 96: Line 97:
Radars and tracking:
Radars and tracking:
* SSR mode selection (none/A/C/S)
* SSR mode selection (none/A/C/S)
* Primary radar option
* Primary radar toggle
* Traffic identification assistant
* Traffic identification assistant
* Position/track vs. strip assignment mismatch warning system
* Position/track vs. strip assignment mismatch warning system
Line 133: Line 134:
=== Communications ===
=== Communications ===
With aircraft:
With aircraft:
* Multiple 8.33 radio support with simultaneous frequency/channel transmissions and monitoring
* Voice radio with 8.33 kHz frequency spacing
* 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)
* [[Controller-pilot data link communication]] (CPDLC), incl. multi-element messages
* Text radio chat with preset messages, auto-completion, predefined and custom aliases for context-sensitive replacements, sender blacklist to filter out trolls
* Text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist


ATC coordination:
ATC coordination:
Line 144: Line 145:
* Text messaging (private channels and general ATC chat room)
* Text messaging (private channels and general ATC chat room)
* "Who has?" requests
* "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 [[FGCom_3.0|stand-alone processes]] or through [[FGCom-mumble|Mumble plug-in]])
* Weather: real world METAR retrieval
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard)
* ATIS: voice recording through FGCom
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 ===
=== Other ===
Line 190: Line 165:
* Ground elevation maps (can be generated automatically with a provided script if FlightGear terrain data available)
* Ground elevation maps (can be generated automatically with a provided script if FlightGear terrain data available)
* Real world magnetic declination lookup
* Real world magnetic declination lookup
=== Session environments ===
{| class="wikitable" style="text-align:center"
! || Solo || FlightGear || FSD || Tutoring (teacher/student)
|-
! Traffic
| AI aircraft generated according to RWY capacities, ACFT equipment, intentions...
| colspan="2" | connected flight sim pilots
| created and simulated by teacher
|-
! ATCs
| virtual ATCs depending on assumed position
| colspan="2" | connected ATC clients (full ATC-pie support, [[#Interoperability with other software|interoperability with other software]])
| teacher-configured ATCs
|-
! Voice radio
| instruction recognition and pilot read-back synthesis
| FGCom [[FGCom_3.0|stand-alone processes]] or [[FGCom-mumble]] plug-in
| working PTT but audio system not integrated (must use third-party software)
| teacher simulates pilots
|-
! ATC phone lines
| rowspan="2" | N/A
| colspan="2" | integrated connection to a Mumble service
| teacher simulates ATCs
|-
! Flight plans
| interface with the FlightGear ''de facto'' [http://flightgear-atc.alwaysdata.net data base by Lenny64]
| available from network, but no FSD support for open/close and only pilots can file/amend
| virtual online system
|-
! 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" |
* mouse-only instructions possible (voice recognition by-pass)
* aircraft type and airline choice with custom appearence in tower view
* configurable airspace rules and traffic density, incl. uncontrolled distractors
| style="text-align:left" |
* multiple radio support with simultaneous transmissions and monitoring
* voice ATIS recording
| 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
|}


== Interoperability with other software ==
== Interoperability with other software ==


=== OpenRadar ===
=== OpenRadar ===
OpenRadar is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways:
[[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 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;
* 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;
Mickybadia
265

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/134197"

Navigation menu