The failure is not always visible
Jamming announces itself. Spoofing does not — the receiver reports a confident position that is wrong, and everything downstream believes it.
EvioNav
Vision navigation for harsh, GNSS-denied environments.
Mapping and localization when ordinary cameras are not enough — leveraging a new generation of event-camera sensing that still works in darkness, glare, and motion blur.
The problem
GNSS goes. The aircraft still has to land.
Jamming and spoofing are no longer exotic. The signal can drop out, or it can quietly lie. Either way the aircraft has to know where it is and where it is going — well enough to find a known site, in darkness, backlight, cloud, motion and vibration.
The IMU only buys seconds
Inertial dead reckoning bridges short gaps. Over minutes the error compounds with nothing left to correct it, and the estimate stops being worth trusting.
The camera goes blind first
The fallback is to look at the ground. Night, low sun and hard motion are exactly when an ordinary camera stops returning an image worth matching.
Turning back has a price
Aborting is the honest answer today. It is also the mission not flown, the site not reached, the cargo still on the ground.
What EvioNav is
Position fixes that survive when the camera goes blind.
Vision navigation without GNSS already works: a frame camera matches the ground, an IMU bridges the gaps. EvioNav does not replace any of that.
It is the event-camera layer of that stack. Event pixels fire on change, not on exposure, so fixes keep arriving in the darkness, glare and motion that leave a frame camera with nothing to match.
A layer, not a replacement
It sits alongside the frame camera and the IMU. While they hold, nothing changes. When they stop, the fixes keep coming.
Availability, not extra accuracy
The claim is not a sharper position. It is a position at all, where the alternative is dead reckoning and hope.
Algorithm and hardware
The sensor and the mathematics that make sense of it, delivered together and installable on any vehicle.
The mission continues
The vehicle stays on route to a known site instead of turning back at the moment the ground stops being visible.
Why events
The event camera takes over when the ordinary one cannot see.
An ordinary camera takes pictures. An event camera only notices change — so it still works when the picture would be too dark, too bright, or too fast.
| How they differ | Vision | event camera |
|---|---|---|
| Pictures | Vision A full photo, on a timer | event camera Only when something moves or changes |
| Fast motion | Vision Turns into a smear | event camera Stays sharp |
| Light | Vision Cannot show sun and shadow at once | event camera Sees both sun and shadow |
| Energy | Vision The whole picture, all the time | event camera Rests when nothing happens |
| Update rate | Vision 30 Hz Fixed frame rate | event camera 10,000 Hz Microsecond timing on every change |
| Dynamic range | Vision ~60 dB Blown highlights or crushed shadows | event camera 120 dB Sun and shadow in the same scene |
| Latency | Vision ~33 ms Waits for the full frame | event camera <1 ms Timestamp on every event |
| Low light | Vision Longer exposure, then noise | event camera Edges still visible in moonlight |
| Glare | Vision Bloom hides the ground | event camera Ground stays visible beside bright sky |
| Shutter | Vision Rolling readout warps the image | event camera Each pixel independent, no sweep |
Team
Built across the whole stack.
Two co-founders. A computer-vision researcher and an aerospace engineer. One writes the event-camera mathematics. The other has shipped flight software and flown the machines.
Dr. Snehal Bhayani
Co-founder
Chief Computer Vision Officer
PhD Computer Vision
University of Oulu
Andreas Myleus
Co-founder
Chief Aerospace Officer
MSc Aerospace Engineering
KTH Royal Institute of Technology
Commercial Helicopter Pilot
Contact
Let us show you the way.
Part of the Slam Dunk Labs community.
Get in touch