Software Platform#
The Honey Badger robot has two onboard computers with separate roles:
LPC (Locomotion PC) — UP Squared Pro 7000
APC (Application PC) — Nvidia Jetson Orin Nano Super
This separation helps keep real-time locomotion control isolated from user applications and high-level compute workloads.
LPC (Locomotion PC)#
The LPC is the primary real-time control computer for the robot. It typically runs:
bridge_node— low-level interface to the mainboard and actuatorscontrol_node— locomotion and motion control stackstate_publisher_node— ROS 2 transform publisherconfig_node— configuration and parameter server
The LPC is responsible for safe, deterministic robot motion and direct hardware handling.
The nodes are started automatically at power-up by the hb50 systemd service, which runs the bringup.launch.py launch file as user hb. The robot name, which is also the ROS 2 namespace (hb50, hb50w or hb40), is set by ROBOT_NS in /etc/default/hb50, together with ROS_DOMAIN_ID. The console output of the current and the previous run is stored in ~/.hb50.log and ~/.hb50_previous.log; ROS 2 log files are kept in RAM in /run/hb/log and removed when the service stops. To restart the robot software, connect over SSH and run:
sudo systemctl restart hb50
The software is installed from the hb50-robot package in /opt/hb50-robot. The installed version is published on the /hb50/version_data/robot topic. For installing new versions, see Software Update.
APC (Application PC)#
The APC is the user-facing application computer. It is intended for:
perception and mapping
autonomous behavior and planning
custom user applications
data logging and analysis
By default, MAB-supplied ROS 2 nodes are not launched on the APC. This keeps the APC available for additional compute workloads without affecting the locomotion stack. The only exception is the optional hb50-payload package, which runs the camera, lidar and LED payload, see Camera & Lidar.
Network roles#
Both computers are connected to the robot’s internal network:
LPC— static IP10.11.0.10, hostnamehb50.lanAPC— static IP10.11.0.11, hostnamehb50-orin.lan
The robot also provides a Wi-Fi access point for external controllers, such as the Steam Deck.
Why this matters#
Separating the locomotion computer from the application computer delivers several benefits:
improved stability for low-level control
reduced jitter when running compute-intensive user code
clearer operational boundaries for users and developers
easier troubleshooting and system monitoring
For network and connectivity details, see Networking.