Compatibility is a key factor while using Mech-Eye API to develop your own program. This post explains the compatibility between different versions to assist you in ensuring that your program continues to run stably after the upgrade of Mech-Eye SDK or camera firmware.
1. Source Code Compatibility
Source code compatibility is a type of compatbility between two versions of Mech-Eye SDK. If two versions are compatible, after the upgrade of Mech-Eye SDK, the program developed based on the lower version can still run properly without significant code modification.
-
If the two versions are compatible, you only need to replace the DLL files and build the program again after upgrading Mech-Eye SDK.
-
If two versions are not compatible, you will need to modify the code for the program to work with the newer version of Mech-Eye SDK.
Source Code Compatibility Table
2. Camera Firmware Compatibility
Camera firmware compatibility is the compatibility between different versions of Mech-Eye API and camera firmware. If compatible, a program using Mech-Eye API can communicate with cameras with different versions of firmware and perform all functions correctly.
- If compatible, the program can perform all functions correctly when connected to the camera.
- If not compatible, the program can still connect to the camera, but some functions or parameters may not be available.
Camera Firmware Compatibility Table
Note:
- The table considers all the functions available in a version of Mech-Eye API. A pair of Mech-Eye API and firmware versions may be listed as “not compatible” in the table, but if you do not use the functions that are not compatible, the program can still run properly. For example, If you do not use the new
LaserProcessingMode
parameter added in Mech-Eye API 2.3.4, then the program can connect to a camera with firmware version 2.3.3 and operate normally.