652
edits
OpenRadarGuide: Difference between revisions
Jump to navigation
Jump to search
→Flight-Plan & Flight-Management: finalized
m (→Communication: change to FGCom3.0 and add Mumble) |
(→Flight-Plan & Flight-Management: finalized) |
||
| Line 345: | Line 345: | ||
---- | ---- | ||
=='''''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 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. | |||
==='''Define/Edit a Flight-Plan:'''=== | ==='''Define/Edit a Flight-Plan:'''=== | ||
| Line 364: | Line 365: | ||
***clicking onto “Handover to” and selecting | ***clicking onto “Handover to” and selecting | ||
****another ATC for takeover | ****another ATC for takeover | ||
****or the “blank” for just removing | ****or the “blank” for just removing his control. | ||
***or clicking onto the button “UnControl” | ***or clicking onto the button “UnControl” | ||
**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 | ||
| Line 379: | Line 380: | ||
*'''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” - | *'''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:''' | ||
| Line 393: | Line 394: | ||
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL) | *'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL) | ||
*'''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 needed | *'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport | ||
*'''Comments''' | *'''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). The 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 402: | Line 403: | ||
* you can also use the '''^'''-key to open the FlightPlan of the active target. | * you can also use the '''^'''-key to open the FlightPlan of the active target. | ||
Then continue as described in the following scenarios: | Then continue as described in the following scenarios: | ||
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small> | |||
'''''1. A target appears on your airport''''' | '''''1. A target appears on your airport''''' | ||
:[[File:OpenRadar-Flightplanning-lables-1.png| | :[[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 filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus | ||
:*the tag-color is “green” | :*the text in the tag-color is “green” - i.e. you did not yet take controll | ||
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything 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. | ||
'''''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 | *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, then you cannot take over prior that the other ATC released or transferred that target!)'' | ||
*'''Generate the Flight-Plan:''' | *'''Generate the Flight-Plan:''' | ||
: | :Compare the Informations given in the target-label and the stripe: | ||
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small> | |||
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]] | |||
::{| class="wikitable" | ::{| class="wikitable" | ||
|- | |- | ||
| Line 420: | Line 423: | ||
|the pilot FGFS-UID | |the pilot FGFS-UID | ||
|- | |- | ||
| | |160° | ||
|the current heading (now on ramp!) | |the current heading (now on ramp!) | ||
|- | |- | ||
| | |HeadSet-sign | ||
|that pilot uses radio (FGCom or Mumble) | |that pilot uses radio (FGCom or Mumble) | ||
|- | |- | ||
| Line 433: | Line 436: | ||
|- | |- | ||
|260° | |260° | ||
|is the straight heading EDDF (departure) to KJFK (destination) | |is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small> | ||
|- | |- | ||
|BIBTI | |BIBTI | ||
| Line 447: | Line 450: | ||
|is the speed (still parking!) | |is the speed (still parking!) | ||
|} | |} | ||
<br> | <br> | ||
*'''Departing:''' | *'''Departing:''' | ||
**GND will use the data as shown to bring the plane to the HoldingPoint | **GND will use the data as shown above, to bring the plane to the HoldingPoint | ||
**TWR will take over | **TWR will take over | ||
**The runway-assignment will be removed automatically after Take-Off | **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| | ::[[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 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. | ||
| Line 464: | Line 464: | ||
: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 – indicating the “next ATC” is active -- and you cannot do any more changes! | *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! | ||
'''''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 ''(i.e. move the Flight-Strip all the way to the left)'' | *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)'' | ||
| Line 472: | Line 472: | ||
**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. 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. | |||
<br> | |||
==='''Summery of Flight-Strips and Target-Tags'''=== | |||
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table: | |||
{| class="wikitable" | |||
|+ | |||
!width="30%"|<small>Status</small> | |||
!width="30%"|<small>FlightStrip</small> | |||
!width="20%"|<small>Traditional | |||
(no transponder interaction)</small> | |||
!width="20%"|<small>Simulation | |||
(Transponder enabled)</small> | |||
!width="20%"|<small>Pure Simulation | |||
(Transponder enforced)</small> | |||
|- | |||
|<small>'''''Target appears on EDDF airport:''''' | |||
no ATC and no Flight-Data are assigned yet</small> | |||
|align="center"|[[File:OpenRadar-target-lables-10.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-11.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-12.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-13.png]] | |||
|- | |||
|<small>'''''jomoATC inputs a Flightplan:''''' | |||
from EDDF to KJFK via SID BIBTI straight hdg EDDF->KJFK 260° on Cruise Alt. FL250 | |||
Rw for TakeOff 25C</small> | |||
|align="center"|[[File:OpenRadar-target-lables-20.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-21.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-22.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-23.png]] | |||
|- | |||
|<small>'''''After TakeOff:''''' | |||
notice that RW25C is canceled</small> | |||
|align="center"|[[File:OpenRadar-target-lables-30.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-31.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-32.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-33.png]] | |||
|} | |||
<small>'''''EDDF forwards target to EDDK:''''' | |||
{| class="wikitable" | |||
|- | |||
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion | |||
after ATC-EDDK has taken over, that yellow will disappear | |||
and the "lastATC ==> "newATC" will be replaced by "currentATC" | |||
and the "private Notes" will be replaced with those of the newATC (if he has some)</small> | |||
|align="center"|[[File:OpenRadar-target-lables-41.png]] | |||
|- | |||
|<small>'''in EDDF''' that private notes remain, | |||
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small> | |||
|align="center"|[[File:OpenRadar-target-lables-42.png]] | |||
|align="center"|[[File:OpenRadar-target-lables-43.png]] | |||
|} | |||
== '''''Useful Features''''' == | == '''''Useful Features''''' == | ||