FGCOM Testing: Difference between revisions

Jump to navigation Jump to search

FGCOM Testing (view source)

Revision as of 10:47, 31 May 2010

27 bytes removed ,  31 May 2010
Typesetted section to be consistent. Made use of indentation rather than bullet point lists.
(Reformmated page for redability. Please do not use the <small> tag unless absolutely necessary and even then think about it.)
(Typesetted section to be consistent. Made use of indentation rather than bullet point lists.)
Line 153: Line 153:
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>
<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>click in the FGFS menu-bar onto "Equipment" --> "Radio Settings"
<li>click in the FGFS menu-bar onto "Equipment" --> "Radio Settings"
*into the field "COM1" enter the frequency "910.00" then click "Apply" (and "OK" if you want to close the Pop-up.)
*into the field "COM1" enter the frequency "910.00" then click "Apply" (and "OK" if you want to close the Pop-up.)
*'''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)!!!'''
* '''Ensure the FGFS is the active window''': if 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>
<li>if the FGCom Command-window initiates, but does not respond to any COMM-Frequency setting:
<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.
: This indicates 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
:: 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)
:: 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:
: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
::add the option “-p5004” to the FGCom start-command
**also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004
::also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004 '''or''' add the option "--generic=socket,out,10,localhost,5004,udp,fgcom" to your FGFS start-command.
***or add the option "--generic=socket,out,10,localhost,5004,udp,fgcom" to your FGFS start-command.
::and you may have to tell your Firewall to allow port UDP 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 !!!
*anyhow make sure all these 3 places contain the same Port-number !!!


<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:
<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.
"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:
::'''if you heard''' that echo:
**keeping the PTT pressed for about 3 sec and watch for a possible start of "funny noises".
::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]]
:::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.
:::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
::'''if you did not hear''' the echoed return
<ul><li>Test your PTT: Watch the FGCOM messages in the FGCOM-Window:
:::Test your PTT: Watch the FGCOM messages in the FGCOM-Window:
<ul><li>When pushing the PTT they must switch between
:::When pushing the PTT they should switch between ''[SPEAK] unmute mic'' followed by ''[LISTEN] mute mic''
</ul></ul></ul>
:::If they did not switch you probably use an airplane model that has reassigned the Space-bar to another function:
    [SPEAK] unmute mic
:: Otherwise 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. There could be others.
    [LISTEN] mute mic
***If they did not switch you probably use an airplane model that has reassigned the Space-bar to another function:
**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.


<br><br>
<br><br>
Gorilla
128

edits

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

Navigation menu