ABB RobotWare 3.2 can illuminate the motor-on lamp without producing motion because the lamp reports permission in one part of the control chain, not confirmed torque at the joints. The number that matters is commanded motor current after all safety, configuration, drive, brake, and feedback checks have passed. With no reported error code, the first action is to capture diagnostics, not repeat the installation.
Motion permission versus joint torque
A stationary robot with the motor lamp on has passed at least part of the enable sequence. Motion still requires a valid motion configuration, an accepted operating command, healthy drive channels, released brakes, usable position feedback, and a closed safety path. Any failed condition can hold commanded current at zero or inhibit a joint even while the visible motor indication remains on.
This is current, timing, and heat, not just logic. A drive must establish controlled current at the requested time without exceeding electrical or thermal limits. A configuration that assigns the wrong manipulator data, motor data, feedback relationship, or drive hardware can prevent that controlled current from being applied.
| Quantity or state | Required result | Where to read it |
|---|---|---|
| Active fault or warning | No motion-inhibiting event | Controller event or diagnostic display |
| Motion command | Jog or program command accepted | Teach pendant status and event history |
| Safety chain | Motion permission remains active during the command | Safety and operating-state indications |
| Drive state | All configured axes ready | Drive diagnostics |
| Joint feedback | Valid position data for every configured axis | Axis or motion diagnostics |
| Motor current | Controlled current appears when motion is requested | Drive monitor or service diagnostics |
| Thermal condition | No motor or drive temperature inhibit | Diagnostic buffer and drive status |
Controller and manipulator identity
The cabinet has no nameplate. Its visible code is 3HAC 2841-1/02, and it contains DSQC373, DSQC323, and DSQC361 boards. It was identified locally as S4C rather than S4C+, with M98 suspected from the cabinet hardware. The manipulator marking identifies an M97 IRB 6400 2.4/120.
Those observations are useful inventory data, but none individually defines the complete system configuration. A cabinet identifier, board population, manipulator designation, installed RobotWare release, motor data, and option set describe different layers. M97 on the arm and a suspected M98 cabinet classification therefore require a compatibility check; silently forcing either interpretation can build a system that starts normally but blocks motion.
The decisive records are the complete manipulator plate, cabinet identity records, installed system configuration, and diagnostic events generated when a move is requested. ABB support can use 3HAC 2841-1/02 and the board inventory to identify hardware, but the code should not be treated as a substitute for the missing nameplate.
Recovery approaches and selection
| Approach | Use when | Diagnostic value | Primary risk |
|---|---|---|---|
| Reinstall RobotWare 3.2 immediately | The installation media or system files are demonstrably damaged | Low if the same selections are repeated | Erases the state needed to identify a selection error |
| Correct the existing system configuration | The controller boots, motors can be enabled, and motion alone is inhibited | High; preserves current alarms and selected data | Requires accurate hardware and manipulator identification |
| Restore a known matching system or backup | A verified backup belongs to this controller-manipulator combination | High when provenance is known | A backup from another robot can reproduce or create a mismatch |
| Obtain ABB identification support | The cabinet plate is missing or compatibility remains ambiguous | Highest for undocumented hardware | Requires complete photographs, codes, and diagnostic records |
Correcting the existing configuration is the preferred first path because the controller reaches motor-on state. Preserve the current event history, establish the exact identity of both halves, and compare that identity with the installed motion configuration. Restore or reinstall only after that comparison identifies a wrong or damaged system.
Diagnostic decision path
- Record every active and historical error before cycling power or rebuilding the system. Include the exact event code, full text, affected axis, and whether it appears at startup, motor-on, or the first jog request.
- Confirm the operating mode and use the normal permitted jogging sequence. Observe whether the motor-on indication stays active when the move is requested. A dropped indication directs diagnosis toward the safety or enable chain; a steady indication with a new event directs it toward motion configuration, feedback, brakes, or drives.
- Inspect the manipulator plate and record the full designation. Use
IRB 6400 2.4/120only if that is the complete plate selection required by the installation utility; do not infer missing configuration fields from the payload and reach notation. - Inventory the controller without interpreting board numbers as software selections. Record
3HAC 2841-1/02,DSQC373,DSQC323, andDSQC361, plus every other readable cabinet and drive identifier. - Compare the installed manipulator, axis, drive, and option configuration with the physical robot. Look for an incorrect robot variant, axis count, drive assignment, or system option. Read exact identifiers from the existing configuration rather than substituting a nearby model.
- Check axis diagnostics while requesting a small permitted jog. Determine whether all axes report valid position feedback, whether brakes release, and whether a drive-ready state changes. The first state that fails separates a configuration inhibit from a power-stage or mechanical problem.
Configuration correction procedure
- Create a recoverable copy of the current system and diagnostic records.
- Resolve the cabinet identity through documented labels or ABB records. Treat the S4C classification and M98 assessment as working hypotheses until the hardware code is identified.
- Resolve the arm identity from its complete plate. Retain the explicit M97 and
IRB 6400 2.4/120markings in the service record. - Build or select a RobotWare 3.2 system whose controller hardware, manipulator variant, axis arrangement, and installed options match the physical equipment. Do not change several uncertain selections at once; each change should answer a recorded mismatch.
- Load the corrected system using the approved installation process, then review startup diagnostics before enabling motors.
- Apply the required calibration or position-reference data from records belonging to this robot. Incorrect or missing axis reference data requires correction before automatic motion.
- Test in the permitted manual mode at a conservative commanded speed, with personnel outside the robot’s reachable space. Begin with a small single-axis request and watch the corresponding feedback and drive state.
Verification and recurring pitfalls
A successful repair produces more than a lit motor lamp. Each requested joint must move in the commanded direction, feedback must change smoothly for that joint, the motor-on state must remain active, and no new motion, drive, feedback, or thermal event may enter the diagnostic buffer. Repeat the test for every configured axis before program execution.
The recurring mistakes are selecting a nearby manipulator variant, treating cabinet generation and manipulator revision as one identifier, interpreting a board number as proof of the entire controller configuration, and reinstalling before recording errors. Another common trap is declaring the controller healthy because motor-on works. That indication does not verify brake release, axis mapping, feedback validity, or torque-producing current.
Frequently asked questions
Why does ABB RobotWare 3.2 show motors on but the robot will not move?
Motor-on indicates partial enable permission, not confirmed joint torque. Read the event history while issuing a jog command and check safety permission, axis-ready state, brakes, feedback, and the installed manipulator configuration.
Why does an M97 IRB 6400 need a controller identity check?
The arm is marked M97 IRB 6400 2.4/120, while the unidentified cabinet was suspected to be M98. Verify both identities independently and select a configuration approved for that exact pairing.
Why are DSQC board numbers not enough to select RobotWare options?
DSQC373, DSQC323, and DSQC361 document installed boards, but they do not define the manipulator variant, complete drive arrangement, or option set by themselves. Compare the full hardware inventory with the existing system configuration.
Why should I record error codes before reinstalling RobotWare 3.2?
The event code and its timing identify which enable stage failed. Reinstallation can remove the diagnostic state while repeating the same incorrect selection.
When should I stop troubleshooting and contact ABB support?
Stop if the cabinet cannot be identified from documented markings, the M97/M98 compatibility remains unresolved, calibration records are missing, or a drive, brake, feedback, or thermal fault persists after configuration checks. Contact official ABB support with 3HAC 2841-1/02, the complete manipulator plate, board inventory, RobotWare 3.2 system details, and exact event codes; keep the robot out of service until the configuration and motion safety are verified.