150 CONTENTS
-2115 DEV_REQUEST_CANT_←-
BE_UNLOCKED
The unlock for a Request ob-
ject failed.
This might happen, if the Re-
quest is not locked at the
time of calling the unlock
function. It either has been
unlocked by the user already
or this request has never
been locked as the request
so far has not been used to
capture image data into its
buffer. Another reason for
this error might be that the
user tries to unlock a request
that is currently processed
by the device driver.[-2115]
-2116 DEV_INVALID_REQUES←-
T_NUMBER
The number for the Request
object is invalid.
The max. number for a Re-
quest object is the value of
the property RequestCount
in the SystemSettings list -
1.[-2116]
-2117 DEV_LOCKED_REQUES←-
T_IN_QUEUE
A Request that hasn't been
unlocked has been passed
back to the driver.
This error might occur if the
user requested an image
from the driver but hasn't un-
locked the Request that will
be used for this new image.[-
2117]
-2118 DEV_NO_FREE_REQUE←-
ST_AVAILABLE
The user requested a new
image, but no free Request
object is available to process
this request.
[-2118]
-2119 DEV_WAIT_FOR_REQU←-
EST_FAILED
The wait for a request failed. This might have several
reasons: the user waited for
an image, but no image has
been requested before.the
user waited for a requested
image, but the image is
still not ready(e.g. because
of a short timeout and a
long exposure time).a trig-
gered image has been re-
quested but no trigger sig-
nal has been detected within
the wait period.a plug and
play device(e.g. an U←-
SB device) has been un-
plugged and therefore can't
deliver images anymore. In
this case the 'state' prop-
erty should be checked to
find out if the device is still
present or not. [-2119]
-2120 DEV_UNSUPPORTED_P←-
ARAMETER
The user tried to get/set a
parameter, which is not sup-
ported by this device.
[-2120]
MATRIX VISION GmbH
To Next Page
Loading...