Learning Targets
- Create and update variables
- Use variables inside Workcell commands
- Explain why variables make automation flexible
Variables for coordinates, speeds, counters, and destinations.
Create and update variables Use variables inside Workcell commands Explain why variables make automation flexible
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.
Suggested work block: 45–60 minutes. Physical builds and projects may span several classes; follow your teacher’s schedule.
A variable is a named storage location. Instead of repeating a coordinate such as 100 throughout a program, you can store it as pickup_x = 100.
Variables make Workcell programs easier to change. If a pickup location moves, you update the variable once instead of editing every motion command.
Python variable names are case-sensitive: pickup_x and pickupX are different names.
Read every line and predict what the program would do before opening the practice check.
pickup_x = 100
pickup_y = 150
pickup_z = 45
arm.move_to(pickup_x, pickup_y, 120)
arm.move_to(pickup_x, pickup_y, pickup_z)
arm.set_end_effector_magnet(True)Rule: If you missed more than one question, reread Learn It and trace the example again before continuing.
If pickup_x changes from 100 to 140, which movements change?
Do first: Write your answer in your engineering notebook.
Both arm.move_to commands change their x-coordinate from 100 to 140.
Find and correct every error before opening the answer.
pickup_x = 100
pickup_y = 150
pickup_z = 45
arm.move_to(pickupX, pickup_y, pickup_z)Change pickupX to pickup_x. The original name is the variable that was defined.
Add a variable named safe_z and use it instead of typing the safe height directly.
Evidence: Paste the revised code into your engineering notebook.
Create variables for one pickup location and one pallet location, then use those variables in arm movement commands.
Edit the code, predict the output, then click Run Code. No physical Workcell is connected.
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.
Without looking back at Learn It, answer these in your notebook:
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.
Move on only when you can check every statement. If one is still uncertain, revisit the worked example or redo Fix It before continuing.
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.
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.