136
edits
Red Griffin ATC: Difference between revisions
Jump to navigation
Jump to search
no edit summary
RedGriffin (talk | contribs) No edit summary |
RedGriffin (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
| developedby = Antonello Biancalana (Red Griffin, IK0TOJ) | | developedby = Antonello Biancalana (Red Griffin, IK0TOJ) | ||
| initialrelease = January 5, 2020 | | initialrelease = January 5, 2020 | ||
| latestrelease = 2. | | latestrelease = 2.2.0 March 6, 2021 | ||
| writtenin = Nasal | | writtenin = Nasal | ||
| developmentstatus = Active (2019-) | | developmentstatus = Active (2019-) | ||
| Line 26: | Line 26: | ||
* Support for ground, take off, visual approach, ILS and landing operations | * Support for ground, take off, visual approach, ILS and landing operations | ||
* ATC assisted approach, guiding the pilot to the proper route, altitude and speed up to the final approach point to runway and according to aircraft type | * ATC assisted approach, guiding the pilot to the proper route, altitude and speed up to the final approach point to runway and according to aircraft type | ||
* Festival Speech Synthesis System support | |||
* Squawking | * Squawking | ||
* Approach and slope monitor | * Approach and slope monitor | ||
| Line 58: | Line 59: | ||
== Running Red Griffin ATC Addon from Command Line == | == Running Red Griffin ATC Addon from Command Line == | ||
* Start | * Start <code>fgfs</code> including <code>--addon=<your_local_path>/RedGriffinATC</code> option in the command line | ||
== Running Red Griffin ATC Addon from the Launcher == | == Running Red Griffin ATC Addon from the Launcher == | ||
| Line 238: | Line 239: | ||
==== Aircraft compatibility ==== | ==== Aircraft compatibility ==== | ||
Red Griffin ATC radio support and use rely on FlightGear properties and, for this reason, it is essential for the aircraft to provide a functional implementation of the radio stack. Red Griffin ATC has been extensively tested with tens of aircraft and, according to these tests, not all aircraft seem to provide a complete implementation of COM radios and, in this particular case, those aircraft will not work because of lack of fundamental properties needed by Red Griffin ATC. As of version 2. | Red Griffin ATC radio support and use rely on FlightGear properties and, for this reason, it is essential for the aircraft to provide a functional implementation of the radio stack. Red Griffin ATC has been extensively tested with tens of aircraft and, according to these tests, not all aircraft seem to provide a complete implementation of COM radios and, in this particular case, those aircraft will not work because of lack of fundamental properties needed by Red Griffin ATC. As of version 2.2.0, Red Griffin ATC uses and relies on the following radio properties for each COM radio: | ||
* /instrumentation/comm[x]/serviceable | * <code>/instrumentation/comm[x]/serviceable</code> | ||
* /instrumentation/comm[x]/signal-quality-norm | * <code>/instrumentation/comm[x]/signal-quality-norm</code> | ||
* /instrumentation/comm[x]/volume | * <code>/instrumentation/comm[x]/volume</code> | ||
* /instrumentation/comm[x]/volume-selected | * <code>/instrumentation/comm[x]/volume-selected</code> | ||
* /instrumentation/comm[x]/power-btn | * <code>/instrumentation/comm[x]/power-btn</code> | ||
* /instrumentation/comm[x]/airport-id | * <code>/instrumentation/comm[x]/airport-id</code> | ||
* /instrumentation/comm[x]/station-name | * <code>/instrumentation/comm[x]/station-name</code> | ||
* /instrumentation/comm[x]/frequencies/selected-mhz | * <code>/instrumentation/comm[x]/frequencies/selected-mhz</code> | ||
* /instrumentation/comm[x]/track-distance-m | * <code>/instrumentation/comm[x]/track-distance-m</code> | ||
* /instrumentation/comm[x]/true-bearing-to-deg | * <code>/instrumentation/comm[x]/true-bearing-to-deg</code> | ||
In case the aircraft does not provide some of the above properties, Red Griffin ATC will show a warning message in the main dialog and any radio operation will not be possible. In this specific case, you can contact the aircraft developer and ask for a revision of the radio implementation in order to comply to the above properties. | In case the aircraft does not provide some of the above properties, Red Griffin ATC will show a warning message in the main dialog and any radio operation will not be possible. In this specific case, you can contact the aircraft developer and ask for a revision of the radio implementation in order to comply to the above properties. | ||
| Line 283: | Line 284: | ||
* Set the altimeter according to the QNH provided by the ATC (aircraft cockpit panel) | * Set the altimeter according to the QNH provided by the ATC (aircraft cockpit panel) | ||
== Approach and | == Approach and Slope Monitor == | ||
When the aircraft is about to land, while it is flying the final leg to runway and within 5 nautical miles from the runway landing area, Red Griffin ATC gives the pilot both the distance to the touch down point as well as an "approach and slope monitor" in order to assist the pilot in following the right course and glide path to landing. | When the aircraft is about to land, while it is flying the final leg to runway and within 5 nautical miles from the runway landing area, Red Griffin ATC gives the pilot both the distance to the touch down point as well as an "approach and slope monitor" in order to assist the pilot in following the right course and glide path to landing. | ||
| Line 292: | Line 293: | ||
In case the aircraft is perfectly aligned and following the proper glide path, the monitor will show "ok". | In case the aircraft is perfectly aligned and following the proper glide path, the monitor will show "ok". | ||
== Festival Speech Synthesis System Support == | |||
Red Griffin ATC can take advantage of the superior voice quality offered by the [https://www.cstr.ed.ac.uk/projects/festival Festival Speech Synthesis System] through FlightGear direct support for Festival running in server mode. In order to use the Festival Speech Synthesis System, you need to have a properly installed and working Festival system in your machine as well as having at least FlightGear version 2020.3.6. Prior to this version, FlightGear cannot properly support and initialize the Festival Speech Synthesis System and will therefore fall back to the [[Flite_TTS|internal default speech synthesizer]]. | |||
The Festival Speech Synthesis System running in server mode allows up to ten simultaneous connections, therefore it can provide up to ten different voices. Red Griffin ATC takes advantage of this feature and can provide a fuller and deeper experience by using those ten different voices and by assigning them to each specific radio. The available voices are assigned at random from the whole pool of voices available and properly configured through FlightGear COMM properties. This will give the sensation of speaking to different operators during the whole flight session. Red Griffin ATC associates a specific voice to any specific radio frequency and the association is kept for the whole duration of the flight. This means you are going to hear the very same voice in case you are tuning back to a radio frequency already used in the current flight session. Please note pilot voice is associated to a specific voice and exclusively used for that purpose. This means the pilot voice will never be used for radio operators. | |||
=== Configuring Red Griffin ATC with Festival Support === | |||
Festival Speech Synthesis System support in Red Griffin ATC is implemented through FlightGear internal properties, in particular those related to sound and voice support, found in the <code>/sim/sound/voices</code> tree. | |||
Voices can be defined and set up by using a configuration <code>XML</code> file describing each FlightGear voice according to the internal structure of the property tree. Here it is how a voice should be configured in order to support the Festival Speech Synthesis System: | |||
<code><voice><br> | |||
<desc>Pilot</desc><br> | |||
<text type="string"/><br> | |||
<volume type="double">1.0</volume><br> | |||
<pitch type="double">100.0</pitch><br> | |||
<speed type="double">0.8</speed><br> | |||
<preamble type="string">(voice_cmu_us_rms_cg) (audio_mode 'async)</preamble><br> | |||
<festival type="bool">true</festival><br> | |||
<htsvoice type="string">cstr_uk_female-1.0.htsvoice</htsvoice><br> | |||
</voice></code> | |||
In order to be used in Festival, a voice needs the <code><festival></code> and <code><preamble></code> properties to be properly initialized. Specifically, <code><festival></code> property must be <code>true</code> (that is, enabled) while <code><preamble></code> property must contain valid Festival <code>scheme</code> commands to be sent to the server at initialization time. The <code><preamble></code> property must at least contain the <code>scheme</code> command selector for the specific Festival voice to be associated to a FlightGear voice. | |||
In this regard, it is strongly advised to set Festival in asynchronous audio mode by adding the <code>scheme</code> command <code>(audio_mode 'async)</code> to the <code>preamble</code> property. In this case, Red Griffin ATC will interact with Festival in a way that will provide a quicker response and by actually creating utterances while speaking, therefore getting a better synchronization with ATC texts shown in the screen. | |||
In case <code>(audio_mode 'async)</code> is not used, Red Griffin ATC interaction with Festival server will result with an "out of sync" speaking in relation to the text shown in the screen. | |||
Voices can also be "fine tuned" by properly setting <code><volume></code>, <code><pitch></code> and <code><speed></code> properties. | |||
The property <code><desc></code> can optionally describe the defined voice and, in particular, the voice to be used for the pilot. In this specific case, <code><desc></code> property must be assigned to "Pilot", like the sample shown above. In case no voice is assigned to the pilot, Red Griffin ATC will use the value found in <code>/sim/sound/voices/pilot</code>. | |||
Red Griffin ATC is distributed with a sample configuration file defining ten different Festival voices and can be used "out of the box" or used as a template in case it is wished a different voice scheme or configuration. The sample configuration file is found at <code><your_local_path>/RedGriffinATC/festival.xml</code>. The <code>festival.xml</code> is configured in order to use some Festival default voices as well as some of those available at [http://festvox.org/packed/festival/2.4/voices Festvox website]. In order to use the configuration file provided with Red Griffin ATC, you need to properly install the Festival voices defined in <code>festival.xml</code> and available at the Festvox website. | |||
=== Running Festival in Server Mode === | |||
In order to run Festival, you need it to be properly installed and working in your system. Festival can be compiled and installed from the source distribution or by using the binary package available for your system. | |||
To start Festival in server mode, you need to open a shell or console window and type: | |||
<code>festival --server</code> | |||
The Festival Speech Synthesis System will then listen to port 1314 waiting for incoming requests and will accept up to ten simultaneous clients. | |||
=== Running FlightGear with Festival Support === | |||
In order to have FlightGear using the configuration file as described above, you need to use the <code>--config</code> option. | |||
In case you are going to start FlightGear from the command line, you need to append the <code>--config</code> option and the path of festival configuration file: | |||
<code>fgfs [your_options] --config=<your_local_path>/RedGriffinATC/festival.xml</code> | |||
In case you are using FlightGear launcher, you need to add <code>--config=<your_local_path>/RedGriffinATC/festival.xml</code> in the "Additional Settings" box found in the "Settings" tab. | |||
== Demonstration Flight and Tutorial == | == Demonstration Flight and Tutorial == | ||
| Line 347: | Line 403: | ||
{{#ev:youtube|65KjUT3Avl4}} | {{#ev:youtube|65KjUT3Avl4}} | ||
=== Red Griffin ATC Using Festival Speech Synthesis System === | |||
{{#ev:youtube|5IhPebn2TgI}} | |||
== Special Thanks == | == Special Thanks == | ||
| Line 360: | Line 420: | ||
It was not my computer though as at that time I owned a Commodore VIC20 and, alas, the only "flight simulators" available for it were Ron Wanttaja's IFR Flight Simulator and Anirog's Flight Path 737. The big step forward was Flight Simulator II for Commodore 64 in 1984 and featuring a Piper PA-28-181 Archer II. The giant step forward was in 1987 when it was released the Commodore Amiga version (one of the most amazing and very best, revolutionary, exceptional computer of all times) which featured three aircraft: Cessna 182RG, Gates Learjet 25G and Sopwith Camel. | It was not my computer though as at that time I owned a Commodore VIC20 and, alas, the only "flight simulators" available for it were Ron Wanttaja's IFR Flight Simulator and Anirog's Flight Path 737. The big step forward was Flight Simulator II for Commodore 64 in 1984 and featuring a Piper PA-28-181 Archer II. The giant step forward was in 1987 when it was released the Commodore Amiga version (one of the most amazing and very best, revolutionary, exceptional computer of all times) which featured three aircraft: Cessna 182RG, Gates Learjet 25G and Sopwith Camel. | ||
I therefore have no ATC procedures experience | I therefore have no real ATC procedures experience and what I know about this subject is from what I read in specialized books about ATC procedures and phraseology found in various website of flight schools, airports and aero clubs. Most of the phraseology used in Red Griffin ATC is created according to the procedures found in these books and manuals, as well as from the many valuable contributions from Red Griffin ATC users, both in FlightGear forum and direct exchange of messages from amateur and professional licensed pilots. I understand the procedures used in this addon may however result incorrect to real pilots, either because of my lack of experience in this subject or because of improper implementation. I am more than glad to get any feedback about ATC procedures from experienced pilots and anyone knowing this subject in order to improve this addon. | ||
Red Griffin ATC © 2019-2021 Antonello Biancalana, Red Griffin, IK0TOJ (for those who wonder about this code, it is my HAM call sign) | Red Griffin ATC © 2019-2021 Antonello Biancalana, Red Griffin, IK0TOJ (for those who wonder about this code, it is my HAM call sign) | ||
| Line 387: | Line 447: | ||
* [https://www.youtube.com/c/RedGriffin Red Griffin YouTube Channel] | * [https://www.youtube.com/c/RedGriffin Red Griffin YouTube Channel] | ||
* [https://www.cstr.ed.ac.uk/projects/festival Festival Speech Synthesis System] | |||
* [http://festvox.org/festival/index.html Festvox Project] | |||
* [http://festvox.org/packed/festival/2.4/voices Voices and lexicons for Festival 2.4] | |||
[[Category:Red Griffin ATC]] | [[Category:Red Griffin ATC]] | ||