In the first step of the camera configuration, you select the camera type and can assign a name.

Camera name

If a new camera is added, it is automatically assigned with a default name. You may however change the camera name by entering a new name in the entry field.

You can also assign individual tags to each camera and thus provide the camera with additional information. Cameras in the Server overview can then be filtered by their tags to only show cameras which have the selected tags.
Camera type

Furthermore, you need to select the camera type from the camera type list. The following camera types are available:

Analog cameras

  • Picolo Diligent for analog cameras connected to ibaCapture Server over frame grabber cards of type Picolo Diligent.

  • Picolo Ux H264 analog cameras connected to ibaCapture Server over frame grabber cards of type Picolo Ux H264 (x = 4 or 8).

Network cameras

  • Axis for IP cameras from Axis

  • ONVIF compatible device for network cameras or imaging devices supporting the ONVIF standard.

  • RTSP source for cameras or other video sources supporting RTSP (Real Time Streaming Protocol).

Virtual cameras

  • ibaCapture-ScreenCam: for virtual cameras for recording HMI screens.

  • ibaVision video output for virtual cameras for recording output videos from ibaVision.

GigE Vision cameras

  • Pleora eBUS SDK: record videos from GigE Vision cameras with the Pleora eBUS SDK

  • Pleora eBUS SDK (Multicast slave): GigE Vision cameras can be configured and recorded as multicast slaves

  • Stemmer CVB: record videos from GigE Vision cameras with the Common Vision Blox as SDK

A detailed description of the handling of GigE Vision cameras can be found in the ibaCapture GigE manual.

Thermal cameras

  • Optris for thermal cameras from Optris

The option Enable live video when not recording and the setting of the camera recording mode are relevant if you want to control the recording of video files with ibaPDA. From ibaPDA version 6.29.1 and ibaCapture version 3.5.0 and higher, you can enable or disable the video recording with digital, virtual output signals from ibaPDA.

For further information regarding recording control with ibaPDA, see chapter Controlling the video recording with ibaPDA.
Camera recording mode

Camera recording mode

Description

Always (default)

By default, video is always recorded, irrespective of whether or not a recording control was enabled in ibaPDA. Even if the recording control is enabled and camera recording is disabled in ibaPDA, ibaCapture will record videos.

Record except when disabled by ibaPDA

Video is recorded unless the recording control is enabled in ibaPDA and recording is disabled for the relevant camera (output signal = true).

Don't record except when enabled by ibaPDA

Video is not recorded unless the recording control is enabled in ibaPDA and recording is enabled for the relevant camera (output signal = true).

Never

No videos are recorded by ibaCapture, irrespective of whether or not a recording control was enabled in ibaPDA. Only a live image is provided.

The following steps depend on the selected camera type. However, a connection to the camera has to be established.
Two user rule

With the two user rule, you can restrict camera access by requiring two users to log in to gain access to videos. The following settings are available:

  • Disabled (default)

  • Two users need to log in

  • Two users of different groups need to log in

If this option is enabled, another user is required to log in after the first user has logged in. Depending on the configuration selected, it may be necessary for the second user to belong to a different user group. See also Video viewing with active two user rule.

The two user rule offers the following security functions:

  • Prevents unauthorized or unilateral access to video material

  • Protects the privacy of individuals who may have been unintentionally recorded

  • Ensures accountability by requiring cross-approval from two authorized users

  • Grants access only when there is a justified and jointly confirmed need, reinforcing transparency and trust in sensitive operational environments