Back to Aurora Vision Library Lite website

You are here: Start » Camera Support » IDS » IDS_ForceTrigger

IDS_ForceTrigger


Header: ThirdPartySdk.h
Namespace: avl

Forces software-controlled captures of an image while a capturing process triggered by hardware is in progress.

Syntax

void avl::IDS_ForceTrigger
(
	IDS_BaseState& ioState,
	const atl::Optional<atl::String>& inDeviceID
)

Parameters

Name Type Default Description
Input will be modified ioState IDS_BaseState& Object used to maintain state of the function.
Input value inDeviceID const Optional<String>& NIL Device serial number or user definable camera ID

Remarks

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 IDS SDK software.

IDS SDK can be downloaded from the following website: https://en.ids-imaging.com/downloads.html

To verify the driver installation, you can run IDS Camera Manager. If the camera was detected and you can see the view from the camera, you can use IDS SDK in Aurora Vision Studio.

Recommended IDS SDK version for Aurora Vision Studio usage is 4.96.1.

Camera identification

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

inDeviceID can be used to pick one of multiple cameras connected to the computer. inDeviceID should be set to device serial number or user definable camera ID.

Source code

In Professional edition this filter is open source. You can use this filter as reference when implementing support for your specific hardware. You can also modify this filter and add some additional functionality.

The source code is located in the directory:

Public Documents\Aurora Vision Studio 5.x Professional\Sources\UserFilters\IDS

Typically it is:

C:\Users\Public Documents\Aurora Vision Studio 5.x Professional\Sources\UserFilters\IDS 

Multithreaded environment

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

See Also