
Simulation
The same code runs on the robot and in simulation
We abstracted the robot's inputs and outputs so one codebase runs on hardware and in a simulator. The simulator runs as a unit test with no Android dependencies, and you can drive it with a normal game controller.
It renders in real time in a USD viewport, with CAD imported straight from STEP files. That's how drivers practise when the robot is in pieces on the bench.
Details
A second simulator runs in the browser on the Jolt physics engine and Three.js. We use it to check autonomous paths.
Both use a physics model that combines motor dynamics, mecanum kinematics and projectile motion, so we can find the robot's limits before testing on hardware.






