How yukitsune/cpdlcplugin works
CPDLC Plugin adds controller-to-aircraft datalink messaging to vatSys through a relay server. The main workflow runs from a controller’s plugin interface over SignalR to the server hub, which dispatches commands and queries; the server manages dialogues and relays ACARS traffic to aircraft. The plugin also supports message history, setup, status labels, and connection management. The graph reflects documented capabilities and sampled call paths; several server subsystems are represented at directory level because their implementations were not sampled.
Main entry points: Handlers Command Handlers · SignalRConnectionManager.cs SignalR Client · ClientManager.cs ACARS Client Manager · HoppieAcarsClient.cs Hoppie Client
Components 17
vatSys Plugin
- Plugin Entry
source/CPDLCPlugin/Plugin.cs - Plugin Windows
source/CPDLCPlugin/Windows - Message Views
source/CPDLCPlugin/ViewModels - SignalR Client
source/CPDLCPlugin/Server/SignalRConnectionManager.cs - Client State
source/CPDLCPlugin
Relay Server
- Controller Hub
source/CPDLCServer/Hubs/ControllerHub.cs - Command Handlers
source/CPDLCServer/Handlers - Repositories
source/CPDLCServer/Persistence - Message Monitor
source/CPDLCServer/Services/MessageMonitorService.cs
Dialogue Domain
- Dialogue State
source/CPDLCServer/Model/Dialogue.cs - Uplink Messages
source/CPDLCServer/Model/UplinkMessage.cs - Downlink Messages
source/CPDLCServer/Model/DownlinkMessage.cs
ACARS Relay
- ACARS Client Manager
source/CPDLCServer/Clients/ClientManager.cs - Hoppie Client
source/CPDLCServer/Clients/HoppieAcarsClient.cs
Other components
- Controller
- Aircraft Network
- CPDLC Server
Connections 23
- Controller → Plugin Entry: uses
README.md - Plugin Entry → Plugin Windows: opens
source/CPDLCPlugin/Plugin.cs - Plugin Windows → Message Views: uses
- Plugin Entry → SignalR Client: connects
source/CPDLCPlugin/Server/SignalRConnectionManager.cs - SignalR Client → Controller Hub: invokes
source/CPDLCPlugin/Server/SignalRConnectionManager.cs - Controller Hub → Command Handlers: dispatches
source/CPDLCServer/Hubs/ControllerHub.cs - Command Handlers → Repositories: accesses
source/CPDLCServer/Handlers/ControllerConnectedNotificationHandler.cs - Command Handlers → Dialogue State: updates
- Dialogue State → Uplink Messages: contains
source/CPDLCServer/Model/Dialogue.cs - Dialogue State → Downlink Messages: contains
source/CPDLCServer/Model/Dialogue.cs - Message Monitor → Repositories: reads
source/CPDLCServer/Services/MessageMonitorService.cs - Message Monitor → Dialogue State: checks
source/CPDLCServer/Services/MessageMonitorService.cs - Message Monitor → Command Handlers: publishes changes
- CPDLC Server → ACARS Client Manager: hosts
- ACARS Client Manager → Hoppie Client: creates
source/CPDLCServer/Clients/ClientManager.cs - ACARS Client Manager → Hoppie Client: reads downlinks
source/CPDLCServer/Clients/ClientManager.cs - Hoppie Client → Aircraft Network: sends ACARS
- Aircraft Network → Hoppie Client: returns messages
- Hoppie Client → ACARS Client Manager: streams messages
source/CPDLCServer/Clients/ClientManager.cs - Command Handlers → ACARS Client Manager: uses clients
- CPDLC Server → SignalR Client: relays CPDLC
README.md - Message Views → SignalR Client: sends requests
- SignalR Client → Client State: updates
source/CPDLCPlugin/Server/SignalRConnectionManager.cs