ATC-pie: Difference between revisions

Jump to navigation Jump to search

ATC-pie (view source)

Revision as of 18:42, 4 September 2022

3,046 bytes removed ,  4 September 2022
v1.8.6
(v1.8.5)
(v1.8.6)
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|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.8.5 (Dec. 19, 2021)
| latestrelease          = 1.8.6 (Sept. 4, 2022)
| writtenin              = Python
| writtenin              = Python
| writteninversion      = 3
| writteninversion      = 3
Line 21: Line 21:
}}
}}


'''ATC-pie''' is a free (libre) [[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);
* "multi-player" network sessions ([[FGMS]] and FSD protocols supported);
* "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 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:
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;
* 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 [[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...


== Working principles ==
To install/configure the program, refer to the [[ATC-pie installation guide]].
 
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".


== Screenshots ==
== Screenshots ==
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.


<gallery mode="packed">
<gallery mode="packed">
Line 79: Line 48:
ATC-pie-screenshot-flightPlans.png|Flight plan editor
ATC-pie-screenshot-flightPlans.png|Flight plan editor
</gallery>
</gallery>
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.


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


=== Sessions ===
=== Sessions and environments ===
Available session types:
Session/connection types:
* Solo simulation (AI traffic)
* solo simulation (AI traffic)
* FlightGear network connection (FGMS protocol)
* FlightGear network connection ([[FGMS]] protocol)
* FSD connection (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)
* Teaching service (spawn and simulate traffic visible to a connected student)
* teaching service (spawn and simulate traffic visible to a connected student)
* Student session (control traffic simulated by teacher)
* student session (control traffic simulated by teacher)
 
Location modes:
* Airport (for ATC 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)
 
=== ATC surveillance ===
Radars and tracking:
* SSR mode 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
* 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:
* 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)
* [[Controller-pilot data link communication]] (CPDLC), incl. 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 (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 [[: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://data.x-plane.com 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)
* Real world magnetic declination lookup
=== Session environments ===
{| class="wikitable" style="text-align:center"
{| class="wikitable" style="text-align:center"
! || Solo || FlightGear || FSD || Tutoring (teacher/student)
! || Solo || FlightGear || FSD || Tutoring (teacher/student)
|-
|-
! Traffic
! ACFT traffic
| AI aircraft generated according to RWY capacities, ACFT equipment, intentions...
| AI aircraft generated according to RWY capacities, ACFT equipment, intentions...
| colspan="2" | connected flight sim pilots
| colspan="2" | connected flight sim pilots
| created and simulated by teacher
| created and simulated by teacher
|-
|-
! ATCs
! ATCs for coordination
| virtual ATCs depending on assumed position
| virtual ATCs depending on assumed positions
| colspan="2" | connected ATC clients (full ATC-pie support, [[#Interoperability with other software|interoperability with other software]])
| colspan="2" | connected ATC clients (full ATC-pie support, [[#Interoperability with other software|interoperability with other software]])
| teacher-configured ATCs
| teacher-configured ATCs
|-
|-
! Voice radio
! Voice radio
| instruction recognition and pilot read-back synthesis
| voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back
| FGCom [[FGCom_3.0|stand-alone processes]] or [[FGCom-mumble]] plug-in
| FGCom integration: [[FGCom-mumble]] plug-in or legacy [[FGCom_3.0|stand-alone]] variant
| working PTT but audio system not integrated (must use third-party software)
| working PTT but third-party audio system expected
| teacher simulates pilots
| teacher simulates pilots
|-
|-
! ATC phone lines
! ATC phone lines
| rowspan="2" | N/A
| rowspan="2" | N/A
| colspan="2" | integrated connection to a Mumble service
| colspan="2" | integrated Mumble connection
| teacher simulates ATCs
| teacher simulates ATCs
|-
|-
! Flight plans
! Flight plans
| interface with the FlightGear ''de facto'' [http://flightgear-atc.alwaysdata.net data base by Lenny64]
| 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
| available from network (NB: protocol does not support open/close and only pilots can file/amend FPLs)
| virtual online system
| virtual online system
|-
|-
Line 204: Line 98:
! Other specific features
! Other specific features
| style="text-align:left" |
| style="text-align:left" |
* mouse-only instructions possible (voice recognition by-pass)
* aircraft type and airline choice with custom appearence in tower view
* aircraft type and airline choice with custom appearence in tower view
* configurable airspace rules and traffic density, incl. uncontrolled distractors
* configurable airspace rules and traffic density, incl. uncontrolled distractors
Line 217: Line 110:
* individual aircraft freeze
* individual aircraft freeze
|}
|}
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
=== 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
* 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
* [[ATIS]] recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)
* [[controller-pilot data link communication]] (CPDLC), incl. 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 (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 [[: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)
* real world magnetic declination lookup


== Interoperability with other software ==
== Interoperability with other software ==
Line 233: Line 202:


Callsign handover policy:
Callsign handover policy:
* O-R to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
* OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
* ATC-pie to O-R: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
* 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.
* pie-to-pie handovers through OpenRadar's service: strip detail preserved, whether present or absent.


Line 243: Line 212:
* CPDLC.
* CPDLC.


Note that who-has requests are fully supported.
Who-has requests are fully supported.


=== Euroscope ===
=== Euroscope ===
Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD. For a long time Euroscope allowed to connect to "plain" FSD servers, although being increasingly tailored for VATSIM, until it discontinued operability outside of VATSIM all together.
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:
 
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);
* 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");
* receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed");
Mickybadia
265

edits

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

Navigation menu