Robot slow at one particular movement?
AriG
✭
Hi everyone, very new user of RobotStudio here. I have been having some issues lately with my program. One move in particular in which the tool translates about 20mm and reorients by 45 degrees. This movement is done primarily in J5. In my program I have set the move speed very high, I have even tried up to max speed. In the RobotStudio simulation the move is shown as happening quite quickly but whenever I run the script on the actual robot (an IRB 4600) this move takes a very long time to complete. The flex pendant says that the program is running at 100% speed, and all of the other moves in the program seem to be being executed at more or less the correct speed. Is it possible there are some limiters set on the robot that are external to the RAPID program? If anyone has any other ideas they would be greatly appreciated.
Post edited by AriG on
Tagged:
0
Comments
-
The component of the speeddata which is limiting your speed is v_ori. All of the predefined speeds, while they have higher v_tcp, have the same v_ori. Make your own speed with a higher orientation speed. Bigger zones might help if you can put some in.Lee Justice0
-
lemster68 said:The component of the speeddata which is limiting your speed is v_ori. All of the predefined speeds, while they have higher v_tcp, have the same v_ori. Make your own speed with a higher orientation speed. Bigger zones might help if you can put some in.0
-
Do you have a high payload? The robot will only move as fast as maximum permitted torque in any motor or gearbox. It will not damage itself because someone tells it to go faster.Lee Justice0
-
The tool weighs less than 1kg0
-
I don't expect that the cog will be far from the flange then. So, back to your programmed speed. 20 mm @ 2000 mm/sec is .01 sec, 45 degrees @ 500 deg/sec is .09 sec. None of which is close to the two seconds. Anyway, are there fine points or timed movements? A timed movement, regardless of a z50 or whatever, will be a fine point because it HAS to: otherwise, how could it time it? Try to play around with making your own speeds, with even slower tcp speeds but higher orientation speed. It used to be, back in the day, that, with close points and high programmed speeds, the robot would run slower. To get faster cycle times we would slow the robot down to get it to run faster. Not kidding.Lee Justice0
-
I am trying to rotate approximately 500g at a distance of about 200mm from the axis of rotation. I don't think it would require a large amount of torque.0
-
You mentioned external axis speed earlier, is there an external axis involved here somewhere?Lee Justice0
-
Hey sorry but we figured out the problem...the robot was in manual mode . Sorry I'm still pretty new to this but thanks for all of your help.0
-
OK good! So you were facing the 250mm/sec limit for manual mode.
Lee Justice0
Categories
- All Categories
- 5.5K RobotStudio
- 396 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 250 ScreenMaker
- 2.8K Robot Controller
- 316 IRC5
- 61 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 798 RAPID Programming
- AppStudio
- 3 RobotStudio AR Viewer
- 18 Wizard Easy Programming
- 105 Collaborative Robots
- 5 Job listings