The Robotic Arm Classroom

Purpose and intended audience

This toolkit helps CTAE engineering teachers plan, teach, and assess a robotic arm project using low-cost, Arduino-based hardware — without assembling every resource from scratch.

It is designed for teachers of introductory and intermediate engineering courses, including Foundations of Engineering and Technology and related pathway courses, who know the engineering design process but may have limited experience with servo-driven robotics or microcontroller programming. Program coordinators and instructional coaches can use it to support pathway teachers. Everything is organized so you can move from planning to classroom delivery to assessment in order. It addresses a documented gap: strong evidence supports robotics instruction, yet classroom-ready support for the teachers who deliver it remains scarce (Anwar et al., 2019).

What you will be able to do

After using this toolkit, CTAE engineering teachers will be able to:

Grounded in how teachers learn

Because the users of this toolkit are experienced educators, its design begins with adult learning theory. Knowles (1980) held that adults learn best when instruction is self-directed, draws on their experience, is oriented to real professional problems, and is immediately applicable. The toolkit therefore supplies concrete, editable materials you adapt to your own context rather than abstract guidance. Research on effective professional development reinforces this: development that changes practice is content-focused, active, collaborative, model-rich, sustained, and supported by feedback (Darling-Hammond et al., 2017), and it is strengthened in professional learning communities (Vescio et al., 2008).

The toolkit also targets teacher readiness. Because self-efficacy shapes whether teachers attempt and persist with new methods (Tschannen-Moran & Woolfolk Hoy, 2001), the materials break the project into low-risk, scaffolded steps and pair every build task with troubleshooting support. Because effective technology use means integrating content, pedagogy, and technology (Mishra & Koehler, 2006), each phase links the engineering concept, the teaching move, and the tool. Because adoption depends on knowledge, confidence, beliefs, and school culture (Ertmer & Ottenbreit-Leftwich, 2010), the design is deliberately low-cost and standards-aligned. The subject matter is well supported: robotics improves engagement and problem-solving (Anwar et al., 2019) and student attitudes toward engineering and technology (Erol et al., 2023), and as project-based learning it succeeds when teachers scaffold investigation and align assessment to project goals (Kokotsaki et al., 2016). Finally, because innovations endure only when they are usable and supported (Century & Cassata, 2016), the toolkit emphasizes clarity, modularity, and built-in feedback.

Unit overview and standards alignment

Over four to six weeks, student teams design, build, wire, program, and demonstrate a servo-driven robotic arm that completes a defined pick-and-place task. The unit integrates the engineering design process, mechanical and electrical systems, programming and control, and technical documentation. Because CTAE standard codes vary by course and are periodically revised, the alignment column names the competency area — insert the exact standard code for your course in each bracket.

A five-week pacing model

This model assumes three 55-minute sessions per week. On block schedules, combine sessions; for a longer unit, extend the Test phase. The pacing front-loads short, structured wins to build early momentum and confidence before students reach the more open-ended programming and testing work.

Facilitation guidance

Launching the project

Open with the design brief and a short demonstration of a working arm so students can see the goal. Establish safety expectations for tools, small parts, and electrical connections before any hardware is distributed. Form teams of three to four and assign rotating roles — design lead, build lead, code lead, documentation lead — so every student engages with each domain over the unit.

Supporting the build and wiring

Distribute the connection map and have teams verify each connection before applying power. Have all servos start from one known, safe position. Circulate with the troubleshooting guide rather than fixing problems directly; guided questioning preserves student ownership while keeping frustration manageable.

Supporting the programming

Introduce the Servo library with the annotated sketch below, then have teams modify angles and timing for their task. Encourage incremental testing — one motion at a time — so errors are easy to isolate.

Build and wiring guide

The reference build uses an Arduino Uno (or compatible board) driving four hobby servos for the base, shoulder, elbow, and gripper. Servos draw more current than the board's onboard regulator can safely supply, so power the servos from a separate 5–6 V supply and connect all grounds together. Pin choices can be changed in code.

Programming guide

This annotated sketch sets a safe starting position and then runs a simple pick-and-place sequence. Students adjust the angles and delays to match their own arm and task.

#include <Servo.h>

Servo baseServo;      // rotates the base
Servo shoulderServo;  // raises/lowers lower arm
Servo elbowServo;     // raises/lowers upper arm
Servo gripperServo;   // opens/closes gripper

void setup() {
  baseServo.attach(3);
  shoulderServo.attach(5);
  elbowServo.attach(6);
  gripperServo.attach(9);
  baseServo.write(90);      // safe start
  shoulderServo.write(90);
  elbowServo.write(90);
  gripperServo.write(20);   // gripper open
}

void loop() {
  baseServo.write(45);      // turn to object
  delay(800);
  shoulderServo.write(120); // reach down
  delay(800);
  gripperServo.write(80);   // close gripper
  delay(800);
  shoulderServo.write(90);  // lift
  delay(800);
  baseServo.write(135);     // turn to drop
  delay(800);
  gripperServo.write(20);   // release
  delay(800);
}

Assessment

The rubric evaluates the four dimensions that matter most for this unit and aligns to the student objectives in Table 2. Because project-based learning depends on assessment that targets project goals rather than compliance (Kokotsaki et al., 2016), each criterion describes observable performance. Share the rubric with students at launch so expectations are transparent.

Engineering portfolio criteria

Each team submits a brief portfolio that includes:

• The design brief and labeled design sketch.
• Photos of the completed build and the connection map used.
• The final program with brief comments explaining the sequence.
• A test log showing at least one problem identified and resolved.
• A short individual reflection connecting the work to the engineering design process.

Troubleshooting guide

These are the issues teams hit most often. Keep this at your side while circulating; students can use it to build independence.

Materials and budget

A starter set for one team. Costs are approximate and vary by supplier. Many programs already own microcontrollers, so per-team costs are often lower. Grippers and frames can be 3D-printed or built from craft materials to reduce cost further.

Using this toolkit in a professional learning community

The toolkit is most effective as an anchor for collaborative learning rather than a solo resource (Darling-Hammond et al., 2017; Vescio et al., 2008). A pathway team can adopt it by co-planning the pacing, teaching the unit in the same window, and meeting once to compare student portfolios and troubleshooting notes.

Robotic arm challenge: your mission

Your team will design, build, wire, and program a robotic arm that can pick up an object and move it to a target zone. Work through each phase, document your progress, and be ready to demonstrate your arm on showcase day.

• Define — Read the design brief and list your requirements.
• Design — Sketch your arm and label each joint and servo.
• Build — Assemble the frame and mount the servos safely.
• Wire — Use the connection map and check every connection before power.
• Program — Start from the sample sketch and adjust angles and timing.
• Test — Run one motion at a time, log problems, and fix them.
• Demonstrate — Show your arm and submit your portfolio.

References

• Anwar, S., Bascou, N. A., Menekse, M., & Kardgar, A. (2019). A systematic review of studies on educational robotics. Journal of Pre-College Engineering Education Research, 9(2), 19–42. https://doi.org/10.7771/2157-9288.1223
• Century, J., & Cassata, A. (2016). Implementation research: Finding common ground on what, how, why, where, and who. Review of Research in Education, 40(1), 169–215. https://doi.org/10.3102/0091732X16665332
• Darling-Hammond, L., Hyler, M. E., & Gardner, M. (2017). Effective teacher professional development. Learning Policy Institute. https://doi.org/10.54300/122.311
• Erol, O., Sevim-Cirak, N., & Başer Gülsoy, Y. G. (2023). The effects of educational robotics activities on students' attitudes towards STEM and ICT courses. International Journal of Technology in Education, 6(2), 203–223. https://doi.org/10.46328/ijte.365
• Ertmer, P. A., & Ottenbreit-Leftwich, A. T. (2010). Teacher technology change: How knowledge, confidence, beliefs, and culture intersect. Journal of Research on Technology in Education, 42(3), 255–284. https://doi.org/10.1080/15391523.2010.10782551
• Knowles, M. S. (1980). The modern practice of adult education: From pedagogy to andragogy (Rev. ed.). Association Press.
• Kokotsaki, D., Menzies, V., & Wiggins, A. (2016). Project-based learning: A review of the literature. Improving Schools, 19(3), 267–277. https://doi.org/10.1177/1365480216659733
• Mishra, P., & Koehler, M. J. (2006). Technological pedagogical content knowledge: A framework for teacher knowledge. Teachers College Record, 108(6), 1017–1054. https://doi.org/10.1111/j.1467-9620.2006.00684.x
• Tschannen-Moran, M., & Woolfolk Hoy, A. (2001). Teacher efficacy: Capturing an elusive construct. Teaching and Teacher Education, 17(7), 783–805. https://doi.org/10.1016/S0742-051X(01)00036-1
• Vescio, V., Ross, D., & Adams, A. (2008). A review of research on the impact of professional learning communities on teaching practice and student learning. Teaching and Teacher Education, 24(1), 80–91. https://doi.org/10.1016/j.tate.2007.01.004