NEORACER DOCS.
Everything you need to take a NeoRacer from a sealed box to a full autonomous lap, and everything you need to teach the next thirty students how to do the same.
THE DATA FLOW
Every NeoRacer behaviour, from a teleop drive to a full racing stack, is the same shape: sensors publish, your code subscribes, your code publishes, actuators subscribe. ROS 2 just provides the cables.
- Each part of the car runs as a separate program, ROS 2 calls these nodes.
- Nodes don't call each other directly.
- They publish on named channels (topics). Anyone listening picks them up.
- NeoRacer's teleop starts four nodes.
create here?
neoracer-teleop. Your code lives in the red panel.BROWSE BY TOPIC.
BOX TO FIRST LAP.
The Getting Started spine is five pages, each under ten minutes. The whole thing fits inside a single classroom period.
WHAT YOU'LL BUILD.
These four are the foundation. The rest of autonomous racing, SLAM, MPC, RL, just builds on them.
Wall follow
Lane keeping
Gap follower
End-to-end RL
What everyone else is reading.
Recently shipped.
v1.0, First shipping customer release.
The full Getting Started spine, the sensor reference, and the motor and servo calibration cookbook are live.
Read the changelog →NeoRacer Playground is the in-browser simulator. Every line of code you write there runs unchanged on the physical car.
