- What the Twelve Content Areas Actually Are
- Domains 1-2: Industrial Robotics Basics and Workplace Safety
- Domains 3-4: Kinematics, Dynamics and Robot Types
- Domains 5-7: Languages, Point-to-Point Programs and Editing
- Domains 8-9: Control Overview and Industrial Applications
- Domains 10-12: Troubleshooting, Calibration and Human-Robot Interaction
- Worked Program Trace: Reading a Pick-and-Place Routine
- Scheduling the Domains Across Your Course
- Testing Mechanics and Requirements
- Frequently Asked Questions
- Fundamentals of Robotics is Festo's Level 1 credential, tested through NC3; the twelve domains here come from Festo's curriculum sheet.
- No official domain weights were verified, so spread study time evenly rather than trusting any invented percentage split.
- Passing requires a score of at least 70%, plus completion of all hands-on labs with an NC3-certified instructor.
- Programming domains (5, 6 and 7) reward tracing real instruction sequences, not memorizing vocabulary.
What the Twelve Content Areas Actually Are
Fundamentals of Robotics (FR) is a Level 1 credential in the Festo Industry Certification Program (FICP). Exams are delivered through the National Coalition of Certification Centers (NC3) by participating schools and training institutions. If you need a broader orientation first, start with What Is FR Certification? and then return here for the content breakdown.
The twelve domains in this guide mirror the topic list on Festo's current Fundamentals of Robotics curriculum sheet. That distinction matters. They are unweighted preparation-curriculum topics, not a published exam blueprint. Neither Festo nor NC3 has released percentage weights that we could verify, so any article claiming "Domain 5 is 18% of the exam" is guessing. This guide does not assign weights. It treats all twelve areas as fair game and tells you what competence in each looks like on the lab floor.
The published learning structure is six units, three labs and three projects. That describes the course, not the exam: it says nothing about question counts or timing. Your instructor's lab sequence is the best map of what you will be asked to do and explain.
Domains 1-2: Industrial Robotics Basics and Workplace Safety
Domain 1: Introduction to industrial robotics
This is the vocabulary and context layer. Expect to explain what makes a machine an industrial robot, how a manipulator differs from fixed automation, and where robots sit in a production cell.
- Core hardware: manipulator arm, controller, teach pendant, power supply and end effector
- Joints, links, axes and degrees of freedom, and how they relate to reach
- Why industry adopts robots: repeatability, throughput, and removing people from hazardous tasks
Domain 2: Robotics and work place safety
Safety is the domain most likely to separate a careful candidate from a careless one, and it shapes how every lab is run. The wording "work place" is retained from the published curriculum.
- Hazard recognition around moving arms, including pinch points, unexpected motion and stored energy
- Guarding, fencing, light curtains and emergency-stop behavior
- Safe procedures when teaching a robot, when only slow, supervised motion is appropriate
- Lockout concepts before maintenance or tool changes
Study Domain 2 alongside Domain 12 later; the two overlap heavily. A question about entering a cell during a teach session is simultaneously a workplace-safety and a human-robot-interaction question.
Domains 3-4: Kinematics, Dynamics and Robot Types
Domain 3: Kinematics and dyanamics of motion and forces in robotic systems
The published sheet spells "dyanamics" with a typo; the subject is the standard study of motion and the forces behind it. At Level 1 the emphasis is conceptual and applied, not heavy calculus.
- Coordinate frames: world, base, tool and user frames, and why position means nothing without a stated frame
- Joint-space versus Cartesian-space motion, and how each shapes the path the tool takes
- Reach, workspace and singularity-style limits on where an arm can go
- Payload, speed and acceleration, and how load and inertia affect accuracy
Domain 4: Familiarization with various robots types
The curriculum retains a deliberately multi-brand scope, so you should be able to compare configurations rather than recite one vendor's catalog.
- Articulated, SCARA, Cartesian (gantry) and delta/parallel configurations
- Where each configuration excels: SCARA for planar assembly, delta for fast light picking, Cartesian for large linear work envelopes
- How axis count and joint type determine flexibility
| Configuration | Motion character | Typical fit |
|---|---|---|
| Articulated | Rotary joints, large flexible workspace | Welding, handling, general-purpose cells |
| SCARA | Compliant in a plane, rigid vertically | Assembly and insertion tasks |
| Cartesian / gantry | Straight-line axes, easy to scale | Pick-and-place across a wide area, machine tending |
| Delta / parallel | Lightweight, very fast | High-speed sorting and packaging of light parts |
Questions here tend to be matching problems: given a task description, pick the configuration that fits. Practice reasoning from the task's demands (speed, payload, reach, orientation freedom) toward the robot, not the other way around.
Domains 5-7: Languages, Point-to-Point Programs and Editing
These three domains form the practical core of the credential. Together they cover how a human tells a robot what to do, and how that instruction gets refined.
Domain 5: Robot programming languages
Robots are programmed through a mix of teach-pendant interfaces, vendor languages and, in some systems, higher-level or graphical environments. You should understand the common building blocks regardless of syntax.
- Motion instructions: linear, joint and circular moves, with speed and termination settings
- Conditional statements: IF/ELSE logic driven by inputs and sensor states
- Loops, counters and wait-for-signal instructions
- Digital inputs and outputs for gripper control and cell handshakes
Domain 6: Point-to-point and task programs
Teaching positions is the signature hands-on skill. A point-to-point program moves between recorded poses; a task program wraps those moves in logic to accomplish something useful.
- Jogging the arm and recording positions, including approach and retreat points
- Why approach points above a part matter for collision avoidance
- Sequencing a pick, a move and a place into one repeatable routine
- Choosing joint moves for speed versus linear moves for controlled paths
Domain 7: Program editing
Real programs are rarely right the first time. Editing means modifying a working routine safely and verifying the change.
- Inserting, deleting and modifying instructions and points
- Adjusting speeds and positions without breaking the surrounding logic
- Testing changes at reduced speed before running at full speed
For extra practice, work through the programming-style scenarios in the FR practice test, which pairs short instruction listings with explained answers.
Domains 8-9: Control Overview and Industrial Applications
Domain 8: Control overview
This domain connects the program to the hardware that executes it, including the supporting competencies that appear throughout the curriculum: control instructions, end effectors and sensor integration.
- The control loop idea: command, motion, feedback and correction
- End effectors: grippers (parallel, angular, vacuum) and when each is suitable for a given part
- Sensors: proximity, photoelectric, vision and force sensing, and how their signals become conditions in a program
- Controller-to-cell communication through I/O signals
Domain 9: Industrial applications
Here the question is always "which robot, tool and program structure fits this job?"
- Material handling, palletizing, machine tending and assembly
- Welding, painting and dispensing as process applications
- Inspection tasks where a sensor or camera decides the next move
- Matching the application's cycle time and precision needs to the robot class
Key Takeaway
When a question names an application, identify the three demands first: payload, speed and precision. Those almost always point to the right configuration and end effector before you read the answer choices.
Domains 10-12: Troubleshooting, Calibration and Human-Robot Interaction
Domain 10: Troubleshooting and maintenance
Troubleshooting questions reward a logical, ordered approach rather than guesswork.
- Separating program faults from hardware, sensor and gripper faults
- Reading alarm and error messages, and checking I/O status first
- Routine maintenance concepts: inspection, lubrication, cable and connector checks, and battery or backup awareness
- Safe restart procedures after a fault
Domain 11: Calibration and accuracy
Learn the difference between terms that sound alike, because they are tested precisely.
- Accuracy: how close the robot gets to a commanded target position
- Repeatability: how consistently it returns to the same position over many cycles
- Tool center point (TCP) definition and why an error there shifts every move
- Why a robot can be highly repeatable yet inaccurate, and how calibration or frame correction addresses it
Domain 12: Human-Robot Interaction
As robots leave fenced cells, interaction design becomes central. This domain builds on Domain 2 and goes further.
- Collaborative workspace concepts and what separates collaborative operation from traditional fenced operation
- Speed and separation monitoring, and force limiting as protective approaches
- Teach-pendant etiquette: enabling devices, who holds the pendant, and who stays outside the cell
- Clear signaling and shared-space rules so people can predict robot behavior
Worked Program Trace: Reading a Pick-and-Place Routine
Candidates often stumble when asked to read a short routine and predict what happens. Practice with a pseudo-code listing like this one (generic, not tied to any vendor's syntax):
- Move to HOME
- Wait until Input 1 (part present) is ON
- Move to APPROACH_PICK
- Move linearly to PICK, close gripper (Output 2 ON)
- Move linearly to APPROACH_PICK
- IF Input 3 (part held) is OFF, jump to step 8; otherwise continue
- Move to PLACE, open gripper (Output 2 OFF), return to HOME
- Raise alarm: part not detected
Trace question: if the gripper closes but the part-held sensor reads OFF, what runs next? The conditional at step 6 routes execution to step 8, so the robot raises the alarm instead of moving to the place point. Notice what the trace tests: Domain 5 (conditionals and I/O), Domain 6 (approach and pick points), Domain 8 (sensor feedback) and Domain 10 (what the fault path tells a technician).
Follow-up: why is step 5 retreating to APPROACH_PICK before testing the sensor? Because lifting the part clear of the fixture confirms the grip is real before committing to a long move, and it avoids dragging the part across the surface. Being able to give that kind of reasoning is exactly what program-editing questions probe.
Scheduling the Domains Across Your Course
This is the one place to think about pacing, and the sequence should follow dependencies between domains rather than generic habits. For deeper pacing advice, see the FR study guide.
Domains 1, 2 and 12
- Safety first, because it governs every lab you will run
- Learn robot anatomy and terminology alongside it
Domains 3, 4 and 8
- Frames, configurations, end effectors and sensors give you the concepts programming depends on
Domains 5, 6 and 7
- Spend the most hands-on time here; trace programs by hand after each lab
Domains 9, 10 and 11
- Apply everything to applications, fault-finding and accuracy scenarios, then review weak areas
Because no official weights exist, avoid skipping a domain on the theory that it is "light." Use mixed practice at the end and let your own results show which areas need more time. To gauge overall difficulty, read How Hard Is the FR Exam?
Testing Mechanics and Requirements
The requirements are straightforward. Students need training from an actively NC3-certified instructor using the required equipment, completion of all hands-on labs, and an exam score of at least 70%. Student recertification is not required. See FR Requirements and FR Passing Score for the full picture.
On cost, NC3 lists a US$0 student certification charge, while training tuition and institutional charges remain separate and vary by school. The FR certification cost breakdown explains how to ask your institution what applies to you.
One scoped example of school-level logistics comes from Virginia's CTE Resource Center: 50 test items, school-administered online delivery, instructor-determined timing, a 70% passing score and no cost per test. Those are Virginia school-testing details, not national rules. Proctoring and open-book or closed-book allowances are set by the school and the specific exam, so confirm them with your instructor. No national written-exam timer or issuer-wide pass rate has been verified; read FR Pass Rate for how to interpret the lack of data, and FR Exam Dates for scheduling through your institution.
On careers, the U.S. Bureau of Labor Statistics reports a US$73,900 May 2025 median annual wage for electro-mechanical and mechatronics technologists and technicians. That is occupational pay for a related field, not a salary attached to this certificate, and it does not prove a pay increase from earning it. For a balanced view, see the FR certification ROI analysis and FR salary guide.
If you are weighing this against a brand-specific option, note that FANUC's certified robot operator credential belongs to a separate FANUC/NOCTI program with its own curriculum and testing specifications. Do not assume your Festo preparation maps onto it, or the reverse. Ready to test yourself? Work through domain-by-domain questions on the FR practice test and compare results against the topics above.
Frequently Asked Questions
No. They are twelve unweighted topics from Festo's Fundamentals of Robotics curriculum sheet. No official percentage weights were verified, so treat all twelve as testable and avoid any source that claims exact weightings.
The curriculum covers various robot types and brands, so you need transferable concepts such as motion types, I/O, conditionals and end effectors rather than one vendor's syntax. Your instructor's lab equipment will show you one real implementation.
With no verified weights, none should be skipped. Many candidates find the programming trio (Domains 5, 6 and 7) the most demanding, and safety (Domains 2 and 12) the most consequential, so give those extra hands-on attention.
No. Simulation and offline programming are useful supplements, but the credential requires completing all hands-on labs on the required equipment with an NC3-certified instructor.
You need at least 70%. NC3 lists a US$0 student certification charge, though training tuition and institutional charges are separate and set by your school. Confirm timing and proctoring rules with your instructor.