Back to FabImage Library website

You are here: Start » Function Reference » Camera Support » Ensenso » Ensenso_StartAcquisition

Ensenso_StartAcquisition


Header: ThirdPartySdk.h
Namespace: fil
Module: ThirdParty

Starts capturing data from an Ensenso camera.

Applications: Typically used for establishing camera connectivity before the first trigger event. Especially important for multiple-camera systems.

Syntax

void fil::Ensenso_StartAcquisition
(
	Ensenso_State& ioState,
	const ftl::Array<fil::EnsensoCameraInformation>& inDevices,
	const ftl::Optional<ftl::File>& inParametersFile,
	const bool inSoftwareTriggered
)

Parameters

Name Type Default Description
Input will be modified
 ioState Ensenso_State& Object used to maintain state of the function.
Input value
 inDevices const Array<EnsensoCameraInformation>& Structures identifying devices
Input value
 inParametersFile const Optional<File>& NIL Initial global parameters
Input value
 inSoftwareTriggered const bool False When true, capture will wait for GenerateSoftwareTrigger

Remarks

Initial parameters

Initial parameters are only set during capture start. To change parameters either restart the stream, or use appropriate Set/Get filters.

Camera identification

When there is only one Ensenso camera connected, the field inDevices can be set to Auto. In this situation, the first available camera will be used.

inDevices can be used to pick one or many of multiple cameras connected to the computer.

Camera driver software

This filter is intended to cooperate with cameras using their vendor's SDK. In order to connect with the camera, it is required to install Ensenso SDK software, and uEye driver (same as in IDS camera filters)

Ensenso SDK can be downloaded from the following website: https://www.ensenso.com/support/sdk-download/

uEye driver can be downloaded from the following website: https://en.ids-imaging.com/download-ueye.html

Recommended Ensenso SDK version for FabImage Studio usage is 2.2 and uEye driver 4.90.

Multithreaded environment

This function is not guaranteed to be thread-safe. When used in multithreaded environment, it has to be manually synchronized.

See Also