Robot Control Principles · SHS3 Robotics

Lesson notes

Learning Objectives

Indicator: 3.1.2.LI.2 - Identify faults in robotic systems and trace them to algorithm flaws, design flaws or coding errors.

By the end of the lesson, learners can:

Classify a fault observed in a robotic system as an algorithm flaw, a design flaw, or a coding error, giving a clear reason for each classification.
Trace a given system fault backwards from its symptom to its root cause using a structured fault-tracing checklist.
Examine a non-functional or faulty robot and produce a written fault report that identifies at least two distinct faults and justifies their classifications.
Brainstorm and discuss whether an observed robotic solution addresses the functional requirements of its intended problem, noting any gaps in performance.
Justify, in small-group discussion, whether the limitations of a given robotic solution are algorithmic, design-related, or programming-related, using evidence from observation.

This lesson builds directly on Weeks 12, 15 and 18, where learners designed, reverse-engineered, and tested autonomous robotic systems. It prepares them for Week 20, where they will fix the faults they identify today through iterative correction.

Sign in with your phone number to read the full note and download the GES plan - free.

Sign in with phone number

Curriculum details

Strand: Principles of Robotic Systems (Strand 1)
Sub-strand: Robot Control Principles (1.2)
Content standard: 3.1.2.CS.3 - 3.1.2.CS.3 Demonstrate practical skills in evaluating and improving existing robotic systems. 3.1.2.LO.3 Create test plans for testing robotic systems to uncover faults and go through an iterative fault detection and correction process to fix the defect.
Indicator: 3.1.2.LI.2 - Identify faults in robotic systems and trace them to algorithm flaws, design flaws or coding errors.
Suggested placement: Semester 1, Week 19 (Week 19 of the year)
Our suggestion, laid out in curriculum order across three terms of twelve weeks. NaCCA does not fix the week, so follow your school's scheme of learning.
Curriculum reference: NaCCA curriculum document, p. 152

Exemplars (from the NaCCA curriculum)

Experiential Learning: For a given problem and a commensurate solution either in video or reality, learners observe sample solution(s) in execution and document the following:
- Outline the functional requirements of a problem
- Brainstorm on whether or not the features of the solution(s) given address all the outlined functional requirements identified.
- Discuss whether the designed solution is realistic, well-proportioned, and efficient.
- List the solution's limitations and classify/justify them as algorithmic, design or programming flaws.

Assessment (3.1.2.AS.2). The document marks these depth-of-knowledge levels for this indicator: Level 3 Strategic reasoning; Level 4 Extended critical thinking and reasoning.

Teaching and Learning Resources:
- Mechanical gauges
- Multimeter
- Oscilloscopes
- Function generators
- Videos on robotic systems
- Real object presentation
- Problem narratives
- Flipcharts
- Non-functional robot
- Problem and solution narratives
- Testing tools(E.g., multimeters, Oscilloscope, mechanical gauges, etc.)
- 3D printers
- Computer-aided design (CAD) tools
- Access to robotics lab with requisite tools (e.g., screwdrivers, glue guns, pliers, multimeters, etc).