265
edits
ATC-pie: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Mickybadia (talk | contribs) mNo edit summary |
Mickybadia (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = Febuary 1, 2015 | | initialrelease = Febuary 1, 2015 | ||
| latestrelease = Febuary | | latestrelease = Febuary 11, 2015 | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| os = Any | | os = Any | ||
| Line 25: | Line 25: | ||
=== General === | === General === | ||
* Real METAR updates with selectable weather station | * Real METAR updates with selectable weather station | ||
* Real declination lookup and true/magnetic distinction | * Real declination lookup and true/magnetic distinction | ||
* Data retrieved from the latest [http://data.x-plane.com X-Plane] file set | * Data retrieved from the latest [http://data.x-plane.com X-Plane] file set | ||
* In-app announcement of ATC session on Lenny64's popular [http://flightgear-atc.alwaysdata.net ATC event page] | * In-app announcement of ATC session on Lenny64's popular [http://flightgear-atc.alwaysdata.net ATC event page] | ||
* Network text chat system | * Network text chat system | ||
* Manage ignored contacts | * Manage ignored contacts | ||
=== Transponder support === | === Transponder support === | ||
| Line 59: | Line 54: | ||
* Use of separate (externally running) FGCom possible | * Use of separate (externally running) FGCom possible | ||
=== Strip management === | === Strip, route and flight plan management === | ||
* Strip drag&drop along and across user-defined strip racks racks | |||
* Strip drag&drop along and across racks | |||
* Link strips to flight plans and radar contacts to merge editable details and inform radar display | * Link strips to flight plans and radar contacts to merge editable details and inform radar display | ||
* Interface with Lenny64's [http://flightgear-atc.alwaysdata.net flight plan data base] including in-game FPL retrieval, filing and editing | |||
* FPL, transponder and vectoring assignment conflicts reported | * FPL, transponder and vectoring assignment conflicts reported | ||
* Strip route management and next waypoint display | |||
* Work with local FPL copies and manage sync with online publication | |||
=== | === GUI === | ||
* | * Floatable/dockable GUI panes: strips, radios, text chat, etc. | ||
* | * General and airport-specific settings saved on close and restored on restart | ||
* Notification system combining selectable sounds, status bar messages and a time-tagged history | |||
* Personal notepads (general and airport-specific) saved across sessions | |||
== Screenshots == | == Screenshots == | ||
{{Gallery | |||
|ATC-pie-screenshot-radarIdentification.png|Radar identification marked in blue (unique strip–transponder match) | |||
-- | |ATC-pie-screenshot-LFPGcloseUp.png|Fine airport tarmac depiction | ||
|ATC-pie-screenshot-stripDetailSheet.png|Strip detail sheet with editable route | |||
|ATC-pie-screenshot-ATISdialog.png|ATIS recording feature with scrap notebook | |||
}} | |||
== Working principles == | == Working principles == | ||
| Line 103: | Line 104: | ||
== User guide == | == User guide == | ||
This section is | This section is very poor standalone documentation. It helps one download and run ATC-pie, and lists a few tips on some of its features. Yet better sources to learn the program are: | ||
* the in-app ''quick reference'' from the help menu (summary of mouse/keyboard gestures, etc.); | |||
* the tutorial videos (to be announced). | |||
Anyone motivated to write a full user guide is obviously welcome to contact the developer. | |||
=== Getting it to run === | === Getting it to run === | ||
| Line 118: | Line 123: | ||
==== Starting the program ==== | ==== Starting the program ==== | ||
Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you need to start the program is to run a Python3 interpreter on the <code>ATC-pie.py</code> file in the top-level directory. To start at a chosen airport location, say with code ICAO, | Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you need to start the program is to run a Python3 interpreter on the <code>ATC-pie.py</code> file in the top-level directory. To start at a chosen airport location, say with code ICAO, add a system command-line argument, which may look as simple as: | ||
: <code>./ATC-pie.py ICAO</code> | : <code>./ATC-pie.py ICAO</code> | ||
| Line 125: | Line 130: | ||
=== Tips === | === Tips === | ||
Here are a few | Here are a few tips to help you navigate and use the program. | ||
* '''Callsigns''' typically start with the ICAO code of a controlled airport, and end with a hint on the provided service: twr, gnd... With no callsign given, you will appear as "ICAOobs" on network connect. Note that FGMS restricts callsigns lengths to 7 characters. :-( | * '''Callsigns''' typically start with the ICAO code of a controlled airport, and end with a hint on the provided service: twr, gnd... With no callsign given, you will appear as "ICAOobs" on network connect. Note that FGMS restricts callsigns lengths to 7 characters. :-( | ||
* For more efficient text chat, a growing list of '''text aliases''' exist (<code>$wind</code>, <code>$qnh</code>, <code>$icao</code>...) | * For more efficient text chat, a growing list of '''text aliases''' exist (<code>$wind</code>, <code>$qnh</code>, <code>$icao</code>...) for both instant and preset chat messages. They automatically expand to the current value when message is sent. | ||
* In airport input fields, a single dot will be replaced by your ICAO position. Use this as a '''shortcut from/to your airport''' when filling strip/FPL details. | |||
Any strip with valid departure and arrival airports will contain a '''parsed route'''. Recognised navpoints in the route field (whitespace-sparated tokens) create waypoints on the way to arrival. All other tokens are stored as route leg specifications to the following waypoint. The current route leg of the selected aircraft (leg spec + waypoint) is displayed in the info pane. | |||
==== Information display ==== | |||
* '''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exception perhaps are the navigator tooltips, for easier identification on the scope. | * '''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exception perhaps are the navigator tooltips, for easier identification on the scope. | ||
* The '''transition level''' is by definition the lowest flight level that is still above the transition altitude. This does not mean the lowest assignable FL, which may take more vertical separation. | * The '''transition level''' is by definition the lowest flight level that is still above the transition altitude. This does not mean the lowest assignable FL, which may take more vertical separation. | ||
* The grouped '''tick marks along the localiser line''' (when shown) indicate best altitudes AMSL for final approach along the defined slope rate. Every mark in a group is 1,000 ft. | * The grouped '''tick marks along the localiser line''' (when shown) indicate best altitudes AMSL for final approach along the defined slope rate. Every mark in a group is 1,000 ft. | ||
* "OK" near the '''route field''' on the strip detail sheet means that the route could be parsed correctly; otherwise "!!" is displayed. This does not matter, only the info boxes will be showing destination (or nothing if unknown) instead of next waypoint. | |||
* "OK" near the | |||
==== Radio ==== | |||
Say you are TWR coordinating with GND at an airport and you want to '''monitor both radio frequencies''' while you are only in charge of one. You can set this up by starting your own radio box on TWR frequency, and turn on a second one to monitor GND, setting the volume to "soft" on the latter so that you can always tell if a message is for you to answer or not. | Say you are TWR coordinating with GND at an airport and you want to '''monitor both radio frequencies''' while you are only in charge of one. You can set this up by starting your own radio box on TWR frequency, and turn on a second one to monitor GND, setting the volume to "soft" on the latter so that you can always tell if a message is for you to answer or not. | ||
The '''FGCom version setting''' is the name of a subdirectory in <code>resources/fgcom</code>. See <code>Notice</code> file there. | |||
==== Resolving conflicts ==== | |||
Strip–FPL conflicts: | |||
* to confirm all strip details: open the strip detail sheet, tick the "push details to FPL" box and save to propagate the strip details; | * to confirm all strip details: open the strip detail sheet, tick the "push details to FPL" box and save to propagate the strip details; | ||
* to confirm all FPL details: reset the strip to overwrite its details with those of the linked flight plan; | * to confirm all FPL details: reset the strip to overwrite its details with those of the linked flight plan; | ||
* to confirm some details of each source: | * to confirm some details of each source: open the strip detail sheet, get rid of the bad details and save without pushing to the flight plan to fall back on the first case where all strip details can be confirmed. | ||
Flight plan local–online conflicts: | |||
* to update the online version with your local modifications, double-click the flight plan and tick the "publish" box before saving (if still decorated red, there was a network problem or the change was rejected by the server); | * to update the online version with your local modifications, double-click the flight plan and tick the "publish" box before saving (if still decorated red, there was a network problem or the change was rejected by the server); | ||
* to discard all local modifications of an online FPL, remove the FPL from the list and check for new flight plans again (the deleted entry should be retrieved with online state). | * to discard all local modifications of an online FPL, remove the FPL from the list and check for new flight plans again (the deleted entry should be retrieved with online state). | ||
[[Category:ATC clients]] | [[Category:ATC clients]] | ||