Automate 2025: IDS releases firmware update 1.1 for uEye Live cameras

Industrial camera provider Imaging Development Systems GmbH (IDS) recently released firmware update 1.1 for its uEye Live monitoring cameras.

Free update 1.1.0.788 adds a number of practical functional enhancements for the uEye Live GL-54J0SCP, including new options for overlays, hardware triggers, storage and uploading of recordings.

All new features are configurable via the camera's improved WebCockpit web front end without requiring programming.

IDS will exhibit its uEye 3D time of flight cameras and other components at Automate 2025 in booth 6000.

The trade show is being hosted by the Association for Advancing Automation (A3) May 12-15 at the Huntington Place Convention Center in Detroit, Mich.

Overlay options, monitoring menu display more

Camera information, such as a logo or image, installation location, live status, crosshair, or a date and time stamp, can now be easily displayed as an overlay on the camera image. 

Additional information can now be displayed in stream 1 or stream 3.

The monitoring menu now also contains the streaming settings and the event recorder settings in addition to the camera status information.

The header top bar in the WebCockpit has been extended with two display elements to help keep track of important processes:

• Recording progress indicator: only visible during the recording of an event.
• Camera status information: camera information returned by the node /signals. Click on the camera status information in the header for further details and information.

Hardware triggers and camera storage

GP I/Os or hardware inputs can now be configured to trigger an event. Recordings can now be started with a trigger line and the recording memory can be used more flexibly for a few long videos or many short ones. 

The limitation of a maximum of 10 videos in the camera storage has been removed, allowing more flexible use.

If overwrite protection is enabled, recordings in the camera storage are not automatically deleted to make space for new recordings. Developers can save recordings until the camera storage is full. To empty the camera storage, users must delete recordings manually.

Uploading and downloading files

Saved content can be manually or automatically deleted, overwritten, or protected. If memory is low, recordings can be saved directly to an FTP server.

Users can now set up the FTP client to automatically transfer recordings to an FTP server after an event. With the new function, recordings can be saved regardless of the usage of the camera storage.

In the recording menu, it is now possible to download all recordings from the camera at once. Previously only individual recordings could be downloaded.

Recording settings and logbook

Storage usage is now also displayed in the recordings section of the WebCockpit.

The source of an event (WebCockpit, REST API, or hardware input) is now included in the filename of the recording.

Actions are logged in the logbook, such as changing recording settings, triggering events, deleting and downloading recordings.

The event recorder settings are deactivated as long as an event is being recorded.

WebCockpit connection, authorization revisions

In the WebCockpit, users can now upload files to the camera via drag and drop.

When WebCockpit is opened via an insecure HTTP connection, users will now receive information and options for secure connection via HTTPS.

The authorizations for the user profile have been revised. Users can only log into the WebCockpit after administrators have assigned a password for the user profile in the user menu.

Users can now also adjust settings in the image settings menu and recording menu and thus react to changed environmental conditions.