FGCOM Testing: Difference between revisions

Jump to navigation Jump to search

FGCOM Testing (view source)

Revision as of 09:18, 1 October 2009

463 bytes added ,  1 October 2009
m
→‎Test the FGCOM together with the FlighGear Simulator: fill in some more hints
m (structural changes)
Line 141: Line 141:
For this test
For this test
<ol><li>start the FGFS with any plane at any airport you like
<ol><li>start the FGFS with any plane at any airport you like
<br><br><li>start the FGCOM (usually it does not matter which one starts first - but in case of trouble you should try to start in this sequence!)</li>
<br><li>if the FGCom Command-window initiates, but does not respond to any COMM or PTT activity:
<ul><li>Try to enforce (the usually predefined) port as option. i.e. add the option “-p16661” to the FGCom Start-Command
<li>check the FGrun extended Options → Input/output “generic=socket..”: The port there must be the same as for the FGCom, i.e. 16661 (if it was not intentionally changed by you)
<li>You may try to change the interface-port to e.g. UPD 5004. In this case you have to watch 3 places:
<ul><li>add the option “-p5004” to the FGCom start-command
<li>also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004.
<li>and you may have to tell your Firewall to allow port UPD 5004
<br><br></ul></ul>
<li>in the FGFS menu-bar select: "Equipment" --> "Radio Settings"
<br><br><li>into the field "COM1" enter the frequency "910.00" then click "Apply" (and "OK" if you want to close the Pop-up.)
<br><br><li>'''make sure the FGFS is the active window - so whenever something does not work out as expected click with the mouse somewhere into the Main-FGFS-window '''(that will activate the window)''' and then retry the last action(s)!!!'''


<br><br><li>Push the PTT ''(normally the Space-Bar (if you reassigned the PTT to another key - use that one!))'' and speak into your microphone:
<br><br>
<ul><li>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.
<li>start the FGCOM (usually it does not matter which one starts first - but in case of trouble you should try to start in this sequence!)</li>
<li>'''if you heard''' that echo:
 
<ul><li>keeping the PTT pressed for about 3 sec and watch for a possible start of "funny noises".
<br>
<li>if those occur continue with chapter [[#Adjust the Microphone and Speaker volumes|Adjust the Microphone and Speaker volumes]]
<li>click in the FGFS menu-bar onto "Equipment" --> "Radio Settings"
<li>otherwise switch your COM1 back to the frequency wanted --> continue with the next numbered item.
*into the field "COM1" enter the frequency "910.00" then click "Apply" (and "OK" if you want to close the Pop-up.)
</ul>
*'''make sure the FGFS is the active window - so whenever something does not work out as expected click with the mouse somewhere into the Main-FGFS-window '''(that will activate the window)''' and then retry the last action(s)!!!'''
<li>'''if you did not hear''' the echoed return
 
<br>
<li>if the FGCom Command-window initiates, but does not respond to any COMM-Frequency setting:
<br>That would indicate a pure Port/Interface problem between the FGCOM and the FGFS.
*Try to enforce (the usually predefined) port as option. i.e. add the option “-p16661” to the FGCom Start-Command
*check the FGrun extended Options → Input/output “generic=socket..”: The port there must be the same as for the FGCom, i.e. 16661 (if it was not intentionally changed by you)
*You may try to change the interface-port to e.g. UPD 5004. In this case you have to watch 3 places:
**add the option “-p5004” to the FGCom start-command
**also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004.
**and you may have to tell your Firewall to allow port UPD 5004
*anyhow make sure all these 3 places contain the same Port-number !!!
 
<br>
<li>Push the PTT ''(normally the Space-Bar (if you reassigned the PTT to another key - use that one!))'' and speak into your microphone:
*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 you heard''' that echo:
**keeping the PTT pressed for about 3 sec and watch for a possible start of "funny noises".
***if those occur continue with chapter [[#Adjust the Microphone and Speaker volumes|Adjust the Microphone and Speaker volumes]]
***otherwise switch your COM1 back to the frequency wanted --> continue with the next numbered item.
<ul><li>'''if you did not hear''' the echoed return
<ul><li>Test your PTT: Watch the FGCOM messages in the FGCOM-Window:
<ul><li>Test your PTT: Watch the FGCOM messages in the FGCOM-Window:
<li>When pushing the PTT they must switch between
<ul><li>When pushing the PTT they must switch between
</ul></ul></ul>
     [SPEAK] unmute mic
     [SPEAK] unmute mic
     [LISTEN] mute mic
     [LISTEN] mute mic
Did they switch?
***If they did not switch you probably use an airplane model that has reassigned the Space-bar to another function:
<li>If they did not switch see chapter
**Check the “''YourPlane''-set.xml” file in your FGFS/data/Aircraft/YourPlane directory: If you find a line “<key n="32">” then this plane is intentionally  using “key 32” (Space) for something other than the PTT. Known planes that do that as of Feb. 2009 are: an2, bluebird-base, ogel, OV10..,  seafireIIc, spitfireIIa, ufo.
 
 
</ul>
 
<br><br>
</ul></ol>
<br><br>


== Adjust the Microphone and Speaker volumes ==
== Adjust the Microphone and Speaker volumes ==
Jomo
652

edits

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

Navigation menu