Common Software Function Issues
1. Software Startup / Shutdown / Restart / Run
1.1 White Screen
Issue: A white screen appears when opening the software.
Affected Versions: All versions
Solution: A monitor must be connected for the interface to display properly.
1.2 Black Screen
Issue: After clicking Run, the computer shows a black screen, powers off, and restarts.
Affected Versions: All versions
Solution: The power supply may have insufficient wattage. Check the power supply wattage. More than 250W is recommended.
1.3 The Software Cannot Start After an Unexpected Power Loss
Issue: After an unexpected power loss, the software cannot start and keeps reporting "Please restart the software".
Affected Versions: All versions
Solution:
Check the .dexforce/project/project_recent.ini file under the user directory.
Open the folder of the first path and check whether the dexforce_proj.json file is damaged.
If the file is damaged, rename this folder. PickWiz will reopen the next Project and can then be opened normally (if you need to use the current Project file, you can restore it from a backup).
When using shadow mode, also check whether the latest_info.json file is damaged.
1.4 Abnormal Video Memory
Issue: The software keeps reporting video memory errors while running.
**Affected Versions:**All versions
Possible Cause:
After two models are loaded, the remaining GPU memory is insufficient to support Inference.
Solution:
1.5 Memory Exception
Issue: During software operation, memory usage continues to increase.
Affected Versions: All versions
Possible Cause: While the software is running, File Explorer or Visual Studio Code is opened to view a specific folder. Since the software writes files to this folder during operation, the number of files keeps increasing, which causes memory usage to continuously rise when viewing that folder.
Solution: Close File Explorer, Visual Studio Code, and any other software with high memory usage.
1.6 glia_error Reported on the First Run
Issue: glia_error is reported on the first run, and the required general model cannot be downloaded.
**Affected Versions:**All versions
Possible Cause:
Solution: According to the error details, download the corresponding model from this document and place it in the corresponding path.
1.7 Automatically Start PickWiz at Boot
Issue: After auto-start is turned off in PickWiz and the computer is restarted, one instance of PickWiz still starts automatically.
Affected Versions: All versions
Possible Cause: The user added a custom task in Task Scheduler to start PickWiz at boot, which conflicts with PickWiz's built-in auto-start function.
Solution: After deleting the custom startup task, PickWiz can start automatically at boot normally.
If you need to configure PickWiz to start automatically at boot, click Menu > Automatically Start PickWiz at Boot > Enable on the main interface.
2. Interaction
2.1 Display Abnormality
Issue: Due to resolution issues in the user interface, some controls cannot be clicked.
**Affected Versions:**All versions
Possible Cause:
Solution: The software is currently not compatible with different resolutions (1920×). Use the middle mouse button or drag to adjust the size of the selection box.
3. User Information Injection
3.1 Failed Replacement of Workpiece Point Cloud Information
Issue: When replacing the Point Cloud file, the software reports an error, and the template to be imported is automatically cleared.
Affected Versions:
Possible Cause: The imported Point Cloud file cannot be placed in the product/product_1/resource directory under the Project directory. It must be imported from another directory.
Solution: Move the imported Point Cloud file from product/product_1/resource under the Project directory to another location.
3.2 Failed Parsing of the Tool Model
Issue: A configuration file parsing failure is reported when importing the fixture model.
Possible Cause: The software currently does not support Chinese characters in the Project path.
Solution: The software currently does not support Chinese characters in the Project path. Please use a fully English path.
3.3 Incomplete 2D Recognition Segmentation
Issue: 2D recognition segmentation is incomplete.
Possible Cause: ROI does not fully cover the target area.
Solution: ROI does not cover the full area, so the entire workpiece should be enclosed.
4. Historical Data
4.1 Pick Strategy / Vision Parameters Did Not Take Effect in Historical Data
Issue: After running historical data, the Pick strategy / vision parameters did not take effect.
Possible Cause: The run configuration of the historical data was used, so the current task's Pick strategy / vision parameters do not take effect.
Solution: Change it to use the current task configuration, and it will work normally.
4.2 Abnormal Error When Running Normal Historical Data
Issue: After test-running historical data that previously output results normally, an exception related to the full inspection function is reported.
Possible Cause: In most cases, this happens when different tasks / ROI3d are used. Because the Point Cloud of the current historical data is inconsistent with the currently used roi, many noise points may be added above the instance Point Cloud, which triggers the full inspection exception.
Solution: Ensure the task is consistent or adjust the roi.
4.3 Whether the scale Parameter of generate_pcds_by_bboxes Takes Effect
Issue: No effective difference is observed before and after setting the scale parameter of generate_pcds_by_bboxes.
Affected Versions:
Possible Cause: The function generate_pcds_by_bbox is used at the instance filtering node for Point Cloud generation. To observe the effect of adjusting this function, you need to inspect the Point Cloud file in the historical data. It will not be visualized on the frontend interface.
Solution: The specific method is as follows.
4.4 Camera Data Cannot Be Used After Batch Running Historical Data
Issue: After batch running historical data, camera data cannot be used.
Affected Versions:
Possible Cause: When the input data is set to "camera data", performing "batch run historical data" causes the input mode to become inconsistent.
Solution: The correct operating steps are as follows:
5. Robot
5.1 Alarm for Failing to Load the Robot Arm Model
Issue: After upgrading from 1.4.1 to 1.4.5, the Robot arm configuration in the duplicated task can no longer be seen.
Affected Versions:
Possible Cause:
Solution:
5.2 Communication Connection
Issue: During communication protocol integration, data transmission between the Robot and the communication assistant is normal, and data transmission between the communication assistant and PickWiz is also normal, but PickWiz cannot receive the photo capture command sent by the Robot.
Affected Versions: All versions
Possible Cause: This is a common issue in communication integration and is caused by the Windows firewall not being disabled.
Solution: Have an FAE perform on-site configuration.
6. Hardware Dongle
6.1 Hardware Dongle Detection Error (27)
Issue: Hardware dongle detection error (27)
Possible Cause: Windows built-in Remote Desktop Connection was used.
Solution: Windows built-in Remote Desktop Connection cannot be used (it poses a risk of data leakage). You must use a monitor / todesk / Sunlogin:
6.2 Hardware Dongle Detection Error (31)
Issue: Hardware dongle detection error (31)
Possible Cause: It indicates that authorization has not been granted.
Solution: Contact the company administrator for authorization.
7. Takt Time
[Stereo Capture Time Record]
A: The stereo Camera image acquisition time (photo capture only, model inference, and total time) is recorded in the logs under the path C:\Users\dex\\.dexforce\log\pickwiz. Find the most recent INFO log and open it with Notepad.
[Long Processing Time Caused by Too Many Instances] Point Cloud Generation Takes a Long Time When There Are Many Instances
Set the mask_on parameter of GliaRcnn to false, which means Mask data is not transmitted;
For versions below 1.4.2, select the processing function generate_pcds_by_masks for Point Cloud generation.
For 1.4.3+, select the processing function generate_pcds_by_bboxes for Point Cloud generation.
[Log Meanings] Meanings of Various Time Costs in Backend Logs
Total node computation time: The total time from entering the first node to exiting the last node, including the total time for algorithm execution and processing function execution of all nodes.
Total detection pipeline time: The total time from triggering the PickLight detection API to completion, including configuration comparison, node updates, algorithm registration, and the above total node computation time.
Total time for this detection process: The total time from receiving Camera data to computing the Pick Point, including task configuration parsing, resource registration, node generation, and the above total detection pipeline time. This time represents the actual time used for one backend computation. During the first run, registration takes longer. In subsequent computations, if the configuration remains unchanged, there will be additional memory recycling time, currently about 0.1-0.2s, so it appears to be always slightly longer than the total detection pipeline time.
[Enable Multi-workflow Cache] Meaning of Workflow Cache
Disabled: Backend single-instance mode. Each time you switch tasks, the backend instance is reloaded, including resource registration / node generation and so on.
Enabled: Backend multi-instance mode. When hardware resources allow, multiple instances are cached to the greatest extent possible. When switching tasks, instance loading is only executed the first time; after that it is cached, and subsequent runs no longer require registration operations.
When multiple tasks exist and these tasks are switched frequently, enabling the multi-workflow cache feature can avoid frequent instance creation / registration operations and improve Takt Time.