These docs are public and open source.Edit on GitHub
TROUBLESHOOTING / FAQ
FREQUENTLY ASKED QUESTIONS.
If a question shows up in support more than twice, it lands here with a canonical answer. They're grouped into four sections: kits, software, classroom, and support. Each answer links out to the page that covers it in full detail.
0 answersUpdated continuously
//KITS & HARDWARE
Why doesn't the kit include a battery?
Due to various international shipping regulations, Neobotics does not directly sell LiPo batteries. The Hardware power page has the specifications you need to pick a that fits.
Can I run the car outside?
The NeoRacer is designed for indoor use on smooth surfaces. Outdoor running on pavement is fine for short tests, but the struggles in direct sun and the wheels were tuned for smooth gym floors.
What's the top speed?
The firmware caps the drivetrain at 6 m/s, and the driver ships with the full range unlocked. The caps are real parameters you can read and lower to derate the car for a classroom; the Motor trim page shows where they live.
//SOFTWARE
Does it support ROS 1?
No. The on-car stack is ROS 2 Humble. Bridging from ROS 1 is possible through the ros1_bridge tool, but we don't ship or support that path.
Can I develop on Windows?
Yes, but indirectly. You write Python on Windows, push to the car over SSH, and run on the car's Ubuntu. The NeoRacer Playground runs in any modern browser, so you can build and iterate fully on Windows before touching the car.
How do I update the on-car software?
Pull the driver repository and re-run the setup script, which is safe to run repeatedly:
cd ~/ros2_ws/src/neoracer_ros2_driver && git pull && bash scripts/setup_all.sh, then racecar service restart. The car needs internet for the pull, the same way as during Get on the car.Will my F1TENTH code run on NeoRacer?
Yes. The ROS 2 topic names and message types match the F1TENTH reference build, so your existing nodes run on a NeoRacer unchanged.
//CLASSROOM
How do multiple cars share one classroom?
The clean classroom setup is one cudy router per car: each car plugs into its own router (Wi-Fi
neoracer-[Car ID], password neobotics) and each student reaches their car at 192.168.10.100 on their own network, so there is no shared access point to overload. A car can also broadcast its own Wi-Fi (neoracer-1, car at 10.42.0.1) when a router isn't around.//SUPPORT
Where do I file a bug?
Email support@neobotics.org with the car's serial number and, if relevant, the output of
journalctl -u neoracer-jupyter -n 60. Most cases get diagnosed inside an hour.Where's the warranty page?
Under Legal → Warranty. The short version: one year on parts that fail under normal classroom use.