Troubleshooting and Commissioning

Commissioning is the controlled process of proving that a machine is wired, configured, calibrated, and safe enough to operate. Troubleshooting is the disciplined process of finding why reality does not match the design. Both are engineering activities, not guesswork.

Learning Objectives

By the end of this lesson, you should be able to plan a staged bring-up, verify sensors and actuators before full motion, isolate mechanical/electrical/software faults, record commissioning evidence, and avoid unsafe debugging habits.

Commissioning Sequence

Start with the lowest-energy checks and move toward full operation only when each gate passes.

flowchart TD A[Documentation review] --> B[Mechanical inspection] B --> C[Wiring and polarity checks] C --> D[Power rails without actuators] D --> E[Controller I/O checks] E --> F[Sensor calibration] F --> G[Low-speed actuator jog] G --> H[Closed-loop tuning] H --> I[Fault and safety tests] I --> J[Production acceptance]

Do not skip early gates because the software "should" handle it. A reversed motor phase, loose coupling, wrong encoder count, or swapped limit switch can damage hardware before software diagnostics react.

Pre-Power Inspection

Before energizing:

compare wiring against the schematic and terminal plan;
verify protective earth and enclosure bonding;
check fuses, breaker ratings, and power-supply voltage selection;
confirm connectors are keyed, locked, and strain-relieved;
inspect belts, gears, couplings, guards, and travel limits;
verify emergency stop and interlock wiring continuity;
remove tools, loose hardware, and shipping locks.

For stored-energy systems, release or secure springs, elevated loads, pneumatics, hydraulics, and charged capacitors before hands-on work.

First Power-Up

Use current limiting, fused supplies, or staged enabling where possible. Keep actuators disabled until logic rails and I/O states are verified.

Recommended checks:

supply voltage and ripple at the controller and driver;
idle current compared with expected values;
regulator and driver temperature after a few minutes;
sensor raw readings before calibration;
digital input polarity and pull-up/pull-down behavior;
output state at reset and during firmware download.

Fault Isolation Method

Good troubleshooting changes one variable at a time. Split the system into layers:

Layer	Typical fault	Test
Mechanical	Binding, backlash, loose coupling	Hand move, dial indicator, torque check
Power	Brownout, blown fuse, voltage drop	DMM, scope, load test
Sensor	Wrong polarity, noise, misalignment	Raw reading, known target
Actuator	Wrong direction, overcurrent	Low-current jog
Control	Bad gain, unstable loop	Step response and logs
Software	State bug, race, timeout	Trace, simulation, unit test

If a symptom crosses layers, test the boundary. For example, command a motor driver input while measuring the driver output and shaft movement.

Useful Measurements

Record measurements with units and conditions:

supply voltage at idle and peak load;
motor current during acceleration and steady motion;
encoder counts per revolution or millimeter;
limit-switch transition points;
sensor calibration slope and offset;
closed-loop overshoot and settling time;
thermal rise after a representative duty cycle.

Common Failure Symptoms

Axis moves the wrong way: swapped motor leads, inverted command sign, encoder direction mismatch.
Controller resets during motion: supply sag, shared ground bounce, inadequate decoupling, EMI.
Position loop oscillates: excessive gain, loose mechanics, wrong encoder scale, low sample rate.
Sensor works by hand but not in machine: alignment, ambient light, cable noise, target material.
Random faults: intermittent connector, cable fatigue, race condition, missing shield termination.

Debugging Guidance

Use logs, trend plots, and checklists. Label every change with time and reason. If a fix is found by swapping parts, still identify the underlying mechanism before release.

For motion systems, start with reduced speed, reduced current, soft limits, and one hand near the emergency stop. Never bypass guards or interlocks for convenience; use a documented maintenance mode with reduced risk.

Acceptance Record

A commissioning record should include:

machine serial number or build ID;
firmware and configuration versions;
passed inspection checklist;
calibration values;
safety and fault-test results;
measured performance against requirements;
open issues and owner;
sign-off date.

Summary

Commissioning proves that a machine is ready for service. Troubleshooting finds faults by isolating layers, measuring evidence, and changing one variable at a time. The best commissioning work leaves a record that another engineer can trust.

Mind Map

mindmap root((Commissioning)) Core concept Prove readiness Troubleshoot by layers Record evidence Calculations Voltage drop Current margin Counts per unit Settling time Applications Robot axis Conveyor Test stand CNC machine Design rules Stage power up Disable actuators first One change at time Keep safety active Practical checks Wiring polarity Sensor raw values Low speed jog Fault tests Common mistakes Full power too soon No records Bypassed interlocks Guessing faults