University: source-level course
Open low-level interfaces; students changed control algorithms and added their own vision module.
32 hours, source-level
A course works only when hardware, materials, teacher training and class hours line up. We split by stage: primary, secondary, university.
One robot, opened to different depths: see the structure, run the program, then change the system.
Disassemble quadrupeds and cars to meet motors, gears and sensors.
Block-based coding to drive, avoid obstacles and finish tasks.
Full assembly, joint calibration and fault finding as a real engineering loop.
Rule-driven structure tuning, control parameters and pre-match sparring.
Model the scene, run algorithms, then transfer to the real machine.
Open low-level interfaces to change control, add sensors, plug in algorithms.
Vision, force control and mobile base commissioned as one system.
Project-driven prototype modification, data capture and experiment support.
| Core goal | Classroom format | |
|---|---|---|
| Primary, grades 3–6 | Structure and principles plus hands-on habits | Teardown plus block coding at one period each |
| Lower secondary | Assembly and debugging and task completion | Assembly plus task challenges in 8–12 project periods |
| Upper secondary | Systems thinking and competition and simulation | Simulation plus real-machine validation as club or elective |
| Undergraduate, early | Robot system composition and integration | Lab plus course design in 16–32 hours |
| Undergraduate, late | Source-level development and algorithms | Project-based and tied to real topics |
| Postgraduate / lab | Prototype rework and research validation | Custom per topic with data and reproducibility |
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.
Confirm stage, class hours, venue, budget and teaching goals.
Split modules per period with lab manuals and rubrics.
Machines, kits, spares and simulation software sized to class.
Teachers run the labs first: teardown, coding, fault finding.
First-term co-teaching support, then iterate on student feedback.
Open low-level interfaces; students changed control algorithms and added their own vision module.
32 hours, source-level
Grasp policy tuned in simulation first, then transferred to hardware to locate the deviation.
Sim-to-real lab
End effector and sensors reworked per topic, with data capture and reproducible experiments.
Research support
Teams assembled quadrupeds, completing joint calibration and gait tuning.
12 project periods
Structure and control parameters tuned to the rulebook, with pre-match sparring.
Pre-match camp
Scenes built and parameters tuned in simulation, then validated on real machines.
Simulation camp
Cars and quadrupeds taken apart to learn what motors, gears and sensors do.
Science curriculum
Obstacle avoidance and line following in block code, presented by each team.
ICT curriculum
Send stage, class size and hours; we return a syllabus, equipment list and training plan.
Leave your process and contact — an engineer replies during working hours. For anything urgent, call us.
No messages yet
Delivered. An engineer will reply during working hours.