Impact Acquire SDK Java
|
Errors reported by the device manager. More...
Static Public Attributes | |
static final int | DEV_ACCESS_DENIED = acquireJNI.DEV_ACCESS_DENIED_get() |
The requested access to a device could not be granted. | |
static final int | DEV_CREATE_SETTING_FAILED = acquireJNI.DEV_CREATE_SETTING_FAILED_get() |
The creation of a setting failed. | |
static final int | DEV_HANDLE_INVALID = acquireJNI.DEV_HANDLE_INVALID_get() |
A driver function has been called with an invalid device handle. | |
static final int | DEV_INPUT_PARAM_INVALID = acquireJNI.DEV_INPUT_PARAM_INVALID_get() |
A driver function has been called but one or more of the input parameters are invalid. | |
static final int | DEV_INTERNAL_ERROR = acquireJNI.DEV_INTERNAL_ERROR_get() |
Some kind of internal error occurred in the device driver. | |
static final int | DEV_INVALID_REQUEST_NUMBER = acquireJNI.DEV_INVALID_REQUEST_NUMBER_get() |
The number for the mvIMPACT.acquire.Request object is invalid. | |
static final int | DEV_INVALID_RTC_NUMBER = acquireJNI.DEV_INVALID_RTC_NUMBER_get() |
The requested real time controller is not available for this device. | |
static final int | DEV_LOCKED_REQUEST_IN_QUEUE = acquireJNI.DEV_LOCKED_REQUEST_IN_QUEUE_get() |
A Request that hasn't been unlocked has been passed back to the driver. | |
static final int | DEV_NO_FREE_REQUEST_AVAILABLE = acquireJNI.DEV_NO_FREE_REQUEST_AVAILABLE_get() |
The user requested a new image, but no free mvIMPACT.acquire.Request object is available to process this request. | |
static final int | DEV_REQUEST_ALREADY_IN_USE = acquireJNI.DEV_REQUEST_ALREADY_IN_USE_get() |
This request is currently used by the driver. | |
static final int | DEV_REQUEST_BUFFER_INVALID = acquireJNI.DEV_REQUEST_BUFFER_INVALID_get() |
A request has been configured to use a user supplied buffer, but the buffer pointer associated with the request is invalid. | |
static final int | DEV_REQUEST_BUFFER_MISALIGNED = acquireJNI.DEV_REQUEST_BUFFER_MISALIGNED_get() |
A request has been configured to use a user supplied buffer, but the buffer pointer associated with the request has an incorrect alignment. | |
static final int | DEV_REQUEST_CANT_BE_UNLOCKED = acquireJNI.DEV_REQUEST_CANT_BE_UNLOCKED_get() |
The unlock for a mvIMPACT.acquire.Request object failed. | |
static final int | DEV_SENSOR_TYPE_ERROR = acquireJNI.DEV_SENSOR_TYPE_ERROR_get() |
There is no sensor found or the found sensor type is wrong or not supported. | |
static final int | DEV_UNKNOWN_ERROR = acquireJNI.DEV_UNKNOWN_ERROR_get() |
An unknown error occurred while processing a user called driver function. | |
static final int | DEV_UNSUPPORTED_PARAMETER = acquireJNI.DEV_UNSUPPORTED_PARAMETER_get() |
The user tried to get/set a parameter, which is not supported by this device. | |
static final int | DEV_WAIT_FOR_REQUEST_FAILED = acquireJNI.DEV_WAIT_FOR_REQUEST_FAILED_get() |
The wait for a request failed. | |
static final int | DEV_WRONG_INPUT_PARAM_COUNT = acquireJNI.DEV_WRONG_INPUT_PARAM_COUNT_get() |
A function has been called with an invalid number of input parameters. | |
static final int | DMR_ACQUISITION_ENGINE_BUSY = acquireJNI.DMR_ACQUISITION_ENGINE_BUSY_get() |
An error returned when the user application attempts to start the acquisition engine at a. | |
static final int | DMR_BUSY = acquireJNI.DMR_BUSY_get() |
An error returned when the user application attempts to perform any operation that currently for any reason cannot be started because something else already running. | |
static final int | DMR_CAMERA_DESCRIPTION_INVALID = acquireJNI.DMR_CAMERA_DESCRIPTION_INVALID_get() |
A function call was associated with a camera description, that is invalid. | |
static final int | DMR_CAMERA_DESCRIPTION_INVALID_PARAMETER = acquireJNI.DMR_CAMERA_DESCRIPTION_INVALID_PARAMETER_get() |
One or more of the camera descriptions parameters are invalid for the grabber it is used with. | |
static final int | DMR_DEV_CANNOT_OPEN = acquireJNI.DMR_DEV_CANNOT_OPEN_get() |
The specified device couldn't be initialized. | |
static final int | DMR_DEV_NOT_FOUND = acquireJNI.DMR_DEV_NOT_FOUND_get() |
The specified device can't be found. | |
static final int | DMR_DEV_REQUEST_CREATION_FAILED = acquireJNI.DMR_DEV_REQUEST_CREATION_FAILED_get() |
A request object couldn't be created. | |
static final int | DMR_DEV_REQUEST_QUEUE_EMPTY = acquireJNI.DMR_DEV_REQUEST_QUEUE_EMPTY_get() |
The devices request queue is empty. | |
static final int | DMR_DRV_ALREADY_IN_USE = acquireJNI.DMR_DRV_ALREADY_IN_USE_get() |
The device is already in use. | |
static final int | DMR_DRV_CANNOT_OPEN = acquireJNI.DMR_DRV_CANNOT_OPEN_get() |
A device could not be initialized. | |
static final int | DMR_EXECUTION_FAILED = acquireJNI.DMR_EXECUTION_FAILED_get() |
The execution of a method object or reading/writing to a feature failed. | |
static final int | DMR_EXECUTION_PROHIBITED = acquireJNI.DMR_EXECUTION_PROHIBITED_get() |
The user is not permitted to perform the requested operation. | |
static final int | DMR_EXPORTED_SYMBOL_NOT_FOUND = acquireJNI.DMR_EXPORTED_SYMBOL_NOT_FOUND_get() |
One or more symbols needed in a detected driver library couldn't be resolved. | |
static final int | DMR_FEATURE_NOT_AVAILABLE = acquireJNI.DMR_FEATURE_NOT_AVAILABLE_get() |
The feature in question is (currently) not available for this device or driver. | |
static final int | DMR_FILE_ACCESS_ERROR = acquireJNI.DMR_FILE_ACCESS_ERROR_get() |
A general error returned whenever there has been a problem with accessing a file. | |
static final int | DMR_FILE_NOT_FOUND = acquireJNI.DMR_FILE_NOT_FOUND_get() |
The specified file can't be found. | |
static final int | DMR_FUNCTION_NOT_IMPLEMENTED = acquireJNI.DMR_FUNCTION_NOT_IMPLEMENTED_get() |
A called function or accessed feature is not available for this device. | |
static final int | DMR_INIT_FAILED = acquireJNI.DMR_INIT_FAILED_get() |
The device manager couldn't be initialized. | |
static final int | DMR_INPUT_BUFFER_TOO_SMALL = acquireJNI.DMR_INPUT_BUFFER_TOO_SMALL_get() |
The user allocated input buffer is too small to accommodate the result. | |
static final int | DMR_INTERNAL_ERROR = acquireJNI.DMR_INTERNAL_ERROR_get() |
Some kind of internal error occurred. | |
static final int | DMR_INVALID_LICENCE = acquireJNI.DMR_INVALID_LICENCE_get() |
The licence doesn't match the device it has been assigned to. | |
static final int | DMR_INVALID_PARAMETER = acquireJNI.DMR_INVALID_PARAMETER_get() |
An invalid parameter has been passed to a function. | |
static final int | DMR_INVALID_QUEUE_SELECTION = acquireJNI.DMR_INVALID_QUEUE_SELECTION_get() |
An error returned when the user application attempts to operate on an invalid queue. | |
static final int | DMR_LAST_VALID_ERROR_CODE = acquireJNI.DMR_LAST_VALID_ERROR_CODE_get() |
Defines the last valid error code value for device and device manager related errors. | |
static final int | DMR_LIBRARY_NOT_FOUND = acquireJNI.DMR_LIBRARY_NOT_FOUND_get() |
One or more needed libraries are not installed on the system. | |
static final int | DMR_NEWER_LIBRARY_REQUIRED = acquireJNI.DMR_NEWER_LIBRARY_REQUIRED_get() |
A suitable driver library to work with the device manager has been detected, but it is too old to work with this version of the mvDeviceManager library. | |
static final int | DMR_NO_ERROR = acquireJNI.DMR_NO_ERROR_get() |
The function call was executed successfully. | |
static final int | DMR_NOT_INITIALIZED = acquireJNI.DMR_NOT_INITIALIZED_get() |
The device manager or another module hasn't been initialized properly. | |
static final int | DMR_OUT_OF_MEMORY = acquireJNI.DMR_OUT_OF_MEMORY_get() |
An error returned when for any reason internal resources (memory, handles, ...) cannot be allocated. | |
static final int | DMR_PRELOAD_CHECK_FAILED = acquireJNI.DMR_PRELOAD_CHECK_FAILED_get() |
A pre-load condition for loading a device driver failed. | |
static final int | DMR_TIMEOUT = acquireJNI.DMR_TIMEOUT_get() |
A general timeout occurred. | |
static final int | DMR_WAIT_ABANDONED = acquireJNI.DMR_WAIT_ABANDONED_get() |
A wait operation has been aborted. | |
Errors reported by the device manager.
These are errors which might occur in connection with the device manager itself or while working with the single devices.
|
static |
The requested access to a device could not be granted.
There are multiple reasons for this error code. Detailed information can be found in the *.log-file.
POSSIBLE CAUSES:
• an application tries to access a device exclusively that is already open in another process
• a network device has already been opened with control access from another system and the current system also tries to establish control access to the device
• an application tried to execute a function that is currently not available
• an application tries to write to a read-only location.
|
static |
The creation of a setting failed.
This can either happen, when a setting with the same name as the one the user tried to create already exists or if the system can't allocate memory for the new setting.
|
static |
A driver function has been called with an invalid device handle.
|
static |
A driver function has been called but one or more of the input parameters are invalid.
There are several possible reasons for this error:
• an unassigned pointer has been passed to a function, that requires a valid pointer.
• one or more of the passed parameters are of an incorrect type.
• one or more parameters contain an invalid value (e.g. a filename that points to a file that can't be found, a value, that is larger or smaller than the allowed values.
• within the current setup one or more parameters impose restrictions on the requested operation that don't allow its execution.
|
static |
Some kind of internal error occurred in the device driver.
More information can be found in the *.log-file or the debug output.
|
static |
The number for the mvIMPACT.acquire.Request object is invalid.
The max. number for a mvIMPACT.acquire.Request object is the value of the property RequestCount in the mvIMPACT.acquire.SystemSettings list - 1.
|
static |
The requested real time controller is not available for this device.
|
static |
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 unlocked the mvIMPACT.acquire.Request that will be used for this new image.
|
static |
The user requested a new image, but no free mvIMPACT.acquire.Request object is available to process this request.
|
static |
This request is currently used by the driver.
This error may occur if the user tries to send a certain request object to the driver by a call to the corresponding image request function.
|
static |
A request has been configured to use a user supplied buffer, but the buffer pointer associated with the request is invalid.
|
static |
A request has been configured 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
|
static |
The unlock for a mvIMPACT.acquire.Request object failed.
This might happen, if the mvIMPACT.acquire.Request 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.
|
static |
There is no sensor found or the found sensor type is wrong or not supported.
|
static |
An unknown error occurred while processing a user called driver function.
|
static |
The user tried to get/set a parameter, which is not supported by this device.
|
static |
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 triggered image has been requested but no trigger signal has been detected within the wait period.
• A plug and play device(e.g. an USB device) has been unplugged and therefore can't deliver images anymore. In this case the 'state' property should be checked to find out if the device is still present or not.
|
static |
A function has been called with an invalid number of input parameters.
|
static |
An error returned when the user application attempts to start the acquisition engine at a.
time, where it is already running.
|
static |
An error returned when the user application attempts to perform any operation that currently for any reason cannot be started because something else already running.
The log-output will provide additional information.
|
static |
A function call was associated with a camera description, that is invalid.
One possible reason might be, that the camera description has been deleted(driver closed?).
|
static |
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. Detailed information can be found in the *.log-file.
POSSIBLE CAUSES:
• The TapsXGeometry or TapsYGeometry parameter of the selected camera description cannot be used with a user defined AOI.
• A scan standard 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.
|
static |
The specified device couldn't be initialized.
|
static |
The specified device can't be found.
This error occurs either if an invalid device ID has been passed to the device manager or if the caller tried to close a device which currently isn't initialized.
|
static |
A request object couldn't be created.
The creation of a request object failed. This might e.g. happen, if the system runs extremely low on memory.
|
static |
The devices request queue is empty.
This error e.g. occurs if the user waits for an image request to become available at a result queue without having send an image request to the device before.
It might also arise when trying to trigger an image with a software trigger mechanism before the acquisition engine has been completely started. In this case a small delay and then again calling the software trigger function will succeed.
|
static |
The device is already in use.
This error e.g. will occur if this or another process has initialized this device already and an application tries to open the device once more or if a certain resource is available only once but shall be used twice.
|
static |
A device could not be initialized.
In this case the log-file will contain detailed information about the source of the problem.
|
static |
The execution of a method object or reading/writing to a feature failed.
More information can be found in the log-file.
|
static |
The user is not permitted to perform the requested operation.
This e.g. might happen if the user tried to delete user data without specifying the required password.
|
static |
One or more symbols needed in a detected driver library couldn't be resolved.
In most cases this is an error handled internally. So the user will not receive this error code as a result of a call to an API function. However when the user tries to get access to an IMPACT buffer type while the needed IMPACT Base libraries are not installed on the target system this error code also might be returned to the user.
|
static |
The feature in question is (currently) not available for this device or driver.
This might be because another feature currently blocks the one in question from being accessible. More information can be found in the *.log-file or the debug output.
|
static |
A general error returned whenever there has been a problem with accessing a file.
There can be multiple reasons for this error and a detailed error message will be sent to the log-output whenever this error code is returned.
POSSIBLE CAUSES:
• The driver tried to modify a file, for which it has no write access.
• The driver tried to read from a file, for which it has no read access.
• ...
|
static |
The specified file can't be found.
This might e.g. happen if the current working directory doesn't contain the file specified.
|
static |
A called function or accessed feature is not available for this device.
|
static |
The device manager couldn't be initialized.
This is an internal error.
|
static |
The user allocated input buffer is too small to accommodate the result.
|
static |
Some kind of internal error occurred.
More information can be found in the *.log-file or the debug output.
|
static |
The licence doesn't match the device it has been assigned to.
When e.g. upgrading a device feature each licence file is bound to a certain device. If the device this file has been assigned to has a different serial number then the one used to create the licence this error will occur.
|
static |
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 context.
|
static |
An error returned when the user application attempts to operate on an invalid queue.
|
static |
Defines the last valid error code value for device and device manager related errors.
|
static |
One or more needed libraries are not installed on the system.
|
static |
A suitable driver library to work with the device manager has been detected, but it is too old to work with this version of the mvDeviceManager library.
This might happen if two different drivers have been installed on the target system and one introduces a newer version of the device manager that is not compatible with the older driver installed on the system. In this case this error message will be written into the log-file together with the name of the library that is considered to be too old.
The latest drivers will always be available online under https://www.balluff.com. There will always be an updated version of the library considered to be too old for download from here.
|
static |
The function call was executed successfully.
|
static |
The device manager or another module hasn't been initialized properly.
This error occurs if the user tries e.g. to close the device manager without having 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
|
static |
An error returned when for any reason internal resources (memory, handles, ...) cannot be allocated.
The log-output will provide additional information.
|
static |
A pre-load condition for loading a device driver failed.
Certain device drivers may depend on certain changes applied to the system in order to operate correctly. E.g. a device driver might need a certain environment variable to exist. When the device manager tries to load a device driver it performs some basic checks to detect problems like this. When one of these checks fails the device manager will not try to load the device driver and an error message will be written to the selected log outputs.
|
static |
A general timeout occurred.
This is the typical result of functions that wait for some condition to be met with a timeout among their parameters.
More information can be found in the *.log-file or the debug output.
|
static |
A wait operation has been aborted.
This e.g. might occur if the user waited for some message to be returned by the driver and the device driver has been closed within another thread. In order to inform the user that this waiting operation terminated in an unusual wait, mvIMPACT.acquire.TDMR_ERROR.DMR_WAIT_ABANDONED will be returned then.