v2.0.0 - 2026.06.02
Breaking Changes:
-
A new license key is required:
SWL-W-XCx-CAMDRIVERxHDVSx-V2NN. Version 1 keys do not work with this release. -
Simulation folder changed: Simulation will load images from
images/<camera id>instead ofimages. If you use simulation mode, please move your existing images into the folder named after the camera before updating.
Added:
-
Several cameras at once. One installation can now operate more than one camera. Please note that each connected camera needs its own license.
-
More accurate image timestamps. The timestamp used for images now defaults to the time reported by the camera itself, which is closer to the moment the picture was actually taken. The ctrlX system clock is still available if you prefer the old behavior (see timestampSource in table 7).
-
Set camera IP addresses from the control system. You no longer need a separate tool to give a camera the right network address.
-
See camera network details without a restart. The IP and MAC addresses of the cameras found on the network are now shown directly, so checking them no longer means restarting the cam-driver.
-
Always get the newest picture. A new camera setting, clearBufferBeforeCapture, discards older images still waiting in the queue so that a capture always returns a fresh one.
Improved:
-
In simulation mode, on connection, it will scan storage folder for images. Users don‘t need to call list-images anymore.
-
The example settings now include a sample image and use the internal storage by default, so a first test works without any preparation.
-
Additional log messages make it easier to check how fast the cam-driver is running.
Bugfix:
-
The application could take a long time to restart, because a connection was left open after it was shut down. Restarts are quick again.
-
The inter-package-delay-us setting could still be changed after the camera was connected, where it had no effect. It is now locked once the camera is in use.
Experimental (Use with caution):
-
User can now set GenICamFeature(Device) in datalayer under
lumiscan-cam-driver/<camera id>/features.
| Currently feature is not cached. If user (i.e. PLC) keep setting feature value might lead to camera instability and performance penalty. |