ATC-pie: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (version update)
(v1.8.8)
 
(55 intermediate revisions by 4 users not shown)
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|help with installation or configuration|ATC-pie installation guide|a manual on how to use it|ATC-pie user guide}}


{{Infobox Software
{{Infobox Software
| title                  = ATC-pie
| title                  = ATC-pie
| logo                  = ATC-pie-logo.png
| logo                  = ATC-pie-logo.png
| image                  = ATC-pie-screenshot-KSFOmess.png
| image                  = ATC-pie-screenshot-towerViewing.png
| alt                    = ATC-pie at the KSFO mess
| alt                    = Tower viewing, following a departing aircraft
| developedby            = Michael Filhol
| developedby            = Michael Filhol
| initialrelease        = February 1, 2015
| initialrelease        = February 1, 2015
| latestrelease          = January 31, 2016 (r8b)
| latestrelease          = 1.8.8 (April 1, 2023)
| writtenin              = Python3
| writtenin              = Python
| writteninversion      = 3
| os                    = Any
| os                    = Any
| platform              = Qt5
| platform              = Qt5
Line 17: Line 18:
| type                  = ATC client
| type                  = ATC client
| license                = GNU GPL v3
| license                = GNU GPL v3
| website                = https://sourceforge.net/projects/atc-pie
| website                = http://mickybadia.free.fr/atcpie
}}
}}


'''ATC-pie''' is an [[air traffic control]] simulation program allowing to play solo games and connect to [[FlightGear]] multi-player networks. It features an en-route (CTR) mode as well as an airport mode where tower viewing is possible. It is essentially designed for realism and simulates many tasks of real-life ATC such as transponder identification, strip rack and sequence management, handovers to/from neighbouring controllers, ATIS recording, flight plan editing, routing and conflict solving.
'''ATC-pie''' is a free (libre) [[air traffic control]] simulation program with strong ties to [[FlightGear]]. It features:
* solo sessions with AI traffic (incl. voice instruction recognition and pilot read-back);
* "multi-player" network sessions (FlightGear and FSD protocols supported);
* tutorial sessions for teacher supervision of an ATC student.


ATC-pie is free and open source, 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 (except for local tower viewing, which requires FlightGear and the appropriate scenery).
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.


== Program features ==
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...


The features listed below have been tested on various Linux versions, Mac and Windows.
== Screenshots ==
 
<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>
 
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.
 
== Detailed feature list ==


=== Game and environment ===
=== Sessions and environments ===
Multi-player and network environment:
Session/connection types:
* Configurable [[FGMS]] connections
* solo simulation (AI traffic)
* ATC handovers: strip exchange with [[OpenRadar]] and other ATC-pie instances in range
* FlightGear network connection ([[FGMS]] protocol)
* Interface with Lenny64's [http://flightgear-atc.alwaysdata.net flight plan data base], including in-game FPL retrieval, filing and editing
* FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
* In-app session announcement facility to post on Lenny64's popular ATC event page
* teaching service (spawn and simulate traffic visible to a connected student)
* student session (control traffic simulated by teacher)


Solo games:
Location modes (available for all sessions):
* Various ATC positions: CTR or free combination of APP, TWR and DEP
* airport (AD): positions such as TWR, GND, APP, DEP at a selected airfield
* Handovers to/from virtual ATCs
* en-route centre (CTR): free positioning of radar, no base airport or runway-related options
* Instruction interface and pilot read back
* Adjustable difficulty (traffic density)
* Departure–arrival and ILS–visual balance options
* Configurable runways in use, entry/exit/routing points


World data:
{| class="wikitable" style="text-align:center"
* Real world METAR updates from selectable weather stations
|+ Feature support by session type
* Real world declination lookup and true/magnetic distinction
! || Solo || FlightGear || FSD || Tutoring (teacher/student)
* Airport and navigation data retrieved from the latest [http://data.x-plane.com X-Plane] file set
|-
* Custom additions possible in separate files
! ACFT traffic
| AI aircraft generated according to RWY capacities, ACFT equipment, intentions...
| colspan="2" | connected flight sim pilots
| created and simulated by teacher
|-
! ATCs and coordination
| virtual ATCs depending on assumed positions
| colspan="2" | connected ATC clients (full ATC-pie interaction, [[#Interoperability with other software|interoperability with other software]])
| teacher-configured ATCs
|-
! Voice radio
| voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back
| colspan="2" | [[FGCom-mumble]] integration
| teacher simulates pilots
|-
! ATC phone lines
| N/A
| colspan="2" | integrated Mumble connection
| teacher simulates ATCs
|-
! Flight plans
| local entries only
| interface with the FlightGear ''de facto'' [http://flightgear-atc.alwaysdata.net data base by Lenny64]
| available from network (NB: protocol does not support open/close and only pilots can file/amend FPLs)
| shared virtual online system
|-
! CPDLC
| interpreted subset of instruction messages
| integrated (supported by MP IRC)
| integrated interface with [https://www.hoppie.nl/acars/ Hoppie's ACARS network]
| full simulation by teacher (with WILCO assistance to execute instructions)
|-
! 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" |
* aircraft type and airline choice with custom appearence in tower view
* configurable airspace rules and traffic density, incl. uncontrolled distractors
| style="text-align:left" |
* exact aircraft rendering in views (incl. control surfaces, etc.)
* legacy [[FGCom_3.0|stand-alone FGCom]] alternate possible (although deprecated)
| 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
|}


GUI:
=== ATC surveillance ===
* Floatable, dockable and closable GUI panes: strips, radios, text chat, etc. (window layout saved)
Radars and tracking:
* Notification system combining selectable sounds, status bar messages and a time-tagged history
* SSR mode capability selection (none/A/C/S)
* General and location-specific notepads and settings saved on close and restored on restart
* primary radar toggle
* Customisable colours
* traffic identification assistant
* Ignore contacts
* position/track vs. strip assignment mismatch warning system
* route/vector conflict anticipation
* separation incident alarm
* runway occupation/incursion detection


=== Radar and visual contacts ===
Tower view in airport mode (rendered by FlightGear):
Transponders:
* view of airport, aircraft, weather, time of day
* Full support and mode-dependant behaviour (off, A, C, S)
* start internal process or use externally running instance
* Choice of simulated mode for non-equipped aircraft models
* control panel to orient/zoom view or follow aircraft
* Radar identification assistant (unique squawk link between radar pick-up and strip assignment detection)
* additional views can be connected (for multiple camera angles)
* Individual and general cheat modes to override XPDR settings


Radar scope:
Other:
* Open multiple radar screens
* radio direction finding (RDF) and integration to radar
* Show/hide options for navigation points, vectors and route assignments, etc.
* multiple weather (METAR) station monitor
* Quick point-to-point heading and distance measuring tool and access to Earth coordinates
* Custom radar background image and image display (e.g. to display maps/charts)
* Custom text labels to annotate radar background
* Configurable horizontal and vertical ranges, and rotation speed
* Primary radar activation (see targets without XPDR signals)


Tower viewing, scene rendering:
=== Traffic management ===
* Real-time rendering of the airport scene from tower viewpoint, available in both MP and solo games
Strips and racks:
* Internally started (requires FlightGear installed) or through connection to an external instance
* user-defined strip racks with configurable colours (for linked radar contacts) and ATCs to receive from
* Controller pane to orient/zoom view or follow aircraft
* runway boxes with automatic RWY separation timers
* Possible use of custom scenery and aircraft model addition/substitution
* loose strip bays with customisable backgrounds
* Additional views can be connected


=== ATC management ===
Flight plans and routes:
Strips, racks, flight plans:
* flight plan system (file, edit, open, close, publish/retrieve online)
* Strip drag&drop along and across user-defined racks, with configurable colours
* world route suggestions, presets, analysis, radar drawing and world map view
* Strip drop on neighbouring ATCs to hand over
* departure clearance assistant
* Link strips to flight plans and radar contacts to merge editable details and inform radar display
* automatic strip printing for expected departures or arrivals (from FPLs)
* Conflicts between linked elements reported
* Work with local FPL copies and manage sync with online publication


Routes, vectors, conflicts:
Radar tools:
* Route parsing, drawing and world map view
* convenient mouse input for instructions (vectors, taxi...) and CPDLC integration
* Route presets and quick retrieval between two end airports
* approach spacing hints (estimated touch-down time difference, sequence optimisation suggestions)
* Current leg and next waypoint display with geodesic calculations of headings and distances
* quick point-to-point heading and distance measuring tool
* Assign vectors and change routes with direct mouse gestures
* direct text annotation of radar screen
* Anticipated conflict warnings and separation incident alarm
* flag/unflag (highlight) radar targets
* Visible mismatches between assigned vectors and picked up positions (see [[:File:ATC-pie-screenshot-courseAndAssignmentsGraphics.png|all-in-one graphics]])


=== Communications ===
=== Communications ===
Radio:
With aircraft:
* [[FGCom]] integration, incl. echo test and possible use of externally running client
* voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
* ATIS recording with pre-filled preparation notepad (see [[:File:ATC-pie-screenshot-ATISdialog.png|feature dialog]])
* [[ATIS]] recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)
* Multiple and single frequency transmissions
* [[controller-pilot data link communication]] (CPDLC), incl. DEP clearance delivery, multi-element messages...
* Frequency-specific sound level selection
* text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist


Text chat:
ATC coordination:
* Customisable preset messages and text aliases for context-sensitive replacements
* strip exchange (handovers)
* Message history and single-click message recall
* CPDLC authority transfers
* Hardcore communication sim possible by disabling unknown senders' callsigns
* telephone lines and switchboard (direct voice communication)
* Senders blacklist management (filter out trolls)
* text messaging (private channels and general ATC chat room)
* "who has?" requests


== Screenshots ==
=== Other ===
<gallery mode="packed">
Misc. tools:
ATC-pie-screenshot-soloMode.png|Playing solo mode with three coloured racks
* world airport, map navpoint and AD parking position browsing/indicating
ATC-pie-screenshot-towerViewing.png|Tower viewing, following a departing aircraft
* aeronautical unit conversion calculator
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
* custom alarm clocks with quick keyboard timer start
ATC-pie-screenshot-routeDetailsView.png|View route details and world path
* general and location-specific notepads restored between sessions
ATC-pie-screenshot-routeConflictDetection.png|Route conflict warning
 
ATC-pie-screenshot-LFPGcloseUp.png|Depiction of airport tarmac and objects
GUI:
</gallery>
* 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)
* manual magnetic declination input


== Working principles ==
== Interoperability with other software ==


=== General ===
=== OpenRadar ===
You are the air traffic controller, and players will connect to the network (or AI traffic be simulated in solo mode) with different types of aircraft and [[transponder]] equipment. As in real life, the radar is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], hence will show you only (unless you cheat or activate the primary radar) what you pick up from on-board ''transponders'' in your range. That means:
[[OpenRadar]] is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways:
* If a transponder is off or on standby, you will not see the aircraft on your radar screen.
* OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip;
* 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.
* 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.


=== Strips ===
For most interactions to work in FlightGear sessions while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange between the two programs:
[[File:ATC-pie-screenshot-stripDetailSheet.png|thumbnail|The ATC-pie strip detail sheet]]
* ATC-pie users can only hand over strips to OpenRadar that are linked to a radar contact;
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:
* aircraft under ATC-pie control are not shown as "owned" to OpenRadar users;
* most importantly, the aircraft's ''callsign'', to be used on the radio;
* handovers from ATC-pie will fail if an OpenRadar user is claiming ownership on the linked radar contact;
* information like aircraft type, airspeed, route... that can be specified by the pilots themselves when filing ''flight plans'';
* when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally.
* transponder code and flight parameter assignments (or vectors: heading, altitude/FL, speed).


=== Linking strips ===
Callsign handover policy:
Strip details can be manually edited, but every strip can also be '''linked''' to a flight plan and/or a visible radar contact on the scope screen—a strip can only be linked to one flight plan and one radar contact. Linking to a strip will automatically:
* OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
* make the strip display the missing elements made available by the linked aircraft transponder or flight plan;
* ATC-pie to OpenRadar: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
* label the radar contact dot with the more informed linked details, e.g. assigned altitude.
* pie-to-pie handovers through OpenRadar's service: strip detail preserved, whether present or absent.
Any detail mismatch between a strip and its linked flight plan or radar contact will be reported for you to resolve.


=== Radar identification ===
Features not supported by OpenRadar:
[[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]]
* wake turbulance category on strips (but detail preserved for ATC-pie clients later receiving the strip);
To ''identify'' an aircraft and link the right radar contact to a strip, an ATC can rely on different things. He 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 an initial radio contact giving his 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:
* ATC text messaging;
* the strip is assigned a transponder code;
* ATC phone lines;
* no other strip is assigned the same code;
* CPDLC transfers.
* the aircraft is the only one 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".
Who-has requests are fully supported.


== Using ATC-pie ==
=== Euroscope ===
To download the program and learn more about how to use it, read the [[ATC-pie user guide]].
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:
* 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]]

Latest revision as of 08:27, 2 April 2023

FlightGear logo.png The FlightGear forum has a
subforum related to: ATC-Pie support & development
This article is about the software and its features. For help with installation or configuration, see ATC-pie installation guide. For a manual on how to use it, see ATC-pie user guide.
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.8 (April 1, 2023)
Written in Python (Version 3)
OS Any
Platform Qt5
Development status Active
Type ATC client
License GNU GPL v3
Website

ATC-pie is a free (libre) air traffic control simulation program with strong ties to FlightGear. It features:

  • solo sessions with AI traffic (incl. voice instruction recognition and pilot read-back);
  • "multi-player" network sessions (FlightGear and FSD protocols supported);
  • tutorial sessions for teacher supervision of an ATC student.

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.

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

Screenshots

  • Sector view around Geneva

    Sector view around Geneva

  • Solo session with three coloured racks

    Solo session with three coloured racks

  • Background image display

    Background image display

  • Depiction of airport tarmac and objects

    Depiction of airport tarmac and objects

  • Runway incursion detected and highlighted in red

    Runway incursion detected and highlighted in red

  • Flight plan editor

    Flight plan editor

Visit the ATC-pie screenshot category for more.

Detailed feature list

Sessions and environments

Session/connection types:

  • solo simulation (AI traffic)
  • FlightGear network connection (FGMS protocol)
  • FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
  • teaching service (spawn and simulate traffic visible to a connected student)
  • student session (control traffic simulated by teacher)

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
Feature support by session type
Solo FlightGear FSD Tutoring (teacher/student)
ACFT traffic AI aircraft generated according to RWY capacities, ACFT equipment, intentions... connected flight sim pilots created and simulated by teacher
ATCs and coordination virtual ATCs depending on assumed positions connected ATC clients (full ATC-pie interaction, interoperability with other software) teacher-configured ATCs
Voice radio voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back FGCom-mumble integration teacher simulates pilots
ATC phone lines N/A integrated Mumble connection teacher simulates ATCs
Flight plans local entries only interface with the FlightGear de facto data base by Lenny64 available from network (NB: protocol does not support open/close and only pilots can file/amend FPLs) shared virtual online system
CPDLC interpreted subset of instruction messages integrated (supported by MP IRC) integrated interface with Hoppie's ACARS network full simulation by teacher (with WILCO assistance to execute instructions)
Weather randomised and evolving real world METAR retrieval fetch from server or retrieve real world METAR controlled by teacher
Other specific features
  • aircraft type and airline choice with custom appearence in tower view
  • configurable airspace rules and traffic density, incl. uncontrolled distractors
  • exact aircraft rendering in views (incl. control surfaces, etc.)
  • legacy stand-alone FGCom alternate possible (although deprecated)
  • frequency tuning system for radio text chat
  • text ATIS repeatedly sent through radio chat on recorded frequency
  • traffic snapshots and recall to repeat situations with the student
  • individual aircraft freeze

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
  • departure clearance assistant
  • 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, multiple radio transmissions and monitoring
  • ATIS recording and reminder alarm (see dialog with pre-filled notepad)
  • controller-pilot data link communication (CPDLC), incl. DEP clearance delivery, 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 and switchboard (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 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 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)
  • manual magnetic declination input

Interoperability with other software

OpenRadar

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 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 in FlightGear sessions while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange between the two programs:

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

  • OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
  • 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.

Features not supported by OpenRadar:

  • wake turbulance category on strips (but detail preserved for ATC-pie clients later receiving the strip);
  • ATC text messaging;
  • ATC phone lines;
  • CPDLC transfers.

Who-has requests are fully supported.

Euroscope

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:

  • 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.
Retrieved from "https://wiki.flightgear.org/w/index.php?title=ATC-pie&oldid=137480"