.jpg?sfvrsn=3ad09b0a_1)
Targets Causing the Collision
Am I missing something, or does the current "stop simulation at collision" not mean what I want it to mean --- diStop the robot at a collision?
Comments
-
Hi,
A limitation in RobotStudio 5.15 caused the robot to complete its current motion before stopping when the option "Stop at collision" was used.
Soon, we are releasing Robotstudio 5.60 that has been improved to stop directly at the point of collision. The way it works is that the simulation is in fact paused, and you can go into the RAPID Editor and check which instruction the program pointer is at. You can resume the simulation, which will make the robot stop at the next collision, if any. One pre-requisite for this behavior is that you use the TimeSlice virtual time mode (and not FreeRun). In the latter case, you will get the same behavior as in 5.15.
RobotStudio 5.60 will be publically available in the beginning of December.
Kind regards,
Henrik
Henrik Berlin
ABB0 -
Nice!
0
Categories
- 10.4K All Categories
- 5.3K RobotStudio
- 346 UpFeed
- 15 Tutorials
- 8 RobotApps
- 281 PowerPacs
- 404 RobotStudio S4
- 1.7K Developer Tools
- 238 ScreenMaker
- 2.6K Robot Controller
- 246 IRC5
- 36 OmniCore
- 6 RCS (Realistic Controller Simulation)
- 3 RobotStudio AR Viewer
- 691 RAPID Programming
- 14 Wizard Easy Programming
- 101 Collaborative Robots
- 3 Job listings