FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 11:44, 12 March 2009

7,770 bytes added ,  12 March 2009
m
→‎Testing: just inputting the raw text for Chap. "Func.Test", will be finalized later
(→‎Tips and Tricks: add PTT hints)
m (→‎Testing: just inputting the raw text for Chap. "Func.Test", will be finalized later)
Line 167: Line 167:
<br>'''In case of trouble''' check the following:
<br>'''In case of trouble''' check the following:


*'''"parsed commandline options"''' not successful: Check for wrong commands and/or missing “-” signs in front of them. See [[FGCOM#FGCom Options|FGcom Options]].
*'''"parsed command-line options"''' not successful: Check for wrong commands and/or missing “-” signs in front of them. See [[FGCOM#FGCom Options|FGcom Options]].
*'''"Reading list of airports .."''' not succesfull: 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 erros, allthough lines of both files may be exchanged/added).
*'''"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”)!  
*'''"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.
*No response '''"Call 0 accepted"''': Check your network.
*If you did not hear the '''"delayed response"''' echoed back, check the Chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]].
*If you did not hear the '''"delayed response"''' echoed back, check the Chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]].
--[[User:Jomo|Jomo]] 01:01, 7 March 2009 (EST)
--[[User:Jomo|Jomo]] 01:01, 7 March 2009 (EST)
====Functional Test + User Briefing====
=====Preflight=====
There is no real significance in the order in which we start FGFS and FGCom. Let us start the FGCom first, so that we can watch all of it's behavior from the beginning and then progress in a predefined order of appearance.
Open a [[command|command-window]] and change into the directory in which FGCom was installed (probably the same as the FGFS) and start the FGCom. Do not use any other options than the server address “-sfgcom.flightgear.org.uk”, so  that we all see the same indications throughout this description:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs<br>sh ./run_fgcom.sh
||for this “CVS complete” you do not need to specify the server address, because it is embedded in the script-file.
|-
||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk<br>sh ./run_fgcom.sh || "-Sfgcom..." with capital "S"
|-
||for Windows e.g.: ||D:<br>cd \flightgear<br>fgcom -sfgcom.flightgear.org.uk || "-sfgcom..." with small "s"
|-
||for Mac: || ||
|}
You should then see:
  /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 is different see Chapter [[Test the basic function]]
Keep this command-window open and accessible for further status/problem indications.
'''Prepare the FGFS-start in FGrun:'''<br>
We suggest to use the FGrun ([[FlightGear Launch Control]]) to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” (compare item 3) active, you also get the correct writing for all the command-options (in case you later want to start from a command-line and/or out of a script). In the following we will just point out those commands which are significant for the FGCom-operation:
If you don't have an Icon available to start the FGrun, then
:use a command-window (like above for the FGCom)
:change into the directory in which FGFS was installed
:and start the program from there:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs<br>sh ./run_fgrun.sh
|-
||for Std. Linux e.g.: ||fgrun
|-
||for Windows e.g.: ||D:<br>cd \flightgear<br>fgrun
|-
||for Mac: || ToBeDefined ||
|}
Wait for the Program-Window to start and then define:<br><br>
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you won't have the  PTT-key (“Push To Talk”) available. See [[Tips/Tricks]])<br>
→ Click “Next”<br><br>
'''2)''' As '''starting place''' we suggest KPAO-13 (Livermore), so we all see the same messages in the following reports. A second reason is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br>
→ Click “Next”<br><br>
'''3)''' Define the '''Multiplayer options:''' (see wiki “Multiplayer” for details)
=====FGrun_Base
#“AI models” must be activated in order to see all traffic
#“Multiplayer” must be activated
#type “mpserverXX.flightgear.org” into the field “Hostname:”, replace “XX” with the available server number nearest you. Actually it does not matter which server you take (as long as it is online) - 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”
#→ Click “Advanced”<br>
'''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:
##open  http://mpmap01.flightgear.org
##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 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
##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 you want to start from another airport.
====> Initial pos
'''5) 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. If you need it, open an [[Command-window|command]] and type
{|border="1"
|+
|width="100"|OS
|width="75"|'''to type'''
|width="40"|Cap. ||returned values
|-
||for linux: ||ifconfig ||eth0 ||
Link encap:Ethernet  HWaddr 00:1d:92:80:a6:ab
<br>inet addr:'''192.168.178.23'''  Bcast:192.168.178.255  Mask:255.255.255.0
|-
||for Windows: ||ipconfig /all ||et ||
Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF
<br>DHCP aktiviert. . . . . . . . . . : Ja
<br>Autokonfiguration aktiviert . . . : Ja
<br>IP-Adresse. . . . . . . . . . . . : '''192.168.178.20'''
<br>Subnetzmaske. . . . . . . . . . . : 255.255.255.0
<br>IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4
|-
||for Mac: || || ||
|}
The  '''192.168.178.23''' (or '''20''') is the number you would have to input between the to commas. Be very careful and double-check that you do not mistype “.” and “,”!!
'''6) Input/Output:''' This defines the interface between FGFS and FGCom.
=====> Input/Output
To input a new line: Start by selecting “generic” in 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
'''7) Avionics:''' let's define:
{|
|+
|-
|width="70"|
|width="70"|Nav1:
|width="100"|114.10 ||San Jose VOR
|-
| ||Nav2: || 115.80 ||SF  VOR
|-
| ||ADF: || 379 || Brijj, beacon at SF
|}
and activate: DME  to Nav1<br><br>
There is no field to input COM-radios, but remember them for manual setting later:
{|
|+
|-
|width="70"|
|width="70" |Com1
|width="100" |118.60 ||Paolo Alto
|-
| ||Com2 || 120.50 || San Francisco
|}
'''8) Properties:''' Here you can define any presetting for any values in the FGFS<br>see e.g.: FGFS-menu-bar --> File --> “Browse Internal Properties”
====> Properties
e.g. I personally do not want the plane to start rolling without me telling it. So I set the parking break as default at startup.
:Input new: Just hit “New” and type your string.
:Edit: Be sure first to click onto an existing item and then edit this “Property”
=====On the Ground=====
=====In the Air=====


====Solving Audio-Problems====
====Solving Audio-Problems====
Line 182: Line 339:


more Tests / TestSetups etc. ToBeDefined
more Tests / TestSetups etc. ToBeDefined
====Final Tests====
ToBeDefined


===Using FGCom===
===Using FGCom===
Jomo
652

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/11140"

Navigation menu