FlightGear wiki - User contributions [en]

Spoken ATC

2020-06-24T18:38:51Z

Rodolfo: /* Comming soon */

{{infobox subsystem
|image = Spoken-ATC-Screenshot.jpg
|name = Spoken ATC
|started = 07/2017
|description = Spoken ATC
|status = Under active development as of 07/2017
|maintainers = {{usr|Rodolfo}}
|developers = Rodolfo (rleibner on the forum)
}}

[[Spoken ATC]] allows the pilot to listen to the directives of the ''Air Traffic Controller''.

The module is not intended to compete with FGComm, Festival or other similar features.
On the contrary, it is meant to substitute them when these are not available (for example due to constrained hardware resources, no Internet connection, etc.)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=312968#p312968
|title = <nowiki> ATC </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Jun 22nd, 2017
|added = Jun 22nd, 2017
|script_version = 0.40
}}</ref>

== Preface ==
'''Typically''', you should tune the ATC-station frequency and make a request by pressing {{key press|<}} key. You may hear something like:


* ''"Charlie X-ray Bravo Echo X-ray , this is Montevideo Carrasco International tower. QNH 1024 or 30 point 24 inches. Join left pattern Runway 1 9 and report."''

So, you enter in the base leg and press {{key press|<}} again:

* ''"Charlie X-ray Bravo Echo X-ray , Wind 1 5 0 degrees, 3 knots. Runway 1 9 cleared to land."''

After landing and while you are braking, you press {{key press|<}} once more:

* ''"Charlie X-ray Bravo Echo X-ray , Exit Runway at first taxiway and contact Ground 121 point 82."''

That is only an example of standard [[ATC phraseology|VFR Phraseology]] that you can expect from '''Spoken ATC'''.

== How to install ==
{{note |This is the latest version, v.2.2.4 (Apr 26, 2019) }}
Download this [[Addons|Addon]] from {{fgaddon source |path=Addons/SpokenATC |text=SourceForge}}. Read the [[FGAddon#Obtaining_aircraft|directions]] as a reference.

Start your FGFS session including <code>--addon=<your local path>/SpokenATC</code> in the command line or in the ''settings'' tab of the launcher.

== How to use it ==
Launch FlighGear (or re-start it) and tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information''),
and press the {{key press|<}} key to transmit your request.

You will hear the ATC's answer according the standard VFR phraseology, depending on your current position, weather and previous messages:
* If you are on ground:
** The code interprets it's a taxi request (if you are far from the runway or you've just landed),
** or a take-off request (if you are on the correct Runway or at his holding point).

* If you are flying:
** The code interprets it's an approach request (if you tunned an APP station),
** or a landing request (if you tunned a TWR station),
** or a departure request (if you tunned a DEP station. and you are climbing after a take-off).

Note that only TWR stations can deliver landing or take-off clearances, and only GND or TWR stations can deliver taxiing ones.

Where there is not a specific GND or APP-DEP freq., TOWER can take their tasks.

If they do exist, TWR will redirect to the specific frequency.

Only at initial contact, the ATC message includes his station name & type, and the current QNH.

APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR).

TWR stations will give instructions to join pattern or make direct final (depending on your position).

== Comming soon ==
Next version (under development now) includes 2 new features:
* User can toggle anytime between Comm1 and Comm2 by pressing {{key press|Alt}}{{key press|<}}
* Can request for a vector to the closest airport by pressing {{key press|Ctrl}}{{key press|Alt}}{{key press|<}}
In addition to that, now you will hear the pilot's voice requesting ATC instructions and their acknowledges.

You can taste (& test) those facilities by replacing the files in your ''<SpokenATC>'' folder with the ones included here:
[https://www.dropbox.com/s/7fhzhzkijdxmovo/beta_SpokenATC.zip?dl=1 next (beta) version].

== Tips ==
=== Heavy airplanes ===
To request a ILS runway, contact Tower using {{key press|Ctrl}}{{key press|<}}.

=== A realistic behavior ===
To achieve realistic behavior, follow a logical sequence of communications, viz.:
* Contact GND (or TWR) prior to taxiing.
* Contact TWR prior to take-off or land.
* Contact DEP (if available) after take-off to leave the CTR.
* Contact APP (if available) prior to enter the CTR.
* etc, etc.

=== On screen voice ===
If the writen messages bother you, when binding (see above) you can call the function as
<syntaxhighlight lang="xml">
<script> <![CDATA[ spoken_atc.speak(n); ]]> </script> </syntaxhighlight>
with '''n''' seconds you want, even 0 meaning no messages at all.

== Phraseology customization ==
You can customize the phraseology by editing the <code>phraseology.xml</code> file.

There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').

=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either <code>"</code> or <code>'</code>.
* Punctuation is meaningfull. }}

=== Substitutions ===
Strings starting by <code>%</code> will call some '''property value'''.
In the example above replace <code>day</code> by <code>% /sim/startup/time-offset-type</code>.

Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.

{{note |
* The called property must be a string.}}

=== Concatenation ===
Strings starting by <code>~</code> will append the sentence with another one.

Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "''

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility.

Better? Fine, but what about the message on the screen?
Include a tag with the pattern <code><nowiki><replace type="string">'''old''':'''new'''</replace></nowiki></code>:
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight>

Besides that, you can call the <code>spoken_atc.say()</code> function at runtime to check your customization.

=== spoken_atc.say() function ===
You can ... [TODO]
<big>And remember this is '''VFR''': heed the instructions of the ATC but '''keep your eyes wide open !'''</big>

== References ==
{{Appendix}}

== Related content ==
=== Wiki articles ===
* [[ATC phraseology]]
* [[Howto:Implementing a simple GCA system]] - Ground Controlled Approaches
* [[Spoken GCA]]

=== Forum topics ===
* [https://forum.flightgear.org/viewtopic.php?f=30&t=32408 Spoken ATC]

[[Category:FlightGear add-ons]]
[[Category:Air Traffic Control]]

Spoken ATC

2020-06-22T15:14:44Z

Rodolfo: /* Comming soon */

{{infobox subsystem
|image = Spoken-ATC-Screenshot.jpg
|name = Spoken ATC
|started = 07/2017
|description = Spoken ATC
|status = Under active development as of 07/2017
|maintainers = {{usr|Rodolfo}}
|developers = Rodolfo (rleibner on the forum)
}}

[[Spoken ATC]] allows the pilot to listen to the directives of the ''Air Traffic Controller''.

The module is not intended to compete with FGComm, Festival or other similar features.
On the contrary, it is meant to substitute them when these are not available (for example due to constrained hardware resources, no Internet connection, etc.)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=312968#p312968
|title = <nowiki> ATC </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Jun 22nd, 2017
|added = Jun 22nd, 2017
|script_version = 0.40
}}</ref>

== Preface ==
'''Typically''', you should tune the ATC-station frequency and make a request by pressing {{key press|<}} key. You may hear something like:


* ''"Charlie X-ray Bravo Echo X-ray , this is Montevideo Carrasco International tower. QNH 1024 or 30 point 24 inches. Join left pattern Runway 1 9 and report."''

So, you enter in the base leg and press {{key press|<}} again:

* ''"Charlie X-ray Bravo Echo X-ray , Wind 1 5 0 degrees, 3 knots. Runway 1 9 cleared to land."''

After landing and while you are braking, you press {{key press|<}} once more:

* ''"Charlie X-ray Bravo Echo X-ray , Exit Runway at first taxiway and contact Ground 121 point 82."''

That is only an example of standard [[ATC phraseology|VFR Phraseology]] that you can expect from '''Spoken ATC'''.

== How to install ==
{{note |This is the latest version, v.2.2.4 (Apr 26, 2019) }}
Download this [[Addons|Addon]] from {{fgaddon source |path=Addons/SpokenATC |text=SourceForge}}. Read the [[FGAddon#Obtaining_aircraft|directions]] as a reference.

Start your FGFS session including <code>--addon=<your local path>/SpokenATC</code> in the command line or in the ''settings'' tab of the launcher.

== How to use it ==
Launch FlighGear (or re-start it) and tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information''),
and press the {{key press|<}} key to transmit your request.

You will hear the ATC's answer according the standard VFR phraseology, depending on your current position, weather and previous messages:
* If you are on ground:
** The code interprets it's a taxi request (if you are far from the runway or you've just landed),
** or a take-off request (if you are on the correct Runway or at his holding point).

* If you are flying:
** The code interprets it's an approach request (if you tunned an APP station),
** or a landing request (if you tunned a TWR station),
** or a departure request (if you tunned a DEP station. and you are climbing after a take-off).

Note that only TWR stations can deliver landing or take-off clearances, and only GND or TWR stations can deliver taxiing ones.

Where there is not a specific GND or APP-DEP freq., TOWER can take their tasks.

If they do exist, TWR will redirect to the specific frequency.

Only at initial contact, the ATC message includes his station name & type, and the current QNH.

APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR).

TWR stations will give instructions to join pattern or make direct final (depending on your position).

== Comming soon ==
Next version (under development now) includes 2 new features:
* User can toggle anytime between Comm1 and Comm2 by pressing {{key press|Alt}}{{key press|<}}
* Can request for a vector to the closest airport by pressing {{key press|Ctrl}}{{key press|Alt}}{{key press|<}}
In addition to that, now you will hear the pilot's voice requesting ATC instructions and their acknowledges.

You can taste (& test) those facilities by replacing the files in your ''<SpokenATC>'' folder with the ones included here:
[https://www.dropbox.com/s/ntdzsfuqam17ihr/beta.zip?dl=1 next (beta) version].

== Tips ==
=== Heavy airplanes ===
To request a ILS runway, contact Tower using {{key press|Ctrl}}{{key press|<}}.

=== A realistic behavior ===
To achieve realistic behavior, follow a logical sequence of communications, viz.:
* Contact GND (or TWR) prior to taxiing.
* Contact TWR prior to take-off or land.
* Contact DEP (if available) after take-off to leave the CTR.
* Contact APP (if available) prior to enter the CTR.
* etc, etc.

=== On screen voice ===
If the writen messages bother you, when binding (see above) you can call the function as
<syntaxhighlight lang="xml">
<script> <![CDATA[ spoken_atc.speak(n); ]]> </script> </syntaxhighlight>
with '''n''' seconds you want, even 0 meaning no messages at all.

== Phraseology customization ==
You can customize the phraseology by editing the <code>phraseology.xml</code> file.

There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').

=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either <code>"</code> or <code>'</code>.
* Punctuation is meaningfull. }}

=== Substitutions ===
Strings starting by <code>%</code> will call some '''property value'''.
In the example above replace <code>day</code> by <code>% /sim/startup/time-offset-type</code>.

Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.

{{note |
* The called property must be a string.}}

=== Concatenation ===
Strings starting by <code>~</code> will append the sentence with another one.

Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "''

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility.

Better? Fine, but what about the message on the screen?
Include a tag with the pattern <code><nowiki><replace type="string">'''old''':'''new'''</replace></nowiki></code>:
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight>

Besides that, you can call the <code>spoken_atc.say()</code> function at runtime to check your customization.

=== spoken_atc.say() function ===
You can ... [TODO]
<big>And remember this is '''VFR''': heed the instructions of the ATC but '''keep your eyes wide open !'''</big>

== References ==
{{Appendix}}

== Related content ==
=== Wiki articles ===
* [[ATC phraseology]]
* [[Howto:Implementing a simple GCA system]] - Ground Controlled Approaches
* [[Spoken GCA]]

=== Forum topics ===
* [https://forum.flightgear.org/viewtopic.php?f=30&t=32408 Spoken ATC]

[[Category:FlightGear add-ons]]
[[Category:Air Traffic Control]]

Spoken ATC

2020-06-22T14:49:09Z

Rodolfo: /* Heavy airplanes */

{{infobox subsystem
|image = Spoken-ATC-Screenshot.jpg
|name = Spoken ATC
|started = 07/2017
|description = Spoken ATC
|status = Under active development as of 07/2017
|maintainers = {{usr|Rodolfo}}
|developers = Rodolfo (rleibner on the forum)
}}

[[Spoken ATC]] allows the pilot to listen to the directives of the ''Air Traffic Controller''.

The module is not intended to compete with FGComm, Festival or other similar features.
On the contrary, it is meant to substitute them when these are not available (for example due to constrained hardware resources, no Internet connection, etc.)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=312968#p312968
|title = <nowiki> ATC </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Jun 22nd, 2017
|added = Jun 22nd, 2017
|script_version = 0.40
}}</ref>

== Preface ==
'''Typically''', you should tune the ATC-station frequency and make a request by pressing {{key press|<}} key. You may hear something like:


* ''"Charlie X-ray Bravo Echo X-ray , this is Montevideo Carrasco International tower. QNH 1024 or 30 point 24 inches. Join left pattern Runway 1 9 and report."''

So, you enter in the base leg and press {{key press|<}} again:

* ''"Charlie X-ray Bravo Echo X-ray , Wind 1 5 0 degrees, 3 knots. Runway 1 9 cleared to land."''

After landing and while you are braking, you press {{key press|<}} once more:

* ''"Charlie X-ray Bravo Echo X-ray , Exit Runway at first taxiway and contact Ground 121 point 82."''

That is only an example of standard [[ATC phraseology|VFR Phraseology]] that you can expect from '''Spoken ATC'''.

== How to install ==
{{note |This is the latest version, v.2.2.4 (Apr 26, 2019) }}
Download this [[Addons|Addon]] from {{fgaddon source |path=Addons/SpokenATC |text=SourceForge}}. Read the [[FGAddon#Obtaining_aircraft|directions]] as a reference.

Start your FGFS session including <code>--addon=<your local path>/SpokenATC</code> in the command line or in the ''settings'' tab of the launcher.

== How to use it ==
Launch FlighGear (or re-start it) and tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information''),
and press the {{key press|<}} key to transmit your request.

You will hear the ATC's answer according the standard VFR phraseology, depending on your current position, weather and previous messages:
* If you are on ground:
** The code interprets it's a taxi request (if you are far from the runway or you've just landed),
** or a take-off request (if you are on the correct Runway or at his holding point).

* If you are flying:
** The code interprets it's an approach request (if you tunned an APP station),
** or a landing request (if you tunned a TWR station),
** or a departure request (if you tunned a DEP station. and you are climbing after a take-off).

Note that only TWR stations can deliver landing or take-off clearances, and only GND or TWR stations can deliver taxiing ones.

Where there is not a specific GND or APP-DEP freq., TOWER can take their tasks.

If they do exist, TWR will redirect to the specific frequency.

Only at initial contact, the ATC message includes his station name & type, and the current QNH.

APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR).

TWR stations will give instructions to join pattern or make direct final (depending on your position).

== Comming soon ==
Next version (under development now) includes 2 new features:
* User can toggle anytime between Comm1 and Comm2 by pressing {{key press|Alt}}{{key press|<}}
* Can request for a vector to the closest airport by pressing {{key press|Ctrl}}{{key press|Alt}}{{key press|<}}

You can taste those facilities by replacing your '''voice.nas''' file with this one:
[https://www.dropbox.com/s/t60csb1pl7nblip/voice.nas?dl=1 next (beta) version]

== Tips ==
=== Heavy airplanes ===
To request a ILS runway, contact Tower using {{key press|Ctrl}}{{key press|<}}.

=== A realistic behavior ===
To achieve realistic behavior, follow a logical sequence of communications, viz.:
* Contact GND (or TWR) prior to taxiing.
* Contact TWR prior to take-off or land.
* Contact DEP (if available) after take-off to leave the CTR.
* Contact APP (if available) prior to enter the CTR.
* etc, etc.

=== On screen voice ===
If the writen messages bother you, when binding (see above) you can call the function as
<syntaxhighlight lang="xml">
<script> <![CDATA[ spoken_atc.speak(n); ]]> </script> </syntaxhighlight>
with '''n''' seconds you want, even 0 meaning no messages at all.

== Phraseology customization ==
You can customize the phraseology by editing the <code>phraseology.xml</code> file.

There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').

=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either <code>"</code> or <code>'</code>.
* Punctuation is meaningfull. }}

=== Substitutions ===
Strings starting by <code>%</code> will call some '''property value'''.
In the example above replace <code>day</code> by <code>% /sim/startup/time-offset-type</code>.

Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.

{{note |
* The called property must be a string.}}

=== Concatenation ===
Strings starting by <code>~</code> will append the sentence with another one.

Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "''

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility.

Better? Fine, but what about the message on the screen?
Include a tag with the pattern <code><nowiki><replace type="string">'''old''':'''new'''</replace></nowiki></code>:
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight>

Besides that, you can call the <code>spoken_atc.say()</code> function at runtime to check your customization.

=== spoken_atc.say() function ===
You can ... [TODO]
<big>And remember this is '''VFR''': heed the instructions of the ATC but '''keep your eyes wide open !'''</big>

== References ==
{{Appendix}}

== Related content ==
=== Wiki articles ===
* [[ATC phraseology]]
* [[Howto:Implementing a simple GCA system]] - Ground Controlled Approaches
* [[Spoken GCA]]

=== Forum topics ===
* [https://forum.flightgear.org/viewtopic.php?f=30&t=32408 Spoken ATC]

[[Category:FlightGear add-ons]]
[[Category:Air Traffic Control]]

Oscilloscope addon

2020-06-15T19:28:03Z

Rodolfo:

[[File:Oscilloscope.png|thumb|This screenshot shows the usual c172p "magnetos checking" Channel 1 (yellow) is '''rpm''' (100 rpm / div).Channel 2 (mauve) is '''magnetos''' (1 / div).Time sweep is 200 ms / div.<ref>{{cite web |url = https://forum.flightgear.org/viewtopic.php?p=325929#p325929 |title = <nowiki> Re: Plot2D and graph helpers </nowiki> |author = <nowiki> rleibner </nowiki> |date = Jan 6th, 2018 |added = Jan 6th, 2018 |script_version = 0.36 }}</ref>]]

This '''oscilloscope''' was created as an example of the use of 3 helpers included in the addon:
* '''skinnable.nas''' to create Canvas GUI dialogs including multiple clickable layers.
* '''graph.nas''' to create various types of Canvas instruments.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=325332#p325332
|title = <nowiki> Re: Spoken GCA </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Dec 27th, 2017
}}</ref>
* '''plot2D.nas''' the very basic Canvas helpers.
But apart from that, the '''oscilloscope''' itself may be an useful tool for developers and coders. Although I do not know any aircraft that has this instrument in its panel, the on-board engineer will eventually appreciate having it on hand at some point.
= Background =
{{cquote|I was just thinking today that it might be cool to have a built in grapher for simple / quick graphing needs.
With the property system it would be trivial to pick an arbitrary property from the property tree and graph it over time -- superimposed on top of everything else.
Things get a bit trickier if you want to control scaling, how much time history get's graphed, multiple values, etc., but even graphing a single value (or maybe just two values) over time could be of some use.
I thought I'd toss this out there in case someone thought it was worth while enough to tackle.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg03651.html |title=idea ... (?)|author=Curtis Olson |date=Fri, 08 Mar 2002 07:43:35 -0800}}</ref>|Curtis Olson}}

= How to install =
{{note | This is the latest version (Jan 30, 2018) 
}}
If your FGFS version accepts [[Addons]], you can download this feature from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/Oscilloscope/ Addons Repository]. Download all the 11 files into the directory of your choice.
Launch FlightGear including --addon argument, eg.:
:::<pre style="color: darkgreen"> fgfs <usual args> --addon=/path/to/fgaddon/Oscilloscope</pre>{{note | From version 2017.4.0, the FG launcher accepts the ''--addon'' option in his ''Settings/Additional Settings'' tab. 
}}Otherwise, you can install it as a submodule. Contact the author for further instructions.

= How to use =
== Manual mode ==
Just pressing the {{key press|o}} key the oscilloscope window appears:
[[File:Oscilloscope (default skin).png|center]] Clicking the {{key press| ? }} button you'll have a basic help about ''clickable areas'' and ''readings''. (click {{key press| ? }} again to close help)

=== Connecting Channel Sources ===
[[File:Source dialog.png|right|Channel Source input dialog.]]
Click any BNC connector (Channel 1 or Channel 2) to open the input dialog. 
Enter a valid source as:
* a Numeric or boolean Property address
:: eg.: ''/position/altitude-agl-ft''
* a Numeric Nasal expression
:: eg.: ''getprop("/engines/engine/rpm") /100 ;'' (do not forget the {{key press|;}})
:: eg.: ''0 ;'' (only useful to adjust Offset)
:: eg.: ''5+4*math.sin(D2R*int(100*systime())) ;''
Since the oscilloscope's time is the simulated one, simulation must not be paused in order to see the resulted plottings. 
The reading window above the connector will display the current source value.
=== Adjusting Channel Gain and Offset ===
Clicking the Gain knobs (upper/lower half) will increase/decrease the Channel's Gain. 
The reading window below the knob will display the current gain (units/div). 
The Offset knobs respond in a similar way.
=== Adjusting Timebase ===
Proceed in the same way with the Timebase knob. The reading window below the knob will display the current sweep speed (secs/div).

=== One Shot store ===
Clicking this button will erase the screen and prepare Channel 2 to act as trigger. 
Channel 2 must be an Integer or Boolean property. Once its value changes, a single sweep is triggered and the screen freezes. 
Click this button again in order to return to the default continuous sweeps.
== Script mode ==
Instead of launching the oscilloscope with the {{key press|o}} key and clicking buttons and knobs, it is possible to instantiate the instrument from a Nasal script. 
Open the Nasal Console (or the REPL interpreter if you prefer) and execute these lines:
<syntaxhighlight lang="nasal">var Osc = oscilloscope.show.new();
var myFunc = func {return 10+4*math.sin(D2R*int(100*systime()));};
Osc.setTimeBase(0.2);
Osc.setChannelInput(2,'/controls/engines/engine/magnetos');
Osc.setChannelInput(1, myFunc);
Osc.setGain(channel:1, gain:2);
Osc.setGain(channel:2, gain:2);
</syntaxhighlight>
Please note that buttons and knobs are still reacting to manual clickings. 

You can explore other nasal instructions like:
<syntaxhighlight lang="nasal">
Osc.setChannelInput(2, func {return 5.5;});
Osc.setChannelInput(1, 'var alt = getprop("/position/altitude-ft"); return alt/10;');
</syntaxhighlight>
= Behind the scene =

= Related =
{{Appendix}}

Spoken ATC

2020-06-04T19:00:06Z

Rodolfo:

{{infobox subsystem
|image = Spoken-ATC-Screenshot.jpg
|name = Spoken ATC
|started = 07/2017
|description = Spoken ATC
|status = Under active development as of 07/2017
|maintainers = {{usr|Rodolfo}}
|developers = Rodolfo (rleibner on the forum)
}}

[[Spoken ATC]] allows the pilot to listen to the directives of the ''Air Traffic Controller''.

The module is not intended to compete with FGComm, Festival or other similar features.
On the contrary, it is meant to substitute them when these are not available (for example due to constrained hardware resources, no Internet connection, etc.)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=312968#p312968
|title = <nowiki> ATC </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Jun 22nd, 2017
|added = Jun 22nd, 2017
|script_version = 0.40
}}</ref>

== Preface ==
'''Typically''', you should tune the ATC-station frequency and make a request by pressing {{key press|<}} key. You may hear something like:


* ''"Charlie X-ray Bravo Echo X-ray , this is Montevideo Carrasco International tower. QNH 1024 or 30 point 24 inches. Join left pattern Runway 1 9 and report."''

So, you enter in the base leg and press {{key press|<}} again:

* ''"Charlie X-ray Bravo Echo X-ray , Wind 1 5 0 degrees, 3 knots. Runway 1 9 cleared to land."''

After landing and while you are braking, you press {{key press|<}} once more:

* ''"Charlie X-ray Bravo Echo X-ray , Exit Runway at first taxiway and contact Ground 121 point 82."''

That is only an example of standard [[ATC phraseology|VFR Phraseology]] that you can expect from '''Spoken ATC'''.

== How to install ==
{{note |This is the latest version, v.2.2.4 (Apr 26, 2019) }}
Download this [[Addons|Addon]] from {{fgaddon source |path=Addons/SpokenATC |text=SourceForge}}. Read the [[FGAddon#Obtaining_aircraft|directions]] as a reference.

Start your FGFS session including <code>--addon=<your local path>/SpokenATC</code> in the command line or in the ''settings'' tab of the launcher.

== How to use it ==
Launch FlighGear (or re-start it) and tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information''),
and press the {{key press|<}} key to transmit your request.

You will hear the ATC's answer according the standard VFR phraseology, depending on your current position, weather and previous messages:
* If you are on ground:
** The code interprets it's a taxi request (if you are far from the runway or you've just landed),
** or a take-off request (if you are on the correct Runway or at his holding point).

* If you are flying:
** The code interprets it's an approach request (if you tunned an APP station),
** or a landing request (if you tunned a TWR station),
** or a departure request (if you tunned a DEP station. and you are climbing after a take-off).

Note that only TWR stations can deliver landing or take-off clearances, and only GND or TWR stations can deliver taxiing ones.

Where there is not a specific GND or APP-DEP freq., TOWER can take their tasks.

If they do exist, TWR will redirect to the specific frequency.

Only at initial contact, the ATC message includes his station name & type, and the current QNH.

APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR).

TWR stations will give instructions to join pattern or make direct final (depending on your position).

== Comming soon ==
Next version (under development now) includes 2 new features:
* User can toggle anytime between Comm1 and Comm2 by pressing {{key press|Alt}}{{key press|<}}
* Can request for a vector to the closest airport by pressing {{key press|Ctrl}}{{key press|Alt}}{{key press|<}}

You can taste those facilities by replacing your '''voice.nas''' file with this one:
[https://www.dropbox.com/s/t60csb1pl7nblip/voice.nas?dl=1 next (beta) version]

== Tips ==
=== Heavy airplanes ===
To request a ILS runway, contact ATC using {{key press|Ctrl}}{{key press|<}}.

=== A realistic behavior ===
To achieve realistic behavior, follow a logical sequence of communications, viz.:
* Contact GND (or TWR) prior to taxiing.
* Contact TWR prior to take-off or land.
* Contact DEP (if available) after take-off to leave the CTR.
* Contact APP (if available) prior to enter the CTR.
* etc, etc.

=== On screen voice ===
If the writen messages bother you, when binding (see above) you can call the function as
<syntaxhighlight lang="xml">
<script> <![CDATA[ spoken_atc.speak(n); ]]> </script> </syntaxhighlight>
with '''n''' seconds you want, even 0 meaning no messages at all.

== Phraseology customization ==
You can customize the phraseology by editing the <code>phraseology.xml</code> file.

There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').

=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either <code>"</code> or <code>'</code>.
* Punctuation is meaningfull. }}

=== Substitutions ===
Strings starting by <code>%</code> will call some '''property value'''.
In the example above replace <code>day</code> by <code>% /sim/startup/time-offset-type</code>.

Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.

{{note |
* The called property must be a string.}}

=== Concatenation ===
Strings starting by <code>~</code> will append the sentence with another one.

Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "''

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility.

Better? Fine, but what about the message on the screen?
Include a tag with the pattern <code><nowiki><replace type="string">'''old''':'''new'''</replace></nowiki></code>:
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight>

Besides that, you can call the <code>spoken_atc.say()</code> function at runtime to check your customization.

=== spoken_atc.say() function ===
You can ... [TODO]
<big>And remember this is '''VFR''': heed the instructions of the ATC but '''keep your eyes wide open !'''</big>

== References ==
{{Appendix}}

== Related content ==
=== Wiki articles ===
* [[ATC phraseology]]
* [[Howto:Implementing a simple GCA system]] - Ground Controlled Approaches
* [[Spoken GCA]]

=== Forum topics ===
* [https://forum.flightgear.org/viewtopic.php?f=30&t=32408 Spoken ATC]

[[Category:FlightGear add-ons]]
[[Category:Air Traffic Control]]

Bombardier CRJ700 series

2019-05-21T18:39:06Z

Rodolfo: /* Startup */

{{:{{PAGENAME}}/info}}
[[File:CRJ700-cockpit-night.jpg|The cockpit at night, demonstrating night lighting capabilities|thumb|350px|right]]
[[File:CRJ700-cabin-night.jpg|The interior cabin, also at night|thumb|350px|right]]

The '''Bombardier CRJ700 series''' is a family of 70- to 100- seat regional jet airliners manufactured by Bombardier Aerospace. Its primary competition is the Embraer E-jet series. The family consists of the Bombardier CRJ700, CRJ900, and CRJ1000. The CRJ700 series was developed from the [[Bombardier CRJ-200LR|Bombardier CRJ200]], and remains one of the most popular regional airliner series in the world.

=Variants=

* CRJ700 - the original CRJ700
* CRJ700ER - extended range version
* CRJ700LR - long-range version
* CRJ900 - the first stretch of the airframe
* CRJ900ER - extended range version
* CRJ900LR - long-range version
* CRJ1000 - the final stretch of the airframe
* CRJ1000 EuroLite - low-range/low-cost version targeted at European operators
* CRJ1000ER - extended range version

=Aircraft help=

HTML documentation is included in the Docs/ folder.

==Key commands==

{| class="keytable"
! Key
! Function
|-
! colspan="2" | Speedbrakes/spoilers
|-
| {{key press|Ctrl|B}}
| Cycle speedbrake setting
|-
| {{key press|j}}
| Decrease ground lift dump setting
|-
| {{key press|k}}
| Increase ground lift dump setting
|-
! colspan="2"|Engines
|-
| {{key press|Ctrl|Del}}
| Arm/disarm thrust reversers
|-
| {{key press|Del}}
| Toggle thrust reversers
|-
! colspan="2" | Autopilot
|-
| {{key press|Ctrl|A}}
| Toggle autopilot altitude mode
|-
| {{key press|Ctrl|F}}
|Engage/disengage autopilot
|-
| {{key press|Ctrl|G}}
| Toggle autopilot approach mode
|-
| {{key press|Ctrl|H}}
| Toggle autopilot heading mode
|-
| {{key press|Ctrl|N}}
| Toggle autopilot NAV mode
|-
| {{key press|Ctrl|P}}
| Set autopilot basic pitch mode
|-
| {{key press|Ctrl|W}}
| Set autopilot basic heading/roll mode
|-
| {{key press|F6}}
| Cycle NAV source
|-
! colspan="2" | Tiller/Nose gear steering
|-
| {{key press|q}}
| Steer tiller left
|-
| {{key press|Shift|Q}}
| Set tiller to full left
|-
| {{key press|w}}
| Center tiller
|-
| {{key press|Shift|W}}
| Pop up tiller dialog
|-
| {{key press|e}}
| Steer tiller right
|-
| {{key press|Shift|E}}
| Set tiller to full right
|-
! colspan="2" | Walk view
|-
| {{key press|r}}
| Walk forward toward view
|-
| {{key press|Shift|R}}
| Run forward toward view
|-
| {{key press|f}}
| Walk backwards from view
|-
| {{key press|y}}
| View point down
|-
| {{key press|Y}}
| View point up
|}

==Simplified procedures==
===Startup===
[[File:Start-123.png|thumb|right|CRJ700 Startup (1,2,3)]]
#Battery switch ... on
#Fuel Pumps ... enable
#APU start/stop switch ... on
#Bleed air source ... automatic
#Engine 1 thrust lever ... idle
#Engine 1 start sequence ... initiated
#Engine 2 thrust lever ... idle
#Engine 2 start sequence ... initiated
#APU start/stop switch ... off
#Engine 1 electric generator ... on
#Engine 2 electric generator ... on

===Takeoff===
#Flaps/slats ... 8 or 20
#Landing lights ... on
#Engine thrust modes ... TO/GA

===Climb and cruise===
#Engine thrust modes ... climb
Nominal cruise speed Mach 0.78 (0.80 for CRJ900)

===Approach and landing===
Remain below 250 knots below 10,000 feet at all times
#Thrust reversers ... armed
#Obey speed limits for flaps and gear extension
#Flaps/slats on final ... 45

===Shutdown===
#Engine thrust levers ... shutoff
#Engine 1 electric generator ... off
#Engine 2 electric generator ... off
#Switch to external power

=Downloading=

The latest version is always available on the official FlightGear aircraft download page and will be committed regularly to [[FGAddon]].

The latest development version at GitHub can also be downloaded [https://github.com/d-jsb/CRJ700-family/archive/master.zip here].

=Aircraft of the Week/Month=

The CRJ700 was reviewed by Thorsten R as part of the "Aircraft of the Week/Month" feature on the FlightGear Forums.

====Model====

The 3d cockpit of the CRJ-700 is very detailed and contains not only functionality on the main panel but also on the central console and an overhead panel. However, as often seen, the cockpit surfaces not covered by instrumentation are very simply textured by a monochromatic grey color - a more natural texture resembling a real material with some wear and tear could add a lot here.

[http://www.phy.duke.edu/~trenk/pics/crj700-cockpit.jpg View image]

There is a lot of functionality in the cockpit - a startup procedure using the APU is supported as well as a full set of external lights and no-smoking and seat belt signs for the passengers. A nice touch of the model is that it also contains an interior view of the cabin in which the signs can be observed. Switches and knobs are usually animated, and the clickspots are placed fairly intuitively. The MFD's all have various selectable functions.

The exterior model of the aircraft is also very nicely done, contains good animations and shows all the light switch settings in the cockpit faithfully. An option to switch livery exists as well.

[http://www.phy.duke.edu/~trenk/pics/crj700-model.jpg View image]

====Flight characteristics====

The FDM of the CRJ-700 is quite plausible for an airliner of its size. I haven't really tested the behaviour at the edge of the performance envelope, but during normal operations, the plane behaves well and reaches basic performance characteristics. All in all, the plane is an airliner (albeit a small one) - it turns slowly, it does not descent rapidly without picking up a lot of excess speed and all maneuvers need to be planned well in advance. Having said that, it's actually fun to fly.

I found the AP nicely tuned and able to fly turns, climb or dive at all altitudes without oscillations or weird behaviour. Unfortunately, the support for AP modes involving navaids is not as good: While I could home in on a VOR station, the AP seems to be tracking the station rather than the chosen radial, i.e. the angle under which I approached the station kept changing. Also, I was unable to intercept an ILS glideslope automatically. However, the plane can be operated well in IFR conditions just using the instruments to display the navaid signals and the heading and altitude modes of the AP to control the plane.

====My personal wishlist====

Fixing the AP to a more consistent behaviour with navaids would be high on my priority list - there are currently very few airliners with a well-tuned AP capable of tracking navaids. Some more natural texturing in the cockpit would also be nice. I realize that the CRJ-700 is a fairly recent addition to the aircraft repository of Flightgear - but I like where the model is going very much.

====Things to experience====

Try flying at night - the CRJ-700 has one of the best light concepts I've ever seen. The instrument lights are very beautifully done and can be dimmed at need, the cabin lights likewise, and all lighting is visible both from internal and external views.

''Editor's note: The autopilot VOR-LOC/ILS holds have been fixed as of CRJ700 v1.0.2.''

=Development status/Issues/Todo=
==Key features==
* Startup and shutdown procedures
* Mostly complete cockpit
* Realistic autopilot
* Functional flight management system (FMS), advisory-only vertical navigation system (VNAV), and control display unit (CDU)
* Emergency procedures with ram air turbine (RAT) and auxiliary power unit (APU)
* Small library of tutorials
* Cockpit, cabin, and exterior model lightmaps
* Reflection shader on the engines
* Developed aircraft systems
* Tiller steering system

==Todo==
For rating information, see [[Formalizing Aircraft Status]].
===FDM (current rating 3)===
* Make something a little more refined than my [[YASim]] solution (any [[JSBSim]] masters?)
===Exterior (current rating 4)===
* Add minor elements like antennas, ram air turbine, improve gear bay texturing and geometry
* More liveries!
===Flight deck (current rating 4)===
* Improve texturing
* Model circuit breakers
===Systems (current rating 3)===
* Add more pages to EICAS

== Development (section added May 2015) ==
D-JSB et al. work on the CRJ700 family.

=== Status without any particular order ===
==== done ====
* Some bugfixes (e.g. MFD wind indicator, nav pointers, MFD symbols)
* Removed 2D panel which depended on Boing 737-300
* More views (cabin windows, gear)
* OHP switches / switchlights (gimmick: implemented the light test button)
* Details of auto pilot panel behaviour like push function of CRS and HDG
* Modified slats/flaps indicator on EICAS
* APU details on EICAS
* EICAS pages for doors
* Simulation of hydraulic system
* EICAS pages for hydraulic system
* Extend failures dialog (hydraulics)
* Re-implement the electrical system (AC and DC).
* Add cargo doors to model
* Add APU door to model

==== In progress / testing ====
* Update of documentation

==== Planed ====
* Canvas implementation of glas cockpit

== Canvas implementation (planed) ==
[[CRJ 700 family canvas ]]

=External links=
* [http://en.wikipedia.org/wiki/Bombardier_CRJ700_series Bombardier CRJ700 series at Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?t=11863 Development thread at the FlightGear Forums]
* [http://www.smartcockpit.com/data/...700.../HGS_00_Pilots_Guide_CRJ_00.pdf GHS Pilots Guide CRJ]
* [http://aligero.us/files/FMS%204200.pdf FMS 4200 Intro]
* [http://www.4shared.com/get/Q_rDeIsz/Collins_FMS-4200_Flight_Manage.html FMS-4200 Manual]

{{Template:Bombardier}}

Bombardier CRJ700 series

2019-05-21T18:37:42Z

Rodolfo: /* Startup */

{{:{{PAGENAME}}/info}}
[[File:CRJ700-cockpit-night.jpg|The cockpit at night, demonstrating night lighting capabilities|thumb|350px|right]]
[[File:CRJ700-cabin-night.jpg|The interior cabin, also at night|thumb|350px|right]]

The '''Bombardier CRJ700 series''' is a family of 70- to 100- seat regional jet airliners manufactured by Bombardier Aerospace. Its primary competition is the Embraer E-jet series. The family consists of the Bombardier CRJ700, CRJ900, and CRJ1000. The CRJ700 series was developed from the [[Bombardier CRJ-200LR|Bombardier CRJ200]], and remains one of the most popular regional airliner series in the world.

=Variants=

* CRJ700 - the original CRJ700
* CRJ700ER - extended range version
* CRJ700LR - long-range version
* CRJ900 - the first stretch of the airframe
* CRJ900ER - extended range version
* CRJ900LR - long-range version
* CRJ1000 - the final stretch of the airframe
* CRJ1000 EuroLite - low-range/low-cost version targeted at European operators
* CRJ1000ER - extended range version

=Aircraft help=

HTML documentation is included in the Docs/ folder.

==Key commands==

{| class="keytable"
! Key
! Function
|-
! colspan="2" | Speedbrakes/spoilers
|-
| {{key press|Ctrl|B}}
| Cycle speedbrake setting
|-
| {{key press|j}}
| Decrease ground lift dump setting
|-
| {{key press|k}}
| Increase ground lift dump setting
|-
! colspan="2"|Engines
|-
| {{key press|Ctrl|Del}}
| Arm/disarm thrust reversers
|-
| {{key press|Del}}
| Toggle thrust reversers
|-
! colspan="2" | Autopilot
|-
| {{key press|Ctrl|A}}
| Toggle autopilot altitude mode
|-
| {{key press|Ctrl|F}}
|Engage/disengage autopilot
|-
| {{key press|Ctrl|G}}
| Toggle autopilot approach mode
|-
| {{key press|Ctrl|H}}
| Toggle autopilot heading mode
|-
| {{key press|Ctrl|N}}
| Toggle autopilot NAV mode
|-
| {{key press|Ctrl|P}}
| Set autopilot basic pitch mode
|-
| {{key press|Ctrl|W}}
| Set autopilot basic heading/roll mode
|-
| {{key press|F6}}
| Cycle NAV source
|-
! colspan="2" | Tiller/Nose gear steering
|-
| {{key press|q}}
| Steer tiller left
|-
| {{key press|Shift|Q}}
| Set tiller to full left
|-
| {{key press|w}}
| Center tiller
|-
| {{key press|Shift|W}}
| Pop up tiller dialog
|-
| {{key press|e}}
| Steer tiller right
|-
| {{key press|Shift|E}}
| Set tiller to full right
|-
! colspan="2" | Walk view
|-
| {{key press|r}}
| Walk forward toward view
|-
| {{key press|Shift|R}}
| Run forward toward view
|-
| {{key press|f}}
| Walk backwards from view
|-
| {{key press|y}}
| View point down
|-
| {{key press|Y}}
| View point up
|}

==Simplified procedures==
===Startup===
[[File:Start-123.png|thumb|right|CRJ700 Start engines (1)]]
#Battery switch ... on
#Fuel Pumps ... enable
#APU start/stop switch ... on
#Bleed air source ... automatic
#Engine 1 thrust lever ... idle
#Engine 1 start sequence ... initiated
#Engine 2 thrust lever ... idle
#Engine 2 start sequence ... initiated
#APU start/stop switch ... off
#Engine 1 electric generator ... on
#Engine 2 electric generator ... on

===Takeoff===
#Flaps/slats ... 8 or 20
#Landing lights ... on
#Engine thrust modes ... TO/GA

===Climb and cruise===
#Engine thrust modes ... climb
Nominal cruise speed Mach 0.78 (0.80 for CRJ900)

===Approach and landing===
Remain below 250 knots below 10,000 feet at all times
#Thrust reversers ... armed
#Obey speed limits for flaps and gear extension
#Flaps/slats on final ... 45

===Shutdown===
#Engine thrust levers ... shutoff
#Engine 1 electric generator ... off
#Engine 2 electric generator ... off
#Switch to external power

=Downloading=

The latest version is always available on the official FlightGear aircraft download page and will be committed regularly to [[FGAddon]].

The latest development version at GitHub can also be downloaded [https://github.com/d-jsb/CRJ700-family/archive/master.zip here].

=Aircraft of the Week/Month=

The CRJ700 was reviewed by Thorsten R as part of the "Aircraft of the Week/Month" feature on the FlightGear Forums.

====Model====

The 3d cockpit of the CRJ-700 is very detailed and contains not only functionality on the main panel but also on the central console and an overhead panel. However, as often seen, the cockpit surfaces not covered by instrumentation are very simply textured by a monochromatic grey color - a more natural texture resembling a real material with some wear and tear could add a lot here.

[http://www.phy.duke.edu/~trenk/pics/crj700-cockpit.jpg View image]

There is a lot of functionality in the cockpit - a startup procedure using the APU is supported as well as a full set of external lights and no-smoking and seat belt signs for the passengers. A nice touch of the model is that it also contains an interior view of the cabin in which the signs can be observed. Switches and knobs are usually animated, and the clickspots are placed fairly intuitively. The MFD's all have various selectable functions.

The exterior model of the aircraft is also very nicely done, contains good animations and shows all the light switch settings in the cockpit faithfully. An option to switch livery exists as well.

[http://www.phy.duke.edu/~trenk/pics/crj700-model.jpg View image]

====Flight characteristics====

The FDM of the CRJ-700 is quite plausible for an airliner of its size. I haven't really tested the behaviour at the edge of the performance envelope, but during normal operations, the plane behaves well and reaches basic performance characteristics. All in all, the plane is an airliner (albeit a small one) - it turns slowly, it does not descent rapidly without picking up a lot of excess speed and all maneuvers need to be planned well in advance. Having said that, it's actually fun to fly.

I found the AP nicely tuned and able to fly turns, climb or dive at all altitudes without oscillations or weird behaviour. Unfortunately, the support for AP modes involving navaids is not as good: While I could home in on a VOR station, the AP seems to be tracking the station rather than the chosen radial, i.e. the angle under which I approached the station kept changing. Also, I was unable to intercept an ILS glideslope automatically. However, the plane can be operated well in IFR conditions just using the instruments to display the navaid signals and the heading and altitude modes of the AP to control the plane.

====My personal wishlist====

Fixing the AP to a more consistent behaviour with navaids would be high on my priority list - there are currently very few airliners with a well-tuned AP capable of tracking navaids. Some more natural texturing in the cockpit would also be nice. I realize that the CRJ-700 is a fairly recent addition to the aircraft repository of Flightgear - but I like where the model is going very much.

====Things to experience====

Try flying at night - the CRJ-700 has one of the best light concepts I've ever seen. The instrument lights are very beautifully done and can be dimmed at need, the cabin lights likewise, and all lighting is visible both from internal and external views.

''Editor's note: The autopilot VOR-LOC/ILS holds have been fixed as of CRJ700 v1.0.2.''

=Development status/Issues/Todo=
==Key features==
* Startup and shutdown procedures
* Mostly complete cockpit
* Realistic autopilot
* Functional flight management system (FMS), advisory-only vertical navigation system (VNAV), and control display unit (CDU)
* Emergency procedures with ram air turbine (RAT) and auxiliary power unit (APU)
* Small library of tutorials
* Cockpit, cabin, and exterior model lightmaps
* Reflection shader on the engines
* Developed aircraft systems
* Tiller steering system

==Todo==
For rating information, see [[Formalizing Aircraft Status]].
===FDM (current rating 3)===
* Make something a little more refined than my [[YASim]] solution (any [[JSBSim]] masters?)
===Exterior (current rating 4)===
* Add minor elements like antennas, ram air turbine, improve gear bay texturing and geometry
* More liveries!
===Flight deck (current rating 4)===
* Improve texturing
* Model circuit breakers
===Systems (current rating 3)===
* Add more pages to EICAS

== Development (section added May 2015) ==
D-JSB et al. work on the CRJ700 family.

=== Status without any particular order ===
==== done ====
* Some bugfixes (e.g. MFD wind indicator, nav pointers, MFD symbols)
* Removed 2D panel which depended on Boing 737-300
* More views (cabin windows, gear)
* OHP switches / switchlights (gimmick: implemented the light test button)
* Details of auto pilot panel behaviour like push function of CRS and HDG
* Modified slats/flaps indicator on EICAS
* APU details on EICAS
* EICAS pages for doors
* Simulation of hydraulic system
* EICAS pages for hydraulic system
* Extend failures dialog (hydraulics)
* Re-implement the electrical system (AC and DC).
* Add cargo doors to model
* Add APU door to model

==== In progress / testing ====
* Update of documentation

==== Planed ====
* Canvas implementation of glas cockpit

== Canvas implementation (planed) ==
[[CRJ 700 family canvas ]]

=External links=
* [http://en.wikipedia.org/wiki/Bombardier_CRJ700_series Bombardier CRJ700 series at Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?t=11863 Development thread at the FlightGear Forums]
* [http://www.smartcockpit.com/data/...700.../HGS_00_Pilots_Guide_CRJ_00.pdf GHS Pilots Guide CRJ]
* [http://aligero.us/files/FMS%204200.pdf FMS 4200 Intro]
* [http://www.4shared.com/get/Q_rDeIsz/Collins_FMS-4200_Flight_Manage.html FMS-4200 Manual]

{{Template:Bombardier}}

File:Start-123.png

2019-05-21T18:32:47Z

Rodolfo: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=CRJ700 Start engines (1)}}
|date=2019-05-21
|source={{own}}
|author=[[User:Rodolfo|Rodolfo]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Bombardier Aerospace]]

Beechcraft B1900D

2019-04-29T22:54:45Z

Rodolfo: /* Starting Procedure */

{{:{{PAGENAME}}/info}}
[[File:b1900d-cockpit-pano.jpg|thumb|270px|[[Howto: Make full spherical panorama|A full spherical panorama]] of the 3d Beechcraft B1900d cockpit]]

The '''Beechcraft 1900''' series [[aircraft]] is the most popular 19-passenger [[:Category:Airliners|airliner]] in history. It is a pressurized, twin-engine [[Powerplant#Turboprop|turboprop]] manufactured by the [[Beechcraft|Beechcraft Division]] of the Raytheon Company (now Hawker Beechcraft). Designed primarily as an all weather regional airliner capable of landing on relatively short runways it has also been used by the United States military and other governments.

Beech announced the improved '''1900D''', simulated here, at the US Regional Airlines Association meeting in 1989. The main difference in the 1900D was the substantially deeper fuselage allowing stand up headroom in the cabin. It also had larger passenger and cargo doors and windows, twin ventral strakes and auxiliary horizontal fixed tails. To carry the extra weight Beech upgraded to two PT6A-67D engines, each rated at 1,279 shaft horsepower. Although rarely used a fully fueled Beechcraft 1900 has a range of 860 miles.

The Beechcraft B1900D is one of the default aircraft in [[FlightGear]] and has been available since [[FlightGear 0.9.8]].

== Review ==

The Beech 1900D is one of the nicer simulator aircraft on Flight Gear. It comes standard with version 1.9.1 which is tested here.

==Model Detail==

The Beech 1900D has a smooth high polygon exterior that looks realistic on the ground and in flight. The propellers spin in a blur even when idling, and the landing gear is fairly detailed. The interior is nicely modeled, including the cockpit and the passenger area which is included as a standard view. Although the windows appear as rough polygons, you can sit in the passenger seat and experience the entire flight. The cockpit and instruments and well modeled and work well.

==Flying==
This aircraft packs a lot of power with the twin engines, and take-off performance is strong and powerful. The B1900D features a very stable flying experience. Anyone graduating from a Cessna 172 will appreciate the stability and the power of the aircraft. Banking too hard will trigger the "Bank Angle" warning and so will descending too fast.

==Landing with caution==

The only potentially serious problem I have encountered on this aircraft is during landing. With some realistic procedures, this can be sorted out. Descending very fast requires a sharp arrest of descent before landing, however pulling up sharply will not slow the descent enough to land smoothly. Also, the right wing tends to dip as the aircraft enters a stall in nose up condition at high speed near the ground, not somewhere you want to be. The solution is to trim the aircraft for landing, ensuring with sufficient elevator control and to approach at the recommended approach speed of 130 kt. Also check the weight configured for the model, try flying empty for a start.

Apart from the above cautions, the B1900D is a real mini airliner, and fun to fly due to its speed, power and rate of climb not to mention the 3D models including a single pilot (no co-pilot and no passengers).

(Reviewed by Openflight 17 Sept 2015)

== Procedures ==

=== Starting Procedure ===
In the menu bar at the top of the screen you may select B1900D and then Autostart. You may also choose to start-up manually. In the help menu you will find a start up tutorial this is a quick summary.

* Switch on the battery
* Switch on the left and right generators located on the lower left pilots panel. This should bring up the electrical systems and you should have instrumentation lights
* Switch on the AC BUSs above the generator switches
* Switch on the avionics located just below the battery and generator switches.
* Look at the throttle panel in between the pilot and co-pilot. The two far right levers are labeled Condition. Move them fully forward by clicking at the top of the lever slots or by pressing “m”.
* Press and hold the Left Engine Start switch. When the Turbine gauge reaches 18~20 you should now hear the engine starting up. Release the Start Switch.
* Repeat the procedure for the Right engine.
* Move the levers labeled Propeller forward by clicking at the top of the lever slots or by pressing “n”.
* Move the levers labeled Throttle to the idle position by clicking at the top of the lever slots or by pressing “9” or “PAGEUP”.
* Switch on Master Panel and any lights needed on the left side of the overhead console.
* Reset the Master Caution Warning in the middle top of the pilot panel that is probably flashing red now that all systems are powered up.
* You probably want to switch on the EFIS Power switches.
* The aircraft is now ready for take off.

=== Takeoff ===
* Decision at 105 KIAS
* Rotation at 110 KIAS
* Pitch 10-15 degrees
* Trim before engaging autopilot

=== Climb ===
* Airspeed 160 KIAS
* Climb Rate 1500 fpm

=== Cruise ===
* 220 –240 KIAS

=== Descent ===
* 180 KIAS
* Descent Rate –1500 fpm

=== Approach ===
* Establish 150 KIAS
* Set flaps to approach
* Establish 130 KIAS
* Landing gear down – set flaps full down
* Final glide slope 110 KIAS

=== Landing ===
* 100 KIAS
* Main wheels down first
* Lower nose gear

=== [[V Speeds]] ===
{| class="wikitable"
|-
|Stall speed, dirty (Vs0)||88 kts
|-
|Stall speed, clean (Vs1)||104 kts
|-
|Best angel of climb (Vx)||123 kts
|-
|Best rate of climb (Vy)||135 kts
|-
|Maneuvering speed (Va)||184 kts
|-
|Never exceed speed (Vne)||247 kts
|}
<ref>{{cite web |url=http://aerolinea.simpilots.es/descargas/Beechcraft_b1900d.pdf |title=Beechcraft B1900D Aircraft Operating Manuals |publisher=SimPilots }}</ref>

== [[GPS]] ==
The B1900D is equipped with a functioning [[Avionics_and_instruments#Further_instruments|Bendix/King KLN 90B]] [[GPS]] that can be slaved to the autopilot. In the help menu you will find a tutorial on [[GPS]] navigation.

== Liveries ==
Apart from the two liveries (SWISS AIR FORCE and AIR NEW ZEALAND) that comes with the b1900d aircraft, it is possible to download more on the [http://liveries.flightgear.org/aircraft.php?display=2&id=21 FlightGear Livery Database].
To create your own livery, a vector template (in svg format) is available in the [http://liveries.flightgear.org/download/paintkits/27.zip livery database].

== Notes ==
* The glas panel instruments (artificial horizon and horizontal situation indicator) don't show up with Rembrandt rendering
{{Appendix}}

{{Beechcraft}}

[[Category:Aircraft with Route Manager support]]

[[fr:Beechcraft B1900D]]

Spoken ATC

2019-04-27T16:44:42Z

Rodolfo:

{{infobox subsystem
|image = Spoken-ATC-Screenshot.jpg
|name = Spoken ATC
|started = 07/2017
|description = Spoken ATC
|status = Under active development as of 07/2017
|maintainers = {{usr|Rodolfo}}
|developers = Rodolfo (rleibner on the forum)
}}

The module is not intended to compete with FGComm, Festival or other similar features.
On the contrary, its use is indicated if these are not available (eg, few hardware resources, no Internet connection, etc.) <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=312968#p312968
|title = <nowiki> ATC </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Jun 22nd, 2017
|added = Jun 22nd, 2017
|script_version = 0.40
}}</ref>

[[Spoken ATC]] allows the pilot to listen to the directives of the ''Air Traffic Controller''.

= Preface =
'''Typically''', you should tune the ATC-station frequency and make a request by pressing {{key press|<}} key. You may hear something like: 

* ''"Charlie X-ray Bravo Echo X-ray , this is Montevideo Carrasco International tower. QNH 1024 or 30 point 24 inches. Join left pattern Runway 1 9 and report."''

So, you enter in the base leg and press {{key press|<}} again:

* ''"Charlie X-ray Bravo Echo X-ray , Wind 1 5 0 degrees, 3 knots. Runway 1 9 cleared to land."''

After landing and while you are braking, you press {{key press|<}} once more:

* ''"Charlie X-ray Bravo Echo X-ray , Exit Runway at first taxiway and contact Ground 121 point 82."''

That is only an example of standard '''VFR Phraseology'''
<ref>{{cite web
|url = http://wiki.flightgear.org/ATC_phraseology |title = wiki.flightgear.org/ATC_phraseology
}}</ref>
that you can expect from '''Spoken ATC'''. 

= How to install =
{{note | This is the latest version, v.2.2.4 (Apr 26, 2019) }}
Download this [[Addon]] from [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/SpokenATC Sourceforge]. Read the [[FGAddon#Obtaining_aircraft|directions]] as a reference.

Start your FGFS session including "''--addon=<your local path>/SpokenATC''" in the command line or in the ''settings'' tab of the launcher.
 
= How to use it =
Launch FlighGear (or re-start it) and tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information''),
and press the {{key press|<}} key to transmit your request. 
You will hear the ATC's answer according the standard VFR phraseology, depending on your current position, weather and previous messages:
* If you are on ground =>
** The code interprets it's a taxi request (if you are far from the runway or you've just landed),
** or a take-off request (if you are on the correct Runway or at his holding point).
* If you are flying =>
** The code interprets it's an approach request (if you tunned an APP station),
** or a landing request (if you tunned a TWR station),
** or a departure request (if you tunned a DEP station. and you are climbing after a take-off). 

Note that only TWR stations can deliver landing or take-off clearances, and only GND or TWR stations can deliver taxiing ones. 
Where there is not a specific GND or APP-DEP freq., TOWER can take their tasks. 
If they do exist, TWR will redirect to the specific frequency. 

Only at initial contact, the ATC message includes his station name & type, and the current QNH. 
APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR). 
TWR stations will give instructions to join pattern or make direct final (depending on your position). 
= Tips =

== Heavy airplanes ==
To request a ILS runway, contact ATC using {{key press|Ctrl}}{{key press|<}}.
== A realistic behavior ==
To achieve realistic behavior, follow a logical sequence of communications, viz.:
* Contact GND (or TWR) prior to taxiing.
* Contact TWR prior to take-off or land.
* Contact DEP (if available) after take-off to leave the CTR.
* Contact APP (if available) prior to enter the CTR.
* etc, etc.
== On screen voice ==
If the writen messages bother you, when binding (see above) you can call the function as
<syntaxhighlight lang="xml">
<script> <![CDATA[ spoken_atc.speak(n); ]]> </script> </syntaxhighlight>
with '''n''' seconds you want, even 0 meaning no messages at all. 

= Phraseology customization =
You can customize the phraseology by editing the "''phraseology.xml''" file. 
There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').
=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either " or ' .
* Punctuation is meaningfull. }}
=== Substitutions ===
Strings starting by '''%''' will call some '''property value'''.
In the example above replace "'''day'''" by "'''% /sim/startup/time-offset-type'''". 
Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.
{{note |
* The called property must be a string.}}
=== Concatenation ===
Strings starting by '''~''' will append the sentence with another one.
Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "'' 

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility..
Better? Fine, but what about the message on the screen?
Include a tag with the pattern <replace type="string">'''old''':'''new'''</replace> :
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight> 

Besides that, you can call the ''spoken_atc.say()'' function at runtime to check your customization. 
=== spoken_atc.say() function ===
You can ... [TODO]

 

<big>And remember this is '''VFR''': heed the instructions of the ATC but '''keep your eyes wide open !'''</big>

= Ground Controlled Approaches =
{{See also|Howto:Implementing a simple GCA system}}

= References =
{{Appendix}}

[[Category:FlightGear add-ons]]
[[Category:Air Traffic Control]]

Beechcraft B1900D

2018-04-23T20:56:38Z

Rodolfo: /* GPS */

{{:{{PAGENAME}}/info}}
[[File:b1900d-cockpit-pano.jpg|thumb|270px|[[Howto: Make full spherical panorama|A full spherical panorama]] of the 3d Beechcraft B1900d cockpit]]

The '''Beechcraft 1900''' series [[aircraft]] is the most popular 19-passenger [[:Category:Airliners|airliner]] in history. It is a pressurized, twin-engine [[Powerplant#Turboprop|turboprop]] manufactured by the [[Beechcraft|Beechcraft Division]] of the Raytheon Company (now Hawker Beechcraft). Designed primarily as an all weather regional airliner capable of landing on relatively short runways it has also been used by the United States military and other governments.

Beech announced the improved '''1900D''', simulated here, at the US Regional Airlines Association meeting in 1989. The main difference in the 1900D was the substantially deeper fuselage allowing stand up headroom in the cabin. It also had larger passenger and cargo doors and windows, twin ventral strakes and auxiliary horizontal fixed tails. To carry the extra weight Beech upgraded to two PT6A-67D engines, each rated at 1,279 shaft horsepower. Although rarely used a fully fueled Beechcraft 1900 has a range of 860 miles.

The Beechcraft B1900D is one of the default aircraft in [[FlightGear]] and has been available since [[FlightGear 0.9.8]].

== Review ==

The Beech 1900D is one of the nicer simulator aircraft on Flight Gear. It comes standard with version 1.9.1 which is tested here.

==Model Detail==

The Beech 1900D has a smooth high polygon exterior that looks realistic on the ground and in flight. The propellers spin in a blur even when idling, and the landing gear is fairly detailed. The interior is nicely modeled, including the cockpit and the passenger area which is included as a standard view. Although the windows appear as rough polygons, you can sit in the passenger seat and experience the entire flight. The cockpit and instruments and well modeled and work well.

==Flying==
This aircraft packs a lot of power with the twin engines, and take-off performance is strong and powerful. The B1900D features a very stable flying experience. Anyone graduating from a Cessna 172 will appreciate the stability and the power of the aircraft. Banking too hard will trigger the "Bank Angle" warning and so will descending too fast.

==Landing with caution==

The only potentially serious problem I have encountered on this aircraft is during landing. With some realistic procedures, this can be sorted out. Descending very fast requires a sharp arrest of descent before landing, however pulling up sharply will not slow the descent enough to land smoothly. Also, the right wing tends to dip as the aircraft enters a stall in nose up condition at high speed near the ground, not somewhere you want to be. The solution is to trim the aircraft for landing, ensuring with sufficient elevator control and to approach at the recommended approach speed of 130 kt. Also check the weight configured for the model, try flying empty for a start.

Apart from the above cautions, the B1900D is a real mini airliner, and fun to fly due to its speed, power and rate of climb not to mention the 3D models including a single pilot (no co-pilot and no passengers).

(Reviewed by Openflight 17 Sept 2015)

== Procedures ==

=== Starting Procedure ===
In the menu bar at the top of the screen you may select B1900D and then Autostart. You may also choose to start-up manually. In the help menu you will find a start up tutorial this is a quick summary.

* Switch on the battery
* Switch on the left and right generators located on the lower left pilots panel. This should bring up the electrical systems and you should have instrumentation lights
* Switch on the AC BUSs above the generator switches
* Switch on the avionics located just below the battery and generator switches.
* Look at the throttle panel in between the pilot and co-pilot. The two far right levers are labeled Condition. Move them fully forward by clicking at the top of the lever slots or by pressing “m”. You should now hear the engines starting up.
* Move the levers labeled Propeller forward by clicking at the top of the lever slots or by pressing “n”.
* Move the levers labeled Throttle to the idle position by clicking at the top of the lever slots or by pressing “9” or “PAGEUP”.
* Switch on Master Panel and any lights needed on the left side of the overhead console.
* Reset the Master Caution Warning in the middle top of the pilot panel that is probably flashing red now that all systems are powered up.
* The aircraft is now ready for take off.

=== Takeoff ===
* Decision at 105 KIAS
* Rotation at 110 KIAS
* Pitch 10-15 degrees
* Trim before engaging autopilot

=== Climb ===
* Airspeed 160 KIAS
* Climb Rate 1500 fpm

=== Cruise ===
* 220 –240 KIAS

=== Descent ===
* 180 KIAS
* Descent Rate –1500 fpm

=== Approach ===
* Establish 150 KIAS
* Set flaps to approach
* Establish 130 KIAS
* Landing gear down – set flaps full down
* Final glide slope 110 KIAS

=== Landing ===
* 100 KIAS
* Main wheels down first
* Lower nose gear

=== [[V Speeds]] ===
{| class="wikitable"
|-
|Stall speed, dirty (Vs0)||88 kts
|-
|Stall speed, clean (Vs1)||104 kts
|-
|Best angel of climb (Vx)||123 kts
|-
|Best rate of climb (Vy)||135 kts
|-
|Maneuvering speed (Va)||184 kts
|-
|Never exceed speed (Vne)||247 kts
|}
<ref>{{cite web |url=http://aerolinea.simpilots.es/descargas/Beechcraft_b1900d.pdf |title=Beechcraft B1900D Aircraft Operating Manuals |publisher=SimPilots }}</ref>

== [[GPS]] ==
The B1900D is equipped with a functioning [[Avionics_and_instruments#Further_instruments|Bendix/King KLN 90B]] [[GPS]] that can be slaved to the autopilot. In the help menu you will find a tutorial on [[GPS]] navigation.

== Liveries ==
Apart from the two liveries (SWISS AIR FORCE and AIR NEW ZEALAND) that comes with the b1900d aircraft, it is possible to download more on the [http://liveries.flightgear.org/aircraft.php?display=2&id=21 FlightGear Livery Database].
To create your own livery, a vector template (in svg format) is available in the [http://liveries.flightgear.org/download/paintkits/27.zip livery database].

== Notes ==
* The glas panel instruments (artificial horizon and horizontal situation indicator) don't show up with Rembrandt rendering
{{Appendix}}

{{Beechcraft}}

[[Category:Aircraft with Route Manager support]]

[[fr:Beechcraft B1900D]]

Seneca II Panel Reference

2018-04-03T16:51:31Z

Rodolfo: /* The Controls of the Seneca II */

This is a quick reference to the instruments and controls in the Seneca's cockpit. (Piper PA34-200T Seneca II)
= The Controls of the Seneca II =
[[File:Seneca_II_reference_left.jpg|thumb|left|Pilot's Panel]]
[[File:Seneca_II_reference_right.jpg|thumb|left|Co-Pilot's Panel]]
[[File:Seneca_II_reference_fuel_trim.jpg|thumb|left|Fuel-Trim Console]]
 

# magneto - left engine
# magneto - right engine
# starter - press left for left engine, right for right engine
# primer - left/right engine
# taxi/landing lights
# nav lights
# anit collision lights - left half: fin (beacon), right half: wing (strobes)
# pitot and stall warning heat
# fuel boost pumps - up: high, down: low, center: off
# battery master
# alternator on/off
# switch panel lights dimmer (noop)
# clock
# airspeed indicator
# attitude indicator (artificial horizon)
# altimeter (barometric)
# radar altimeter
# adf indicator <ref>[https://en.wikipedia.org/wiki/Radio_direction_finder#Automatic_direction_finder_(ADF) Automatic Direction Finder (ADF)]</ref>
# turn coordinator
# horizontal situation indicator (hsi) <ref>[[Horizontal Situation Indicator]]</ref>
# vertical speed indicator (vsi)
# vor/ils indicator NAV2 <ref>[https://en.wikipedia.org/wiki/Course_deviation_indicator Course Deviation Indicator (CDI)]</ref>
# alternator ampere meter (shows alternator load)
# cylinder head temperature
# oil temperature
# oil pressure
# fuel
# RPM left engine
# dual manifold pressure gauge
# RPM right engine
# landing gear lever and emergency gear extension
# landing gear indicator
# autopilot control
# autopilot pitch control
# parking brake
# engine alternate air
# cowl flaps
# instrument lights dimmer
# fuel flow meter
# exhaust gas temperature (EGT) left/right engine
# DME frequency source (NAV1/Hold/NAV2) and ON/OFF
# DME indicator
# HSI gyro control
# ADF radio
# KX165 COM2/NAV2 radio <ref>[[Kx165|KX165]]</ref>
# KX165 COM1/NAV1 radio
# GMA340 intercom
# surface deice (boots)
# wing ice inspection light
# prop deice
# prop deice control gauge
# windshield deice
# annunciator with test button
# gear warning light
# autopilot capture light
# flap lever
# autopilot mode
# gyro pressure
# cicruit breaker panel
# magnetic compass
# fuel selectors - forward: on, center: off, backwards: cross-feed
# elevator trim
# rudder trim

= References =
{{Appendix}}
= Related content =
* [[Piper PA34-200T Seneca II]]
* [[Seneca II Checklist]]
* [[Seneca II HOWTO]]
[[fr:Seneca II Panel Reference]]

[[Category:Piper PA34-200T Seneca II]]

Seneca II Panel Reference

2018-04-02T17:02:51Z

Rodolfo: /* The Controls of the Seneca II */

This is a quick reference to the instruments and controls in the Seneca's cockpit. (Piper PA34-200T Seneca II)
= The Controls of the Seneca II =
[[File:Seneca_II_reference_left.jpg|thumb|left|Pilot's Panel]]
[[File:Seneca_II_reference_right.jpg|thumb|left|Co-Pilot's Panel]]
[[File:Seneca_II_reference_fuel_trim.jpg|thumb|left|Fuel-Trim Console]]
 

# magneto - left engine
# magneto - right engine
# starter - press left for left engine, right for right engine
# primer - left/right engine
# taxi/landing lights
# nav lights
# anit collision lights - left half: fin (beacon), right half: wing (strobes)
# pitot and stall warning heat
# fuel boost pumps - up: high, down: low, center: off
# battery master
# alternator on/off
# switch panel lights dimmer (noop)
# clock
# airspeed indicator
# attitude indicator (artificial horizon)
# altimeter (barometric)
# radar altimeter
# adf indicator <ref>[https://en.wikipedia.org/wiki/Radio_direction_finder#Automatic_direction_finder_(ADF) Automatic Direction Finder (ADF)]</ref>
# turn coordinator
# horizontal situation indicator (hsi) <ref>[[Horizontal Situation Indicator]]</ref>
# vertical speed indicator (vsi)
# vor/ils indicator NAV2 <ref>[https://en.wikipedia.org/wiki/Course_deviation_indicator Course Deviation Indicator (CDI)]</ref>
# alternator ampere meter (shows alternator load)
# cylinder head temperature
# oil temperature
# oil pressure
# fuel
# RPM left engine
# dual manifold pressure gauge
# RPM right engine
# landing gear lever and emergency gear extension
# landing gear indicator
# autopilot control
# autopilot pitch control
# parking brake
# engine alternate air
# cowl flaps
# instrument lights dimmer
# fuel flow meter
# exhaust gas temperature (EGT) left/right engine
# DME frequency source (NAV1/Hold/NAV2) and ON/OFF
# DME indicator
# HSI gyro control
# ADF radio
# KX165 COM2/NAV2 radio
# KX165 COM1/NAV1 radio
# GMA340 intercom
# surface deice (boots)
# wing ice inspection light
# prop deice
# prop deice control gauge
# windshield deice
# annunciator with test button
# gear warning light
# autopilot capture light
# flap lever
# autopilot mode
# gyro pressure
# cicruit breaker panel
# magnetic compass
# fuel selectors - forward: on, center: off, backwards: cross-feed
# elevator trim
# rudder trim

= References =
{{Appendix}}
= Related content =
* [[Piper PA34-200T Seneca II]]
* [[Seneca II Checklist]]
* [[Seneca II HOWTO]]
[[fr:Seneca II Panel Reference]]

[[Category:Piper PA34-200T Seneca II]]

Seneca II Panel Reference

2018-04-02T16:48:07Z

Rodolfo: /* The Controls of the Seneca II */

This is a quick reference to the instruments and controls in the Seneca's cockpit. (Piper PA34-200T Seneca II)
= The Controls of the Seneca II =
[[File:Seneca_II_reference_left.jpg|thumb|left|Pilot's Panel]]
[[File:Seneca_II_reference_right.jpg|thumb|left|Co-Pilot's Panel]]
[[File:Seneca_II_reference_fuel_trim.jpg|thumb|left|Fuel-Trim Console]]
 

# magneto - left engine
# magneto - right engine
# starter - press left for left engine, right for right engine
# primer - left/right engine
# taxi/landing lights
# nav lights
# anit collision lights - left half: fin (beacon), right half: wing (strobes)
# pitot and stall warning heat
# fuel boost pumps - up: high, down: low, center: off
# battery master
# alternator on/off
# switch panel lights dimmer (noop)
# clock
# airspeed indicator
# attitude indicator (artificial horizon)
# altimeter (barometric)
# radar altimeter
# adf indicator
# turn coordinator
# horizontal situation indicator (hsi) <ref>[[Horizontal Situation Indicator]]</ref>
# vertical speed indicator (vsi)
# vor/ils indicator NAV2 <ref>[https://en.wikipedia.org/wiki/Course_deviation_indicator Course Deviation Indicator]</ref>
# alternator ampere meter (shows alternator load)
# cylinder head temperature
# oil temperature
# oil pressure
# fuel
# RPM left engine
# dual manifold pressure gauge
# RPM right engine
# landing gear lever and emergency gear extension
# landing gear indicator
# autopilot control
# autopilot pitch control
# parking brake
# engine alternate air
# cowl flaps
# instrument lights dimmer
# fuel flow meter
# exhaust gas temperature (EGT) left/right engine
# DME frequency source (NAV1/Hold/NAV2) and ON/OFF
# DME indicator
# HSI gyro control
# ADF radio
# KX165 COM2/NAV2 radio
# KX165 COM1/NAV1 radio
# GMA340 intercom
# surface deice (boots)
# wing ice inspection light
# prop deice
# prop deice control gauge
# windshield deice
# annunciator with test button
# gear warning light
# autopilot capture light
# flap lever
# autopilot mode
# gyro pressure
# cicruit breaker panel
# magnetic compass
# fuel selectors - forward: on, center: off, backwards: cross-feed
# elevator trim
# rudder trim

= References =
{{Appendix}}
= Related content =
* [[Piper PA34-200T Seneca II]]
* [[Seneca II Checklist]]
* [[Seneca II HOWTO]]
[[fr:Seneca II Panel Reference]]

[[Category:Piper PA34-200T Seneca II]]

Seneca II Panel Reference

2018-04-02T16:43:26Z

Rodolfo: /* The Controls of the Seneca II */

This is a quick reference to the instruments and controls in the Seneca's cockpit. (Piper PA34-200T Seneca II)
= The Controls of the Seneca II =
[[File:Seneca_II_reference_left.jpg|thumb|left|Pilot's Panel]]
[[File:Seneca_II_reference_right.jpg|thumb|left|Co-Pilot's Panel]]
[[File:Seneca_II_reference_fuel_trim.jpg|thumb|left|Fuel-Trim Console]]
 

# magneto - left engine
# magneto - right engine
# starter - press left for left engine, right for right engine
# primer - left/right engine
# taxi/landing lights
# nav lights
# anit collision lights - left half: fin (beacon), right half: wing (strobes)
# pitot and stall warning heat
# fuel boost pumps - up: high, down: low, center: off
# battery master
# alternator on/off
# switch panel lights dimmer (noop)
# clock
# airspeed indicator
# attitude indicator (artificial horizon)
# altimeter (barometric)
# radar altimeter
# adf indicator
# turn coordinator
# horizontal situation indicator (hsi) <ref>[[Horizontal_Situation_Indicator]]</ref>
# vertical speed indicator (vsi)
# vor/ils indicator NAV2
# alternator ampere meter (shows alternator load)
# cylinder head temperature
# oil temperature
# oil pressure
# fuel
# RPM left engine
# dual manifold pressure gauge
# RPM right engine
# landing gear lever and emergency gear extension
# landing gear indicator
# autopilot control
# autopilot pitch control
# parking brake
# engine alternate air
# cowl flaps
# instrument lights dimmer
# fuel flow meter
# exhaust gas temperature (EGT) left/right engine
# DME frequency source (NAV1/Hold/NAV2) and ON/OFF
# DME indicator
# HSI gyro control
# ADF radio
# KX165 COM2/NAV2 radio
# KX165 COM1/NAV1 radio
# GMA340 intercom
# surface deice (boots)
# wing ice inspection light
# prop deice
# prop deice control gauge
# windshield deice
# annunciator with test button
# gear warning light
# autopilot capture light
# flap lever
# autopilot mode
# gyro pressure
# cicruit breaker panel
# magnetic compass
# fuel selectors - forward: on, center: off, backwards: cross-feed
# elevator trim
# rudder trim

= References =
{{Appendix}}
= Related content =
* [[Piper PA34-200T Seneca II]]
* [[Seneca II Checklist]]
* [[Seneca II HOWTO]]
[[fr:Seneca II Panel Reference]]

[[Category:Piper PA34-200T Seneca II]]

Seneca II Panel Reference

2018-04-02T16:41:06Z

Rodolfo: /* The Controls of the Seneca II */

This is a quick reference to the instruments and controls in the Seneca's cockpit. (Piper PA34-200T Seneca II)
= The Controls of the Seneca II =
[[File:Seneca_II_reference_left.jpg|thumb|left|Pilot's Panel]]
[[File:Seneca_II_reference_right.jpg|thumb|left|Co-Pilot's Panel]]
[[File:Seneca_II_reference_fuel_trim.jpg|thumb|left|Fuel-Trim Console]]
 

# magneto - left engine
# magneto - right engine
# starter - press left for left engine, right for right engine
# primer - left/right engine
# taxi/landing lights
# nav lights
# anit collision lights - left half: fin (beacon), right half: wing (strobes)
# pitot and stall warning heat
# fuel boost pumps - up: high, down: low, center: off
# battery master
# alternator on/off
# switch panel lights dimmer (noop)
# clock
# airspeed indicator
# attitude indicator (artificial horizon)
# altimeter (barometric)
# radar altimeter
# adf indicator
# turn coordinator
# horizontal situation indicator (hsi) <ref>{{http://wiki.flightgear.org/Horizontal_Situation_Indicator}}</ref>
# vertical speed indicator (vsi)
# vor/ils indicator NAV2
# alternator ampere meter (shows alternator load)
# cylinder head temperature
# oil temperature
# oil pressure
# fuel
# RPM left engine
# dual manifold pressure gauge
# RPM right engine
# landing gear lever and emergency gear extension
# landing gear indicator
# autopilot control
# autopilot pitch control
# parking brake
# engine alternate air
# cowl flaps
# instrument lights dimmer
# fuel flow meter
# exhaust gas temperature (EGT) left/right engine
# DME frequency source (NAV1/Hold/NAV2) and ON/OFF
# DME indicator
# HSI gyro control
# ADF radio
# KX165 COM2/NAV2 radio
# KX165 COM1/NAV1 radio
# GMA340 intercom
# surface deice (boots)
# wing ice inspection light
# prop deice
# prop deice control gauge
# windshield deice
# annunciator with test button
# gear warning light
# autopilot capture light
# flap lever
# autopilot mode
# gyro pressure
# cicruit breaker panel
# magnetic compass
# fuel selectors - forward: on, center: off, backwards: cross-feed
# elevator trim
# rudder trim

= References =
{{Appendix}}
= Related content =
* [[Piper PA34-200T Seneca II]]
* [[Seneca II Checklist]]
* [[Seneca II HOWTO]]
[[fr:Seneca II Panel Reference]]

[[Category:Piper PA34-200T Seneca II]]

Seneca II Panel Reference

2018-04-02T16:35:33Z

Rodolfo: /* Related content */

This is a quick reference to the instruments and controls in the Seneca's cockpit. (Piper PA34-200T Seneca II)
= The Controls of the Seneca II =
[[File:Seneca_II_reference_left.jpg|thumb|left|Pilot's Panel]]
[[File:Seneca_II_reference_right.jpg|thumb|left|Co-Pilot's Panel]]
[[File:Seneca_II_reference_fuel_trim.jpg|thumb|left|Fuel-Trim Console]]
 

# magneto - left engine
# magneto - right engine
# starter - press left for left engine, right for right engine
# primer - left/right engine
# taxi/landing lights
# nav lights
# anit collision lights - left half: fin (beacon), right half: wing (strobes)
# pitot and stall warning heat
# fuel boost pumps - up: high, down: low, center: off
# battery master
# alternator on/off
# switch panel lights dimmer (noop)
# clock
# airspeed indicator
# attitude indicator (artificial horizon)
# altimeter (barometric)
# radar altimeter
# adf indicator
# turn coordinator
# horizontal situation indicator (hsi)
# vertical speed indicator (vsi)
# vor/ils indicator NAV2
# alternator ampere meter (shows alternator load)
# cylinder head temperature
# oil temperature
# oil pressure
# fuel
# RPM left engine
# dual manifold pressure gauge
# RPM right engine
# landing gear lever and emergency gear extension
# landing gear indicator
# autopilot control
# autopilot pitch control
# parking brake
# engine alternate air
# cowl flaps
# instrument lights dimmer
# fuel flow meter
# exhaust gas temperature (EGT) left/right engine
# DME frequency source (NAV1/Hold/NAV2) and ON/OFF
# DME indicator
# HSI gyro control
# ADF radio
# KX165 COM2/NAV2 radio
# KX165 COM1/NAV1 radio
# GMA340 intercom
# surface deice (boots)
# wing ice inspection light
# prop deice
# prop deice control gauge
# windshield deice
# annunciator with test button
# gear warning light
# autopilot capture light
# flap lever
# autopilot mode
# gyro pressure
# cicruit breaker panel
# magnetic compass
# fuel selectors - forward: on, center: off, backwards: cross-feed
# elevator trim
# rudder trim

= References =
{{Appendix}}
= Related content =
* [[Piper PA34-200T Seneca II]]
* [[Seneca II Checklist]]
* [[Seneca II HOWTO]]
[[fr:Seneca II Panel Reference]]

[[Category:Piper PA34-200T Seneca II]]

Spoken ATC

2018-03-24T23:38:14Z

Rodolfo:

{{infobox subsystem
|image = Spoken-ATC-Screenshot.jpg
|name = Spoken ATC
|started = 07/2017
|description = Spoken ATC
|status = Under active development as of 07/2017
|maintainers = {{usr|Rodolfo}}
|developers = Rodolfo (rleibner on the forum)
}}

The module is not intended to compete with FGComm, Festival or other similar features.
On the contrary, its use is indicated if these are not available (eg, few hardware resources, no Internet connection, etc.) <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=312968#p312968
|title = <nowiki> ATC </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Jun 22nd, 2017
|added = Jun 22nd, 2017
|script_version = 0.40
}}</ref>

[[Spoken ATC]] allows the pilot to listen to the directives of the ''Air Traffic Controller''.

= Preface =
'''Typically''', you should tune the ATC-station frequency and make a request by pressing "'''<'''" key. You may hear something like: 

* ''"Charlie X-ray Bravo Echo X-ray , this is Montevideo Carrasco International tower. QNH 1024 or 30 point 24 inches. Join left pattern Runway 1 9 and report."''

So, you enter in the base leg and press "'''<'''" again:

* ''"Charlie X-ray Bravo Echo X-ray , Wind 1 5 0 degrees, 3 knots. Runway 1 9 cleared to land."''

After landing and while you are braking, you press "'''<'''" once more:

* ''"Charlie X-ray Bravo Echo X-ray , Exit Runway at first taxiway and contact Ground 121 point 82."''

That is only an example of standard '''VFR Phraseology'''
<ref>{{cite web
|url = http://wiki.flightgear.org/ATC_phraseology |title = wiki.flightgear.org/ATC_phraseology
}}</ref>
that you can expect from '''Spoken ATC'''. 

= How to install =
{{note | This is the latest version, v.2.2 (Ago 31, 2017) }}
If your FGFS version accepts [[Addons]], you can download this feature from [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/SpokenATC Sourceforge]. Read the [[FGAddon#Obtaining_aircraft|directions]] as a reference.

Otherwise, follow this:
#- Download the [https://drive.google.com/file/d/0BzzojFuPdeyMTGNDYmZDcEljQkU/view?usp=sharing spoken_atc.zip]. There you will find a "''spoken_atc.nas''" file and a "''spoken_atc''" directory with 6 files inside.
#- Extract all into the ''[[$FG_HOME]]/Nasal'' directory '''(keeping the directory structure !)'''.
#- Edit the ''[[$FG_ROOT]]/keyboard.xml'' file and include the following lines in order to bind
<ref>{{cite web
|url = http://wiki.flightgear.org/Howto:Reassign_keyboard_bindings
|title = wiki.flightgear.org/Howto:Reassign_keyboard_bindings
}}</ref>
the "'''<'''" key:
<syntaxhighlight lang="xml">
<key n="60">
<name>less-than</name>
<desc>Spoken ATC</desc>
<binding>
<command>nasal</command>
<script><![CDATA[
spoken_atc.speak(15);
]]>
</script>
</binding>
</key>
</syntaxhighlight>

And that's all ! 
If you prefer, you can bind an unused joystick button too. 

= How to use it =
Launch FlighGear (or re-start it) and tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information''),
and press the "'''>'''" key to transmit your request. 
You will hear the ATC's answer according the standard VFR phraseology, depending on your current position, weather and previous messages:
* If you are on ground =>
** The code interprets it's a taxi request (if you are far from the runway or you've just landed),
** or a take-off request (if you are on the correct Runway or at his holding point).
* If you are flying =>
** The code interprets it's an approach request (if you tunned an APP station),
** or a landing request (if you tunned a TWR station),
** or a departure request (if you tunned a DEP station. and you are climbing after a take-off). 

Note that only TWR stations can deliver landing or take-off clearances, and only GND or TWR stations can deliver taxiing ones. 
Where there is not a specific GND or APP-DEP freq., TOWER can take their tasks. 
If they do exist, TWR will redirect to the specific frequency. 

Only at initial contact, the ATC message includes his station name & type, and the current QNH. 
APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR). 
TWR stations will give instructions to join pattern or make direct final (depending on your position). 
= Tips =

== A realistic behavior ==
To achieve realistic behavior, follow a logical sequence of communications, viz.:
* Contact GND (or TWR) prior to taxiing.
* Contact TWR prior to take-off or land.
* Contact DEP (if available) after take-off to leave the CTR.
* Contact APP (if available) prior to enter the CTR.
* etc, etc.
== On screen voice ==
If the writen messages bother you, when binding (see above) you can call the function as
<syntaxhighlight lang="xml">
<script> <![CDATA[ spoken_atc.speak(n); ]]> </script> </syntaxhighlight>
with '''n''' seconds you want, even 0 meaning no messages at all. 

= Phraseology customization =
You can customize the phraseology by editing the "''phraseology.xml''" file. 
There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').
=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either " or ' .
* Punctuation is meaningfull. }}
=== Substitutions ===
Strings starting by '''%''' will call some '''property value'''.
In the example above replace "'''day'''" by "'''% /sim/startup/time-offset-type'''". 
Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.
{{note |
* The called property must be a string.}}
=== Concatenation ===
Strings starting by '''~''' will append the sentence with another one.
Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "'' 

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility..
Better? Fine, but what about the message on the screen?
Include a tag with the pattern <replace type="string">'''old''':'''new'''</replace> :
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight> 

Besides that, you can call the ''spoken_atc.say()'' function at runtime to check your customization. 
=== spoken_atc.say() function ===
You can ... [TODO]

 

<big>And remember this is '''VFR''': heed the instructions of the ATC but '''keep your eyes wide open !'''</big>

= Ground Controlled Approaches =
{{See also|Howto:Implementing a simple GCA system}}

= References =
{{Appendix}}

[[Category:FlightGear add-ons]]
[[Category:Air Traffic Control]]

Air traffic control

2018-03-24T23:34:52Z

Rodolfo: /* Related content */

{{stub}}

'''Air traffic control''' (ATC) is a service mostly provided by ground-based controllers who direct aircraft on the ground and in the air. The primary purpose of ATC systems worldwide is to separate aircraft to prevent collisions, to organize and expedite the flow of traffic, and to provide information and other support for pilots when able. In some countries, ATC may also play a security or defense role (as in the United States), or actually be run entirely by the military (as in Brazil).

== Related content ==
* [[ATC phraseology]] lists common phraseology and their meanings.
* [[Spoken_ATC]] allows the pilot to listen to the directives of the Air Traffic Controller.

== ATC in FlightGear multi-player ==

To know if an area is controlled or booked:
*Check for announced ATC sessions on [http://flightgear-atc.alwaysdata.net/ Lenny's website].
*Check the Pilot List in FlightGear or the [[MPMap|Multiplayer map]]. Usually, controllers:
** have a callsign ''XXXX_DE'', ''XXXX_GN'', ''XXXX_TW'' or ''XXXX_AP'' (where ''XXXX'' is the ICAO code of the airport they are manning);
** generally use ''[[OpenRadar]]'' or ''[[ATC-pie]]'', which appear as aircraft models on the map, or older ''ATC-*'' named models.

=== For pilots ===

* [[ATC Tutorial]]
* [[ATC best practices#For pilots|Best practices]]
* [[SquawkGear|Connecting to Vatsim]]

=== For controllers ===

* [[ATC best practices#For controllers|Best practices]]
* "[http://flightgear-atc.alwaysdata.net Lenny's website]" is today's ''de facto'' ATC platform featuring a [[Flight_planning|flight plan]] data base, tutorials and resources, software downloads, and a schedule where ATCs announce their session and let pilots know when and which airport will be controlled

Software for controlling on FlightGear:
* Standalone programs for more realistic experience: [[OpenRadar]], [[ATC-pie]]
* FG aircrafts like [[ATC-FS]], an ATC model with flight strips

[[Category:Air Traffic Control]]

Communications

2018-03-24T23:32:01Z

Rodolfo: /* Air Traffic Control */

== CTAF, UNICOM, and MF ==
Airports without a control tower (or other air-traffic facility) normally publish a standard frequency for pilots to communicate with each-other: in the US, for example, this is called the ''Common Traffic Advisory Frequency'' (CTAF), and in Canada, it is called ''Aerodrome Traffic Frequency'' (ATF). When making calls on the CTAF, the pilot addresses them to "Traffic" (e.g. "Ogdensburg Traffic, Grob 123 downwind for runway 09").

These airports may also have a facility that is (sometimes) staffed by someone who is not an air-traffic controller or flight-services specialist, for example, a dispatcher at a flight school, or a fuel operator at an FBO. These people cannnot give official clearances, but they can often provide a '''field advisory''' including the current temperature, altimeter setting, wind, runway surface condition, fuel availability, and any known traffic, and can also provide radio checks and similar services. The frequency for obtaining the advisory is called the UNICOM (''Universal Communications'').

Most of the time, the CTAF and UNICOM frequencies are the same, but they can occasionally be different. The pilot should address only specific requests to "UNICOM" (e.g. "Brockville UNICOM, this is Cessna ABC, radio check seat one."). All position reporting should be addressed to "Traffic" over the CTAF; otherwise, the poor UNICOM operator will keep running to the mic thinking that someone is making a request.

Note that many airports have control towers that are not open 24/7. When the control tower is closed, the tower frequency will typically become a CTAF, and pilots do their own position reporting, as at any uncontrolled field.

In Canada and some other countries, when talking over the CTAF/ATS is required, it is referred to as the MF (''Mandatory Frequency''), and will often be monitored by a flight-services specialist. The MF is typically for limited hours, and outside of those, it also becomes a CTAF. If there is an FSS specialist monitoring the MF, then the pilot will address calls to "Radio" (e.g. "Kingston Radio, Cherokee FBJO turning left base 19."); otherwise, the pilot will address them to "Traffic", as with the CTAF.

Even without an MF, it is generally recommended that pilots of aircraft having radio equipment permitting two-way communications should contact the Airport UNICOM to obtain advisory information, and announce their intentions over the CTAF when within ten (10) miles of the Airport. Pilots are also encouraged to maintain a listening watch on the frequency when operating within a ten mile radius of the Airport. All departing aircraft shall announce on the CTAF their intention and runway to be used for departure.

On initial contact, pilots report altitude, aircraft type and identification, and location relative to the airport and state their intention, to land or overfly.

Pilots give position reports on downwind and final approach, and will often make an optional call on the base leg as well.

=== FlightGear CTAF ===
FlightGear does not fully implement CTAF entirely. CTAF works best in multiplayer, where you actually have listeners (though in real life, pilots often broadcast blind over a CTAF with no listeners, too).

* To access CTAF or UNICOM, press the dash key (-) to enter the radio chat menu. Press the number that corresponds to '[XXX TRAFFIC]'
(where 'XXX' corresponds to the airport you are closest), then choose your message.

== Air Traffic Control ==
{{Main article|Air Traffic Control}}

[[FlightGear]] provides various systems for [[ATC]] experience.

* '''ATC chatter''' (enable "Chatter" from the <tt>File > Sound Configuration</tt> dialog): plays random records of real ATC communications, probably best left disabled if going for multi-player mode with voice communications
* '''ATIS''' generated from current METAR (tick the somewhat misleadingly named "ATC" sound configuration option): set COM1 to the ATIS frequency of the closest airport to hear a faint broadcast automatically generated by FlightGear—in a controlled multiplayer session and with FGCom turned on, you may hear a proper ATIS if it was recorded by the ATC, so always tune in first!
* '''[[FGCom]]''' (enable it from the multiplayer menu): for voice communications over the [[Howto: Multiplayer|multiplayer]] network.
* '''[[Spoken_ATC]]''' (available as addon): allows to listen to the directives of the Air Traffic Controller.


== ATIS ==
The Automatic Terminal Information Service is broadcast from most airports, informing about active runways, weather and conditions, exceptional airport information, etc. It is typically recorded every half-hour by controllers and looped over on a published frequency for pilots to listen before making contact.

== Tuning ==
Most radio racks have similar controls. As an example look at the [[Kx165]] VHF communication transceiver and VHF navigation receiver.

== Transponder ==
Wikipedia: [http://en.wikipedia.org/wiki/Transponder_code Transponder]

== External link ==
* [http://www.faa.gov/air_traffic/publications/atpubs/aim/ FAA's Aeronautical Information Manual]

{{Understanding}}

[[de:Kommunikation]]
[[es:Communications]]

[[Category:Air Traffic Control]]
[[Category:Multiplayer]]
[[Category:FlightGear wiki:Needs summary or introduction]]

Addon

2018-03-16T20:38:29Z

Rodolfo: /* List of Addons */

{{Stub}}
[[File:Jigsaw.png|thumb]]
{{forum|10000|FlightGear Addons}}
== Background ==
{{See also|Howto:Creating a simple modding framework}}

ATC chatter was removed in 2015, see fgdata commit: [https://sourceforge.net/p/flightgear/fgdata/ci/81607f734e13add9be02816ddaec305d05bc4e47/ 81607f734e13add9be02816ddaec305d05bc4e47]

and the devel list messages referenced in the commit log.
the other relevant commit is this: b60736ba7add2a7cd39af3d8a974d5be3ea46e8b
It would not be very difficult to restore this functionality, or even generalize/improve it significantly (which was the scope of the original discussion on the devel list)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=288388#p288388
|title = <nowiki> Re: Whatever happened to radom radio </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Jun 11th, 2016
|added = Jun 11th, 2016
|script_version = 0.40
}}</ref>

The restored functionality could be distributed as a tarball that is extracted into $FG_ROOT - alternatively, into $FG_HOME, because Nasal files there are treated as overlays, which basically means that you can install user-specific extensions there without having to tamper with $FG_ROOT, it would only take very minor changes to turn the chatter feature into a corresponding "addon" - not unlike fgcamera ...<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=288392#p288392
|title = <nowiki> Re: Whatever happened to radom radio </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Jun 11th, 2016
|added = Jun 11th, 2016
|script_version = 0.40
}}</ref>

we should absolutely stop telling anyone to edit preferences.xml in FG_ROOT; any documentation or advice which says to should be changes ASAP. <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=192632#p192632
|title = <nowiki> Re: NavCache:init failed:Sqlite error:Sqlite API abuse </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Oct 26th, 2013
|added = Oct 26th, 2013
|script_version = 0.40
}}</ref>

As of 12/2017, the addon API is in the process of being significantly updated <ref>https://sourceforge.net/p/flightgear/mailman/message/36146017/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36150159/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36150444/</ref>

== Good to know ==
this API does nothing more than loading a overlay XML into the property tree and starts a well known Nasal function<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314620#p314620
|title = <nowiki> Re: New Feature: Addon - "API" </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

The new addon "API" lets you add a config.xml to override the settings in defaults.xml.

That easily allows to
* Override key bindings (as in the spoken atc addon)
* Add or override autopilots and property rules
* And of course introduce XML-statemachines

Unless your really want to add/change/remove those at runtime, this should cater for most use cases.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314902#p314902
|title = <nowiki> Re: Spoken </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 23rd, 2017
|added = Jul 23rd, 2017
|script_version = 0.40
}}</ref>

We have some instructions how to use SVN [[FGAddon|in our wiki]]. It covers mostly aircraft development but the workflow is pretty much the same for addons.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314647#p314647
|title = <nowiki> Re: Spoken ATC </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

* [[Property tree]]
* [[PropertyList XML File]]
* [[FlightGear configuration via XML]]
* [[Properties persistent between sessions]]
* [[FlightGear_configuration_via_XML#preferences.xml]]
* [[Nasal]]

== Overlays ==

Torsten ended up using a fairly clever method to come up with this idea for implementing addon support via PropertyList-XML overlays loaded via the --config argument - however, that also brings with it all the power for conflicting with stuff you are loading using the same mechanism, and/or any defaults you have customied. So just be aware of how this works - and again, kudos to Torsten for coming up with such a fancy approach to make this work, despite people arguing for the better part of a decade that FlightGear would not have "proper addon/modding" support" ... ;-)
With that being said, it would probably be a good idea to formalize the whole method and stop using tons of embedded Nasal, and instead document/favor the use of io.load_nasal() and/or io.include() to load Nasal code from the addon directory.
Equally, such code should ideally wrap setlistener and settimer/maketimer to honor the /sim/signal "events" - but apart from that, it's a really clever idea<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=295617#p295617
|title = <nowiki> Re: Whatever happened to radom radio chatter?? </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Sep 27th, 2016
|added = Sep 27th, 2016
|script_version = 0.40
}}</ref>

== API ==

We now have a simple API to add addons to FlightGear without the need to mess around with FGData/Nasal or FGHome/Nasal directories. FlightGear now accepts the command line switch --addon=/path/to/some/addon (note: command line switch is just that: a command line switch - not an option to be entered into the launcher). fgfs (through options.cxx) takes care of
* creating a property under /addons/addon[n]/path=/path/to/some/addon
* adding /path/to/some/addon/config.xml as a config file (same as --config=/path/to/some/addon/config.xml)
* adding /path/to/some/addon to the list of allowed directories (same as --fg-aircraft=/path/to/some/addon)

The addon may be installed anywhere on your hard disk and it needs at least two files:
* config.xml - a standard PropertyList to be used to populate or modify the property tree. (Same as to be used in --config=foo.xml)
* main.nas - the Nasal hook for the logic. This file needs a function called main() which will be called from the global addon initialier (FGData/addons.nas)

It is pretty simple but does it's job nicely with our two addons we currently have in FGAddon (ATCChatter and SpokenATC). There is a /very/ simple Skeleton addon available to be used as a boilerplate here: https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/Skeleton/ As always: feedback is much appreciated. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35951307/
|title = <nowiki> [Flightgear-devel] Simple API for creating FlightGear addons/plugins </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Jul 18th, 2017
|added = Jul 18th, 2017
|script_version = 0.40
}}</ref> <ref> {{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314563#p314563
|title = <nowiki> New Feature: Addon - "API" </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 18th, 2017
|added = Jul 18th, 2017
|script_version = 0.40
}}</ref>

Triggered by this addon, Torsten has overhauled the addon "API" to make it a little easier to use.

Along with this, he added the spoken ATC feature as an addon to fgaddon: https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/SpokenATC/
It is now very easy to use (given you have FlightGear compiled from git HEAD or use FlightGear 2017.3.x or later.

you need at least these commits:

FlightGear: https://sourceforge.net/p/flightgear/flightgear/ci/f6698a0b1f9e8c0791314aa09cbe1625927ef3ff/

FGData: https://sourceforge.net/p/flightgear/fgdata/ci/5c1f4a69f131a55521050f4631b8fda42f050dd2/
* Get the addon from https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/SpokenATC/
* start flightgear with --addon=/your/full/path/to/SpokenATC

done.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314562#p314562
|title = <nowiki> Re: Spoken ATC </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 18th, 2017
|added = Jul 18th, 2017
|script_version = 0.40
}}</ref>

== Implementation ==
For the time being, the addon.nas module will:
* initialize addons configured with --addon=foobar command line switch
* loop over /addons/addon[n] nodes
* get root path in /addons/addon[n]/path property (set by options.cxx from --addon=/foo/bar)
* load main.nas therein into namespace __addon[n]__
* call function main() from that main.nas with addon-path as arg

It depend on a change to options.cxx to accept an optional --addon argument <ref>https://sourceforge.net/p/flightgear/flightgear/ci/f6698a0b1f9e8c0791314aa09cbe1625927ef3ff/</ref>

== List of Addons ==
* [[Landing Rate addon]] [https://forum.flightgear.org/viewtopic.php?f=6&t=33101&p=327787#p327787]
* [[YASim Development Tools]] (by jsb)
* [[Model Cockpit View]]
* [[FGPlot]]
* ATC Chatter (ported by Torsten) {{progressbar|100}}
* [[Spoken ATC]] (ported by Torsten <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314095#p314095
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 10th, 2017
|added = Jul 10th, 2017
|script_version = 0.40
}}</ref>)
* [[Oscilloscope_addon]]
* [[PAR_instrument]] (Precision Approach Radar and Ground Controlled Approach)
* [[FGCamera]] (work in progress by Torsten <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314650#p314650
|title = <nowiki> Re: Alternative camera control </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref> <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=319804#p319804
|title = <nowiki> Re: New Feature: Addon - "API" </nowiki>
|author = <nowiki> slawekmikula </nowiki>
|date = Oct 2nd, 2017
|added = Oct 2nd, 2017
|script_version = 0.40
}}</ref>)
* [[Ground Services]] (ported by ThomasS<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316400#p316400
|title = <nowiki> Re: </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Aug 12th, 2017
|added = Aug 12th, 2017
|script_version = 0.40
}}</ref>)
* cockpit-view (work in progress by wkitty42 <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316498#p316498
|title = <nowiki> Re: </nowiki>
|author = <nowiki> wkitty42 </nowiki>
|date = Aug 13th, 2017
|added = Aug 13th, 2017
|script_version = 0.40
}}</ref>)
* [[A Failure Management Framework for FlightGear]]

== Ideas ==

=== Catalog & Package Manager support ===

if this works with more complex, pre-existing addons such as [[Bombable]], where the file layout is a replica of the old FGData layout, these types of mature addons might be better as SourceForge FlightGear sub-projects rather than being copied into FGAddon. Maybe the config file and nasal script could be used to automate the installation process ?<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35953179/
|title = <nowiki> Re: [Flightgear-devel] Simple API for creating FlightGear
addons/plugins </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>
The [[Bombable]] addon is one of the most popular addons out there, and a large number of aircraft in FGAddon have bombable support, so it is worth not forgetting about. Especially if the addon system one day becomes automated through a [[Catalog metadata|catalog.xml type system]]<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35953650/
|title = <nowiki> Re: [Flightgear-devel] Simple API for creating FlightGear
addons/plugins </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

== References ==
{{Appendix}}

Skinnable canvas window

2018-03-12T22:14:18Z

Rodolfo:

[[File:Precision Approach Radar.png|thumb|left|Stand-alone PAR instrument]]{{Template:Canvas Navigation}}
'''skinnable.nas''' implements the ''skinnable'' class. It inherits from ''canvas''. 
Skinnable objects enables the creation of Graphic UIs overlapping images with hotspot areas. ''[[Oscilloscope_addon|Oscilloscope]]'' and ''[[PAR_instrument|PAR]]'' addons are examples of its use.

== Constructor ==
=== new: func(size, title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <syntaxhighlight lang="nasal"> var sk = canvas.skinnable.new([575,290]);</syntaxhighlight>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));</syntaxhighlight>

=== listen_mouse_events: func(caller, Hots) ===
: '''Hots''' as vector of hashes as: 
* {type:"click", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''>, parms:<''parms''> }
* {type:"wheel", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''> }
* {type:"cursor", x:<''x''>, y:<''y''>, style:<''style''>, tol:<''tol''>, tip:<''tipText''> }
* {type:"tip", x:<''x''>, y:<''y''>, text:<''tipText''>, tol:<''tol''> }
: where ''x'' and ''y'' are the local coords of the hotspot.
::: ''action'' (as string) is a function. The event will call the '''''caller['action']''''' method.
::: ''tol'' is the tolerance, the hotspot radious.
::: ''parms'' (as vector, scalar or nil) will be passed to ''caller.action()'' as arguments.
::: ''style'' (as string) is the cursor style to be used over the hotspot.
::: ''tipText'' is the string to be shown over the hotspot. Use an empty string for none.
 
: e.g. (borrowed from Oscilloscope) <syntaxhighlight lang="nasal">var wheelHots = [
{type:'wheel', x:417, y:82, action:'set1Gain', tol:12 },
{type:'cursor', x:417, y:82, style:'hand', tol:12, tip:'Ch-1 Gain' },
{type:'click', x:427, y:82, action:'set1Gain', tol:6 , parms:1 },
{type:'click', x:403, y:82, action:'set1Gain', tol:6 , parms:-1 },...
];
me.sk.listen_mouse_events(caller:me, Hots:Hots);</syntaxhighlight>

== Members ==

=== skinnable.size ===
: returns the window size as [''width, height''].
=== skinnable.window ===
: returns the canvas.Window object.
=== skinnable.canvas ===
: returns the canvas object.
=== skinnable.root ===
: returns the ''root'' group/layer.

: e.g. <syntaxhighlight lang="nasal">
var sk = canvas.skinnable.new([575,290]);
sk.window.set("title","oscilloscope" ).clearFocus();
sk.canvas.set("background", '#224422');
myGroup = sk.root.createChild("group");
</syntaxhighlight>

Skinnable canvas window

2018-03-12T21:48:27Z

Rodolfo:

[[File:Precision Approach Radar.png|thumb|left|Stand-alone PAR instrument]]{{Template:Canvas Navigation}}
'''skinnable.nas''' implements the ''skinnable'' class. It inherits from ''canvas''. 
Skinnable objects enables the creation of Graphic UIs overlapping images with hotspot areas. ''Oscilloscope'' and ''PAR'' addons are examples of its use.

== Constructor ==
=== new: func(size, title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <syntaxhighlight lang="nasal"> var sk = canvas.skinnable.new([575,290]);</syntaxhighlight>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));</syntaxhighlight>

=== listen_mouse_events: func(caller, Hots) ===
: '''Hots''' as vector of hashes as: 
* {type:"click", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''>, parms:<''parms''> }
* {type:"wheel", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''> }
* {type:"cursor", x:<''x''>, y:<''y''>, style:<''style''>, tol:<''tol''>, tip:<''tipText''> }
* {type:"tip", x:<''x''>, y:<''y''>, text:<''tipText''>, tol:<''tol''> }
: where ''x'' and ''y'' are the local coords of the hotspot.
::: ''action'' (as string) is a function. The event will call the '''''caller['action']''''' method.
::: ''tol'' is the tolerance, the hotspot radious.
::: ''parms'' (as vector, scalar or nil) will be passed to ''caller.action()'' as arguments.
::: ''style'' (as string) is the cursor style to be used over the hotspot.
::: ''tipText'' is the string to be shown over the hotspot. Use an empty string for none.
 
: e.g. (borrowed from Oscilloscope) <syntaxhighlight lang="nasal">var wheelHots = [
{type:'wheel', x:417, y:82, action:'set1Gain', tol:12 },
{type:'cursor', x:417, y:82, style:'hand', tol:12, tip:'Ch-1 Gain' },
{type:'click', x:427, y:82, action:'set1Gain', tol:6 , parms:1 },
{type:'click', x:403, y:82, action:'set1Gain', tol:6 , parms:-1 },...
];
me.sk.listen_mouse_events(caller:me, Hots:Hots);</syntaxhighlight>

== Members ==

=== skinnable.size ===
: returns the window size as [''width, height''].
=== skinnable.window ===
: returns the canvas.Window object.
=== skinnable.canvas ===
: returns the canvas object.
=== skinnable.root ===
: returns the ''root'' group/layer.

: e.g. <syntaxhighlight lang="nasal">
var sk = canvas.skinnable.new([575,290]);
sk.window.set("title","oscilloscope" ).clearFocus();
sk.canvas.set("background", '#224422');
myGroup = sk.root.createChild("group");
</syntaxhighlight>

Skinnable canvas window

2018-03-12T21:45:17Z

Rodolfo:

[[File:Precision Approach Radar.png|thumb|Stand-alone PAR instrument]]{{Template:Canvas Navigation}}
skinnable.nas implements the ''skinnable'' class. It inherits from ''canvas''. 
Skinnable objects enables the creation of Graphic UIs overlapping images with hotspot areas. Oscilloscope and PAR addons are examples of its use.

== Constructor ==
=== new: func(size, title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <syntaxhighlight lang="nasal"> var sk = canvas.skinnable.new([575,290]);</syntaxhighlight>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));</syntaxhighlight>

=== listen_mouse_events: func(caller, Hots) ===
: '''Hots''' as vector of hashes as: 
* {type:"click", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''>, parms:<''parms''> }
* {type:"wheel", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''> }
* {type:"cursor", x:<''x''>, y:<''y''>, style:<''style''>, tol:<''tol''>, tip:<''tipText''> }
* {type:"tip", x:<''x''>, y:<''y''>, text:<''tipText''>, tol:<''tol''> }
: where ''x'' and ''y'' are the local coords of the hotspot.
::: ''action'' (as string) is a function. The event will call the '''''caller['action']''''' method.
::: ''tol'' is the tolerance, the hotspot radious.
::: ''parms'' (as vector, scalar or nil) will be passed to ''caller.action()'' as arguments.
::: ''style'' (as string) is the cursor style to be used over the hotspot.
::: ''tipText'' is the string to be shown over the hotspot. Use an empty string for none.
 
: e.g. (borrowed from Oscilloscope) <syntaxhighlight lang="nasal">var wheelHots = [
{type:'wheel', x:417, y:82, action:'set1Gain', tol:12 },
{type:'cursor', x:417, y:82, style:'hand', tol:12, tip:'Ch-1 Gain' },
{type:'click', x:427, y:82, action:'set1Gain', tol:6 , parms:1 },
{type:'click', x:403, y:82, action:'set1Gain', tol:6 , parms:-1 },...
];
me.sk.listen_mouse_events(caller:me, Hots:Hots);</syntaxhighlight>

== Members ==

=== skinnable.size ===
: returns the window size as [''width, height''].
=== skinnable.window ===
: returns the canvas.Window object.
=== skinnable.canvas ===
: returns the canvas object.
=== skinnable.root ===
: returns the ''root'' group/layer.

: e.g. <syntaxhighlight lang="nasal">
var sk = canvas.skinnable.new([575,290]);
sk.window.set("title","oscilloscope" ).clearFocus();
sk.canvas.set("background", '#224422');
myGroup = sk.root.createChild("group");
</syntaxhighlight>

Skinnable canvas window

2018-03-12T21:29:38Z

Rodolfo:

[[File:Precision Approach Radar.png|thumb|Stand-alone PAR instrument]]{{Template:Canvas Navigation}}
skinnable.nas implements the ''skinnable'' class. It inherits from ''canvas''.

== Constructor ==
=== new: func(size, title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <syntaxhighlight lang="nasal"> var sk = canvas.skinnable.new([575,290]);</syntaxhighlight>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));</syntaxhighlight>

=== listen_mouse_events: func(caller, Hots) ===
: '''Hots''' as vector of hashes as: 
* {type:"click", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''>, parms:<''parms''> }
* {type:"wheel", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''> }
* {type:"cursor", x:<''x''>, y:<''y''>, style:<''style''>, tol:<''tol''>, tip:<''tipText''> }
* {type:"tip", x:<''x''>, y:<''y''>, text:<''tipText''>, tol:<''tol''> }
: where ''x'' and ''y'' are the local coords of the hotspot.
::: ''action'' (as string) is a function. The event will call the '''''caller['action']''''' method.
::: ''tol'' is the tolerance, the hotspot radious.
::: ''parms'' (as vector, scalar or nil) will be passed to ''caller.action()'' as arguments.
::: ''style'' (as string) is the cursor style to be used over the hotspot.
::: ''tipText'' is the string to be shown over the hotspot. Use an empty string for none.
 
: e.g. (borrowed from Oscilloscope) <syntaxhighlight lang="nasal">var wheelHots = [
{type:'wheel', x:417, y:82, action:'set1Gain', tol:12 },
{type:'cursor', x:417, y:82, style:'hand', tol:12, tip:'Ch-1 Gain' },
{type:'click', x:427, y:82, action:'set1Gain', tol:6 , parms:1 },
{type:'click', x:403, y:82, action:'set1Gain', tol:6 , parms:-1 },...
];
me.sk.listen_mouse_events(caller:me, Hots:Hots);</syntaxhighlight>

== Members ==

=== skinnable.size ===
: returns the window size as [''width, height''].
=== skinnable.window ===
: returns the canvas.Window object.
=== skinnable.canvas ===
: returns the canvas object.
=== skinnable.root ===
: returns the ''root'' group/layer.

: e.g. <syntaxhighlight lang="nasal">
var sk = canvas.skinnable.new([575,290]);
sk.window.set("title","oscilloscope" ).clearFocus();
sk.canvas.set("background", '#224422');
myGroup = sk.root.createChild("group");
</syntaxhighlight>

File:Precision Approach Radar.png

2018-03-12T21:26:01Z

Rodolfo: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Stand-alone PAR instrument}}
|date=2018-03-12
|source={{own}}
|author=[[User:Rodolfo|Rodolfo]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Canvas GUI]]
[[Category:Canvas]]

Skinnable canvas window

2018-03-08T16:00:55Z

Rodolfo: /* Methods */

{{Template:Canvas Navigation}}

skinnable.nas implements the ''skinnable'' class. It inherits from ''canvas''.
== Constructor ==
=== new: func(size, title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <syntaxhighlight lang="nasal"> var sk = canvas.skinnable.new([575,290]);</syntaxhighlight>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));</syntaxhighlight>

=== listen_mouse_events: func(caller, Hots) ===
: '''Hots''' as vector of hashes as: 
* {type:"click", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''>, parms:<''parms''> }
* {type:"wheel", x:<''x''>, y:<''y''>, action:<''action''>, tol:<''tol''> }
* {type:"cursor", x:<''x''>, y:<''y''>, style:<''style''>, tol:<''tol''>, tip:<''tipText''> }
* {type:"tip", x:<''x''>, y:<''y''>, text:<''tipText''>, tol:<''tol''> }
: where ''x'' and ''y'' are the local coords of the hotspot.
::: ''action'' (as string) is a function. The event will call the '''''caller['action']''''' method.
::: ''tol'' is the tolerance, the hotspot radious.
::: ''parms'' (as vector, scalar or nil) will be passed to ''caller.action()'' as arguments.
::: ''style'' (as string) is the cursor style to be used over the hotspot.
::: ''tipText'' is the string to be shown over the hotspot. Use an empty string for none.
 
: e.g. (borrowed from Oscilloscope) <syntaxhighlight lang="nasal">var wheelHots = [
{type:'wheel', x:417, y:82, action:'set1Gain', tol:12 },
{type:'cursor', x:417, y:82, style:'hand', tol:12, tip:'Ch-1 Gain' },
{type:'click', x:427, y:82, action:'set1Gain', tol:6 , parms:1 },
{type:'click', x:403, y:82, action:'set1Gain', tol:6 , parms:-1 },...
];
me.sk.listen_mouse_events(caller:me, Hots:Hots);</syntaxhighlight>

== Members ==

=== skinnable.size ===
: returns the window size as [''width, height''].
=== skinnable.window ===
: returns the canvas.Window object.
=== skinnable.canvas ===
: returns the canvas object.
=== skinnable.root ===
: returns the ''root'' group/layer.

: e.g. <syntaxhighlight lang="nasal">
var sk = canvas.skinnable.new([575,290]);
sk.window.set("title","oscilloscope" ).clearFocus();
sk.canvas.set("background", '#224422');
myGroup = sk.root.createChild("group");
</syntaxhighlight>

PAR instrument

2018-03-01T21:37:34Z

Rodolfo: /* Behind the scene */

{{Infobox addon
|name=Precision Approach Radar Addon
|started=02/2018
|desc= PAR addon
|status=under active development as of 02/2018
|contributors={{Usr|Rodolfo}}
}}

[[File:PAR.png|right|Precision Approach Radar screen]]

<big>Precision Approach Radar (PAR)</big> is a ground instrument conceived primarily to provide the GCA service.
{{WIP|Although still incomplete, the information it contains is valid and available. |nocat=}}
'''PAR''' allows the Ground Controlled Approach (GCA) controller to deliver approach directives to the requesting aircraft. 
(see [[Howto:Implementing_a_simple_GCA_system]])
= Background =
{{FGCquote
|Is there any work on GCA (ground controlled approach) in progress, or have missed it? GCA is surprisingly accurate and easy to use, both as a pilot and a controller. |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=193941#p193941
|title=<nowiki>Re: Spoken ATC</nowiki>
|author=<nowiki>Alant</nowiki>
|date=<nowiki>Sun Ago 13</nowiki>
}}
}}
= What PAR and GCA are =
* https://secretsofcoldwarradar.omeka.net/exhibits/show/cold-war-radar-technology/radar-equipment/ground-controlled-approach-and
* https://aroundthepattern.com/training/ground-controlled-approaches-gca/
* https://en.wikipedia.org/wiki/Ground-controlled_approach
* http://www.rquirk.com/cdnradar/cor/chapter21.pdf

= What can you expect from GCA =

[[File:Gca1.png|left|thumb|Horizontal trajectory when pilot follows GCA instructions]]Arriving in the vicinity of the airport with little or no visibility, the pilot can request the GCA service.
The Controller, assisted by a PAR (''Precision Approach Radar''), will guide you through a safe path (both in heading and in altitude) that will take you to the head of the used runway.[[File:Gca2.png|center|thumb|Vertical trajectory when pilot follows GCA instructions]] 
 
 
 
= How to install =
{{note | This is the latest version (Feb 22, 2018) 

If your FGFS version accepts [[Addons]], you can download this feature from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/PAR/ Addons Repository]. Download all the 12 files into the directory of your choice. 

Launch FlightGear including --addon argument, eg.:
<syntaxhighlight>
fgfs <usual args> --addon=/path/to/PARaddon/</syntaxhighlight>
{{note | From version 2017.4.0, the FG launcher accepts the ''--addon'' option in his ''Settings/Additional Settings'' tab. }}
Otherwise, you can install it as a submodule. Contact the author for further instructions.

And that's all ! 

= How to use it =
When you are about 15 or 20 miles from your destination, tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information'' or at the {{key press|F12}} dialog). 
Press the {{key press|>}} key to see the PAR instrument (you can open as many as you want). Verify the airport and runway destination. 
On the screen you should see not only your plane but all the flying MP/AI in range. Adjust Zoom if necessary. 
Click the {{key press|GCA}} button to request GCA assistance. 
You will hear the GCA's answer ''"<callsign>, this will be a PAR approach to <airport> runway <rwy>."'' 
Now, as you do not want to cheat, you should click the {{key press|hide}} button. (Remember: this PAR is a ground instrument, not a flying one). 
But not worry, once you have landed (or anytime, indeed) you can press the {{key press|>}} key again to visualize and analyze your plotted trajectory. 

Depending on your position and altitude, the GCA will give you a vector towards the base leg or towards the final one. Also will instruct to climb or descend if necessary. 
Follow closely those instructions making standard turns first, and half standard ones when indicated.
Adopt about 90 to 110 kts IAS until you hear ''"Begin descent"'', and configure a "final" atitude then. 
If you are adviced ''"<Well/Slightly> <left/right> of course."'' then make "S" turns to fix that. Little ones if "Slightly", big ones if "Well". 
Correct your vertical speed if you hear ''"<Above/Below> glidepath."''
 
= Phraseology customization =
You can customize the phraseology by editing the "''phraseology.xml''" file. 
There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').
=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either " or ' .
* Punctuation is meaningfull. }}
=== Substitutions ===
Strings starting by '''%''' will call some '''property value'''.
In the example above replace "'''day'''" by "'''% /sim/startup/time-offset-type'''". 
Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.
{{note |
* The called property must be a string.}}
=== Concatenation ===
Strings starting by '''~''' will append the sentence with another one.
Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "'' 

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility..
Better? Fine, but what about the message on the screen?
Include a tag with the pattern <replace type="string">'''old''':'''new'''</replace> :
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight> 
= Roadmap =

* To implement a setting dialog (binded to the {{key press|set}} button) allowing further customizations.(as glideslope, TTS arguments, etc.)
* To improve the terrain ''getVertProfilefunction'' when unloaded tiles are needed. 
* General improvements & optimizations
= Behind the scene =

Supporting all the graphic work:
* [[Canvas Nasal API|Canvas_Nasal_API]]
* plot2D.nas
* graph.nas
* [[Skinnable canvas window]]

( to be continued ... )

Skinnable canvas window

2018-03-01T21:32:19Z

Rodolfo: /* Constructor */

Skinnable canvas window

2018-03-01T21:30:26Z

Rodolfo: /* skinnable.root */

Skinnable canvas window

2018-03-01T21:28:05Z

Rodolfo:

Skinnable canvas window

2018-03-01T21:25:20Z

Rodolfo: /* Methods */

Skinnable canvas window

2018-03-01T21:16:19Z

Rodolfo:

Skinnable canvas window

2018-03-01T21:12:08Z

Rodolfo: /* listen_mouse_clicks: func(object, function) */

{{Template:Canvas Navigation}}

skinnable.nas implements the skinnable class.
== Constructor ==
=== new: func(size,title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <syntaxhighlight lang="nasal"> var sk = canvas.skinnable.new([575,290]);</syntaxhighlight>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));</syntaxhighlight>

=== listen_mouse_clicks: func(object, function) ===
: creates the listener and binds the events to ''function(e)''. Also checks the {{key press |ctrl}} key: ''ctrl-click'' outputs the mouse coordinates.
'''object''' as the calling object. 
'''function''' as the callback function. 
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));
sk.listen_mouse_clicks(object:me, function:me.onClick);
</syntaxhighlight>

Skinnable canvas window

2018-03-01T21:07:13Z

Rodolfo:

{{Template:Canvas Navigation}}

skinnable.nas implements the skinnable class.
== Constructor ==
=== new: func(size,title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <syntaxhighlight lang="nasal"> var sk = canvas.skinnable.new([575,290]);</syntaxhighlight>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));</syntaxhighlight>

=== listen_mouse_clicks: func(object, function) ===
: creates the listener and binds the events to ''function(e)''.
'''object''' as the calling object. 
'''function''' as the callback function. 
: e.g. <syntaxhighlight lang="nasal">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));
sk.listen_mouse_clicks(object:me, function:me.onClick);
</syntaxhighlight>

Skinnable canvas window

2018-03-01T21:03:19Z

Rodolfo: /* addSkin: func(filename) */

{{Template:Canvas Navigation}}

skinnable.nas implements the skinnable class.
== Constructor ==
=== new: func(size,title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <pre style="color: green"> var sk = canvas.skinnable.new([575,290]);</pre>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <pre style="color: green">var sk = canvas.skinnable.new([575,290]);
sk.addSkin("/foo/osc2.png"));</pre>

=== listen_mouse_clicks: func(object, function) ===
: creates the listener and binds the events to ''function(e)''.
'''object''' as the calling object. 
'''function''' as the callback function. 
: e.g. <syntaxhighlight lang="nasal">sk.addSkin("/foo/osc2.png"));
me.sk.listen_mouse_clicks(object:me, function:me.onClick);
</syntaxhighlight>

Skinnable canvas window

2018-03-01T21:01:49Z

Rodolfo: /* Methods */

{{Template:Canvas Navigation}}

skinnable.nas implements the skinnable class.
== Constructor ==
=== new: func(size,title) ===
'''size''' mandatory as [''width, height''] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. <pre style="color: green"> var sk = canvas.skinnable.new([575,290]);</pre>

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
: loads the image file and creates Canvas Image element.
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. <pre style="color: green"> sk.addSkin("/foo/osc2.png"));</pre>
=== listen_mouse_clicks: func(object, function) ===
: creates the listener and binds the events to ''function(e)''.
'''object''' as the calling object. 
'''function''' as the callback function. 
: e.g. <syntaxhighlight lang="nasal">sk.addSkin("/foo/osc2.png"));
me.sk.listen_mouse_clicks(object:me, function:me.onClick);
</syntaxhighlight>

Skinnable canvas window

2018-03-01T20:22:25Z

Rodolfo: /* new: func(size,title) */

Skinnable canvas window

2018-03-01T20:21:47Z

Rodolfo: /* Methods */

Skinnable canvas window

2018-03-01T20:18:32Z

Rodolfo: /* new: func(size,title) */

Skinnable canvas window

2018-03-01T20:14:37Z

Rodolfo: Created page with "{{Template:Canvas Navigation}} skinnable.nas implements the skinnable class. == Constructor == === new: func(size,title) === '''size''' mandatory as [width, height] vector,..."

{{Template:Canvas Navigation}}

skinnable.nas implements the skinnable class.
== Constructor ==
=== new: func(size,title) ===
'''size''' mandatory as [width, height] vector, the window dimension. 
'''title''' optional as string , the window title. Empty by default. 
: e.g. var sk = canvas.skinnable.new([575,290]);

== Methods ==
Skinnable objects includes 2 methods:
=== addSkin: func(filename) ===
'''filename''' as the absolute file path. The file must be a .png or a .jpg image.
: e.g. sk.addSkin("/foo/osc2.png"));

PAR instrument

2018-02-22T20:40:26Z

Rodolfo: /* Roadmap */

[[File:PAR.png|right|Precision Approach Radar screen]]
<big>Precision Approach Radar (PAR)</big> is a ground instrument conceived primarily to provide the GCA service.
{{WIP|Although still incomplete, the information it contains is valid and available. |nocat=}}
'''PAR''' allows the Ground Controlled Approach (GCA) controller to deliver approach directives to the requesting aircraft. 
(see [[Howto:Implementing_a_simple_GCA_system]])
= Background =
{{FGCquote
|Is there any work on GCA (ground controlled approach) in progress, or have missed it? GCA is surprisingly accurate and easy to use, both as a pilot and a controller. |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=193941#p193941
|title=<nowiki>Re: Spoken ATC</nowiki>
|author=<nowiki>Alant</nowiki>
|date=<nowiki>Sun Ago 13</nowiki>
}}
}}
= What PAR and GCA are =
* https://secretsofcoldwarradar.omeka.net/exhibits/show/cold-war-radar-technology/radar-equipment/ground-controlled-approach-and
* https://aroundthepattern.com/training/ground-controlled-approaches-gca/
* https://en.wikipedia.org/wiki/Ground-controlled_approach
* http://www.rquirk.com/cdnradar/cor/chapter21.pdf

= What can you expect from GCA =

[[File:Gca1.png|left|thumb|Horizontal trajectory when pilot follows GCA instructions]]Arriving in the vicinity of the airport with little or no visibility, the pilot can request the GCA service.
The Controller, assisted by a PAR (''Precision Approach Radar''), will guide you through a safe path (both in heading and in altitude) that will take you to the head of the used runway.[[File:Gca2.png|center|thumb|Vertical trajectory when pilot follows GCA instructions]] 
 
 
 
= How to install =
{{note | This is the latest version (Feb 22, 2018) 

If your FGFS version accepts [[Addons]], you can download this feature from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/PAR/ Addons Repository]. Download all the 12 files into the directory of your choice. 

Launch FlightGear including --addon argument, eg.:
<syntaxhighlight>
fgfs <usual args> --addon=/path/to/PARaddon/</syntaxhighlight>
{{note | From version 2017.4.0, the FG launcher accepts the ''--addon'' option in his ''Settings/Additional Settings'' tab. }}
Otherwise, you can install it as a submodule. Contact the author for further instructions.

And that's all ! 

= How to use it =
When you are about 15 or 20 miles from your destination, tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information'' or at the {{key press|F12}} dialog). 
Press the {{key press|>}} key to see the PAR instrument (you can open as many as you want). Verify the airport and runway destination. 
On the screen you should see not only your plane but all the flying MP/AI in range. Adjust Zoom if necessary. 
Click the {{key press|GCA}} button to request GCA assistance. 
You will hear the GCA's answer ''"<callsign>, this will be a PAR approach to <airport> runway <rwy>."'' 
Now, as you do not want to cheat, you should click the {{key press|hide}} button. (Remember: this PAR is a ground instrument, not a flying one). 
But not worry, once you have landed (or anytime, indeed) you can press the {{key press|>}} key again to visualize and analyze your plotted trajectory. 

Depending on your position and altitude, the GCA will give you a vector towards the base leg or towards the final one. Also will instruct to climb or descend if necessary. 
Follow closely those instructions making standard turns first, and half standard ones when indicated.
Adopt about 90 to 110 kts IAS until you hear ''"Begin descent"'', and configure a "final" atitude then. 
If you are adviced ''"<Well/Slightly> <left/right> of course."'' then make "S" turns to fix that. Little ones if "Slightly", big ones if "Well". 
Correct your vertical speed if you hear ''"<Above/Below> glidepath."''
 
= Phraseology customization =
You can customize the phraseology by editing the "''phraseology.xml''" file. 
There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').
=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either " or ' .
* Punctuation is meaningfull. }}
=== Substitutions ===
Strings starting by '''%''' will call some '''property value'''.
In the example above replace "'''day'''" by "'''% /sim/startup/time-offset-type'''". 
Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.
{{note |
* The called property must be a string.}}
=== Concatenation ===
Strings starting by '''~''' will append the sentence with another one.
Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "'' 

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility..
Better? Fine, but what about the message on the screen?
Include a tag with the pattern <replace type="string">'''old''':'''new'''</replace> :
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight> 
= Roadmap =

* To implement a setting dialog (binded to the {{key press|set}} button) allowing further customizations.(as glideslope, TTS arguments, etc.)
* To improve the terrain ''getVertProfilefunction'' when unloaded tiles are needed. 
* General improvements & optimizations
= Behind the scene =

Supporting all the graphic work:
* Canvas-API
* plot2D.nas
* graph.nas
* skinnable.nas

( to be continued ... )

PAR instrument

2018-02-22T20:33:36Z

Rodolfo: /* Phraseology customization */

PAR instrument

2018-02-22T20:17:08Z

Rodolfo: /* What GCA is */

PAR instrument

2018-02-22T20:10:51Z

Rodolfo: /* How to install */

[[File:PAR.png|right|Precision Approach Radar screen]]
<big>Precision Approach Radar (PAR)</big> is a ground instrument conceived primarily to provide the GCA service.
{{WIP|Although still incomplete, the information it contains is valid and available. |nocat=}}
'''PAR''' allows the Ground Controlled Approach (GCA) controller to deliver approach directives to the requesting aircraft. 
(see [[Howto:Implementing_a_simple_GCA_system]])
= Background =
{{FGCquote
|Is there any work on GCA (ground controlled approach) in progress, or have missed it? GCA is surprisingly accurate and easy to use, both as a pilot and a controller. |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=193941#p193941
|title=<nowiki>Re: Spoken ATC</nowiki>
|author=<nowiki>Alant</nowiki>
|date=<nowiki>Sun Ago 13</nowiki>
}}
}}
= What GCA is =
* https://secretsofcoldwarradar.omeka.net/exhibits/show/cold-war-radar-technology/radar-equipment/ground-controlled-approach-and
* https://aroundthepattern.com/training/ground-controlled-approaches-gca/
* https://en.wikipedia.org/wiki/Ground-controlled_approach
* http://www.rquirk.com/cdnradar/cor/chapter21.pdf

= What can you expect from GCA =

[[File:Gca1.png|left|thumb|Horizontal trajectory when pilot follows GCA instructions]]Arriving in the vicinity of the airport with little or no visibility, the pilot can request the GCA service.
The Controller, assisted by a PAR (''Precision Approach Radar''), will guide you through a safe path (both in heading and in altitude) that will take you to the head of the used runway.[[File:Gca2.png|center|thumb|Vertical trajectory when pilot follows GCA instructions]] 
 
 
 
= How to install =
{{note | This is the latest version (Feb 22, 2018) 

If your FGFS version accepts [[Addons]], you can download this feature from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/PAR/ Addons Repository]. Download all the 12 files into the directory of your choice. 

Launch FlightGear including --addon argument, eg.:
<syntaxhighlight>
fgfs <usual args> --addon=/path/to/PARaddon/</syntaxhighlight>
{{note | From version 2017.4.0, the FG launcher accepts the ''--addon'' option in his ''Settings/Additional Settings'' tab. }}
Otherwise, you can install it as a submodule. Contact the author for further instructions.

And that's all ! 

= How to use it =
When you are about 15 or 20 miles from your destination, tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information'' or at the {{key press|F12}} dialog). 
Press the {{key press|>}} key to see the PAR instrument (you can open as many as you want). Verify the airport and runway destination. 
On the screen you should see not only your plane but all the flying MP/AI in range. Adjust Zoom if necessary. 
Click the {{key press|GCA}} button to request GCA assistance. 
You will hear the GCA's answer ''"<callsign>, this will be a PAR approach to <airport> runway <rwy>."'' 
Now, as you do not want to cheat, you should click the {{key press|hide}} button. (Remember: this PAR is a ground instrument, not a flying one). 
But not worry, once you have landed (or anytime, indeed) you can press the {{key press|>}} key again to visualize and analyze your plotted trajectory. 

Depending on your position and altitude, the GCA will give you a vector towards the base leg or towards the final one. Also will instruct to climb or descend if necessary. 
Follow closely those instructions making standard turns first, and half standard ones when indicated.
Adopt about 90 to 110 kts IAS until you hear ''"Begin descent"'', and configure a "final" atitude then. 
If you are adviced ''"<Well/Slightly> <left/right> of course."'' then make "S" turns to fix that. Little ones if "Slightly", big ones if "Well". 
Correct your vertical speed if you hear ''"<Above/Below> glidepath."''
 
= Phraseology customization =
You can customize the phraseology by editing the "''phraseology.xml''" file. 
There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').
=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either " or ' .
* Punctuation is meaningfull. }}
=== Substitutions ===
Strings starting by '''%''' will call some '''property value'''.
In the example above replace "'''day'''" by "'''% /sim/startup/time-offset-type'''". 
Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.
{{note |
* The called property must be a string.}}
=== Concatenation ===
Strings starting by '''~''' will append the sentence with another one.
Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "'' 

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility..
Better? Fine, but what about the message on the screen?
Include a tag with the pattern <replace type="string">'''old''':'''new'''</replace> :
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight>

PAR instrument

2018-02-22T20:02:51Z

Rodolfo: /* How to install */

PAR instrument

2018-02-22T19:31:46Z

Rodolfo:

Spoken GCA

2018-02-22T19:17:08Z

Rodolfo:

{{note | SpokenGCA is being replaced by the [[PAR_instrument|PAR addon]]. We strongly recommend using the new PAR.
}}


[[File:Gca-ui.png|thumb|Screenshot showing rleibner's GCA/PAR screen (Canvas based) in conjunction with a Canvas driven GUI dialog to configure the GCA <ref>https://forum.flightgear.org/viewtopic.php?f=30&t=32882&p=319257#p319257</ref>]]

[[Spoken GCA]] allows the pilot to listen to the directives of the ''Ground Controlled Approach''.
(see [[Howto:Implementing_a_simple_GCA_system]])
= Background =
{{FGCquote
|Is there any work on GCA (ground controlled approach) in progress, or have missed it? GCA is surprisingly accurate and easy to use, both as a pilot and a controller. |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=193941#p193941
|title=<nowiki>Re: Spoken ATC</nowiki>
|author=<nowiki>Alant</nowiki>
|date=<nowiki>Sun Ago 13</nowiki>
}}
}}
= What GCA is =
* https://secretsofcoldwarradar.omeka.net/exhibits/show/cold-war-radar-technology/radar-equipment/ground-controlled-approach-and
* https://aroundthepattern.com/training/ground-controlled-approaches-gca/
* https://en.wikipedia.org/wiki/Ground-controlled_approach
* http://www.rquirk.com/cdnradar/cor/chapter21.pdf

= What can you expect from GCA =

[[File:Gca1.png|left|thumb|Horizontal trajectory when pilot follows GCA instructions]]Arriving in the vicinity of the airport with little or no visibility, the pilot can request the GCA service.
The Controller, assisted by a PAR (''Precision Approach Radar''), will guide you through a safe path (both in heading and in altitude) that will take you to the head of the used runway.[[File:Gca2.png|center|thumb|Vertical trajectory when pilot follows GCA instructions]] 
 
 

= How to install =
{{note | This is the latest version (Nov 24, 2017) 
Latest modifications: 
* plot2D helpers available.
* {{key press|Track}} button at PAR screen chooses which aircraft must be tracked.
* PAR screen shows local traffic.
* {{key press|RWY}}, {{key press|FLIP}} and {{key press|+}} {{key press|-}} zoom buttons at PAR screen.
}}
If your FGFS version accepts [[Addons]], you can download this feature from the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/SpokenGCA/ Addons Repository]. Download all the 9 files into the directory of your choice.
Launch FlightGear including --addon argument, eg.:
<syntaxhighlight>
fgfs <usual args> --addon=/path/to/fgaddon/SpokenGCA</syntaxhighlight> 

Otherwise, you can install it as a submodule. Contact the author for further instructions.

And that's all ! 
If you prefer (as I do), you can bind an unused joystick button to request GCA service. 

= How to use it =
[[File:PARS-by-rleibner.png|thumb|Screenshot showing the latest GCA addon, featuring support for plotting terrain profiles and customizing other parameters of the GCA addon at runtime]]

When you are about 10 or 15 miles from your destination, tune Comm1 to an available ATC frequency (you can find them at ''Menu/Location/Airfield information''),
and press the {{key press|>}} key to request GCA assistance. 
You will hear the GCA's answer ''"<callsign>, this will be a PAR approach to <airport> runway <rwy>."'' 

Depending on your position and altitude, it will give you a vector towards the base leg or towards the final one. Also will instruct to climb or descend if necessary. 
Follow closely those instructions making standard turns first, and half standard ones when indicated.
Adopt about 90 to 110 kts IAS until you hear ''"Begin descent"'', and configure a "final" atitude then. 
If you are adviced ''"<Well/Slightly> <left/right> of course."'' then make "S" turns to fix that. Little ones if "Slightly", big ones if "Well". 
Correct your vertical speed if you hear ''"<Above/Below> glidepath."''

 

= The PAR screen =
From version 0.5 onwards, the script calls an enhanced PARscreen. Unlike ''parscreen_class.nas'', which it replaces, the new ''par_class.nas'' provides a stand-alone canvas window. 
That means that you can instance as many PAR objects as you like.
From the Nasal console try this:
<syntaxhighlight>
var par24= gca.PAR(icao:"SUMU", rwy:"24").wndow.move(600,0);
var par06= gca.PAR(icao:"SUMU", rwy:"06").flipX();
</syntaxhighlight>[[File:TouchAndGo.png|none]]
This way (choosing opposite runways) you can check your ''touch-n-go'' skills. And this without using the GCA itself at all!

= Phraseology customization =
You can customize the phraseology by editing the "''phraseology.xml''" file. 
There you can find groups of tags like:
<syntaxhighlight lang="xml">
. . . .
<foo type="string">Hello world. </foo>
<foo type="string">It is a good </foo>
<foo type="string">day </foo>
<foo type="string">to fly. </foo>
. . . . </syntaxhighlight>
which will be read as a single sentence (''"Hello world. It is a good day to fly. "'').
=== Literals ===
Those in the example above are literal sentences that you can change by the strings you want.
{{note |
* You should not include either " or ' .
* Punctuation is meaningfull. }}
=== Substitutions ===
Strings starting by '''%''' will call some '''property value'''.
In the example above replace "'''day'''" by "'''% /sim/startup/time-offset-type'''". 
Now the sentence will be read as ''"Hello world. It is a good morning to fly. "'' or ''"Hello world. It is a good evening to fly. "'' depending on the time.
{{note |
* The called property must be a string.}}
=== Concatenation ===
Strings starting by '''~''' will append the sentence with another one.
Try this:
<syntaxhighlight lang="xml">
. . . .
<short type="string">% /satc/callsign-fmt</short>
<short type="string">, </short>

<foo type="string">Have a nice fly, </foo>
<foo type="string">~short</foo>
. . . . </syntaxhighlight>when calling ''foo'' you should hear ''"Have a nice fly, <your-callsign> , "'' 

=== Word Replacement ===
If you find that the word ''Wind'' is not pronounced clearly, you can change it by ''Winnded'' or similar to increase its intelligibility..
Better? Fine, but what about the message on the screen?
Include a tag with the pattern <replace type="string">'''old''':'''new'''</replace> :
<syntaxhighlight lang="xml">
. . . .
<replace type="string">Winnded:Wind</replace>
. . . . </syntaxhighlight> 

= How control.nas script works =
[[File:Gca schema1.png|right|This is the general (simplified) scheme of the gca module:<ref>{{cite web |url = https://forum.flightgear.org/viewtopic.php?p=319409#p319409 |title = <nowiki> Re: Spoken GCA </nowiki> |author = <nowiki> rleibner </nowiki> |date = Sep 26th, 2017 |added = Sep 26th, 2017 |script_version = 0.40 }}</ref>]]

The ''gca.Control()'' function instances an object from ''gca_class'' and sets destination values. 
That GCAobject contains all the AI to design the approaching path and will check the aircraft's position once per second. Instructions are built and transmitted to the caller. 

It also instances an object from ''PARScreen_class'' to track the aircraft on the PAR screen. 

Each second, the script receives an instruction. But it is neither possible nor convenient to pass these instructions to the pilot every second ! 
So it checks the ''demo.phrase'' and ''demo.maxsecs'' members. (''demo.phrase'' is not the instruction itself, but the "instruction-type". And ''demo.maxsecs'' is the maximum elapsed time between consecutive "spoken" instructions.) 
If the received ''demo.phrase'' is the same as the previous one, the script waits <demo.maxsecs> seconds before instruct the pilot. 
But if ''demo.phrase'' changes, then the pilot will be instructed immediately. 
<big>(To be continued . . . )</big> 

= Roadmap =

* In gca_class.nas: add validation of all setters arguments. {{done}}
* Let user to open the UI dialog from the "Set" button" at Par screen. {{progressbar|20}}
* Move join() function and phraseology.xml to be accesible for gca_class.nas.
* Add a version control. {{done}}
* improvements & optimizations
* support for different GUI modes/tabs (pilot, controller, developer) {{pending}} <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=320294#p320294
|title = <nowiki> Re: Spoken GCA </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Oct 10th, 2017
|added = Oct 10th, 2017
|script_version = 0.40
}}</ref> ?
* add support for using AI/MP callsigns for looking up the proper /position root automatically. {{done}} [https://forum.flightgear.org/viewtopic.php?f=30&t=32882&p=320328#p320328]
* add [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Nasal/canvas/gui/widgets/CheckBox.nas checkboxes] to the PAR dialog to show/hide optional elements (labels, flight history etc) ?

= Addon Version =
now structured our prototype as an Addon and uploaded to the [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/SpokenGCA/ Addons repository]

= Testing =
For testing/debugging I'm using a challenging situation:<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=319553#p319553
|title = <nowiki> Re: Spoken GCA </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Sep 28th, 2017
|added = Sep 28th, 2017
|script_version = 0.40
}}</ref>

<pre>
fgfs --aircraft=c172p --airport=SLLP --com1=119.5 --prop:/engines/engine[0]/running=true --offset-distance=10 --offset-azimuth=280 --altitude=14000 --vc=80 --wind=280@10
</pre>

If you try it, be careful:
# At such altitudes a C172 can hardly fly.
# Pilot must manage the Mixture (for starting engines and later often when descending).
# You will be soon flying into the "mushing regime".
# If you fly a heavy aircraft, select rwy 28, cause the 28R is a grass short one. <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=319553#p319553
|title = <nowiki> Re: Spoken GCA </nowiki>
|author = <nowiki> rleibner </nowiki>
|date = Sep 28th, 2017
|added = Sep 28th, 2017
|script_version = 0.40
}}</ref>
Another interesting one:
<pre>
fgfs --aircraft=c172p --airport=LOWI --com1=119.27 --prop:/engines/engine[0]/running=true --offset-distance=6 --offset-azimuth=82 --altitude=10000 --vc=80 --wind=80@10
</pre>
Try editing "Final Approach" and "Glide Slope" values (use the "Apply" button).

= References =
{{Appendix}}

PAR instrument

2018-02-22T18:49:28Z

Rodolfo:

File:PAR.png

2018-02-22T18:43:31Z

Rodolfo: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Precision Approach Radar screen}}
|date=2018-02-22
|source={{own}}
|author=[[User:Rodolfo|Rodolfo]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Canvas]]