LockwoodSTEMStudent Engineering Hub
ADM Python P.1

Reading Workcell Python

Program order, comments, method calls, and predicting robot behavior.

Begin Self-Guided LessonCrash Course Home

Your lesson guide

Objective

Read Python from top to bottom Identify comments and method calls Predict the order of Workcell actions

Materials

For the online work: a browser and your engineering notebook. Follow the activity’s materials list for any physical build, and get teacher approval before using equipment.

Plan your time

Suggested work block: 45–60 minutes. Physical builds and projects may span several classes; follow your teacher’s schedule.

Learning Targets

  • Read Python from top to bottom
  • Identify comments and method calls
  • Predict the order of Workcell actions

How to Use This Page

  1. Read the short lesson.
  2. Attempt every Practice Check before revealing the answer.
  3. Complete Predict It and Fix It by tracing and correcting code.
  4. Complete Modify It and Program It by writing Workcell-style Python code.
  5. Use the Mastery Check before moving to the next lesson.
Learn It

Python Idea + Workcell Connection

Python normally executes one line at a time from top to bottom. A line beginning with # is a comment for humans; it does not command the robot.

A command such as arm.move_to(100, 150, 120) calls a method on the configured arm. The numbers are arguments that tell the method where to move.

Trace the commands in order and translate each line into the physical action it would represent.

Worked Example

Trace This Code

Read every line and predict what the program would do before opening the practice check.

# Move above the pickup point
arm.move_to(100, 150, 120)

# Move down to the part
arm.move_to(100, 150, 45)

# Pick up the part
arm.set_end_effector_magnet(True)

# Lift the part
arm.move_to(100, 150, 120)
Practice Check A

Check Your Understanding

  1. Does the first comment move the robot?

    Check Answer

    No. Comments are ignored by Python.

  2. Which line turns on the magnet?

    Check Answer

    arm.set_end_effector_magnet(True)

  3. What is the robot's last movement?

    Check Answer

    It moves back to (100, 150, 120).

Rule: If you missed more than one question, reread Learn It and trace the example again before continuing.

1 · Predict It

Trace the Code

Number the four robot actions in the order they occur. What would change if the final movement command were deleted?

Do first: Write your answer in your engineering notebook.

Reveal Self-Check

The arm moves above the part, lowers, turns on the magnet, then lifts. Without the last movement command, the arm would remain at the pickup height after the magnet turns on.

2 · Fix It

Debug the Program

Find and correct every error before opening the answer.

arm.move_to(100, 150, 120)
arm.set_end_effector_magnet(True
arm.move_to(100, 150, 45)
Reveal Debugging Check

Add the missing closing parenthesis. Also consider sequence: if the intent is to pick up the part, the arm should normally lower before activating the magnet.

3 · Modify It

Change Working Code

Change the program so the arm moves above the part, lowers to the part, turns the magnet on, and then lifts the part.

Success Check

  • Your code is syntactically correct.
  • The change affects only the intended Workcell behavior.
  • You can explain what changed and why.

Evidence: Paste the revised code into your engineering notebook.

4 · Program It

Build It Yourself

Write a short Workcell sequence that moves to a safe point, approaches a pickup point, activates the magnet, and returns to the safe point.

Before You Finish

  • Trace the code once by hand.
  • Check variable names, colons, parentheses, and indentation.
  • Verify that the coordinates and logic match the written scenario.
  • Add useful comments.
Interactive Practice

Python Practice Lab

Edit the code, predict the output, then click Run Code. No physical Workcell is connected.

Browser Python

P.1 Practice

Ready
Output / Errors
Predict what the code will do, then click Run Code.

Tip: Press Ctrl+Enter (Cmd+Enter on Mac) to run. The mock arm object prints simulated Workcell actions instead of controlling hardware.

Practice Check B

Explain Your Code

Without looking back at Learn It, answer these in your notebook:

  1. What Python structure or idea did you use?
  2. What Workcell behavior would this code represent?
  3. What mistake would cause the code to behave incorrectly?
What a Strong Response Includes

A strong response names the Python idea accurately, connects it to a specific Workcell action or decision, and identifies a realistic syntax or logic error from this lesson.

Mastery Gate

Ready for the Next Lesson?

  • □ I can identify comments versus commands.
  • □ I can trace Workcell code in order.
  • □ I can explain what each method call makes the robot do.

Move on only when you can check every statement. If one is still uncertain, revisit the worked example or redo Fix It before continuing.

Command Reference

VEX Workcell Python API

Use the official VEX API only as a programming reference to verify method names and parameters. The examples use the configured arm name arm. No physical Workcell is required.

Open EXP Workcell Arm API
← PreviousNext Lesson →

Build your lesson report

Checkpoint: is your evidence ready?
  • Check calculations, units, labels, and measurements against the activity requirements.
  • Record what actually happened, including unexpected results.
  • Explain what you changed and why; attach required drawings, photos, CAD, or code in your classroom assignment.

Submit the evidence specified in the activity and your classroom assignment. The report below collects your notes, calculations, observations, and reflections; attach any required drawings, photos, CAD, or code separately.

A PDF download is not a submission. Review it, then upload it and any required attachments through your classroom assignment system.