https://wiki.flightgear.org/w/api.php?action=feedcontributions&user=Jomo&feedformat=atomFlightGear wiki - User contributions [en]2024-03-28T08:25:57ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=117740OpenRadarGuide2019-04-07T06:00:43Z<p>Jomo: </p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "itpns.ddns.net"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see https://sourceforge.net/projects/openradar/files/<br />
* Download "Latest Release" for the latest version prior to the new "Flight-Strip-Bay" version<br />
* Download "Next Release" for the really newest version.<br />
Prior to extracting move the ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''itpns.ddns.net'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''not use''' runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''use''' runway 18 for "Starts" only --> thus enable "Starts" only<br />
:::'''use''' runway 07L and 25R for "Landings" only --> thus enable only "Landing"<br />
:::<small>(Compare the picture "The Runway Manager" on the right: The left marks enable the function - the right ones enable the SID/STAR functions)<br />
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="keytable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[sourceforge.net/projects/openradar/files|'''Download''' OpenRadar]]<br />
* [[OpenRadar_FGFS_ORCAM|'''ORCAM''' = View the targets as model]]<br />
* [[OpenRadar:_Transponder|Using '''Transponder'''-Codes]]<br />
* [[OpenRadar: Editing routes|Editing '''STAR/SID''' routes]]<br />
* [[OpenRadar:_Flightstrip|'''Flightstrips''']]<br />
* [[OpenRadar:_Flightstrips-Bay|'''Flightstrips-Bay''']]<br />
* [[OpenRadar:_Chat_aliases|'''Chat_aliases''']]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadarFeatureWishlist|OpenRadarFeatureWishlist]]<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:EDDF-ATC-20190105.jpg&diff=117065File:EDDF-ATC-20190105.jpg2019-01-08T17:15:47Z<p>Jomo: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Working as ATC}}<br />
|date=2019-01-08<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:ATCing]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:EDDF-ATC-20190105.png&diff=117064File:EDDF-ATC-20190105.png2019-01-08T16:33:27Z<p>Jomo: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Working as ATC at EDDF}}<br />
|date=2019-01-08<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:ATCing]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:Proposed_BlueYellow_replacment_for_EDDF.png&diff=107979File:Proposed BlueYellow replacment for EDDF.png2017-06-01T09:10:34Z<p>Jomo: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Replaced standard GLIDER-model by A321/A321-WowAir.xml -- in order for ATC's to spot easy!}}<br />
|date=2017-06-01<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:EDDF-terraGIT.png&diff=107820File:EDDF-terraGIT.png2017-05-13T08:17:35Z<p>Jomo: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=First use of the new terraGIT-scenery during our regular EDDF-Triangle Events}}<br />
|date=2017-05-13<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other versions=<br />
}}<br />
EDDF scenery<br />
<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Scenery]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=107273OpenRadarGuide2017-03-04T15:12:50Z<p>Jomo: /* OpenRadar */ change Download Internetpage</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see https://sourceforge.net/projects/openradar/files/<br />
* Download "Latest Release" for the latest version prior to the new "Flight-Strip-Bay" version<br />
* Download "Next Release" for the really newest version.<br />
Prior to extracting move the ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''mumble.allfex.org'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="keytable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[sourceforge.net/projects/openradar/files|'''Download''' OpenRadar]]<br />
* [[OpenRadar_FGFS_ORCAM|'''ORCAM''' = View the targets as model]]<br />
* [[OpenRadar:_Transponder|Using '''Transponder'''-Codes]]<br />
* [[OpenRadar: Editing routes|Editing '''STAR/SID''' routes]]<br />
* [[OpenRadar:_Flightstrip|'''Flightstrips''']]<br />
* [[OpenRadar:_Flightstrips-Bay|'''Flightstrips-Bay''']]<br />
* [[OpenRadar:_Chat_aliases|'''Chat_aliases''']]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadarFeatureWishlist|OpenRadarFeatureWishlist]]<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadar_FGFS_ORCAM&diff=104265OpenRadar FGFS ORCAM2016-09-25T16:39:14Z<p>Jomo: /* Move camera location */ change mouse-key for view-save</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running FlightGear to make it act like a tower window, or a airport surveillance camera.<br />
<br />
== Introduction ==<br />
With only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.<br />
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.<br />
<br />
'''Forwarding of multiplayer data'''<br />
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.<br />
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.<br />
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.<br />
<br />
== Configuration ==<br />
=== Install the aircraft orcam ===<br />
At first you need to install the flightgear aircraft ''ORCAM''. It is a slightly modified ATC aircraft. <br />
<br />
All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface. <br />
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable. Help is appreciated anyway!<br />
<br />
The aircraft is delivered with OpenRadar. You find it in OpenRadar's subdirectory "orcam". Please extract it into your aircraft directory!<br />
<br />
(If it is not there, please update your OpenRadar first!)<br />
<br />
=== Write a fgfs startup script ===<br />
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to. <br />
The script can look like this:<br />
<pre><br />
#!/bin/bash --<br />
fgfs \<br />
--aircraft=ORCAM \<br />
--callsign=_ \<br />
--airport=LFSB \<br />
--telnet=,,100,,5010, \<br />
--multiplay=in,100,,5010 \<br />
--multiplay=out,100,localhost,5010 \<br />
--fg-aircraft=/data/fgdata/Aircraft<br />
</pre><br />
<br />
'''The parameters'''<br />
{| class="wikitable"<br />
|-<br />
! parameter !! Note<br />
|-<br />
| --aircraft || This tells fgfs which aircraft to load<br />
|-<br />
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.<br />
|-<br />
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.<br />
|-<br />
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.<br />
|-<br />
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.<br />
|}<br />
Note: You may add all other flightgear parameters too. This is an example only.<br />
<br />
It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.<br />
OpenRadar will restore the first camera preset at start, healing this.<br />
<br />
=== Configure OpenRadar ===<br />
The known startup dialog of OpenRadar has got a new tab for ORCAM.<br />
<br />
[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]<br />
<br />
These settings define the other, controlling side of the setup.<br />
{| class="wikitable"<br />
|-<br />
! Field !! Example !! Content<br />
|-<br />
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off<br />
|-<br />
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam<br />
|-<br />
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above<br />
|-<br />
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.<br />
|-<br />
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.<br />
|}<br />
<br />
These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)<br />
<br />
== Setups ==<br />
=== One Camera ===<br />
==== One computer ====<br />
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).<br />
<br />
{| class="wikitable"<br />
|-<br />
! Computer !! OR Parameter !! FGFS Setting<br />
|-<br />
| localhost || <pre>Enable Cam 1: checked<br />
Client host: localhost<br />
FGFS telnet Port: 5010<br />
Enable MP forwarding: checked<br />
FGFS MP Port: 5010<br />
</pre><br />
|| <br />
<pre><br />
<br />
<br />
--telnet=,,100,,5010, \<br />
--multiplay=in,100,,5010 \<br />
--multiplay=out,100,localhost,5010 \<br />
</pre><br />
|}<br />
==== Two Computers ====<br />
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Computer !! OR Parameter !! FGFS Setting<br />
|-<br />
| computer1 == localhost || <pre>Enable Cam 1: checked<br />
Client host: computer2<br />
FGFS telnet Port: 5010<br />
Enable MP forwarding: checked<br />
FGFS MP Port: 5010<br />
</pre><br />
|| no ORCAM ||<br />
|-<br />
| computer 2 || no OpenRadar ||<br />
<pre><br />
--telnet=,,100,,5010, \<br />
--multiplay=in,100,,5010 \<br />
--multiplay=out,100,computer1,5010 \<br />
</pre><br />
|}<br />
<br />
<br />
<br />
=== Two Cameras ===<br />
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.<br />
<br />
==== Two Computers ====<br />
<br />
I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!<br />
<br />
{| class="wikitable"<br />
|-<br />
! Instance !! Computer !! OR Parameter !! FGFS Setting<br />
|-<br />
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked<br />
Client host: localhost<br />
FGFS telnet Port: 5010<br />
Enable MP forwarding: checked<br />
FGFS MP Port: 5010<br />
</pre><br />
|| <br />
<pre><br />
<br />
<br />
--telnet=,,100,,5010, \<br />
--multiplay=in,100,,5010 \<br />
--multiplay=out,100,localhost,5010 \<br />
</pre><br />
|-<br />
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked<br />
Client host: computer2<br />
FGFS telnet Port: 5020<br />
Enable MP forwarding: checked<br />
FGFS MP Port: 5020<br />
</pre><br />
|| <br />
<pre><br />
<br />
<br />
--telnet=,,100,,5020, \<br />
--multiplay=in,100,,5020 \<br />
--multiplay=out,100,computer1,5020 \<br />
</pre><br />
|}<br />
<br />
==== One, very powerful computer ====<br />
<br />
{| class="wikitable"<br />
|-<br />
! Instance !! Computer !! OR Parameter !! FGFS Setting<br />
|-<br />
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked<br />
Client host: localhost<br />
FGFS telnet Port: 5010<br />
Enable MP forwarding: checked<br />
FGFS MP Port: 5010<br />
</pre><br />
|| <br />
<pre><br />
<br />
<br />
--telnet=,,100,,5010, \<br />
--multiplay=in,100,,5010 \<br />
--multiplay=out,100,localhost,5010 \<br />
</pre><br />
|-<br />
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked<br />
Client host: localhost<br />
FGFS telnet Port: 5020<br />
Enable MP forwarding: checked<br />
FGFS MP Port: 5020<br />
</pre><br />
|| <br />
<pre><br />
<br />
<br />
--telnet=,,100,,5020, \<br />
--multiplay=in,100,,5020 \<br />
--multiplay=out,100,localhost,5020 \<br />
</pre><br />
|}<br />
=== Two Cameras, second camera shows same picture like first ===<br />
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.<br />
<br />
Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!<br />
<br />
This will remove the second cam control line in OR and control CAM2 just like CAM1.<br />
<br />
== Usage ==<br />
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.<br />
<br />
[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]<br />
<br />
This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.<br />
<br />
=== Activate a preset ===<br />
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.<br />
<br />
To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.<br />
<br />
=== Modifying the view ===<br />
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed. <br />
Try it: Click the right mouse button in flightgear window and move your mouse.<br />
<br />
You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.<br />
<br />
And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)<br />
<br />
=== Save a preset ===<br />
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.<br />
<br />
=== Move camera location ===<br />
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.<br />
<br />
# Enable the preset you want to move<br />
# Move the OR map (zoom), to be able to click, where your camera should be<br />
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.<br />
# Click on the map, where the camera should be. MoveCam change its colour to normal and the FGFS display will move to the new position.<br />
# In FGFS modify your camera view and save it via "centre mouse click" onto the current preset.<br />
<br />
=== Follow a contact ===<br />
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.<br />
<br />
As long as he is in view (6000m), OR will tell FGFS to follow this contact. <br />
<br />
OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.<br />
<br />
You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.<br />
<br />
To '''start follow mode''', click on Follow, while the contact is selected. The text follow changes, to display whom OR follows.<br />
<br />
To '''end the follow mode''', click on Follow again, while the followed contact is selected.<br />
<br />
To '''follow somebody else''', select the new contact and follow him.<br />
<br />
== FAQ ==<br />
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.<br />
<br />
[[Category:OpenRadar]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=104142OpenRadarGuide2016-09-19T09:01:59Z<p>Jomo: /* Related content */ Add more References (Flightstrips, new DownloadAdr, etc)</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see https://sourceforge.net/projects/openradar/files/latest/download?source=files. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''mumble.allfex.org'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="keytable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[sourceforge.net/projects/openradar/files|'''Download''' OpenRadar]]<br />
* [[OpenRadar_FGFS_ORCAM|'''ORCAM''' = View the targets as model]]<br />
* [[OpenRadar:_Transponder|Using '''Transponder'''-Codes]]<br />
* [[OpenRadar: Editing routes|Editing '''STAR/SID''' routes]]<br />
* [[OpenRadar:_Flightstrip|'''Flightstrips''']]<br />
* [[OpenRadar:_Flightstrips-Bay|'''Flightstrips-Bay''']]<br />
* [[OpenRadar:_Chat_aliases|'''Chat_aliases''']]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadarFeatureWishlist|OpenRadarFeatureWishlist]]<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=104139OpenRadarGuide2016-09-17T15:14:45Z<p>Jomo: /* OpenRadar */ change OR-Download-Address</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see https://sourceforge.net/projects/openradar/files/latest/download?source=files. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''mumble.allfex.org'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="keytable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=Initial_Starting_Positions&diff=98948Initial Starting Positions2016-06-01T09:02:01Z<p>Jomo: Add chapter: "Starting within an active Multiplayer environment"</p>
<hr />
<div>You can define any point on Earth as the '''initial starting position''' for your FlightGear-Session, as well on airports as outside, ashore or in the mids of the oceans, even somewhere in the air above. You even do not need to have the Sceneries installed for that Starting-Position! ''(But if the scenery is not available you will see nothing but a big blue water around you – wherever you are! Of course you could load that scenery then by [[TerraSync]]'')<br />
<br />
If you are flying just by yourself (i.e. without having [[Howto: multiplayer|Multiplayer]] activated) you may just choose an airport and leave it up to FlightGear to place you somewhere onto a runway. That is the most easiest procedure at all – but absolutely unrealistic – '''and if done, while others are around, it is absolutely recklessness against those already there!''' Because if you start FlightGear with the [[Howto: Multiplayer|MP-Options]] directly on a runway you cannot watch for somebody being there already, or being on short final to it, or if there is an [[:Howto: Be a controller|ATC]] who may start to dislike you a lot, or … or ...! Best is you just use proper procedures and always start at a parking-position, gate, or terminal when you are not alone! That way you even have the advantage of getting accustomed to the controls and instruments again while taxiing to the runway.<br />
<br />
'''So please consider the following procedures to define your start-position in FlightGear:'''<br />
<br />
== Starting within an active Multiplayer environment ==<br />
When starting your session you should ensure that you do not disturb ongoing operations by others. Nobody likes it, if e.g.:<br />
* you pop-up within his plane at a gate or parking-position<br />
* or while he is on short final and you pop up on his runway<br />
* or when you block his taxiway<br />
* etc.<br />
This procedure will help you to avoid that all, because you are only visible to others '''after''''' being at an empty gate or parking-lot!<br />
<br />
In general that means: <br />
* start without the Multiplayer-option active (so nobody will notice you yet!) <br />
* taxi to a free Gate or parking-lot <br />
* only after that enable the multiplayer-option <br />
<br />
<br><br />
In detail that means:<br><br />
1. disable the "--multiplay" options during start-up<br />
:::They will be set to default when starting MP later.<br />
:::''(If you want to set unique MP-options you may predefine all MP-options -- '''EXCEPT''' the "multiplay=out"!)''<br />
<br />
2. Start at any airport you want by defining e.g. "--airport=EDDF" (nothing else is needed!).<br />
::: ''(Of course you may also predefine any position as described in the other procedures -- '''EXCEPT''' the "multiplay=out"!)''<br />
<br />
3. After you taxied to a free Gate or parking-lot of your choice <br />
::: --> click: ''''Menu --> Multiplayer --> Multiplayer Settings --> Connect''''<br />
:and you are visible to everybody - and nobody is shouting on you !!<br />
<br />
<br />
*''In case you have forgotten to disable MP and popped up where you are "not welcomed" - just do (very fast!) the reverse:<br />
::: --> click: Menu --> Multiplayer --> Multiplayer Settings --> '''Disconnect'''<br />
:and then continue with item 3 above!''<br />
<br />
== Starting-Position at a Terminal, Gate, Parking-lot, etc. ==<br />
This option is the only one that meets reality! And should always be used when flying amongst others.<br />
* '''With [[FlightGear Launch Control|FGrun]]''' you find the available Starting-Positions on the page where you define the Airport, on the right side underneath the Runways.<br />
* '''Without [[FlightGear Launch Control|FGrun]]''' you find these places inside the file “groundnet.xml” for each airport, where those are available. See e.g. ''''$FG_Root\Airports\K\O\A\KOAK.groundnet.xml''''.<br />
<br />
:There you will find e.g. the position:<br />
::<Parking index="2" <br />
:::type="gate" <br />
:::name="747b11" <br />
:::number="1" <br />
:::lat="N37 42.807" <br />
:::lon="W122 12.963" <br />
:::heading="130" <br />
:::radius="39" <br />
:::airlineCodes="" <br />
::/><br />
<br />
:Thus you could define this “Gate” by adding the options<br />
::''''--airport=KOAK --parkpos=747b11''''<br />
:to your start-command. <br />
<br />
:Of course you also could use the above shown “lat/lon/heading”-values to define that position in [[GPS]] (see next chapter) – but you would have to convert those from Decimal to Grad° (You could do that with e.g. http://www.fcc.gov/mb/audio/bickel/DDDMMSS-decimal.html).<br />
<br />
Sorry enough: Those Starting-Points are not defined for all airports - due to the limited availability of unpaid volunteers. But You can define your own “groundnet.xml” or add parking-lots to an existing one according to the above scheme – for HowTo get additional [[GPS]]-data see the next chapter! That way you could create your own personal “VIP-Parking” for your most favorite airports! Save the new "parking.xml"-file into the ''''[[$FG_ROOT]]/AI/Airports/ICAO-Code/'''' (or if you use FlightGear 2.4.0 or newer into'''[[$FG_ROOT]]/Scenery/Airports/[i]/[C]/[A]/ICAO.groundnet.xml''') directory. Please note, however, that parking positions are defined as part of a ground network file that was originally designed for FlightGear's AI system. Checkout the [[Interactive_Traffic]] page for more information on ground networks. <br />
<br />
And if you do that for yourself, why not add a few more statements and make them available to everybody! See e.g. the http://wiki.flightgear.org/index.php/Volunteer and airport-diagrams, which are available in the Internet.<br />
<br />
At http://media.lug-marl.de/flightgear/Airports.tgz you can download an optional Airports folder with parking positions for 7125 airports.<br />
<br />
== Starting-Position per GPS-Data ==<br />
You always have 3 possibilities to define your Starting-Positions by [[GPS]]:<br />
[[File:KRHV-startpoistion.png|250px|thumb|left|]]1. Open [[MPmap]] and zoom into the airport you wish. Move your Mouse-pointer to the place you want – e.g. to the place on KRHV where “jomo” is parked now. And then read the lat/lon-data in the upper right corner (see the big red arrow). In addition decide on the direction you want to view: In the example on the left that is parallel to runway 31R, i.e. 310°+14°=324°. (The 14° are the difference between the magnetic and the cartographic North-pole in that area – if you do not know it: Just try e.g. the 310° and vary the heading until you are satisfied – or try the next item!)<br />
<br />
2. You could also just land on that airport and taxi to a parking-lot you like and park there. After parking open inside your cockpit ''''Menü → File → Browse Internal Properties → position'''' and note down the „latitude-deg“ and „longitude-deg“ (up to 6 decimal places is enough!). The needed heading you can take directly from your Compass.<br />
<br />
3. Of course you could also get that data by any atlas or navigation system and convert the data if needed!<br />
<br />
* If you start '''with [[FlightGear Launch Control|FGrun]]''' input those data into ''''“Advanced” → “Initial Position”''''. Watch out: The sequence of the lon/lat input-fields in FGrun are just reverse to MPmap. <br />
<br />
* If you start '''with a command or a command-file''' just add the options, eg.:<br />
:''''--lat=37.334047 --lon=-121.816320 --heading=324''''<br />
<br />
''If after that you end up in KSFO instead of where you wanted, then you probably have mixed up the Longitude and Latitude – or mistyped - or you found a new way to define a non existing place on earth!''<br />
<br />
== Starting-Position in relation to navigational points ==<br />
This is a wonderful way to test unique parts of a flight: With that Option you can start at unique locations and start your exercise, e.g. a “final approach”, or flying towards a NDB under different wind-conditions, etc.<br />
<br />
As reference-point you can choose any navigational aid available in FlightGear, e.g. VOR, NDB, FIX, Carrier, airports – whatever! But watch out: For some VOR's and NDB's there may exist multiple stations with the same ID! e.g. there is a VOR “RIED” with the ID=”RID” southwest of EDDF (Germany). Another VOR “RID” exists in Richmond (Indiana, USA) - thus you never know where you end up. That does not happen very often – but you should be aware of that “mishap”! More secure in this cases is the above GPS-procedure!<br />
<br />
* '''With [[FlightGear Launch Control|FGrun]]''' you can (since version 2) input the needed data direct into ''''“Advanced” → “Initial Position”''''.<br />
* '''For a command file''' add options like:<br />
::--vor <small>or</small> --ndb <small>or</small> --fix <small>or</small> --carrier <small>or</small> --airport<br />
::--offset-distance <small>and</small> --offset-azimuth <small>(if wanted)</small><br />
::--on-ground <small>or</small> --altitude=feet<br />
:Try e.g. ''''--fix=FITKI --heading=276 --vc=100 --altitude=1500''''<br />
:that will place you directly over a FIX for the ILS approach for runway 27R at KOAK. The speed (vc=100) fits to a C172 and the altitude (1500) is the proper altitude on the glide-slope for that. So this is a good Start for training visual Approaches (and or ILS). Other FIX-points you may find by opening [[MPmap]] in the area you are interested in and search for “all fixes”. (ref. http://wiki.flightgear.org/index.php/Mpmap )<br />
<br />
== Starting-Position direct on a Runway ==<br />
This is the easiest way to start – and thus often used to get beginners into the air for the first time! But as I pointed out at the beginning you should use this option only when you are all by yourself, that means without [[Howto: Multiplayer|Multiplayer]] activated! And all of us will be very thankful if you promote not to use this option when other [[Howto: Multiplayer|Multiplayer]] are in the area!<br />
<br />
Anyhow there exist 2 possibilities for this:<br />
<br />
=== Starting-position by defining just the airport ===<br />
In this case FlightGear choses a runway itself according to wind-direction etc. - and thus assigns the very same place for everybody ''(that wants to be piled up one above the other!)''. This usually end's up with lots of bad words by <br />
* pilots just being on short final and suddenly see some obstacle appearing on their runway! Not every pilot is then cool enough to continue going through that other guy<br />
* pilots suddenly sitting in their plane within your plane!<br />
* an [[Howto: Be a controller|ATC]] whom you just destroyed all his efforts in trying hard to get some order into all that “flying objects”<br />
<br />
You have no ideas about what kind of nice words those guys are able to use for you in such cases – you better switch off your FGCOM and/or MPchat if kids are around!<br />
<br />
So we definitely do not suggest to use this option – but if you want to use it (when you are alone!):<br />
* '''in [[FlightGear Launch Control|FGrun]]:''' Just pick an Airport<br />
* '''for a command-file''' add e.g. the option:<br />
::''''--airport=KOAK''''<br />
<br />
=== Starting-position by defining an airport and a runway ===<br />
This is even worse than the above! To all that bad happenings from before you are now even prone to start in a different direction to the other traffic! And thus those others would not just use even worse words – they would even laugh about you, that “stupid that does not know that you must start against the wind!”<br />
<br />
This option may be useful only for real beginners, that cannot yet perform above possibilities. These poor guys can choose a small, usually unused runway as their Starting-Position. As I said: As long as they still are “bloody beginners”!<br />
<br />
In that case:<br />
* '''in [[FlightGear Launch Control|FGrun]]''' select in addition to the wanted Airport also the wanted runway<br />
* '''for a command-file''' add e.g. the option: <br />
::''''--airport=KOAK --runway=33''''<br />
You can find available and fitting Runways in [[MPmap]] by selecting the Airport wanted and zooming in.<br />
<br />
[[Category:Multiplayer]]<br />
<br />
[[de:Initial Starting Positions]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=TerraGear_GUI&diff=85715TerraGear GUI2015-06-23T05:36:44Z<p>Jomo: /* For GNU/Linux users */ Add HelpLines for common Errors</p>
<hr />
<div>{{Infobox Software<br />
| title = TerraGear GUI<br />
| image = TerraGear GUI download San Francisco.png<br />
| alt = The download page with the San Francisco bay area selected.<br />
| developedby = Gijs de Rooy (original by Alex Park)<br />
| initialrelease = March 24, 2009 (original)<br>March 27, 2010<br />
| latestrelease = 0.9.x (2012)<br />
| writtenin = C++ (Qt)<br />
| os = Windows, Linux, Mac OS X<br />
| website = https://sourceforge.net/p/flightgear/fgscenery/terrageargui/ci/master/tree/<br />
}}<br />
The '''GUI''' tool for '''[[TerraGear]]''' allows people to create [[scenery]] for [[FlightGear]] without using commandlines.<br />
<br />
== Obtaining the GUI ==<br />
You can either build the GUI [https://sourceforge.net/p/flightgear/fgscenery/terrageargui/ci/master/tree/ from source], or download a pre-compiled build:<br />
* [http://liveries.flightgear.org/terrageargui/ Windows builds]<br />
Please note that:<br />
* you need to download/compile a recent version of [[TerraGear]] as well;<br />
* for Windows users, you'll need to add three DLLs to you TerraGear GUI root directory:<br />
** msvcp71.dll (see [[TerraGear_Installation_for_Windows]] to know how to get it)<br />
** mscvr71.dll (see [[TerraGear_Installation_for_Windows]] to know how to get it)<br />
** gdal12.dll (this can be retrieved from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/terragear-cs-Win32-20101002.zip )<br />
<br />
==== For GNU/Linux users ====<br />
# Grab the sources and store it where you want:<br/><pre>git clone git://git.code.sf.net/p/flightgear/fgscenery/terrageargui</pre><br />
# Then go in the source:<br/><pre>cd terrageargui</pre><br />
# Create a build dir:<br/><pre>mkdir build && cd build</pre><br />
# Now build it:<br/><pre>qmake .. </pre> or<pre>qmake-qt4 ..</pre> then<pre>make</pre><br />
:::<sub>In case of ERRORS You may have to add the following via SYNAPTIC:</sub><br />
:::*<sub>for "/usr/lib/i386-linux-gnu/qt4/bin/uic: Command not found" add: libqt4-dev-bin</sub><br />
:::*<sub>for "QtGui/QApplication: No such file or directory" add: qt4-dev-tools</sub><br />
<br /><br />
# You can now start it with:<br/><pre>"./bin/TerraGUI" or "./build/TerraGUI"</pre><br />
<br />
You're done!<br />
<br />
== Using the GUI ==<br />
The GUI exist of several tabs. For normal scenery creation, all the tabs should be gone through in the order they are arranged.<br />
<br />
=== Start ===<br />
# Set the TerraGear directory, in which you'll find the subdirectories bin/ and share/. TerraGear must be downloaded/build seperatly from the GUI!<br />
# Set the project's directory. In this directory, all project related stuff will be stored throughout the process. You best choose an empty directory specific to your project.<br />
# Set your FlightGear's root ([[$FG_ROOT]]). This is used to retrieve the list of available terrain materials.<br />
<br />
=== Download ===<br />
Specify boundaries in the boxes on the left, or select an area on the map. Next select a source to download shapefiles for that area. Note that OpenStreetMap only includes line date (roads, rivers), so you'll need some polygon data for the actual terrain. Both [[World Custom Scenery Project|Custom Scenery]] and [[CORINE]] (only Europe) provide that. The GUI downloads and unpacks the package to your <tt>{project's directory}/data/</tt>.<br />
<br />
Alternatively you can download shapefiles from [http://mapserver.flightgear.org/download.psp the mapserver by hand]. Unpack the downloaded file(s) to your <tt>{project's directory}/data/</tt>.<br />
<br />
==== Elevation data ====<br />
Elevation files are optional, but of course required to generate scenery with elevation offsets (even flat countries like the Netherlands need elevation data, since no country is completely at sealevel. Simply select a data source and then click the button to download the HGT files that span your specified area. The original source is usgs.gov, but a cleaned variant of the same data is available from fgx.ch (see [http://downloads.fgx.ch/geodata/data/srtm/README.txt the readme] for more information). The data will be saved in in <tt>{project's directory}/data/SRTM-3</tt>. <br />
<br />
===== By hand =====<br />
[[File:HGT tiles example.png|thumb|An example of HGT file tiles.]]<br />
Downloading tiles by hand is somewhat tricky. If your scenery has a boundary of:<br />
{| class="wikitable"<br />
!<br />
! Min<br />
! max<br />
|-<br />
! Latitude<br />
| 33<br />
| 37<br />
|-<br />
! Longitude<br />
| -2<br />
| 2<br />
|}<br />
The GUI would display the range as <tt>N33W002-N37E002</tt>. This means you have to download all tiles in that range, which are all the tiles as shown in the image on the right. Unpack the downloaded elevation file(s) in <tt>{project's directory}/data/SRTM-3</tt>.<br />
<br />
If you don't know how to find the boundaries range you can use Google Earth with this KMZ file : [http://clemaez.fr/flightgear/grid_1_degree.kmz grid_1_degree.kmz]<br />
# Download KMZ file above<br />
# Open it with Google Earth and active it (if not yet active). A lot of red lines should appears<br />
# Zoom where you want know the boundaries range<br />
# Click on the bottom left boundary wanted and report the displayed value in TerraGear GUI. (i.e: if Google Earth value is "W9_N42", report Minimum Latitude value "42" and Minimum Longitude value "-9")<br />
# Click on the top right boundary wanted and report the displayed value in TerraGear GUI. (i.e: if Google Earth value is "E6_N45", report Maximum Latitude value "45" and Maximum Longitude value "6")<br />
<br />
=== Elevation ===<br />
This will convert the .hgt.zip files (that you have downloaded earlier) into a form that TerraGear can read. Simply select the directory in which you placed the elevation downloads (probably <tt>{project's directory}/data/SRTM-3</tt>). Make sure you do set the correct resolution! For the USA this can be 1 arcsec, while the rest of the world is provided in 3 arcsec resolution.<br />
<br />
=== Airports ===<br />
What is scenery without airports in a flight simulator? If your area does not contain any airports, you can skip this part and continue with [[#ogr-decode|ogr-decode]].<br />
<br />
You can do two things now:<br />
*'''Already-made airports:''' use FlightGear's <tt>apt.dat.gz</tt> file, which is usually in <tt>[[$FG ROOT]]/Airports/</tt>.<br />
*'''Home-made airports:''' if you created an airport in [[WorldEditor]], use the .dat file that you exported.<br />
<br />
Use the button to browse to the .dat file of your choice.<br />
<br />
* '''All airports in area''' generates all the airports within the boundaries as set on the start tab.<br />
* '''Single airport''' to generate the scenery for a specific airport. Enter the ICAO code into the field. <br />
* '''Single tile''' only processes airports that are located on the given tileid.<br />
* '''All airports in apt.dat''' the tool will run through the entire apt.dat file, which can take a long (!) time when using the default apt.dat from FlightGear.<br />
<br />
=== Materials ===<br />
Now we need to decode the shapefiles into TerraGear format, which we do with OGR Decode. After clicking the "Retrieve shapefiles" button, the list will be populated with the shapefiles from your project's data directory. The GUI will try to assign fitting materials. If a shapefile has no material, you'll need to assign it by hand. Each single shapefile must have a material.<br />
<br />
You can delete shapefiles from the list by double-clicking on them. A single click on a material will allow you to edit it; to create custom materials that are not (yet) in materials.xml (do note that FlightGear will apply the default material to those landclasses, untill you create the material in materials.xml!). <br />
<br />
Line width is only used on line-data (like roads, rivers and railroads). If you leave the line width fields empty, a default width of 10 meters is used.<br />
<br />
===== Example =====<br />
<br />
{| class="wikitable"<br />
|-<br />
! Shapefile !! Material !! Line width (in meters)<br />
|-<br />
| osm_canal || Canal || 12<br />
|-<br />
| osm_motorway || Road-Motorway || 12<br />
|-<br />
| osm_primary || Road-Primary || 10<br />
|-<br />
| osm_rail || Railroad || 5<br />
|-<br />
| osm_river || Canal || 8<br />
|-<br />
| osm_secondary || Road-Secondary || 8<br />
|-<br />
| osm_stream || Stream || 3<br />
|-<br />
| osm_tertiary || Road-Tertiary || 6<br />
|-<br />
| osm_trunk || Road-Trunk || 18<br />
|}<br />
<br />
=== Construct ===<br />
[[Image:TerraGearGUI.png|thumb|270px|The construction page.]]<br />
'''Note: with recent TerraGear builds, it is required to add the used material-names to the default_priorities.txt file.'''<br />
<br />
The tg-construct tool brings all your gathered data together, throws it in a washing machine and spits it out the otherside in a format ready for use with FlightGear. Click the "Update list" button to populate the field with all decoded shapefiles. In the list you select all types that you'd like to include in your scenery.<br />
<br />
After clicking the "Generate scenery" button, it may take a long time for TerraGear to finish. Depending on the size of the area you are creating the scenery for and the level of detail in your shapefiles. Simple and small sceneries will take a couple of minutes, where larger, more detailed areas can take over an hour! So trying new things on small areas first will save you a lot of time.<br />
<br />
=== Running the scenery ===<br />
The folders and files in your project's <tt>output/</tt> directory are ready to use as scenery. You can set the [[$FG_SCENERY|scenery path]] of FlightGear to this directory to check if the scenery is generated correctly. <br />
<br />
== GUI development ==<br />
The current source code can be retrieved [https://sourceforge.net/p/flightgear/fgscenery/terrageargui/ci/master/tree/ from SourceForge].<br />
<br />
Feel free to add feature requests and/or bug reports to this page. Anyone interested in helping is invited to contact Gijs at the forum.<br />
<br />
=== Requested features ===<br />
Also see [[TerraGear scenery build server]]<br />
<br />
[[File:TerraGear-GUI-Remote-Mode.png|thumb|Prototyping a remote mode for [[TerraGear]] as part of [[TerraGear GUI]]]]<br />
<br />
* Multi-threading, so the GUI doesn't freeze when running a process [http://forum.flightgear.org/viewtopic.php?f=5&t=25688&p=235873&hilit=#p235623]<br />
* Support a new "Setup" page where people can decide if TerraGear is installed locally or remotely {{Not done}} <br />
* Add a command handler abstraction so that commands can be easily run over SSH [http://doc.qt.digia.com/qtcreator-extending/utils-sshconnection.html] {{Not done}}<br />
* File retrieval would ideally be wrapped via SFTP {{Not done}}<br />
<br />
== External link ==<br />
* [http://forum.flightgear.org/viewtopic.php?f=5&t=7485 Forum topic]<br />
<br />
[[Category:Scenery enhancement]]<br />
[[Category:TerraGear]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=82783OpenRadarGuide2015-03-24T08:07:40Z<p>Jomo: /* Operating */ typos</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''mumble.allfex.org'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=82782OpenRadarGuide2015-03-24T08:05:33Z<p>Jomo: /* Startup */</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''mumble.allfex.org'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar_-_FGFS_ORCAM.png&diff=82781File:OpenRadar - FGFS ORCAM.png2015-03-24T06:11:54Z<p>Jomo: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=For the OpenRadar Manual/Guide}}<br />
|date=2015-03-24 07:07:26<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
[[Category:OpenRadar screenshots]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar_-_Tweaks.png&diff=82780File:OpenRadar - Tweaks.png2015-03-24T06:05:13Z<p>Jomo: Jomo uploaded a new version of File:OpenRadar - Tweaks.png</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=OpenRadar Start page 2}}<br />
|date=2014-01-20 10:10:25<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
{{Location dec|0|0}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-Flightplans-Linux.png&diff=82779File:OpenRadar-Flightplans-Linux.png2015-03-24T06:03:22Z<p>Jomo: Jomo uploaded a new version of File:OpenRadar-Flightplans-Linux.png</p>
<hr />
<div></div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-_Settings-linux.png&diff=82778File:OpenRadar- Settings-linux.png2015-03-24T05:55:54Z<p>Jomo: Jomo uploaded a new version of File:OpenRadar- Settings-linux.png</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=For the OpenRadar Manual}}<br />
|date=2012-12-22<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar_-_Welcome-Linux.png&diff=82777File:OpenRadar - Welcome-Linux.png2015-03-24T05:52:31Z<p>Jomo: Jomo uploaded a new version of File:OpenRadar - Welcome-Linux.png</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=For the OpenRadar Manual}}<br />
|date=2012-12-22<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar_-_Welcome-Linux.png&diff=82776File:OpenRadar - Welcome-Linux.png2015-03-24T05:51:55Z<p>Jomo: Jomo uploaded a new version of File:OpenRadar - Welcome-Linux.png</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=For the OpenRadar Manual}}<br />
|date=2012-12-22<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=Frankfurt_am_Main_Airport&diff=80814Frankfurt am Main Airport2015-02-10T09:42:22Z<p>Jomo: updates for FGFS 3.x</p>
<hr />
<div>{{infobox Airport<br />
|name = Frankfurt International Airport<br />
|image =EDDF1.jpg<br />
|alt = 364 feet<br />
|iata =FRA<br />
|icao =EDDF<br />
|type =Public + Cargo<br />
|city =Frankfurt am Main<br />
|owner =Fraport<br />
|website =http://www.frankfurt-airport.com/<br />
|runway= 07L/25R<br />
|length= 2800 m <br />
|material= Concrete<br />
|runway2= 07C/25C<br />
|length2= 4000 m <br />
|material2= Asphalt <br />
|runway3= 07R/25L<br />
|length3= 4000 m <br />
|material3= Asphalt<br />
|runway4= 18<br />
|length4= 4000 m <br />
|material4= Concrete <br />
}}<br />
<br />
The '''Frankfurt International Airport''', also known as '''Flughafen Frankfurt am Main''' or '''Rhein-Main-Flughafen''', is in Europe the third larges airport for passengers (after London and Paris) - and the largest for cargo. It is located 12 km (7.5mi) southwest of downtown Frankfurt am Main. This airport-model is complete with respect to the Terminals. However, as there are constant changes going on in reality <small>(e.g. a "Terminal 3" will be coming soon)</small> work is never really finished. In addition to the airport the scenery also contains a fair amount of skyscrapers of Frankfurt and some other details.<br />
<br />
The version available through TerraSync is reasonably up-to date, while the version in the GIT repo contains some future changes (new runway, buildings under construction). In addition to that there is a new custom scenery with many details for the area around the airport.<br />
In General:<br />
* starting with FGFS 3.0. (and Scenery 2.12) the new runways and new ILS-frequencies are included and/or uploaded by TerraSync<br />
* prior to that you may use the AddOn-Scenery-Package from http://www.emmerich-j.de/EDDF/EDDF-ELLX-new.zip (See the README inside the package)<br />
<br /><br />
== Runways ==<br />
EDDF has 4 runways. Three runways are positioned approximately parallel east-west, and the forth is north-south.<br />
<br />
=== Runway 07L-25R ===<br />
These runways are used only for landings of medium size aircraft - no starts are allowed.<br />
<br />[[Instrument Landing System]] is available for runway 07L, tune your NAV radio to 111.75 with a heading of 069.614.<br />
<br />[[Instrument Landing System]] is available for runway 25R, tune your NAV radio to 111.35 with a heading of 249.568.<br />
<br />
=== Runway 07C-25C ===<br />
[[Instrument Landing System]] is available for runway 07C, tune your NAV radio to 110.55 with a heading of 069.614.<br />
<br />[[Instrument Landing System]] is available for runway 25C, tune your NAV radio to 111.55 with a heading of 249.568 ''(prior to FGFS 3.0 the frequency was 109.50)''.<br />
<br />
=== Runway 07R-25L ===<br />
[[Instrument Landing System]] is available for runway 07R, tune your NAV radio to 110.95 with a heading of 069.619.<br />
<br />[[Instrument Landing System]] is available for runway 25L, tune your NAV radio to 111.15 with a heading of 249.571 ''(prior to FGFS 3.0 the frequency was 110.70)''.<br />
<br />
=== Runway 18 ===<br />
Runway 18 does not have an [[Instrument Landing System]] as it is used only for departures in real life. There is NO runway 36 as that direction leads towards the Taunus mountains that would be in the way at takeoff.<br />
<br />
== Custom Frankfurt scenery ==<br />
{|<br />
| Autor: || Christian Schmitt and others<br />
|-<br />
|-<br />
| Where to get: || Generally, changes go mostly directly into the scenery DB and are distributed via TerraSync. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery<br />
|}<br />
<br />
== See also ==<br />
{| type="wikitable"<br />
|-<br />
|* [[http://www.emmerich-j.de/GND-tot.png Layout]] || A Ground-Overview for pilots<br />
|-<br />
|* [[http://www.vacc-sag.org/airport/EDDF Airport Diagrams]] || For all official airport documents, including SID, STARS, IAC, etc.<br />
|-<br />
|* [[ATC at EDDF]] || for general rules during ATC-sessions on EDDF<br />
|-<br />
|* [[http://www.emmerich-j.de/EDDF/Films/Films.html]] || for filmed ATC-events at EDDF<br />
|-<br />
|* [[Airports]] || list of other airports based on development aspects<br />
|-<br />
|* [[Suggested_Airports]] || list of other airports based on development aspects<br />
|-<br />
|* [[Germany]] || for Pilots<br />
|}<br />
<br />
[[Category:Airports in Germany]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79793OpenRadarGuide2015-02-07T08:45:17Z<p>Jomo: /* OpenRadar-Welcome - Select Airport */ link correction</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
:* type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
::* if that ICAO code is available, then OpenRadar will list add it to the list<br />
::* a single mouseclick onto the listed airport will activate that selection<br />
:::* and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
:::* then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
::* a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
::* that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''mumble.allfex.org'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79790OpenRadarGuide2015-02-07T08:41:40Z<p>Jomo: correcting links</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
:* type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
::* if that ICAO code is available, then OpenRadar will list add it to the list<br />
::* a single mouseclick onto the listed airport will activate that selection<br />
:::* and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [#[Status_Informations]])</small><br />
:::* then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
::* a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
::* that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''mumble.allfex.org'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79786OpenRadarGuide2015-02-07T08:22:03Z<p>Jomo: minor correction</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
:* type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
::* if that ICAO code is available, then OpenRadar will list add it to the list<br />
::* a single mouseclick onto the listed airport will activate that selection<br />
:::* and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[Status_Informations]])</small><br />
:::* then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
::* a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
::* that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''mumble.allfex.org'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[Status Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79736OpenRadarGuide2015-02-05T15:58:46Z<p>Jomo: Proposed update for Feb 2015 release</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar: See the "Flightplans-tab" at [[#Startup]]. <br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[Status Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79726OpenRadarGuide2015-02-05T07:05:58Z<p>Jomo: /* Flight-Plan & Flight-Management */ part of general update</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
# The first line contains several informations:<br />
#* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
#* "5000/TL055" is the so called '''transient altitude''' for that airport/area, in which:<br />
#** 5000 gives the "Transient Altitude" in feet when climbing<br />
#** TL055 gives the "Transient Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
#*:<br />
#* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar: See the "Flightplans-tab" at [[#Startup]]. <br />
#:<br />
# The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
# The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
#* With a mouse-click on the upper line only that line will be sent to the target <br />
#* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[Status Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target<br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79687OpenRadarGuide2015-02-04T10:05:09Z<p>Jomo: /* Flight Strip Manager */ Part of general update</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
# The first line contains several informations:<br />
#* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
#* "5000/TL055" is the so called '''transient altitude''' for that airport/area, in which:<br />
#** 5000 gives the "Transient Altitude" in feet when climbing<br />
#** TL055 gives the "Transient Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
#*:<br />
#* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar: See the "Flightplans-tab" at [[#Startup]]. <br />
#:<br />
# The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
# The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
#* With a mouse-click on the upper line only that line will be sent to the target <br />
#* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[Status Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79683OpenRadarGuide2015-02-04T07:27:57Z<p>Jomo: /* Runway Settings */</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
# The first line contains several informations:<br />
#* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
#* "5000/TL055" is the so called '''transient altitude''' for that airport/area, in which:<br />
#** 5000 gives the "Transient Altitude" in feet when climbing<br />
#** TL055 gives the "Transient Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
#*:<br />
#* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar: See the "Flightplans-tab" at [[#Startup]]. <br />
#:<br />
# The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
# The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
#* With a mouse-click on the upper line only that line will be sent to the target <br />
#* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[Status Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79682OpenRadarGuide2015-02-04T05:19:46Z<p>Jomo: /* COM-Radios */ add links</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
# The first line contains several informations:<br />
#* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
#* "5000/TL055" is the so called '''transient altitude''' for that airport/area, in which:<br />
#** 5000 gives the "Transient Altitude" in feet when climbing<br />
#** TL055 gives the "Transient Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
#*:<br />
#* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar: See the "Flightplans-tab" at [[#Startup]]. <br />
#:<br />
# The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
# The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
#* With a mouse-click on the upper line only that line will be sent to the target <br />
#* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79657OpenRadarGuide2015-02-03T17:51:50Z<p>Jomo: /* Status Informations */ correction</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
# The first line contains several informations:<br />
#* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
#* "5000/TL055" is the so called '''transient altitude''' for that airport/area, in which:<br />
#** 5000 gives the "Transient Altitude" in feet when climbing<br />
#** TL055 gives the "Transient Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
#*:<br />
#* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar: See the "Flightplans-tab" at [[#Startup]]. <br />
#:<br />
# The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
# The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
#* With a mouse-click on the upper line only that line will be sent to the target <br />
#* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79655OpenRadarGuide2015-02-03T17:40:09Z<p>Jomo: /* Status Informations */ Part of general update</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
# The first line contains several informations:<br />
#* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
#* "5000/TL055" is the so called '''transient altitude''' for that airport/area, in which:<br />
#** 5000 gives the "Transient Altitude" in feet when climbing<br />
#** TL055 gives the "Transient Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
#*:<br />
#* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar: See the "Flightplans-tab" at [[Startup]]. <br />
#:<br />
# The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
# The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
#* With a mouse-click on the upper line only that line will be sent to the target <br />
#* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79644OpenRadarGuide2015-02-03T07:09:57Z<p>Jomo: /* Operating */ add msg-area scrolling</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79642OpenRadarGuide2015-02-02T08:13:52Z<p>Jomo: /* Radar Map */ part of update</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>/Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-Approach.png&diff=79640File:OpenRadar-Approach.png2015-02-02T06:25:15Z<p>Jomo: Jomo uploaded a new version of File:OpenRadar-Approach.png</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=An OpenRadar Approach}}<br />
|date=2012-12-25<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79512OpenRadarGuide2015-01-31T10:36:30Z<p>Jomo: /* Operating */ Part of Update for new release</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:<br />
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.''''' <br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center that "Target-Airport-Axis" into the center<br />
<br />
You may assign any current settings to any of the 4 zoom levels <small>(GROUND, TOWER, APP and SECTOR)</small> by a right mouse-click onto the wanted level''<br />
<br /><br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations <small>(depending on Squake-Codes they may look different)</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan (see chapter [[#Flight-management]])||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 5 different colors: <br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable"<br />
|-<br />
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline <small>(e.g. see "D-Leon" who just is getting his "clear to land")</small><br />
|-<br />
|align="middle"|blue||targets who's Flight-Stripe is placed to the left, indicating it is under your ATC-control <small>(e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)</small><br />
|-<br />
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle <small>(e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)</small><br />
|-<br />
|align="center"|green||targets who's Flight-Stripe is placed to the right <small>(not actively controlled by you right now, see e.g. "jomo2": just parking)</small><br />
|-<br />
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>/Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-Radar-Options.png&diff=79510File:OpenRadar-Radar-Options.png2015-01-31T09:52:27Z<p>Jomo: Shows radar-option below the radar screen</p>
<hr />
<div>== Summary ==<br />
Shows radar-option below the radar screen<br />
== Licensing ==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79476OpenRadarGuide2015-01-30T10:27:06Z<p>Jomo: /* OpenRadar */ replace "prototype"</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into three regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.<br />
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature. <br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''COM-Radios''' <small>''(only if you have defined one or more)''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<span style="background: lightblue;">Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!</span><br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:<br />
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.''''' <br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
<span style="background:lightblue;"><br />
* <span style="background:lightblue;">a double mouse-click onto the scope will move that point into the center of the scope<br />
* <span style="background:lightblue;">a double right mouse-click will center the scope back to your location<br />
</span><br />
You may assign any current settings to any of the 4 zoom levels <small>(GROUND, TOWER, APP and SECTOR)</small> by a right mouse-click onto the wanted level''<br />
<br /><br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The '''''Radar-targets''''' <br />
*do have a label attached with the following informations<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 5 different colors: <br />
::<small>''(See also the chapter "Flight Strip Manager")''</small><br />
:{| class="wikitable"<br />
|-<br />
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline <small>(e.g. see "D-Leon" who just is getting his "clear to land")</small><br />
|-<br />
|align="middle"|blue||targets who's Flight-Stripe is placed to the left <small>(e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)</small><br />
|-<br />
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle <small>(e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)</small><br />
|-<br />
|align="center"|green||targets who's Flight-Stripe is placed to the right <small>(e.g. see "jomo2" just parking - not actively controlled right now)</small><br />
|-<br />
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:<br />
{| class="wikitable"<br />
|-<br />
| '''''FIX''''' || Show/NoShow FIX's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''NDB''''' || Show/NoShow NDB's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''VOR''''' || Show/NoShow VOR's<br />
|-<br />
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. <small>The PPNs will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|- style="background:lightblue"<br />
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)</small><br />
|}<br />
<br />
The "Runway Manager" <small>(on the right side of the screen)</small> allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:<br />
*25L, 25R, and 18 are active (see the green and red dots at the ends)<br />
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.<br />
<br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79475OpenRadarGuide2015-01-30T10:24:42Z<p>Jomo: /* Preface */ replace "prototype"-indicator</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into three regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.<br />
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature. <br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''COM-Radios''' <small>''(only if you have defined one or more)''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<span style="background: lightblue;">Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!</span><br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:<br />
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.''''' <br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
<span style="background:lightblue;"><br />
* <span style="background:lightblue;">a double mouse-click onto the scope will move that point into the center of the scope<br />
* <span style="background:lightblue;">a double right mouse-click will center the scope back to your location<br />
</span><br />
You may assign any current settings to any of the 4 zoom levels <small>(GROUND, TOWER, APP and SECTOR)</small> by a right mouse-click onto the wanted level''<br />
<br /><br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The '''''Radar-targets''''' <br />
*do have a label attached with the following informations<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 5 different colors: <br />
::<small>''(See also the chapter "Flight Strip Manager")''</small><br />
:{| class="wikitable"<br />
|-<br />
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline <small>(e.g. see "D-Leon" who just is getting his "clear to land")</small><br />
|-<br />
|align="middle"|blue||targets who's Flight-Stripe is placed to the left <small>(e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)</small><br />
|-<br />
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle <small>(e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)</small><br />
|-<br />
|align="center"|green||targets who's Flight-Stripe is placed to the right <small>(e.g. see "jomo2" just parking - not actively controlled right now)</small><br />
|-<br />
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:<br />
{| class="wikitable"<br />
|-<br />
| '''''FIX''''' || Show/NoShow FIX's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''NDB''''' || Show/NoShow NDB's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''VOR''''' || Show/NoShow VOR's<br />
|-<br />
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. <small>The PPNs will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|- style="background:lightblue"<br />
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)</small><br />
|}<br />
<br />
The "Runway Manager" <small>(on the right side of the screen)</small> allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:<br />
*25L, 25R, and 18 are active (see the green and red dots at the ends)<br />
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.<br />
<br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79474OpenRadarGuide2015-01-30T09:13:00Z<p>Jomo: /* Startup */ Updates for newest version</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.<br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
=== OpenRadar-Welcome - Select Airport ===<br />
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:<br />
*'''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''<br />
*If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
*If the wanted airport is not yet listed:<br />
**type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
**if that ICAO code is available, then OpenRadar will list that one<br />
***a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")<br />
***that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
*To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
=== Settings (Communication) ===<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
=== Flightplans ===<br />
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
=== Tweaks ===<br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into three regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.<br />
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature. <br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''COM-Radios''' <small>''(only if you have defined one or more)''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<span style="background: lightblue;">Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!</span><br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:<br />
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.''''' <br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
<span style="background:lightblue;"><br />
* <span style="background:lightblue;">a double mouse-click onto the scope will move that point into the center of the scope<br />
* <span style="background:lightblue;">a double right mouse-click will center the scope back to your location<br />
</span><br />
You may assign any current settings to any of the 4 zoom levels <small>(GROUND, TOWER, APP and SECTOR)</small> by a right mouse-click onto the wanted level''<br />
<br /><br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The '''''Radar-targets''''' <br />
*do have a label attached with the following informations<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 5 different colors: <br />
::<small>''(See also the chapter "Flight Strip Manager")''</small><br />
:{| class="wikitable"<br />
|-<br />
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline <small>(e.g. see "D-Leon" who just is getting his "clear to land")</small><br />
|-<br />
|align="middle"|blue||targets who's Flight-Stripe is placed to the left <small>(e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)</small><br />
|-<br />
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle <small>(e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)</small><br />
|-<br />
|align="center"|green||targets who's Flight-Stripe is placed to the right <small>(e.g. see "jomo2" just parking - not actively controlled right now)</small><br />
|-<br />
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:<br />
{| class="wikitable"<br />
|-<br />
| '''''FIX''''' || Show/NoShow FIX's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''NDB''''' || Show/NoShow NDB's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''VOR''''' || Show/NoShow VOR's<br />
|-<br />
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. <small>The PPNs will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|- style="background:lightblue"<br />
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)</small><br />
|}<br />
<br />
The "Runway Manager" <small>(on the right side of the screen)</small> allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:<br />
*25L, 25R, and 18 are active (see the green and red dots at the ends)<br />
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.<br />
<br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-Status_2.png&diff=79472File:OpenRadar-Status 2.png2015-01-30T05:21:54Z<p>Jomo: Jomo uploaded a new version of &quot;File:OpenRadar-Status 2.png&quot;</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=The Status Informations of OpenRadar}}<br />
|date=2012-12-28<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-Runways_2.png&diff=79471File:OpenRadar-Runways 2.png2015-01-30T05:19:27Z<p>Jomo: Jomo uploaded a new version of &quot;File:OpenRadar-Runways 2.png&quot;</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=The Runway-Settings of OpenRadar}}<br />
|date=2012-12-28<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-Flightplanning.png&diff=79470File:OpenRadar-Flightplanning.png2015-01-30T05:14:48Z<p>Jomo: Jomo uploaded a new version of &quot;File:OpenRadar-Flightplanning.png&quot;</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=The Flightplanning feature input sheet for OpenRadar}}<br />
|date=2014-02-24 09:58:11<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}<br />
<br />
[[Category:OpenRadar screenshots]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79434OpenRadarGuide2015-01-29T18:00:02Z<p>Jomo: /* Startup */ Add new tab: Flightplans</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.<br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 3 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome ''(Linux)'']] <br />
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings tab ''(Linux)'']]<br />
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans tab ''(Linux)'']]<br />
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks tab ''(Linux)'']] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
If this is the very first time you start OpenRadar, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:<br />
<br />
=== OpenRadar-Welcome - Settings ===<br />
These settings are grouped into 3 parts:<br />
===='''1) FGCom (Radio/Voice Communication)'''====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users can uses this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sdelta384.server4you.de -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
===='''2) Multiplayer Chat'''====<br />
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
===='''3) Flightplan exchange'''====<br />
You must define the Server for the FlightPlan data. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
===='''4) METAR'''====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br />
Please click on the verify button to have your settings checked prior to returning to the left/primary tab:<br />
<br />
===Select Airport===<br />
This is always the first window that you will see after starting OpenRadar.<br />
<br />
But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:<br />
<br />
In order to '''define a new work-location''' simply enter the airport code (ICAO) or a part of the name into the search field and hit “search”: The list below then shows the results found in the airport database delivered with OpenRadar. There may be found several, so click on the one wanted and then activate the button "Download Scenery". Be patient and watch the Info-Field at the bottom: This first download of the required scenery will take some time before you see a "Ready"! <br />
<br />
'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.<br />
Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into three regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.<br />
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature. <br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''COM-Radios''' <small>''(only if you have defined one or more)''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<span style="background: lightblue;">Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!</span><br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:<br />
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.''''' <br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
<span style="background:lightblue;"><br />
* <span style="background:lightblue;">a double mouse-click onto the scope will move that point into the center of the scope<br />
* <span style="background:lightblue;">a double right mouse-click will center the scope back to your location<br />
</span><br />
You may assign any current settings to any of the 4 zoom levels <small>(GROUND, TOWER, APP and SECTOR)</small> by a right mouse-click onto the wanted level''<br />
<br /><br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The '''''Radar-targets''''' <br />
*do have a label attached with the following informations<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 5 different colors: <br />
::<small>''(See also the chapter "Flight Strip Manager")''</small><br />
:{| class="wikitable"<br />
|-<br />
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline <small>(e.g. see "D-Leon" who just is getting his "clear to land")</small><br />
|-<br />
|align="middle"|blue||targets who's Flight-Stripe is placed to the left <small>(e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)</small><br />
|-<br />
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle <small>(e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)</small><br />
|-<br />
|align="center"|green||targets who's Flight-Stripe is placed to the right <small>(e.g. see "jomo2" just parking - not actively controlled right now)</small><br />
|-<br />
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:<br />
{| class="wikitable"<br />
|-<br />
| '''''FIX''''' || Show/NoShow FIX's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''NDB''''' || Show/NoShow NDB's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''VOR''''' || Show/NoShow VOR's<br />
|-<br />
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. <small>The PPNs will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|- style="background:lightblue"<br />
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)</small><br />
|}<br />
<br />
The "Runway Manager" <small>(on the right side of the screen)</small> allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:<br />
*25L, 25R, and 18 are active (see the green and red dots at the ends)<br />
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.<br />
<br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-Flightplans-Linux.png&diff=79409File:OpenRadar-Flightplans-Linux.png2015-01-29T09:39:39Z<p>Jomo: </p>
<hr />
<div></div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar_-_Tweaks.png&diff=79408File:OpenRadar - Tweaks.png2015-01-29T09:34:10Z<p>Jomo: Jomo uploaded a new version of &quot;File:OpenRadar - Tweaks.png&quot;</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=OpenRadar Start page 2}}<br />
|date=2014-01-20 10:10:25<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
{{Location dec|0|0}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar-_Settings-linux.png&diff=79407File:OpenRadar- Settings-linux.png2015-01-29T09:30:41Z<p>Jomo: Jomo uploaded a new version of &quot;File:OpenRadar- Settings-linux.png&quot;</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=For the OpenRadar Manual}}<br />
|date=2012-12-22<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79406OpenRadarGuide2015-01-29T09:18:14Z<p>Jomo: /* Prerequisites */ just typing/rewording</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.<br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 3 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome ''(Linux)'']] || [[File:OpenRadar- Settings-linux.png|thumb|Settings tab ''(Linux)'']] || [[File:OpenRadar - Tweaks.png|thumb|Tweaks tab ''(Linux)'']] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
If this is the very first time you start OpenRadar, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:<br />
<br />
=== OpenRadar-Welcome - Settings ===<br />
These settings are grouped into 3 parts:<br />
===='''1) FGCom (Radio/Voice Communication)'''====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users can uses this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sdelta384.server4you.de -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
===='''2) Multiplayer Chat'''====<br />
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
===='''3) Flightplan exchange'''====<br />
You must define the Server for the FlightPlan data. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
===='''4) METAR'''====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br />
Please click on the verify button to have your settings checked prior to returning to the left/primary tab:<br />
<br />
===Select Airport===<br />
This is always the first window that you will see after starting OpenRadar.<br />
<br />
But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:<br />
<br />
In order to '''define a new work-location''' simply enter the airport code (ICAO) or a part of the name into the search field and hit “search”: The list below then shows the results found in the airport database delivered with OpenRadar. There may be found several, so click on the one wanted and then activate the button "Download Scenery". Be patient and watch the Info-Field at the bottom: This first download of the required scenery will take some time before you see a "Ready"! <br />
<br />
'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.<br />
Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.<br />
<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into three regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.<br />
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature. <br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''COM-Radios''' <small>''(only if you have defined one or more)''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<span style="background: lightblue;">Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!</span><br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:<br />
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.''''' <br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
<span style="background:lightblue;"><br />
* <span style="background:lightblue;">a double mouse-click onto the scope will move that point into the center of the scope<br />
* <span style="background:lightblue;">a double right mouse-click will center the scope back to your location<br />
</span><br />
You may assign any current settings to any of the 4 zoom levels <small>(GROUND, TOWER, APP and SECTOR)</small> by a right mouse-click onto the wanted level''<br />
<br /><br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The '''''Radar-targets''''' <br />
*do have a label attached with the following informations<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 5 different colors: <br />
::<small>''(See also the chapter "Flight Strip Manager")''</small><br />
:{| class="wikitable"<br />
|-<br />
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline <small>(e.g. see "D-Leon" who just is getting his "clear to land")</small><br />
|-<br />
|align="middle"|blue||targets who's Flight-Stripe is placed to the left <small>(e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)</small><br />
|-<br />
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle <small>(e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)</small><br />
|-<br />
|align="center"|green||targets who's Flight-Stripe is placed to the right <small>(e.g. see "jomo2" just parking - not actively controlled right now)</small><br />
|-<br />
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:<br />
{| class="wikitable"<br />
|-<br />
| '''''FIX''''' || Show/NoShow FIX's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''NDB''''' || Show/NoShow NDB's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''VOR''''' || Show/NoShow VOR's<br />
|-<br />
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. <small>The PPNs will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|- style="background:lightblue"<br />
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)</small><br />
|}<br />
<br />
The "Runway Manager" <small>(on the right side of the screen)</small> allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:<br />
*25L, 25R, and 18 are active (see the green and red dots at the ends)<br />
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.<br />
<br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=79403OpenRadarGuide2015-01-29T08:56:43Z<p>Jomo: /* Preface */ just typing/rewording</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.<br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
There may not be enough time for typing!<br />
<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directely from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "mumble.allfex.org"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 3 TABs to define your preferences:<br />
{|<br />
|-<br />
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome ''(Linux)'']] || [[File:OpenRadar- Settings-linux.png|thumb|Settings tab ''(Linux)'']] || [[File:OpenRadar - Tweaks.png|thumb|Tweaks tab ''(Linux)'']] <br />
|}<br />
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.<br />
<br /><br />
If this is the very first time you start OpenRadar, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:<br />
<br />
=== OpenRadar-Welcome - Settings ===<br />
These settings are grouped into 3 parts:<br />
===='''1) FGCom (Radio/Voice Communication)'''====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users can uses this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sdelta384.server4you.de -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
===='''2) Multiplayer Chat'''====<br />
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
===='''3) Flightplan exchange'''====<br />
You must define the Server for the FlightPlan data. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
===='''4) METAR'''====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br />
Please click on the verify button to have your settings checked prior to returning to the left/primary tab:<br />
<br />
===Select Airport===<br />
This is always the first window that you will see after starting OpenRadar.<br />
<br />
But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:<br />
<br />
In order to '''define a new work-location''' simply enter the airport code (ICAO) or a part of the name into the search field and hit “search”: The list below then shows the results found in the airport database delivered with OpenRadar. There may be found several, so click on the one wanted and then activate the button "Download Scenery". Be patient and watch the Info-Field at the bottom: This first download of the required scenery will take some time before you see a "Ready"! <br />
<br />
'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.<br />
Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.<br />
<br />
<br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into three regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.<br />
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature. <br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''COM-Radios''' <small>''(only if you have defined one or more)''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
<span style="background: lightblue;">Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!</span><br />
<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:<br />
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.''''' <br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
<span style="background:lightblue;"><br />
* <span style="background:lightblue;">a double mouse-click onto the scope will move that point into the center of the scope<br />
* <span style="background:lightblue;">a double right mouse-click will center the scope back to your location<br />
</span><br />
You may assign any current settings to any of the 4 zoom levels <small>(GROUND, TOWER, APP and SECTOR)</small> by a right mouse-click onto the wanted level''<br />
<br /><br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The '''''Radar-targets''''' <br />
*do have a label attached with the following informations<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 5 different colors: <br />
::<small>''(See also the chapter "Flight Strip Manager")''</small><br />
:{| class="wikitable"<br />
|-<br />
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline <small>(e.g. see "D-Leon" who just is getting his "clear to land")</small><br />
|-<br />
|align="middle"|blue||targets who's Flight-Stripe is placed to the left <small>(e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)</small><br />
|-<br />
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle <small>(e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)</small><br />
|-<br />
|align="center"|green||targets who's Flight-Stripe is placed to the right <small>(e.g. see "jomo2" just parking - not actively controlled right now)</small><br />
|-<br />
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:<br />
{| class="wikitable"<br />
|-<br />
| '''''FIX''''' || Show/NoShow FIX's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''NDB''''' || Show/NoShow NDB's <small>(they will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''VOR''''' || Show/NoShow VOR's<br />
|-<br />
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. <small>The PPNs will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|- style="background:lightblue"<br />
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)</small><br />
|}<br />
<br />
The "Runway Manager" <small>(on the right side of the screen)</small> allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:<br />
*25L, 25R, and 18 are active (see the green and red dots at the ends)<br />
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.<br />
<br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]<br />
<br />
This area shows in 4 lines the most used status-informations:<br />
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" <small>(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))</small><br />
</li><li>In the second line you see the ICAO <small>(the international Code for airports)</small> and the long name of your airport. In addition you see on the right the currently selected radar contact <small>(e.g. "jomo")</small>.<br />
</li><li>The third line lets you predict several values for that "radar contact" <small>(e.g. "jomo")</small>. Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:<br />
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM) <br />
*Miles: The distance between the target and the mouspointer.<br />
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small><br />
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...<br />
</li></ol><br />
<br />
====='''COM-Radios'''=====<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
According to the amount of FGcom-Ports you defined during setup <small>(compare chapter "3.1.1 FGcom")</small> you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
:{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the "FGComMode" in chapter "Startup")</small>, then<br />
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>:<br />
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden<br />
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears<br />
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.<br />
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!<br />
<br />
*From left to right you see the following informations for each runway (if available):<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:<br />
<br />
"ILS VOR FGC NRW || GED MTR"<br />
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> <br />
<br />
"ILS VOR FGC NRW || KJFK 280° f510"<br />
<br /><small>This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"</small><br />
<br />
You are absolutely free to define your own codes and whatever. To do so<br />
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''<small>(Mac: Alt + right mouse-click)</small>'' while pressing onto the stripe<br />
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)<br />
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!<br />
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.<br />
<br />
You can '''''manipulate the listing''''' of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!<br />
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)<br />
Again: That is a proposal - you can define your on assignments!<br />
<br />
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:<br />
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.<br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. <br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
You can also open the "active" target by the '''^'''-key<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will<br />
**either remove his “ownership” by <br />
***clicking onto “Handover to” and selecting <br />
****another ATC for takeover <br />
****or the “blank” for just removing his control. <br />
***or clicking onto the button “UnControl” <br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”<br />
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) <br />
*'''Squawk''' shows the Squake-Code you assigned to the target<br />
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''Route''' defines the SID, STAR, etc. assigned<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Route''' can be used to document a preplanned route<br />
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take controll<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background. <br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)'' <br />
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
*If the target lands on your airport:<br />
**assign a STAR and/or RW <br />
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C is canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Useful Features''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="wikitable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|}<br />
<br />
== Related content ==<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
<br />
[[Category:OpenRadar|Guide]]</div>Jomohttps://wiki.flightgear.org/w/index.php?title=File:OpenRadar_-_Welcome-Linux.png&diff=79402File:OpenRadar - Welcome-Linux.png2015-01-29T08:28:16Z<p>Jomo: Jomo uploaded a new version of &quot;File:OpenRadar - Welcome-Linux.png&quot;</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=For the OpenRadar Manual}}<br />
|date=2012-12-22<br />
|source={{own}}<br />
|author=[[User:Jomo|Jomo]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}</div>Jomohttps://wiki.flightgear.org/w/index.php?title=User_talk:Jomo&diff=71078User talk:Jomo2014-05-13T08:47:54Z<p>Jomo: </p>
<hr />
<div>== Quick Check for FGFS 3.0 Scenery 2.12 problems ==<br />
<br />
'''''This is a proposal -- not yet final:'''''<br />
<br />
It seems with FGFS 3.0 and scenery 2.12 many users are running into problems and try now to debug/tune there system. In the meantime there are many very good and detailed wikis available (which then reference to even more detailed wiki). e.g.:<br />
* http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes<br />
* http://wiki.flightgear.org/System_Crashes<br />
* http://wiki.flightgear.org/Howto:Improve_framerates<br />
* http://wiki.flightgear.org/Unexpected_Crashes_with_Scenery_ver.2<br />
<br />
But I am afraid not everybody will really read them all - so let me give you some hints - and if you want more details see the wikis!<br />
<br />
You should start with a rather "complex plane" on a rather "complex airport" <small>''(e.g. EDDF, KSFO, etc.)''</small> when there is much traffic active -- of course you should stay OffSide on an unused parking-lot and inform ATC about what you are doing and watch MPchat! Then:<br />
* Before starting to tune set the frame-rate to the default 60 and activate <small>(see: View -> Rendering Option -> Throttle frame rate)</small> - then the actual frame-rate will be shown in the lower right corner of your screen. The goal should be to have '''''at least 20'''''! ''(With "my" Concorde at EDDF I am also satisfied with 10 - but for e.g. a dogfight you certainly need more!)''<br />
* Try several rendering options and see how much influence they have:<br />
: View → Rendering Options<br />
:* Use the "Reload Scenery” button at the bottom to make sure all of the current scenery is loaded and shown<br />
:**set Animated Jetways →off<br />
:**set Custom Settings → off<br />
:**3D Clouds → usually may remain on (but you should try)<br />
:**Atmospheric light scattering → did not have a big influence for me<br />
* View --> Adjust LOD Ranges <br />
:LODs <small>''(Level Of Detail)''</small> have of course a very big influence - especially while moving! Because the scenery-tiles for scenery 2.12. became much bigger - they need of course lots of more PC and Video-Card and Memory power to display them! If your frame-rate is marginal, try to adjust a little during a full approach from at least 20 mi out, all the way down to the terminal and watch also other planes when they become visible!<br />
: There are 4 levels of details defined -- and you define at what distance the different levels shall be used - and thus you define how much more or less data your system must work with! The default settings are:<br />
:*Detailed = 1500 m<br />
:*Rough = 9000 m<br />
:*Bare = 30000<br />
:*AI = 10000 (i.e. do not try to spot an aircraft further out than 10 km)<br />
* '''Make sure that you do not mix any part of the previous scenery tiles with any of the new ones.''' I suggest:<br />
** rename your now existing "scenery" and "terrasync" directories to e.g. "sceneryOLD" and "terrasyncOLD"<br />
** create new "scenery" and "terrasync" directories ''(that way you do not have have to change your directory-definitions and still have a "fall back option")''<br />
** then fill up those new ones by<br />
*** just using TerraSync<br />
*** and or download scenery from http://www.flightgear.org/legacy-Downloads/scenery-v2.12.html<br />
* At the end I suggest:<br />
:#set the frame-rate a little lower then the average shown - that will prevent from erratic changes that may irritate you and may even crash your system!<br />
:# If you have disabled or changed some values, decide if you want to keep the changed values or change them back<br />
<br />
If that all did not help: Remember the wikis named at the top for much more tips and details.</div>Jomohttps://wiki.flightgear.org/w/index.php?title=User_talk:Jomo&diff=71077User talk:Jomo2014-05-13T08:25:39Z<p>Jomo: /* Quick Check for FGFS 3.0 Scenery 2.12 problems */ new section</p>
<hr />
<div>== Quick Check for FGFS 3.0 Scenery 2.12 problems ==<br />
<br />
'''''This is a proposal -- not yet final:'''''<br />
<br />
It seems with FGFS 3.0 and scenery 2.12 many users are running into problems and try now to debug/tune there system. In the meantime there are many very good and detailed wikis available (which then reference to even more detailed wiki). e.g.:<br />
* http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes<br />
* http://wiki.flightgear.org/System_Crashes<br />
* http://wiki.flightgear.org/Howto:Improve_framerates<br />
* http://wiki.flightgear.org/Unexpected_Crashes_with_Scenery_ver.2<br />
<br />
But I am afraid not everybody will really read them all - so let me give you some hints - and if you want more details see the wikis!<br />
<br />
You should start with a rather "complex plane" on a rather "complex airport" <small>''(e.g. EDDF, KSFO, etc.)''</small> when there is much traffic active -- of course you should stay OffSide on an unused parking-lot and inform ATC about what you are doing and watch MPchat! Then:<br />
* Before starting to tune set the frame-rate to the default 60 and activate <small>(see: View -> Rendering Option -> Throttle frame rate)</small> - then the actual frame-rate will be shown in the lower right corner of your screen. The goal should be to have '''''at least 20'''''! ''(With "my" Concorde at EDDF I am also satisfied with 10 - but for e.g. a dogfight you certainly need more!)''<br />
* Try several rendering options and see how much influence they have:<br />
: View → Rendering Options<br />
:* Use the "Reload Scenery” button at the bottom to make sure all of the current scenery is loaded and shown<br />
:**set Animated Jetways →off<br />
:**set Custom Settings → off<br />
:**3D Clouds → usually may remain on (but you should try)<br />
:**Atmospheric light scattering → did not have a big influence for me<br />
* View --> Adjust LOD Ranges <br />
:LODs '''(Level Of Detail)''' have of course a very big influence - especially while moving! Because the scenery-tiles for scenery 2.12. became much bigger - they need of course lots of more PC and Video-Card and Memory power to display them! If your frame-rate is marginal, try to adjust a little during a full approach from at least 20 mi out, all the way down to the terminal and watch also other planes when they become visible!<br />
: There are 4 levels of details defined -- and you define at what distance the different levels shall be used - and thus you define how much more or less data your system must work with! The default settings are:<br />
:*Detailed = 1500 m<br />
:*Rough = 9000 m<br />
:*Bare = 30000<br />
:*AI = 10000 (i.e. do not try to spot an aircraft further out than 10 km)<br />
* At the end I suggest:<br />
:#set the frame-rate a little lower then the average shown - that will prevent from erratic changes that may irritate you and may even crash your system!<br />
:# If you have disabled or changed some values, decide if you want to keep the changed values or change them back<br />
<br />
If that all did not help: Remember the wikis named at the top for much more tips and details.</div>Jomo