==Configuring FGCOM and FlightGear To Have Use Of An Optional Second Comm Radio==

* ''This article is not yet finished, please check back later.''

====The Goal====
# Be able to monitor both the comm1 frequency and comm2 frequency at the same time.
# Be able to select between comm1 and comm2 to transmit on easily.
# Keep the second radio optional, but easily added at runtime when needed.
# To do so with existing fgcom and flightgear functionality.

====What Is Involved====
* Two instances of fgcom, one for each comm radio.
* A second, slightly modified fgcom protocol file for comm2.
* A second generic protocol definition for the above.
* A bit of nasal script to glue it all together
* A little bit of patience.

====Files====
* The secondary fgcom protocol file - [http://.com fgcom_comm2.xml]
* The nasal script file - [http://.com fgcom.nas]

=====Protocol File=====
This is a slightly modified version of the normal fgcom protocol file. It is used to get the second instance of fgcom to use comm2 frequency and ptt.

Place this file in '''''FG_ROOT/Protocols'''''.

=====Nasal Script=====
The script file defines and creates an instance of an FGComRadio object. This object is used to select radio(s) and transmit on the right one, it is available to other nasal script as '''''fgcom.radio'''''

======Api======
*'''fgcom.radio.ptt(BOOL)''' - Enable/disable push to talk on the currently selected radio(s). ''BOOL'' should be '''1''' to start transmitting, '''0''' to stop.
*'''fgcom.radio.next_radio()''' - Switch to the next radio for transmitting. This cycles through comm1, comm2, both, and back to comm1.
*'''fgcom.radio.select_radio(INT)''' - Select a specific radio for transmitting. ''INT'' should be '''0''' for comm1, '''1''' for comm2, or '''2''' for both.
*'''fgcom.radio.selected_radio()''' - Returns the currently selected radio for transmitting. '''0''' for comm1, '''1''' for comm2, or '''2''' for both.

<nowiki>*</nowiki> ''all other methods or attributes are for internal use only and should not be used or modified''

The script also exposes some properties which will be found in flightgear under '''''/local/fgcom'''''. These properties are purely informational and should be considered read only, changing them will not affect anything. By default the script displays these properties at the upper left of your screen. If you do not want this, remove or comment the appropriate lines in the script...last 4 lines...read the comments.

Place this file in '''''FG_HOME/Nasal'''''. On Linux this is '''''/home/<username>/.fgfs/Nasal''''', create if needed. I'm sorry but I do not know the path used on Windows or Mac. It is '''important''' that you '''do not''' put this file in '''''FG_ROOT/Nasal'''''!

====Setup====
Setup is fairly simple and consists of the following:
# Configuring a second generic protocol for comm2.
# Adding bindings to the joystick or keyboard to call the methods in the '''''fgcom.radio''''' object.

=====Protocol=====
Start by configuring the second generic protocol for flightgear. This is in addition to the fgcom protocol you have setup previously, and should be the same except '''change port to 16662''' and change the protocol name to '''fgcom_comm2'''. If you need help in setting up the protocol again(in fgrun), refer to this section of [http://wiki.flightgear.org/index.php/FGCOM#Functional_Test_.2B_User_Briefing the main fgcom article](scroll down to part '''6) Input/Output'''). If your using fgcomgui, you can go to ''Help->HTML Docs'' and refer to the flightgear section there.

=====Bindings=====
The default push to talk binding in flightgear is the spacebar, but only affects properties for comm1. You can try to modify the default bindings if you wish, but I recommend just leaving them and adding your own bindings elsewhere. I personally use two buttons on my joystick for this, one for push to talk, and one for switching between comm radios. So I will just show those parts of my joystick config as an example for how to setup bindings using the '''''fgcom.radio''''' object for control.

'''''binds button 1 on my joystick to push to talk. Transmits (on selected radio) while pressed, stops when released.'''''
<code>
<button>
<number>
<unix>1</unix>
<windows>1</windows>
</number>
<desc>Push To Talk</desc>
<binding>
<command>nasal</command>
<script>fgcom.radio.ptt(1);</script>
</binding>
<mod-up>
<binding>
<command>nasal</command>
<script>fgcom.radio.ptt(0);</script>
</binding>
</mod-up>
</button>
</code>

'''''binds button 4 on my joystick to switching selected radio(s) for transmitting.'''''
<code>
<button>
<desc>Change comm radio used for ptt</desc>
<number>
<unix>4</unix>
<windows>4</windows>
</number>
<binding>
<command>nasal</command>
<script>fgcom.radio.next_radio();</script>
</binding>
</button>
</code>

====Bringing It All Together====
Ok, so you have placed the files in the appropriate places, added the generic protocol definition to fgrun(if you use it), added keyboard/joystick bindings, and now your ready to try it all out.

=====Starting FlightGear=====
First we will go ahead and launch flightgear using your preferred method below. If all is well you should see no errors, and will see the '''''fgcom.radio''''' properties at the top left of your flightgear window. Pressing the button you've bound to switching radios, you should see the ''active_radio'' property changing from comm1->comm2->both->comm1. Pressing the button you've bound to ptt, you should see the ''ptt'' property switching between 0 to 1. If it's all working, congrats, you can now move on to the Starting FGCom section. If you had any problems or errors, please refer to the Trouble Shooting section for possible solutions. Resolve any problems before moving on.

======FGRun======
Just go ahead and start flightgear. Making sure you set up the second protocol definition first of course.

======Command Line======
Starting flightgear, using the ufo and specifying the fgcom protocols. Notice the different port and protocol name for the second.
jacob@dualbuntu:~ $ fgfs --aircraft=ufo --generic=socket,out,10,localhost,16661,udp,fgcom --generic=socket,out,10,localhost,16662,udp,fgcom_comm2

====Starting FGCom====
To have two comm radios, we will need to run two instances of fgcom. For the first instance you can use fgcomgui for run fgcom from the command line. For the second instance I recommend using the command line, as fgcomgui is was not really intended to be run multiple times.

=====First FGCom Instance=====
<nowiki>*</nowiki> ''If you wish to use fgcomgui as your first instance instead, go ahead and start it now, making sure port is set to 16661(the default).''

Starting first instance of fgcom from the command line, using default settings.
jacob@dualbuntu:~ $ fgcom -Sfgcom.flightgear.org.uk

Using your binding created earlier, make sure comm1 is selected, set comm1 frequency to 910 and press your ptt key/button. You should hear everything echoed back to you. If you have any problems refer to the Trouble Shooting section for possible solutions and try again.

=====Second FGCom Instance=====
Ok, with first instance working, let's start the second one. Notice that we set port to 16662 this time.
jacob@dualbuntu:~ $ fgcom -Sfgcom.flightgear.org.uk -p16662

Using your binding created earlier, make sure comm2 is selected, set comm2 frequency to 910, and press your ptt key/button. You should hear everything echoed back to you. If you have any problems refer to the Trouble Shooting section for possible solutions and try again.

User:Tuxklok

2009-10-07T16:41:48Z

Tuxklok:

User:Tuxklok

2009-10-07T16:30:43Z

Tuxklok:

Tuxklok

2009-10-07T06:53:39Z

Tuxklok: moved Tuxklok to User:Tuxklok: oops

#REDIRECT [[User:Tuxklok]]

User:Tuxklok

2009-10-07T06:53:39Z

Tuxklok: moved Tuxklok to User:Tuxklok: oops

Tuxklok: /* Innsbruck Gets A Face Lift */

Welcome to the second edition of the FlightGear Newsletter. In this issue, we have a new GA aircraft in the hangar, a report from LinuxTag 2009, and a description of a Tornado simulator.

The newsletter is still a bit thin on contributions, so if you'd like to contribute, please feel free to log onto the wiki and start editing the next edition [[FlightGear Newsletter September 2009| here]]. We're still looking for a permanent (or even a temporary) newsletter editor, so if you'd like to get involved, have a look on the [http://www.flightgear.org/forums/ Forums].

==What's New in CVS==

===Configurable Shaders===

Tim Moore has committed a significant change to the graphics system that will allow much easier integration of OpenGL shaders within the simulator.

Shaders are small programs that run on your graphics card itself, and allow the simulator to do graphics operations that would otherwise be too computationally expensive. The current FG release (1.9.1) uses shaders for the forests of trees and 3D clouds.

This change represented a lot of work on the infrastructure of the project for long-term benefit. While there aren't any significant graphics changes based on this yet, we can expect a lot in the future, including integration of some nice water effects.

===Generic Binary I/O protocol===

The input and output code of FlightGear has been very flexible for many years by allowing for communications to (and from) files, serial ports and network sockets just by altering a command-line option.

In conjunction with that FlightGear has had support for a generic ASCII only input-output protocol handler for a number of years now. It is called 'generic' because it allows handling of just about any information in any form by altering a user modifiable xml configuration file. The functionality has been extended further by the possibility to define an offset and a multiplication factor. This approach might not cover every possible scenario but it will probably be good enough for most cases.

With the help of Anders Gidenstam the generic protocol has recently been extended to also support binary input and output. The data will be tightly packed in a packet that contains the requested data described in the configuration file. Supported types are: boolean values (8-bit), integer values (32-bit), floating point values (32-bit) and double precision floating point values (64-bit). Anders also added the option to support network byte ordering (big-endian) or system native byte-ordering which will save some processing time when only one type of system is used. To make it easier to see how the packet will be handled by FlightGear a utility called generic-protocol-analyze has been created which can be found in FlightGear/utils/xmlgrep. It outputs the data offset and size along with it's description.

==New Wiki Articles ==
The wiki provides now a new article for aspiring core developers about extending the built-in Nasal scripting interpreter with custom extension functions: [[Howto:Extending Nasal]].
The [[Nasal scripting language|Nasal documentation]] itself has been slightly reworked to provide a step by step introduction for users completely new to scripting or programming in general.

==In the Hangar==

[[Image:Pa22.jpg|150px|Piper Tri-Pacer]]
[[Image:Pa22cockpit.jpg|150px|Piper Tri-Pacer cockpit]]

There's a new aircraft in the CVS hangar - the [http://en.wikipedia.org/wiki/Piper_Pacer PA 22-160 Tri Pacer]. Created by Robert Leda (aka erobo) and Pawel Luchowski, this is a lovely GA aircraft and well worth having a flight in. If you enjoy VFR cross-country flying, or even simple IFR, and want to try something different to the Cessna 172, this is the plane for you.

The level of detail is very impressive - you must prime to start the engine (making sure the mixture is set), the sound varies depending on whether you've got the window open, and the doors slam shut. All in all, it's a great polished aircraft, and a fine addition to the hanger.

The FG hangar now has a very wide range of Piper aircraft, from the simple Cub, through the Cherokee Warrior II, Comanche 250, to the Seneca II. It is worth noting that the Warrior, Comanche and Seneca are all based on airframes flown by FG contributors in real life.

==Useful Links==

For those wanting to do some dead reckoning, this [http://www.csgnetwork.com/e6bcalc.html CRP5 E6B] online calculator may be of interest. Get your stopwatch, chinagraph pencils, ruler and protractor ready!

There are a whole host of funky aviation converters [http://www.csgnetwork.com/aviationconverters.html here]. Thanks to eeK on the forums for the links.

==LinuxTag 2009==
[[Image:Linuxtag2009_1.jpg|thumb|200px|A view of the FlightGear stand]]
[[Image:Linuxtag2009 terrain before.jpg|thumb|150px|left|Terrain texture (before)]]
[[Image:Linuxtag2009 terrain after.jpg|thumb|150px|left|Terrain texture (linuxtag)]]
[[Image:Shader sea linuxtag2009.jpg|thumb|150px|right|Sea texture (linuxtag)]]

The 2009 edition of the LinuxTag has been concluded and the FlightGear hangar was there full of aircraft and pilots ! You could easily spot our stand since it seemed to me the most popular one, the idea to take a free virtual flight coupled with a free flight instructor was like honey for bears. Furthermore the hardware was impressive, 2 flight stations with 3 big monitors each and real controls were worth a try ! You could even track your flight through a projected mapserver on the wall.<br/> We flew mostly around the [[EDDF|Frankfurt]] area, where a highly detailed airport (still with a high fps rate) was the background of our participants. The favorite aircraft was the [[Piper_PA34-200T_Seneca_II|SenecaII]] as it was perfect to be flown with our equipment. Meanwhile in the forward station was easy to see some [[Eurocopter_Bo105|Eurocopter Bo105]] pilot or [[Grumman_F-14_Tomcat|F-14 Tomcat]] top gun enjoying [[Aircraft_carrier|carrier]] approaches.<br/>

But it was not just all flying and fun. At the stand you could talk to some code and model developers, discussing new features and wishes. There was a developers section too: Till was hacking an earth and sea textures generator to improve our virtual world terrain painting, applying [http://en.wikipedia.org/wiki/Shader shaders] instead of fixed photos; early results where really interesting and I hope to see them soon in [[CVS]].

The FlightGear guys prove themselves very friendly and always spoke in english in my presence. Martin Spott took care to manage an entrance pass for me and kept me informed prior to LinuxTag via Emails. This means you have no excuses to miss the event next year (At least only if you are not afraid of virtually flight !).

* [http://brisa.homelinux.net/zenphoto/index.php?album=linuxtag2009 photos from Francesco and Matthias of the stand]

- Francesco Brisa

==Tornado F3 Simulator==

I had the very good fortune to use a genuine Panavia Tornado F3 simulator at RAF Leuchars in Scotland at the start of August.

I flew in from the south in my microlight, as part of a fly-in to the base. This was a rather unique event, as the last fly in to the base had been some 15 years before, and the RAF made us very welcome, with talks about their ATC and how to avoid the fast jets that fly near us (top tip - don't be at 250ft AGL - that's where they spend most of their time!).

The simulator itself did not have a moving platform, but did use a real cockpit, had a 120 degree field of view display and was used for training by the pilots, including interceptions and weapons training. The short sortie I flew took off from RAF Leuchars (EGQL) up the Firth of Forth, underneath the Forth Bridges, and then landing at Edinburgh (EGPH). The feeling of "being there" was quite remarkable, and it was a real privilege to have the opportunity to use it.

One of the things that struck me however, was that there was nothing there that was beyond the capabilities of FlightGear. The graphics were possibly slightly lower in quality (no scenery objects apart from the bridges) and the display technology was using DLP projectors (there's a description [http://ntdd2489.fm.netbenefit.co.uk/recentInstallations/Industry/Simulation/RAF_Leuchars/index.asp here]). The key thing that made the experience so realistic was the wide field of view and the use of real hardware. I was sat in a real Tornado cockpit, the canopy was closed (with warning klaxon), the stick was heavy, and the throttles had to be moved appropriately for reheat or reverse thrust. So, perhaps its time to see if there are any real cockpits available...

Of course, none of this is news to the various people who are building fixed base simulators using FG as a software platform. There is a list of the known FG-based projects [http://www.flightgear.org/Projects/ here], and almost certainly plenty more around.

-Stuart Buchanan

==Innsbruck Gets A Face Lift==
[[Image:Innsbruck_after_003.jpg|thumb|175px|left|screenshot]]
[[Image:Innsbruck_after_006.jpg|thumb|175px|left|screenshot]]

Custom scenery for the area in and around Innsbruck, Austria, is now available for downloading.The scenery covers a 1x1 degree area in and around Innsbruck, Austria, and makes use of accurate data from the '''Corine Land Cover''' and '''Open Street Map''' projects. See the forum topic [http://flightgear.org/forums/viewtopic.php?f=5&t=5350 here] for more details, pictures, and links to download the scenery.

-Jacob Burbach (Tuxklok)<br/><br/><br/>

==And Finally...==
Check out the cockpit of an Airbus A380 and have a virtual tour here:
[http://www.airbus.com/store/mm_repository/cockpit_airbusA380/flash/cockpit1.htm http://www.airbus.com/store/mm_repository/cockpit_airbusA380/flash/cockpit1.htm]

[[Category:FlightGear Newsletter|2009 8]]

FlightGear Newsletter August 2009

2009-08-03T21:39:35Z

Tuxklok: /* Innsbruck Gets A Face Lift */