Kollmorgen Support Network

To better serve our Kollmorgen users with questions too complex to be addressed in this space, we made the painful decision to close this Community forum.

Please submit your question using the contact us form to reach our application engineering team.

For the immediate future, you can still access and read past posts.

Thank you for understanding and for participating in the community over the years.

AKD IL.LIMITP / IL.LIMITN Behavior | 08 Mar 2018 | |

AKD IL.LIMITP / IL.LIMITN Behavior

Hi!

I was playing around with an AKD and I tried to change the current limit to avoid breaking things in case some mechanical part is blocking the motion. I read the manual and I found the two limit variables: IL.LIMITP and IL.LIMITN and they work well. The thing is: when I set the current to a small value and force it with my hand to simulate something blocking the motion, the drive simply disables without returning any warning or fault. Is this right? I would expect to get some fault from that.

Thank you!

Comments & Answers

Dan.Wolke@Koll… said ...

Dan.Wolke@Koll… | Thu, 03/08/2018 - 19:00

I can not reproduce this with a simple AKD and Workbench setup. I think he is using a Fieldbus. I asked him to try again without the fieldbus.

bruno.luvizotto said ...

bruno.luvizotto | Fri, 03/09/2018 - 11:55
Thank you for the reply, Dan. I was testing it using a PDMM and KAS. With a simple AKD and WorkBench it worked properly.

Ron Van Bruwaene | Tue, 03/13/2018 - 21:54

This may have been caused by a program running that was monitoring position fault. If you are using one of the templates, you may find a program called FaultMonitor. If so, you may want to increase the variable Axis1PosErrorLimit or Axis2PosErrorLimit. This is for a version of the PLCOpen FFLD template.

bruno.luvizotto | Thu, 03/15/2018 - 14:33

Ron, I found out that was the case. The PDMM was disabling the drive. Thanks for the reply!

About this Question

bruno.luvizotto
Taxonomy: