🚧 Under construction — VoTechWorks is being built. A free tech program — complimentary, as our commitment to get America working.
voTechWorksGrade 13 · a vocational technology learning center, by urbanicity
newSchoolWorks.com › VoTechWorks › Manufacturing & Marine › Robotics / Mechatronics › Troubleshooting Mechatronic and Robotic Systems › Lesson 9
MFG-MECH15-07 · Lesson 9 · 18 clock hours · lab

Systematic Multi-System Fault Isolation on an Integrated Machine

Objective. Students will isolate and correct a fault in an integrated mechatronic system where the symptom is in one subsystem (e.g., robot stops) but the root cause is in a different subsystem (e.g., pneumatic gripper pressure loss), using the seven-step process and full documentation.

⚠ Pending professional review

This lesson, its worked examples and its practice questions has not yet been verified by a licensed engineer or certified journey-level tradesperson or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.

VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.

Systematic Multi-System Fault Isolation on an Integrated Machine

Why Faults Migrate Across Subsystems

An integrated mechatronic cell links several subsystems — a PLC, a conveyor driven by a variable-frequency drive (VFD), a pneumatic pick station, and a FANUC robot — into one coordinated machine. Because these subsystems exchange signals constantly, a failure in one subsystem almost always shows up as a symptom somewhere else. This is called cross-system fault migration.

A classic example: the pneumatic gripper loses pressure because a solenoid coil wire is loose. The robot closes the gripper, picks up a part, and carries it toward the conveyor. The part slips and falls. The robot program detects a missing part confirmation signal, throws a fault alarm, and stops. A technician who looks only at the robot alarm screen will chase the wrong system. The root cause is electrical — a loose wire at the solenoid — but the symptom appeared as a robot program abort.

Understanding this pattern before you touch anything is the single most important skill in integrated-system troubleshooting.

The Seven-Step Fault Isolation Process

Apply these steps in order. Skipping steps wastes time and can introduce new faults.

1. Recognize and define the symptom. Record exactly what the machine is doing and not doing. Note any alarm codes on the FANUC teach pendant, the PLC HMI, or the VFD display.

2. Establish a baseline. Confirm the machine was operating correctly before the fault. Review the last successful cycle, recent maintenance, and any recent changes to settings or hardware.

3. List all possible causes. Think across every subsystem. A robot timeout could trace to a slow conveyor (VFD), a missed sensor (electrical), low air pressure (pneumatic), or a bad PLC output signal. Build a cause-and-effect map before touching anything.

4. Prioritize tests from most likely to least likely. Use your cause-and-effect map. Start with the subsystem that feeds the signal or motion that is missing.

5. Test and measure — one change at a time. Record the actual value versus the expected value for every test. A pressure gauge, multimeter, or PLC I/O monitor reading without a written record is wasted work.

6. Identify and repair the root cause. Fix the actual cause, not the symptom. Replacing a robot I/O card when the real problem is a loose solenoid wire wastes money and time.

7. Verify the repair. Run the machine through at least one full automatic cycle. Confirm all alarms are cleared, all signals are normal, and the cell operates as designed.

Reading the Signal Flow

Before testing, trace the signal flow for the affected function. In a PLC-controlled cell, digital outputs from the PLC energize solenoid valves and relay coils. Sensors send digital or analog inputs back to the PLC. The PLC then sends permissive signals to the FANUC robot over a hardwired I/O connection or a network. The robot responds and sends status signals back.

When a robot shows a timeout fault, ask: What signal was the robot waiting for? Check the robot I/O screen on the teach pendant — it shows the current state of every digital input. If the expected input never went high, the fault is upstream of the robot. Then check the PLC output that drives that input. If the PLC output is commanded ON but the robot input is OFF, the fault is in the wiring between them. If the PLC output is not commanded ON, look at why the PLC logic is holding it off — often a sensor or interlock condition.

Pneumatic and Pressure Faults

Pneumatic faults produce force and speed symptoms. A gripper that closes slowly or incompletely may indicate low supply pressure, a partially closed isolation valve, a clogged flow control, or a worn cylinder seal. Always measure pressure at the point of use, not just at the compressor outlet. A significant pressure drop between the supply manifold and the cylinder suggests a restriction or leak in that branch.

NFPA 79 requires that pneumatic and hydraulic circuits on industrial machinery have clearly labeled isolation points. Before disconnecting any pneumatic fitting, isolate and exhaust the circuit following your site's lockout/tagout procedure under OSHA 29 CFR 1910.147.

Safety Requirements for This Lab

This lab involves live electrical circuits, moving machinery, and a robot. You must follow every rule below before beginning any test.

Documenting Your Work

Your work-order form is not optional paperwork — it is your proof of a systematic process. Record the symptom, every test performed, the actual versus expected value for each measurement, your reasoning for the next test, the root cause found, the repair made, and the verification result. A work order that shows random probing without logic will not meet the 80% rubric standard for this lab.

Key terms10

Cross-system fault migrationA condition in which the root cause of a failure exists in one subsystem but the visible symptom appears in a different subsystem, requiring the technician to trace signal and energy flow across system boundaries.
Cause-and-effect mapA diagram drawn before testing that lists all subsystems contributing to a function and maps how a failure in each one could produce the observed symptom; used to prioritize test sequence.
Signal flowThe path a command or feedback signal takes from its source (sensor, PLC output, robot I/O) through wiring and devices to its destination; tracing signal flow is the foundation of systematic electrical troubleshooting.
PLC I/O monitorA software view in PLC programming software or the HMI that displays the real-time ON/OFF or analog value of every input and output channel, used to confirm whether a signal is present at the controller level.
VFD overload tripA protective shutdown triggered by a variable-frequency drive when motor current exceeds the programmed overload threshold for a set time; the drive latches a fault and removes power from the motor until the fault is reset.
Permissive signalA digital input to the robot controller (or PLC) that must be ON before a programmed motion or output action is allowed to execute; missing permissives are a common cause of robot timeout faults in integrated cells.
Root causeThe original, underlying failure that initiated the fault chain, as distinguished from downstream symptoms; a correct repair addresses only the root cause.
Pressure dropThe difference in pneumatic or hydraulic pressure measured between two points in a circuit; an abnormally large drop between supply and point-of-use indicates a restriction, leak, or partially closed valve in that branch.
ANSI/RIA R15.06The US industrial robot safety standard (aligned with ISO 10218) governing safeguarding, work-envelope protection, collaborative robot operation, and required safe practices when working in or near a robot cell.
Verification runA complete automatic machine cycle performed after a repair is made to confirm that the root cause is corrected, all alarms are cleared, and the machine performs its intended function without new faults.

Worked examples4

1. A pressure gauge at the gripper cylinder inlet reads 42 psi during actuation. The cylinder specification requires 60 psi minimum to generate adequate gripping force. The main supply manifold reads 90 psi. Calculate the pressure drop across the branch and determine whether the branch loss alone explains the shortfall.
  1. Step 1 — Identify measured values: supply manifold = 90 psi; cylinder inlet during actuation = 42 psi.
  2. Step 2 — Calculate branch pressure drop: drop = 90 psi − 42 psi = 48 psi.
  3. Step 3 — Compare cylinder inlet to requirement: 42 psi available vs. 60 psi required; shortfall = 60 − 42 = 18 psi below minimum.
  4. Step 4 — Interpret: A 48 psi drop in a short pneumatic branch is abnormally high and fully explains the gripping failure. Likely causes are a clogged flow control, a kinked hose, or a partially closed ball valve in that branch. Isolate, exhaust, and inspect the branch before reconnecting.
Answer: Branch pressure drop = 48 psi; cylinder inlet is 18 psi below the 60 psi minimum, confirming the branch restriction is the root cause of inadequate gripper force.
2. While troubleshooting a conveyor that is running slower than expected, you measure motor speed as 1,455 RPM. The conveyor motor is a 4-pole, 60 Hz induction motor. Calculate synchronous speed and percent slip.
  1. Step 1 — Calculate synchronous speed using Ns = 120 × f / P: Ns = 120 × 60 / 4 = 7,200 / 4 = 1,800 RPM.
  2. Step 2 — Calculate slip RPM: slip RPM = 1,800 − 1,455 = 345 RPM.
  3. Step 3 — Calculate percent slip: slip % = (345 / 1,800) × 100 = 19.2%.
  4. Step 4 — Interpret: Normal full-load slip for a standard induction motor is roughly 2–5%. At 19.2% slip the motor is heavily loaded or is experiencing a mechanical restriction on the conveyor. Check for a mechanical jam or excessive load before resetting the VFD overload fault.
Answer: Synchronous speed = 1,800 RPM; slip = 345 RPM; percent slip ≈ 19.2%, which is far above normal and indicates an overload or mechanical restriction.
3. A 4–20 mA analog sensor sends a signal to the PLC analog input card to report conveyor belt tension. The card is configured for 4–20 mA = 0–500 lb. Your multimeter reads 11.2 mA on the signal wire. What tension value should the PLC be displaying?
  1. Step 1 — Determine the span of the mA signal: 20 − 4 = 16 mA represents the full span.
  2. Step 2 — Determine the position of 11.2 mA within the span: 11.2 − 4 = 7.2 mA above the live-zero.
  3. Step 3 — Calculate the fraction of span: 7.2 / 16 = 0.45 (45%).
  4. Step 4 — Apply fraction to the engineering-unit span: 0.45 × 500 lb = 225 lb.
  5. Step 5 — Verify: PLC display should read 225 lb. If the display shows a different value, the scaling parameters in the PLC analog input block are configured incorrectly.
Answer: The PLC should display 225 lb. A mismatch between this expected value and the actual display points to an analog scaling error in the PLC configuration.
4. A pneumatic cylinder with a bore diameter of 2.0 inches must clamp a workpiece. Available supply pressure is 80 psi. Calculate the theoretical clamping force on the extend stroke.
  1. Step 1 — Calculate the piston area: radius = 2.0 / 2 = 1.0 inch; area = π × r² = 3.1416 × 1.0² ≈ 3.14 in².
  2. Step 2 — Apply the cylinder force formula: Force = pressure × area = 80 psi × 3.14 in² = 251.2 lb.
  3. Step 3 — Interpret: The cylinder can produce approximately 251 lb of theoretical clamping force at 80 psi. Actual force will be slightly less due to friction and seal losses. If the part is slipping during clamping, compare this theoretical value to the required clamping force in the machine specification.
Answer: Theoretical clamping force ≈ 251 lb at 80 psi. If the application requires more force, pressure must be increased (within safe system limits) or a larger-bore cylinder must be used.

The math in this lesson2

Learners scale a mA reading to belt tension on a 0–500 lb range and compute motor slip.
F-LE.1G-MG.2
Brush up in the math halls at newSchoolWorks.com:
In class: Pre-lab briefing: instructor explains the concept of cross-system fault migration — how a hydraulic or pneumatic failure manifests as a robot alarm, how a sensor fault creates a PLC output fault, and how a drive trip stops a conveyor that is monitored by a robot cell; students sketch a cause-and-effect map for three given symptom-root-cause pairs. · Integrated lab: the training cell (PLC-controlled conveyor + pneumatic pick station + FANUC robot) has one seeded cross-system fault per lab group from a pool of six scenarios (examples: blocked sensor causes PLC to not release conveyor, which causes robot to fault on timeout; gripper solenoid wiring loose causes robot to drop part and abort program; VFD overload on conveyor motor causes PLC to halt entire cell); each group follows the seven-step process, documents every test, and makes the repair. · Group debrief: each group presents their fault, test sequence, key measurement that bracketed the fault, and the lesson learned about where to start testing on an integrated system; class votes on whether the group's process was systematic or random and discusses improvements.
Materials: Integrated training cell (PLC, conveyor with VFD, pneumatic pick station, FANUC robot), multimeter, pressure gauge, PLC programming laptop, teach pendant, work-order forms, fault-scenario instructor cards, ANSI/RIA R15.06 safeguarding checklist
Check: Work order and verbal debrief: work order must show a logical test sequence (not random probing), each measurement recorded with actual vs. expected value, correct root cause identified, repair verified with a successful auto cycle; group debrief must show understanding of why the fault appeared in a different subsystem; 80% rubric to pass.

Practice check8

Answer each question, then check it. Nothing is recorded; this is your own practice.

FANUC CERT / PLC troubleshooting
1. A FANUC robot displays a timeout fault while waiting for a part-in-place confirmation. The robot I/O screen shows the expected digital input is OFF. The PLC I/O monitor shows the corresponding output is commanded ON. What does this evidence most directly indicate?
Safety / OSHA 29 CFR 1910.147
2. Before disconnecting a pneumatic fitting on a pressurized gripper circuit to inspect for a restriction, which safety requirement must be completed first?
PMMI Mechatronics / Motor and Motor Controls
3. A conveyor motor trips the VFD on an overload fault shortly after starting. Using the seven-step fault isolation process, what should the technician do BEFORE resetting the VFD and restarting?
Safety / ANSI/RIA R15.06
4. Which standard governs safeguarding and safe work practices specifically for industrial robots, including rules about entering a robot work envelope during troubleshooting?
Siemens Mechatronics L1 / Troubleshooting methodology
5. During a lab debrief, Group A explains that they started troubleshooting the robot alarm code, then checked the PLC, then checked the pneumatic pressure. Group B explains they first built a cause-and-effect map for all three subsystems, identified the pneumatic branch as most likely, measured pressure at the cylinder, found low pressure, and traced it to a blocked flow control. Which group demonstrated a more systematic process, and why?
PMMI Mechatronics / Motor and Motor Controls
6. A 4-pole, 60 Hz induction motor driving a conveyor measures 1,710 RPM under load. What is the percent slip?
PMMI Mechatronics / Industrial Electricity / PLC analog
7. A 4–20 mA pressure transmitter is scaled to 0–150 psi in the PLC. During a fault investigation you measure 8 mA on the signal wire. What pressure should the PLC be displaying?
Safety / Troubleshooting verification
8. A technician repairs a loose solenoid wire that was causing the robot gripper to drop parts. Before returning the cell to automatic production, what must be done to confirm the repair is complete?
Record this lesson on my transcript. Sign in with your key and enrollment email to record lessons (enroll free if you have no key). This page stays open to read and practise.
← Previous lessonProgram planNext lesson →