Neobotics Foundation Inc.
Wi-Fi can't connectNEORACER DOCS
NEORACER DOCS
These docs are public and open source.Edit on GitHub
TROUBLESHOOTING / NETWORK

THE CAR'S WI-FI.

The car is its own access point. It broadcasts a network named neoracer-[Car ID] that you join from your laptop, then reach the car at racecar@neoracer. When that fails it's almost always one of three things, and there's a wired fallback (ethernet) that works regardless. See networking for the full access walkthrough.

~0 minutesCar is its own APEthernet fallback
// YOU SEE
The neoracer-[Car ID] network never shows up in your Wi-Fi list, joining it fails, or ssh racecar@neoracer hangs once you're on it.
// WHAT SHOULD HAPPEN
You join neoracer-[Car ID] with password neobotics, then connects within a second and drops you at the racecar@neoracer:~$ prompt. The car stays quiet otherwise, since there's no inbound port mapped by default.
01 / IS IT JOINING OR ROUTING?

JOINING VS ROUTING.

Two kinds of failure look alike from the user's side. The split is whether your laptop can join the car's Wi-Fi at all or whether, once joined, it can reach the static IP (routing).

bash
# Test 1: is the car broadcasting and did you join it?
# Look for "neoracer-[Car ID]" in your Wi-Fi list (Car 1 = neoracer-1)
# and join it with password "neobotics".

# Test 2: once joined, can you reach the car's static IP?
# Cudy path: the car is 192.168.10.100. Access point: it is 10.42.0.1.
ping 192.168.10.100        # or 10.42.0.1 on the access point

# Reachable IP == you're in; ssh racecar@<that address>.
# No IP after joining == wrong Car ID or the car hasn't finished booting.
02 / WHAT ACTUALLY BREAKS

THE FAILURE MODES.

01

Can't see or join the Wi-Fi

The neoracer-[Car ID] network never appears.
The car broadcasts its own access point only once it's powered and booted, which takes a minute or so. If neoracer-[Car ID] still isn't in your Wi-Fi list after that, confirm the car is on, then re-scan. Join it with password neobotics.
ssid: neoracer-1 · pw: neobotics
02

Joined but can't reach the IP

You're on the network but SSH hangs.
The car's address depends on the network you joined: on the cudy router it is 192.168.10.100, on its own access point it is 10.42.0.1. If a ping to the right one times out, the car may still be finishing its boot. Wait a minute and re-ping.
ssh racecar@192.168.10.100
03

Wrong network

You joined a different Wi-Fi than the car's.
The address only answers on its own network: joining the cudy Wi-Fi and pinging 10.42.0.1 (or the reverse) times out every time. Match the pair: neoracer-[ID] → 192.168.10.100, neoracer-1 → 10.42.0.1.
network → address, matched
03 / FALLBACK

THE ETHERNET FALLBACK.

The Jetson has a real ethernet port on the rear of the chassis. Running a cable from there to your laptop or a router gives you a reliable path that doesn't care about the Wi-Fi radio or which access point the car is broadcasting.

bash
# Direct laptop-to-car cable, no router in the middle.
# The Jetson auto-assigns a link-local IPv4 on eth0 if it can't find DHCP.
sudo nmap -sn 169.254.0.0/16          # find the car's link-local IP
ssh racecar@<link-local-ip>           # then SSH straight to it