fighting with RobotStudio changing configurations
in RobotStudio
Maybe it's because I'm using a 7-axis robot or maybe I'm too close to singularities or robot limits but it happens all the time: I teach a target with the right configuration add some more targets and movements and find out later that somehow RobotStudio changes the robot configurations of some of the targets. Let's say I teach this target:
https://imgur.com/a/2iyA0wS (I couldn't embed an image... don't know why)
and after an hour of work simulating and adding RAPID code, I end up noticing the robot reaches that target with a different configuration:
And there's no way I can correct it because target|configuration doesn't show the original configuration anymore. Nor I know why or when it changed. All I can do I delete the target and re-create it with the desired configuration.
I'm a newbie so maybe I'm doing some stupid mistakes but working with RobotStudio is becoming more and more frustrating. Is there some way to know when a target configuration changes or why? Is there a way to avoid this unpredictable behaviour or to fix a target?
Regards,
Leonardo
Tagged:
0
Categories
- All Categories
- 5.5K RobotStudio
- 394 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 249 ScreenMaker
- 2.7K Robot Controller
- 309 IRC5
- 59 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 785 RAPID Programming
- AppStudio
- 3 RobotStudio AR Viewer
- 18 Wizard Easy Programming
- 105 Collaborative Robots
- 4 Job listings