Achieving Software Quality Excellence Thru Software-Hardware Co-Design & Co-Verification
summary
Robotics team reports concrete results: in a 2m30s match regimen they add an IR sensor plus an LED panel so intake detection becomes consistent (15–20 trial comparison shows weight‑timed code fluctuates while IR is stable), an automated tester diagnoses 12 servos and 8 motors in about 4 minutes, odometry plus distance sensors and a Calman filter cut localization Y‑error significantly, and a 30s straight‑line test shows Pedro paing yields much less trajectory error than Road Runner, improving autonomous scoring.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:13First Tech Challenge rules
- 4:35Co-design and co-verification
- 6:21Good code design strategies
- 8:53Deposition system case study
- 12:55Automated robot testing
- 15:03Intake sensor SWAT case study
- 18:05Autonomous movement case study
- 27:24Kalman filter validation
- 27:44Trajectory libraries
- 33:08Performance analysis
- 34:38Conclusion
- 36:25Acknowledgements
- 36:46Question and answer session
related talks
49mBuilding a self driving RC car
47mPanel: The Future of Robotics
19mThe Physical Turing Test: Solving General Purpose Robotics
31mData as an instrument for more efficient collaboration with robots
21mAPP4MC RaceCar: A Practical ADAS Demonstrator for Evaluating and Verifying Timing Behavior
18mRobotics: why now?
13mChallenges in High Performance Robotics Systems
27mAutomated Python Powered Turret