Hello everyone, I am facing an issue with my servo motor and I'm puzzled as to why it is not functioning properly. Even without a gearbox or any load attached to the motor, it trips out due to excessive velocity error when a jog command is sent to it. The torque reference spikes up significantly, exceeding the limit and causing the motor to halt, leading to a velocity error and eventual fault. What confuses me is that during the motor and feedback test, it runs smoothly but faults when MAM/MAJ commands are sent. Can anyone shed light on why this is happening? I have gone through the knowledge base and checked all the wiring, ensuring it is correctly connected to the drive. Has anyone encountered this issue before and can suggest a solution for the sudden increase in torque reference? Any other troubleshooting tips I should consider? Could it be as simple as a faulty motor that needs replacing?
Are you able to provide a screenshot of your MAM/MAJ settings (expanded)? Based on my limited experience, I would suggest focusing on tuning up within the MAM/MAJ parameters. My first step would be to delete the existing axis and create a new one with default parameters. Simply input the motor's catalog number, utilize the motion direct command to move it at a very slow speed, and avoid making changes to any other parameters. This simple process can help optimize your MAM/MAJ settings effectively.
In my experience, Siemens servos can be prone to issues when the gain or other parameters are set too high for a no-load situation compared to when a load is applied. This discrepancy in settings can result in malfunctions.
dmroeder asked for a screenshot of the MAM/MAJ parameters. In my limited experience, tuning is crucial in the MAM/MAJ settings. A good starting point would be to delete the axis, create a new one with default parameters, input the motor catalog number, use a motion direct command to move it at a slow speed. Avoid changing any other parameters at this stage. I have tried using an MAJ of 5 units per second in the motion direct command, with default settings for the rest of the MAJ. I plan on tuning it further once I confirm that it is functioning properly.
Maxkling explained that he has encountered issues with Siemens servos in the past due to parameters being set too high for when a load is not applied. This problem persists even with the gearbox attached and in mesh with the rack. Interestingly, another machine on site using the same motor and gearbox with identical parameters functions without any issues.
Do you know what type of drive/motor platform your system is using? It's important to note that during a feedback test, the system does not utilize the feedback for control purposes. Any issues with the feedback will not impact the motor during the test, but they will affect the motor during regular operation. It seems like there may be a mismatch between the feedback and motor rotation. After conducting a feedback test, does the system indicate a successful test completion?Keith
Hey there, it sounds like you've done some solid troubleshooting already. One possibility that comes to mind is that your motor might be trying to accelerate too quickly. This could explain why your torque reference is spiking and causing a velocity error - the motor simply can't handle the rapid change in speed. You could try adjusting your acceleration settings to see if that alleviates the issue. Another possibility could be related to your servo drive's tuning settings, not all motors are compatible with default tuning parameters, so modification might be necessary. As a last resort, it could indeed be a faulty motor. But I'd exhaust all other options first before going down that route. It might also be helpful to consult with a servomotor expert or the manufacturer if problems persist. Good luck!
Hey there, it definitely sounds like a frustrating problem. One possible issue might be with your servo drive configuration. If your motor is configured with the wrong parameters on the drive side, it may cause the kind of issues you're seeing. You need to make sure your motor characteristics (like rated torque, motor speed, etc.) are correctly set in the drive parameters. If the drive sees an abnormality, it could be incorrectly interpreting this as an error and halting operation. Another possible reason could be the PID settings, fine-tuning them might rectify your jog command issue. If you've covered these areas, then it may be a mechanical issue, perhaps a faulty encoder. Consider getting a motor technician to give it a once-over before you consider replacing the entire motor.
Your issue could possibly be due to feedback problems, incorrect tuning, or a fault between your motor and its controller. Although the motor seems to run fine during testing, real-time commands might introduce additional system dynamics that aren't captured in a static test. Also, it's worth considering if there might be a potential damage to the encoder. If you haven't done so already, I'd encourage you to run some diagnostic tests on your feedback device to ensure it's properly functioning. Also, check the tuning parameters- it could be that the motor is overreacting to error because of excessive gain. However, if everything else fails, a replacement might be necessary.
It sounds like you’ve already done a thorough job checking your setup! The issue you’re experiencing could be related to the tuning parameters of your servo drive. Sometimes, if the proportional or integral gains are set too high, it can cause the motor to become overly reactive, resulting in those torque spikes when commands are applied. It might be worth revisiting the tuning or even resetting it to factory defaults to see if that resolves the issue. Also, double-check your command signal for any noise or interference that might be contributing to the problem. Good luck, and keep us posted on what you find!
It sounds like you're dealing with a tricky issue! One thing to check is the settings in your motor controller configuration—sometimes the acceleration or jerk limits might be set too aggressively, leading to those velocity errors. It could also be useful to look at how the jog commands are implemented; if there’s a sudden change in command input, that could spike the torque reference unexpectedly. Additionally, make sure that the feedback device (like an encoder, if you’re using one) is working correctly; any discrepancies there might give false readings and cause issues. If possible, try reducing the jog speed or ramping it up gradually to see if that helps with the torque spikes. Let us know how it goes!
âś… Work Order Management
âś… Asset Tracking
âś… Preventive Maintenance
âś… Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The excessive velocity error causing the servo motor to trip could be due to issues with torque references, motor control commands, or feedback loop tuning.
Answer: Answer: This discrepancy could indicate a problem with the motor control commands (MAM/MAJ) being sent to the servo motor, potentially leading to sudden torque spikes and velocity errors.
Answer: Answer: Troubleshooting steps may include checking the wiring connections, verifying control parameters, adjusting feedback loop tuning, ensuring the motor and drive compatibility, and investigating potential mechanical issues causing the torque spikes.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.