Fr/FGCom

Cet article requiert un toilettage pour un respect des standards de qualité de ce wiki. Veuillez SVP améliorer cet article si vous le pouvez.

FGCom

Développé par	Holger Wirtz, Martin Spott, Csaba Halasz
Niveau de développement	Active (2007-)
Licence	GNU General Public License
Site web

FGCom est un ajout pour FlightGear. Avec FGCom (et son infrastructure), FlightGear a maintenant un système vocal de communication en temps réel qui enrichit ses possibilités, et spécialement les fonctions multiplayer , comme:

• Voler en groupe, voir forum des évenements multiplayer
  • Inviter des amis à faire une visite guidée dans votre zone préférée ou faire “Fly In's”
  • Faire des entraînements militaires comme “Ravitaillement en vol”, “Dog fights”, “vols d'escorte ”, etc.
• Offrir des services supplémentaires à un aéroport, comme ATC, chasse-neige, pushbacks, compétitions etc.
• Avoir un entraînement au vol en temps réel (p.ex. pilote à Hongkong, moniteur à Sydney), faire du planeur, demander de l'aide en ligne pendant le vol ou bien parler avec quelqu'un des caractéristiques d'un avion.
• Ou juste s'asseoir dans un cockpit en Allemagne pendant la visite de San Francisco dans un C172, discuter avec un Texan dans un avion (Super Constellation) auquel je rêvais quand j'étais gosse et en même temps, obtenir des informations d'un gars de Nouvelle-Zélande (il paraît que c'est une île magnifique mais est-elle réellement habitée? Il a dit Oui!!).
• Et plus encore!

Vous pouvez même l'utiliser dans les modèles d'avions sans radio- faites le menu standard FlightGear (Equipment > Radio Settings).

Dans le futur, FGCom s'améliorera encore et on aura sûrement la possibilité d'avoir “Speech to Text” afin d'intégrer les routines des textes automatiques ATC dans FlightGear.

Installation du Client

Conditions

Matériels requis

Si vous êtes satisfaits des temps d'opérations et de réponses avec votre installation actuelle, vous ne trouverez aucune différence aprés l'ajout de FGCom. Si votre installation est un peu limite, alors, vous pourrez observer des retards lorsque beaucoup d'avions sont chargés. C'est possible dans les aéroports très fréquentés. Vous pouvez contrôler/vérifier ainsiI "short-time overload" dans la fenêtre de commande de FlightGear.

Pour plus de détails, voir les conditions requises pour le matériel et le driver.

Bien sûr, il vous faut aussi une connection internet pour la communication vocale en temps réel et dans le monde entier.

Conditions requises pour le logiciel

FlightGear	L'installation de base du simulateur de vol FlightGear . Il doit être installé avant FGCom (sauf avec la version Linux "Git complete" qui peut installer en même temps FGCom et FlightGear).
Multiplayer	“Multiplayer” n'est pas un programme installable mais une fonction intégrée FGFS. Comme son nom l'indique, il active la communication entre plusieurs joueurs via une chat-fonction (par clavier - mais maintenant avec l'interface vocale: FGCom).

Bon à avoir

FGrun	FlightGear Launch Control (aussi connu comme FG Wizard), est un "graphical front end" pour démarrer FGFS. Il rend très facile le démarrage de FGFS avec toutes les options possibles. Dans quelques distributions récentes, il est déja intégré dans le paquet de base d'installation de FGFS.
MPMap	MPMap est une application de navigateur basée sur Google Maps, ne nécessitant aucune installation, sauf un navigateur Web. Avec MPMap vous pouvez voir tous les avions des utilisateurs du monde entier, sur une carte routière , sur des images satellites ou les deux à la fois. On y trouve la plupart des aéroports, les aides à la navigation, et la météo du moment. Donc, on peut s'en servir pour faire un plan de vol sans avoir FGFS démarré ni même installé. Mais il faut être connecté à Internet en permanence- ainsi, vous pouvez faire votre préparation de vol partout où il y a un PC connecté à Internet.
SkyVector	SkyVector est une application de navigateur stadalone. C'est un outil de plan de vol, fantastique, comparable à "MPMap" - mais basé sur une vraie carte aéronautique ("Par sections"). Vous pouvez y planifier vos routes graphiquement,- voir l'icone "Help Video"-dans la barre des menus du haut. Mais il n'est pas relié directement à FGFS, MPMap ou Multiplayer -- et il couvre seulement les États-Unis.
Atlas	Atlas affiche la position actuelle de votre avion dans la carte du paysage, en même temps que les informations de navigation. Il tire directement ses données de FGFS. Ainsi, vous n'avez pas besoin d'Internet.
Festival	Festival est un système TTS (Text To Speech) qui peut convertir tout texte écrit, affiché dans FGFS (ATC, Chat, etc.) en paroles et le mettre dans vos écouteurs.

Installation de FGCom

Installer sur Linux

Pour les systèmes Linux, Trois moyens pour installerl:

1. Télécharger depuis le “Distributor” (Debian, Ubuntu, Red Hat, Suse, etc.).
   • Avantage: C'est le moyen le plus facile qui assure maintenance et services pour ce paquet, ainsi que toutes les aides automatiques dans un laps de temps raisonnable.
   • Inconvénient: La disponibilité de ces paquets est récente, et la plupart des Distributors ne couvre pas toutes les versions FGFS. A notre connaissance, aucun Distributor n' avait de paquet FGCom disponible en Mars 2009.
   • Installation: Suivez la procédure habituelle de votre distributeur sur la façon d'installer des paquets supplémentaires.
2. Installer un “Git complet”
   • Avantage: C'est le moyen le plus facile, et en une seule étape, tous les modules pré-requis sont installés (FGFS, FGrun, FGcom, PLIB, OSG, Simgear, AT). Tout peut être ajouté ou enlevé sans déranger quoique ce soit (Libraries, Menus, Structures, etc.). Il a été testé sur plusieurs systèmes Ubuntu et Debian.
   • Inconvénient: Pas de maintenance automatique disponible. La manipulation est un peu différente de la pratique guidée du menu standard.
   • Installation: Scripted Compilation on Linux Debian/Ubuntu
3. Compilation locale:
   • Avantage: Après une installation réussie, c'est intégré dans le système comme un paquet du distributeur.
   • Inconvénient: Pas de maintenance automatique disponible. Donc l'utilisateur doit avoir quelques connaissances de base de son système et de ses possibilités.
   • Installation: instructions

La suite avec FGCOM Testing.

Installer sur Mac

MacFlightGear 1.9.1/2.6.0
Vous pouvez télécharger l'application "MacFlightGear"- sur FlightGear download-center. La version actuelle 2.6.0 contient FGCom et marche pour OSX >= 10.5. (avec les OSX versions < 10.5 vous terminerez avec un message générique "bus error").

Installer sur Windows

Veuillez utiliser la decription d'installation disponible sur FGCOM for Windows.

Essai

Pendant l'essai, vous testerez/ajusterez:

1. les fonctions de base FGCom sans FlightGear
2. FGCom en même temps que FlightGear
3. le système micro-hautparleurs

Pour ces tests veuillez vous référer à FGCOM Testing.

Test de fonctionnement & briefing de l'utilisateur

La pratique montre que la coordination entre FGCom et FlightGear se fait mieux si FlightGear est démarré en premier. Ainsi, nous commencerons le test avec un environnement de vol installé.

Démarrer FlightGear

Nous suggérons FGRun pour définir les installations demandées et/ou proposées, afin d'éviter des erreurs typo. Si vous gardez la “Show command line” active (comparez l'item 3 suivant), vous aurez aussi l'inscription correcte pour toute les options de commande(au cas ou vous voudriez plus tard partir de la ligne de commande et/ou du script). A l'avenir, vous n'aurez qu'à désigner ces commandes qui actionnent l'opération FGCom:

Si vous n'avez pas d'icone disponible pour démarrer FGrun, alors, démarrer FlightGear manuallement:

1. Ouvrez une fenêtre de commande
2. Allez dans le répertoire dans lequel FGFS a été installé
3. Exécutez les commandes suivantes, ou quelque chose de similaire

Linux	fgrun
Linux Git:	cd ~/fgfs sh ./run_fgrun.sh
Windows	C: cd 'C:\Program Files\Flightgear\win32' fgrun.exe

Attendez la fenêtre du programme pou commencer, et ensuite précisez:

1. Commencez par choisir un avion. Pour ce premier essai, nous suggérons le Cessna C172P, ainsi, nous comprendrons la suite. Considérez aussi que certains dessineurs d' avions réattribuant des touches de clavier (p.ex. la barre d'espace”), ainsi, vous pouvez ne pas avoir la touche PTT (“Push To Talk”- Appuyez pour parler-) disponible. VoirFGCOM#Trucs et Astuces.
   → Click "Next".
2. Comme lieu de départ, précisez airport KPAO (Palo Alto) piste 13, ainsi, nous verrons tous les mêmes messages dans les rapports suivants. Une autre raison pour KPAO est que KPAO a les scènes de base par défaut, et donc est valable pour tout le monde.
   → Click "Next".
   

   Basic & multiplayer options
3. Précisez Multiplayer options: (voir Howto: Multiplayer pour les détails).
   • “AI models” doit être activé afin de voir tout le trafic
   • “Multiplayer” doit être activé
   • tapez “mpserverXX.flightgear.org” dans le champ “Hostname:”, remplacez “XX” avec le numéro de serveur le plus proche de vouswit - selectionnez le dans http://pigeond.net/flightgear/mpstatus/. En fait, pas besoin de choisir (as long as it is online and pas aussi encombré que mpserver02) - you might try which server gives you the best response-times.
   • Insert your “Callsign:” (max. 7 characters)
   • define the “in” and “out” ports both with the standard “5000”
   • With "Load/Save as" you may build up yourself a library of settings for different airports.
     → Click "Advanced".
     

     Advanced: Initial Position
4. In the “Advanced Options” check the following sections (click/select them in the left column):
   • General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).
   • Features: “AI Traffic” should be activated already
   • Initial Position: You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: (see next item)
     • Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So do not forget to change/delete the here defined positions if some time you want to start from another airport. Of course you may save/reload settings for different airports, see "Load/save as" on the main window.
       

       MPMap
5. Open the MPMap
   • if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”
   • click on “nav”
   • disable all options except “apt code”
   • type “KPAO” into the filed “Navaids lookup”
   • hit ENTER or click onto the reading-glass symbol
   • click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”
   • now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links”
   • then zoom into the airport
   • set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen
   • type those long/lat values into the field below and also the wanted heading of the plane while parking
     

     Advanced: Network
6. Network: Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.
   • WARNING: When saving these settings and reloading them again, FGRun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".
   • If you need to define the unique IP-Address, open a command-window and type

OS	to type	cap.	returned values
Linux	ifconfig	eth0	Link encap:Ethernet HWaddr 00:1d:92:80:a6:ab inet addr:192.168.178.23 Bcast:192.168.178.255 Mask:255.255.255.0
Windows	ipconfig /all	et	Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF DHCP aktiviert. . . . . . . . . . : Ja Autokonfiguration aktiviert . . . : Ja IP-Adresse. . . . . . . . . . . . : 192.168.178.20 Subnetzmaske. . . . . . . . . . . : 255.255.255.0 IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4

1. • 192.168.178.23 (or 20) is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!!
     

     Advanced: Input/Output
2. Input/Output:
   • You do need a "generic" line as shown, because this defines the interface between FlightGear and FGCom.
     • To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown.
     • Editing an existing line: Start by clicking onto the existing one, then change as required.
     • Deleting an existing line: Click onto the line to be deleted, then hit "Delete"
3. Avionics: let us define:

Nav1:	114.10	San Jose VOR
Nav2:	115.80	SF VOR
ADF:	379	Brijj, beacon at SF

1. • And activate DME to Nav1
   • There is no field to input COM-radios, but remember them for setting them later manually:

Com1	118.60	Paolo Alto
Com2	120.50	San Francisco

1. Properties:
   • Here you can define any presetting for any values in the FGFS. See e.g.: File > Browse Internal Properties in the FlightGear menu.
     

     Advanced: Properties
   • I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
     • Input a new line: Just hit “New” and type your string.
     • Edit a line: Be sure first to click onto an existing item and then edit this “Property”
     • Delete a line: Click onto the line to be deleted then hit "Delete"
2. Hit “OK” → “Run” and watch FlightGear starting. If screen-place allows you may want to pull the shown "FGFS Report-Window" to the side and watch how busy your PC is while loading the other multi-player models.

Start FGCom

Open a command-window and change into the directory in which FGCom was installed (probably the same as FlightGear) and start FGCom. Do not use any other options than the server address “-Sfgcom.flightgear.org.uk”:

Linux	fgcom -Sfgcom.flightgear.org.uk	"-Sfgcom..." with capital "S"
Linux Git	cd ~/fgfs sh ./run_fgcom.sh	for this “Git complete” you do not need to specify the server address, because it is embedded in the script-file.
Windows	cd 'C:\Program Files\Flightgear\win32' fgcom.exe -Sfgcom.flightgear.org.uk	"-Sfgcom..." with capital "S"

For the following test position this command-window somewhere, where you can monitor it throughout the test.

The first response should be:

  /fgcom - a communication radio based on VoIP with IAX/Asterisk 
  (c)2007 by H. Wirtz <wirtz@dfn.de> 
  Version 1.2.2 build 206M 
  Using iaxclient library Version SVN 206M 
  
  Successfully parsed command-line options. 
  Reading list of airports...done. 
  Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk

If your printout up to that line is different go back to chapter Test the basic function

1) If, due to a prior flight, COM1 was set to anything else but 118.600 (e.g. to 119.650) you will see the following 2 lines added to the initialization of the FGCom-window:
Selected frequency: 119.650 Call rejected by remote	Instead of “119.650” there will be shown the last used frequency. In this case the source of the nearest ATC-Freq. 119.650 is more than 50km away from your actual position of the airplane, so FGCom rejects a connection to it. If the last frequency used would have been within 50 km you get an indication very similar to the next item.
2) Switch COM1 to 118.60 (needed at Palo Alto):
Selected frequency: 118.600 Hanging up call 0 Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km) Call 0 accepted Call 0 answered Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)	This last line will be repeated according the to time span you defined in the “Input/Output” command “--generic=socket,in,10,,5500,tcp”, you may change that value later according to your preferences.
3) Press your PTT (PushToTalk on space-bar and joystick, as available):
[SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker [SPEAK] unmute mic, mute speaker [LISTEN] mute mic, unmute speaker	Only in between “SPEAK” and “LISTEN” you are able to talk to others.
Now lets set/verify the other Radios: COM2 = 120.50 San Francisco NAV1 = 114.10 San Jose NAV2 = 115.80 San Francisco 4) Pressing Upper+Space will switch to the next radio: NAV1
Radio-Select: NAV1 Selected frequency: 114.100 Hanging up call 0 Call rejected by remote [LISTEN] mute mic, unmute speaker	Compare this to the NAV2 indication 2 steps later: something is wrong – and it wasn't your fault: Although this NAV is valid (see ...FGFS/data/Airports/apt.dat.gz), it is missing in the FGCom listing .../FGCom/positions.txt. I encountered this problem several times, as well for Airports as also for VOR's. If this happens with your most beloved airport you can add those missing data with a text-editor. But before changing be sure to save the original data somewhere - just in case!
5) Pressing Upper+Space once more switches to COM2
Radio-Select: COM2 Selected frequency: 120.500 Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km) [LISTEN] mute mic, unmute speaker Call 0 accepted Call 0 answered	That looks OK: San Francisco is about 29 km away watch the “km” instead of miles! 10 km = 6.2137 mi
6) Pressing Upper+Space once more switches to NAV2
Radio-Select: NAV2 Selected frequency: 115.800 Hanging up call 0 Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km) Call 0 accepted Call 0 answered [LISTEN] mute mic, unmute speaker	And Yes: The SF VOR is just a little closer than the airport(center)
7) Pressing Upper+Space once more brings back COM1:
Radio-Select: COM1 Selected frequency: 118.600 Hanging up call 0 Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km) Call 0 accepted Call 0 answered [LISTEN] mute mic, unmute speaker
8) Lets us start and continue flying in the direction about 130°:
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km) Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km) Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km) Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km) Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km) Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km)	notice that you first come closer (to the center of the airport) and after that getting away
9) Let's switch to COM2 (San Francisco) and watch:
Radio-Select: COM2 Selected frequency: 120.500 Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km) Call 0 accepted Call 0 answered [LISTEN] mute mic, unmute speaker Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km) Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km) .. Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km) Hanging up call 0 Radio-Select: NAV2 Selected frequency: 115.800 Call rejected by remote [LISTEN] mute mic, unmute speaker	That means: at about 50KM we are getting out of range and thus the on COM2 active SF getts terminated. Notice that also the inactive NAV2 gets terminated, because it exceeded the allowable range at about the same time!

10) You could turn now and watch the opposite: At about the same distance those two will become active again (automatically, if you did not change the settings).

If you got here without any (technical) problems your FGCom is fully functional. Have fun when using it.

Using FGCom

There are basically three types of FGCom-usage:

• Normal usage at airports: i.e. You set your radio to the airport as usual. Thus you are set up for the usual ATC-(keyboard)-procedures (either through the "'" (UpperCase#) and/or the Chat-Menus). In addition you then can talk to anybody in a radius of about 50 km (about 30 miles) around the airport, may that be friends, a maintained FGCOM-ATC/Twr-Operator, airport utilities, etc.. Be aware that as of April 2009 only very few planes are using the FGCOM for ATC-purposes - thus you should always use the ATC-Chat "keyboard"-procedures to announce arrivals/departures/taxiing etc. in addition. (We hope that may change in some future!)
• The AirToAir frequencies (122.75 and 123.45) are ideal for all Multiplayer events. They are without any range-limitations - and not yet "overcrowded!). Also when traveling you might want to listen on the 122.75 for others who want to contact you (or reverse). When there is much "talk" on the 122.75 you might just arrange with your partner to switch to 123.45 - and return to 122.75 afterward. As of April 2009 the 122.75 is already operational for this application, the 123.45 will follow soon. You may try from time to time if this limitations still exist.
• Finally you can manipulate the frequency-tables (positions.txt in your FGFS/FGCOM local directory) and define an own frequency for special events. e.g. a Flight-School at one airport with maybe multiple student-groups. Of course those are local manipulations on your own PC, which you have to agree on with your (planned to be) partners in advance.

Supplemantery Information

Tips and Tricks

Airport missing in FGCom:

In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “positions.txt” in your fgcom directory. See e.g. the line

  KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl

You can add extra lines for any locations you want. e.g.: (watch the separation comas)

apt-code = DUMY   (a "dummy" or your favorite, but missing, airport code)
KHz      = take it out of your “FGFS-home/data/Airports/apt.dat.gz”
           or just take one of which you are sure that you do not need it in the FGFS-reality
           (notice that several Airports (far apart) use same frequencies!
long/lat = take out of the Mpmap (or Google Map)
type     = whatever
name     = whatever

(of course those definition are only known to your own PC and last only until the next data update!)

Editing FGCOM-Data-Files

If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.

• For windows you can use "WordPad"
• For Linux the "gedit" works fine

Copying-Printing this WIKI-Page

If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:

• to copy:
  • select in the Browser-Menu: "File" --> "Save Page as.. "
• to print:
  • go to the printable version.
  • Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply"
  • before printing I recommend: Menu --> File --> "Print Preview" and you see those many many pages!
  • If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer

Joystick compatibility between Operating Systems:

Consultez la page Joystick à ce sujet.

You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you already. Check e.g. (Unix, Mac, Win having assigned different "numbers"):

<axis>        (instead of the usual <axis n=”3”> )
 <desc>Mixture</desc> 
 <number> 
  <unix>3</unix> 
  <mac>5</mac> 
  <windows>5</windows> 
 </number> 
 <binding> 
  <command>nasal</command> 
  <script>controls.mixtureAxis()</script> 
 </binding> 
</axis>

Assign PTT to joystick

If you want to assign the PushToTalk function to your joystick, add the following (for n you have to find your own number!)

<button n="x"> 
 <desc>PTT - Push To Talk</desc> 
 <binding> 
  <command>nasal</command> 
  <script>controls.ptt(1)</script> 
 </binding> 
 <mod-up> 
  <binding> 
   <command>nasal</command> 
   <script>controls.ptt(0)</script> 
  </binding> 
 </mod-up> 
</button>

Helpful internet adresses

World-Time:

• standard deviations
• direct conversions

Especially for multiplayer events you should define all times in the internationally used GMT (Greenwich Meantime). Just pick up your deviation from GMT and memorize it. If everybody does it, we could avoid a lot of misunderstandings.

• Decimal to Degree http://www.hbnweb.de/mathematik/grad-dezimal.html
  

  Some programs need Decimal Lon/Lat values, others the Degrees/Minutes/Sec. Just convert it.
  
  

• Miles, km, feet, etc. etc. ...: http://www.convertunits.com/

  If like to avoid troubles (like NASA lost a satellite because of it) just look it up.

Ports needed

In case of problems over the internet you might check that the the following ports are allowed:

1314	TCP	if the Festival-Server is used for Text/Sound 
2005	UDP	Vcp-Stream
4569	UDP	FGCom  VoIP, (Inter-Asterisk eXchange)
5000	UDP	in/out Multiplayer    (VPN Sftw.)
5001	UDP	Enable HTTP-server
5002	UDP	Enable property server
5003	UDP	Enable Screen-Shot services
5004   UDP     (may be used as a spare)
5505	UDP	Terra Sync
16661	UDP	FGCom listening to FGFS, usually “local host” only

Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).

Commandline Parameters

fgcom --help

returns the following useful info

   fgcom - a communication radio based on VoIP with IAX/Asterisk
   (c)2007 by H. Wirtz <wirtz@dfn.de>
   Version 1.2.2 build 163M
   Using iaxclient library Version SVN 163M
 
 OPTION                                        DESCRIPTION
 
 -d, -debug, --debug=                          show debugging information
 -S, -voipserver, --voipserver=                voip server to connect to (default: 'fgcom1.parasitstudio.de')
 -s, -fgserver, --fgserver=                    network device to connect to  (default: 'localhost')
 -p, -port, --port=                            where we should listen to FG (default: '16661')
 -a, -airport, --airport=                      airport-id (ICAO) for ATC-mode
 -f, -frequency, --frequency=                  frequency for ATC-mode
 -U, -user, --user=                            username for VoIP account (default: 'guest')
 -P, -password, --password=                    password for VoIP account (default: 'guest')
 -i, -mic, --mic=                              mic input level (0.0 - 1.0)
 -o, -speaker, --speaker=                      speaker output level (0.0 - 1.0)
 -b, -mic-boost, --mic-boost=                  enable mic boost
 -l, -list-audio, --list-audio=                list audio devices
 -r, -set-audio-in, --set-audio-in=            use <devicename> as audio input
 -k, -set-audio-out, --set-audio-out=          use <devicename> as audio output
 -c, -codec, --codec=                          use codec <codec> as transfer codec (default: 'u')
 
 Available codecs:
       u - ulaw (default and best codec because the mixing is based onto ulaw)
       a - alaw
       g - gsm
       s - speex
       7 - G.723
 
 Mode 1: client for COM1 of flightgear:
       $ fgcom
 - connects fgcom to fgfs at localhost:16661
       $ fgcom -sother.host.tld -p23456
 - connects fgcom to fgfs at other.host.tld:23456
 
 Mode 2: client for an ATC at <airport> on <frequency>:
       $ fgcom -aKSFO -f120.500
 - sets up fgcom for an ATC radio at KSFO 120.500 MHz
 
   Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!

Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so do not use -U or -P

Server installation

Consultez la page Howto: Set up a FGCom server à ce sujet.

External links

• fgcom(SourceForge-Project) Subversion is available here. If you haven't used Subversion before, you might find it easier to fetch a archive instead.
• latest source available here (?): http://code.google.com/p/fgcomgui/

Deprecated or broken links

• Old Official website
• Manual

Status

• March, 2009:

Adding User-Information for installing, using, maintaining FGCOM on different platforms.

• 18 November, 2008:

Latest SVN (rev 163) has the compile problems fixed. Also we have a new server: fgcom.flightgear.org.uk. User accounts not required (ie. do not use -U or -P)

• 31 October, 2008:

The latest SVN release at this time is the r149 which does not compile due to a constant that is not defined (STL_STRING). Such constant appears at line 57 in the file src/fgcom_init.cpp which is: #include STL_STRING

I guess that such constant must point to the STL library include file but I am not sure. I revert to the r148 SVN version which successfully compiles.

Command to get such version is: svn co -r148 svn://svn.dfn.de:/fgcom/trunk fgcom-r148

• 19 June, 2008: Currently the server is down due to hardware problems. It is unknown when the service comes back because he currently has no time to fix the problems.

• 22 November 2007: Due to heavy development at this time there may be some differences between the information on the web pages and the installation. Please follow the discussions on the FlightGear development list!

Related content

• FlightGear related projects
• FGComGui