Mech-Vision 1.8 Release Notes

Project registration occasionally failed after renaming a project.

The software crashed when a new project with the same name as an existing project was created under the solution.

Opening too many Mech-Vision projects might have caused the software to crash.

When backing up solutions, the software backed up robot flange pose files outside the specified time range.

After configuring permissions for the solution, double-clicking the VIS file could not open the project.

Role names in the main interface failed to update after roles in a solution were renamed.

When “Custom background” was selected under Login settings in Solution Access Control  Advanced settings, then the cursor was moved to + and “No background” was selected, the “Click to upload” element disappeared.

When opening an autoload solution took a long time and the “Auto enable interface service when opening the solution” was enabled in the robot communication configuration, the interface service started twice after opening the solution.

Running the“Capture Images from Camera” Step failed to write to the intrinsic parameter file, causing the Step and project execution to fail.

If the “Scan Duration” parameter in the “3D Laser Profiler” Step was set to a custom value, setting the Data Acquisition Trigger Source to “External” and connecting the laser profiler to acquire images would reset the “Scan Duration” parameter to its default value after saving the configuration and reopening the project.

When the “Line Scan Trigger Source” in the “3D Laser Profiler” Step was set to "Fixed rate,” the “3D Laser Profiler” Steps with the same IP address across multiple projects could not use different parameter groups.

When manually entering the robot flange pose during calibration, the software failed to update the Euler angle convention based on the robot model information.

During configuration before calibration, the software did not use the protocol format configured in the robot communication configuration.

Differences in the calibration circle information detected at the same calibration point might have caused the software to incorrectly calculate the robot’s movement distance.

In the configuration before calibration for gantry robots, after selecting “Rotation around the Z-axis” as the movement affecting the camera position, the setting did not take effect.

In the “Set Motion Path” step during calibration, the path estimation warning persisted after clicking Yes in the prompt about the movement path being too long.

During hand-eye calibration with a UHP-140 camera, the software did not prompt the user to select an appropriate “Capture Mode” in Mech-Eye Viewer.

During the hand-eye calibration process for gantry robots, the calibration could not be completed properly after using multiple calibration boards to add calibration points.

The software crashed when the “3D Workpiece Recognition” Step encountered an internal error.

In the EIH scenario, after clicking Run project in the pose adjustment tool, the visualization area failed to update poses correctly.

The text and axis size settings in the 3D simulation area of the “Path Planning” tool only took effect after reopening the “Path Planning” tool.

Resetting the path planning configuration in the “Path Planning” tool might cause Mech-Vision to crash.

The default robot motion type for the “Vision Move” and “Relative Move” Steps in the path planning tool was set to “Joint move.”

In the Production Interface Configurator, if changes to the geometric model in the “New workpiece” step were not saved, the changes did not take effect after entering the production interface directly.

When using a “Model-making project” to add a new workpiece, modifications to the workpiece were not updated in the New Workpiece Wizard.

Once the currently used production recipe was deleted in the production interface, the information was not updated in the Workpiece info area.

The unit in the accuracy analysis results obtained via the error analysis tool is incorrect.

The software occasionally crashed after running the “3D Coarse Matching V2” Step.

If an exception occurred while running scripts with the “Calc Results by Python” Step, garbled texts appeared in the error message.

The configuration of the “Upward Offset along Z-Axis” parameter in the “Predict Pick Points V2” and “Predict Pick Points (Any Objects)” Steps did not take effect.

Pop-up errors interrupted project execution when the “Predict Pick Points V2” or “Predict Pick Points (Any Objects)” Steps failed to recognize objects with the deep learning model.

In EIH scenarios, the “Save Images” Step did not save robot flange poses according to the set “Max Images Number” parameter.

Deleting certain output ports of the “Bridge” Step caused other output ports to stop working or led to a software crash during project execution.

In the “Validate Box Object Masks” Step, after selecting the “All Box Must Be Same Dimension” option, the error message was unclear when the input depth map and mask image sizes were inconsistent.

The path generated by the “Generate Path from Contour” Step was incorrect.

There was a low probability of software crashes when using the “Mask Gridding” Step to process certain data.

The software crashed after automatically formatting Steps when a circular data flow existed between Steps.

After modifying the configurations in the deep learning model package management tool, the configurations were lost upon reopening the software.

When the graphics card information could not be retrieved properly, the software incorrectly judged the GPU usage as high, causing the point cloud to not display.

For user-specified ROI names, the software did not validate illegal characters and did not consider names differing only in case as duplicates.

When naming point cloud models in the “Matching Model and Pick Point Editor,” the software did not validate illegal characters.

Saved point cloud models were occasionally lost in the “Matching Model and Pick Point Editor.”

When external services triggered the Mech-Vision project execution, the software did not check whether the camera used in the current project was virtual, potentially causing robot collisions.