FGCOM Testing
This "FGCOM_Testing" is intended to support FGCOM-users in debugging their FGCOM-System directly after installation, but also for those who want to verify the basic functionality or want to readjust the audio-system. It covers the following 3 areas in more detail:
- Initial test of the standalone FGCOM Installation
- Test FGCOM together within the FlighGear Simulator
- Adjust the Microphone and Speaker (or joystick, etc.) volumes
Of course the prerequisite for the following is that you have already installed the FGCOM (see the FGCOM-main-page) !
-
The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"
Prior to executing the following command change into the directory, into which the FGCom was installed. After the then shown path (and "$") type the "fgcom"-command with the required/wanted options. For a detailed description of all available options see Commandline Parameters - in the following we will only show the usually required options:
fgcom -Sfgcom.flightgear.org.uk -f910
fgcom the command (in case you installed by using the download_and_compile.sh script for LINUX-Systems you have to replace the command "fgcom" with "sh ./run_fgcom.sh". Then the complete command would be: "sh ./run_fgcom.sh -f910") -Sfgcom.flightgear.org.uk the central server for FGCOM -f910 the only available frequency for echo-tests optional In case your audiosystem is rather weak, you may try the options: -i and/or -o: i=input(microphone) o=output(Speaker), both values between 0.0 and 1.0 (e.g.: -i0.9)
You do not need any Login-Passwords and/or User-Names !!!
That should give you the following output: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 Successfully parsed commandline options. Reading list of airports...done. Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk Call 0 accepted Call 0 answered
Speak into your microphone and your words should be echoed back with a short delay. e.g. say "one" - and you should notice that the "one" is returned after you finished speaking it.
If that was OK- type ctrl-C to exit this Quick-Test
- and continue with the next chapter.
In case of trouble check the following most probable errors:- Typically if you did not define the correct Home-Directory for FGCOM
typical for Windows-Systems: C:\Users\emmerich>cd \Programme\Fxx The System cannot find the given path. C:\Users\emmerich>fgcom.exe -Sfgcom.flightgear.org.uk -f910 The command "fgcom.exe" is either mistyped or could not be found.
typical for Linux-Systems: /home/emmerich/Desktop/Link to fgcom: line 1: cd: /home/emmerich/fgf: No such file or directory sh: Can't open run_fgcom.sh
- The system is right: I gave it (for testing) a wrong directory!
- Typically for a TYPO (mistyped command or option) would be: ./fgcom - a communication radio based on VoIP with IAX/Asterisk (c)2007 by H. Wirtz <wirtz@dfn.de> Version 1.2.2 build 223M Using iaxclient library Version SVN 223M AL lib: alsa.c:564: set access failed: Invalid argument Successfully parsed command-line options. Reading list of airports...done. Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk most likely you may have
- defined a wrong Frequency to use or you may have forgotten to define one. You must define -f910
- forgotten a "-"sign in front of an option
- typed a small "-sfgcom..." instead the capital "-Sfgcom..."
- mistyped the Server-Name or defined a wrong FGCOM-Server
- or you may have created your own "typos" (lol).
- Typically if the "Phone-book" and/or "positions" cannot be found and/or are damaged: ./fgcom - a communication radio based on VoIP with IAX/Asterisk (c)2007 by H. Wirtz <wirtz@dfn.de> Version 1.2.2 build 223M Using iaxclient library Version SVN 223M AL lib: alsa.c:564: set access failed: Invalid argument Successfully parsed commandline options. Reading list of airports...Cannot open /home/emmerich/fgfs/install/fgcom/fgcom/positions.txt fopen: No such file or directory Stopping service. (etc)
- check the directory in which the FGCOM is installed for the files "phonebook.txt" and "positions.txt". These are normal text-files in which you can add missing informations with a standard editor, for Windows you should use the "WordPad" (not the "Editor")). Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added.
- Typical Network or Firewall problem: ./fgcom - a communication radio based on VoIP with IAX/Asterisk (c)2007 by H. Wirtz <wirtz@dfn.de> Version 1.2.2 build 223M Using iaxclient library Version SVN 223M AL lib: alsa.c:564: set access failed: Invalid argument Successfully parsed commandline options. Reading list of airports...done. Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk I.e. everything is fine, except the final Call 0 answered is missing.
- Check your network by using some other application (e.g. your file browser to look up an usually not used http-address - if you use a recently used address the answer might be out of your locally saved copies - even so the network is not connected! (e.g. use "http://mainz.de/")
- If you use a firewall (what you should - out of general safety reasons!) make sure the ports 2005 UDP Vcp-Stream 4569 UDP FGCom VoIP, (Inter-Asterisk eXchange) 5000 UDP in/out Multiplayer (VPN Sftw.) 16661 UDP FGCom listening to FGFS, usually “local host” only are enabled for your PC.
-
Test FGCOM together within the FlighGear Simulator
In the forgoing chapter you checked the FGCOM as a standalone application. Now we will test whether the FGFS (FlighGear Flight-Simulator) itself and the FGCOM work together, inclusive the PTT-button (PushToTalk, usually the space-bar) and the internal connections via the assigned ports.
For this test- start the FGFS with any plane at any airport you like
- start the FGCOM (usually it does not matter which one starts first - but in case of trouble you should start in this sequence!)