265
edits
ATC-pie: Difference between revisions
v 1.5.2
Mickybadia (talk | contribs) (v 1.5.1) |
Mickybadia (talk | contribs) (v 1.5.2) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = 1.5. | | latestrelease = 1.5.2 (August 25, 2018) | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| os = Any | | os = Any | ||
| Line 20: | Line 20: | ||
}} | }} | ||
'''ATC-pie''' is an [[air traffic control]] simulation program | '''ATC-pie''' is an [[air traffic control]] simulation program featuring solo sessions, multi-player network connections (through [[FGMS]]) and tutorial sessions for teacher supervision of an ATC student. It can simulate en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...), and allows 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 49: | Line 49: | ||
=== General === | === 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 | 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 student traffic generated and controlled by the teacher, all with different types of aircraft, [[transponder]] equipment and intentions. | ||
As in real life, your main | As in real life if you use a radar, your main technology is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], hence unless you cheat or activate the primary radar, it 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 off or out of range, 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. | * if a transponder is on and in range, 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 and your radar capabilities. | ||
=== Strips === | === Strips === | ||
| Line 70: | 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]] | ||
When using radar, ATCs can rely on different things to ''identify'' an aircraft and link the right contact to a strip. 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: | 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: | ||
| Line 82: | Line 82: | ||
Available modes and session types: | Available modes and session types: | ||
* FlightGear multi-player connections | * FlightGear multi-player connections | ||
* Solo sessions with simulated IFR traffic | * 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 | * For all sessions in airport mode: 3D tower view available | ||
=== Session environments === | === Session environments === | ||
FlightGear multi-player sessions: | FlightGear multi-player sessions: | ||
* Connection to FGMS networks | |||
* Strip exchange: handovers with other ATC-pie and [[OpenRadar]] instances in range | |||
* 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), incl. run-time retrieval, opening, closing, filing and editing (work on local copies and manage sync with online status) | * 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 | ||
| Line 99: | Line 100: | ||
* Voice instruction recognition (with Sphinx) | * Voice instruction recognition (with Sphinx) | ||
* Pilot read-back speech synthesis (with pyttsx) | * Pilot read-back speech synthesis (with pyttsx) | ||
* Strip exchange: handovers to/from virtual ATCs | |||
* Weather: randomised | * Weather: randomised | ||
* Airline choice and custom aircraft appearence | * Airline choice and custom aircraft appearence | ||
* Configurable airspace rules and entry/exit/routing points | * Configurable airspace rules and entry/exit/routing points | ||
| Line 107: | Line 108: | ||
Tutoring sessions (teacher with student): | 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) | ||
* Strip exchange: configurable ATC neighbours and handover supervision by teacher | |||
* Weather: wind control by teacher | * Weather: wind control by teacher | ||
* Traffic snapshots and recall to repeat situations with the student | * Traffic snapshots and recall to repeat situations with the student | ||
| Line 116: | Line 117: | ||
* Ground elevation maps (can be generated automatically with a provided script) | * Ground elevation maps (can be generated automatically with a provided script) | ||
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.) | * Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.) | ||
* | * Real world magnetic declination lookup | ||
=== General === | === General === | ||
| Line 127: | Line 128: | ||
Misc. tools: | Misc. tools: | ||
* Quick point-to-point heading and distance measuring tool | * Quick point-to-point heading and distance measuring tool | ||
* Multiple weather station monitor | * Multiple weather station monitor | ||
* Direct text annotation of radar screen | * Direct text annotation of radar screen | ||
* AD/ | * World airport, map navpoint and AD parking position browsing/indicating | ||
* | * Aeronautical unit conversion calculator | ||
* 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 | * General and location-specific notes and settings saved on close and restored on restart | ||
| Line 137: | Line 138: | ||
=== ATC surveillance === | === ATC surveillance === | ||
Radar and transponders: | Radar and transponders: | ||
* SSR and primary radar activation | * SSR mode selection and primary radar activation | ||
* Full transponder support and mode-dependant radar behaviour | * Full transponder support and mode-dependant radar behaviour | ||
* | * Traffic identification assistant | ||
* Runway occupation/incursion detection | * Runway occupation/incursion detection | ||
* Visible mismatches between assigned vectors and picked up positions | * Visible mismatches between assigned vectors and picked up positions | ||
| Line 164: | Line 165: | ||
=== Communications === | === Communications === | ||
Radio: | Radio: | ||
* [[FGCom]] integration | * [[FGCom]] integration (not for solo sessions; possible use of externally running client), incl. ATIS recording (see [[:File:ATC-pie-screenshot-ATISdialog.png|feature dialog]] with pre-filled preparation notepad), multiple frequency transmissions and monitoring, frequency-specific sound level selection | ||
* Radio direction finding (not available on FlightGear MP networks) | |||
ATC coordination: | ATC coordination: | ||
* General ATC chat room | * General ATC chat room | ||
* Private messaging ("landlines") | * Private messaging (text "landlines") | ||
* "Who has" requests | * "Who has" requests | ||