sl-firmware c66a5ce974 feat: Add Issue #408 - ROS2 system health monitor with node heartbeats + auto-restart
Implements central health monitoring system for SaltyBot with:
- Heartbeat subscription from /saltybot/<node_name>/heartbeat
- Dead node detection (>5s timeout, configurable)
- Automatic restart via ros2 launch with configurable retry limits
- System health publishing to /saltybot/system_health (JSON)
- Face alert integration for CRITICAL node failures
- Full_stack.launch.py integration at t=1s launch sequence

Package structure:
- saltybot_system_health: Main ROS2 package
  - health_monitor_node.py: Central monitoring node
  - msg/SystemHealth.msg, msg/NodeStatus.msg: Health status messages
  - config/health_monitor.yaml: Node definitions and criticality levels
  - launch/health_monitor.launch.py: Standalone launch

Configuration:
- heartbeat_timeout: 5.0 seconds (node marked DEAD if missing)
- monitor_freq: 2.0 Hz (check interval)
- auto_restart: enabled with max 3 restarts per node
- face_alert: triggers on CRITICAL node down

Node definitions include: robot_state_publisher, STM32 bridge,
cmd_vel bridge, sensors (RPLIDAR, RealSense), SLAM (RTAB-Map),
Nav2, perception, follower, and rosbridge.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2026-03-04 22:44:30 -05:00
..

Jetson Nano — AI/SLAM Platform Setup

Self-balancing robot: Jetson Nano dev environment for ROS2 Humble + SLAM stack.

Stack

Component Version / Part
Platform Jetson Nano 4GB
JetPack 4.6 (L4T R32.6.1, CUDA 10.2)
ROS2 Humble Hawksbill
DDS CycloneDDS
SLAM slam_toolbox
Nav Nav2
Depth camera Intel RealSense D435i
LiDAR RPLIDAR A1M8
MCU bridge STM32F722 (USB CDC @ 921600)

Quick Start

# 1. Host setup (once, on fresh JetPack 4.6)
sudo bash scripts/setup-jetson.sh

# 2. Build Docker image
bash scripts/build-and-run.sh build

# 3. Start full stack
bash scripts/build-and-run.sh up

# 4. Open ROS2 shell
bash scripts/build-and-run.sh shell

Docs

Files

jetson/
├── Dockerfile              # L4T base + ROS2 Humble + SLAM packages
├── docker-compose.yml      # Multi-service stack (ROS2, RPLIDAR, D435i, STM32)
├── README.md               # This file
├── docs/
│   ├── pinout.md           # GPIO/I2C/UART pinout reference
│   └── power-budget.md     # Power budget analysis (10W envelope)
└── scripts/
    ├── entrypoint.sh       # Docker container entrypoint
    ├── setup-jetson.sh     # Host setup (udev, Docker, nvpmodel)
    └── build-and-run.sh    # Build/run helper

Power Budget (Summary)

Scenario Total
Idle 2.9W
Nominal (SLAM active) ~10.2W
Peak 15.4W

Target: 10W (MAXN nvpmodel). Use RPLIDAR standby + 640p D435i for compliance. See docs/power-budget.md for full analysis.