Event-based vision
Cameras that react to change, so fast movement stays sharp. For landing, avoiding collisions and fast inspection.
Event-based visionHow we work
Every project starts with the problem.
We take the time to understand what you need, write it down as a specification you sign off, and build to it. Below are the six steps, what happens in each, and what you get.
01 / The six steps
From your problem to a product.
- 01
Listen
We start with a conversation, and where it helps, a visit to where the problem happens. We ask who has the problem, when it happens, what it costs them, and what “solved” would look like.
- You get
- A one-page problem statement.
- You decide
- Is this the right problem to solve?
- 02
Shape
We look at the ways the problem could be solved, including ways that need no new hardware. We check each option against a target cost for the parts, the numbers you expect to make, the rules the product must meet (certification, for example) and what is already on the market.
- You get
- Two or three options with their trade-offs, and the one we recommend.
- You decide
- Which way to go, or whether to stop here.
- 03
Specify
We write the specification: what the product must do, how well, and where it has to work, whether that means heat, rain, vibration or a moving vehicle. Each line traces back to the problem statement.
- You get
- A specification you sign off. It is the yardstick for everything after.
- You decide
- Sign off the specification.
- 04
Design
We design the electronics, the firmware (the software inside the device) and the enclosure to the specification. The design is reviewed at fixed points, and every circuit board goes through six checks before it is ordered.
- You get
- The design files and a record of each review.
- You decide
- Approve the design before boards are made.
- 05
Prove
Where it is cheaper to test in software, we simulate first. Then we test the real hardware against every line of the specification, on our bench and on your machine.
- You get
- A test report, with each result next to the line it checks.
- You decide
- Accept the prototype.
- 06
Deliver
Prototypes, pilot units (a small first batch), and everything a factory needs to make the product in volume.
- You get
- Production files, the specification, test reports and documents for your project.
- You decide
- When to build in volume, and with which manufacturer.
02 / Why we start with the problem
The problem writes the spec.
Our battery boards show how this works. The problem we kept hearing from drone teams was easy to state: a battery fails when one of its cells is weak, and the drone finds out too late.
A common answer is a protection board that cuts the power when a cell runs low. On a drone in the air, that turns a weak cell into a crash. So our specification says: report every cell to the flight controller, and never cut the power. The drone decides when to land.
That one line came straight from the problem, and it shaped the whole board.
See the battery boardsSpecificationExample
Problem
“A battery fails when one cell is weak, and the drone finds out too late.”
- 01Report every cell to the flight controllerChecked by: Compare each reported cell with a meter
- 02Never cut the power in flightChecked by: No switch in the battery’s power path, checked at design review
- 03Wake up when a dock powers itChecked by: Power the dock’s connection and watch the board start
03 / What thorough looks like
Small checks, made early.
Six checks before a board is ordered
Between a finished drawing and an order, every board goes through six checks:
- Every connection is right.
- Every part’s copper pattern matches the maker’s drawing.
- The board maker’s limits and safe gaps are met.
- Parts sit where heat and noise won’t bother them.
- Every connection is drawn in copper.
- The factory files agree with each other.
On one of our battery boards, check 2 found a power terminal sold online as 135 A. The maker’s own drawing for the same part said 80 A, and the board carries 100 A.
135A
online listing
80A
maker’s drawing
100A
what the board carries
The same check found two output pins swapped on a small power converter. Both took minutes to fix on screen. On a finished board, one would have run hot and the other would have been wired backwards.
We simulate before we spend
Before buying any parts for our landing system, we built it in software: the camera, the marker, the lighting and the drone’s movement. The simulation found three design faults that would have cost weeks to find on real hardware.
The landing project
0 ms
1.8 ms
3.6 ms
5.3 ms
7.1 ms
Tested line by line
Every line of the specification has a test written next to it, and the test report follows the same order. You can see at a glance what was asked for and what the product does.
04 / Ways to work with us
Four ways to start.
Every piece of work starts with a written scope.
01
Specification SprintNew
The first three steps: Listen, Shape and Specify, as a short piece of work with a fixed scope. It ends with a specification you own and can take to any team.
02
Research Engagement
For an open question, such as how to keep a drone connected over long distances. Runs for several months, with written findings every month.
03
Integration Sprint
A fixed window to get hardware working on your machine, with clear milestones. On site when the work needs it.
04
Custom Build
We design and build hardware to your specification: circuit boards, battery systems, radio modules. Often it starts from one of our products, changed for your system.
05 / What we design
Four kinds of problem we know well.
Battery and power
Battery boards that watch every cell and report to the machine’s controller. For drones, robots, light vehicles and energy storage.
ProductsLong-range links
Radio links that keep a drone connected far from its pilot, designed around the aircraft they fly on.
MODL-CoreEmbedded hardware
Circuit boards built to survive vibration, heat and weather, for machines where a fault is expensive.
06 / Our own ideas
Ideas we are developing ourselves.
PATENT FILED
StrobeTag
A landing marker that lights up for an event camera, so a drone can land quickly and precisely.
See the projectFLYING TODAY
OpenWing HAT
A long-range radio add-on for the Raspberry Pi, a small computer. It flies today as the backup link on a client’s drone.
Contact
Start with the problem.
Answer five short questions. We turn your answers into an email or WhatsApp message, ready for you to send. Nothing you type is stored on this site.