Before anything else, confirm whether the X-axis problem belongs to the Fagor controller, the axis drive, the motor-feedback circuit, or the machine mechanics. Replacing the controller before isolating that fault can preserve the same failure while adding an unresolved drive-interface problem.
Retrofit Path Comparison
| Approach | Best fit | Primary requirement | Main risk |
|---|---|---|---|
| Repair the existing Fagor system | The fault is confined to the X axis and the remaining control functions operate correctly | Controller diagnostics, wiring information, and axis substitution tests | Repairing the wrong subsystem because the controller is blamed before the drive, feedback, and mechanics are tested |
| Retain the Fagor drives and install MASSO | Every required drive accepts a command and enable interface that MASSO can provide | Electrical and functional interface documentation for both products | Command, feedback, enable, fault, or spindle-orientation incompatibility |
| Replace the controller and drives | The existing drive interfaces are undocumented, proprietary, damaged, or incompatible | New drives matched to the installed motors and feedback devices | Greater rewiring, motor-feedback compatibility work, and commissioning scope |
Start with fault isolation, then evaluate retaining the drives. This sequence preserves the least invasive repair option and produces the measurements needed for a defensible retrofit decision. Do not move on to controller selection until the command, feedback, enable, ready, fault, and safety interfaces are identified for every axis and the spindle.
Controller-to-Drive Compatibility
A motion controller does not communicate with a servo drive merely because both can control an axis. Compatibility requires matching the complete control architecture. The controller must issue the command format accepted by the drive, satisfy its enable sequence, receive usable status signals, and coordinate the feedback loop at the correct layer.
| Interface | Question to answer | Acceptance test |
|---|---|---|
| Motion command | Does the drive require an analog command, pulse-and-direction signals, or a digital network? | The MASSO hardware documentation lists the same output method and electrical levels. |
| Feedback | Does feedback terminate at the drive, the controller, or both? | Position and direction remain correct through a slow commanded move and an externally measured displacement. |
| Enable and status | What states enable the drive, and how are ready and fault conditions reported? | The drive cannot energize unexpectedly, and removing permission stops motion through the intended control path. |
| Limits and homing | Are switches wired to the controller, a drive, or another machine circuit? | Each input changes state at the correct physical device and in the correct direction. |
| Spindle functions | Can the replacement system command speed, run direction, orientation, and any position feedback needed for indexing? | Each required function is demonstrated independently before rigid tapping is attempted. |
The DMG 35M Ultrasonic is described as a 3+2 machine, but that label does not define whether all five axes interpolate simultaneously or how the rotary axes are clamped and enabled. Read the machine wiring and control configuration to identify those behaviors. A controller that handles basic three-axis motion may still be unsuitable if it cannot reproduce the rotary-axis or spindle sequence.
Retrofit Prerequisites
- Record the controller, drive, motor, feedback-device, spindle-drive, and I/O module nameplate data. Photograph each connector before disturbing the wiring.
- Obtain the Fagor drive manuals and the documentation for the exact MASSO hardware under consideration. Locate connector pinouts, command types, signal levels, feedback formats, and enable logic.
- Trace the X-axis command, enable, feedback, limit, home, brake, ready, and fault conductors. Label both ends rather than relying on wire color.
- Create an I/O list for all axes, the spindle, lubrication, coolant, clamps, tool functions, and the safety chain. Mark whether each signal is an input, output, analog channel, pulse signal, or network connection.
- Define required machine functions before selecting the retrofit scope. Include X-axis closed-loop motion, the two additional axes, spindle indexing, and rigid tapping if those capabilities are required.
Do not use successful closed-loop stepper operation on a Bridgeport Interact 1 as proof that the Fagor servos or drives will interface with MASSO. That installation uses a different motion architecture. Compatibility must be established from the DMG hardware interfaces.
X-Axis Fault Isolation
- Lock out machine power and inspect the X-axis motor, coupling, screw, guides, feedback cable, drive wiring, and connectors. Correct mechanical binding, contamination, loose connections, or cable damage before applying motion commands.
- Read the controller and drive diagnostics without clearing them. Record the displayed fault text or code, the operating state that triggers it, and whether it occurs at power-up, enable, homing, or commanded motion.
- Compare X-axis status with a working axis. Check enable state, ready state, position feedback, limit inputs, commanded position, following behavior, and drive fault indication. Use the difference to select the next test.
- With power isolated, perform continuity and shield checks on the command and feedback paths using the machine diagrams. Do not megohm-test connected electronics or feedback devices.
- Where the hardware documentation permits substitution, exchange one known-compatible element at a time between X and a working axis. Move only cables or modules explicitly identified as interchangeable. If the symptom follows the exchanged element, investigate that element; if it remains on X, investigate the stationary wiring, mechanics, and controller channel.
- Measure the controller command and drive response during a restricted low-speed test. A changing command with no drive response points toward the enable path, drive, motor, or power stage. No command despite a valid motion request points toward controller logic, limits, interlocks, configuration, or the controller output channel.
- Verify feedback polarity and direction before allowing normal travel. Stop immediately if commanded motion and reported position diverge, because positive feedback can produce uncontrolled acceleration.
MASSO Integration Procedure
- Build a signal-by-signal compatibility matrix from the two manufacturers' documents. Mark an interface compatible only when command type, voltage or current range, polarity, reference, timing, and connector function all match.
- Bench-test one drive interface with the motor mechanically unloaded where practical. Include enable, disable, command direction, feedback direction, ready indication, and fault response. Do not connect the remaining axes until the first channel behaves predictably.
- Configure travel direction, feedback direction, homing direction, and limits for one axis. Use reduced speed and acceleration during initial motion. Confirm measured travel against reported travel before increasing performance.
- Repeat the same controlled commissioning sequence for each linear and rotary axis. Test any brake or clamp sequence before commanding the associated axis.
- Commission the spindle as a separate subsystem. Prove start, stop, direction, and speed control first; then prove spindle position feedback and orientation. Attempt indexing or rigid tapping only after the controller receives the feedback those functions require.
- Integrate auxiliary and safety-related signals only from the traced machine circuit. Test loss of drive-ready, activation of limits, controller stop requests, and removal of operating permission without relying on software motion commands alone.
Commissioning Verification
- Power-cycle the system and confirm that no axis or spindle moves during startup.
- Home one axis at a time, checking switch state, approach direction, repeatability, and available travel.
- Command positive and negative incremental moves, then compare displayed displacement with an independent measurement.
- Run each axis through its usable travel at restricted speed while monitoring cables, mechanics, feedback, drive status, and following behavior.
- Test coordinated linear motion before introducing the two additional axes. Verify rotary direction, clamp state, and position independently before combined moves.
- Remove each relevant permission or activate each protective input individually. Confirm that motion stops through the intended circuit and that restart requires the intended reset sequence.
Frequently Asked Questions
How do I know whether MASSO can control the Fagor drives?
Match the documented drive command, enable, status, and feedback interfaces against the exact MASSO hardware. A compatible motion-command input alone is insufficient if the enable sequence, electrical levels, or feedback architecture differ.
How do I determine whether the X-axis fault is in the controller or drive?
Compare X-axis commands and status with a working axis, then substitute only documented interchangeable components one at a time. A fault that follows a component identifies that path; a fault that remains on X directs attention to its wiring, mechanics, feedback, or controller channel.
How do I retain rigid tapping after a controller retrofit?
Confirm that the spindle system provides the position feedback required by the replacement controller and that the controller can command and verify spindle orientation. Prove speed control, feedback direction, position reporting, and orientation before testing rigid tapping.
How do I verify the retrofit before running a part?
Power-cycle without unexpected motion, home each axis separately, compare commanded travel with an independent measurement, and test every limit and operating-permission path. Finish by running restricted-speed coordinated motion and confirming correct direction, position, clamp state, and drive status on all commanded axes.