Experiencing an issue with a Kinetix 5700 servo drive where erroneous data is sporadically generated in the Average Actual Velocity and Actual Velocity registers while the drive is in run mode and no command signal is applied via EthernetIP. This data fluctuates between -2.7 E-4 and +2.7 E+4, causing our program to mistakenly advance a step at times. The issue quickly arises and then returns to "0.0". Instead of a temporary solution, it is essential to identify the root cause of this problem for a permanent fix.
What does a zero command signal imply in motion control systems? Are you instructing it to Jog or Move while maintaining a speed of 0? Or have you finished a move, activated MAS on the axis, and the servo is simply on (MSO)? Perhaps you are attempting to maintain a position against external forces, including gravity.
Are you utilizing the condition "velocity not equal to 0.0" to trigger a specific action? It is common to observe slight fluctuations in floating point values, also known as "flutter."
In programming, using "velocity not equal to 0.0" as a condition is common when dealing with floating point values. It is not uncommon to see some fluctuations or "flutter" in these values. For example, a change of +2.7 E+4 would be considered a significant flutter. If the intended value was actually +2.7 E-4, then it would make more sense. In this scenario, it is acceptable for a servo's velocity to vary between -.00027 and .00027 in order to maintain position stability.
Robertmee pointed out that a value of +2.7 E+4 would result in a significant fluctuation. It is likely that the original poster meant to write +2.7 E-4 instead. In such a scenario, it is acceptable for a servo's zero position to fluctuate between -.00027 and .00027. The discussion was focused on velocity values rather than positions. In my experience with Rexroth equipment, it is not uncommon to encounter unpredictable velocities even while maintaining a stable position.
dwoodlock explained that he was referring to the velocity, not the position, which is a common issue when working with Rexroth equipment. It is not uncommon to experience erratic velocities while maintaining a steady position. Rest assured, the velocity likely did not reach 27000 units per second in just a few scans.
I had a similar issue with my 5700 drive a while back. I found that the problem could reside in a few places. The most common culprit is electromagnetic interference from other devices. The fluctuations in the values of your Actual Velocity and Average Actual Velocity registers might be caused by electrical noise. Be sure all your cables are properly shielded and grounded, as poor grounding can often lead to such erratic behavior. Additionally, verify that your EthernetIP communication is steady and reliable because communication dropouts can also cause incorrect readings. Lastly, consider the firmware version you are currently using. Certain firmware versions of the Kinetix 5700 drive have known bugs related to speed control, so upgrading to a newer version may resolve the issue.
I've had a similar issue in the past and after several tests, we found that it was due to electrical noise interruption in the communication line. What kind of electrical environment is your servo drive situated in? If it's around high-power equipment, rapid temperature changes, or in the presence of high electrical noise, it might be affecting the feedback signals to and from the drive, leading to these sporadic fluctuations. It's worth considering using shielded cables and checking whether your EthernetIP grounding is solid. Also, like @MrEd suggested, do a complete diagnostic check of the drive. Hope this helps!
I've experienced a similar issue and the problem might be stemming from electromagnetic interference, especially if your drive is located near heavy-duty equipment. These interferences can affect the voltage drives and result in irregular data spikes like those you've mentioned. Also, confirm whether this issue is occurring even with a new drive, as this could illuminate potential issues with your EthernetIP network. You might want to consider installing an oscilloscope to monitor your system and pinpoint any irregularities. This could assist in identifying and troubleshooting the root cause effectively.
It sounds quite familiar to an issue I previously encountered with a similar Kinetix servo drive. One thing you could check is the integrity of the Ethernet cable or potentially even your EthernetIP connection. Intermittent glitches can be caused by slight connection disruptions. Alternatively, you could look at the conditions under which the issue occurs. Things like temperature fluctuations or electrical noise might influence the device's reading. If you've ruled that out, it's possibly a software bug, and you might want to update or patch your software. It's about identifying potential physical or software interferences. Let me 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 fluctuations could be caused by various factors such as electrical interference, communication issues, software glitches, or hardware malfunctions within the servo drive system.
Answer: Answer: You can start by checking the integrity of the communication network, verifying the configuration settings, inspecting the hardware components for any damage or loose connections, and updating the firmware of the servo drive to ensure compatibility with other system components.
Answer: Answer: While identifying the root cause for a permanent fix is crucial, you may consider implementing error-checking mechanisms in the program logic to detect and handle the erroneous data, ensuring smoother operation until the issue is resolved permanently.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.