98
-2103
DMR_DEV_CANNOT_
←
-
OPEN
The specified device couldn't
be initialized.
[-2103]
-2104
DMR_NOT_INITIALIZED
The device manager or an-
other module hasn't been
initialized properly.
This error occurs if the user
tries e.g.
to close the de-
vice manager without hav-
ing initialized it before or if
a library used internally or a
module or device associated
with that library has not been
initialized properly or if
[-2104]
-2105
DMR_DRV_CANNOT_
←
-
OPEN
A device could not be initial-
ized.
In this case the log-file will
contain detailed information
about the source of the prob-
lem.
[-2105]
-2106
DMR_DEV_REQUEST_
←
-
QUEUE_EMPTY
The devices request queue
is empty.
This error e.g. occurs if the
user waits for an image re-
quest to become available
at a result queue without
having send an image re-
quest to the device before.
It might also arise when try-
ing to trigger an image with
a software trigger mecha-
nism before the acquisition
engine has been completely
started. In this case a small
delay and then again calling
the software trigger function
will succeed.
[-2106]
-2107
DMR_DEV_REQUEST_
←
-
CREATION_FAILED
A request object couldn't be
created.
The creation of a request ob-
ject failed.
This might e.g.
happen, if the system runs
extremely low on memory.
[-2107]
-2108
DMR_INVALID_
←
-
PARAMETER
An invalid parameter has
been passed to a function.
This might e.g.
happen
if a function requiring a
pointer to a structure has
been passed an unassigned
pointer or if a value has been
passed, that is either too
large or too small in that con-
text.
[-2108]
MATRIX VISION GmbH
Summary of Contents for MATRIX VISION mvBlueNAOS
Page 1: ...mvBlueNAOS Technical Manual English Version 2 14...
Page 2: ......
Page 8: ......
Page 22: ...14 MATRIX VISION GmbH...
Page 183: ...1 18 Use Cases 175 Figure 2 Sample settings MATRIX VISION GmbH...
Page 286: ...278 Test setup front side MATRIX VISION GmbH...
Page 292: ...284 MATRIX VISION GmbH...