OpenRadarGuide: Difference between revisions

=='''''Preface'''''==

[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.

Some words to our project targets:

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

:::The most used Mumble-server is "mumble.allfex.org"

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  

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

** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories

* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!

== '''''Startup''''' ==

Inside the downloaded OpenRadar base-directory you will find start-scripts. See

At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 3 TABs to define your preferences:

{|

===Select Airport===

This is always the first window that you will see after starting OpenRadar.

But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:

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

'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.

Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.

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

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

* adjust the map-center by dragging it with your mouse (click-hold left and drag)

</span>

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

=====Status Informations=====  

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

This area shows in 4 lines the most used status-informations:

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

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

</li></ol>

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

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

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

*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.

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

[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]

You can '''''manipulate the listing''''' of the flight strips:

On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!

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

*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact

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

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

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.

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

[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]

You open the Flight-Plan for a target by clicking with the “center mouse-button”

*onto the Flight-Strip of the target

|-

|<small>'''''jomoATC inputs a Flightplan:'''''

Rw for TakeOff 25C</small>

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

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

|}

== Related content ==