BasicDeviceSettings Class Reference

A base class for essential device related settings. More...

Inheritance diagram for BasicDeviceSettings:

Public Member Functions
	__init__ (self, *args)

Properties
	basedOn = property(lib_mvIMPACT_acquire.BasicDeviceSettings_basedOn_get, doc=)
	A string property (read-only) containing the name of the setting this setting is based on.
	imageRequestTimeout_ms = property(lib_mvIMPACT_acquire.BasicDeviceSettings_imageRequestTimeout_ms_get, doc=)
	An integer property defining the maximum time to wait for an image in ms.
	thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc="The membership flag")

Detailed Description

A base class for essential device related settings.

This class acts as a base class for essential device related settings. It only contains features that are available for every device.

Since

1.12.58

Constructor & Destructor Documentation

__init__()

__init__	(		self,
		*	args )

Reimplemented from ComponentCollection.

Reimplemented in BasicDeviceSettingsWithAOI, CameraSettingsBase, CameraSettingsVirtualDevice, CameraSettingsV4L2Device, CameraSettingsBlueDevice, CameraSettingsBlueFOX, CameraSettingsBlueCOUGAR, and CameraSettingsFrameGrabber.

Property Documentation

basedOn

basedOn = property(lib_mvIMPACT_acquire.BasicDeviceSettings_basedOn_get, doc=)

static

A string property (read-only) containing the name of the setting this setting is based on.

Since

1.12.67

imageRequestTimeout_ms

imageRequestTimeout_ms = property(lib_mvIMPACT_acquire.BasicDeviceSettings_imageRequestTimeout_ms_get, doc=)

static

An integer property defining the maximum time to wait for an image in ms.

Attention

Since Impact Acquire 2.32.0 the default value for this property has been changed! See Calling 'imageRequestWaitFor' Never Returns / An Application No Longer Terminates After Upgrading To Impact Acquire 2.32.0 Or Greater for details.

When this property is set to 0 the timeout never elapses. If the timeout this property defines elapses the currently processed request will be returned to the user even if no data has been captured so far. The result structure of the request object should be examined in that case. Also this should be considered as an error from the users point of view in which case he should clean up the acquisition queue by calling mvIMPACT.acquire.FunctionInterface.imageRequestReset. Afterwards the capture loop can be restarted.

Note

It is crucial to understand that this is a timeout PER REQUEST! The timespan taken into account for the measurement starts when the driver begins to capture data into this particular buffer! So when queuing 4 buffers with a timeout of 3000 ms each and no data being transmitted by the device for any reason will cause the last buffer to time out 3000*4 = 12000 ms AFTER the buffer has been queued and the acquisition has been started as the driver will wait for up to 3 seconds for each buffer that is being processed. When the device sends data this timeout does not affect the runtime behaviour at all. No additional delay is introduced by it when everything runs as planned.

thisown

thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc="The membership flag")

static