Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make FGFS read and use the RDF data #22

Closed
hbeni opened this issue Jul 9, 2020 · 3 comments
Closed

Make FGFS read and use the RDF data #22

hbeni opened this issue Jul 9, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request low prio Low priority Protocol Protocol stuff Sim clients Affecting compatibility to Simulator/ATC clients
Milestone

Comments

@hbeni
Copy link
Owner

hbeni commented Jul 9, 2020

Make Flightgear able to parse the information and , if tuned to the frequency, make ADF needle move accordingly.
Note: this may be impossible if the property is tied to C++ space (which i assume); this then would need changes in the fgfs core. A Proposal could be another property that is investigated from the RDF/ADF C++ code and also taken into account.

We should look into this once mumble 1.4 is out and we have some pilot feedback on the overall system.

(Followup on the RDF feature #8)

@hbeni hbeni added enhancement New feature or request low prio Low priority Protocol Protocol stuff labels Jul 9, 2020
@hbeni hbeni added this to the Soon™ (=Future) milestone Jul 9, 2020
@hbeni hbeni added the Sim clients Affecting compatibility to Simulator/ATC clients label Aug 20, 2020
@hbeni
Copy link
Owner Author

hbeni commented Apr 22, 2021

The prop in question is instrumentation/adf[0]/indicated-bearing-deg.

The idea might be to send the ADF in the protocol file as separate radio, make it receiving, but do not show it on the statuspage in order to not confuse people.
A generic and probably nice solution would be another boolean flag sync=true in the radio, which when set to false will prevent synchronization to remote clients.

[EDIT] just tested it with the C172p and the C182s: The property is writable and keeps the value.
That means we can push back the RDF value into the FGFS protocol and implement a simple nasal script that parses this and tries to push the needle into the proper direction when an RDF signal is received.

@hbeni
Copy link
Owner Author

hbeni commented Apr 22, 2021

Digged into this a little more.
It seems FGFS is currently not capable of assign the sending client port as listen port dynamically.

Asked on the forums: https://forum.flightgear.org/viewtopic.php?f=36&t=39073
If all fails, we might probably assign a fixed port and overwrite the identites UDP client port setting in the plugin using the UDP_TGT_PORT=12345 feature.

@hbeni hbeni self-assigned this Apr 23, 2021
@hbeni hbeni closed this as completed in df0396f Apr 23, 2021
@hbeni
Copy link
Owner Author

hbeni commented Apr 23, 2021

Implemented and tested with the C182s and C172p :)

Seeing the needle move when some fgcom-mumble client sends on the ADF frequency move is rather cool :D 😎

[edit] Btw, the audio that is transmitted on the net (ident morse code, or radio program) is bound to the ident-audible property of the ADF. It ident is on, audio can be heared. Ident is supposed to be set from some audio panel in the aircraft.
I used default properties, so this should work with any aircraft - it certainly does with the two tested ones.

Funny real life example on tuning to an ordinary AM station: https://www.youtube.com/watch?v=HKXZZXoLMO8

@hbeni hbeni modified the milestones: Soon™ (=Future), 1.0 Apr 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low prio Low priority Protocol Protocol stuff Sim clients Affecting compatibility to Simulator/ATC clients
Projects
None yet
Development

No branches or pull requests

1 participant