ATC-pie user guide: Difference between revisions

A click on the "new strip" tool bar button (shortcut <code>F2</code>) or double-click on an empty strip rack or bay space will open a dialog to fill flight details on a fresh blank strip, e.g. destination, type of aircraft, etc. Double-clicking on an existing strip allows to edit the filled details.

A strip can also be linked to a filed flight plan (FPL). This will make radar and strip display fall back on filed information for missing details. The strip dialog also shows the mismatching information between the two, though this is rather common because the strip typically gets updated as the flight progresses.

For fast and efficient service, every initial contact by a pilot should basically make you hit <code>F2</code> and type the callsign announced. You should then soon figure out if:

ATC-pie provides with three types of placeholders for flight strips: ''racks'', ''loose strip bays'' and ''runway boxes''. According to your ATC position and local facilities, you should choose and arrange your placeholders for optimal control. Strips can then be moved between them using mouse drag and drop.

A '''strip rack''' is the preferred way of keeping track of a sequence, e.g. a departure queue at a runway threshold. Rack panels can be created from the main window workspace, popped out as separate windows, and a persistent one can be found among the available docks. You can create as many racks as you wish in every panel. Double click on a rack's name to rename it or edit its properties. Use mouse drag to move strips up and down a rack sequence.

A '''loose strip bay''' allows free-hand positioning of strips in its reserved space. Such bays are useful for unsequenced traffic, or to map out relative positions when controlling without a radar. You may also import background images, e.g. a ground chart to keep visual track of taxiing aircraft and vehicles. See <code>CONFIG/bg-img/Notice</code> to learn how.

A '''runway box''' is a placeholder for a single strip, named after a physical runway and denoting a clearence to use it (enter, cross, land...). Runway boxes are contained in their own dock, with one made visible for each runway marked as in use in either direction. Thorough use of runway boxes will help you avoid bad mistakes like clear an aircraft to land over lined up traffic. When freed, runway boxes start and display a timer together with the wake turbulance category of the last contained strip to help with TKOF/LDG separation. What is more, if you use radar, a filled runway box marks the runway as ''reserved'' on the scope.

* an ATC callsign in the ATC panel to initiate a handover;

* a '''strip shelf''' (flat button at the bottom of loose and racked strip panels), which clears the strip from your workbench and stores it as shelved.

You can hook up '''additional viewers''' to your session, for example placed around your airport for exciting camera footage of challenging landings. You will not be able to control those viewers from ATC-pie like the tower viewer, but you will be able to activate/stop the connection from the ''View'' menu. Additional viewers are registered by their host+port address, from the ''View'' menu at run-time or from a custom settings file (see <code>CONFIG/Notice</code>) read at start-up and on explicit reload (''System'' menu).

* help monitor traffic, checking tracked positions against route/vector assignments;

* help manage traffic, anticipating route and FL conflicts between controlled aircraft.

* holding <code>SHIFT</code>, click and drag vertically for altitude/FL vectors;

* holding <code>SHIFT</code>, click and drag horizontally for speed instructions;

* holding <code>SHIFT</code>, double-click on the radar target to clear registered vecors from the linked strip.

NB: If DEP and ARR airports are not both recognised, radar tags show the strip destination detail if it is filled, possibly with a heading if it is recognised.

* alternatively, if the aircraft is connected to CPDLC, you can send instructions through the data link (see ''Mouse gestures'' in the quick reference, combining the <code>ALT</code> key).

* CPDLC authority transfers;

* voice land lines (direct phone calls);

* ''who-has'' requests, to query the system and know who is claiming contact/control of callsigns;

* ATC text chat, to exchange messages between connected ATCs (see ''Communications'' section).

On FlightGear session start, there are three "sub-systems" that can be activated for coordination. They differ in terms of supported features and interoperability with other clients:

* the '''IRC sub-system''' enables all coordination features with other ATC-pie clients, but does not currently operate with other software;

* the '''PyMumble land lines''' enable direct voice (telephone) lines to other connected ATCs in the ''ATC coordination'' panel (also ATC-pie only);

* who-has requests will remain unanswered by Euroscope;

* there are no integrated phone land lines to Euroscope clients.

ATC-pie clients interact normally between each other for all coordination purposes listed above, but note that CPDLC is not supported by the FSD protocol (so there will be no transfers).

The '''''PTT turns off sounds''''' option is recommended if you do not wear a headset. It will avoid picking up GUI sound notifications with your microphone while transmitting.

The ATC text messaging system allows to talk to other ATCs in channels that are separate from the public one read by pilots. It offers '''private channels''' simulating one-to-one landline conversations, and a '''general ATC chat room''' in network sessions, readable by all connected ATCs. Note however that ATC-pie features a direct voice (phone) land line switching system for a lot more realistic coordination between human ATCs!

* The ATC text chat system allows to chat to the student directly as the teacher, and to simulate landline conversations with the student (select ATC callsign to interact as).