v2.2.0 - 2026.08.05
Added:
-
All cameras can now share one image folder. A new system setting unifiedStorage decides where images are kept. With the default
false, each camera stores and loads its images in its own folder named after the camera, as introduced in v2.0.0. Set it totrueand all cameras use the storage folder directly, which is the flat layout used before v2.0.0. The setting applies both to saved images and to the images that simulation mode loads.
Changed:
-
A refused
executenow says whether waiting will help. Writing to<camera name>/control/<operation>/executewhile the operation’sreadysignal isfalsenow answersDL_INVALID_OPERATION_MODE;DL_TOO_MANY_OPERATIONSis left to mean what it says, that the camera is busy with another operation and the same command will work in a moment. The two used to be reported alike, so a program that retries on "busy" could retry forever after, for example, capturing without being connected, saving before anything had been captured, or capturing again after a capture fault that only aresetclears. See When is an operation ready. -
The application now proves that it may run by actually taking its licenses. Previously it asked the licensing service how many licenses existed on the device. That number also counts licenses another application had already taken, so the cam driver could start on a license that was not really free and then fail. It now takes the licenses it needs at startup, and refuses to start if it cannot get them, naming the license and how many were needed.
-
Licenses are renewed every 30 minutes. If a license expires, is withdrawn, or the licensing service stops granting it, the application writes a warning naming the license and shuts down instead of continuing without a valid license. Previously a license lost while the application was running went unnoticed.
Bugfix:
-
Licenses that were installed separately are now all found. The application used to look only at the first Cam Driver V2 entry that ctrlX OS reported. A device whose licenses had been installed one after another therefore appeared to have a single license, and a cam driver configured for several cameras refused to start, reporting that there were not enough licenses.
This affects v2.1.0 and earlier. On those versions, please install all licenses together, so that the Licenses page of ctrlX OS shows one Cam Driver V2 entry covering all cameras instead of one entry per license. If the problem occurs, the application reports the status missingLicense(code -4) with the text "No valid license found, please purchase one. If you do have one, please try to restart ctrlX", and stops. See Requirements. -
Shutting down is faster. Returning each license took about five seconds, so a cam driver holding three licenses took roughly fifteen seconds longer to stop than it needed to.