AGV Servo Motor Commissioning: Common Setup and Tuning Issues

A servo motor that performs perfectly on a test bench can behave very differently once it is bolted into an AGV chassis, connected to a real gearbox and wheel, and asked to move a loaded vehicle across a warehouse floor. Most of the problems that appear at this stage are not motor defects — they are commissioning issues. A phase wired in the wrong order, a missing bus terminator, an encoder cable routed alongside a motor power line, or a gain value tuned on an empty vehicle will all produce symptoms that look like hardware faults but are entirely correctable in setup. This guide walks through AGV servo motor commissioning in the order it should actually be performed, and explains what the most common symptoms are telling you.

Why Commissioning Deserves a Defined Sequence

Commissioning is often treated as an informal step between installation and testing, handled differently by whoever happens to be doing it. That informality is where most avoidable problems originate. Skipping a pre-power check to save fifteen minutes can mean discovering a wiring error only after the motor has already tried to drive a loaded vehicle into a rack. Tuning gains before verifying encoder feedback means tuning against a signal that may be wrong in the first place.

A defined sequence matters because each stage depends on the one before it. Parameter setup is meaningless if the wiring is wrong. Gain tuning is meaningless if the parameters do not match the motor. Load testing is meaningless if the vehicle cannot yet hold a straight line unloaded. Working in order isolates each variable, so when something does go wrong, the cause is narrowed to whatever changed most recently rather than the entire system at once.

Pre-Power Checks Before First Motion

Everything in this stage happens before the drive is enabled. It is the cheapest stage to be thorough in, and the most expensive stage to rush.

Power Wiring and Phase Order

Verify motor phase connections against the drive terminal labeling before applying power. A brushless servo motor with two phases swapped will not simply run backwards — depending on the drive's commutation method, it may fail to produce usable torque, draw excessive current, or run away uncontrolled when enabled. Confirm supply polarity as well, since reversed DC input can damage the drive immediately on power-up.

Encoder Cable Routing and Shielding

Encoder feedback is a low-voltage signal running near high-current switching electronics, which makes it the most noise-sensitive connection in the system. Route encoder cables physically separated from motor power cables rather than bundled alongside them, use shielded cable, and ground the shield at one end only. Grounding a shield at both ends can create a ground loop that injects more noise than it blocks. Symptoms of encoder noise are distinctive: position counts that drift without motion, intermittent following-error alarms, or velocity feedback that shows ripple when the motor is mechanically still.

Fieldbus Termination and Grounding

On a CAN-based system, the bus requires a 120-ohm terminating resistor at each physical end of the network — not one, and not one at every node. A bus missing a terminator will often still communicate during bench testing at short cable lengths and low speeds, then become intermittent once installed in a full-length chassis harness. This is one of the most time-consuming faults to diagnose precisely because it does not fail cleanly. Verify termination physically rather than assuming it, and confirm that all devices share a common ground reference.

Mechanical Verification

Before enabling the drive, confirm that the motor shaft turns freely by hand where the design allows, that the gearbox is correctly coupled without axial preload on the motor bearing, and that mounting fasteners are torqued. If the motor includes a holding brake, verify that the brake releases and engages audibly before it is asked to hold a real load.

Initial Parameter Setup

With wiring verified, the next stage is loading a parameter set that matches the actual hardware. Many commissioning problems trace back to a drive running with default parameters intended for a different motor.

Motor and Drive Matching

Set the motor's rated current, peak current limit, rated speed, and pole pair count to match the motor actually installed. The current limit deserves particular attention on AGV applications: set too high, it allows the drive to push the motor past its thermal rating during a stall event such as a wheel jammed against an obstacle; set too low, the vehicle will trip on overcurrent during normal acceleration under full payload.

Encoder Configuration

Configure the encoder type and resolution to match the feedback device in the motor. An incremental encoder configured at the wrong pulse count will produce velocity and position values scaled incorrectly, which typically appears as a vehicle that travels a different distance than commanded. On systems using absolute feedback, confirm that the commutation offset has been correctly established, since an incorrect offset produces weak torque and elevated current draw at all speeds.

Communication Address and Baud Rate

Every node on the bus needs a unique address and a matching baud rate. Duplicate node addresses are common when multiple identical drives are installed from the same configuration, and the resulting symptom — one or both nodes dropping off the bus intermittently — is easily mistaken for a cabling fault. Confirm addresses are unique before connecting all nodes to the same bus rather than after.

Motion Limits and Ramps

Set maximum velocity, acceleration, and deceleration limits conservatively for the first tests. Commissioning is not the time to run at design speed. Reduced limits make it possible to observe behavior and stop safely if something is wrong, and they can be raised incrementally once stable motion is confirmed.

First Motion Test

The first enable should happen with the drive wheel off the ground or the vehicle safely blocked, never with the vehicle free to move on the floor.

Direction and No-Load Rotation

Command a low velocity and confirm the motor rotates in the expected direction. If direction is inverted, correct it in the drive parameter rather than by rewiring phases, which keeps the wiring consistent with documentation for future service.

Encoder Feedback Verification

Compare commanded velocity against reported feedback velocity. They should track closely at steady state. A feedback value that is consistently a fixed multiple of the command usually indicates an encoder resolution mismatch. Feedback that is noisy or unstable at constant speed points back to encoder wiring or shielding.

Brake Sequencing

For motors with a holding brake, verify the timing relationship between brake release and torque enable. The brake must fully release before motion is commanded, and must engage only after the motor has come to a stop and torque is still applied. Releasing the brake too late causes the drive to push against a locked shaft and trip; engaging it too early causes the brake to absorb motion energy it was never designed to absorb, wearing it out prematurely.

Tuning the Control Loops

Tuning is where commissioning becomes iterative. The objective is not maximum stiffness but stable, repeatable motion across the vehicle's full operating range.

Velocity Loop

Begin with the velocity loop, since the position loop sits above it and cannot behave well over an unstable velocity loop. Increase proportional gain gradually until the motor holds commanded speed with minimal error, then introduce integral gain to eliminate steady-state offset. Increase in small steps and observe after each change.

Position Loop and Following Error

Once velocity response is stable, tune the position loop for acceptable following error — the difference between commanded and actual position during motion. Some following error is normal and expected during acceleration. What matters is that it returns to near zero at steady state and settles quickly at the end of a move without extended oscillation.

Recognizing Excessive Versus Insufficient Gain

Excessive gain announces itself audibly and physically: a high-pitched whine from the motor at standstill, visible vibration in the chassis, or oscillation that grows rather than settles when the vehicle stops. Insufficient gain looks like sluggish response to speed changes, large following error during acceleration, slow settling at stopping points, and on some systems a low-speed crawl or stick-slip behavior where the vehicle moves in small increments rather than smoothly.

Between these two failure modes there is a usable range rather than a single correct value. For AGV applications, erring slightly toward the lower end of that range generally produces smoother, quieter operation at the cost of marginally slower response, which is usually the right tradeoff in a shared human-robot environment.

Retuning Under Real Load

Gains tuned on an unloaded vehicle will rarely remain correct once payload is added. Added mass changes the effective inertia the motor sees, which changes the system's response to the same gain values. Always repeat tuning verification at the vehicle's expected working payload, and ideally at both minimum and maximum payload if the range is wide. A system tuned only at one extreme may oscillate at the other.

When Tuning Cannot Fix the Problem

Some instability is not a tuning problem at all. If the ratio between reflected load inertia and motor rotor inertia is too high, no combination of gain values will produce both responsive and stable behavior — raising gain causes oscillation, lowering it causes sluggishness, and there is no usable setting between them. The fix at that point is not in the drive parameters but in the selection: a motor with higher rotor inertia, or a different gear ratio that reduces reflected inertia at the motor shaft.

Mechanical resonance is a related case. If a specific speed range produces vibration that other speeds do not, the cause is usually a structural or drivetrain resonance being excited rather than a gain error. Many drives provide a notch filter to suppress a narrow frequency band, but the more durable fix is addressing the mechanical stiffness or coupling that is resonating.

Commissioning a Differential Drive Pair

Vehicles using two independently driven wheels introduce a requirement that single-axis commissioning does not: the two sides must behave identically, not merely acceptably.

Tune both drives to matching gain values rather than tuning each independently to its own optimum. Two axes individually tuned to slightly different response characteristics will track a straight-line command differently, and the vehicle will arc away from its intended path. After tuning, run a straight-line test over the longest available distance and measure lateral deviation at the end — this reveals mismatches that are invisible over short moves. Also verify that wheel diameter and wheelbase values configured in the controller match the physical vehicle, since errors in these geometric parameters produce heading drift that no amount of drive tuning can correct.

Repeat the same check for in-place rotation. A vehicle that rotates cleanly around its own center has matched wheel speeds; one that drifts laterally while rotating does not.

Common Commissioning Faults and What They Indicate

Most fault codes encountered during commissioning fall into a small number of categories, each with a characteristic set of causes.

Overcurrent during acceleration usually indicates a current limit set too low for the actual payload, a gain setting causing the drive to fight itself, or genuine mechanical binding in the drivetrain. Check whether the fault occurs at a repeatable point in the motion profile — a consistent trigger point suggests a parameter issue, while a random one suggests a mechanical or electrical intermittent.

Overvoltage during deceleration is specific to battery-powered vehicles and frequently surprises engineers commissioning their first AGV. When the vehicle decelerates, the motor acts as a generator and pushes energy back toward the DC bus. If the battery cannot absorb it quickly enough, bus voltage rises until the drive trips protectively. Softening the deceleration ramp reduces the regenerated power; where aggressive braking is a functional requirement, a braking resistor may be needed to dissipate it.

Overtemperature that appears only after extended running points to duty cycle or thermal environment rather than an immediate setup error — a motor sized for intermittent duty being run continuously, or a chassis with insufficient ventilation around the drive.

Encoder alarms and communication timeouts almost always return to the wiring and termination issues covered in the pre-power stage, which is precisely why those checks are worth doing carefully the first time. A broader treatment of drive-level faults and their root causes is available in this guide to common AGV servo drive problems.

FAQ

How long does commissioning an AGV servo motor typically take?

It varies with how much is already known about the configuration. A repeat build using a proven parameter set can be commissioned quickly, while a first prototype with new motors, a new gearbox ratio, and an unfamiliar controller can take considerably longer, with most of the time spent on tuning iterations rather than initial setup.

Can I copy tuning parameters from one vehicle to another?

Yes, provided the vehicles are mechanically identical — same motor, gearbox ratio, wheel diameter, chassis mass, and payload range. Copying parameters between vehicles that differ in any of these will produce a starting point rather than a finished tune, and the result should still be verified under load.

Why does my AGV run smoothly unloaded but oscillate when loaded?

Added payload increases the effective inertia the motor must control, which changes system response to the same gain values. This is normal and is why tuning should always be verified at working payload. If oscillation persists across all reasonable gain settings under load, the issue is more likely inertia matching in the original motor selection than tuning.

What should I check first if the motor will not enable at all?

Work backward through the enable chain: supply voltage present and within range, emergency stop circuit closed, safe torque off inputs satisfied, drive enable signal received, and no active fault latched from a previous attempt. A drive that will not enable is usually being correctly prevented from enabling by something upstream rather than failing itself.

Does encoder type affect the commissioning process?

Yes. Incremental feedback typically requires a homing routine to establish a position reference after each power cycle, while absolute feedback retains position through power loss and skips that step, though it requires correct commutation offset configuration during initial setup. The tradeoffs between the two are covered in more detail in this guide to AGV drive motor encoder selection.

Conclusion

AGV servo motor commissioning goes wrong in predictable ways, and nearly all of them are preventable by working through the stages in order rather than jumping to tuning when something misbehaves. Verify wiring and termination before power, load parameters that match the actual hardware, confirm feedback before trusting it, and tune under the load the vehicle will actually carry. When a system resists tuning entirely, recognize that as a selection or mechanical issue rather than continuing to adjust gains. Commissioning done carefully once produces a parameter set that can be reused across a production fleet; commissioning done hastily produces problems that surface later in the field, where they are far more expensive to diagnose.