Feasibility read within 2 working hours — if it will not work, we say so

Leave your contact

Stage, goal and format

Core goalClassroom format
Primary, grades 3–6Structure and principles plus hands-on habitsTeardown plus block coding at one period each
Lower secondaryAssembly and debugging and task completionAssembly plus task challenges in 8–12 project periods
Upper secondarySystems thinking and competition and simulationSimulation plus real-machine validation as club or elective
Undergraduate, earlyRobot system composition and integrationLab plus course design in 16–32 hours
Undergraduate, lateSource-level development and algorithmsProject-based and tied to real topics
Postgraduate / labPrototype rework and research validationCustom per topic with data and reproducibility

Taking it apart is the fastest way to understand

Hand a robot to students and the first task is not code, it is a screwdriver. Once opened, why the motor sits in the joint, how the encoder reads angle, why the harness runs through the middle — all become visible questions. With the structure understood, students know which part each line of code drives.

  • Teardown checklists and torque specs, safe and repeatable
  • Every part maps to a knowledge point
  • It must run when reassembled
  • Fault-finding builds engineering thinking
  • Simulation first, less wear on hardware
  • Extends into competition and projects
Taking it apart is the fastest way to understand

Five steps to launch a course

  1. STEP 1

    Align

    Confirm stage, class hours, venue, budget and teaching goals.

  2. STEP 2

    Design

    Split modules per period with lab manuals and rubrics.

  3. STEP 3

    Equip

    Machines, kits, spares and simulation software sized to class.

  4. STEP 4

    Train teachers

    Teachers run the labs first: teardown, coding, fault finding.

  5. STEP 5

    Run & review

    First-term co-teaching support, then iterate on student feedback.

Campus course cases

University: source-level course

Engineering school (anonymised)

Open low-level interfaces; students changed control algorithms and added their own vision module.

32 hours, source-level

University: sim-to-real lab

Automation dept. (anonymised)

Grasp policy tuned in simulation first, then transferred to hardware to locate the deviation.

Sim-to-real lab

University: thesis prototype rework

Robotics group (anonymised)

End effector and sensors reworked per topic, with data capture and reproducible experiments.

Research support

Secondary: assembly and debugging

STEM-focused school (anonymised)

Teams assembled quadrupeds, completing joint calibration and gait tuning.

12 project periods

Secondary: competition camp

Competition team (anonymised)

Structure and control parameters tuned to the rulebook, with pre-match sparring.

Pre-match camp

Secondary: simulation camp

School club (anonymised)

Scenes built and parameters tuned in simulation, then validated on real machines.

Simulation camp

Primary: teardown class

Science team (anonymised)

Cars and quadrupeds taken apart to learn what motors, gears and sensors do.

Science curriculum

Primary: block coding tasks

Primary ICT class (anonymised)

Obstacle avoidance and line following in block code, presented by each team.

ICT curriculum

Note: courses on this page describe stage-based designs; hours and equipment are adjustable to each school. Cases describe course types with school names anonymised. Syllabus and credit recognition follow the school academic office review.

Campus FAQ

We have no robotics teacher — can we still run it?
Yes. Teacher training plus first-term co-teaching: teachers complete the teardown, coding and fault-finding labs before class, with lesson plans, manuals and rubrics ready to use.
How many units do we need?
Set by class size and grouping: primary teardown 4–6 students per group, secondary assembly one unit per 2–3 students, university labs one per two. Add a share of spares and wear parts so one failure does not stall a class.
How should class hours be arranged?
Primary: single periods over 6–8 sessions; secondary: 8–12 project periods; university: 16–32 hours. Separate teardown from coding and alternate simulation with hardware to hold attention.
Does it connect to competitions?
Yes. Structure tuning, parameter setting and fault finding map to common event requirements; a pre-match camp then adapts structure and parameters to the rulebook.
How open is the university-level interface?
Layer by layer as needed: control interfaces, sensor inputs, protocols and log data, plus SDKs and sample projects. Firmware-level changes are agreed per project.
How are safety and service handled?
Teaching units can be speed-limited with emergency stop; teardown parts have rounded edges and anti-pinch design. Warranty and standby units are available, and teacher training covers safety rules.

A course sized to your stage and hours

Send stage, class size and hours; we return a syllabus, equipment list and training plan.

Talk to us