ATC-pie: Difference between revisions

1,302 bytes added ,  26 March 2015
no edit summary
No edit summary
Tag: Mobile edit
No edit summary
Line 117: Line 117:
Any detail mismatch between a strip and its linked flight plan or radar contact will be reported for you to resolve.
Any detail mismatch between a strip and its linked flight plan or radar contact will be reported for you to resolve.


=== Radar identification ===
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 it is visible (or cheated), 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:
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 it is visible (or cheated), 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:
* the strip is assigned a transponder code;
* the strip is assigned a transponder code;
Line 177: Line 178:


==== Radio and communications ====
==== Radio and communications ====
The '''FGCom version''' setting is the name of a subdirectory in <code>resources/fgcom</code>. See <code>Notice</code> file in that directory. FGCom version should be 3.4 (January 2015).
Say you are TWR coordinating with GND at your airport, and you want to '''monitor both radio frequencies''' while you are only in charge of one. To set this up, start your radio box on TWR frequency and turn on a second one to monitor GND, tick "Kbd PTT" only for TWR so that you only transmit to your frequency and don't interfere with the other, and set 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 your airport, and you want to '''monitor both radio frequencies''' while you are only in charge of one. To set this up, start your radio box on TWR frequency and turn on a second one to monitor GND, tick "Kbd PTT" only for TWR so that you only transmit to your frequency and don't interfere with the other, and set the volume to "soft" on the latter so that you can always tell if a message is for you to answer or not.


Line 239: Line 238:


A: Yes, and virtually anything else, using background images and hand drawings. See the tip section above.
A: Yes, and virtually anything else, using background images and hand drawings. See the tip section above.
'''Q: FGCom radio is not working. What is going on?'''
A: There can be a variety of reasons, all of them to rule out before reporting a bug in the program. Start a single ATC-pie instance and try the echo test (system menu). If it works, you may skip directly to item 3 below.
# bad FGCom version setting
#: Verify the "FGCom version" set in the system menu, which should name a subdirectory in <code>resources/fgcom</code> and suit your operating system (see <code>Notice</code> file). Four versions are initially packaged with ATC-pie: Linux64, Linux32, Mac, Win32. FGCom version should be 3.4 (January 2015).
# FGCom server down
#: This does happen, sometimes unfortunately for up to a few days. Check for responses from the server, e.g. with <code>ping fgcom.flightgear.org</code>.
# FGCom run time error
#: If the server is up, check for errors in the logged FGCom output files in the <code>output</code> directory.
# port mess-up on your side
#: If you are running multiple instances of ATC-pie, make sure you have no more than one radio box on every port. In any case, verify you only choose available ports that are not already in use by your operating system for example. Typically, default ports (from 16661 counting up) work fine, but you will have to change them for parallel instances, using the --fgcom-ports= command-line option (see section: ''starting the program''). To check what port a radio box is using, see the "On/off" button tooltip.


[[Category:ATC clients]]
[[Category:ATC clients]]
265

edits