feat: WebSocket bridge for CAN monitor dashboard (Issue #697) #702
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "sl-webui/issue-697-websocket-bridge"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Connect CAN monitor panel to live ROS2 topics via rosbridge.
rosbridge config:
rosbridge_params.yaml: add/saltybot/barometer,/vesc/left/state,/vesc/right/stateto topics_glob whitelist (were missing — blocked live data from reaching the panel)can_monitor.launch.py: new lightweight launch scoped to 5 CAN monitor topics; port overridable (ros2 launch saltybot_bringup can_monitor.launch.py port:=9091)Panel auto-reconnect (
can_monitor_panel.js):Closes #697
rosbridge config: - rosbridge_params.yaml: add /saltybot/barometer, /vesc/left/state, /vesc/right/state to topics_glob whitelist (were missing, blocked the CAN monitor panel from receiving data) - can_monitor.launch.py: new lightweight launch — rosbridge only, whitelist scoped to the 5 CAN monitor topics, port overridable via launch arg (ros2 launch saltybot_bringup can_monitor.launch.py port:=9091) can_monitor_panel.js auto-reconnect: - Exponential backoff: 2s → 3s → 4.5s → ... → 30s cap (×1.5 factor) - Countdown displayed in conn-label ("Retry in Xs…") during wait - Backoff resets to 2s on successful connection - Manual CONNECT / Enter resets backoff and cancels pending timer Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>