OpenRadarGuide: Difference between revisions

Jump to navigation Jump to search
m
→‎Startup: reworded
m (update wordings)
m (→‎Startup: reworded)
Line 57: Line 57:
*for Windows: OpenRadar.bat
*for Windows: OpenRadar.bat
*for Linux: OpenRadar.sh
*for Linux: OpenRadar.sh
*for OSX: ''We do not know yet – pls help us with a FGFS-PersonalMessage to “wagnerw” or “jomo”''
*for OSX: ''We do not know yet – pleases help us with a FGFS-PersonalMessage to “wagnerw” or “jomo”''
<br />
<br />
At Startup you will always be welcomed with a the window “OpenRadar – Welcome” that presents 2 TABs to define your preferences:
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 2 TABs to define your preferences:
{|
{|
|-
|-
Line 67: Line 67:
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.
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 />
If this is the very first time you start OpenRader you first have to verify your “Settings”, thus click onto that “Settings”-tab:
If this is the very first time you start OpenRader, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:


=== OpenRadar-Welcome - Settings ===
=== OpenRadar-Welcome - Settings ===
Line 73: Line 73:
===='''1) FGcom'''====
===='''1) FGcom'''====
:OpenRadar can support up to 4 instances of FGcom in 2 ways:
:OpenRadar can support up to 4 instances of FGcom in 2 ways:
:#It can start and controll FgCom instances that operate in the background as sub-tasks of OpenRadar
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar
:#or just control manually started FgCom-sessions.
:#or just control manually started FgCom-sessions.


:You select these modes of operation by the “'''FgComMode'''” selection:
:You select these modes of operation by the “'''FgComMode'''” selection:
:'''a) Internal:''' FgCom(s) are started and controlled by OpenRadar
<br />
:'''a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar
::For this mode you have to define all available fields to tell OpenRader where your FGcom resides and what options shall be used:
::For this mode you have to define all available fields to tell OpenRader where your FGcom resides and what options shall be used:
::'''Path:''' Here you define where your FGcom is installed.
::'''Path:''' Here you define where your FGcom is installed.
Line 94: Line 95:
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)
|}
|}
::::<small>*) for OSX we do not know – pls help us by definig it here or send a PersonalMessage to “Wagnerw” or “jomo”</small>
::::<small>*) for OSX we do not know – pls help us by defining it here or send a PersonalMessage to “Wagnerw” or “jomo”</small>
</small>
</small>
::'''Executable:''' Here you define the Programname that shall be started
::'''Executable:''' Here you define the program-name that shall be started
<small>
<small>
:::*For Windows: "fgcom.exe" or  "anyName.bat"
:::*For Windows: "fgcom.exe" or  "anyName.bat"
:::*for Linux: "fgcom"  or  "anyName.sh"
:::*for Linux: "fgcom"  or  "anyName.sh"
:::*OSX: ''We do not know – pls help us by definig it here or send a PersonalMessage to “Wagnerw” or “jomo”''
:::*OSX: ''We do not know – pls help us by defining it here or send a PersonalMessage to “Wagnerw” or “jomo”''
</small>
</small>
::'''Server:''' There are 2 FGcom-servers available:
::'''Server:''' There are 2 FGcom-servers available as of today:
::*delta384.server4you.de <small>''(we do suggest this one)''</small>
::*delta384.server4you.de <small>''(we do suggest this one)''</small>
::*fgcom.flightgear.org.uk
::*fgcom.flightgear.org.uk
Line 108: Line 109:
::'''FGcom Ports:''' The here defined values are crucial for the operation because:  
::'''FGcom Ports:''' The here defined values are crucial for the operation because:  
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!
::*They also define how many “Radio Units” (COM0, COM!, etc.) are generated within OpenRadar
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar
::Simply provide a coma separated list of UDP Ports to be used by FGcom, but be warned, more than two are hard to handle.
::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!
:::::e.g. 16661,16662
:::::e.g. 16661,16662
 
<br />
:'''b) External:''' Control a manually started external instance of FGcom.
:'''b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.
:::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:
:::*Client: locahost
::*'''Client:''' locahost
:::*FGcom Ports: 16661,16662  (if e.g. 2 FGcom instances were started)
::*'''FGcom Ports:''' 16661,16662  ''(if e.g. 2 FGcom instances were started)''
 
<br />
:'''c) OFF:''' No FGcom support
:'''c) OFF:''' No FGcom support
:::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 fields and there will not be defined any Radio (e.g. COM0) in OpenRadar. This mode is not suggested!
::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 fields and there will not be defined any Radio (e.g. COM0) in OpenRadar. This mode is not suggested!
 


===='''2) FG Multiplayer'''====
===='''2) FG Multiplayer'''====
Line 133: Line 133:


===Select Airport===
===Select Airport===
This is always the first window that you will see after starting OpenRadar.  
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. In order to define your future work-locations 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. If an airport does already exist, it will be shown in the big center-field.
<br />
<br /><br />
 
When you start OpenRadar later on, you will see this list of already downloaded airports. Double click onto one of them (or select one with one click and then click onto start) and you are in the ATC seat.
But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:
<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 />
 
'''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.
<br /><br />
<br /><br />
----
----
== '''''Operating''''' ==
== '''''Operating''''' ==
[[File:OpenRadar Prototype.png|thumb|270px|Oakland international used in new OpenRadar]]
[[File:OpenRadar Prototype.png|thumb|270px|Oakland international used in new OpenRadar]]
652

edits

Navigation menu