uArm Swift Pro Calibration forcing recalibration

Several times after powering off or disconnecting the uArm the calibration is off by a considerable amount forcing a recalibration.

What is the cause and how can it be prevented?

Could you tell us how you test that so we could try to reproduce it in the lab?

I’m not entirely sure. It has happened several times that I have had to recalibrate.

Can you tell me what conditions require a recalibration?

Normally on the condition when you get the Z aixs diviation, for example when you give coordinates like from (150,0,0) move to (250,0,0), no Z aixs movement on code but the real height of the TCP changes for more than 1mm.