ATC-pie FAQ: Difference between revisions

Jump to navigation Jump to search

ATC-pie FAQ (view source)

Revision as of 19:17, 4 September 2022

573 bytes added ,  4 September 2022
v1.8.6
(v1.8.5)
(v1.8.6)
Line 6: Line 6:


=== This aircraft is connected but I am not seeing it on my radar. ===
=== This aircraft is connected but I am not seeing it on my radar. ===
You only see an aircraft on your scopes if a radar contact is established, i.e. if it is visible to the primary radar or if the secondary radar (SSR) picks up a transponder signal from it.
As in real life, the main radar technology is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], which only shows what is picked up from on-board transponders in its range. It coexists with primary radar, which detects aircraft regardless of transponders but offers no information other than position (angle and distance), i.e. neither of callsign, altitude, type, IAS, etc.


The following cases will therefore prevent you from seeing a connected aircraft:
The following cases will therefore prevent you from seeing a connected aircraft:
* The radars are turned off. Turn on at least a primary radar from the ''Options'' menu, or an SSR capability from the ''Radar'' tab in the ''Local settings'' dialog (any setting other than "none" will pick up contacts).
* The radars are turned off. Turn on at least a primary radar from the ''Options'' menu, or an SSR capability from the ''Radar'' tab in the ''Local settings'' dialog. Any SSR setting other than "none" will pick up contacts.
* The aircraft is out of radar range. It can be under the radar floor (minimum signal pick-up alt.) or too far out. In the radar settings, check the floor ("SFC" will pick up all signals down to the ground) and horizontal range. Primary and secondary radars share the same range.
* The aircraft is out of radar range, either too far out or under the radar floor. Check the horizontal range and floor settings ("SFC" will pick up all signals down to the ground). Primary and secondary radars share the same range.
* Its onboard transponder is turned off (and primary is off); see [https://www.youtube.com/watch?v=kpPzRiwzx9Q&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb&index=1 ATC-pie video tutorial 1]. You should tell the pilot to switch it on. Otherwise if you accept cheating, you can activate the "radar cheat mode" which will simulate a mode S transponder for all aircraft in horizontal range; see [https://www.youtube.com/watch?v=lSyH88HR-4w&index=3&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb tutorial 3].
* Its onboard transponder is turned off (and primary radar is off); see [https://www.youtube.com/watch?v=kpPzRiwzx9Q&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb&index=1 ATC-pie video tutorial 1]. You should tell the pilot to switch it on. Otherwise if you accept cheating, you can activate the "radar cheat mode" which will simulate a mode S transponder for all aircraft in horizontal range; see [https://www.youtube.com/watch?v=lSyH88HR-4w&index=3&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb tutorial 3].


=== Connected pilots do not receive my text messages. ===
=== Connected pilots do not receive my text messages. ===
This happens with pre-2017.2 clients if you are using the latest protocol to encode properties. Tick the FGMS system option to "use the legacy protocol" for property encoding. Everybody should be able to read you, but it will come at the expense of network throughput. Tell those pilots to upgrade their client.
This happens with pre-2017.2 FlightGear clients. Tell those pilots to upgrade! Until they do, you can tick the "legacy protocol" option from the FG system settings. Everybody should then be able to read you, but at the expense of network load.
 
=== The aircraft vectoring tool does not come up when I click and drag out of radar contacts. ===
Your radar contact is not linked. Link it to a strip to enable the vectoring feature. Vectors issued with it will be registered on the strip, and inform the displays according to the current options, e.g. altitude reaching point, unfollowed vector warnings, etc.


=== FGCom is not working. ===
=== FGCom is not working. ===
First, verify that the FGCom variant selected in the ''system settings'' is the one you want to use. Check that your sound is on, your volume loud and your microphone working (system sound monitor picking up a signal). Close all open sessions and open a single ATC-pie instance.
First, there are two variants for FGCom and you should note that they are ''not'' interoperable: users can only hear and interact with others using the same variant and server. Also note that the standalone variant is deprecated. So before troubleshooting it, you should consider switching to the newer [[FGCom-mumble]] variant.
 
If you have chosen the '''standalone''' FGCom variant, take the steps below in order:
# Echo test
#: Start a standalone FGCom configuration test from the system tools menu. While the test is running, speak in the microphone and check if you can hear yourself back. If so, you may skip directly to step 4.
# Path to executable
#: Verify the FGCom command entered in the system settings. It should contain an executable system command or a relative or absolute path to an FGCom executable file. If you have FlightGear installed on your machine, you can point to the FGCom executable already available with it. On Linux, the default "fgcom" command usually does the job. Otherwise, [https://sourceforge.net/projects/atc-pie/files/fgcom-standalone/ download an FGCom standalone program] from ATC-pie's SourceForge file list. In any case, try the entry from a terminal in the ATC-pie directory to manually check that it runs correctly.
# FGCom server status
#: The server may temporarily be down, unfortunately even for up to a few days. Check for responses from the server, e.g. with <code>ping fgcom.flightgear.org</code> (adjusting the server name to match the one entered in the settings). FGCom will not work without a responding server.
# FGCom subprocess error
#: After turning your radio on, check for errors in the logged FGCom output files in the <code>OUTPUT</code> directory.
# Port mess-up in your session?
#: When creating a new radio box at run time, make sure you choose an available port number for each. Caution when running multiple ATC-pie instances: do not use a port more than once across the system at the same time.
 
If you have chosen the '''FGCom-Mumble plug-in''':
# Plug-in status
#: Check that your Mumble client is connected and properly running the FGCom plug-in.
# Port setting
#: Check that the control port in ATC-pie is set to the one FGCom-Mumble is listening on.
# Echo test
#: Start an FGCom-Mumble configuration test from the system tools menu.


Note that the two variants are ''not'' interoperable. Users will only be able to hear and interact with others using the same variant (and server) as their own.
In either case, to troubleshoot:
* close all open sessions, open a single ATC-pie instance and check the FGCom variant selected in the ''system settings'';
* check that your sound is on, your volume loud and your system picking up a signal from your microphone;
* start an FGCom configuration test from the system tools menu;
* speak in the microphone while the echo test is running, and read below if you cannot hear yourself back.


=== Recording ATIS with standalone FGCom: no beep is heard after pressing "record". ===
'''FGCom-mumble''' is a plug-in that must be run with an external ''Mumble'' client (minimum version 1.4.0) connected to a chosen server. See the project [https://github.com/hbeni/fgcom-mumble/releases release] and wiki pages to download and install it. The control port in ATC-pie must be set to the one FGCom-mumble is listening on.
Assuming FGCom standalone is working (confirm this with an echo test before reading on)...


Due to the design of this legacy FGCom variant, you may only record an ATIS if the requested frequency is enlisted as recordable on the distant server's "phone book" for the airport. The one for <code>fgcom.flightgear.org</code> was compiled a while ago, based on the latest <code>apt.dat</code> at the time. It filtered the frequencies through the two following conditions:
For the '''standalone''' variant (deprecated), the FGCom command in the system settings should be a valid command or path to an FGCom executable. If you have FlightGear installed on your machine, you can point to the FGCom executable already available with it. On Linux, the default "fgcom" command usually does the job. Otherwise, get one from ATC-pie's [https://sourceforge.net/projects/atc-pie/files/fgcom-standalone/ SourceForge file list]. Try the entry from a terminal in the ATC-pie directory to manually check that it runs correctly. Other things you might check:
# it is of the "recorded" type (row code 50);
* server status: check for responses from the chosen server, e.g. with <code>ping</code>;
# its name contains the uppercase string "ATIS".
* subprocess error: after turning a first radio on, check the FGCom error logs in the <code>OUTPUT</code> directory;
 
* port mess-up: make sure you choose an available port number for each created radio at run time, e.g. do not use a port more than once when running multiple ATC-pie instances!
If you are relying on the old data provided by ATC-pie, in other words you have not downloaded new data or edited the frequencies yourself, check against the <code>.dat</code> file extracted in the <code>OUTPUT</code> directory on your side, as it should still be similar to the one on the server's side. One of the two conditions is probably not met, or the frequency missing. NB: The frequencies in the ATIS drop-down list of ATC-pie are matched against the condition (1), but not against the somewhat restrictive condition (2).
 
In any case, consider switching to the newer FGCom-Mumble plug-in variant. It simulates radio waves, frequencies and ranges, which avoids the phone book problem all together.


=== Tower view is not starting. ===
=== Tower view is not starting. ===
Ruling out that FlightGear is not installed at all, your system path settings are probably wrong. From a terminal or a file system navigator, find the right command to start FlightGear and enter it as ''FlightGear executable'' from the system settings. Do not add options of any kind; they will be taken care of internally. You may have to enter a ''FlightGear root directory'' as well, especially if you have the program files installed somewhere unexpected.
Ruling out that FlightGear is not installed at all, your system path settings are probably wrong. From a terminal or a file system navigator, find the right command to start FlightGear and enter it as ''FlightGear executable'' from the system settings. Do not add options here; they will be taken care of internally. You may have to enter a ''FlightGear root directory'' as well, especially if you have the program files installed somewhere unexpected.


=== My tower is in the middle of the sea, and aircraft floating/landing on water! ===
=== My tower is in the middle of the sea, and aircraft floating/landing on water! ===
You are missing the FlightGear scenery data for your location, or ATC-pie does not know where it is. If you have downloaded scenery and saved it somewhere, have you tried filling the scenery directory with that location in the system settings? Also check out the ''Tower viewing'' [[ATC-pie_user_guide#Tower_view_window|feature note]] in the user guide.
You are missing the FlightGear scenery data for your location, or ATC-pie does not know where it is. If you have downloaded scenery and saved it somewhere, have you tried filling the scenery directory with that location in the system settings? Also read the [[ATC-pie_installation_guide#Airport scene rendering|related section]] in the installation guide.


=== Simulated aircraft appear to dip underground or levitate over taxiways. ===
=== Simulated aircraft dip underground or levitate over taxiways. ===
Do you have a ground elevation map for the location? Quoting from <code>CONFIG/elev/Notice</code>: "''When no elevation map is found for an airport, the field elevation value is used everywhere on the ground. This should be OK for a rough approximation on flat terrain, but ground traffic will not follow any slopes, thus may appear as floating above the ground, or dipping into it.''" Read the full notice for instructions on how to build your elevation map.
Do you have a ground elevation map for the location? Quoting from <code>CONFIG/elev/Notice</code>: "''When no elevation map is found for an airport, the field elevation value is used everywhere on the ground. This should be OK for a rough approximation on flat terrain, but ground traffic will not follow any slopes, thus may appear as floating above the ground, or dipping into it.''" Read the full notice for instructions on how to build your elevation map.


Once you have one or decide that your field is flat enough, the next focus is on the FlightGear aircraft models. Each model has its own coordinate system chosen at developer's discretion. ATC-pie must be given the height difference between each model's origin and the aircraft touch-down point (gear wheels) to position aircraft more accurately. You can do this on a per-model basis with ":height" specifications in <code>CONFIG/acft/icao2fgfs</code>. Read the associated <code>Notice</code> section for more information.
Once you have an elevation map, the next focus is on the FlightGear aircraft models. Because each model has its own coordinate system chosen at developer's discretion, ATC-pie must be given the height difference between each model's origin and the aircraft touch-down point (gear wheels) to position aircraft more accurately. You do this on a per-model basis with ":height" specifications in <code>CONFIG/acft/icao2fgfs</code>. Read the associated <code>Notice</code> section for more information.


=== Phone lines have broken, choppy or dragged out sound ===
=== Phone lines have broken, choppy or dragged out sound ===
Line 77: Line 60:
=== What "social name" should I use for FlightGear/FSD sessions? ===
=== What "social name" should I use for FlightGear/FSD sessions? ===
Choose any name you would like to be recognised by on the network. In ATC-pie, it will appear in the tool tip over your callsign for connected ATCs who see you. This feature is only social in the sense that it does not refer to an account or to anything technical, but it makes sense as typical ATC callsigns (e.g. "VHHHtwr") remain mostly anonymous. Use this field to identify yourself on the network.
Choose any name you would like to be recognised by on the network. In ATC-pie, it will appear in the tool tip over your callsign for connected ATCs who see you. This feature is only social in the sense that it does not refer to an account or to anything technical, but it makes sense as typical ATC callsigns (e.g. "VHHHtwr") remain mostly anonymous. Use this field to identify yourself on the network.
=== What is the purpose of the flat "strip shelf" button in the strip panes? ===
More than a button, the strip shelf is where you should drop the contacts you release without a handover, e.g. parked traffic shutting down, VFR traffic flying out of your airspace, etc. Clicking on the shelf allows to browse the previously shelved strips, and to recall them, for example if shelved inadvertently.
=== What is "radio direction finding"? ===
RDF is a system that detects the horizontal direction of radio sources when signals are received. Its most common uses are:
* to locate ACFT making new radio contacts on their first transmissions;
* to give bearings to the airport to disoriented VFR pilots.
Setting up your location as equipped with RDF will essentially provide two things:
* a status bar indication of the form "hdg/qdm" in the main window, where "hdg" is the heading of the currently detected radio signal (direction to source, or "---" if none), and "qdm" the opposite heading of the last received signal (bearing from source, displayed until the next signal is received);
* the option to draw a line on radar scopes when a signal is received, making it easy to visualise the transmitting ACFT as the line should hit its target.


=== Are the vector headings true or magnetic? ===
=== Are the vector headings true or magnetic? ===
Line 83: Line 78:
Also note: all directions are geodesic, i.e. initial headings to take on a great circle.
Also note: all directions are geodesic, i.e. initial headings to take on a great circle.


=== What is the purpose of the flat "strip shelf" button in the strip panes? ===
=== How do approach spacing hints work? ===
More than a button, the strip shelf is where you should drop the contacts you release without a handover, e.g. parked traffic shutting down, VFR traffic flying out of your airspace, etc. Clicking on the shelf allows to browse the previously shelved strips, and to recall them, for example if shelved inadvertently.
When the option is turned on, an approach spacing hint will show on every strip verifying the following conditions:
* it is racked in sequence behind another marked with the same (recognised) destination;
* both are linked to an airborne aircraft with a known ground speed;
* the time hint value (see below) does not exceed 30 minutes.
 
The first hint shown on a strip is an estimated time difference between the linked aircraft touchdown and that of the traffic ahead (see the quick reference for more details: ''Display conventions'' for strips). To work it out, ATC-pie assumes:
* both present ground speeds;
* for the aircraft ahead, a straight path to destination;
* for the linked aircraft, a path straight to the one ahead first, then straight to destination.
 
Caution: some judgement is required depending on the aircraft positions, because the actual paths to expect can vary from those above. For example, the interpretation of the hint should be different whether both aircraft are aligned with the runway or coming from opposite directions.


=== What do the various markings along the approach centre line mean? ===
=== What do the various markings along the approach centre line mean? ===
Line 127: Line 132:
Besides, you can create aliases with the local notepad for a quick and integrated way of sending them through text chat, which will be saved when you close ATC-pie. For example, use the following format, one runway per line: <code>ils05=111.11 MHz</code>. See [[ATC-pie_user_guide#Public text chat|custom text aliases]] for more.
Besides, you can create aliases with the local notepad for a quick and integrated way of sending them through text chat, which will be saved when you close ATC-pie. For example, use the following format, one runway per line: <code>ils05=111.11 MHz</code>. See [[ATC-pie_user_guide#Public text chat|custom text aliases]] for more.


=== The navigation/airport data is outdated. How can I update it? ===
=== The airport/navigation data is outdated. How can I update it? ===


For '''airport data''' (taxiways, parking positions, frequencies, etc.), the included source is the last world-wide <code>apt.dat</code> compiled before it became too large to maintain as one huge file. We keep it there because it allows to run ATC-pie anywhere in the world without requiring external data, but its contents grows out of date with time. You should check for more recent sources on the [http://gateway.x-plane.com/airports/page X-plane airport gateway], directly accessible from the ''System'' menu, on a per-airport basis. Extract the <code>apt.dat</code> file from the download, rename it after the airport's ICAO code (keeping the extension, e.g. <code>KJFK.dat</code>), and place it in <code>CONFIG/ad</code> (also see the <code>Notice</code> there). Alternatively, for a quick manual touch-up of the included data, you can move and edit extracted files (see <code>OUTPUT/Notice</code>).
The included '''airport data''' (taxiways, parking positions, frequencies, etc.) is the latest but outdated world-wide <code>apt.dat</code> file compiled by ''X-plane'' ages ago. We keep it there because it allows to run ATC-pie anywhere in the world without requiring external data, but for any serious work at a specific airfield, you should provide the latest source available on the [http://gateway.x-plane.com/airports/page X-plane airport gateway], directly accessible from the ''System'' menu. Extract the <code>apt.dat</code> file from the downloaded package, rename it after the airport's ICAO code keeping the extension (e.g. <code>KJFK.dat</code>), and place it in <code>CONFIG/ad</code> (see the <code>Notice</code> there). Alternatively, for a quick manual touch-up of the old data, you can use the locally extracted file (see <code>OUTPUT/Notice</code>).


For '''navigation data''' (navaids, fixes, airways, etc.), the included data is the latest version of each file that was seen released as GPL, which makes some of it date back to 2013! You should provide more recent navigation data, as explained in <code>CONFIG/nav/Notice</code>.
The included '''navigation data''' (navaids, fixes, airways, etc.) is the latest GPL version seen for each relevant ''X-plane'' file, also all out of date today. You should provide more recent navigation data, as explained in <code>CONFIG/nav/Notice</code>.


=== How do I customise the GUI and colours? ===
=== How do I customise the GUI and colours? ===
Mickybadia
265

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/135470"

Navigation menu