Back to Aurora Vision Library website

You are here: Start » Function Reference » Camera Support » The Imaging Source » ICImagingControl_EnableExternalTrigger

ICImagingControl_EnableExternalTrigger


Header: ThirdPartySdk.h
Namespace: avl
Module: ThirdParty

Controls camera external trigger.

Syntax

void avl::ICImagingControl_EnableExternalTrigger
(
	ICImagingControlState& ioState,
	const atl::Optional<const atl::String&>& inDeviceID,
	bool inEnable
)

Parameters

Name Type Default Description
Input will be modified ioState ICImagingControlState& Object used to maintain state of the function.
Input value inDeviceID const Optional<const String&>& NIL Serial number, display name, unique name or base name of the camera
Input value inEnable bool External trigger state

Remarks

Camera driver software

This filter is intended to cooperate with a camera using its vendor SDK. To be able to connect to a camera, it is required to install ICImagingControl SDK software. Currently Aurora Vision Studio requires ICImagingControl SDK version 3.5.7.

Proper camera drivers and ICImagingControl SDK (IC Imaging Control .NET Component, C++ Class Library ) can be downloaded from the following website: https://www.theimagingsource.com/en-us/support/download/. To work with the Imaging Source SDK you need to install SDK on the target machine or copy manually the .dll files from the Documents\IC Imaging Control 3.5\redist\c++\win32\ directory on your computer (or Documents\IC Imaging Control 3.5\redist\c++\x64\ if you use Aurora Vision Studio x64) and add them to the Aurora Vision Studio directory in Program Files.

Camera identification

When there is only one camera connected to the computer, field inDeviceID can be set to Auto. In such case, the first available camera will be found and connected.

inDeviceID can be used to pick one of multiple cameras connected to the computer. inDeviceID can be set to:

  • serial number,
  • display name,
  • unique name,
  • base name of the camera.

Multithreaded environment

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

See Also