652
edits
OpenRadarGuide: Difference between revisions
Jump to navigation
Jump to search
m
→Flight-Plan & Flight-Management: part of general update
m (→Flight Strip Manager: Part of general update) |
m (→Flight-Plan & Flight-Management: part of general update) |
||
| Line 412: | Line 412: | ||
=='''''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. | There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") 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. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot! | ||
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. | <br /><br /> | ||
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net". | |||
==='''Define/Edit a Flight-Plan:'''=== | ==='''Define/Edit a Flight-Plan:'''=== | ||
| Line 429: | Line 430: | ||
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change | * If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change | ||
*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will | *If it is “'''Controlled by …..'''” | ||
**either remove his “ownership” by | **you must wait till the ATC controlling it now will | ||
***clicking onto “Handover to” and selecting | ***either remove his “ownership” by | ||
****another ATC for takeover | ****clicking onto “Handover to” and selecting | ||
****or the “blank” for just removing his control. | *****another ATC for takeover | ||
***or clicking onto the button | *****or the “blank” for just removing his control. | ||
****or clicking onto the button “Control” (besides the lable "Uncontrolled...") | |||
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically | **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 | **or you send the controlling ATC a mail asking him to release the target | ||
| Line 445: | Line 447: | ||
'''Mandatory fields of the OR-Flight-Plan:''' | '''Mandatory fields of the OR-Flight-Plan:''' | ||
*'''Contact''' is the FGFS-UID of the target (will be set automatically) | *'''Contact''' is the FGFS-UID of the target (will be set automatically) | ||
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..) | |||
*'''Aircraft''' is the model-code of the target (will be set automatically) | *'''Aircraft''' is the model-code of the target (will be set automatically) | ||
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings” | |||
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot | |||
*'''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 ICAO-code of the destination (e.g. EDDF for Frankfurt) | *'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt) | ||
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL) | |||
*'''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) | *'''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:''' | '''Optional fields of the OR-Flight-Plan:''' | ||
*'''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” | *'''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” | ||
*'''Squawk''' shows the Squawk-Code you assigned to the target | |||
*'''Squawk''' shows the | *'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems) | ||
*''' | |||
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below)) | *'''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 | ||
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed) | *'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed) | ||
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport | *'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport | ||
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route | *'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route | ||
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). | *'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These 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:'''=== | ||
| Line 475: | Line 477: | ||
'''''1. A target appears on your airport''''' | '''''1. A target appears on your airport''''' | ||
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]] | :[[File:OpenRadar-Flightplanning-lables-1.png|500px]] | ||
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus | :There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus | ||
:*the text in the tag-color is “green” - i.e. you did not yet take | :*the text in the tag-color is “green” - i.e. you did not yet take control | ||
:*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 | :*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 | ||
:*a simple mouse-click or any other action will remove the green background. | :*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan). | ||
'''''2. You define a new Flight Plan''''' | '''''2. You define a new Flight Plan''''' | ||
| Line 526: | Line 528: | ||
*'''Transfer Control to next ATC (or blank) ''' | *'''Transfer Control to next ATC (or blank) ''' | ||
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]] | ::[[File:OpenRadar-Flightplanning-lables-3.png|500px]] | ||
*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 to the 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 up 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” | ||
| Line 534: | Line 536: | ||
'''''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 (i.e. move the Flight-Strip all the way to the left)'' if | ||
*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. | :* there is no ATC assigned yet | ||
*If the target lands on your airport: | :* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small> | ||
**assign a STAR | * 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. | ||
**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).'' | * If the target lands on your airport: | ||
** assign a RW and optional a STAR | |||
** 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. A ATC forgets to “reassign” or “free” a target:''''' | '''''4. A ATC forgets to “reassign” or “free” a target:''''' | ||
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over. | * The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over. | ||
* or you contact that ATC and require to release that target out of his control | |||
<br> | <br> | ||
==='''Summery of Flight-Strips and Target-Tags'''=== | ==='''Summery of Flight-Strips and Target-Tags'''=== | ||
| Line 572: | Line 577: | ||
|- | |- | ||
|<small>'''''After TakeOff:''''' | |<small>'''''After TakeOff:''''' | ||
notice that RW25C | notice that RW25C has been canceled</small> | ||
|align="center"|[[File:OpenRadar-target-lables-30.png]] | |align="center"|[[File:OpenRadar-target-lables-30.png]] | ||
|align="center"|[[File:OpenRadar-target-lables-31.png]] | |align="center"|[[File:OpenRadar-target-lables-31.png]] | ||
| Line 578: | Line 583: | ||
|align="center"|[[File:OpenRadar-target-lables-33.png]] | |align="center"|[[File:OpenRadar-target-lables-33.png]] | ||
|} | |} | ||
<small>'''''EDDF forwards target to EDDK:'''''</small> | <small>'''''EDDF forwards the target to EDDK:'''''</small> | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||