Mech-Eye SDK 2.3.2 Release Notes

You are currently viewing the documentation for version 2.3.2. To access documentation for other versions, click the "Switch Version" button located in the upper-right corner of the page.

■ To use the latest version, visit the Mech-Mind Download Center to download it.

■ If you're unsure about the version of the product you are using, please contact Mech-Mind Technical Support for assistance.

This topic introduces the new features, improvements, and resolved issues of Mech-Eye SDK 2.3.2.

Mech-Eye Viewer

Adjust Virtual Device Parameters

Resolved Issues

The following issues have been resolved in Mech-Eye SDK 2.3.2:

  • If the software + fixed rate trigger method was used in the scan mode to acquire data, occasionally the acquisition failed.

  • If the Line Scan Trigger Source parameter was set to Encoder and acquisition was started when no encoder was connected, after the acquisition was stopped manually, the software interface was frozen until the time set in the Timeout Period parameter had passed.

  • With a resolution of 1980 × 1080 and scaling of 125%, the software interface could not be fully displayed on the screen when the restore button was clicked after the software interface had been maximized.

  • With a resolution of 1280 × 800 and scaling of 100%, the Measurement Tool window could not be fully displayed on the screen.

Mech-Eye API

Resolved Issues

The following issues have been resolved in Mech-Eye SDK 2.3.2:

  • When multiple clients were used at the same time (including Mech-Vision), if the laser profiler had started acquiring data according to the command of one client, another client could not successfully register a callback function. After the laser profiler had stopped acquiring data, the latter client could successfully register the callback function but could not retrieve the acquired data.

  • If the LineScanTriggerSource parameter was set to Encoder and acquisition was started when no encoder was connected, after the StopAcquisition() method had been called, the client program was frozen until the time set in the TimeoutPeriod parameter had passed.

  • If the software + fixed rate trigger method was used in the scan mode to acquire data, occasionally the acquisition failed.

  • When VisionPro samples were used to acquire data, some of the depth data were deleted because the Z-axis measurement range used by the samples to calculate the Z-axis resolution was inconsistent with the actual Z-axis measurement range.

GenICam Interface

Resolved Issues

The following issues have been resolved in Mech-Eye SDK 2.3.2:

  • If the software + fixed rate trigger method was used in the scan mode to acquire data, occasionally the acquisition failed.

  • When the value of Height (Scan Line Count) set in HALCON exceeded 3400, the error message Image acquisition: timeout (error code: 5322) prompted.

  • The point cloud obtained through HALCON was distorted and inconsistent with that obtained through Mech-Eye Viewer.

We Value Your Privacy

We use cookies to provide you with the best possible experience on our website. By continuing to use the site, you acknowledge that you agree to the use of cookies. If you decline, a single cookie will be used to ensure you're not tracked or remembered when you visit this website.