Mech-Eye Viewer
Added Display of Sensor Head Temperature
The display of sensor head temperature has been added to the Acquisition info tab, so that you can monitor the heat-dissipation situation of the sensor head conveniently.
Resolved Issues
The following issues have been resolved in Mech-Eye SDK 2.3.4:
-
When the internal system of the laser profiler encountered logical abnormality, the laser profiler had to be restarted to recover.
-
When the computer was not connected to the Internet, the laser profiler could not synchronize the computer’s system time.
-
When an encoder was used to trigger line scan, if the value of the Scan Line Count parameter was not a multiple of 16, the actually acquired number of profile was less than the parameter value.
-
After the profile display area of Measurement Tool had been zoomed in, when the detection area contained profile, the measurement result still displayed Error.
Mech-Eye API
Obtain Controller and Sensor Head Temperatures
You can now obtain the controller and sensor head temperatures by calling the following methods to conveniently monitor the heat-dissipation situation of the controller and sensor.
|
The relevant sample PrintProfilerStatus can be obtained from the installation path or GitHub. For the sample usage guide of different languages, please refer to Sample Usage Guide. |
-
C++
-
C#
-
Python
ErrorStatus getProfilerStatus(ProfilerStatus& status) const;ErrorStatus GetProfilerStatus(ref profilerStatus);self.profiler.get_profiler_status(self.profiler_status)New Timeout Period Parameter Added
A new BatchRetrievalTimeout parameter has been added for setting the timeout period of obtaining a batch of data. The function of this parameter is the same as the Timeout Period parameter in Mech-Eye Viewer. The existing CallbackRetrievalTimeout parameter is used to set the timeout period when a callback function is used to retrieve data. Meanwhile, its maximum value has been changed from 60000 ms to 9999999 ms.
IP Configuration Tool: Non-Interactive Command Mode Added
A new non-interactive command mode has been added to IP configuration tool. In this mode, you can execute commands to complete corresponding modifications of IP configuration, satisfying more diverse needs, such as developing an IP configuration graphical user interface based on this tool.
Speed of Data Retrieval Using Callback Function Enhanced
The mechanism for the data retrieval callback function has been improved in Mech-Eye API 2.3.4, so that the speed of data retrieval is enhanced when using a callback function.
Resolved Issues
The following issues have been resolved in Mech-Eye SDK 2.3.4:
-
When the internal system of the laser profiler encountered logical abnormality, the laser profiler had to be restarted to recover.
-
When the computer was not connected to the Internet, the laser profiler could not synchronize the computer’s system time.
-
When the data of the first acquire profile was lost, the callback function for data retrieval could not be triggered.
-
When none of the profile data could be retrieved due to timeout, the callback function could not be triggered, and the value of ErrorStatus could not be returned.
-
When an encoder was to trigger line scan, if the value of the ScanLineCount parameter was not a multiple of 16, the actually acquired number of profile was less than the parameter value.
GenICam Interface
IP Configuration Tool: Non-Interactive Command Mode Added
A new non-interactive command mode has been added to IP configuration tool. In this mode, you can execute commands to complete corresponding modifications of IP configuration, satisfying more diverse needs, such as developing an IP configuration graphical user interface based on this tool.
Resolved Issues
The following issues have been resolved in Mech-Eye SDK 2.3.4:
-
When the internal system of the laser profiler encountered logical abnormality, the laser profiler had to be restarted to recover.
-
When the computer was not connected to the Internet, the laser profiler could not synchronize the computer’s system time.
-
When an encoder was to trigger line scan, if the value of the ScanLineCount parameter was not a multiple of 16, the actually acquired number of profile was less than the parameter value.