Forum Migration Notice
Update (2026-01-21): The user forums are now in read-only mode pending the data migration.
Update (2026-01-12): The user forums will be put into read-only mode on the 21st of January, 00:00 CET, to prepare for the data migration.
We're transitioning to a more modern community platform by beginning of next year. Learn about the upcoming changes and what to expect.
Update (2026-01-12): The user forums will be put into read-only mode on the 21st of January, 00:00 CET, to prepare for the data migration.
We're transitioning to a more modern community platform by beginning of next year. Learn about the upcoming changes and what to expect.
Checking reachability on the fly
avitalb
✭
Initially I thought, intuitively that I could handle a "out of reach" event and correct my path generation after such an event in error handler. It turns out that this is an error of type "System Error", and supposedly these cannot be handled by Rapid routines/procedures. I'd love to be corrected about this.
At any rate I still need to handle the event where the Robot may move out of reach because of an invalid/unreachable Robtarget that I have created. Is there a way to check for reachablity on a given Robtarget before executing a move instruction on it?
At any rate I still need to handle the event where the Robot may move out of reach because of an invalid/unreachable Robtarget that I have created. Is there a way to check for reachablity on a given Robtarget before executing a move instruction on it?
0
Categories
- All Categories
- 5.7K RobotStudio
- 402 UpFeed
- 21 Tutorials
- 16 RobotApps
- 307 PowerPacs
- 407 RobotStudio S4
- 1.8K Developer Tools
- 251 ScreenMaker
- 2.9K Robot Controller
- 368 IRC5
- 92 OmniCore
- 8 RCS (Realistic Controller Simulation)
- 859 RAPID Programming
- 43 AppStudio
- 4 RobotStudio AR Viewer
- 19 Wizard Easy Programming
- 111 Collaborative Robots
- 5 Job listings