Changes

Jump to: navigation, search

FGCom (before 3.0)

134 bytes added, 17:37, 8 March 2011
m
Robot: Cosmetic changes
In the future FGCom surely will extend further and surely will get a “Speech to Text” capability in order to also integrate the text-based automated ATC-routines inside FlightGear.
==The Client installation=====Prequisites=======Hardware Requirements====
If you are satisfied with the operation and responsetimes of your current FlightGear installation, then you should see no significant difference after adding the FGCom. If your FlightGear installation runs already a little marginal, then you might experience some delays when many new airplane-models etc. must be loaded. This may happen when starting up at a busy airport. You can monitor/verify such a "short-time overload" in the FlightGear command-window.
Of course you will also need a connection to the internet for this real-time, worldwide voice communication.
====Software requirements====
{| border="1"
|align="center" width="90px" |'''FlightGear''' ||The basic [[FlightGear]] Flight Simulation installation. This must be installed prior to installing FGCom ''(except if installing the Linux "Git complete" version which can install FGCom and FlightGear concurrently)''.
|}
====Nice to have====
{| border="1"
|align="center" width="90px" | '''FGrun'''||This [[FlightGear Launch Control]] (also known as FG Wizard), is a graphical front end to start the FGFS. This makes it very easy to startup the FGFS with all it's possible options. In some newer distributions this is already part of the basic FGFS installation package
|}
===Installing FGCom=======Install on Linux====
For Linux-Systems there are three ways to install:
Then continue with testing on [[FGCOM Testing]].
====Install on Mac====
'''MacFlightGear 1.9.1/2.0.0'''<BRbr />
You can download the "MacFlightGear"-Application from the [http://www.flightgear.org/Downloads/binary.shtml#mac FlightGear download-center]. The current version 2.0.0 of the code does contain the FGCom and works for OSX >= 10.5. (with OSX versions < 10.5 you will end up with a generic "bus error" message).
====Install on Windows====
Please use the Windows installation description, available through [[FGCOM for Windows]].
===Testing===
During testing we will test/adjust:
# the basic FGCom functions without FlightGear
For these tests please refer to [[FGCOM Testing]].
===Functional test & user briefing===
Experiences pointed out, that the cooperation between FGCom and FlightGear works more reliable, if FlightGear is started first. So we will start with setting up a flight-test-environment:
====Start FlightGear====
We suggest to use [[FGRun]] to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), 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 FGCom-operation:
|-
! style="background:#efefef" | Linux Git:
|cd ~/fgfs<br/>sh ./run_fgrun.sh
|-
! style="background:#efefef" | Windows
|C:<br/>cd 'C:\Program Files\Flightgear\win32'<br/>fgrun.exe
|}
Wait for the program window to start and then define:
# Start by '''choosing an airplane'''. For this first try we suggest the [[Cessna C172]]P, 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 may not have the PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]].<br/>→ Click "Next".# As '''starting place''' please define the [[airport]] KPAO (Palo Alto) runway 13, so we all see the same messages in the following reports. A second reason for KPAO is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br/>→ Click "Next".[[ImageFile:FGrun_base.jpg|thumb|Basic & multiplayer options]]
# Define the '''Multiplayer options:''' (see [[Howto: Multiplayer]] for details).
#* “AI models” must be activated in order to see all traffic
#* 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.<br/>→ Click "Advanced".[[ImageFile:FGrun_IP.jpg|thumb|Advanced: Initial Position]]
# 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.[[imageFile:MPmap.jpg|thumb|[[MPMap]]]]#Open the '''[http://mpmap01.flightgear.org 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[[ImageFile:FGrun_net.jpg|thumb|Advanced: Network]]
# '''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".
|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
|-
! style="background:#efefef" | Windows
|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
|}
#*'''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 “,”!![[imageFile:FGrun_IO.jpg|thumb|Advanced: Input/Output]]#'''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"
#'''Avionics:''' let us define:
{|
! style="background:#efefef" | Nav1:
|}
#'''Properties:''' #* Here you can define any presetting for any values in the FGFS. See e.g.: <tt>File > Browse Internal Properties</tt> in the FlightGear [[menu]].[[imageFile:FGrun_prop.jpg|thumb|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.
# 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 line|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”:
{|
|-
! style="background:#efefef" |Linux Git
| cd ~/fgfs<br/>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.
|-
! style="background:#efefef" |Windows
|cd 'C:\Program Files\Flightgear\win32'<br/>fgcom.exe -Sfgcom.flightgear.org.uk
|"-Sfgcom..." with capital "S"
|}
|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.
|-
|<br/>3) Press your PTT (PushToTalk on space-bar and joystick, as available):
|-
|
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.
|-
|<br/>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'''
|-
|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!
|-
|<br/>5) Pressing Upper+Space once more switches to '''COM2'''
|-
|
Call 0 accepted
Call 0 answered
|That looks OK: San Francisco is about 29 km away<br/><br/>watch the “km” instead of miles!<br/>'''10 km''' = '''6.2137 mi'''
|-
|<br/>6) Pressing Upper+Space once more switches to '''NAV2'''
|-
|
|And Yes: The SF VOR is just a little closer than the airport(center)
|-
|<br/>7) Pressing Upper+Space once more brings back '''COM1''':
|-
|
[LISTEN] mute mic, unmute speaker
|-
|<br/>8) Lets us start and continue flying in the direction about 130°:
|-
|
|notice that you first come closer (to the center of the airport) and after that getting away
|-
|<br/>9) Let's switch to '''COM2''' (San Francisco) and watch:
|-
|
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 Informations=======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
''(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 [http://wiki.flightgear.org/index.php?title=FGCOM&printable=yes 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:=====
{{Main article|Joystick}}
</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">
</button>
====Helpful internet adresses====
'''World-Time:'''
* [http://www.timeanddate.com/worldclock/custom.html?sort=1 standard deviations]
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 <br/>*: Some programs need Decimal Lon/Lat values, others the Degrees/Minutes/Sec. Just convert it.<br/><br/>
* '''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.
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
Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''
==Server installation==
{{Main article|Howto: Set up a FGCom server}}
==External links==
* [http://squonk.abacab.org/dokuwiki/fgcom Old Official website] DOWN!
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual] DOWN!
* latest source avaiable here (?): http://code.google.com/p/fgcomgui/
==Status==*'''March, 2009:'''
Adding User-Informations 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:
* '''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]]
[[Category:Software]]
4,400
edits

Navigation menu