Back to Aurora Vision Library Lite website

You are here: Start » Camera Support » Photoneo » Photoneo_StopAcquisition

Photoneo_StopAcquisition


Header: ThirdPartySdk.h
Namespace: avl

Starts capturing data from a Photoneo camera.

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

Syntax

void avl::Photoneo_StopAcquisition
(
	Photoneo_State& ioState,
	const atl::Optional<atl::String> inDeviceID
)

Parameters

Name Type Default Description
Input will be modified ioState Photoneo_State& Object used to maintain state of the function.
Input value inDeviceID const Optional<String> NIL Device identification string

Remarks

PhoXi Control

PhoXi Control process needs to run for the filters to work.

Camera Setup

It is advisable to use Photoneo_StartAcquisition filter and setup inCaptureSettings with proper values. Some values might not be set to values the user expects and acquisition will fail or wait infinitely, when wrong trigger source or output type is selected.

Camera identification

When there is only one Photoneo 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 camera 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 Photoneo PhoXi Control software.

Photoneo PhoXi Control can be downloaded from the following website: https://www.photoneo.com/downloads/phoxi-control/

Supported PhoXi Control version for Aurora Vision Studio usage is 1.11.1.

Environment variable PHOXI_CONTROL_PATH which should point to the installation folder of PhoXi Control. PHO_LOG_FILES_DIR environment variable must contain a path to accessible folder. PHO_LOG_FILES_DIR is not set automatically after SDK installation. Manual configuration of this variable may be a requirement. Failure to meet these requirements may result in unexpected termination of the application.

Rebooting computer after SDK installation is mandatory.

See Also