ROBOTICS TRACK / LEVEL 06 ROADMAP

Vision-Guided Robotics

Coordinate high-level vision and low-level robot control through explicit messages, independent safety checks, timeouts, and recoverable failure.

Roadmap status: complete integration chain unvalidated

This final-level plan depends on approved robot-control and computer-vision baselines. Messaging, power, mounting, command expiry, independent local safety, restart, latency, and emergency-stop behavior must all pass together before the level can be frozen. Do not purchase Level 6 hardware from this page.

THE GOAL

Build autonomy that fails safely

Students divide responsibilities between processors, design a small communication protocol, calibrate camera evidence into steering, preserve local obstacle safety, diagnose latency, and prove what happens when data becomes uncertain, malformed, stale, or missing.

READY IF…

Both upstream systems work independently

  • Meet Level 4 robot-control and Level 5 vision readiness.
  • Operate and diagnose the robot and vision pipeline separately.
  • Distinguish NO_TARGET, UNSURE, invalid data, and subsystem failure.
  • Work with coordinate error, elapsed time, graphs, and repeated trials.
  • Follow and demonstrate the Level 6 emergency-stop protocol.

PROVISIONAL HARDWARE

Integrate proven systems

HW
REUSE

Level 3–4 robot plus Level 5 vision computer

The pathway is designed to combine the already proven low-level robot controller, motors and sensors with the already proven camera, computer, and inspectable vision pipeline.

INTEGRATION DIRECTION

Wired serial/USB first

The current candidate uses an explicit message link between the vision processor and robot controller. Exact cable, mounting, power, protocol, and recovery details remain provisional until the physical chain passes.

Planning estimate: $45–$100 incremental beyond reused Level 3–5 hardware. The larger upstream platforms are not included in that incremental band.

PLANNED LEARNING ARC

Twelve lessons

12
Lesson 01 / BoundariesTwo processors and clear responsibilities

Decide what vision may request and what the robot must always control locally.

Lesson 02 / ProtocolMessage format, parsing, acknowledgements, and validation

Create explicit, inspectable communication instead of hidden coupling.

Lesson 03 / LivenessHeartbeats, command expiry, watchdogs, and safe stop

Prove that stale or missing messages cannot keep the robot moving.

Lesson 04 / CalibrateCamera-to-robot coordinates

Measure how image position relates to the robot’s physical steering direction.

Lesson 05 / SteerPixel error to differential motion

Translate a validated target position into bounded steering requests.

Lesson 06 / VetoVision plus independent distance safety

Keep local obstacle evidence authoritative even when vision requests movement.

Lesson 07 / CommandsMarkers, duplicate suppression, and states

Validate commands and prevent one repeated marker from advancing a mission repeatedly.

Lesson 08 / MissionMulti-step plans and sensor-evidence branches

Represent a mission whose next action depends on checked evidence.

Lesson 09 / RecoverLost target, blocked path, and bounded recovery

Handle expected failures without endless searching or unsafe movement.

Lesson 10 / DiagnoseTimestamped logs, latency, and regression

Align evidence across processors and locate communication or timing faults.

Lesson 11 / IntegrateFull mission prototype

Assemble vision, protocol, low-level control, independent safety, and recovery.

Lesson 12 / ProveRepeated challenge, revision, and safety case

Run comparable missions, improve one decision, and defend the final safety boundaries.

PATHWAY CAPSTONE

Autonomous mission robot

06
CAPSTONE FAMILIES

A mission with meaningful evidence

Planned choices include destination-marker delivery, colored-target following, a station-reading warehouse robot, a high-visibility rescue rover, or an equivalent approved invention.

COMPLETION STANDARD

Prove the safety chain

Students must defend processor responsibilities, calibration, uncertainty handling, stale and invalid command stops, the independent distance override, one bounded recovery, timestamped diagnosis, three comparable trials, and a reachable physical emergency stop.