FGCOM Testing: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(Starting a new Help)
 
m (/* The Initial test of the standalone FGCOM Installation --> continuing new input)
Line 15: Line 15:
|+
|+
|-
|-
|align="center"|fgcom||the command ''(in case you installed by using the [[Scripted_Compilation_on_Linux_Debian/Ubuntu|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 -Sfgcom.flightgear.org.uk -f910)''
|align="center"|fgcom||the command ''(in case you installed by using the [[Scripted_Compilation_on_Linux_Debian/Ubuntu|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'''")''
|-
|-
|align="center"|-Sfgcom.flightgear.org.uk||the central server for FGCOM
|align="center"|-Sfgcom.flightgear.org.uk||the central server for FGCOM
|-
|-
|align="center"|-f910||the only available frequency for echo-tests
|align="center"|-f910||the only available frequency for echo-tests
|-
|align="center"|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 !!!)''


<br>That should give you the following output:
<br>That should give you the following output:
Line 39: Line 43:
*and continue with the next chapter.
*and continue with the next chapter.
<br>'''In case of trouble''' check the following most probable errors:
<br>'''In case of trouble''' check the following most probable errors:
<ul><li>Typically if you did not define the correct '''Home-Directory''' for FGCOM
{|border="1"
|+
|-
||typical for '''Windows'''-Systems
||typical for '''Linux'''-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.
||
/home/emmerich/Desktop/Link to fgcom: line 1: cd: /home/emmerich/fgf: No such file or directory
sh: Can't open run_fgcom.sh
|}
<ul><li>The system is right: I gave it (for testing) a wrong directory!</li></ul></ul>
<br><br>
<ul><li>Typically for a '''TYPO''' (mistyped command or option) would be:</li>
<ul><li>Typically for a '''TYPO''' (mistyped command or option) would be:</li>
  ./fgcom - a communication radio based on VoIP with IAX/Asterisk
  ./fgcom - a communication radio based on VoIP with IAX/Asterisk
Line 46: Line 70:
   
   
  '''AL lib: alsa.c:564: set access failed: Invalid argument'''
  '''AL lib: alsa.c:564: set access failed: Invalid argument'''
  Successfully parsed commandline options.
  Successfully parsed command-line options.
  Reading list of airports...done.
  Reading list of airports...done.
  Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
  Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
most likely you may have
most likely you may have
<ul><li>forgotten a "-"sign in front of an option</li>
<ul><li>defined a wrong Frequency to use or you may have forgotten to define one. You '''must define -f910'''</li>
<li>forgotten a "-"sign in front of an option</li>
<li>or typed a small "-sfgcom..." instead the capital "-Sfgcom..."</li>
<li>or typed a small "-sfgcom..." instead the capital "-Sfgcom..."</li>
<li>or mistyped the Server-Name or defined a wrong FGCOM-Server</li>
<li>or other typos.</li></ul>
<li>or other typos.</li></ul>



Revision as of 05:40, 24 September 2009

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:

  1. Initial test of the standalone FGCOM Installation
  2. Test FGCOM together within the FlighGear Simulator
  3. 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) !

  1. 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 the mic 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 typical for Linux-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.
      
      /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
      • or typed a small "-sfgcom..." instead the capital "-Sfgcom..."
      • or mistyped the Server-Name or defined a wrong FGCOM-Server
      • or other typos.
    • "Reading list of airports .." not successful: Check your file “positions.txt” which should be in the same directory in which you installed the FGCom. This is a normal text-file in which you can add missing informations. (Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added).
    • "Initializing IAX client" not successful: Check if you defined the right server, it must be "-Sfgcom.flightgear.org.uk”. Watch it: The “S” must be capital in Linux, but small for Windows (“-sfgcom.flightgear.org.uk”)!
    • No response "Call 0 accepted": Check your network, especially your firewall for open ports.