Skip to content

Repository files navigation

Project 3: FANUC CRX Collaborative Robot Programming

Due: Wednesday, March 11 at 11:50 AM
Location: ALIC @ Bessemer (FANUC CRX Educational Cell)


Table of Contents


Overview

In this project, you will work with a FANUC CRX collaborative robot and its Tablet TP. You have already covered the introductory slides and completed a simulated preparation activity. This project begins with a brief orientation — safe startup, jogging, and manual guided movement — then moves quickly into programming, testing, and pick-and-place.

Because we have 19 students and 5 robots, teams will be larger than usual, so this project includes explicit role rotation and peer/self-evaluation to keep everyone engaged and accountable.


Learning Outcomes

By completing this project, you will be able to:

  1. Identify major components of a FANUC collaborative robot cell and explain their roles
    Fulfills Course Learning Outcome 1
  2. Operate the robot safely in teach mode (TP enabled) using the Tablet TP, jogging controls, and manual guided movement
    Fulfills Course Learning Outcome 4
  3. Create, test, and revise a basic robot program using taught positions and motion commands
    Fulfills Course Learning Outcome 2
  4. Implement a simple pick-and-place task using a gripper and approach/retreat logic
    Fulfills Course Learning Outcome 2
  5. Debug robot motion by adjusting points, speeds, and sequencing during program verification
    Fulfills Course Learning Outcome 2
  6. Explain how collaborative robot safety differs from ordinary manual or non-collaborative automation
    Fulfills Course Learning Outcome 5
  7. Document robot behavior, team decisions, and testing results in a clear engineering record
    Fulfills Course Learning Outcome 2

Team Structure

  • Team Size: approximately 4 students per robot
  • Team Formation: teams are assigned by the instructor
  • Shared Constraint: only one student can actively manipulate the pendant at a time, so turn-taking is required
  • Individual Accountability: every student must complete hands-on robot actions and document their contributions
  • Evaluation: team product, peer/self-evaluation, and documented contributions determine the final grade

Required turn-taking

Since only one person can operate the Tablet TP at a time, your team must rotate roles every 10–15 minutes during each session. Use a timer or let the Safety Monitor call switches.

Roles (rotate through all of them each session):

Role Responsibilities
Pendant Operator Holds and operates the Tablet TP; performs jogging, touch-up, and program execution
Safety Monitor Watches robot motion, workspace clearance, and team positioning; has authority to call stop immediately
Recorder Takes notes on taught points, parameter choices, errors, and successes; captures photos/video
Spotter / Analyst Reads the program timeline and checks whether planned motion matches actual behavior; suggests edits

If your team has only three members, combine Recorder and Spotter. With four members, all roles should be distinct.

Tip: In your reflection, record who held which role and when. This is how individual contribution is verified.

Minimum participation requirements

Each student must personally do all of the following at least once:

  • Observe all three movement methods and personally perform at least one during Part 1
  • Touch up or record at least one robot position during Part 2 or Part 3
  • Operate the pendant during at least one program test run
  • Contribute to the written reflection

Students who do not participate hands-on should expect a grade penalty even if the team program works.


Hardware and Software

Hardware

  • FANUC CRX 10iA collaborative robot (max payload 10 kg, reach 1249 mm)
  • CRX Controller: R30iB Mini Plus
  • Tablet Teach Pendant (Tablet TP): Android-based touch-screen controller
  • SCHUNK EGP 64 Gripper: Fully electronic gripper — max gripping weight 1.25 kg, 10 mm stroke per jaw, standard opening 44 mm. 3D-printed gripper fingers.
  • Welded steel table with payload and palletizing board (pickup spots and circular placement spots)
  • Trace board for shape-tracing programs
  • 3D-printed pointer and pointer holder (used for tracing exercises)
  • Pick-and-place objects provided in lab

Software / Interface

  • FANUC Tablet Teach Pendant interface (timeline-based programming)
  • Existing Home program available on the robot
  • Gripper plugin (Android-based, compatible with CRX Tablet TP)

Project Structure

You will complete three parts. Each part builds on the previous one — Part 1 is orientation, Part 2 is movement programming, and Part 3 adds pick-and-place using the gripper.

Part 1: Safety, Startup, and Manual Operation

See part1-manual-operation.md for full details, including startup steps, visual references, required evidence, and checkpoint questions.

Part 2: Create and Run a Movement Program

See part2-movement.md for full details, including minimum requirements, recommended sequence, visual references, required evidence, and checkpoint questions.

Part 3: Pick-and-Place Program

See part3-pick-and-place.md for full details, including minimum requirements, programming ideas, design advice, visual references, required evidence, and success threshold.


Assessment

Total: 10 points (part of 40 points for all projects)

Your grade = Team Product Score − Contribution Penalty

Team Product (10 points)

All team members start with the same team product score.

Part 1: Safety and Manual Operation (1.5 points)

  • Each member observed all three movement methods; each member personally performed at least one
  • Reflection questions for Part 1 answered clearly

Part 2: Shape-Tracing Programs (3.0 points)

  • At least two shape programs created and tested (straight-edged + circle)
  • Loop modification implemented and team can explain the choice
  • Reflection describes positions, revisions, loop design, and design choices

Part 3: Pick-and-Place Program (3.5 points)

  • Program performs a pick-and-place cycle (or reaches substantial partial completion)
  • Payload changes handled correctly
  • Reflection describes approach/retreat strategy, gripper settings, and what was adjusted

Documentation and Reflection (2.0 points)

  • Reflection completed thoroughly with all sections filled in
  • Role rotation log filled in for each session

Peer Evaluation & Contribution Penalty (0 to −10 points)

After calculating the team product score, a penalty may be applied based on peer evaluations and contribution evidence.

Penalty determined by:

  • Peer evaluation feedback (hands-on participation, collaboration, reliability)
  • Role rotation log in the reflection (did you actually take turns?)
  • Self-reflection quality and alignment with peer feedback

Penalty levels:

Peer Review Avg Penalty Description
4.5–5.0 None (0 pts) Excellent participation and peer reviews
3.5–4.4 −0.5 to −1 Good reviews, minor concerns
2.5–3.4 −1.5 to −3 Adequate reviews, limited hands-on work
1.5–2.4 −4 to −7 Poor reviews, minimal participation
< 1.5 −8 to −10 Very poor reviews, non-participation

Team Evaluation Process

Each student will individually complete the Self & Team Evaluation Form.

Part 1: Peer Evaluation

For each teammate (including yourself), rate on a scale of 1–5:

  1. Hands-on Participation: Did they actively operate the robot, or just observe?
  2. Work Quality: Did they put genuine effort into understanding and completing each part?
  3. Collaboration: Were they engaged in discussion, willing to help debug, and supportive?
  4. Contribution: Did they contribute a fair share of programming, testing, and documentation?
  5. Reliability: Did they attend all sessions and follow through on commitments?

Part 2: Self-Reflection

  • List which parts you personally operated the pendant for
  • List which roles you held and when (reference your role rotation log)
  • Rate your own participation honestly (1–5)
  • Note any circumstances that affected your ability to contribute

Resources

Primary class resources


Submission Instructions

Deadlines

Submit via your team GitHub repository by Wednesday, March 11 at 11:50 AM.

Each team member must also complete the peer and self-evaluation form by the same deadline.

What to submit

  1. Reflection

    • writing/reflection.md — completed with all sections
  2. Part 2 evidence

    • Video of each shape program running (one per shape — two total), or live in-class demo
    • Video of your loop modification running, or live in-class demo
    • Screenshot of each program timeline
  3. Part 3 evidence

    • Video of pick-and-place program running, or live in-class demo
    • Screenshot of program timeline
  4. Peer and self-evaluation (each student individually)


Academic Integrity

  • Collaboration: Work within your team, but do not copy another team's robot program or documentation
  • External resources: If you use online tutorials or documentation, cite them in the reflection
  • LLM usage: If you use ChatGPT, Copilot, or another AI tool, describe what you asked and how you used the response
  • Responsibility: You must understand and be able to explain any program structure, motion plan, or terminology included in your submission

About

Starter project 3

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors