652
edits
OpenRadarGuide: Difference between revisions
Jump to navigation
Jump to search
finalizing that new feature
(→Flight-Plan & Flight-Management: first insert of this feature) |
(finalizing that new feature) |
||
| Line 229: | Line 229: | ||
**Then you may type or copy/past anything behind that - and send it out by ENTER | **Then you may type or copy/past anything behind that - and send it out by ENTER | ||
*Generate a standard message: | *Generate a standard message: | ||
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will open a list with the available messages - select one with a left mouse-click | **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 | ||
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER | **That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER | ||
*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. | *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. | ||
| Line 352: | Line 352: | ||
---- | ---- | ||
=='''''Flight-Plan & Flight-Management'''''== | =='''''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. 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. | |||
There is a | |||
==='''Define/Edit a Flight-Plan:'''=== | ==='''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” | You open the Flight-Plan for a target by clicking with the “center mouse-button” | ||
*onto the Flight-Strip of the target | |||
*or the target on the radar-screen | |||
You can also open the "active" target by the '''^'''-key | |||
'''Controlling the ownership:'''<br> | '''Controlling the ownership:'''<br> | ||
| Line 377: | Line 378: | ||
*If it shows “'''Controlled by me'''” you can release the target | *If it shows “'''Controlled by me'''” you can release the target | ||
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover | **by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover | ||
**or you grab the Flight-Strip with the mouse and move it left into the radar-scope and select an ATC (or “blank”) | **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”) | ||
**or you move the Flight-Strip all the way to the right – that will just remove your ownership | **or you move the Flight-Strip all the way to the right – that will just remove your ownership | ||
'''Mandatory fields of the OR-Flight-Plan:''' | '''Mandatory fields of the OR-Flight-Plan:''' | ||
*'''Contact''' is the | *'''Contact''' is the FGFS-UID of the target (will be set automatically) | ||
*'''Aircraft''' is the model-code 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) | *'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual) | ||
*'''Destination''' needs the IATA-code of the destination (e.g. EDDF for Frankfurt) | *'''Destination''' needs the IATA-code of the destination (e.g. EDDF for Frankfurt) | ||
*'''ETA''' is the “Estimated Time of Arrival” - it is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (will be calculated automatically) | *'''ETA''' is the “Estimated Time of Arrival” - it is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (will be calculated automatically - you might override it if you know/want it more realistic) | ||
'''Optional fields of the OR-Flight-Plan:''' | '''Optional fields of the OR-Flight-Plan:''' | ||
*'''native language''' is per default “en” for English. If you choose another language your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” | *'''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” | ||
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble) | *'''FgCom''' indicates that target can use Radio (FGCom or Mumble) | ||
*'''Squawk''' shows the Squake-Code you assigned to the target | *'''Squawk''' shows the Squake-Code you assigned to the target | ||
*'''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” | *'''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” | ||
*'''Route''' defines the SID, STAR, etc. assigned | *'''Route''' defines the SID, STAR, etc. assigned | ||
*'''Altitude''' as assigned by ATC from time to time (not the constant Crsg.Alt!) | *'''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 | *'''Code''' will be used in future when given by a more professional Flight-Planning system | ||
*'''IFR/VFR''' may be defined by the PullDown | *'''IFR/VFR''' may be defined by the PullDown | ||
| Line 401: | Line 402: | ||
*'''Alt.Airports''' can be defined as needed deviations in case of bad weather etc. | *'''Alt.Airports''' can be defined as needed deviations in case of bad weather etc. | ||
*'''Comments''' these are comments that will be kept together with the Flight-Plan | *'''Comments''' these are comments that will be kept together with the Flight-Plan | ||
*'''Private notes''' are comments that remain with the ATC making these (in file OpenRadar/settings/atcComments.xml) and will always be inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not. | *'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml) and will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not. | ||
==='''Flight-management:'''=== | ==='''Flight-management:'''=== | ||
Open the wanted Flight-Plan | |||
* by a center-mouse-click onto the radar-target or the FlightStrip | |||
* you can also use the '''^'''-key to open the FlightPlan of the active target. | |||
Then continue as described in the following scenarios: | |||
'''''1. A target appears on your airport''''' | '''''1. A target appears on your airport''''' | ||
:[[File:OpenRadar-Flightplanning-lables-1.png|thumb|270px]] | |||
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus | |||
:*the tag-color is “green” | |||
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it. | |||
:*a simple mouse-click or any other action will remove the green background. | |||
'''''2. You define a new Flight Plan''''' | '''''2. You define a new Flight Plan''''' | ||
*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 in charge you cannot take over prior that the other ATC released or transferred that target!)'' | *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 in charge, then you cannot take over prior that the other ATC released or transferred that target!)'' | ||
*'''Generate the Flight-Plan:''' | *'''Generate the Flight-Plan:''' | ||
:See the Informations given in the target-label and the stripe. e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)” it could look like: | :See the Informations given in the target-label and the stripe. e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)” it could look like: | ||
| Line 457: | Line 461: | ||
**GND will use the data as shown to bring the plane to the HoldingPoint | **GND will use the data as shown to bring the plane to the HoldingPoint | ||
**TWR will take over | **TWR will take over | ||
**The runway-assignment will be removed automatically | **The runway-assignment will be removed automatically after Take-Off | ||
<br> | <br> | ||
*'''Transfer Control to next ATC (or blank) ''' | *'''Transfer Control to next ATC (or blank) ''' | ||
::[[File:OpenRadar-Flightplanning-lables-3.png|thumb|270px]] | ::[[File:OpenRadar-Flightplanning-lables-3.png|thumb|270px]] | ||
*grab-move the FlightStrip left into the Scope and select the next ATC (or open the Flight-plan and select at “Handover to:”). | *grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''. | ||
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route. | *if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route. | ||
*the FlightStrip will indicate the pending transfer by showing | *the FlightStrip will indicate the pending transfer by showing | ||
:::“current ATC” => “next ATC” | :::“current ATC” => “next ATC” | ||
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention! | :The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention! | ||
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – | *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:''''' | '''''3. A target appears in your airspace:''''' | ||
*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 | *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)'' | ||
*if the target has no owner yet and is just crossing your airspace and | *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. | ||
*If the target lands on your airport: | *If the target lands on your airport: | ||
**assign a STAR and/or RW | **assign a STAR and/or RW | ||
**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).'' | **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).'' | ||
'''''4. | '''''4. A ATC forgets to “reassign” or “free” a target''''' | ||
the ownership will automaticalle be removed as soon as the tagets gets out of the rang of that ATC (~100mi). After that any other ATC may take over. | |||
== '''''Useful Features''''' == | == '''''Useful Features''''' == | ||
| Line 492: | Line 497: | ||
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field | :* '''left''' click '''selects''' the contact and sets cursor into the chat input field | ||
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language) | :* '''middle''' click opens the radar '''contact settings''' (ATC note and native language) | ||
:* '''right''' click opens the '''ATC messages''' | :* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /> | ||
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact) | :* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact) | ||