VEL · BY SKANDA · EARLY ACCESS
Vel knows what your hardware should read.
Point it at your schematic, CAD, simulation results and firmware. It works out what every rail, temperature and deflection should be, and the conditions each holds under. Then it checks the real hardware with your supply, meter, thermal camera and gauges.
Below is an example run: a startup bringing up a drone motor and the board that drives it.
Example run · a drone motor and its controller board
- 01
Reads the design
Schematic, CAD, FEA and firmware become expected values: every rail, bolt torque, thrust and how far the motor arm may flex.
- 02
Stops a mistake
Someone asks for 12 V on the 3.3 V rail. Vel refuses: the rail is capped at 3.6 V, and 12 V would destroy U1.
- 03
Stops a mechanical one
The torque wrench is set to 3.0 N·m for the motor mount. Vel stops it: those threads are rated 1.2 N·m. All four bolts go in at spec.
- 04
Checks the first rail
3V3 at TP1 reads 3.30 V, inside its band.
- 05
Catches the wrong number
At TP2, 1V8 reads 3.18 V. It should read 1.77 to 1.83 V.
- 06
Sees the heat
The thermal camera shows U1, the MCU, running hot. Vel starts working out why.
- 07
Rules out the easy causes
1V8 sits 0.12 V below 3V3, so it isn't a short. The enable pin reads 3.30 V, so it isn't floating.
- 08
Finds the cause
U3 is marked 33A: the 3.3 V part. The BOM calls for 18A, the 1.8 V one.
- 09
Checks the fix
With U3 swapped, 1V8 reads 1.80 V.
- 10
Runs clean
The motor spins up. Thrust, motor temperature and arm flex all pass.
How it works: one loop, safer every run.
- 01
Reads the design
Schematic, CAD, simulation and firmware become expected values and safe limits. Every number is calculated from your files, never made up by a language model.
- 02
Asks first
Nothing runs until you say yes, and never past a limit. One trip turns every output off.
- 03
Measures
Every reading, from every instrument and sensor, is checked against what it should be.
- 04
Finds the cause
A reading that is off gets a cause, and the evidence for it.
- 05
Remembers
A confirmed cause becomes a check on every run after that.
Every run makes the next one safer.
Bring Vel to your next bring-up.
We're letting hardware teams in a few at a time. We'll email you when your invite is ready.