Skip to content
शिक्षाby Grow10x
A line-following robot style build, as students make in Class 11
Class 11 · Engineering

Engineer & validate.Line-Following Robot

Reproducible experiments, model pipelines and system design. Showcase build: an AI-assisted line-following study with a baseline and failure tests.

See all 16 projectsPlan Class 11
  • 16 projects8 robotics, 4 AI, 4 integrated
  • 20 to 80Sessions by plan
  • Python + ArduinoMain language
  • Supervised linkAI to hardware
Class 11 at a glance

What students do, and what they prove.

Showcase build11

Line-Following Robot

An AI-assisted line-following study with a baseline and failure tests.

Learning check. Deliver a reproducible AI and robotics prototype with a baseline, failure tests and a model card.

Individual check. Every learner, on their own: “Defend a baseline comparison.”

Entry task

Use functions and datasets, and explain train/test separation and a robot stop state.

Robotics core

Line sensing, calibrated control, PWM, event logs, state machines and system integration.

AI layer

Supervised models, cross-validation, leakage checks, text features and reproducible evaluation.

Code & tools

Python and Arduino C/C++; optional SQL and JavaScript. Python + scikit-learn, Arduino IDE, Local datasets, API simulator.

Cross-subject link

Distributions, metrics, proportional control and experimental design.

Scaffolding

Template pipelines first. Advanced extensions only after demonstrated readiness.

How AI meets hardware here

Local inference and bounded serial control. Connected designs are simulated, not put online.

Class 11 project sequence

Sixteen projects, four blocks of twenty sessions.

Each block follows the same pattern: two builds, one AI project, then one integrated project. Open any project to see its five sessions.

  • RRobotics
  • AAI
  • IIntegrated
Block 1Sessions 01-20In every plan, from Discovery (3 months)

  1. 01
    Ask & understand · Week 1
    Voltage, ground and safe motor power
  2. 02
    Build & design · Week 1
    Read individual line channels
  3. 03
    Implement · Week 2
    Record light/dark values and thresholds
  4. 04
    Test & improve · Week 2
    Test surface and ambient-light changes
  5. 05
    Explain & reflect · Week 3
    Explain a calibration table
Materials

Grade 11 UNO, line sensor, USB, test surfaces

Minimum test

Each sensor tested over light/dark surfaces; motors disconnected.

Hands-on build

A physical circuit, sensor or mechanism, built and tested on the bench.

Open the project page

  1. 06
    Ask & understand · Week 3
    Boolean decisions and motor directions
  2. 07
    Build & design · Week 4
    Build a basic line-state table
  3. 08
    Implement · Week 4
    Program a slow line-following loop
  4. 09
    Test & improve · Week 5
    Test missing line and motor stop
  5. 10
    Explain & reflect · Week 5
    Document baseline track performance
Materials

Grade 11 LFR kit, verified L298N module, approved pack

Minimum test

Three track runs and five lost-line tests.

Hands-on build

A physical circuit, sensor or mechanism, built and tested on the bench.

Open the project page

  1. 11
    Ask & understand · Week 6
    Features, labels and session-based splitting
  2. 12
    Build & design · Week 6
    Build a small line-sensor dataset
  3. 13
    Implement · Week 7
    Compare a baseline with a simple classifier
  4. 14
    Test & improve · Week 7
    Evaluate a separate capture session
  5. 15
    Explain & reflect · Week 8
    Explain leakage risks
Materials

Local Python/scikit-learn, recorded sensor CSV

Minimum test

Split by capture session; compare per-class results.

AI project

A model, an evaluation study or an AI-checking workflow.

Open the project page

  1. 16
    Ask & understand · Week 8
    Map predictions to bounded state names
  2. 17
    Build & design · Week 9
    Use a simulator before any motor link
  3. 18
    Implement · Week 9
    Compare predicted and rule-based states
  4. 19
    Test & improve · Week 10
    Require operator approval for physical runs
  5. 20
    Explain & reflect · Week 10
    Test stale data and unknown states
Materials

P02/P03, USB or simulator, approved stop control

Minimum test

Twenty recorded states plus invalid/stale cases.

Supervised link

A laptop model sends named commands only after bench tests, with a simulator as fallback.

Open the project page
Block 2Sessions 21-40From the Builder plan (6 months)

  1. 21
    Ask & understand · Week 11
    PWM and load limits
  2. 22
    Build & design · Week 11
    Create a controlled travel experiment
  3. 23
    Implement · Week 12
    Record response at three settings
  4. 24
    Test & improve · Week 12
    Compare motor imbalance
  5. 25
    Explain & reflect · Week 13
    Select a conservative control setting
Materials

LFR chassis, ruler/timer, approved pack

Minimum test

Three settings, three runs each; no unguarded stall test.

Hands-on build

A physical circuit, sensor or mechanism, built and tested on the bench.

Open the project page

  1. 26
    Ask & understand · Week 13
    Error from a line-sensor array
  2. 27
    Build & design · Week 14
    Map error to bounded speed corrections
  3. 28
    Implement · Week 14
    Tune one gain cautiously
  4. 29
    Test & improve · Week 15
    Compare with the Boolean baseline
  5. 30
    Explain & reflect · Week 15
    Explain overshoot and loss of line
Materials

LFR kit, compatible multi-channel sensor output

Minimum test

Same track and start condition for both controllers.

Hands-on build

A physical circuit, sensor or mechanism, built and tested on the bench.

Open the project page

  1. 31
    Ask & understand · Week 16
    Train/validation/test roles
  2. 32
    Build & design · Week 16
    Build a preprocessing-plus-model pipeline
  3. 33
    Implement · Week 17
    Compare two simple models with fixed settings
  4. 34
    Test & improve · Week 17
    Check capture-session leakage
  5. 35
    Explain & reflect · Week 18
    Save configuration and results
Materials

Local Python/scikit-learn, sensor CSV

Minimum test

An untouched final test session; record random seed and versions.

AI project

A model, an evaluation study or an AI-checking workflow.

Open the project page

  1. 36
    Ask & understand · Week 18
    Define a fair comparison question
  2. 37
    Build & design · Week 19
    Run both decision methods in simulation
  3. 38
    Implement · Week 19
    Apply reviewed bounded serial outputs on a raised rig
  4. 39
    Test & improve · Week 20
    Measure error and response delay
  5. 40
    Explain & reflect · Week 20
    Decide whether ML adds value
Materials

LFR kit, laptop model, safe bridge or simulator

Minimum test

Same held-out route states and same safety limits for both methods.

Supervised link

A laptop model sends named commands only after bench tests, with a simulator as fallback.

Open the project page
Block 3Sessions 41-60Innovation plan (12 months)

  1. 41
    Ask & understand · Week 21
    Data schema, units and event timestamps
  2. 42
    Build & design · Week 21
    Log sensor states and commands
  3. 43
    Implement · Week 22
    Reject malformed messages
  4. 44
    Test & improve · Week 22
    Visualise a recorded run
  5. 45
    Explain & reflect · Week 23
    Explain why local serial is not internet IoT
Materials

UNO, USB, local Python, LFR kit

Minimum test

Fifty records including five malformed examples.

Hands-on build

A physical circuit, sensor or mechanism, built and tested on the bench.

Open the project page

  1. 46
    Ask & understand · Week 23
    Startup, running, lost-line and stopped states
  2. 47
    Build & design · Week 24
    Draw event and transition rules
  3. 48
    Implement · Week 24
    Implement timeout and manual isolation
  4. 49
    Test & improve · Week 25
    Test state priority and reset
  5. 50
    Explain & reflect · Week 25
    Publish an operator checklist
Materials

LFR kit, physical power switch, local console

Minimum test

All transitions plus five intentional faults.

Hands-on build

A physical circuit, sensor or mechanism, built and tested on the bench.

Open the project page

  1. 51
    Ask & understand · Week 26
    Define supported maintenance intents
  2. 52
    Build & design · Week 26
    Use synthetic short text examples
  3. 53
    Implement · Week 27
    Train a local text classifier
  4. 54
    Test & improve · Week 27
    Test unknown and contradictory requests
  5. 55
    Explain & reflect · Week 28
    Link results to source-backed checklists
Materials

Local Python, reviewed synthetic phrases, device notes

Minimum test

Twenty held-out cases; unsafe requests routed to a teacher.

AI project

A model, an evaluation study or an AI-checking workflow.

Open the project page

  1. 56
    Ask & understand · Week 28
    Design read-only tools and a command schema
  2. 57
    Build & design · Week 29
    Connect triage labels to approved troubleshooting cards
  3. 58
    Implement · Week 29
    Keep drive actions unavailable
  4. 59
    Test & improve · Week 30
    Test adversarial or irrelevant input
  5. 60
    Explain & reflect · Week 30
    Document permissions and refusals
Materials

P11 model, local manual, simulated tool API

Minimum test

Ten valid and five rejected requests; no hardware writes.

Advisory only

The AI advises a person. It has no control over the hardware.

Open the project page
Block 4Sessions 61-80Innovation plan (12 months)

  1. 61
    Ask & understand · Week 31
    Control experimental conditions
  2. 62
    Build & design · Week 31
    Build two clearly labelled track layouts
  3. 63
    Implement · Week 32
    Log repeated runs and route states
  4. 64
    Test & improve · Week 32
    Compare performance by condition
  5. 65
    Explain & reflect · Week 33
    Write a limitations statement
Materials

LFR kit, track material, logging computer

Minimum test

Three runs per layout with identical starting conditions.

Hands-on build

A physical circuit, sensor or mechanism, built and tested on the bench.

Open the project page

  1. 66
    Ask & understand · Week 33
    Device, gateway and dashboard roles
  2. 67
    Build & design · Week 34
    Specify JSON messages and status fields
  3. 68
    Implement · Week 34
    Simulate a connection using local files/loopback
  4. 69
    Test & improve · Week 35
    Test missing data and reconnect rules
  5. 70
    Explain & reflect · Week 35
    Explain what extra hardware real IoT needs
Materials

Computer, UNO optional, local JSON/CSV files

Minimum test

Five normal and five failure messages.

Hands-on build

A physical circuit, sensor or mechanism, built and tested on the bench.

Open the project page

  1. 71
    Ask & understand · Week 36
    Define a task, trigger, resources and limits
  2. 72
    Build & design · Week 36
    Create a portable workflow specification
  3. 73
    Implement · Week 37
    Add examples, tests and version history
  4. 74
    Test & improve · Week 37
    Review optional tool scopes and dependencies
  5. 75
    Explain & reflect · Week 38
    Run a repeatability and failure test
Materials

Markdown/text, test files, local scripts; optional teacher Skills demo

Minimum test

Three valid and three invalid tasks with expected outcomes.

AI project

A model, an evaluation study or an AI-checking workflow.

Open the project page

  1. 76
    Ask & understand · Week 38
    Define a measurable robotics question
  2. 77
    Build & design · Week 39
    Integrate controller, model and audit log
  3. 78
    Implement · Week 39
    Preserve independent interlocks and human authority
  4. 79
    Test & improve · Week 40
    Run reproducible baseline and failure trials
  5. 80
    Explain & reflect · Week 40
    Defend results, limitations and responsible-use choices
Materials

LFR kit, local Python model, reviewed bridge or simulator

Minimum test

Three repeat runs plus unknown, stale-data, stop and reset tests.

Supervised link

A laptop model sends named commands only after bench tests, with a simulator as fallback.

Open the project page
How thinking grows

Class 11 adds one more layer of judgement.

Hardware thinking

Reproducible system experiments

AI & data thinking

Pipelines, leakage and model comparison

Programming depth

Python and Arduino; optional SQL and JavaScript

Reusable skill

A reproducible, evaluated workflow with failure tests.

Tool and permission habit

Review dependencies, access scopes, logs and lifecycle.

Evidence

A portable workflow specification and evaluation pack.

Python + scikit-learnArduino IDELocal datasetsAPI simulator
Two teachers guiding uniformed students as they build a robot car in a classroomFor school leaders

Bring Class 11
to your school.

Start with the four Discovery projects for Class 11 (20 sessions), review the evidence together, then extend to Builder or Innovation.

  • Prospectus and class-wise plan
  • Kit and readiness check
  • Pilot one class first
  • Evidence at every milestone
School enquiry

Let's plan your pilot.

Share a few details and we will send the right plan for your classes.

Classes you are considering

No spam. We reply within two working days. Prefer email? shiksha@grow10x.io