Menu ▾ ▴

#5 Support FGCom-mumble

open
nobody
FGCom (2) Mumble (1) Radio (2)
2022-01-17
2020-07-18
Benedikt Hallinger
No

Hello, i just wanted to bring FGCom-mumble to your attention.

Work on FGCom-mumble did very good progress and we have a working version already.
While several radios should work out of the box with the "standalone" option togheter with separate mumble instances, it would be nice if OpenRadard would support FGCom-mumble a little better.

There is also a RDF feature in the forge (see rdfSupport branch, which will be merged soon) .

ATC-Pie already has support in a development branch.

Basicly, you just need to send UDP string packets to the FGCom port, containing the already known fields. Details are documented in the plugin specification documentation readme: plugin.spec.md (github.com). This way, users just need a single mumble instance to have several OpenRadar radios.

Note, for testing you need a compiled version of mumble 1.4.0 with the plugin framework, as it's not yet included in mumble releases.

Discussion

  • Benedikt Hallinger

    Benedikt Hallinger - 2020-10-15

    With the latest commits, the plugin supports different "identities" which are derived form the UDP client port.

    Trough this, OpenRadar may support several radios out of the box, when supplying the plugins port as "FgCom ports" in the settings multiple times.

    To implement it, each Radio string UDP packet should have its own (stable) source client UDP port. This will yield different "identites" mapped in the FGCom-mumble plugin, and such no interference/overwriting of the COMs to each other.

    Alternatively, it could be implemented (probably cleaner) if:

    • users give the same UDP target port for each radio instance
    • OpenRadar detects that it's the same target port and constructs the message accordingly.
      This approach would also be compatible to the legacy FGCom protocol.
     

    Last edit: Benedikt Hallinger 2020-10-15

Log in to post a comment.

MongoDB Logo MongoDB