mjp123gp
Member
We have a Kinteix 7000 that is used in a winding application. About a month ago we started having issues where the drive will get a stop command and will come to a complete stop, then it will slowly start ramping back up and running at a slow speed. It doesn't do this everytime. It has only happened maybe 10 times in the past few weeks. We have been running trends trying to capture some data when this events happen and what we are seeing is the logic is giving the stop command, the command velocity goes to zero along with the actual velocity. The DriveEnableStatus bit along with the ServoActionStatus bit both go low but the actual velocity will still creep back up. If I understand this correctly, the MSF command should be what would normaly cause the DriveEnableStatus bit to go low. I have also heard that a drive fault will also cause this to go low but unfortunately I wasn't trending any fault statuses at the time it last happened. It has since been added and we're waiting on the next event.
Just a little more info about when this issue started that may or may not be related- We had the vendor that designed the machine in here doing some programming around the same time this started happening so the first thought was that it was something they did that caused the issue but now, seeing it run after losing the DriveEnableStatus, i'm not so sure. The initial problem we had with this axis was instability of this motor with a lot of vibration. They were not able to tune it out so the motor and drive were both replaced. After replacing both, we still had the same problem. Their fix was to use SSV commands to change the drive gains depending on the speed it was running. From looking at the logic, I don't see where this would cause the issue but i'm not exactly sure what all is affected behind the scenes when doing these SSV's.
Any ideas on what might cause this or suggestions on other data point I should trend to help capture more important data?
Thanks in advance.
EDIT: Just wanted to add a little more info. This drive is controlled over SERCOS. It does not use hardwire enable. Since the last trend capture I have also added a new trend to watch torque feedback, Sercos ring faults, axis faults, and drive faults. I can try to upload the trend log file when I get back to the office in the morning. Not sure what the file size limit is here but I think the files is around 3-4mb.
Just a little more info about when this issue started that may or may not be related- We had the vendor that designed the machine in here doing some programming around the same time this started happening so the first thought was that it was something they did that caused the issue but now, seeing it run after losing the DriveEnableStatus, i'm not so sure. The initial problem we had with this axis was instability of this motor with a lot of vibration. They were not able to tune it out so the motor and drive were both replaced. After replacing both, we still had the same problem. Their fix was to use SSV commands to change the drive gains depending on the speed it was running. From looking at the logic, I don't see where this would cause the issue but i'm not exactly sure what all is affected behind the scenes when doing these SSV's.
Any ideas on what might cause this or suggestions on other data point I should trend to help capture more important data?
Thanks in advance.
EDIT: Just wanted to add a little more info. This drive is controlled over SERCOS. It does not use hardwire enable. Since the last trend capture I have also added a new trend to watch torque feedback, Sercos ring faults, axis faults, and drive faults. I can try to upload the trend log file when I get back to the office in the morning. Not sure what the file size limit is here but I think the files is around 3-4mb.
Last edited: