OpenRadarGuide: Difference between revisions

[[File:OpenRadar-Status.png|thumb|right|200px|The general Status Informations]]

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

</li><li>The third line lets you predict several values for that "radar contact" shown in the second line at the right (e.g. "D-Leon"). Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:

*Miles: The distance between the target and the mouspointer

*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!!

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

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 following keyboard-keys:

|COM0||Ctrl||NumOff+0

|COM1||Upper||NumOff+1

|COM2|| ||NumOff+4

|COM3|| ||NumOff+7

Please watch the color change of the PTT buttons to know, when you can speak. If the radio label turns to red, FGcom does not establish a connection on this frequency. OpenRadar has more frequencies available than FGcom knows of...

[[File:OpenRadar-Runways.png|thumb|right|200px|The Setting area runways]]

Here you define the major variables for your airport operations: That is the assignments of the runways. For this purpose OpenRadar gives you already a lot of precalculated values that shall help you. See e.g. the picture on the right:

**The runway-name  

**Check-boxes to define if it 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)

**a graphical display of the cross winds: They are green from 0-5kn, orange 5-10kn and red above. Gusts are additional highlighted.

**above that bar you see the length and width of the runway in '''meter'''!

**to the right follow 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>

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

|Target UID||Aircraft Type||direction to it

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

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 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 lines in the example:

"ILS VOR FGC NRE || GED MTR"

"ILS VOR FGC NRE || KJFK 280° f510"

<br /><small>This pilot also can use ILS, VOR, FGcom, NRE || and will depart to JFK on a straight course of 280° on FL510"</small>

You can manipulate the listing of the flight strips:

*New radar-targets always appear at the end of the list on the right side

*You can move them in vertical order by drag and drop

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

You cannot change these combinations of color and position -- but you might define your own definition of what the position means! We suggest the following:

*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 disturbe the radar-views.