265
edits
ATC-pie: Difference between revisions
Jump to navigation
Jump to search
v1.8.3, moving sections across articles to balance sizes
Mickybadia (talk | contribs) m (v1.8.2) |
Mickybadia (talk | contribs) (v1.8.3, moving sections across articles to balance sizes) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = 1.8. | | latestrelease = 1.8.3 (Aug. 13, 2021) | ||
| writtenin = Python | | writtenin = Python | ||
| writteninversion = 3 | | writteninversion = 3 | ||
| Line 21: | Line 21: | ||
}} | }} | ||
'''ATC-pie''' is | '''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 through [[FGMS]] and FSD; | * network sessions ("multi-player"), through [[FGMS]] and FSD; | ||
* tutorial sessions for teacher supervision of an ATC student. | * tutorial sessions for teacher supervision of an ATC student. | ||
It | 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: | ||
* strip rack and sequence management; | * strip rack and sequence management; | ||
* radar monitoring and transponder identification; | * radar monitoring and transponder identification; | ||
| Line 41: | Line 41: | ||
<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| | 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 90: | Line 90: | ||
Location modes: | Location modes: | ||
* Airport (for ATC positions such as TWR, GND, APP, DEP at a selected | * 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) | * En-route centre (free positioning of radar, no base airport or runway-related options) | ||
| Line 141: | Line 141: | ||
* Strip exchange (handovers) | * Strip exchange (handovers) | ||
* CPDLC authority transfers | * CPDLC authority transfers | ||
* Telephone | * Telephone lines (direct voice communication) | ||
* Text messaging (private channels and general ATC chat room) | * Text messaging (private channels and general ATC chat room) | ||
* "Who has?" requests | * "Who has?" requests | ||
| Line 155: | Line 155: | ||
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]] | ||
* Voice radio: | * Voice radio: FGCom integration (using [[FGCom_3.0|stand-alone processes]] or through [[FGCom-mumble|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) | * Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard) | ||
* ATIS: voice recording through FGCom | * ATIS: voice recording through FGCom | ||
FSD network sessions: | FSD network sessions: | ||
| Line 191: | Line 190: | ||
* 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 | ||
== Interoperability with other software == | |||
=== FlightGear sessions and compatibility with OpenRadar === | |||
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 while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange: | |||
* 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: | |||
* O-R 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; | |||
* 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 instances later receiving the strip); | |||
* ATC text messaging; | |||
* ATC phone lines; | |||
* CPDLC. | |||
Note that who-has requests are fully supported. | |||
=== FSD sessions and compatibility with Euroscope === | |||
Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD, available in ATC-pie. 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. Older versions of Euroscope are still around and connecting to FSD networks. ATC-pie is able to interact with them 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. | |||
[[Category:ATC-pie]] | [[Category:ATC-pie]] | ||
[[Category:ATC clients]] | [[Category:ATC clients]] | ||
[[Category:Air Traffic Control]] | [[Category:Air Traffic Control]] | ||