CPDLC: Difference between revisions

Jump to navigation Jump to search
244 bytes added ,  18 October 2020
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
{{WIP}}
{{WIP}}


{{Hackathon Proposal}}
'''Controller-pilot data link communication''' (CPDLC) is a direct connection between ATC and aircraft through which controllers can communicate with pilots based on text, thereby relieving radio traffic. Its use is increasing everywhere in real life, while no aircraft is equipped in FlightGear yet.
'''Controller-pilot data link communication''' (CPDLC) is a direct connection between ATC and aircraft through which controllers can communicate with pilots based on text, thereby relieving radio traffic. Its use is increasing everywhere in real life, while no aircraft is equipped in FlightGear yet.


Line 11: Line 10:
* work is currently in progress on a cockpit CPDLC panel;
* work is currently in progress on a cockpit CPDLC panel;
* a CPDLC middleware is under dev, required at this point because FG models cannot open their own TCP connections.
* a CPDLC middleware is under dev, required at this point because FG models cannot open their own TCP connections.
At the moment we would be interested in users to take up this project in the Hackathon, any assistance whatsoever would be welcome.


== Issues/ideas ==
== Issues/ideas ==
The following could be done in the hackathon:
The following could be done in the hackathon:
* write the Nasal to exchange the right data with the outside system;
* write the Nasal to exchange the right data with the outside system;
* write the IRC hook to connect FlightGear to IRC (not least a generic capability, that other applications may use)
* involving core dev's at least for the design choice, a way to get rid of the middleware eventually, e.g. allow Nasal connections to FG-approved servers (like irc.flightgear.org) or integrate specific accesses in the C++ code base (sort of the same history as FGCom, going from standalone executables to an option in the FG menu)?
* involving core dev's at least for the design choice, a way to get rid of the middleware eventually, e.g. allow Nasal connections to FG-approved servers (like irc.flightgear.org) or integrate specific accesses in the C++ code base (sort of the same history as FGCom, going from standalone executables to an option in the FG menu)?
* can someone create a sketch of a block diagram of the elements that need to communicate and the connections between them? -- p callahan
* can someone create a sketch of a block diagram of the elements that need to communicate and the connections between them? -- p callahan Done -- J Redpath


[[File:CPDLC Block.png|thumb|Block diagram for CPDLC subsystem]]
[[File:CPDLC Block.png|thumb|Block diagram for CPDLC subsystem]]
842

edits

Navigation menu