GPS jammed
They keep going on what they can still trust.Each vehicle works out where it probably is, and how sure it is, and plans around that.
Software that keeps a team of drones, ground robots and boats on mission when GPS is jammed, the radio cuts out, and nobody at base can reach them.
Then someone jams GPS. The radio link gets patchy. The operator back at base loses contact. Each drone can usually keep itself in the air. What falls apart is the team: who watches which stretch, who follows what was spotted, and who fills the gap when one goes down.
This is what current conflicts look like. It is not rare any more.
It puts the whole team plan on every vehicle. No vehicle waits for base, and no vehicle is the boss. If the group gets split up, each part carries on by itself.
Every drone has an autopilot that flies it very well. It has no idea what the other drones are doing. So today the teamwork usually runs from a laptop or server at base, and when that link is jammed, every vehicle is left waiting for orders. We moved the teamwork onto the vehicles.
Each vehicle works out where it probably is, and how sure it is, and plans around that.
Vehicles pass messages along for each other and hold them until a path opens up again.
The rest of the group notices the gap and shares out the work again, without being told.
StatusAll of this has been tested in simulation. None of it has flown on a real aircraft yet.
Most systems store a position as a dot on a map and trust it. Ours stores the dot and a circle around it that says how sure the vehicle is. The worse the GPS, the bigger the circle, and the vehicle plans around the circle.
Dashed box: the spot it takes. Orange circle: how sure it is of its own position.
Armies rarely buy all their drones from one maker, and they change suppliers. So TurtleShield sits on top of the autopilot. Adding a new kind of vehicle means writing a small adapter. The part that does the thinking stays exactly the same, and customers keep the drones they already own.
The second brand, ArduPilot, has only been tested standing still in simulation so far. All our flying tests use the first, PX4.
What the operator sees. Three modes, one click each. Orders go in as plain English and nothing moves until a person holds the button down.
Built for a rugged laptop in the field, with its own maps and no internet needed. It tells vehicles where to go and what to watch. Nothing more.
Drawn for this page. The real Turtle Eyes runs on sample data today and says MOCK in the corner, same as this one.
We keep every failure, because that is where the lessons are. Everything on the left happened in simulation, with the same autopilot software that flies real aircraft.
531 passed, 141 failed, 70 were skipped. Every failure is kept on record.
Our software commanding simulated aircraft after the base station handed over, counted across recorded runs.
6 out of 6 runs passed. Closest approach 33.25 m against a 30 m limit, measured from the simulator's true positions.
Average error went from 396–750 m down to 25.5–39.0 m. Still not accurate enough to rely on.
47 of them are still open.
TurtleShield contains no weapon code. It stops at a suggestion, and a person takes it from there.
An operator can pause the mission, stop it, or call every vehicle home at any time.
A safety pilot on standby, every bench safety check done first.
Radio use brought down to budget. Real numbers replace simulated ones.
Backup behaviours switched on. Our core idea, tested for real.
Operated through Turtle Eyes, with jamming and radio trouble, and signed off by someone who watched.
Homingvector is raising a pre-seed round to take TurtleShield from simulation to a witnessed field trial. Founded by Nidhip Sharma, who wrote TurtleShield and the testing system behind it. If you fly drones, build them, or fund the people who do, write to us.