A STEM lab needs a working lesson sequence, not just a shelf of devices. Begin with the activity students should complete: reading a sensor, making a decision in code, moving a mechanism and explaining the result. The mBot2 record below links to Makeblock’s learning platform information. A desktop arm can support a different manipulation exercise, but it should not be treated as a substitute for a mobile coding lesson.
Before requesting a class set, have the teacher install the proposed environment on a school-managed device. Confirm that projects can be saved and reopened under the school’s account rules, that the intended lesson works on the available network and that students have a clear way to recover from an error. Separate functions demonstrated in a vendor lesson from activities the teacher has personally validated.
Plan the practical station as well as the robot: storage, charging, labelled parts, a clear work area and an accessible way for students to stop an activity. Ask for replacement parts and the instructions needed to repair common classroom damage. Record which tasks require adult supervision and follow the manufacturer’s age, handling and operating instructions.
For a pilot lesson, use the actual timetable and group arrangement. Observe setup time, how many students can participate, whether projects survive switching devices and what support the teacher needs. Compare complete working stations with the same learning objective. These catalogue records are starting points for that evaluation; they do not establish curriculum alignment or independently measured learning outcomes.