How ivan-smit/aux-robot-4x4 works
AUX-ROBOT-4x4 combines a browser control panel, a Python proxy/planner, and ESP32 motor firmware. The main workflow is to connect the launcher to the robot’s Wi-Fi, send manual commands or draw a route, then use camera-derived marker pose to guide Turn-and-Go movement and report status to the UI. README-described capabilities include live controller tuning, detection-zone filtering, trajectory plots, and one-click launch. Some README features are represented at subsystem level because their implementation was not sampled; edges are limited to explicit README or source evidence.
Main entry points: proxy.py WebSocket / TCP proxy · main.js UI controls · planner.py Trajectory tracker · visual_odometry.py Visual odometry
Components 15
Launch
- Launcher
client/launcher.py
Control interface
- Browser panel
client/static/index.html - UI controls
client/static/js/main.js - WebSocket / TCP proxy
client/proxy.py - Route drawing and plots
client/static/js/main.js
Autonomous navigation
- Robot configuration
client/config.py - Visual odometry
client/visual_odometry.py - Marker detection
client/visual_odometry.py - Trajectory tracker
client/planner.py - Trajectory images
client/graphs
Robot runtime
- ESP32 firmware
src/bobr4x4.c - Motor drivers
src/bobr4x4.c - Robot Wi-Fi AP
src/bobr4x4.c
Other components
- Operator
- Camera
Connections 22
- Operator → Launcher: starts
README.md - Launcher → WebSocket / TCP proxy: starts process
client/launcher.py - Operator → Browser panel: uses
README.md - Browser panel → UI controls: loads
- UI controls → WebSocket / TCP proxy: sends commands
client/static/js/main.js - WebSocket / TCP proxy → ESP32 firmware: sends TCP commands
client/proxy.py - ESP32 firmware → Robot Wi-Fi AP: hosts
src/bobr4x4.c - Operator → Route drawing and plots: draws route
README.md - Route drawing and plots → UI controls: sends route
client/static/js/main.js - WebSocket / TCP proxy → Visual odometry: starts capture
client/proxy.py - Camera → Visual odometry: provides frames
client/visual_odometry.py - Visual odometry → Marker detection: detects marker
client/visual_odometry.py - WebSocket / TCP proxy → Trajectory tracker: starts tracker
client/proxy.py - WebSocket / TCP proxy → Trajectory tracker: updates pose
client/proxy.py - Trajectory tracker → ESP32 firmware: sends motor commands
client/planner.py - ESP32 firmware → Motor drivers: applies PWM
src/bobr4x4.c - Robot configuration → Trajectory tracker: configures
client/planner.py - Robot configuration → Visual odometry: configures
client/visual_odometry.py - Trajectory tracker → WebSocket / TCP proxy: broadcasts telemetry
client/planner.py - WebSocket / TCP proxy → UI controls: sends telemetry
- UI controls → Trajectory images: saves trajectory PNG
client/static/js/main.js - WebSocket / TCP proxy → Visual odometry: starts debug view
client/proxy.py