Description

The LumiScan Cam Driver connects Ethernet-enabled, GenICam-compliant cameras to a ctrlX CORE or ctrlX IPC (ctrlX OS) or to a PC, and makes their images and camera functions available through the Data Layer: the ctrlX Data Layer on ctrlX OS, LumiScan Keryx on a PC. The node addresses are the same on both.

What is the same for every LumiScan app - how addresses are built, the handshake, execute and stream call patterns, status codes, settings and tools - is described in the LumiScan Keryx manual. This manual covers only what is specific to LumiScan Cam Driver; the pages of this manual describe its own nodes.

It handles camera discovery, connection, image acquisition, and basic camera configuration. Camera parameters such as exposure time, pixel format, and other supported GenICam features can be accessed through the application configuration and Data Layer.

The available camera features depend on the camera model and its GenICam implementation. Some functions may not be available for every camera.

Where Images Can Be Accessed

Each configured camera publishes its acquired image through the Data Layer.

For example:

hdvisionsystems/lumiscan-cam-driver/camera1/output/image

The image node provides the image data together with information such as its width, height, and pixel type.

Other LumiScan applications can use this Data Layer address as their image source. The image data can also be accessed directly by applications that support the corresponding Data Layer interface.

Streaming Images

From v2.3.0, a camera can also stream its images: after <camera name>/control/publish/execute, the Cam Driver publishes every image the camera delivers on <camera name>/control/publish/output/stream/frame for a subscriber, instead of one image per capture request. The images come as the camera is triggered: by hardware, by control/trigger/execute, or continuously. This feature is experimental. See Streaming Images (Experimental).

Modules

A module represents one configured camera.

Each module defines which camera is used and contains the camera-specific configuration, such as:

  • Camera identification

  • Connection settings

  • Acquisition settings

  • Camera features and parameters

  • Data Layer addresses for control, status, and image output

Each module has its own Data Layer address and operates independently from the other configured cameras.

For example:

hdvisionsystems/lumiscan-cam-driver/camera1
hdvisionsystems/lumiscan-cam-driver/camera2

This allows one LumiScan Cam Driver installation to connect and manage multiple cameras, with each camera using its own module and configuration.