18.5 Error code list 153
-2139 DEV_REQUEST_BUFFE←-
R_MISALIGNED
A request has been config-
ured to use a user supplied
buffer, but the buffer pointer
associated with the request
has an incorrect alignment.
Certain devices need
aligned memory to perform
efficiently thus when a user
supplied buffer shall be
used to capture data into
this buffer must follow these
alignment constraints[-2139]
-2140 DEV_ACCESS_DENIED The requested access to a
device could not be granted.
This might e.g. happen if an
application tries to access a
device exclusively that is al-
ready open in another pro-
cess. This could also hap-
pen if a network device
has already been opened
with control access from an-
other system and the cur-
rent system also tries to es-
tablish control access to the
device.[-2140]
-2141 DMR_PRELOAD_CHEC←-
K_FAILED
A pre-load condition for load-
ing a device driver failed.
Certain device drivers may
depend on certain changes
applied to the system in or-
der to operate correctly. E.g.
a device driver might need a
certain environment variable
to exist. When the device
manager tries to load a de-
vice driver it performs some
basic checks to detect prob-
lems like this. When one of
these checks fails the device
manager will not try to load
the device driver and an er-
ror message will be written
to the selected log outputs.[-
2141]
-2142 DMR_CAMERA_DESCR←-
IPTION_INVALID_PARA←-
METER
One or more of the camera
descriptions parameters are
invalid for the grabber it is
used with.
There are multiple reasons
for this error code. De-
tailed information can be
found in the ∗.log-file.←-
POSSIBLE CAUSES: The
TapsXGeometry or TapsY←-
Geometry parameter of the
selected camera description
cannot be used with a user
defined AOI.A scan stan-
dard has been selected, that
is not supported by this
device.An invalid scan rate
has been selected.... This
error code will be returned
by frame grabbers only.[-
2142]
MATRIX VISION GmbH
To Next Page
Loading...