Learning Targets
- Use ==, !=, <, >, <=, and >=
- Evaluate Boolean expressions
- Connect comparisons to manufacturing decisions
Comparison operators and True/False conditions in automation.
Use ==, !=, <, >, <=, and >= Evaluate Boolean expressions Connect comparisons to manufacturing decisions
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 comparison asks a yes/no question and produces either True or False. Automation programs use these results to decide what should happen next.
Use == to compare values. A single = assigns a value to a variable.
Comparisons can represent inspection limits, destinations, production counts, or other Workcell conditions.
Read every line and predict what the program would do before opening the practice check.
part_height = 48
max_height = 50
part_ok = part_height <= max_height
print(part_ok)Rule: If you missed more than one question, reread Learn It and trace the example again before continuing.
What value prints? What would print if part_height were 53?
Do first: Write your answer in your engineering notebook.
The program first prints True. If part_height is 53, it prints False.
Find and correct every error before opening the answer.
destination = 2
if destination = 2:
print("Pallet 2")Use == in the comparison: if destination == 2:.
Add a minimum acceptable height and create a Boolean expression that checks whether the part is within both limits.
Evidence: Paste the revised code into your engineering notebook.
Create a variable named destination and a comparison that is True only when the part should go to Pallet 1.
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.