Balluff MATRIX VISION mvBlueNAOS Technical Manual page 108

100
-2115 DEV_REQUEST_CANT_
BE_UNLOCKED
-2116 DEV_INVALID_
REQUEST_NUMBER
-2117 DEV_LOCKED_
REQUEST_IN_QUEUE
-2118 DEV_NO_FREE_
REQUEST_AVAILABLE
-2119 DEV_WAIT_FOR_
REQUEST_FAILED
-2120 DEV_UNSUPPORTED_
PARAMETER
The unlock for a Request ob-
ject failed.
The number for the Request
object is invalid.
A Request that hasn't been
unlocked has been passed
back to the driver.
The user requested a new
image, but no free Request
object is available to process
this request.
The wait for a request failed.
The user tried to get/set a
parameter, which is not sup-
ported by this device.
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]
The max. number for a Re-
quest object is the value of
the property RequestCount
in the SystemSettings list - 1.
[-2116]
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]
This might have several
reasons: The user waited for
an image, but no image has
been requested before.
The user waited for a re-
quested image, but the im-
age is still not ready(e.g. be-
cause of a short timeout and
a long exposure time).
A triggered image has been
requested but no trigger sig-
nal has been detected within
the wait period.
A plug and play device(e.
g. an USB device) has
been unplugged and there-
fore can't deliver images
anymore. In this case the
'state' property should be
checked to find out if the de-
vice is still present or not.
[-2119]
[-2120]
MATRIX VISION GmbH