These docs are public and open source.Edit on GitHub

SOFTWARE / NETWORKING

THE CAR'S NETWORK.

There are two ways to reach the car, and both end with it at a fixed address. The cudy router travels with the car and can share internet, which suits a classroom or several cars at once. The car's own access point needs no extra hardware at all. Pick either; the rest of this page works the same on both.

cudy · 192.168.10.100access point · 10.42.0.1user racecar

01 / TWO WAYS ON

PICK YOUR NETWORK.

With the cudy router, the car plugs into the router and both join its Wi-Fi; the router can also uplink to the internet. With the access point, the Jetson broadcasts its own Wi-Fi and your laptop joins the car directly.

	Cudy router	Access point
Wi-Fi to join	neoracer-[ID] (+ -5G twin)	neoracer-1
Wi-Fi password	neobotics	neobotics
The car	192.168.10.100	10.42.0.1
Gateway	192.168.10.1 (router)	10.42.0.1 (the car)
Internet	via the router uplink	none
Extra hardware	the included cudy router	none

02 / GET A SESSION

THREE WAYS IN.

//SSH

A terminal is all you need for most work. in as racecar at the address for your network:

bash
ssh racecar@192.168.10.100     # cudy router
ssh racecar@10.42.0.1          # access point
# password: neobotics

//Remote desktop (RustDesk)

For the full Jetson desktop, open on your laptop and connect by the car's IP address (direct IP; the password is neobotics).

//Wired USB fallback

With no Wi-Fi at all, a USB-A to USB-C cable from your PC to the Jetson's Type-C port brings up a point-to-point link, and the Jetson answers at a fixed address:

bash
ssh racecar@192.168.55.1       # over the USB cable
# password: neobotics

03 / NO SSH REQUIRED

IN A BROWSER.

The car brings up its whole stack at boot: the driver, the watchdog, the health dashboard, and JupyterLab all run as services. Two of them are web pages, so a browser on the car's network is enough:

bash
http://192.168.10.100:8080     # health dashboard   (10.42.0.1 on the AP)
http://192.168.10.100:8888     # JupyterLab        (10.42.0.1 on the AP)

04 / ROS 2 ACROSS THE LINK

ROS 2 DISCOVERY.

Once your laptop is on the car's network, you share its (192.168.10.x on the cudy, 10.42.0.x on the access point), and ROS 2 uses to find the car's nodes automatically. You can list topics and run nodes on the laptop that talk to /scan, /drive, and the rest.

bash
# From your laptop, on the car's network.
ros2 topic list                  # /scan /camera /imu /odom /battery /drive ...
ros2 topic echo /scan --once     # a single scan, straight off the car

01

Same subnet

You get this by joining the car's Wi-Fi.

DDS discovery reaches the car nodes when both sides are on the same subnet. Joining the car's network, cudy or access point, puts you there.

ros2 topic list

02

Same ROS_DOMAIN_ID

Matched on both ends.

ROS 2 only joins peers that share the same ROS_DOMAIN_ID. Set the same value on the laptop and the car, and the two halves of the graph see each other.

export ROS_DOMAIN_ID=...

05 / THE CUDY ROUTER, IF YOU NEED IT

FIND IT, RENAME IT.

On the cudy path, you rarely touch the router itself. You open it to find the car's address if it isn't at the default, or to rename the Wi-Fi. The admin page is at http://192.168.10.1, and the admin password is neobotics.

01

Find the car's IP

System Status → Devices.

The DHCP pool hands out addresses from 192.168.10.101, and the car holds the static 192.168.10.100 once the driver setup has run. If a device picked up a different address, the Devices list shows the wired client and its IP.

02

Rename the Wi-Fi

Quick Setup → Wireless.

Change the 2.4G and 5G SSID and password in the setup wizard's Wireless step. After you Save & Apply, re-join the renamed network from your laptop.

06 / RACECAR SETUP NETWORKING

THE SETUP COMMAND.

racecar setup networking configures the car's side of everything on this page: the access point, the fixed Ethernet address, and the lidar link. Run with no flags it applies the defaults. Flags change a setting, and every flag value is saved to ~/.config/racecar/networking.env on the car, so the setting survives reboots and later runs.

bash
racecar setup networking --ssid=neoracer-2   # rename the access point
racecar setup networking --psk=mypassword    # change the AP password
racecar setup networking --show              # print the saved settings
racecar setup networking --reset             # back to the defaults

Flag	Sets	Default
--ssid	Access point name	neoracer-1
--psk	Access point password	neobotics
--channel	Access point 2.4 GHz channel	6
--ap-addr	The car's address on the access point	10.42.0.1/24
--eth-static	The car's fixed address on the cudy	192.168.10.100/24
--lidar-host	Host address on the lidar link	192.168.8.1/24
--wifi-iface	Wi-Fi interface name	wlP1p1s0
--eth-iface	Ethernet interface name	nr_eth0

07 / NETWORKING AT A GLANCE

QUICK REFERENCE.

Task	How	What it needs
Get on the car (cudy)	Join the router's Wi-Fi.	neoracer-[ID] · 192.168.10.100
Get on the car (AP)	Join the car's own Wi-Fi.	neoracer-1 · 10.42.0.1
Terminal	SSH in as racecar.	racecar@<car address>
Full desktop	RustDesk by direct IP.	<car address>
No Wi-Fi	Wired USB-C, RNDIS link.	racecar@192.168.55.1
Rename the AP	racecar setup networking.	--ssid=neoracer-N
Health dashboard	Browser, auto-started.	:8080
Write code	JupyterLab, auto-started.	:8888
See the car nodes	ROS 2 DDS discovery.	same subnet + ROS_DOMAIN_ID

◀Previous

Workspaces

Next▶

Firmware flashing