Contains convenience functions to control features understood by a devices custom command interpreter. More...

Inheritance diagram for CustomCommandGenerator:

Public Member Functions
	__init__ (self, *args)
	Constructs a new mvIMPACT.acquire.CustomCommandGenerator object.

	commandBufferSize (self)
	Returns the size of the command buffer for this device in bytes.

	commandBufferSizeUsed (self)
	Returns the amount of bytes of the command buffer currently used(thus the amount of bytes that await sending) for this device in bytes.

	discardCommandBuffer (self)
	Discards all pending custom commands to the device.

	modifySequencerSetValue (self, *args)
	Modifies a value of a certain sequencer set at runtime.

	queueSequencerSetValueModification (self, *args)
	Queues the modification of a value of a certain sequencer set at runtime.

	queueTransmissionRequest (self, *args)
	Request the transmission of an image with a certain timestamp in a different mode/ROI.

	requestTransmission (self, *args)
	Request the transmission of an image with a certain timestamp in a different mode/ROI.

	sendCommandBuffer (self)
	Applies all pending custom commands to the device.

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

Detailed Description

Contains convenience functions to control features understood by a devices custom command interpreter.

Note: Creating an instance of this class will only succeed when the device associated with this object supports the mvIMPACT.acquire.mvCustomData.mvCustomCommandBuffer feature. If the feature is not supported an exception will be raised!

This class will allow to create various special commands understood by some MATRIX VISION and Balluff imaging devices. For example an application can modify parameters in a running sequencer program without stopping the acquisition engine and/or the sequencer program (see mvIMPACT.acquire.SequencerControl and the corresponding use cases for details). This allows changes to be applied much faster than with a conventional approach which would work like this:

ac = acquire.AcquisitionControl(getDeviceReferenceFromSomewhere())
sc = acquire.SequencerControl(getDeviceReferenceFromSomewhere())
sc.sequencerMode.writeS("Off")
sc.sequencerConfigurationMode.writeS("On")
sc.sequencerSetSelector.write(2)
sc.sequencerSetLoad.call() # needed as otherwise other parameters in the set might get changed as well.
ac.exposureTime.write(20000)
sc.sequencerSetSave.call()
sc.sequencerConfigurationMode.writeS("Off")
sc.sequencerMode.writeS("On")

A single parameter in a defined sequencer set can be modified much faster at runtime like this:

ccg = acquire.CustomCommandGenerator(getDeviceReferenceFromSomewhere())
# change the exposure time in sequencer set 2 to 30000 us.
ccg.modifySequencerSetValue(2, acquire.sspExposureTime, 30000)

Attention: In a real world application the instance of mvIMPACT.acquire.CustomCommandGenerator should be a member of a class or stored elsewhere as constructing objects from the mvIMPACT.acquire namespace is taking time so this shouldn't be done for each command that shall be sent!

This class uses an internal command buffer which allows an application to send multiple change commands in a single packet. This can be achieved like this:

ccg = acquire.CustomCommandGenerator(getDeviceReferenceFromSomewhere())
# queue 2 parameter change requests
# change the \c AnalogAll gain in sequencer set 0 to 3.14 dB.
ccg.queueSequencerSetValueModification(0, acquire.sspGain_AnalogAll, 3.14)
# change the exposure time in sequencer set 1 to 20000 us.
ccg.queueSequencerSetValueModification(1, acquire.sspExposureTime, 20000)
# send the 2 modifications in a single package
ccg.sendCommandBuffer()

The command queue NEVER overflows. When no more data can be stored in the queue before queuing the next parameter change all the pending changes will be transmitted to the device. Calling mvIMPACT.acquire.CustomCommandGenerator.queueSequencerSetValueModification and mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer directly afterwards is equivalent to call mvIMPACT.acquire.CustomCommandGenerator.modifySequencerSetValue. So the previous example can also be rewritten like this:

ccg = acquire.CustomCommandGenerator(getDeviceReferenceFromSomewhere ())
# queue 2 parameter change requests
# change the \c AnalogAll gain in sequencer set 0 to 3.14 dB.
ccg.queueSequencerSetValueModification(0, acquire.sspGain_AnalogAll, 3.14)
# change the exposure time in sequencer set 1 to 20000 us and send both requests to the device in a single packet.
ccg.modifySequencerSetValue(1, acquire.sspExposureTime, 20000)

Because there can never be an overflow of the command queue even this code is valid:

for i in range(0, 100, 2):
   # if the command buffer is full everything should be sent to the device thus no error should be returned here
   ccg.queueSequencerSetValueModification(i % 5, acquire.sspCounterDuration_Counter1, i * 100)
   ccg.queueSequencerSetValueModification(i % 5, acquire.sspExposureTime, ac.exposureTime.getMinValue() + (i * 10))

Apart from modifying sequencer sets at runtime some MATRIX VISION and Balluff imaging devices support the so called Smart Frame Recall feature. For more information about the feature itself please refer to the corresponding use case in the product documentation. There is also a C++ example called GenICamSmartFrameRecallUsage.cpp which can be read to get a first glimpse. The source code and the documentation of this example can be found in the C++ version of this documentation. The mvIMPACT.acquire.CustomCommandGenerator provides functions to request a full resolution version of an image based on a mvIMPACT.acquire.Request object containing an image with reduced resolution passed to it (internally the relevant piece of information is the timestamp of the image to request). To request an image an application can call one of the various versions of the mvIMPACT.acquire.CustomCommandGenerator.requestTransmission functions.

def getNextRandomValue(min, max):
   value = min + int((max - min + 1) * random.uniform(0, 1))
   if(value < min):
       return min
   if(value > max):
       return max
   return value
...
# switch on the smart frame recall feature
ac = acquire.AcquisitionControl( pDev )
ac.mvSmartFrameRecallEnable.write( acquire.bTrue )
# more code
pRequest = getRequestFromSomewhere()
# request the transmission of an arbitrary ROI of this image in full resolution
w = getNextRandomValue(1, pRequest.getImageWidth.read())
h = getNextRandomValue(1, pRequest.getImageHeight.read())
x = getNextRandomValue(0, pRequest.getImageWidth.read() - w)
y = getNextRandomValue(0, pRequest.getImageHeight.read() - h)
ccg.requestTransmission(pRequest, x, y, w, h, acquire.rtmFullResolution)

To allow the application to distinguish easily between images belonging to the reduced data stream and the ones that have been explicitly requested by the application the mvIMPACT.acquire.Request.chunkmvCustomIdentifier can be used. When requesting a full resolution ROI the application can tag the requested images with a custom identifier. This identifier is later returned in the chunk data of the image. The following example demonstrates how to use this feature:

ccg = acquire.CustomCommandGenerator(getDeviceReferenceFromSomewhere())
# switch on the smart frame recall feature
ac = acquire.AcquisitionControl(getDeviceReferenceFromSomewhere())
ac.mvSmartFrameRecallEnable.write(acquire.bTrue)
# the chunk mode must be switched on to use chunk data for processing:
cdc = acquire.ChunkDataControl(getDeviceReferenceFromSomewhere())
cdc.chunkModeActive.write(acquire.bTrue)
cdc.chunkSelector.writeS("Image")
cdc.chunkEnable.write(acquire.bTrue)
# enable the 'mvCustomIdentifier' chunk
cdc.chunkSelector.writeS("mvCustomIdentifier")
cdc.chunkEnable.write(acquire.bTrue)
# more code ...
pRequest = getRequestFromSomewhere()
customID = 42
if pRequest.chunkmvCustomIdentifier.read() == 0:
 # As the 'mvCustomIdentifier' is 0 this is a frame from the normal stream
 Rect r # assuming this to be a valid Python class for a rectangle
 if doesImageContainInteresstingData(r):
   # request the transmission of the interesting ROI this image in full resolution
   ccg.requestTransmission(pRequest, r.x, r.y, r.w, r.h, acquire.rtmFullResolution, customID)
elif pRequest.chunkmvCustomIdentifier.read() == customID:
  # As the 'mvCustomIdentifier' is 'customID' this is a frame explicitly requested by the application
  processImage(pRequest)
else:
  # some other ID (this however must have been set by the application as well)
# normal 'unlocking' code for requests should reside here!!
# more code...

Since: 2.18.0

Constructor & Destructor Documentation

◆ init()

__init__	(		self,
		*	args )

Constructs a new mvIMPACT.acquire.CustomCommandGenerator object.

Parameters

pDev	[in] A pointer to a mvIMPACT.acquire.Device object obtained from a mvIMPACT.acquire.DeviceManager object.
settingName	[in] The name of the driver internal setting to access with this instance. A list of valid setting names can be obtained by a call to mvIMPACT.acquire.FunctionInterface.getAvailableSettings, new settings can be created with the function mvIMPACT.acquire.FunctionInterface.createSetting

Member Function Documentation

◆ commandBufferSize()

commandBufferSize ( self )

Returns the size of the command buffer for this device in bytes.

Since: 2.18.0

Returns: The size of the command buffer for this device in bytes.

◆ commandBufferSizeUsed()

commandBufferSizeUsed ( self )

Returns the amount of bytes of the command buffer currently used(thus the amount of bytes that await sending) for this device in bytes.

Since: 2.18.0

Returns: The amount of bytes of the command buffer currently used(thus the amount of bytes that await sending) for this device in bytes.

◆ discardCommandBuffer()

discardCommandBuffer ( self )

Discards all pending custom commands to the device.

This function will discard all pending custom commands. After calling this function the pending command queue will be empty an can be filled with new commands.

Since: 2.18.0

◆ modifySequencerSetValue()

modifySequencerSetValue	(		self,
		*	args )

Modifies a value of a certain sequencer set at runtime.

OVERLOAD 1:

This is a convenience function combining a call to mvIMPACT.acquire.CustomCommandGenerator.queueSequencerSetValueModification directly followed by a call to mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer. Commands which have been queued before and have not yet been sent will be sent as well when calling this function.

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

sequencerSet	The index of the sequencer set to modify.
parameter	The parameter within the selected sequencer set to modify.
value	The new value the selected parameter within the selected sequencer set shall be set to.

OVERLOAD 2: Modifies a value of a certain sequencer set at runtime.

This is a convenience function combining a call to mvIMPACT.acquire.CustomCommandGenerator.queueSequencerSetValueModification directly followed by a call to mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer. Commands which have been queued before and have not yet been sent will be sent as well when calling this function.

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

sequencerSet	The index of the sequencer set to modify.
parameter	The parameter within the selected sequencer set to modify.
value	The new value the selected parameter within the selected sequencer set shall be set to.

◆ queueSequencerSetValueModification()

queueSequencerSetValueModification	(		self,
		*	args )

Queues the modification of a value of a certain sequencer set at runtime.

OVERLOAD 1:

This function queues a single parameter modification of a selected sequencer set. The actual modification will not become effective until mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer is called. With this function multiple modifications can be sent to a device at once. When the new command does not fit inside the internal command queue any more all pending commands will be sent to the device before the new one is put into the queue.

See also: mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

sequencerSet	The index of the sequencer set to modify.
parameter	The parameter within the selected sequencer set to modify.
value	The new value the selected parameter within the selected sequencer set shall be set to.

OVERLOAD 2: Queues the modification of a value of a certain sequencer set at runtime.

This function queues a single parameter modification of a selected sequencer set. The actual modification will not become effective until mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer is called. With this function multiple modifications can be sent to a device at once. When the new command does not fit inside the internal command queue any more all pending commands will be sent to the device before the new one is put into the queue.

See also: mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

sequencerSet	The index of the sequencer set to modify.
parameter	The parameter within the selected sequencer set to modify.
value	The new value the selected parameter within the selected sequencer set shall be set to.

◆ queueTransmissionRequest()

queueTransmissionRequest	(		self,
		*	args )

Request the transmission of an image with a certain timestamp in a different mode/ROI.

OVERLOAD 1:

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in a different mode/resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.1

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

timestamp_us	[in] The timestamp of the mvIMPACT.acquire.Request object shall be transmitted again.
offsetX	[in] The X-offset of the ROI of the image that shall be transmitted within the current image.
offsetY	[in] The Y-offset of the ROI of the image that shall be transmitted within the current image.
width	[in] The width of the ROI of the image that shall be transmitted within the current image.
height	[in] The height of the ROI of the image that shall be transmitted within the current image.
mode	[in] The mode in which this image shall be transmitted.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 2: Request the transmission of an image currently associated with the Request object in a different mode/ROI.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in a different mode/resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.1

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
offsetX	[in] The X-offset of the ROI of the image that shall be transmitted within the current image.
offsetY	[in] The Y-offset of the ROI of the image that shall be transmitted within the current image.
width	[in] The width of the ROI of the image that shall be transmitted within the current image.
height	[in] The height of the ROI of the image that shall be transmitted within the current image.
mode	[in] The mode in which this image shall be transmitted.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 3: Request the transmission of an image currently associated with the Request object in a different mode/ROI.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in a different mode/resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.1

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
offsetX	[in] The X-offset of the ROI of the image that shall be transmitted within the current image.
offsetY	[in] The Y-offset of the ROI of the image that shall be transmitted within the current image.
width	[in] The width of the ROI of the image that shall be transmitted within the current image.
height	[in] The height of the ROI of the image that shall be transmitted within the current image.
mode	[in] The mode in which this image shall be transmitted.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 4: Request the transmission of an image currently associated with the Request object in a different mode/ROI.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in a different mode/resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.1

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
offsetX	[in] The X-offset of the ROI of the image that shall be transmitted within the current image.
offsetY	[in] The Y-offset of the ROI of the image that shall be transmitted within the current image.
width	[in] The width of the ROI of the image that shall be transmitted within the current image.
height	[in] The height of the ROI of the image that shall be transmitted within the current image.
mode	[in] The mode in which this image shall be transmitted.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 5: Request the transmission of an image currently associated with the Request object in full resolution.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to queue the transmission request of the image currently associated with pRequest in full resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

The actual transmission request will not be sent to the device until mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer is called. With this function multiple commands can be sent to a device at once. When the new command does not fit inside the internal command queue any more all pending commands will be sent to the device before the new one is put into the queue.

See also: mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer

Since: 2.18.1

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 6: Request the transmission of an image currently associated with the Request object in full resolution.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to queue the transmission request of the image currently associated with pRequest in full resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

The actual transmission request will not be sent to the device until mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer is called. With this function multiple commands can be sent to a device at once. When the new command does not fit inside the internal command queue any more all pending commands will be sent to the device before the new one is put into the queue.

See also: mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer

Since: 2.18.1

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

◆ requestTransmission()

requestTransmission	(		self,
		*	args )

Request the transmission of an image with a certain timestamp in a different mode/ROI.

OVERLOAD 1:

This is a convenience function combining a call to mvIMPACT.acquire.CustomCommandGenerator.queueTransmissionRequest directly followed by a call to mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer. Commands which have been queued before and have not yet been sent will be sent as well when calling this function.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in a different mode/resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.1

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

timestamp_us	[in] The timestamp of the mvIMPACT.acquire.Request object shall be transmitted again.
offsetX	[in] The X-offset of the ROI of the image that shall be transmitted within the current image.
offsetY	[in] The Y-offset of the ROI of the image that shall be transmitted within the current image.
width	[in] The width of the ROI of the image that shall be transmitted within the current image.
height	[in] The height of the ROI of the image that shall be transmitted within the current image.
mode	[in] The mode in which this image shall be transmitted.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 2: Request the transmission of an image currently associated with the Request object in a different mode/ROI.

This is a convenience function combining a call to mvIMPACT.acquire.CustomCommandGenerator.queueTransmissionRequest directly followed by a call to mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer. Commands which have been queued before and have not yet been sent will be sent as well when calling this function.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in a different mode/resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
offsetX	[in] The X-offset of the ROI of the image that shall be transmitted within the current image.
offsetY	[in] The Y-offset of the ROI of the image that shall be transmitted within the current image.
width	[in] The width of the ROI of the image that shall be transmitted within the current image.
height	[in] The height of the ROI of the image that shall be transmitted within the current image.
mode	[in] The mode in which this image shall be transmitted.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 3: Request the transmission of an image currently associated with the Request object in a different mode/ROI.

This is a convenience function combining a call to mvIMPACT.acquire.CustomCommandGenerator.queueTransmissionRequest directly followed by a call to mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer. Commands which have been queued before and have not yet been sent will be sent as well when calling this function.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in a different mode/resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
offsetX	[in] The X-offset of the ROI of the image that shall be transmitted within the current image.
offsetY	[in] The Y-offset of the ROI of the image that shall be transmitted within the current image.
width	[in] The width of the ROI of the image that shall be transmitted within the current image.
height	[in] The height of the ROI of the image that shall be transmitted within the current image.
mode	[in] The mode in which this image shall be transmitted.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 4: Request the transmission of an image currently associated with the Request object in a different mode/ROI.

This is a convenience function combining a call to mvIMPACT.acquire.CustomCommandGenerator.queueTransmissionRequest directly followed by a call to mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer. Commands which have been queued before and have not yet been sent will be sent as well when calling this function.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in a different mode/resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
offsetX	[in] The X-offset of the ROI of the image that shall be transmitted within the current image.
offsetY	[in] The Y-offset of the ROI of the image that shall be transmitted within the current image.
width	[in] The width of the ROI of the image that shall be transmitted within the current image.
height	[in] The height of the ROI of the image that shall be transmitted within the current image.
mode	[in] The mode in which this image shall be transmitted.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 5: Request the transmission of an image currently associated with the Request object in full resolution.

This is a convenience function combining a call to mvIMPACT.acquire.CustomCommandGenerator.queueTransmissionRequest directly followed by a call to mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer. Commands which have been queued before and have not yet been sent will be sent as well when calling this function.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in full resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

OVERLOAD 6: Request the transmission of an image currently associated with the Request object in full resolution.

This is a convenience function combining a call to mvIMPACT.acquire.CustomCommandGenerator.queueTransmissionRequest directly followed by a call to mvIMPACT.acquire.CustomCommandGenerator.sendCommandBuffer. Commands which have been queued before and have not yet been sent will be sent as well when calling this function.

If mvIMPACT.acquire.AcquisitionControl.mvSmartFrameRecallEnable is set to mvIMPACT.acquire.bTrue this function can be used to request the transmission of the image currently associated with pRequest in full resolution. One use case would be to transmit every image taken by the sensor with a very coarse resolution e.g. by setting the properties mvIMPACT.acquire.ImageFormatControl.decimationHorizontal and/or mvIMPACT.acquire.ImageFormatControl.decimationVertical to values greater than 1. When then an algorithm finds something interesting within an image this function can be used to request the transmission of the very same image in full resolution for detailed processing.

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Parameters

pRequest	[in] A pointer to a mvIMPACT.acquire.Request object currently associated with the image that shall be transmitted again.
identifier	[in] A user defined identifier that shall be attached to the image that will be sent as a result of calling this function. This value will be written into the mvIMPACT.acquire.Request.chunkmvCustomIdentifier property so in order to actually benefit from this parameter the corresponding chunk must be enabled. See mvIMPACT.acquire.ChunkDataControl for details.

◆ sendCommandBuffer()

sendCommandBuffer ( self )

Applies all pending custom commands to the device.

This function will send all pending custom commands to a device. After calling this function the pending command queue will be empty an can be filled with new commands. Calling this function multiple times without queuing new commands after each send will have no effect!

Since: 2.18.0

Returns

mvIMPACT.acquire.DMR_NO_ERROR if successful.
A negative error code as listed here: Error code list .

Property Documentation

◆ thisown

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

static

Public Member Functions

Properties

Detailed Description

Constructor & Destructor Documentation

◆ __init__()

Member Function Documentation

◆ commandBufferSize()

◆ commandBufferSizeUsed()

◆ discardCommandBuffer()

◆ modifySequencerSetValue()

◆ queueSequencerSetValueModification()

◆ queueTransmissionRequest()

◆ requestTransmission()

◆ sendCommandBuffer()

Property Documentation

◆ thisown

◆ init()