Common Requirements
About 645 wordsAbout 2 min
6. Common Requirements
6.1 Pick Multiple Cartons from One Capture
The default is “one capture, one pick”: each time the robot triggers a task, PickWiz captures a new image, calculates the result, and returns it.
If you have confirmed that picking a carton will not noticeably move the stack and that the cached coordinates will remain safe and valid, you can use “one capture, multiple picks”:
- Open Visual Computation Configuration and go to Pick Logic Settings.
- Enable “One Capture, Multiple Picks.”
- Set “Number of Poses to Calculate” to the number of cartons to calculate and cache from one capture.
- Use “Number of Instances to Send” to control how many instances are sent to the robot on each trigger.
- In a depalletizing task, each instance can output only one Pick Point. Do not change “Number of Pick Points to Send.”
- Save the configuration and run a low-speed integrated test to check the instances returned each time and their order.
Picking a carton may move adjacent cartons or change the position of the stack. If the cached coordinates no longer match the cartons’ actual positions, use “one capture, one pick” to capture a new image and recalculate before each pick.
For detailed configuration instructions, see the Visual Computation Configuration User Guide.
6.2 Adjust the Picking Order of Cartons on the Same Layer
To change the picking route for cartons on the same layer, keep descending Z as the first priority, then adjust the Y and X direction strategies:
- To have the robot pick from one side to the other, select the ascending or descending strategy for the corresponding coordinate axis.
- To pick from the center of the stack toward both sides, use a strategy based on distance from the center.
- Reduce the grouping step size if a group contains too many cartons. Increase it if cartons on the same layer are split into too many groups.
- Adjust only one strategy at a time, and use instance IDs and logs to confirm the actual order.
For the full set of strategies, see the Instance Sorting Configuration Guide.
6.3 Optimize Visual Computation Cycle Time
Optimize cycle time after the visual results are stable and the picks have been verified:
- Use the logs to identify processing stages that take longer. Do not change parameters based on total elapsed time alone.
- Switch from “Save All (Debug Mode)” to “Save Raw Images Only (Ultra-Fast Mode).”
- Do not enable shadow mode if model data collection is unnecessary.
- Set “Number of Poses to Calculate” to the number actually required by the process.
- Keep auto enhancement off when it is unnecessary. Configuring multiple scale factors and rotation angles increases the amount of 2D computation accordingly.
- If “Extract Topmost-Layer Texture” takes too long, you can appropriately reduce the number of point clouds used for clustering, but you must reconfirm that the top-layer cartons’ textures remain complete.
- Before enabling visual computation acceleration, check whether the current task and feature options meet its usage restrictions.
- After each optimization, rerun the acceptance samples to confirm that recognition, sorting, and Pick Points have not degraded.
For specific troubleshooting methods, see Common Cycle Time Issues and Solutions.