FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 09:36, 13 March 2009

5,597 bytes added ,  13 March 2009
→‎On the Ground: adding new chapter "FGCom cooperating with FGFS
(→‎Preflight: finalize the preflight chapter)
(→‎On the Ground: adding new chapter "FGCom cooperating with FGFS)
Line 352: Line 352:
--[[User:Jomo|Jomo]] 13:55, 12 March 2009 (EDT)
--[[User:Jomo|Jomo]] 13:55, 12 March 2009 (EDT)


=====On the Ground=====
=====FGCom cooperating with FGFS=====
In the open FGrun program-window hit “OK” → “Run” and watch the FGCom command-window (constantly, if screen-space allows):
{|
|+
|-
|width="300"| ||
|-
|1) If COM1 was set to 119.650 during a prior session you will now see the following 2 lines added to the initialization of the FGCom-window, as soon as FGFS comes up: ||
|-
|
Selected frequency: 119.650
Call rejected by remote
|
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 the for this airport needed 118.60:
|-
|
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
|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):
|-
|
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.
|-
|<br>Now lets set the other Radios:
*COM2 = 120.50 San Francisco
*NAV1  = 114.10 San Jose
*NAV2  = 115.80 San Francisco
4) Pressing Upper+Space will now switch to the next radio: '''NAV1'''
|-
|
Radio-Select: NAV1
Selected frequency: 114.100
Hanging up call 0
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|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'''
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km)
[LISTEN] mute mic, unmute speaker
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'''
|-
|
Radio-Select: NAV2
Selected frequency: 115.800
Hanging up call 0
Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|And Yes: The SF VOR is just a little closer than the airport(center)
|-
|<br>7) Pressing Upper+Space once more brings back '''COM1''':
|-
|
Radio-Select: COM1
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|-
|<br>8) Lets us start and continue flying in the direction about 130°:
|-
|
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km)
|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:
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km)
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km)
..
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km)
Hanging up call 0
Radio-Select: NAV2
Selected frequency: 115.800
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|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).
<br><br>
If you got here without any (technical) problems your FGCom is fully functional. All you have to do now, is trying to test the audio.
=====Audio Test=====
There is no formal Test-Environment for that. Just cruise within the San Francisco (or any other) area and listen and/or try calling from time to time:  “This is ''YourCallSign'', is somebody listing” or similar. If you hear somebody talking (and it is not the AI-ATC chatter!) but get no answers, see the chapter "Solving Audio-Problems".
--[[User:Jomo|Jomo]] 05:36, 13 March 2009 (EDT)
 
=====In the Air=====
=====In the Air=====


Jomo
652

edits

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

Navigation menu