OpenRadarGuide: Difference between revisions

:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.

:::To activate it see http://mumble.sourceforge.net/Mumbleguide

=== Java V7 ===

=== OpenRadar ===

<br /><br />

If you did already work with an OpenRadar installation you may want to

* for Linux: OpenRadar.sh

* for OSX: OpenRadar.jar

=== OpenRadar-Welcome - Select Airport ===

=== Settings (Communication) ===

This window lets you define your communication settings:

: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!

=== Flightplans ===

<br>http://h2281805.stratoserver.net/FgFpServer/

<br>Under this address you can also check where ATC's are offering services right now.

Please click on the "Check Settings" button to have your settings checked prior to continue:

=== Tweaks ===

Select/enable according to the descriptions.

<br />Be aware that these option may influence the responstimes of your PC drastically!

== '''''Operating''''' ==

[[File:OpenRadar Prototype.png|right|270px]]

##'''Runway Manager''' to set up runways used  

##the '''Flight Strip Manager''', where you can manage your radar targets.

==== Radar Map ====

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:

**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

**Then you may type or copy/past anything behind that - and send it out by ENTER

*Generate a standard message:

**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

This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:

====='''COM-Radios'''=====

[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]

!COMx

!left on keyboard

|COM3|| ||NumOff+Num7

|}

====='''Runway Settings'''=====

**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.

**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  

:*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"!

:*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!)''.

:*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>.

:*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!

:*To the right follows

::*in the upper line the exact runway heading (as needed for older type autopilots)

|distance to it||IAS+GND speed||Altitude (FL)||current heading

|}

* You can move the stripes in vertical order by drag and drop

* 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)''

* 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!

* The radar-targets will change their color according to the horizontal position of their stripe:

** the radar-targets for stripes in the center will be '''yellow'''

** the radar-targets for stripes at the left side will be '''cyan'''

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:

:'''''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.)

**its listed messages in the MPchat-list become colored cyan

**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer

=='''''Flight-Plan & Flight-Management'''''==

==='''Define/Edit a Flight-Plan:'''===

*onto the Flight-Strip of the target

*or the target on the radar-screen

'''Controlling the ownership:'''<br>

* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change

**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan  will be set to “Uncontrolled” automatically

**or you send the controlling ATC a mail asking him to release the target

'''Mandatory fields of the OR-Flight-Plan:'''

*'''Contact''' is the FGFS-UID of the target  (will be set automatically)

*'''Aircraft''' is the model-code of the target  (will be set automatically)

*'''Departure''' is the departure Airport  (will be set automatically to your airport if on GND - or manual)

*'''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)

'''Optional fields of the OR-Flight-Plan:'''

*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))

*'''Code''' will be used in future when given by a more professional Flight-Planning system

*'''IFR/VFR''' may be defined by the PullDown

*'''Crsg.TAS.:'''  Define the planned TAS en route (usually as GND-speed)

*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route

==='''Flight-management:'''===

'''''1. A target appears on your airport'''''

:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]

:*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

'''''2. You define a new Flight Plan'''''

*'''Transfer Control to next ATC (or blank) '''

::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]

*the FlightStrip will indicate the pending transfer by showing  

:::“current ATC” => “next ATC”

'''''3. A target appears in your airspace:'''''

'''''4. A ATC forgets to “reassign” or “free” a target:'''''

<br>

==='''Summery of Flight-Strips and Target-Tags'''===

|-

|<small>'''''After TakeOff:'''''

|align="center"|[[File:OpenRadar-target-lables-30.png]]

|align="center"|[[File:OpenRadar-target-lables-31.png]]

|align="center"|[[File:OpenRadar-target-lables-33.png]]

|}

{| class="wikitable"

|-

|}

'''Radar Map'''

* On contact

''' Shortcuts '''

|-

! Shortcut !! Action

|-

|-

|-

|-

| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)

|-

|-

| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)

|-

| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)

|}

== Related content ==

* [[OpenRadar|The Design-Rules for OpenRadar]]

[[Category:OpenRadar|Guide]]