DIY Integration Case · Canada
A recurring Y-axis dual-drive servo alarm was eliminated after a focused three-month troubleshooting process. The case involved a non-standard belt-and-rack transmission, two 750W Leadshine servos and an XC3000 control system. The final breakthrough came when remote motion testing revealed incorrect and incomplete dual-drive parameter settings.
Case at a glance
- Customer location: Canada
- Machine: DIY plate-and-tube fiber laser cutter
- Y-axis drive: Belt-and-rack hybrid with dual 750W Leadshine servos
- Control system: XC3000 host + EDS3000 controller
- Main symptom: Repeated Y-axis servo alarm after cutting cycles
- Resolution: Dual-drive direction and configuration parameters corrected remotely
The Challenge: A Persistent Dual-Drive Alarm
A Canadian DIY customer integrated a fiber laser cutting kit purchased from AlleriaStore into a custom plate-and-tube machine. Unlike a typical rack-and-pinion Y axis, this build used a belt-and-rack hybrid transmission with two servo motors. The arrangement introduced additional vibration sensitivity and made synchronization errors more difficult to isolate.
During the focused troubleshooting period from March to June 2026, the Y-axis dual-drive system repeatedly triggered servo alarms after cutting cycles. Adjustments to pulse-equivalent values, servo gains, belt tension and alarm tolerance produced partial changes, but none removed the problem.
Why this case was difficult: the mechanical vibration did not act alone. It amplified a software-configuration mismatch, causing the investigation to move repeatedly between mechanical and control-system causes.
How the Problem Was Diagnosed
Phase 1: Mechanical and Servo Checks
The first stage focused on the most common causes of a dual-drive alarm: pulse-equivalent accuracy, servo gain, belt tension, backlash and synchronization. The Y-axis pulse setting was iteratively adjusted from approximately 55.48 to 55.67, while Leadshine Pr003 and Pr004 parameters were also tested.
These changes affected vibration and motion behavior but did not eliminate the alarm. The team also confirmed that the controller's easy-tuning function was intended for rack-and-pinion transmission and was not suitable as an automatic solution for this belt-driven configuration.
Phase 2: Motion Accuracy and Alarm-Tolerance Tests
The team then used a 100 mm marking test to establish a motion-accuracy baseline and continued reviewing the mechanical parameters. Increasing the alarm-tolerance setting from 0.3 to 0.5 also failed to stop the recurring alarm.
This result was important: simply widening the tolerance could not compensate for an underlying dual-drive configuration error.
Phase 3: Dedicated Remote Motion Testing
On June 24, the team scheduled a dedicated remote session and connected to the customer's computer. Instead of changing more values by message, the technician asked the customer to move the X and Y axes separately in 500 mm increments while the relevant settings and operating response were reviewed in real time.
This systematic comparison exposed two control-side issues: one critical direction setting was incorrect and should have been set to 0, while a second required configuration item had not been set correctly. Together, they created a persistent synchronization deviation between the two Y-axis drives.
Root Cause: Parameter Direction Plus Belt Sensitivity
The alarm was not caused by one isolated mechanical defect. It resulted from the interaction of three factors:
- Incorrect direction setting: a critical dual-drive parameter used the wrong direction value.
- Incomplete configuration: another required control item was not correctly configured.
- Mechanical amplification: vibration in the belt-driven system magnified the synchronization error until it exceeded the allowable range.
Earlier adjustments changed the system's behavior, but they did not correct the control logic creating the mismatch. The dedicated remote session made it possible to compare axis movement and configuration together rather than treating the mechanical and software systems separately.
The Solution and Immediate Result
The technician corrected the direction parameter to 0 and completed the missing configuration. The recurring alarm stopped immediately, and the Y axis returned to normal motion during the remote test.
Customer feedback: “It looks like it's working now after months.” The customer later added, “You are my hero.”
At the time recorded in the case notes, the alarm had been eliminated and normal axis operation had been restored. A later cutting test was still pending, so this case confirms resolution of the servo-alarm condition rather than long-term production performance.
Five Lessons for DIY Integrators
- Treat belt-driven dual-servo systems as high-sensitivity configurations. Small parameter deviations may be amplified by belt vibration.
- Check direction values as carefully as numerical values. A correct magnitude with the wrong direction can still create a persistent synchronization error.
- Do not use higher alarm tolerance as the main fix. A wider tolerance may hide symptoms without correcting the source of the mismatch.
- Use dedicated remote motion tests for complex faults. Separate, controlled X- and Y-axis movements can reveal issues that screenshots and messages miss.
- Confirm whether automatic tuning matches the transmission type. A tuning function designed for rack-and-pinion systems may not be suitable for a belt-driven axis.
Commissioning Checklist for a Dual-Drive Y Axis
- Verify that the two servo drives use matching parameters where required.
- Confirm master-slave synchronization, motor direction and encoder direction before cutting.
- Check belt tension, backlash, pulley ratios and mechanical alignment.
- Run measured single-axis moves and compare commanded travel with actual travel.
- Record every parameter change with screenshots and the reason for the change.
- Prepare a stable wired network connection if remote commissioning support is required.
Frequently Asked Questions
What caused the Y-axis dual-drive servo alarm?
The immediate control-side causes were an incorrect direction parameter and a second configuration item that had not been set correctly. Belt-drive vibration amplified the resulting synchronization deviation.
Why did changing the servo parameters not solve the problem?
Gain and tolerance changes affected vibration and alarm behavior, but they did not correct the underlying direction and synchronization configuration.
Can easy tuning be used for this type of Y-axis drive?
According to the project notes, the easy-tuning function used in this case was intended for rack-and-pinion transmission. The non-standard belt-driven system required manual parameter review and testing.
Was the machine fully production-verified after the repair?
The remote session confirmed that the alarm was eliminated and the axis was operating normally. The available case record states that a later cutting test was still pending, so long-term cutting performance is not claimed here.
What information should be prepared before requesting support?
Provide the controller and drive models, software version, transmission ratios, motor and encoder directions, pulse-equivalent settings, alarm history, parameter screenshots and videos of controlled axis movements.
Need Help With a DIY Fiber Laser Integration?
Send us your controller model, servo-drive model, transmission details, alarm codes and parameter screenshots. Our team can review the configuration and help identify the next troubleshooting step.
This article documents one customer integration case based on supplied troubleshooting records and screenshots. Parameter values shown here are case-specific and should not be copied directly to another machine. Servo tuning and dual-drive configuration depend on the controller, drive, motor, transmission, mechanical structure and safety requirements. Back up the original parameters and consult the relevant equipment manuals or a qualified technician before making changes.
