Skip to main content

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.

FB1.TRACKINGCAL function | 15 Sep 2015 | |



I have a problem with a AKM motor + SFD Feedback and a AKD-P-NBCC drive : randomly, the error F421 appears on the drive (sometimes after some minutes, sometimes as soon as I switch on the drive)...

I have finally set FB1.TRACKINGCAL to 1, and it seems that I don't have the error anymore ...(But sometimes, I hear a strange noise during few millisecond...I suppose that without TRACKINGCAL, I would have F421 error)

Is it possible to have more detailed on this parameter? Is it possible to monitor the trace of the feedback with AKD Scope ( I mean Sin signal and Cos signal)...

It seems that this parameter is linked with FB1.CALTHRESH (Release FW 1.7...) but this parameter does not exist anymore in V1.13 version ?

Thank you very much.

Best regards.

Comments & Answers

Joerg Muslewski said ...

Joerg Muslewski | Mon, 09/21/2015 - 08:30


This issue could be related to EMC- or shielding problems. Does it happen when the drive is enabled ? Are you using SFD with one cable solution ?

SFD feedback provides only a digital signal, thus you cannot trace any analog signal.

At the moment it is not possible to record the analog signals of a feedback by AKD scope function.

You can record the parameter <VL.FBUNFILTERED> which gives an information about the quality of the velocity signal.



defty | Mon, 09/21/2015 - 09:06

Hi Joerg,

Thanks a lot for this answer.
It happens sometimes at the end of the boot phase (the drive is disabled), sometimes, it happens when the drive is disabled and when we manually rotate the motor shat, sometimes when the drive is enabled, but the motor does not move, sometimes when the motor is running....It seems effectively to be a shield problem.
But it happens on my customer machine, but also at my office with another drive & cable set.
On the customer machine, we have change the motor by another one, with exactly same cables, and we don't have the problem...
It is a 2 cables solution (1 for the power, the other one for the feedback...)
Best regards.

Djillali Hani | Fri, 09/20/2019 - 15:38

i have the same problem can you tell me where i can find the FB1.TRACKINGCAL

About this Question