FGCom (before 3.0): Difference between revisions

Open a [[Command line|command-window]] and change into the directory in which FGCom was installed (probably the same as FlightGear) and start FGCom. You must decide what server you want to use! Since Oct.2012 there are 2 FGCOM-servers available:

# The original: '''fgcom.flightgear.org'''

# A new one: '''delta384.server4you.de'''

So insert the server-address after a "-S" (watch: The "S" must be a capital!):

{|

! style="background:#efefef" |Linux  

|fgcom -Sfgcom.flightgear.org

! style="background:#efefef" |Linux Git

| for this “Git complete” you do not need to specify the server address, because it is embedded in the script-file.

|cd 'C:\Program Files\Flightgear\win32'<br />fgcom.exe -Sfgcom.flightgear.org

The first response should be:

   Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org

 

|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: ||

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):

|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'''

|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''':

|<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:  

|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).