Robot controller crashes when using \Conc movements
I'm using the IRB660 and trying to execute non-blocking movements, but when attempted the robot controller crashes after the first movement and locks the joints.
My only hint is that a joint position error is throw for joint rob1_1 being too far from the ordered position.
Example:
I'm sending less than 5 movement commands back to back. Has anyone run into this?
My only hint is that a joint position error is throw for joint rob1_1 being too far from the ordered position.
Example:
MoveL \Conc, pPos1, speed, z100, tTool;
MoveL \Conc, pPos2, speed, z100, tTool;
I'm sending less than 5 movement commands back to back. Has anyone run into this?
0
Comments
-
If you remove the \conc argument from all of the move commands giving the issue do you still get an error?
0 -
Per the RAPID Overview manual the concurrent switch for motion commands is for logical instructions e.g. IO instructions.
It is suspected the manipulator's motion planner would be overtaxed trying to interpolate multiple paths simultaneously.0
Categories
- All Categories
- 5.5K RobotStudio
- 390 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 249 ScreenMaker
- 2.7K Robot Controller
- 304 IRC5
- 59 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 3 RobotStudio AR Viewer
- 772 RAPID Programming
- 17 Wizard Easy Programming
- 105 Collaborative Robots
- 4 Job listings