External Move
Function
This Step obtains the target pose from the external service, Adapter, and then performs path planning and robot motion control in Mech-Viz. You can set JPs, TCP, and the object pose in the “External Move” Step.
Parameter Description
Move-Type Step Common Parameters
Send Waypoint
Selected by default to send waypoint poses to the receiver, such as the robot. When this option is unselected, the waypoint pose will not be sent. However, the waypoint will remain in the planned path.
Try Continuously Running through Succeeding Non-Moves
Unselected by default. When non-move Steps, such as Vision Look, Set DO, Check DI, etc., are connected between move-type Steps, the robot’s path planning will be interrupted, and the actual robot will take a short pause, reducing the smoothness of running.
When this option is selected, the project will continue to run without waiting for the current move-type Step to complete execution, and therefore the robot can move in a smooth way without pauses. However, enabling this option may cause the execution of the Step to end prematurely.
Why will this option cause the execution of the Step to end prematurely?
Mech-Viz will send multiple poses simultaneously to the robot when the project is running. When the currently returned JPs of the robot correspond to the last pose sent by Mech-Viz, Mech-Viz will assume that the robot has moved to the last position.
For example, there are 10 move-type Steps in a path, and the pose of the 5th move-type Step is the same as that of the last move-type Step. When the robot moves at low speed, it sends JPs to Mech-Viz when it moves to the 5th move-type Step, Mech-Viz may mistakenly determine that the robot has finished the move-type Steps and prematurely ends the Steps since the poses of the 5th move-type Step and the last move-type Step are the same in the path.
Do Not Check Collision with Placed Workobject
Unselected by default, namely that the collision with the already placed objects will not be detected. When this option is selected, the collisions between the robot, end tool, and placed objects will be detected.
In palletizing scenarios, the two possible cases of error are as follows:
-
When the robot is placing a carton, the robot may come into light contact with the placed cartons while no deformation will be caused. After Mech-Viz detects this collision in simulation, it will plan other positions for placing the carton, and therefore a full stack cannot be formed.
-
Usually, the TCP of a suction cup is inside the suction cup model instead of on the surface of it. Under this circumstance, the suction cup may be embedded in the model of the picked carton in the simulation of picking, while the software does not detect the collision between the end tool and the picked object. After the robot places the object and the carton model turns into an object model in the scene, a collision between the suction cup and the carton will be detected and the palletizing cannot be completed.
When this option is selected, no collision between the robot, end tool, and the placed object will be detected, and the above two cases of errors can be avoided.
Point Cloud Collision Detection Mode
Select the proper mode according to the requirement of the on-site situation. Usually, the default setting Auto can be used. Do not check collision mode can be used in move-type Steps before the robot picks the object, and Check collision mode can be used after the robot picks the object.
Auto |
Default setting. Collision with point cloud is checked only for the “Vision Move” Step and the “Relative Move” Step that depends on the “Vision Move” Step, but not for all move-type Steps. |
Do not check collision |
Point cloud collisions for all move-type Steps will not be detected. |
Check collision |
Point cloud collisions for all move-type Steps will be detected. |
| When is switched on, Mech-Viz will detect collisions between the robot model, end tool model, and point cloud when planning the path. By default, the collisions between the robot and the target objects will be detected during picking and placing. When there are point cloud outliers, non-exiting collisions will be detected, which leads to errors in path planning. |
Ignore Workobject Symmetry
This parameter will only take effect when Waypoint type of the Step is set to Workobject pose.
None |
Default setting, i.e., do not disable symmetry on any axis. |
Around workobject frame Z axis |
Only disable symmetry on Z-axis of the workobject reference frame. |
Around workobject frame X&Y axis |
Disable symmetry on X-axis and Y-axis of the workobject reference frame. |
Around all axes |
Once the object symmetry is disabled, the robot will place the objects strictly according to the workobject poses. |
| In some special cases, objects are not pickable due to their peculiar poses. Setting Rotational symmetry under in Resources may solve this problem. Candidate poses of the recognized workobjects will be calculated according to the set rotational symmetry angle. When Mech-Viz plans to pick workpieces, if the default pose is not feasible for picking, the candidate poses will be tried. As the candidate poses calculated based on the settings of Rotational symmetry are different from the original poses output from Mech-Vision, the consistency of the objects’ place poses cannot be guaranteed. |
Plan Failure Out Port
Once this parameter is selected, a “Plan failure” exit port will be added to the Step.
During the planning process, planning is carried out along the branch after the “Success” exit port. If the planning fails in the current Step, the branch process after the “Planning failure” exit port will be executed.
Held Workobject Collision Detection Settings
Do Not Check Collision with Scene Object/Robot
Unselected by default. Once this option is selected, the collisions between the held workobject with the scene objects or robot will not be detected, and therefore the calculation workload of collision detection will be reduced, the planning speed can be increased, and the cycle time can be shortened. It is usually enabled in the first one or two move-type Steps after the robot picks the object.
Please enable this option cautiously as there may be collision risks.
When Detect collision between held workobject and others under is enabled, the software will detect whether the model of the held object collides with the models of the scene objects and the robot.
In palletizing projects, the calculated carton dimensions have millimeter-level errors with the actual dimensions, and frictions between cartons may occur during picking but no collisions will occur. For some move-type Steps that will obviously not cause collisions, detecting such collisions only adds to the calculation workload and planning time, and consequently extending the cycle time. In palletizing projects, enabling Do Not Check Collision with Scene Objects does not affect the collision detection between the held carton and the placed cartons. This option can be enabled when there are scene objects under the stack to avoid failure of finding the palletizing solution.
Do Not Check Collision with Point Cloud
Unselected by default. Once this option is selected, the collisions between the held workobject with the point clouds in the scene will not be detected, and therefore the calculation workload of collision detection will be reduced, the planning speed can be increased, and the cycle time can be shortened.
-
When both Detect collision between held workobject and others under and Configuration on point cloud ‣ Detect collision between point cloud and others are enabled, the software will detect whether the model of the held workobject will collide with the point cloud in the scene.
-
When Mech-Vision sends the point cloud and object model to Mech-Viz, the point cloud and the object model are fitted together. After the robot picks the object, the model moves along the planned path, and the collision between the model of the held workobject and the point cloud will occur.
-
It is known that the model of the held workobject will have false collisions with the point cloud. Detecting such collisions unnecessarily adds to the calculation workload and extends the planning time.
Service Name
The Adapter’s external service name registered in Mech-Center, which is used to connect the interface of this Step and send waypoints. Please make sure that the service name is the same as the Adapter name.
Use JPs from External Service
Unselected by default. The software will use the previous waypoint as the initial position when planning the path. Once this option is selected, the initial position for path planning will be the joint positions obtained from external services. This function is usually used in the scenarios where Mech-Viz is not used for master-control of the robot.
Interface Example
class CustomOuterMoveService(OuterMoveService):
def gather_targets(self, di, jps, flange_pose):
self.add_target(self.move_target_type, [0.189430,-0.455540,0.529460,-0.079367,0.294292,-0.952178,0.021236])The CustomOuterMoveService class is developed based on the OuterMoveService class. self.move_target_type indicates the target type. Valid values: 0, 1, and 2. A value of 0 indicates the JP type, a value of 1 indicates the TCP type, and a value of 2 indicates the object pose type. Mech-Viz calls getMoveTargets() when running an External Move Step. Different External Move Steps can be distinguished by their service names.
def _register_service(self):
self.outer_move_service = CustomOuterMoveService()
self._outer_move_server, port = register_service(outer_move_service, port)| If self.move_target_type is set to 2, you must place a Step that defines the picking before the External Move Step. Otherwise, the following error message will pop up: - The posture of the object is invalid when the object is not held!. |