These docs are public and open source.Edit on GitHub
NEORACER DOCS.
The documentation for the NeoRacer V1. Getting Started takes a new car from the box to its first program; the rest is the reference you come back to: hardware, software, calibration, troubleshooting, and the full Python and ROS 2 APIs.
CHOOSE A SECTION.
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 carries the messages between them.
- 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.
FIG. A / DATA FLOW, HARDWARE TO SOFTWARE TO HARDWARE
● each topic streams at its own ratehover a lane for its message typeROS 2 keeps the different rates in sync
teleop.launch.py starts once you have built neoracer_ros2_driver.