Saga wrote in Tue Jun 30, 2015 6:39 pm:I think fgcom standalone mute the microphone at startup and should be demuted by using the FG protocol to control fgcom. See
here. Is that implemented in OpenRadar and ATC-pie?
Yes, both. See below.
Saga wrote in Tue Jun 30, 2015 6:39 pm:And I think with sockets you can change the frequency without restarting the client, My opinion is that this is how fgfs deal with it.
Yes, that was my point when I was referring to "control packets". I am sorry I thought you knew all about it.
ATC clients send UDP packets to running FGCom clients, most of the time children processes. Included in those packets are two specs relevant to our thread:
- PTT=0 to listen (mic muted); PTT=1 to speak (headphones/speaker deafened); this answers one of your concerns
- COM1_FRQ=xxx.xxx specifying the tuned frequency; I thought this made any --frequency option useless (thus my naming them "dummy start" freqs)
daweed wrote in Tue Jun 30, 2015 7:18 pm:But maybe we could find a way to force OR / ATC-pie to start process with this parameter.
That is *exactly* the test I have made the other day and was reporting on:
- somebody connected at EHAM with latest ATC-pie and integrated FGCom monitoring 119.225
- me connecting to same freq, same place, same version and all works though 100% CPU load (as Saga reports in his EDIT as well)
Then, I changed the code inside ATC-pie to add a --frequency=xxx option to the FGCom client start command, trying three different values for xxx, including the tested frequency. As I said, the load disappeared each time but I could not be heard any longer.
Apparently adding a --frequency option changes the behaviour in two surprising ways, which constitute my two main questions in view of finding a solution:
1.
not heard any moreWhy is that? Does the --frequency value block any subsequent COM1_FRQ changes? Note that even with --frequency=119.225 (launching FGCom) and COM1_FRQ=119.225 (tuned within the app), i.e. same frequency, I was not heard at the other end.
2.
no more loadWhy is that? Is the COM1_FRQ machanism that different to that of the command-line?