FlightGear wiki - User contributions [en]

User:Mcantsin

2014-12-02T21:51:06Z

Mcantsin:

{{User
|name = Luther Blissett
|location = world
|interests = ATC, navigation data, radar client, GNU/Linux, copyleft
|callsign = mcantsin
|favourite = Falcon 7X
}}

== Why I am here ==
As an GNU/Linux and Aviation enthousiast I like the approach and the way flightgear is being built and developed. As an ATC controller for [http://vatsim.net/ VatSim], which is a very professional and hierarchical organisation, I control areas such as South-Eastern Asia (ASEA FSS), [http://vatthd.net/ Thailand (VTBB FIR)], [http://vcats.no-ip.org/ Cambodia (VDPP FIR)] etc., produced charts and training material for virtual controllers and virtual pilots. Due to the [http://forums.vatsim.net/viewtopic.php?f=7&t=25284&start=60 caginess of the VatSim community] towards Free Software, especially GNU/Linux, I am willing to invest my spare time to bring ATC services for FlightGear further and am especially looking forward into the development of [[OpenRadar]]. - So I might be new to the FlightGear community, but am nevertheless willing to provide professional knowledge and ideas.

== Contact ==
E-mail: open.pop.star@gmail.com 
Twitter: [http://twitter.com/openpopstar/ OpenPopStar] 
IRC: mcantsin @de.irc.flightgear.org 
Video Broadcast of FG sessions: [http://twitch.tv/mcantsin Twitch]

User:Mcantsin

2014-12-02T21:49:54Z

Mcantsin:

{{User
|name = Luther Blissett
|location = world
|interests = ATC, navigation data, radar client, GNU/Linux, copyleft
|callsign = mcantsin
|favourite = Falcon 7X
}}

== Why I am here ==
As an GNU/Linux and Aviation enthousiast I like the approach and the way flightgear is being built and developed. As an ATC controller for [http://vatsim.net/ VatSim], which is a very professional and hierarchical organisation, I control areas such as South-Eastern Asia (ASEA FSS), [http://vatthd.net/ Thailand (VTBB FIR)], [http://vcats.no-ip.org/ Cambodia (VDPP FIR)] etc., produced charts and training material for virtual controllers and virtual pilots. Due to the [http://forums.vatsim.net/viewtopic.php?f=7&t=25284&start=60 caginess of the VatSim community] towards Free Software, especially GNU/Linux, I am willing to invest my spare time to bring ATC services for FlightGear further and am especially looking forward into the development of [[OpenRadar]]. - So I might be new to the FlightGear community, but am nevertheless willing to provide professional knowledge and ideas.

== Contact ==
E-mail: open.pop.star@gmail.com 
Twitter:
IRC: mcantsin @de.irc.flightgear.org 
Video Broadcast of FG sessions: [http://twitch.tv/mcantsin Twitch]

OpenRadar

2014-12-02T21:43:18Z

Mcantsin: corrected wrong image description

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease =
| latestrelease = 15th March 2014
| writtenin = Java
| os =
| platform =
| developmentstatus = active
| type =
| license =
| website = http://www.gitorious.org/fg/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Binary release download, updated 2014-05-18]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadarDownload|Download! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadarKnownIssues|FAQ / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:Air Traffic Control]]
[[Category:Java]]
[[Category:OpenRadar| ]]

Talk:OpenRadar: Editing routes

2014-10-20T17:32:20Z

Mcantsin: Created page with "I understand using ''addPoint'' to add missing navigation points. But how can a existing, misplaced waypoint be changed to the correct position? ~~~~"

I understand using ''addPoint'' to add missing navigation points. But how can a existing, misplaced waypoint be changed to the correct position? [[User:Mcantsin|Mcantsin]] ([[User talk:Mcantsin|talk]]) 17:32, 20 October 2014 (UTC)

Talk:Airport data (apt.dat) update

2014-05-12T18:27:11Z

Mcantsin: Navigraph announcement to support X-Plane format in future release

==Independent apt.dat source==
I would like to suggest to use an independent, community based source for apt.dat data, such as [http://github.com/mcantsin/x-plane-navdata/wiki this project on github].
[[User:Mcantsin|Mcantsin]] 01:57, 28 February 2013 (UTC)
:: Then maybe you can explain what is not independent and community based on Robin's data? It's GPL and a new release is around the corner. --[[User:Papillon81|Papillon81]] 11:09, 28 February 2013 (UTC)
::: If you read [http://github.com/mcantsin/x-plane-navdata/wiki the description] you will learn why. [[User:Mcantsin|Mcantsin]] 11:23, 28 February 2013 (UTC)
:::: Hi Luther,
:::: Your GitHub is also maintained by a single maintainer (you), right? So how's that different, other than being a Git repository?
:::: The idea in itself is interesting, but I see lots of issues, just to name a few:
::::* How would you deal with merging back changes that are made to the official data?
::::* Do changes made in your repository get merged in Robin's?
::::* What if your and Robin's data conflict; who is "right"?
::::* What if a new apt.dat format is designed, how will you be able to convert the data to that new format?
:::: When I can choose between two sources of data: one having all kind of infrastructure in place to ensure easy maintenance and dozens of contributors, and one with no infrastructure and just a single commiter, I'd choose for the first option...
:::: [[User:Gijs|Gijs]] 11:45, 28 February 2013 (UTC)
::::: I understand your points, GiJs. But the idea of (officially) releasing *up-to-date* apt.dat data through git(hub) means:
:::::* Having the ability of keeping track (publicly visible) of the changed data through version control.
:::::* Offering the possibility to a group of multiple people to publish "releases", which can be argued and officially announced. (e.g. official "master" tree).
:::::* Offering *anyone* to pull, change and publish his own tree.
:::::* Offering to *anyone* to contribute to the source data directly withouth obstacles.
:::::* Offering *anyone* to pull *any* version of the data, not just the latest one.
:::::* Disposing of the fact that Robin is unresponsive to data correction submissions. (I have waited 11 months to receive a cheap answer to my e-mail to Robin, saying that he is too busy...)

:::::Regarding your questions:
:::::* Who would maintain the "official" master tree
::::: I would be most happy to let the FG dev team name and appoint the individuals forming some sort of "official data" group. - They would be the ones drafting rules for data submissions (format, procedure etc.) in the first place.
:::::* Robin's data
::::: Frankly spoken I don't care about Robin's data any longer, as it is largely out of data and out of accuracy. I wrote my own awk shell script, which converts my navigraph data into apt.dat and that does a wonderful job for my personal use. I don't pull Robin's data any longer...
:::::* "Conflict"
::::: There would not be a "conflict", as Robin's data simply is not accurate any longer and in case of a "official fg data release group" a possible conflict could be argued, then discussed and decided. - Not by one single person that only has a focus on local airports and nav data, but by an international community. And in case of conflict the real life data can simply be adapted. (There are many real life ATC's and Pilots who would deliver this most accurate data to be used in case of a conflict.)
:::::* Conversions
::::: Conversions can simply be made using GNU awk, sql, etc. there are large tools available and this is not an issue yet.

:::::So. - Having the ability of bringing apt.dat to the next generation or remaining dependent to one single, unresponsive maintainer... Make a wise joice.
:::::[[User:Mcantsin|Mcantsin]] 12:44, 28 February 2013 (UTC)
:::::P.S. I don't say that it has to be [http://github.com/mcantsin/x-plane-navdata/wiki this particular project]. What I offer is just a suggestion of thinking about the benefit of using git for maintaining up-to-date and accurate data.

I have to agree with Mcantsin about submissions to Robin: he doesn't acknowledge them nor include those from others,despite his heading. I submitted several Canadian suggestions which I (naively) expected to see in the 2.10 release of FG's nav.dat and fix.dat, but they were not to be found. They were submitted well in advance, so lateness shouldn't be an excuse for them not to be there. As to conflicting about accuracy, most of what I'm finding are misplaced navaids, or those which have not yet made it into the list. As with anything in the scenery, I think an argument about who is 'right' or more accurate would be as senseless as some other arguments I see on FG. I have corrected several NDB poistions, and fixes, which led me off track on a final approach to runway, and after my corrections, that no longer happened, as I test my corrections before submitting them. I would trust that anyone who is submitting corrections or new navaids would at least fly them to ensure they're where they're supposed to be in relation to the function for which they placed there in the first place. I support this effort, as I"m tired of being disappointed with each new release and the same old errors and omissions in navaids and fixes are still there. I would like to encourage the devs to access this database, combine our efforts with those of Robin, allowing us, in some small way, to contribute to the project and generally make flying more enjoyable for everyone. "Never put all your eggs in one basket," might seem to be a good analogy here; if we're going to stubbornly stick to one source (Robin's) I believe we're doing a disservice to the project, and those who use it.
[[User:Trennor|Trennor]] 04:45, 2 April 2013 (UTC)

: Ahem, flightgear is still using the old 8.10 apt.dat format file, thus the outdated data. That does not mean a change in the way apt.dat source is maintained and updated is not a good idea. --[[User:Aep|Aep]] 11:40, 2 April 2013 (UTC)

: To complement what's said by Aep, FlightGear is currently using the .dat files from a long time ago. Simply because FlightGear does/did not support the new format that X-Plane (and Robin) have moved to. Luckily we're catching up fast and scenery with the new format will probably be available this summer. In order to have matching navigational data and scenery, it is important that we update both at the same time (which is why we cannot just update the nav data right now).
: I've spoken to several FlightGear people who sent changes to Robin and all of them were included in the latest files from http://data.x-plane.com Please check those files to see if your changes are in (make sure you download "Latest data"). It's not fair to blame Robin for something he has no control over.
: Needless to say that we cannot "combine our efforts" maintaining two independent databases.
: [[User:Gijs|Gijs]] 16:16, 2 April 2013 (UTC)

::Well. I hereby would like to express my deepest sympathy and condolences for Robin's feelings. - But let's focus on how to frame the publishing of accurate and up-to-date navigation data for that flightsimulators can be used for training of (real life) pilots and ATC's. 
::So I kindly & heartily invite you to discuss and draft a **true** GPL based navigation data source. [[User:Mcantsin|Mcantsin]] 18:35, 2 April 2013 (UTC)

:::I want to see an example of outdated or inaccurate nav data in '''Robin's''' database, not what we ship with flightgear. Changing datasources is NOT going to happen (at least in the short term) - It's taken a team of 3 people over 2 years now to update the scenery generation tools to use the x-plane 8.50 - 10.00 formats. We should have the results finalized by summer. Remember - the data involved contains all of the airport (runways, taxiways, towers, parking positions, etc) as well as nav data. If you have nav data that doesn't contain the layout of the airport, guess what - your ILS landings will take you into the grass, not the runway. </end rant> --[[User:Psadro gm|Psadro gm]] 19:57, 2 April 2013 (UTC)

[http://www.navigraph.com/downloads/xplane-zbaa-1405.png Navigraph today announced X-Plane support] in the upcoming AIRAC1406! \o/ [[User:Mcantsin|Mcantsin]] ([[User talk:Mcantsin|talk]]) 18:27, 12 May 2014 (UTC)

OpenRadarFeatureWishlist

2013-07-26T21:48:23Z

Mcantsin: Transponder code bug

Boeing 737-400

2013-05-01T01:51:45Z

Mcantsin: dead download link

{{infobox Aircraft
|image =737-400.png
|alt =Boeing 737-400 at Frankfurt Main EDDF
|name =Boeing 737-400
|type =Airliner
|livery =Aerolineas Argentinas, Avior Airlines, China Southern, EasyJet, FlightGear iEspana, Hapag-Lloyd Express, HLX-TMobile, Iberia, LAN Chile, Lufthansa, MALEV, Malaysia Airlines, Mexicana, Ryanair, Scandanavian Airlines, Southwest, Turkish, United Airlines, Viasa, Virgin Blue, Virgin Express, Volaris
|authors =David Culp, Innis Cunningham, FlightGear Iespaña Team
|fdm = [[JSBSim]]
|status =In-Development
|fgname =737-400
|download = http://flightgear.iespana.es (dead link)
}}
The '''Boeing 737-400''' was launched in 1985 as a stretched [[737-300]], primarily for use by charter airlines.

== Download ==
You have to download two files, since the model and the sounds come in two different packages and go into two different directories.

Note: Divshare may not function on Windows 7 Laptops.

In November 2009, the direct links are:
* Model: http://www.divshare.com/download/7242443-cb1 (--> unpack to FGROOT\data\aircraft)
* Sounds: http://www.divshare.com/download/5256565-2c4 (--> unpack to FGROOT\data)
You can find the newest version of both on http://flightgear.iespana.es/

== Aircraft help ==
For information on engine startup, livery selection, auto brake, reject take off etc. press "?" or "Help --> Aircraft Help" when the simulation is running.

== Navigation ==
As far as I know, out of all airliners the 737-400 has the best modelled navigation panels available in FlightGear. You can set almost all frequencies and Autopilot settings from the 3D cockpit, and very detailed information is given back to you on the screens and instruments. Here are some features:

=== TCAS ===
The TCAS ([http://en.wikipedia.org/wiki/Traffic_Collision_Avoidance_System Traffic Alert and Collision Avoidance System]) displays other aircraft on the main screen. The radar has a range of 20nm. Each bar on the white line in the middle marks 5nm. To use TCAS, you have to switch it on:

[[File:Tcas1.png|200px]]

TCAS off.

[[File:Tcas2.png|200px]]

TCAS on. Blue triangles: Other multiplayer pilots. White triangles: AI aircraft. (This screenshot was taken at an airport.)

[[File:Tcas3.png|200px]]

Switch on TCAS in the middle console. A voice will say "TCAS system test okay".
=== FMC (Flight Management Computer) ===
For example, I have set up the [[Route Manager]] to follow the fixes OMOGI, OKAVO, AKONI and OBERO.

[[File:RoutemanB7341.png|200px]]

Once route is programmed, it's displayed in the middle console. The distance to the next waypoint OMOGI is 13.5 nm. The total distance to the last waypoint is 31.9 nm.

[[File:RoutemanB7342.png|200px]]

The next waypoint is displayed on the screen as a yellow dot.

=== VOR ===
[[VHF Omni-directional Radio Range|VOR]] arrows (vectors) are blue if in NAV1 and green if in NAV2. They point in the direction of the [[VHF Omni-directional Radio Range|radial]] you defined in the radio settings (Equipment --> Radio Settings). In the 737-400, when are 20 nm or closer, the VOR will show up on the screen. In the following screenshot, a VOR, for which you have set a radial of 080, is 10 nm away from you and you are flying directly to it. Note that there is traffic at your 5 o'clock.

[[File:B734vor1.png|200px]]

=== NDB ===
[[List of abbreviations#N|NDB]] arrows are dark yellowish. The long one points in the direction of the NDB, i.e. tells you where the NDB is relative to you. The short arrow indicates the radial you defined in the radio settings dialogue.

[[File:B734ndb1.png|200px]]

The NDB is at a heading of approximately 267 from you (long arrow), but you want to approach it at a radial of 250 (short arrow). Fly a little to the right to align both arrows:

[[File:B734ndb2.png|200px]]

=== ILS ===
[[ILS]] appear in the same way as VORs, as blue or green arrows. The thick dot in their center is the beginning of the runway. In the following example you approach runway 25R at EDDF from southwest. On the map you see several navaids:

[[File:B734ils3.png|200px]]

On the extended runway, apart from the ILS localizer, there are also the VOR Frankfurt FFM and the NDB Frankfurt FR. In the two following screenshots, you use more than one navaid. Left image: ILS localizer and NDB (radial 250). Right image: You add the VOR (radial 250).

[[File:B734ils1.png|200px]] [[File:B734ils2.png|200px]]

Have fun flying this cool plane and feel free to improve this article!

{{Boeing}}

[[Category:Airliners]]

[[fr:Boeing 737-400]]

Airbus A330-200 (Old)

2013-05-01T01:47:50Z

Mcantsin: dead download link

{{non-GPL}}

This aircraft is NOT GNU-GPL Compatible, so if you'd like to use parts of it for other aircraft, please contact '''muraleen@my.erau.edu'''.
''NOTE - This wiki page applies for the A330-300s too.''

{{infobox Aircraft
|image = A332-splash.png
|name = Airbus A330-200 Series
|type = Wide-body Airliner
|fdm = JSBSim
|status = v2.0, Git Development Version
|authors = Narendran M, Chris M, Zhuang T, Geir M, Kyle D, A320neo Developers
|fgname = A330-203, A330-223, A330-243
|download = http://theomegahangar.yolasite.com/aircraft.php (download link is dead)
|development = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main
}}
This aircraft package is now rembrandt compatible! (Simply checkout the rembrandt branch from the git repository to get it)

The '''Airbus A330-200 series''' project consists of the '''Airbus A330-203''' (A330-200 with ''General Electric CF6-80E1 Engines''), '''Airbus A330-223''' (A330-200 with ''Pratt and Whitney PW4000 Engines'') and the '''Airbus A330-243''' (A330-200 with ''Rolls Royce Trent 772B-69 Engines''). The project uses theOmegaHangar's new [[Airbus A320neo|Airbus A320/30/40]] cockpit and systems and new Airbus A330-200 models. Feel free to start a discussion in [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 the forum topic] if you'd like to contribute to the project.

==Airbus Systems==

===Airbus Fly-By-Wire===
The Airbus fly-by-wire (adapted from the Airbus A320neo fly-by-wire) is a system which continuously takes in the pilot's stick input, uses them as Pitch/Roll-Rate commands, and calculates the required surface deflection to achieve the commanded rate. The fly-by-wire also provides flight envelope protection and the soft/hard bank feature.

====Pitch/Roll-Rate and G-Force Command====
For the Roll Axis, the stick all the way to the left commands a negative 30 degrees roll rate and all the way to the right commands a positive 30 degrees roll rate.

As for the Pitch Axis, the commands are divided according to the airspeed of the aircraft. If the Airspeed is under 210 knots, pitch-rate is used and over 210 knots, g-force is used. Under 210 knots, pulling the stick all the way to the back commands a 30 degrees pitch rate and pushing it all the way forward commands a negative 30 degrees pitch rate. Over 210 knots, pulling the stick all the way to the back commands a 2.75G acceleration and pushing it all the way forward commands a -0.75G acceleration.

====Flight Envelope Protection====
For the Roll Axis, having the stick less than half way deflected either side, you get what's called a ''soft bank''. With a soft bank, the aircraft can't exceed 33 degrees of bank to either side. If the stick is deflected more than half way, you get a hard bank and the aircraft can be banked up till 67 degrees to either side.

For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.

=== Hydraulics System ===
The Airbus A320, A330 and [[Airbus A340|A340]] series have similar hydraulic systems. There are three hydraulic systems on the aircraft, each having it's own reservoir- the '''GREEN''' system, the '''YELLOW''' system and the '''BLUE''' system.

The Green system is powered by the Left Engine's Hydraulic Pump, the yellow by the Right Engine's Hydraulic Pump and the Blue System with an Electric Pump. During normal operation, each hydraulic system should have their hydraulic pressure between 2500 and 3000 PSI. (Pounds per Square Inch) The engine systems control the surfaces, stabilizers, flaps/slats and landing gears while the electric pump system connect to only the surfaces and stabilizers. In case a system fails, an alternate system can be used. The yellow system also has an electric pump which can be used to power the hydraulics using external power when the aircraft is on the ground.

The Yellow and Green Hydraulic systems have a power transfer unit which is used to transfer hydraulic pressure between the pumps in case there is a 500 PSI difference between the pressures in the green and yellow systems.

All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.

'''MORE SYSTEMS INFORMATION COMING SOON'''

== Example Flights ==

We'll show 2 example flights- a flight that uses a company route from the default flight database and a custom planned flight.

=== MIA134 from Brisbane to Singapore (Company Route) ===

MIA134 is one of merlion's alternate-day flights from Brisbane to Singapore. We'll just be using this as an example and you can use the same procedures from any route from the company database. (Take a look at our database flights below) Flight MIA134 is flown with an Airbus A330-243 (Rolls Royce Trent 772B-60 Engines) virtually registered S-QDAZ.

First, start-up at any of the parking ramps at Brisbane's (YBBN) International Apron. As Brisbane doesn't have parking positions at the moment, start-up on runway 01 and taxi-to (best using pushback) a parking gate in the International Apron.

==== Pre-Flight Planning ====

To start with the pre-flight planning, we need electrical power. For Airports that provide external power, we can use that and for other airports, the APU can provide power. At Brisbane, external power is available, so make sure your ground services dialog has external power box enabled and turn on '''EXT PWR''' from the ''Overhead Panel''. (View)

Before we start anything, let's make sure everything's how they should be. Make sure only the following Overhead panel buttons have OFF showing on them- HYD YELLOW ELEC PUMP, ENG1, ENG2 and CTR TNK LTK FUEL PUMPS 1 AND 2, BAT1, BAT2, GEN1, GEN2 and APU GEN. EXT PWR should show ON. Now, look at the Pedestal and make sure both engine master switches are at OFF, the throttle is at idle, the engine mode is set to NORM, the speed-brakes are at 0, the parking brake is ON and the Flaps Lever is at 0. Let's now start with the pre-flight planning.

* Turn to the ''FMGC/mCDU View'' and turn on the Airbus mCDU by rotating (scroll) the BRT knob to full.

* Click on DATA and then A/C STATUS. Make sure the ACTIVE NAV DATABASE is ''27MAY-26AUG MIADatav3.1''. If not, please re-download the ''Database/Company/routes.xml'' file from gitorious.

* Now, click on INIT to head to the routes initialization page. You can initialize the company route by entering the company route ID (reference below) or the departure and arrival ICAOs. I normally enter the departure and arrival ICAOs as that way, it gives you all available routes you can choose from. So enter '''YBBN/WSSS''' and click on the LSK (Line Selector Key) next to FROM/TO.

* The mCDU will show 2 available routes (MIABNESIN1 and MIABNESIN2) which you can scroll through using the left and right arrow keys on the mCDU keypad. We'll be using MIABNESIN2 for this flight, so view that and click on the LSK next to INSERT. Once you do that, you should see that MIASINBNE2 would be written under CO_RTE and YBBN/WSSS would be written under FROM/TO.

* Enter the Flight Number '''MIA134''' and click on the LSK next to FLT NUM. '''(OPTIONAL)'''

* If you want, you can also enter a COST INDEX for the flight (normally between 25 and 40). '''(OPTIONAL)'''

* If you have an alternate route (not supported atm), you can enter the Alternate airport ICAO and RTE ID in the ALTN/CO_RTE Field.

* The final step in the INIT A page is your cruise altitude and Temperature. We'll be cruising at Flight Level 360 (FL360/36,000 ft) and checking the ''Environment>Weather Dialog'', it's about -55 degrees at that altitude, so enter '''360/-55''' and hit the LSK next to CRZ ALT/TEMP.

''NOTE: To get the '''-''', press on the '''+/-''' key in the keypad twice.''

* After INIT A is complete, let's proceed to INIT B (aka. FUEL PREDICTION Page), click on the RIGHT ARROW KEY on the keypad to go there.

''NOTE: Please skip the next 2 steps for the moment as this part requires fixing.''

* Once there, the trip fuel/time should show about 120 blocks of fuel (atm, it shows 24 but it will be fixed soon) required for the flight. The Aircraft can hold a maximum of 172.5 Blocks (1 Block = 804 KG JET-A Fuel). It should also show that the total flight will be about 442 minutes long using the initialized route. That is 8 hours and 22 minutes, a decent time for about 4000 miles.

* We'll take 10% fuel with us for reserves, so enter '''0/10''' and hit the LSK next to RSV. The mCDU will automatically calculate our extra fuel, TOW (Take-off Weight) and LW (Landing Weight).

* Now, click on F-PLN to go to the Primary Flight-plan Management Page. Here, you'll see the automatically initialized flight plan which you can scroll through using the up and down arrow keys on the keypad. Atm, we don't need to make any changes to our flight-plan as the company route sets everything perfect for us. We'll come back to F-PLN Lateral Revision (LAT REV) in the next custom planned example flight.

* We need to select a DEPARTURE and ARRIVAL procedure for our flight. To select a DEPARTURE Terminal Procedure, click on the LSK next to YBBN (Right above F-PLN DISCONTINUITY) and click on the LSK next to DEPARTURE.

* I'll be using runway 19 for departure (Currently Winds are 200@9), so I click on the LSK next to 19.

* Our first waypoint (after YBBN) is WOODY, so I want a DEPARTURE PROCEDURE that'll take me to WOODY. A procedure available for Runway 19 is ''WODY2A.19'' (at the end of the list). Select that and hit the LSK next to INSERT.

* Now, for the arrival procedure, you want to find your last waypoint before WSSS, so go to the F-PLN page and scroll to the end. With this route, ''REPOV'' is the last waypoint. (With MIABNESIN1, LAVAX is the last waypoint.

* Scroll back up and click on the LSK next to DEST WSSS and then select ARRIVAL.

* We'll be landing on Runway 20R (usually the default intl. runway at WSSS), so I select 20R. For the Arrival Procedure, select and INSERT REME6B.20R as that procedure starts at REPOV.

''NOTE: Small sections based on the PERF, DIR and PROG pages are remaining but we'll get back to that once it's completely functional.''

We have completed out basic flight-planning. We will focus on Radio Navigation later. Let's now fuel up for the flight. As we entered in the mCDU, we'll be starting with 130 blocks of fuel for this 8 and a half hour flight. That's 104,500 KG JET-A fuel. Open the Fuel Truck dialog, enable to truck, connect it to the aircraft, enter '''104500''' in hte REQUEST KG and Start Filling up the aircraft. Once the fueling is complete, we can disconnect the fuel truck and proceed to starting up the aircraft. Remember to first disconnect all ground services and remove the chokes.

==== Manual Engines Start-Up Procedure ====

* Turn on the Beacon Lights from the Lighting Control Panel.

* Look up at the overhead panel and turn on the APU by turning on the APU MASTER SW and the START button. You should hear the APU spooling. Once it's started, turn off the APU START switch and turn on the APU GEN.

* To get fuel to the engines, you need to turn on the LTK PUMPS, so turn on all the ENG1, ENG2 and CTR TNK FUEL PUMPS.

* Switch to Pedestal View and in the throttle quadrant, set the Engine MODE to START, and then turn both engine master switches to ON.

* Keep an eye on the Upper ECAM. When both Engine N1% exceeds 25%, the engines are started and running. Turn the Engine MODE back to NORM and turn off the APU.

* Turn on the Navigation Lights.

Release Parking Brakes and use 2 notches of Flaps for take-off. Pushback and taxi to the runway as usual. While taxiing, you could set your autopilot and other preferences. For autopilot, I'm going to make sure everything is disarmed and then set speed to IAS:250|MACH:0.72, altitude to 36000 ft (switch the black knob in behind the ALT knob to 1000 for easier scrolling, V/S to 2200 and finally click on the HDG knob to turn it to ''Managed'' Mode. You can also set ND and Lower ECAM Display Pages- I use the NAV page on the ND with 40 nm range (VORD, NDB and ARPT selected), and normally keep the FUEL page on the Lower ECAM. If you need to check another system, you can use the switching panel to change to that display.

Finally, remember to set your altimeter setting. Get your altimeter setting from Environment>Weather and scroll the altimeter setting knob on the Glare-shield panel to that reading.

''NOTE: Managed Mode means the FMGC tells the computer where the plane should go. This is equivalent to LNAV on Boeing aircraft.''

==== Take-off and Cruise ====

Once you're holding short, revise your reference speeds. At this weight, they'd be- V1:140, Vr:150, V2:156.

When the runway is clear (and/or you have ATC's permission), taxi on to the runway and turn on the Strobe Lights. Power up the throttle all the way, and rotate at Vr and make sure you're airborne by V2. Retract your gears and when you reach the respective flaps extension speeds (PRINTED ON THE MAIN PANEL), retract the respective flaps. Once you've maintained a steady climb, turn on the A/THR and AP1 from the Glare-shield panel.

The autopilot will automatically fly the departure procedure you entered and then transition to the F-PLN (flight-plan) from the Company Route. Once over 10000 ft, switch to 280 KIAS Speed and keep climbing, Around 18000 ft, switch to mach (setting at 0.72) and reduce the V/S to around 1800 fpm.

Once you're over FL260 (26000 ft), reduce your V/S to 1000 fpm and increase mach to 0.78. Then sit back and relax (or go do something else) while the computer automatically takes you to your destination.

'''REST COMING UP SOON'''

=== Custom Emirates Flight from Frankfurt to Munich ===

This flight was requested by Detlef N. (MIA0283), and video tutorials were recorded for different sections of the flight. The videos can be viewed below or in the ''FlightGear Airbus'' YouTube channel. Thank you for watching!

==== Flight Planning ====

{{#ev:youtube|R66q_10dwKw|480|auto|Part 1: Flight Planning}}

==== Manual Start-up ====

{{#ev:youtube|8TI14RJDn2k|480|auto|Part 2: Manual Start-up}}

==== Take-off and Climb ====

{{#ev:youtube|IpkdhebC4-o|480|auto|Part 3: Take-off and Climb}}

''NOTE: Cruise skipped due to the fact that it may be '''boring'''''...

==== Descent and Autoland ====

{{#ev:youtube|NeX3samzrqU|480|auto|Part 4: Descent and Autoland}}

== Liveries ==
The Airbus A330-200 series have liveries for each variant (203, 223 an 243) and are managed by Chris Mueffelmann. Please let us know if you're creating a livery by changing the status on the livery below so that duplicates are avoided.

=== Airbus A330-203 operators ===
'''''All liveries complete!'''''
{|
| valign="top" |
* Afriqiyah Airways - '''COMPLETE'''
* Air Algérie - '''COMPLETE'''
* Air Europa - '''COMPLETE'''
* Air France - '''COMPLETE'''
* EVA Air - '''COMPLETE'''
* EVA Air (Hello Kitty) - '''COMPLETE'''
* Jet Airways - '''COMPLETE'''
| valign="top" |
* Jetstar Airways - '''COMPLETE'''
* KLM Royal Dutch Airline - '''COMPLETE'''
* Qantas Airways - '''COMPLETE'''
* Qantas Airways ('''one'''world) - '''DEVEL''' (''muffinman'')
* Qatar Airways - '''COMPLETE'''
* TAM Linhas Aereas - '''COMPLETE'''
* Turkish - '''COMPLETE'''
|}

=== Airbus A330-223 operators ===
'''''All liveries complete!'''''
{|
| valign="top" |
* Air Berlin - '''COMPLETE'''
* Air Caraibes - '''COMPLETE'''
* Air Greenland - '''COMPLETE'''
* Air India - '''COMPLETE'''
* Atlasjet - '''COMPLETE'''
* Brussels Airlines - '''COMPLETE'''
* China Southern - '''COMPLETE'''
* Delta Airlines - '''COMPLETE'''
* Edelweiss Air - '''COMPLETE'''
| valign="top" |
* Eurofly - '''COMPLETE'''
* Hong Kong Airlines - '''COMPLETE'''
* Korean Air - '''COMPLETE'''
* Malaysia Airlines - '''COMPLETE'''
* Royal Jordanian - '''COMPLETE'''
* Swiss International Air Lines - '''COMPLETE'''
* TAM Linhas Aereas- '''COMPLETE'''
* TAP Portugal - '''COMPLETE'''
* Vietnam Airlines - '''COMPLETE'''
|}

===Airbus A330-243 operators===
{|
| valign="top" |
* Aeroflot - '''COMPLETE'''
* Air China - '''COMPLETE'''
* Air China (Star Alliance) - '''COMPLETE'''
* Air Europa - '''COMPLETE'''
* Air Nigeria - '''DEVEL''' (''Bravo123'')
* Air Transat - '''COMPLETE'''
* Avianca - '''COMPLETE'''
* China Eastern - '''COMPLETE'''
* Corsairfly - '''COMPLETE'''
* Cyprus Airways - '''COMPLETE'''
* Egyptair - '''COMPLETE'''
* Emirates - '''COMPLETE'''
* Etihad - '''COMPLETE'''
* Fiji Airways - '''COMPLETE'''
* Garuda Indonesia - '''COMPLETE'''
* Gulf Air - '''COMPLETE'''
* Hainan Airlines - '''COMPLETE'''
| valign="top" |
* Hawaiian Air - '''COMPLETE'''
* Hi Fly - '''COMPLETE'''
* Hong Kong Airlines - '''COMPLETE'''
* Jet Airways - '''COMPLETE'''
* Middle East Airlines - '''COMPLETE'''
* Monarch Airlines - '''COMPLETE'''
* Oman Air - '''DEVEL''' (''connect'')
* Sichuan Airlines - '''COMPLETE'''
* South African Airways - '''COMPLETE'''
* SriLankan Airlines - '''COMPLETE'''
* Thomas Cook Airlines - '''COMPLETE'''
* Thomas Cook Scandinavia - '''COMPLETE'''
* US Airways - '''DEVEL''' (''Omega95'')
* Virgin Australia - '''COMPLETE'''
* XL Airways
* Yemenia Airlines - '''COMPLETE'''
|}

==Default Flight Database==

The Default Flight Database contains [[Merlion Virtual Airlines]] Airbus A330-200 Routes. This database can be used by anyone, whether he/she is a merlion pilot or not. The example flight above explains how to use routes from the Flight Database.

If you fly for a different Virtual Airline which uses the Airbus A330-200 (203/223/243), please contact your staff for the flight database.

* Current Active Database - '''MIA_Data_v3.1''' ''(27MAY-26AUG)''
* Previous (Standby) Database - '''MIA_Data_v3.0''' (DOES NOT EXIST YET)

===Available Routes Tables===

''The following routes are complete and available.''

{| class="wikitable sortable"
|-
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)
|-
| MIA131 || WSSS || YBBN || S-QDAZ || MIASINBNE1, MIASINBNE2
|-
| MIA132 || YBBN || NZAA || S-QDAZ || MIABNEAKL1
|-
| MIA133 || NZAA || YBBN || S-QDAZ || MIAAKLBNE1
|-
| MIA134 || YBBN || WSSS || S-QDAZ || MIABNESIN1, MIABNESIN2
|-
| MIA135 || WSSS || FAJS || S-QDBZ || MIASINJNB1
|-
| MIA136 || FAJS || SBGR || S-QDBZ || MIAJNBGRU1
|-
| MIA137 || SBGR || FAJS || S-QDBZ || MIAGRUJNB1
|-
| MIA138 || FAJS || WSSS || S-QDBZ || MIAJNBSIN1
|-
| MIA139 || WSSS || RJGG || S-QDCZ || MIASINNGO1
|-
| MIA140 || RJGG || KLAX || S-QDCZ || MIANGOLAX1
|-
| MIA141 || KLAX || RJGG || S-QDCZ || MIALAXNGO1
|-
| MIA142 || RJGG || WSSS || S-QDCZ || MIANGOSIN1, MIANGOSIN2
|}

The Rest of Merlion's Flight Database is available for merlion pilots from the website Downloads section.

==Important developments remaining==

''We have completed the highest priority developments on the list, if you'd like us to do anything for the aircraft, please make a note below.''

==Important Recently Completed Developments==

* Modeled the Rolls Royce Trent 772B-60 Engines for the A330-243
* Animated Flaps, Speed-brakes and Parking Brake Levers (NOT PICK, ONLY TRANS/ROTATE)
* Animated the Throttle Quadrant (incl. Engine cutoffs - REQUIRED FOR MANUAL START-UP) - ''Manual Start-up is now possible''
* Fixed the '''Blue''' Hydraulic System
* Completed Separate Engine Sounds for the each variant

== External link ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 Development topic]

{{Airbus}}

[[Category:Airliners]]

OpenRadarFeatureWishlist

2013-04-28T16:41:40Z

Mcantsin: /* General */ Dubai (OMDB) error loading tower position

[[OpenRadar| Back to mainpage]]

This page collects the feature proposals for [[OpenRadar]].

== General ==
* (by design) Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10
:(comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]])
::Well this should be fixed. What if multiple controllers controll with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST)
* Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers
:(ww: yes, but as much as I know they use mumble right now... I am looking for a smart way to do this)
* Make it not working at FG's [[KSFO|default airport]] (to guard against heart attacks on trying-to-be-KSFO-police people).
:ww: We are living in a free world of free software. Its like forbidding aircrafts at an airport. I have seen pilots missing all decency and mad ATC guys. We cannot lock them out without creating a closed environment... No, that is not the way it should be done... If someone wants to disturb he still can use aircrafts or the different ATC-models out there...
* (done: SHIFT+F12) The ability to reload the airport without having to restart the whole application. This is while I am developing Routes, it's a pain to constantly have to restart the entire thing.
:(ww: yes, pretty useful, I think about it. Reloading the routes would be enough I think...)
* Wider radar range for CTR controllers (FGCom radio & visibility range)
:ww:I need to validate, but to my current knowledge, FGCOM is restricted on server side and the contact visibility by the MP server. I thought already about a special mode for CTR, that registers OR as MP server (proxy). Then it would get all contacts worldwide. For FGCOM we could add these special frequencies to the list of frequencies that are available everywhere at the FGCOM server.
* (MP data?) Squawk / Transponder codes
:ww: Are not part of the MP protocol => are not transfered to OpenRadar.
* (MP data?) Private message feature
:ww: Is not part of the MP protocol.
* Intercom FGCom frequency call GND to GND to call other ATC's
:ww: Some ATCs are using mumble right now, for this purpose. I keep it in mind. But I don't want to exclude the ATC-models out of the game.
* Controlling multiple airports (CTR controller)
:ww: To be able switch some features from airport to airport (METAR, runways, FGCOM, StdRoutes) I need to rework some parts of the application (relocation of OR multiplayer client to new airport, loading of different METAR, runways, routes etc). It would work like an hopping from airport to airport. Something for future releases, I think.
* (implemented as bi-directional checkbox in rw settings dialog) Enable "contradictory" runway setting. (E.g. The common setting in [http://www.cats.com.kh/siem-reap-airport.php VDSR], - in real life, - [http://www.cats.com.kh/atis.php is rwy 23 for departure and 05 for landing], which seems contradictory but is the commonly used configuration.)
:ww: interesting. How many airports have this setting? I think about a special checkbox in runway settingsdialog.
::mc: Yes, e.g. airports in "rural areas", especially when there are temples, military conflicts (prohibited, danger and restricted areas).
* ATIS recording feature
:ww: Recording and then replay over the ATIS frequency? This might be possible, but FGCOM is a separate application, linked to OR via a simple network protocol. Difficult... Especially as we support many different operating systems and setups.
::mc: Yes. compare with VRC (VatSim Virtual Radar Client), which has a recording option and EuroScope which does generate if from recorded fragments. - Text to speech (Espeak/Festival) integration would be the "tripple-A" feature!1!! ;)
* Give the fullname of a VOR when going over it with the cursor (MLN = Melun, LGL = L'Aigle) as ATC and pilot use also VOR names in real life. (Do the same for Airports and NDB?)
* Direction finder: as we don't have flightplans yet, it would be useful to be able to find the direction from say XXXX to EDDF when sitting as ATC at XXXX so to find the best SID at XXXX. Maybe the search box at the bottom of the radar window could be able to find any apt/navaid point and indicate its distance and heading from the current airport one controls.
* OpenRadar fails for LSZN (Hausen am Albis) with error "SEVERE: Error: could not parse tower position in file sectors.properties for airport LSZN"
:LSZN TWR is +47° 14' 16.86" N +8° 30' 51.51" E, LSZN runway +47° 14' 19" N, +8° 30' 56" E
* Same error for OMDB (Dubai):
:de.knewcleus.openradar.gui.setup.AirportData checkTowerPosition
:SEVERE: Error: could not parse tower position in file sectors.properties for airport OMDB

== Aircraft/Pilot Flag ==
* See assigned flightlevel (according to flightplan)
* (MP data?) Squawk/Transponder Code
* (MP data?) "True" altitude according to local air pressure below transition level and flightlevel according to standard pressure (QNH 1013/2992) above transition level
ww: I have no access to the airpressure at the spot, where the plane is. All I get is the TRUE position of the airplane in world coordinate system. If the MP protocol would deliver both, the true altitude and the FL- pressure dependent altitude, this would be no problem.
* (MP data?) Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN)
* (done: Set in contact dialog, displayed as little headset) Voice, Text ability of Pilot (FGCom)

== METAR ==
* (corrected) Winds below 100 degrees with preceeding 0/00, so that wind directions are read in 3 numbers. (E.g. wind 9@3 is read as "wind zero-zero-niner at tree")
* METAR of nearby airports
* (available via tooltip text of wind, pressure line) Full METAR code

== Messages ==
:ww: Up to now, we are still close to the implementation of ATC-ML, although there are some minor differences. I understand the need to change the following and will make it, but maintenance effort will increase.
* (done) Angles in the ATIS message should also be padded with 0 (see comment on the Winds below 100 deg in previous section)
* (done): The angle of the ILS is confusing as written: <code>active rwy(s) 06 ILS 108.50-62</code>, I'd rather see that: <code>active rwy(s) 06 ILS 108.50 (062)</code>
* (done) FGCOM message should list all frequencies the ATC listens too. Ex: FGCOM 118.700 TWR, 123.87 APP, 117.750 GND
* (done) QNH should be given in inHg and hPa. Ex: QNH 30.12/1020, except if there is a way to tell OpenRadar which unit the ATC wants to give (which is even better).
* (exists: try ESC! )A shortcut should be available to cancel and clear the whole message line

== Radar Map ==
* show more ground detail (data source?)
* separation rings (1000ft in vertical and 500ft in horizontal distance)
* alerts for collision and speed violations
* an alarm for when new aircraft enter the area so that when you are busy doing something else while waiting for someone to come into your area you will be notified
* (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas
* Accurate and up-to-date navigation data. (Some SID/STAR are not being displayed, because the navigation data is incomplete and inaccurate. - [[Talk:Airport data (apt.dat) update|See this thread]] and/or [http://github.com/mcantsin/x-plane-navdata/wiki this proposal].)
:ww: I use the latest apt.dat file from xplane already (format 10.00) if something is missing, you can add the navaids for OR display in the standard route files. The problem for the pilots persist until the FG database is updated/corrected, but even in xplane file, there are some fixes missing)

== Route Editing ==
* (done: syntax <code><addPoint code="AGOLO" point="50.200000,9.676111"/></code> ) Ability to specific locally specific points. Rather than hacking the Apt.dat.tgz file, adding to say nav.xml within folder. Additionally these points should be in the form of existing points notification and searched first before globals
* Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?)
* (done: example: <code>begin="KOAK-RW29"</code>) The ability to reference runway start and end as nav points
* (done: both formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10') ability to specify geographic coordinates in degrees, minutes, seconds and not only in decimal degrees

== Radar Contact handling ==
== FGCom Integration ==
* (Done) Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT. SH: If using FGcom, most of the time there would be no need to use anything but single key presses, so therefore any button would be fine. Remember LShift is the primary key for PTT2. Fn keys?)
:ww: removed CTRL+CLICK, there is a textbutton above the flightstrips now, to toggle neglect
* Add "set PTT button" feature

=== Missing/not working frequencies ===
ww: I have changed from the frequencies delivered by the xplane files to the phonebook of fgcom. Both did mismatch. Now they are equal and (if you don't use an older Fgcom phonebook) you should be able to connect to all displayed frequencies.
BUT: this does not mean, that all frequencies are there. The frequencies should be maintained by the FGCOM team, as I am only a client. I will update the phonebook when I notice it has been updated.

* 118.10 seems not to work at LSZH TWR. - Maybe there is a collision with the frequency of another airport?
* LSZH_DEL missing Delivery frequency 121.920
* LSZH_GND missing APRON frequencies 121.850
* LSZH_APP missing Approach frequencies 118.0, 120.750, 119.7
* LSZH_DEP missing Departure frequency 125.950

== ATC Coordination ==
* coordinate multiple instances of OpenRadar using a protocol a la VatSim (ww: this will work only for OpenRadar instances, not to ATC-ML, ATC-TOWER etc...)
* (mp data) see what frequencies othe ATC's are using
:ww: I transmit the first frequency via FGCOM protocol, but do not display it yet, because the FG frequencies are set to a fix value.
* Hand-off feature
:* (mp data) See to which frequency the Pilot is connected to (com1 & com2)
::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background)
:* "owning" and aircraft according to the flight strip
:* See on the map what regions are "controlled" by who (dark grey if an area is controlled, so the ATC knows to whom he can do the handoff)
:* (mp data) Assigning squawk code to the flightstrip
::ww:Squawk codes are not transmitted via MP protocol.
* See & edit the flightplan
::ww: Suggest central registration for this.

== Missing/incomplete FG MP protocol data ==
* '''Squawk code'''
* '''Active''', tuned in '''frequency''' (COM1/COM2)
* '''local, airpressure dependent, altitude''', additional to the true altitude (as displayed in the airplane to show the FL above transition alt)
* the '''tuned-in COM frequencies''', there is one for COM1, but it is not implemented, it delivers no data
[[Category:OpenRadar|FeatureWishlist]]
* MP Chat Unicode support
* MP Chat private message support
* ?ATC extensions? (extensions for ATC MP partners)
:* STRING: list of contacts that are controlled by the ATC
:* STRING: xml messages, like handovers, flightplan transfer

OpenRadarKnownIssues

2013-04-27T21:04:33Z

Mcantsin: /* (Unknown) Issues */ error in left hand holding patterns

[[OpenRadar| Back to mainpage]]

This is more or less the help page of [[OpenRadar]]. If you don't find answers here, at the install page or in the guide, please ask in the [http://www.flightgear.org/forums/viewtopic.php?f=68&t=18263 Forum]!

== FAQ ==
* '''FGCom setup''': [[OpenRadarDownload|See installation page]]!
* '''How can I contact the developer?''': Send me mails from the fg forum.
* '''ATIS wind direction differs from METAR''': Yes, spoken is MAGNETIC, written is TRUE. ATIS information always respects the magnetic declination, in OR as reported by US geological society.

== Known Issues ==
* '''I can't see all 24 runways on my netbook, there is no scrollbar''' Sorry guys. but we need space. There is so much to display and tell that you should really consider to use a wider screen! Our target platform is a modern wide screen monitor. If you have two, the better: You can run a flightgear instance with a "camera aircraft" on the other and you add a nice view for ground operations...

* '''It is slow!!!''' If you download new shapefiles for an airport in Europe, you may suffer a really bad performance. Underlying reason: For some weeks the shape file download has been delivering the data for Europe as a whole. So there are many more bytes to download, to load at startup and to move, when you try to move the map. The maintainers of the shape file database know and care about it.
:'''Fixed''' at Landcode DB: Please delete the slow airport from sectors directory and download it again.

* '''Unsupported major.minor version x.y''': Your installed Java is too old. Please install at least Java 6

* '''METAR support for small airports''' METAR is available only for big airports. => add property metarSource into data/(airportCode)/sector.properties file and set it to a bigger airport with METAR nearby!
example: metarSource=LFSB

* '''MP Map shows airplane symbol''' This is because the Model "OpenRadar" is not recognized as ATC. Status: Changed in coding. Next rebuild of multiplayer map servers will show it correctly. This one is already updated: http://mpmap02.flightgear.org/

== (Unknown) Issues ==
* '''Left hand holding'''. The left handed holding patterns are drawn with two supplement lines. - I guess this is a rendering bug...
e.g. <loop navpoint="LBU" inboundHeading="177" length="5" arrows="both" right="false" minHeight="5000"/>

[[Category:OpenRadar|KnownIssues]]

OpenRadarFeatureWishlist

2013-04-09T11:02:31Z

Mcantsin: /* General */

[[OpenRadar| Back to mainpage]]

This page collects the feature proposals for [[OpenRadar]].

== General ==
* (by design) Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10
:(comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]])
::Well this should be fixed. What if multiple controllers controll with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST)
* Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers
:(ww: yes, but as much as I know they use mumble right now... I am looking for a smart way to do this)
* Make it not working at FG's [[KSFO|default airport]] (to guard against heart attacks on trying-to-be-KSFO-police people).
:ww: We are living in a free world of free software. Its like forbidding aircrafts at an airport. I have seen pilots missing all decency and mad ATC guys. We cannot lock them out without creating a closed environment... No, that is not the way it should be done... If someone wants to disturb he still can use aircrafts or the different ATC-models out there...
* (done: SHIFT+F12) The ability to reload the airport without having to restart the whole application. This is while I am developing Routes, it's a pain to constantly have to restart the entire thing.
:(ww: yes, pretty useful, I think about it. Reloading the routes would be enough I think...)
* Wider radar range for CTR controllers (FGCom radio & visibility range)
:ww:I need to validate, but to my current knowledge, FGCOM is restricted on server side and the contact visibility by the MP server. I thought already about a special mode for CTR, that registers OR as MP server (proxy). Then it would get all contacts worldwide. For FGCOM we could add these special frequencies to the list of frequencies that are available everywhere at the FGCOM server.
* (MP data?) Squawk / Transponder codes
:ww: Are not part of the MP protocol => are not transfered to OpenRadar.
* (MP data?) Private message feature
:ww: Is not part of the MP protocol.
* Intercom FGCom frequency call GND to GND to call other ATC's
:ww: Some ATCs are using mumble right now, for this purpose. I keep it in mind. But I don't want to exclude the ATC-models out of the game.
* Controlling multiple airports (CTR controller)
:ww: To be able switch some features from airport to airport (METAR, runways, FGCOM, StdRoutes) I need to rework some parts of the application (relocation of OR multiplayer client to new airport, loading of different METAR, runways, routes etc). It would work like an hopping from airport to airport. Something for future releases, I think.
* (implemented as bi-directional checkbox in rw settings dialog) Enable "contradictory" runway setting. (E.g. The common setting in [http://www.cats.com.kh/siem-reap-airport.php VDSR], - in real life, - [http://www.cats.com.kh/atis.php is rwy 23 for departure and 05 for landing], which seems contradictory but is the commonly used configuration.)
:ww: interesting. How many airports have this setting? I think about a special checkbox in runway settingsdialog.
::mc: Yes, e.g. airports in "rural areas", especially when there are temples, military conflicts (prohibited, danger and restricted areas).
* ATIS recording feature
:ww: Recording and then replay over the ATIS frequency? This might be possible, but FGCOM is a separate application, linked to OR via a simple network protocol. Difficult... Especially as we support many different operating systems and setups.
::mc: Yes. compare with VRC (VatSim Virtual Radar Client), which has a recording option and EuroScope which does generate if from recorded fragments. - Text to speech (Espeak/Festival) integration would be the "tripple-A" feature!1!! ;)
* Give the fullname of a VOR when going over it with the cursor (MLN = Melun, LGL = L'Aigle) as ATC and pilot use also VOR names in real life. (Do the same for Airports and NDB?)
* Direction finder: as we don't have flightplans yet, it would be useful to be able to find the direction from say XXXX to EDDF when sitting as ATC at XXXX so to find the best SID at XXXX. Maybe the search box at the bottom of the radar window could be able to find any apt/navaid point and indicate its distance and heading from the current airport one controls.
* OpenRadar fails for LSZN (Hausen am Albis) with error "SEVERE: Error: could not parse tower position in file sectors.properties for airport LSZN"
:LSZN TWR is +47° 14' 16.86" N +8° 30' 51.51" E, LSZN runway +47° 14' 19" N, +8° 30' 56" E

== Aircraft/Pilot Flag ==
* See assigned flightlevel (according to flightplan)
* (MP data?) Squawk/Transponder Code
* (MP data?) "True" altitude according to local air pressure below transition level and flightlevel according to standard pressure (QNH 1013/2992) above transition level
ww: I have no access to the airpressure at the spot, where the plane is. All I get is the TRUE position of the airplane in world coordinate system. If the MP protocol would deliver both, the true altitude and the FL- pressure dependent altitude, this would be no problem.
* (MP data?) Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN)
* (done: Set in contact dialog, displayed as little headset) Voice, Text ability of Pilot (FGCom)

== METAR ==
* (corrected) Winds below 100 degrees with preceeding 0/00, so that wind directions are read in 3 numbers. (E.g. wind 9@3 is read as "wind zero-zero-niner at tree")
* METAR of nearby airports
* (available via tooltip text of wind, pressure line) Full METAR code

== Messages ==
:ww: Up to now, we are still close to the implementation of ATC-ML, although there are some minor differences. I understand the need to change the following and will make it, but maintenance effort will increase.
* (done) Angles in the ATIS message should also be padded with 0 (see comment on the Winds below 100 deg in previous section)
* (done): The angle of the ILS is confusing as written: <code>active rwy(s) 06 ILS 108.50-62</code>, I'd rather see that: <code>active rwy(s) 06 ILS 108.50 (062)</code>
* (done) FGCOM message should list all frequencies the ATC listens too. Ex: FGCOM 118.700 TWR, 123.87 APP, 117.750 GND
* (done) QNH should be given in inHg and hPa. Ex: QNH 30.12/1020, except if there is a way to tell OpenRadar which unit the ATC wants to give (which is even better).
* (exists: try ESC! )A shortcut should be available to cancel and clear the whole message line

== Radar Map ==
* show more ground detail (data source?)
* separation rings (1000ft in vertical and 500ft in horizontal distance)
* alerts for collision and speed violations
* an alarm for when new aircraft enter the area so that when you are busy doing something else while waiting for someone to come into your area you will be notified
* (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas
* Accurate and up-to-date navigation data. (Some SID/STAR are not being displayed, because the navigation data is incomplete and inaccurate. - [[Talk:Airport data (apt.dat) update|See this thread]] and/or [http://github.com/mcantsin/x-plane-navdata/wiki this proposal].)
:ww: I use the latest apt.dat file from xplane already (format 10.00) if something is missing, you can add the navaids for OR display in the standard route files. The problem for the pilots persist until the FG database is updated/corrected, but even in xplane file, there are some fixes missing)

== Route Editing ==
* (done: syntax <code><addPoint code="AGOLO" point="50.200000,9.676111"/></code> ) Ability to specific locally specific points. Rather than hacking the Apt.dat.tgz file, adding to say nav.xml within folder. Additionally these points should be in the form of existing points notification and searched first before globals
* Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?)
* (done: example: <code>begin="KOAK-RW29"</code>) The ability to reference runway start and end as nav points
* (done: both formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10') ability to specify geographic coordinates in degrees, minutes, seconds and not only in decimal degrees

== Radar Contact handling ==
== FGCom Integration ==
* (Done) Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT. SH: If using FGcom, most of the time there would be no need to use anything but single key presses, so therefore any button would be fine. Remember LShift is the primary key for PTT2. Fn keys?)
:ww: removed CTRL+CLICK, there is a textbutton above the flightstrips now, to toggle neglect
* Add "set PTT button" feature

=== Missing/not working frequencies ===
ww: I have changed from the frequencies delivered by the xplane files to the phonebook of fgcom. Both did mismatch. Now they are equal and (if you don't use an older Fgcom phonebook) you should be able to connect to all displayed frequencies.
BUT: this does not mean, that all frequencies are there. The frequencies should be maintained by the FGCOM team, as I am only a client. I will update the phonebook when I notice it has been updated.

* 118.10 seems not to work at LSZH TWR. - Maybe there is a collision with the frequency of another airport?
* LSZH_DEL missing Delivery frequency 121.920
* LSZH_GND missing APRON frequencies 121.850
* LSZH_APP missing Approach frequencies 118.0, 120.750, 119.7
* LSZH_DEP missing Departure frequency 125.950

== ATC Coordination ==
* coordinate multiple instances of OpenRadar using a protocol a la VatSim (ww: this will work only for OpenRadar instances, not to ATC-ML, ATC-TOWER etc...)
* (mp data) see what frequencies othe ATC's are using
:ww: I transmit the first frequency via FGCOM protocol, but do not display it yet, because the FG frequencies are set to a fix value.
* Hand-off feature
:* (mp data) See to which frequency the Pilot is connected to (com1 & com2)
::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background)
:* "owning" and aircraft according to the flight strip
:* See on the map what regions are "controlled" by who (dark grey if an area is controlled, so the ATC knows to whom he can do the handoff)
:* (mp data) Assigning squawk code to the flightstrip
::ww:Squawk codes are not transmitted via MP protocol.
* See & edit the flightplan
::ww: Suggest central registration for this.

== Missing/incomplete FG MP protocol data ==
* '''Squawk code'''
* '''Active''', tuned in '''frequency''' (COM1/COM2)
* '''local, airpressure dependent, altitude''', additional to the true altitude (as displayed in the airplane to show the FL above transition alt)
* the '''tuned-in COM frequencies''', there is one for COM1, but it is not implemented, it delivers no data
[[Category:OpenRadar|FeatureWishlist]]
* MP Chat Unicode support
* MP Chat private message support
* ?ATC extensions? (extensions for ATC MP partners)
:* STRING: list of contacts that are controlled by the ATC
:* STRING: xml messages, like handovers, flightplan transfer

OpenRadarFeatureWishlist

2013-04-03T13:02:32Z

Mcantsin: comments answered for ww

Talk:Airport data (apt.dat) update

2013-04-02T18:35:52Z

Mcantsin: /* Independent apt.dat source */

==Independent apt.dat source==
I would like to suggest to use an independent, community based source for apt.dat data, such as [http://github.com/mcantsin/x-plane-navdata/wiki this project on github].
[[User:Mcantsin|Mcantsin]] 01:57, 28 February 2013 (UTC)
:: Then maybe you can explain what is not independent and community based on Robin's data? It's GPL and a new release is around the corner. --[[User:Papillon81|Papillon81]] 11:09, 28 February 2013 (UTC)
::: If you read [http://github.com/mcantsin/x-plane-navdata/wiki the description] you will learn why. [[User:Mcantsin|Mcantsin]] 11:23, 28 February 2013 (UTC)
:::: Hi Luther,
:::: Your GitHub is also maintained by a single maintainer (you), right? So how's that different, other than being a Git repository?
:::: The idea in itself is interesting, but I see lots of issues, just to name a few:
::::* How would you deal with merging back changes that are made to the official data?
::::* Do changes made in your repository get merged in Robin's?
::::* What if your and Robin's data conflict; who is "right"?
::::* What if a new apt.dat format is designed, how will you be able to convert the data to that new format?
:::: When I can choose between two sources of data: one having all kind of infrastructure in place to ensure easy maintenance and dozens of contributors, and one with no infrastructure and just a single commiter, I'd choose for the first option...
:::: [[User:Gijs|Gijs]] 11:45, 28 February 2013 (UTC)
::::: I understand your points, GiJs. But the idea of (officially) releasing *up-to-date* apt.dat data through git(hub) means:
:::::* Having the ability of keeping track (publicly visible) of the changed data through version control.
:::::* Offering the possibility to a group of multiple people to publish "releases", which can be argued and officially announced. (e.g. official "master" tree).
:::::* Offering *anyone* to pull, change and publish his own tree.
:::::* Offering to *anyone* to contribute to the source data directly withouth obstacles.
:::::* Offering *anyone* to pull *any* version of the data, not just the latest one.
:::::* Disposing of the fact that Robin is unresponsive to data correction submissions. (I have waited 11 months to receive a cheap answer to my e-mail to Robin, saying that he is too busy...)

:::::Regarding your questions:
:::::* Who would maintain the "official" master tree
::::: I would be most happy to let the FG dev team name and appoint the individuals forming some sort of "official data" group. - They would be the ones drafting rules for data submissions (format, procedure etc.) in the first place.
:::::* Robin's data
::::: Frankly spoken I don't care about Robin's data any longer, as it is largely out of data and out of accuracy. I wrote my own awk shell script, which converts my navigraph data into apt.dat and that does a wonderful job for my personal use. I don't pull Robin's data any longer...
:::::* "Conflict"
::::: There would not be a "conflict", as Robin's data simply is not accurate any longer and in case of a "official fg data release group" a possible conflict could be argued, then discussed and decided. - Not by one single person that only has a focus on local airports and nav data, but by an international community. And in case of conflict the real life data can simply be adapted. (There are many real life ATC's and Pilots who would deliver this most accurate data to be used in case of a conflict.)
:::::* Conversions
::::: Conversions can simply be made using GNU awk, sql, etc. there are large tools available and this is not an issue yet.

:::::So. - Having the ability of bringing apt.dat to the next generation or remaining dependent to one single, unresponsive maintainer... Make a wise joice.
:::::[[User:Mcantsin|Mcantsin]] 12:44, 28 February 2013 (UTC)
:::::P.S. I don't say that it has to be [http://github.com/mcantsin/x-plane-navdata/wiki this particular project]. What I offer is just a suggestion of thinking about the benefit of using git for maintaining up-to-date and accurate data.

I have to agree with Mcantsin about submissions to Robin: he doesn't acknowledge them nor include those from others,despite his heading. I submitted several Canadian suggestions which I (naively) expected to see in the 2.10 release of FG's nav.dat and fix.dat, but they were not to be found. They were submitted well in advance, so lateness shouldn't be an excuse for them not to be there. As to conflicting about accuracy, most of what I'm finding are misplaced navaids, or those which have not yet made it into the list. As with anything in the scenery, I think an argument about who is 'right' or more accurate would be as senseless as some other arguments I see on FG. I have corrected several NDB poistions, and fixes, which led me off track on a final approach to runway, and after my corrections, that no longer happened, as I test my corrections before submitting them. I would trust that anyone who is submitting corrections or new navaids would at least fly them to ensure they're where they're supposed to be in relation to the function for which they placed there in the first place. I support this effort, as I"m tired of being disappointed with each new release and the same old errors and omissions in navaids and fixes are still there. I would like to encourage the devs to access this database, combine our efforts with those of Robin, allowing us, in some small way, to contribute to the project and generally make flying more enjoyable for everyone. "Never put all your eggs in one basket," might seem to be a good analogy here; if we're going to stubbornly stick to one source (Robin's) I believe we're doing a disservice to the project, and those who use it.
[[User:Trennor|Trennor]] 04:45, 2 April 2013 (UTC)

: Ahem, flightgear is still using the old 8.10 apt.dat format file, thus the outdated data. That does not mean a change in the way apt.dat source is maintained and updated is not a good idea. --[[User:Aep|Aep]] 11:40, 2 April 2013 (UTC)

: To complement what's said by Aep, FlightGear is currently using the .dat files from a long time ago. Simply because FlightGear does/did not support the new format that X-Plane (and Robin) have moved to. Luckily we're catching up fast and scenery with the new format will probably be available this summer. In order to have matching navigational data and scenery, it is important that we update both at the same time (which is why we cannot just update the nav data right now).
: I've spoken to several FlightGear people who sent changes to Robin and all of them were included in the latest files from http://data.x-plane.com Please check those files to see if your changes are in (make sure you download "Latest data"). It's not fair to blame Robin for something he has no control over.
: Needless to say that we cannot "combine our efforts" maintaining two independent databases.
: [[User:Gijs|Gijs]] 16:16, 2 April 2013 (UTC)

::::::Well. I hereby would like to express my deepest sympathy and condolences for Robin's feelings. - But let's focus on how to frame the publishing of accurate and up-to-date navigation data for that flightsimulators can be used for training of (real life) pilots and ATC's. 
::::::So I kindly & heartily invite you to discuss and draft a **true** GPL based navigation data source. [[User:Mcantsin|Mcantsin]] 18:35, 2 April 2013 (UTC)

OpenRadarKnownIssues

2013-04-02T08:38:59Z

Mcantsin: typo

[[OpenRadar| Back to mainpage]]

This is more or less the help page of [[OpenRadar]]. If you don't find answers here, at the install page or in the guide, please ask in the [http://www.flightgear.org/forums/viewtopic.php?f=68&t=18263 Forum]!

== FAQ ==
* '''FGCom setup''': [[OpenRadarDownload|See installation page]]!
* '''How can I contact the developer?''': Send me mails from the fg forum.
* '''ATIS wind direction differs from METAR''': Yes, spoken is MAGNETIC, written is TRUE. ATIS information always respects the magnetic declination, in OR as reported by US geological society.

== Known Issues ==
* '''I can't see all 24 runways on my netbook, there is no scrollbar''' Sorry guys. but we need space. There is so much to display and tell that you should really consider to use a wider screen! Our target platform is a modern wide screen monitor. If you have two, the better: You can run a flightgear instance with a "camera aircraft" on the other and you add a nice view for ground operations...

* '''It is slow!!!''' If you download new shapefiles for an airport in Europe, you may suffer a really bad performance. Underlying reason: For some weeks the shape file download has been delivering the data for Europe as a whole. So there are many more bytes to download, to load at startup and to move, when you try to move the map. The maintainers of the shape file database know and care about it.
:'''Fixed''' at Landcode DB: Please delete the slow airport from sectors directory and download it again.

* '''Unsupported major.minor version x.y''': Your installed Java is too old. Please install at least Java 6

* '''METAR support for small airports''' METAR is available only for big airports. => add property metarSource into data/(airportCode)/sector.properties file and set it to a bigger airport with METAR nearby!
example: metarSource=LFSB

* '''MP Map shows airplane symbol''' This is because the Model "OpenRadar" is not recognized as ATC. Status: Changed in coding. Next rebuild of multiplayer map servers will show it correctly. This one is already updated: http://mpmap02.flightgear.org/

== (Unknown) Issues ==

* Drawing a line, in a SID/STAR file, from a point into the direction of 180 or 360 degrees, causes to draw a bizzarre line. 
e.g. <line start="7.8NM234@ZUE" angle="180" length="5.3" text="360°"/>

[[Category:OpenRadar|KnownIssues]]

OpenRadarKnownIssues

2013-04-02T08:38:38Z

Mcantsin: added minor (unknown?) bug

[[OpenRadar| Back to mainpage]]

This is more or less the help page of [[OpenRadar]]. If you don't find answers here, at the install page or in the guide, please ask in the [http://www.flightgear.org/forums/viewtopic.php?f=68&t=18263 Forum]!

== FAQ ==
* '''FGCom setup''': [[OpenRadarDownload|See installation page]]!
* '''How can I contact the developer?''': Send me mails from the fg forum.
* '''ATIS wind direction differs from METAR''': Yes, spoken is MAGNETIC, written is TRUE. ATIS information always respects the magnetic declination, in OR as reported by US geological society.

== Known Issues ==
* '''I can't see all 24 runways on my netbook, there is no scrollbar''' Sorry guys. but we need space. There is so much to display and tell that you should really consider to use a wider screen! Our target platform is a modern wide screen monitor. If you have two, the better: You can run a flightgear instance with a "camera aircraft" on the other and you add a nice view for ground operations...

* '''It is slow!!!''' If you download new shapefiles for an airport in Europe, you may suffer a really bad performance. Underlying reason: For some weeks the shape file download has been delivering the data for Europe as a whole. So there are many more bytes to download, to load at startup and to move, when you try to move the map. The maintainers of the shape file database know and care about it.
:'''Fixed''' at Landcode DB: Please delete the slow airport from sectors directory and download it again.

* '''Unsupported major.minor version x.y''': Your installed Java is too old. Please install at least Java 6

* '''METAR support for small airports''' METAR is available only for big airports. => add property metarSource into data/(airportCode)/sector.properties file and set it to a bigger airport with METAR nearby!
example: metarSource=LFSB

* '''MP Map shows airplane symbol''' This is because the Model "OpenRadar" is not recognized as ATC. Status: Changed in coding. Next rebuild of multiplayer map servers will show it correctly. This one is already updated: http://mpmap02.flightgear.org/

== (Unknown) Issues ==

* Drawing a line, in a SID/STAR file, from a point into the direction of 180 or 360 degrees, causes to draw a bizzarre line. 
e.g. <line start="7.8NM234@ZUE" angle="181" length="5.3" text="360°"/>

[[Category:OpenRadar|KnownIssues]]

OpenRadarFeatureWishlist

2013-04-02T04:14:26Z

Mcantsin: /* Radar Map */ accurate navigation data

User:Mcantsin

2013-04-01T21:43:09Z

Mcantsin:

{{User
|name = Luther Blissett
|location = world
|interests = ATC, navigation data, radar client, GNU/Linux, copyleft
|callsign = ops
|favourite = Falcon 7X
}}

== Why I am here ==
As an GNU/Linux and Aviation enthousiast I like the approach and the way flightgear is being built and developed. As an ATC controller for [http://vatsim.net VatSim], which is a very professional and hierarchical organisation, I control areas such as South-Eastern Asia (ASEA FSS), [http://vatthd.net/ Thailand (VTBB FIR)], [http://vd.vatsea.net/ Cambodia (VDPP FIR)] etc., produced charts and training material for virtual controllers and virtual pilots. Due to the [http://forums.vatsim.net/viewtopic.php?f=7&t=25284&start=60 caginess of the VatSim community] towards Free Software, especially GNU/Linux, I am willing to invest my spare time to bring ATC services for FlightGear further and am especially looking forward into the development of [[OpenRadar]]. - So I might be new to the FlightGear community, but am nevertheless willing to provide professional knowledge and ideas.

== Contact ==
E-mail: open.pop.star@gmail.com 
Twitter: [http://twitter.com/openpopstar openpopstar] 
IRC: mcantsin @de.irc.flightgear.org

Talk:Virtual Air Traffic Organization

2013-04-01T12:38:49Z

Mcantsin: Created page with "Where is the difference between [http://vatofg.x10.mx vATO] and [http://www.flightgearvao.org/ FGvao]? ~~~~"

Where is the difference between [http://vatofg.x10.mx vATO] and [http://www.flightgearvao.org/ FGvao]? [[User:Mcantsin|Mcantsin]] 12:38, 1 April 2013 (UTC)

OpenRadarFeatureWishlist

2013-04-01T03:07:28Z

Mcantsin: /* Radar Map */

OpenRadarFeatureWishlist

2013-04-01T03:05:33Z

Mcantsin: /* General */

OpenRadarFeatureWishlist

2013-04-01T02:56:03Z

Mcantsin:

OpenRadarFeatureWishlist

2013-04-01T01:31:34Z

Mcantsin:

OpenRadarFeatureWishlist

2013-03-31T21:40:58Z

Mcantsin: /* RadarMap */

OpenRadarFeatureWishlist

2013-03-31T21:38:41Z

Mcantsin: /* General */

OpenRadarFeatureWishlist

2013-03-31T21:35:35Z

Mcantsin: /* ATC Coordination */

OpenRadarFeatureWishlist

2013-03-31T21:28:38Z

Mcantsin: /* FGCom Integration */ missing frequencies

User:Mcantsin

2013-03-31T20:55:31Z

Mcantsin: added IRC address

== Why I am here ==
As an GNU/Linux and Aviation enthousiast I like the approach and the way flightgear is being built and developed. As an ATC controller for [http://vatsim.net VatSim], which is a very professional and hierarchical organisation, I control areas such as South-Eastern Asia (ASEA FSS), [http://vatthd.net/ Thailand (VTBB FIR)], [http://vd.vatsea.net/ Cambodia (VDPP FIR)] etc., produced charts and training material for virtual controllers and virtual pilots. Due to the [http://forums.vatsim.net/viewtopic.php?f=7&t=25284&start=60 caginess of the VatSim community] towards Free Software, especially GNU/Linux, I am willing to invest my spare time to bring ATC services for FlightGear further and am especially looking forward into the development of [[OpenRadar]]. - So I might be new to the FlightGear community, but am nevertheless willing to provide professional knowledge and ideas.

== Contact ==
E-mail: open.pop.star@gmail.com 
Twitter: [http://twitter.com/openpopstar openpopstar] 
IRC: mcantsin @de.irc.flightgear.org

User:Mcantsin

2013-03-31T20:27:33Z

Mcantsin: about

Talk:OpenRadarFeatureWishlist

2013-03-31T20:05:25Z

Mcantsin: Created page with "I love the idea to, - finally, - get an ATC radar client that runs on GNU/Linux. - That is great news! E.g. Radar Clients for VatSim, such as [http://www1.metacraft.com/VRC/ V..."

I love the idea to, - finally, - get an ATC radar client that runs on GNU/Linux. - That is great news!
E.g. Radar Clients for VatSim, such as [http://www1.metacraft.com/VRC/ VRC] and [http://www.euroscope.hu/ Euroscope], which are proprietary, have nice features but do not run well on GNU/Linux. I would love to see some of these features to be included into OpenRadar, as it would atract some controllers to join FG. Therefore I propose to "tidy up" the feature request page in the first place to see what is already done, what should be done and what should be discussed.
[[User:Mcantsin|Mcantsin]] 20:05, 31 March 2013 (UTC)

Talk:Airport data (apt.dat) update

2013-02-28T13:00:07Z

Mcantsin:

Talk:Airport data (apt.dat) update

2013-02-28T12:49:46Z

Mcantsin: /* Independent apt.dat source */

Talk:Airport data (apt.dat) update

2013-02-28T12:44:32Z

Mcantsin: /* Independent apt.dat source */

Talk:Airport data (apt.dat) update

2013-02-28T11:23:24Z

Mcantsin: /* Independent apt.dat source */

Talk:Airport data (apt.dat) update

2013-02-28T01:57:41Z

Mcantsin: suggestion