265
edits
CPDLC: Difference between revisions
Post-Hackathon PoV
No edit summary |
Mickybadia (talk | contribs) (Post-Hackathon PoV) |
||
| Line 1: | Line 1: | ||
{{WIP}} | {{WIP}} | ||
'''Controller-pilot data link communication''' (CPDLC) is a direct connection between ATC and aircraft through which controllers can communicate | '''Controller-pilot data link communication''' (CPDLC) is a direct connection between ATC and aircraft through which pilots and controllers can communicate based on text, thereby relieving radio traffic. | ||
Its use is increasing everywhere in real life, | Its use is increasing everywhere in real life, and an extension to FlightGear is currently under development to support it in the multi-player environment. | ||
== | == Status in FlightGear multi-player == | ||
Recent efforts have already taken place towards making it possible: | Recent efforts have already taken place towards making it possible: | ||
* [[ | * the [[Virtual FSWeekend Hackathon 2020]] attracted a team to work on the CPDLC proposal, and significant progress was made (see [[#Hackathon 2020 results]]); | ||
* work is currently in progress on a cockpit CPDLC panel; | * work is currently in progress on a cockpit CPDLC panel; | ||
* | * [[ATC-pie]], an ATC client able to join FG networks, already integrates a working service for when the first ACFT are equipped (use of a demo dialog in the mean time). | ||
== Hackathon 2020 results == | |||
We have a proof of concept up and running :) | |||
[[File:Cpdlc-demo.png|thumb|CPDLC demo dialg]] | |||
* Basic IRC protocol has been implemented in C++ | |||
* Some dummy CPDLC messages have been successfully passed around | |||
* CPDLC connect/disconnect works, handover to othe ATS unit works | |||
* Inbound CPDLC messages are processed and queued for later display in the cockpit | |||
* A simple PUI dialog interface is available in FGAddon | |||
== Hackathon run-up (historical) == | |||
The following sections are kept here for the record as they are still recent. They contain speculation and technical aspects discussed before the Hackathon event, and wrong information. | |||
== 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; | ||
| Line 64: | Line 75: | ||
});</tt> | });</tt> | ||
== Available ATC-pie IRC scheme == | === Available ATC-pie IRC scheme === | ||
When connected to an IRC server, e.g. <code>irc.flightgear.org</code>, ATC-pie features an integrated text chat system for ATCs to coordinate off the (public) FG text chat. The choice of IRC and plain text lines was in part motivated by the possibility for users of other clients (e.g. OpenRadar) still to take part via their own IRC client. | When connected to an IRC server, e.g. <code>irc.flightgear.org</code>, ATC-pie features an integrated text chat system for ATCs to coordinate off the (public) FG text chat. The choice of IRC and plain text lines was in part motivated by the possibility for users of other clients (e.g. OpenRadar) still to take part via their own IRC client. | ||
| Line 90: | Line 101: | ||
* <code>REJECT <optional_reason></code> | * <code>REJECT <optional_reason></code> | ||
* <code>TEXT <free_text></code> | * <code>TEXT <free_text></code> | ||
[[Category:Hackathon 2020 Ideas]] | [[Category:Hackathon 2020 Ideas]] | ||