A supervisor's console simulation for a team of autonomous drones. One operator directs up to 10 self-flying aircraft at once, assigning search areas, managing the links between them and stepping in when something goes wrong.
Runs in the browser on a tablet, laptop or desktop.
Open Consol on a bigger screen. It needs more room than a phone has; a tablet, laptop or desktop works.
Training
The aircraft fly their own routes and search the sectors they are given. Each one returns to launch (RTL) by itself when its battery hits bingo or its link stays down past the failsafe timeout. The operator decides where each aircraft goes and keeps the links up. When a failsafe is about to pull an aircraft out of the plan, you step in or hand its work to another one.
The debrief reports verified coverage, lost-link reaction time and confirmed finds. Every mission and drill is kept as a replay you can step through afterwards.
Operator tasks
Draw a sector or open one from a tasking. Give it to one aircraft or split it across several. Verified coverage is tracked against the deadline.
Each aircraft shows live, stale or lost. Stale starts 2.5 s after the last packet, and the console declares the link lost at 20 s. A lost aircraft stays on the map at its last known position, inside an r95 ring that grows the longer it is gone.
Once a link is declared lost, the aircraft has a 40 s grace period before RTL fires. Restore the link or relay it through another aircraft. If you let it come home, its sector needs someone else.
At bingo, 22% on most of the fleet, an aircraft returns to the pad for a fresh pack. Stagger the swaps so no sector or watch goes empty.
Hits arrive as a possible person, a heat source or a possible vehicle. Review each one and confirm or dismiss it.
Run a spare through preflight and fix what it finds. Then commission it and give it a sector.
About
A product of Workshop Labs LLC. Send questions and feedback to [email protected].