Chips’nCode
← Back to Unit 2

Week 4: Build, Drive, and Test the Cube Collector Clawbot

YEAR 9 DIGITAL TECHNOLOGIES • WEEK 4

Build, Drive, and Test the Cube Collector Clawbot

This week you will build or finish building the Cube Collector Clawbot, test it with driver control, and begin noticing how the physical design affects performance.

Used each lesson: VEX IQ kit, BaseBot build, Clawbot build, battery, controller, IQ cubes, field tiles, device with VEXcode IQ, and your engineering notebook.

💻 VEXCODE HELP

If you need help opening VEXcode, connecting your robot, configuring devices, downloading a project, or checking robot setup, use the internal VEXcode reference page first.

Open the VEXcode setup and help page
🎯 THIS WEEK
  • build or complete the Cube Collector Clawbot
  • check battery, controller, ports, build quality, and robot setup
  • use the Driver Control program on the Brain
  • test different driver control configurations
  • complete Stack and Score practice
  • attempt the Speed Stack challenge
  • observe the arm and claw stability problem for next week
📘 ENGINEERING NOTEBOOK

Your engineering notebook is required in every lesson.

  • record build progress and problems fixed
  • sketch or photograph the finished Clawbot
  • record driver control tests and configuration changes
  • record what happens when the robot lifts or stacks cubes
✅ BY THE END OF WEEK 4
  • your Cube Collector Clawbot should be built or mostly complete
  • your robot should be tested using Driver Control
  • your notebook should show build evidence and driver-control testing
  • you should have noticed at least one physical design issue to investigate next week
📌 IMPORTANT
  • Do not force parts together if they do not fit.
  • Check orientation carefully before connecting pieces.
  • Do not drive the robot into people, walls, bags, or other robots.
  • Do not lift stacked cubes high or fast until you have tested robot stability.
Lesson 1: Build the Cube Collector Clawbot
📝 TODAY'S RECORDING

Record your build progress, any problems your group solved, and evidence that your robot is ready for driver-control testing.

🔧 WHAT TO DO
  1. Check that your battery and controller are charged.
  2. Pair the Controller and Brain if they are not already connected.
  3. Open the BaseBot build instructions if your robot base is not complete.
  4. Build or check the BaseBot carefully before adding the claw and arm.
  5. Open the Clawbot build instructions.
  6. Add the claw and arm attachment to the BaseBot.
  7. Check that all pins, beams, gears, shafts, and cables are secure.
  8. Check that the arm can move without catching on the frame.
  9. Check that the claw can open and close without jamming.
  10. Show your build to your teacher before moving into driver testing.
✍️ WHAT TO WRITE IN YOUR ENGINEERING NOTEBOOK
  1. Write the date and lesson title: Lesson 1 - Build the Cube Collector Clawbot.
  2. Record your starting build stage: not started, BaseBot partly complete, BaseBot complete, or Clawbot partly complete.
  3. Record what your group completed today.
  4. Sketch or photograph the finished or partly finished build.
  5. Write one build problem your group noticed.
  6. Write how your group fixed or checked that problem.
  7. Record whether the arm and claw moved freely by the end of the lesson.
✅ WHAT COUNTS AS FINISHED
  • BaseBot checked
  • claw and arm attached or build progress recorded
  • battery and controller checked
  • arm and claw inspected
  • notebook entry complete
  • teacher build check completed
🛟 IF YOU GET STUCK
  • Check the step number in the build instructions.
  • Check the orientation of the part before connecting it.
  • Compare your build with another group that is further ahead.
  • Ask for a build check before forcing a part into place.
🚀 IF YOU FINISH EARLY
  • check every cable and port
  • check that the arm lifts smoothly
  • check that the claw grips one cube
  • help another group with build checking, not building it for them
Lesson 2: Driver Control and Stack and Score
📝 TODAY'S RECORDING

Record which driver control configuration you tested, how easy it was to drive, and how well the robot stacked or scored cubes.

🔧 WHAT TO DO
  1. Open the Driver Control resources.
  2. Start the Driver Control program on the VEX IQ Brain.
  3. Choose one driver control configuration to test first.
  4. Practise driving forward, reversing, turning, lifting the arm, and using the claw.
  5. Set up the Stack and Score practice activity.
  6. Drive the robot to pick up and stack one cube.
  7. Drive the robot to move the other cube into the matching scoring zone.
  8. Record how comfortable the driver control setup felt.
  9. Change one driver control setting or strategy and test again.
  10. Make sure each group member has a chance to test driving if time allows.
✍️ WHAT TO WRITE IN YOUR ENGINEERING NOTEBOOK
  1. Write the date and lesson title: Lesson 2 - Driver Control and Stack and Score.
  2. Write the driver control configuration you tested first.
  3. Record whether it was easy or difficult to drive accurately.
  4. Record whether you successfully picked up a cube.
  5. Record whether you successfully stacked or scored a cube.
  6. Write one change your group made to improve control.
  7. Record whether that change helped.
✅ WHAT COUNTS AS FINISHED
  • Driver Control program tested
  • at least one configuration tested
  • Stack and Score attempted
  • one control change tested
  • notebook evidence complete
  • teacher check completed
🛟 IF YOU GET STUCK
  • Check the Controller is paired with the Brain.
  • Check the robot battery level.
  • Check the motors are plugged into the expected ports.
  • Practise one movement at a time before trying to score.
  • Drive slowly when lining up with a cube.
🚀 IF YOU FINISH EARLY
  • test a second driver control configuration
  • compare which configuration gives better precision
  • try stacking more carefully, not just faster
  • record which driver strategy works best for your group
Lesson 3: Speed Stack and Engineering Observation
🎯 TODAY'S CHALLENGE

Drive your Clawbot to score both cubes as quickly as possible, with at least one cube stacked. Then observe what happens when the robot lifts or carries stacked cubes.

🔧 WHAT TO DO
  1. Finish any build or Driver Control catch-up work first.
  2. Set up the Speed Stack challenge field.
  3. Choose the driver control configuration your group wants to use.
  4. Run one serious timed attempt.
  5. Record your result in your notebook.
  6. Make one strategy change: speed, approach angle, arm height, claw use, or driver role.
  7. Run the challenge again and compare the result.
  8. After the main challenge, test what happens when the robot tries to lift or move stacked cubes.
  9. Watch carefully for tipping, dropping, wobbling, or unstable arm movement.
  10. Record the engineering problem you noticed and one possible cause.
⚠️ ENGINEERING PROBLEM TO NOTICE

When the Clawbot tries to lift or carry stacked cubes, the robot may become unstable. It can tip forward, wobble, drop the cubes, or become harder to control.

Do not rush to fix this yet. Your job today is to observe the problem carefully and collect evidence so we can engineer a better solution next week.

✍️ WHAT TO WRITE IN YOUR ENGINEERING NOTEBOOK
  1. Write the date and lesson title: Lesson 3 - Speed Stack and Engineering Observation.
  2. Record your first timed Speed Stack result.
  3. Record your best timed result.
  4. Write one strategy change your group tested.
  5. Write whether that strategy change helped.
  6. Record what happened when the robot lifted or carried stacked cubes.
  7. Write one possible reason the robot tipped, wobbled, or dropped cubes.
  8. Write one idea your group might test next week to improve stability.
✅ WHAT COUNTS AS FINISHED
  • Speed Stack attempted
  • at least two runs recorded if time allows
  • one strategy change tested
  • stacked-cube stability observed
  • engineering problem recorded
  • teacher notebook sign-off completed
🛟 IF YOU GET STUCK
  • Go back to Stack and Score before trying Speed Stack again.
  • Drive more slowly while lining up the claw.
  • Check that the claw is gripping the cube properly.
  • Check whether the arm is lifting higher than needed.
  • Ask for a build check if the robot behaves strangely.
🚀 IF YOU FINISH EARLY
  • compare two driver configurations
  • test whether slower arm movement improves control
  • test whether lower lifting height reduces tipping
  • sketch one possible engineering modification for next week

📍 Looking ahead to Week 5

Next week we will start by engineering a better solution to the arm and claw stability problem. If the robot tips, wobbles, or drops stacked cubes, that is not just a driving problem. It is a design problem.

After that, we will move from driver control into autonomous coding for cube collection and scoring. Keep your Cube Collector Clawbot assembled, save your notes, and make sure your notebook clearly shows what your group observed.