This one is a form, not an article. Download it, print it, and bring it to the event. Every robot competing in a Sphero Robotics Competition is inspected before it is allowed on the field, and this is the sheet the inspector fills in.
It is one page. An inspector works down it with the team, marking each robot PASS or FIX, and signs it at the bottom alongside a student representative. A robot marked FIX may not compete until the problem is corrected and the robot passes re-inspection. Both of a team’s robots have to pass before that team competes.
What gets checked
Seven checks, each tied to a rule in the SRC Competition Manual. Team Coordinators are better off reading these before the event than discovering them at the inspection table.
- LP-R1, the robot is the team’s own. It belongs uniquely to this team and has not been shared with another.
- LP-R4, size. The robot fits fully inside the official Inspection Sizing Tool in every configuration: no more than 20 pitch by 16 pitch by 22 pitch, which is 500 mm by 400 mm by 550 mm. Length and width are not measured diagonally.
- LP-R5, the drive base. A Sphero Blueprint Swerve Drive Robot is the drive and control base, with the drive system, control board and battery unmodified.
- LP-R6, power. The standard Sphero Blueprint Swerve Drive Robot battery is the only power source.
- LP-R7, electronics and motors. Only the allowed Sphero Blueprint Robotics parts, which include the High-Speed Motor, the High-Torque Motor, the Distance Sensor and the Magnetic Proximity Switch.
- LP-R8, safety. No parts that could cause damage, snag or entangle, and no exposed sharp edges, loose fasteners or prohibited modifications.
- LP-R2 and LP-R9, Student-Powered. Students confirm that they designed, built and coded the robot, including any 3D printed parts. Sphero Rapid Robot designs and programs are allowed.
What the sheet records
Team number and inspector at the top. A PASS or FIX box for each check, for each of the two robots. A final status of TEAM Ready or Re-inspection needed for each robot. Then two signatures, one from a student representative and one from the robot inspector, and a space for correction notes so a team knows exactly what to fix before coming back.
Who needs it
Event Hosts print a copy for every team attending and hand them to the inspectors. Team Coordinators should read it in advance and check their own robots against it, because every item on it is a reason a robot can be turned away on the day.