I read through the manuals but I didn’t find a good introduction to how to use the MultiMove programming feature in robot studio.
This was the best walk through I found.
This is the process I observe and what I would like to have a better understanding of.
Once the controller and system is built
create a work object for each “Tool Robot” and attach to the workpiece robot
add whatever targets/paths you want, to the tool robots under their workobject
in the multimove window, make sure path config update is green
in the multimove window test, play
This seems to try and create an automated motion for the “tool robot” where as the other robots can try and reach their respective paths. Is that the case?
Is that the entire goal of the multimove programming window?
How do I program a scenario where I want the tool robot to follow a specific path, instead using the software to find a path for it?
Is there a way we automatically make the robots avoid collision with each other?
First and foremost, MultiMove requires the proper controller settings, but the functionality ultimately is derived from the specific RAPID commands.
WaitSyncTask being a semi-coordinated command, SyncMoveOn/Off being full coordinated, etc.
The concept of a workpiece robot/tool driving a workobj, which then drives the subsequent tasks/robots in the system, is powerful, but not required for a multimove system. As long as the tasks within a controller use the correct commands, it is technically a semi-coordinated or fully coordinated multimove system.
The multimove addon within robotstudio isnt required to program. I believe its best use case is to help find the path of the robot the work piece attached, ie, you already have the path for the child worker robot, then press play and it find the path for the work piece robot.
