265
edits
ATC-pie: Difference between revisions
v1.6.4
Mickybadia (talk | contribs) (Version 1.6.2) |
Mickybadia (talk | contribs) (v1.6.4) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = 1.6. | | latestrelease = 1.6.4 (March 15, 2020) | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| os = Any | | os = Any | ||
| Line 58: | Line 58: | ||
=== Strips === | === Strips === | ||
[[File:ATC-pie-screenshot-stripDetailSheet.png|thumbnail|The ATC-pie strip detail sheet]] | [[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 | 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; | * most importantly, the aircraft's ''callsign'', to be used on the radio; | ||
* information like aircraft type, airspeed, route... that can be | * information like aircraft type, airspeed, route... that can be provided by the pilots themselves when filing ''flight plans''; | ||
* transponder code and flight parameter assignments ( | * transponder code and flight parameter assignments (heading, altitude/FL, air speed). | ||
=== Linking strips === | === Linking strips === | ||
Every strip can be '''linked''' to a flight plan and/or a radar contact. A linked strip will automatically: | |||
* | * display its missing elements when available from the linked flight plan or aircraft transponder; | ||
* | * populate the linked aircraft radar tag with useful details, e.g. assigned altitude. | ||
Any detail mismatch between a strip and its linked | Any detail mismatch between a strip and its linked elements will be reported for you to resolve. | ||
=== 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 | When using radar, ATCs can rely on different things 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: | 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 122: | Line 122: | ||
* Position/track vs. assignment mismatch warning system | * Position/track vs. assignment mismatch warning system | ||
Tower viewing | Tower viewing for airport mode (requires FlightGear): | ||
* Renders view of airport, aircraft, weather, time of day | * Renders view of airport, aircraft, weather, time of day | ||
* Internally started or through an externally running instance | * Internally started or through an externally running instance | ||
| Line 131: | Line 131: | ||
Strips and racks: | Strips and racks: | ||
* User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from | * User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from | ||
* Strip auto-print for expected departures | * Strip auto-print for expected departures or arrivals | ||
* Runway boxes with automatic | * Runway boxes with automatic RWY separation timers | ||
* Loose strip bays with customisable backgrounds | * Loose strip bays with customisable backgrounds | ||