Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Iterative calibrating
#1
If I run a calibration, then master my arm, then finish by inputting the link lengths into the machine.dat of the kuka controller - can I then update the link lengths in RoboDK, and re-run the calibration and get a tighter result?

我校准然后重新灌录了更糟糕的是calibration result (2mm max versus 0.3 originally). Wondering if I can rewind and follow the method above, or something similar.
#2
You should not run the mastering procedure after calibrating your robot. This will make accuracy worse because the calibrated parameters are optimized for the robot arm as it is without any modifications. When you calibrate the robot with RoboDK you'll obtain an optimal set of parameters for the current state of the robot.

One option if you want to improve the accuracy before calibration and after calibration is to calibrate the robot first with only the mastering parameters (4 values), reset your joint zeros for joints 2 to 5 (so you'll be changing the nominal accuracy), and then calibrate the robot again using all parameters.
#3
(08-12-2022, 07:38 AM)Albert Wrote:You should not run the mastering procedure after calibrating your robot.

I guess I misunderstood this note, this must refer to doing what you're saying - master-only parameters first, then enter them into robot, then full calibration. I did full calibration, remastered, then full calibration again, and got a worse result. Pretty sure at that point I also had the updated joint lengths in the machine.dat of the kuka though, and not in robodk.

Going back to defaults today and restarting. Only takes about 25 minutes now for base, tool, and 65 calibration points, I'm very happy with that!

#4
Something else with this that I don't understand.

I ran through this, and the laser would point exactly to where the SMR ended up each pose. So I expected the calibration to be like zero mm error, but the calibrated result was 94mm error.

I restarted with a new cell again and did just the mastering. The laser would be pointing 5-10mm from the SMR in each pose, but when it finished it claimed a 0.7mm max error. Then I remastered, and re-ran the calibration with the complete calibration enabled. The laser was still 5-10mm from the SMR in each pose, but the calibrated result is 0.2mm error.

So the method definitely works, it's just opposite from what I'd expect!
#5
Thank you for your feedback. I'm happy to hear you were able to make it work and you are satisfied.

When you say you got a worse result, do you mean after you try to run a new calibration from scratch? I don't understand where the 94 mm error comes from...

运行整个只应校准一次enough if your robot was mastered using the standard procedure. You can get an idea of the impact of calibrating only with the mastering parameters. However, if nominal accuracy is 2-5 mm I don't think that redoing your mastering and recalibrating again will give you better accuracy with the calibrated model. On the other hand, if you run the calibration and you see that nominal errors are around 20 mm, you can apply this procedure (reset your mastering first and then recalibrate).

Please note the mastering program from RoboDK does not reset the mastering for joints 1 and joint 6. You need reference points for these to work. However, mastering joints 1 and 6 is not so important because these parameters are redundant with defining the robot TCP and your reference frame.
#6
(08-13-2022, 02:26 PM)Albert Wrote:if nominal accuracy is 2-5 mm I don't think that redoing your mastering and recalibrating again will give you better accuracy with the calibrated model

My nominal accuracy at the moment is probably 2mm at best, I just tried a 4-point TCP and had an error of 1.7mm, and the TCP drifts at least 5mm.

I calibrated with mastering parameters only, then mastered the robot, then recalibrated with full calibration. At this point my mastering should be about as good as it can get, shouldn't it? Using the Kuka mastering tool I was able to get our other kuka arm to a 0.3mm error TCP (just the tool, no software like RoboDK to calibrate)




Users browsing this thread:
1 Guest(s)