A couple of questions with the recent RobotWare 6

Robot Controller
, , , ,
1

Got a new robot recently and it came with RW6. I was initially really excited about it but it ran into some issues, which I’m unsure exactly where the fault lies.

Anyway, does anyone have proper documentation or experience with the new “Responsive Jogging” feature? We believe it is causing some errors whereby the TCP does not stay in the same spot when jogging the robot in reorient mode either in the world frame or tool frame (at least 10 times more severe errors in this frame). The repeatability is almost non-existent and the TCP just drifts away indefinitely if you continue jogging it. In case you are wondering, I’m pretty sure the TCP location is defined correctly. Imgur: The magic of the Internet Wrote a simple program (using reltool Rx,Ry,Rz) to see whether this happens in program execution and indeed it does. However it is all running in the world/base frame. How can I program it such that it is in effect the same as selecting toolframe-reorient in the flexpendant? Imgur: The magic of the Internet

1853×492 273 KB
On the other hand, do you guys think AbsAcc would have any help in this situation? If you can, please elaborate on the working principles of the AbsAcc package.

Also, A 2-axis turntable came with the robot and I tried to do coordinated motion on it. But the robot is not following the turntable motion correctly. Where can I check the controller’s record of where the turntable is physically with respect to the robot base? What is the correct way of setting up coordinated motion?

Thank you.

2

Help, anyone?

3

Any clues at all?

4

Hello
What max error did u get when calibrating the tool?

5

Its within acceptable range. I’ll just keep doing it until its below 0.5

6

Hey, not sure if you figured it out yet, but I just ran into this problem today. I work with routing, so I need my TCP to be very accurate. This bug is due to a feature in RobotWare 6 called Responsive Jogging. Not sure what it does, but after disabling it, my TCP went back to being dead on like it was in RW5. To disable it I connected via RobotStudio, went under configuration then Motion. Under Jog Parameters you will find a Jog Mode option that is probably set to “Responsive”. Change that to “Standard” and restart. Your problem should be fixed afterwards!