-
Notifications
You must be signed in to change notification settings - Fork 0
Quickstart
Assumes Installation, the Cloud Run agents and the X-Plane plugin are done. Prefer watching first? Full demo on YouTube.
docker compose upOpen the Controller HMI at http://localhost:8005, then start X-Plane 12 with the plugin
loaded (backend first — the plugin needs the Orchestrator on host port 8007).
Pick a departure flight strip in the HMI, key the mic, and speak a Delivery instruction —
the aircraft starts in the DEL phase. Then walk it through the lifecycle:
Controller: "Iberia 5471, taxi to holding point runway 25 via Charlie."
-> ASR (Whisper ATC) transcribes audio + corrects callsign -> IBE5471
-> Orchestrator routes to GND agent (current phase: GND)
-> GND agent (Gemini) validates route in taxi graph, drafts readback
-> X-Plane plugin drives aircraft along taxiway C, holds short of 25
Pilot (TTS): "Taxi to holding point runway 25 via Charlie, Iberia 5471."
Typical sequence: IFR clearance (DEL) → pushback/taxi (GND) → line-up and takeoff (TWR). The Orchestrator advances each aircraft's phase automatically as clearances are acknowledged.
- Flight strips — phase and clearance state per aircraft.
- Ground radar — aircraft moving along the taxi routes you cleared.
- Chat/transcript — your transmission, the corrected callsign, and the pilot readback.
- X-Plane — the aircraft physically taxiing; the readback spoken via TTS.
- Arrivals — the Arrival Simulator keeps AI arrivals coming down the ILS for you to sequence.
End the session and generate the debrief (HMI → debrief): the Orchestrator summarizes your session from the recorded transmissions and movement events.
No pilot reply → agent URLs (Troubleshooting). No aircraft motion → plugin/backend order (Troubleshooting).
Getting Started
Help
Modules
- System-Overview
- Agents
- Shared
- X-Plane
- Service-Arrival-Simulator
- Service-Asr
- Service-Controller-Hmi
- Service-Flight-Plan
- Service-Orchestrator
- Service-Weather
Internals