- Generated on Thu Dec 19 2024 18:45:19
|
Impact Acquire SDK .NET
|
| Numerical Value | String Representation | Brief Description | Detailed Description |
| -2000 | PROPHANDLING_NOT_A_LIST | This component is not a list. | This component is not a list. A list operation for this component has been called but this component does not reference a list. |
| -2001 | PROPHANDLING_NOT_A_PROPERTY | This component is not a property. | This component is not a property. A property operation for this component has been called but this component does not reference a property. |
| -2002 | PROPHANDLING_NOT_A_METHOD | This component is not a method. | This component is not a method. A method operation for this component has been called but this component does not reference a method. |
| -2003 | PROPHANDLING_NO_READ_RIGHTS | The caller has no read rights for this component. | The caller has no read rights for this component. It has been tried to read data from this component, but the caller has no read rights for this component. |
| -2004 | PROPHANDLING_NO_WRITE_RIGHTS | The caller has no write rights for this component. | The caller has no write rights for this component. It has been tried to modify data of this component, but the caller has no write rights for this component. |
| -2005 | PROPHANDLING_NO_MODIFY_SIZE_RIGHTS | The caller can't modify the size of this component. | The caller can't modify the size of this component. It has been tried to modify the size of this list or the number of values stored by a property, but the caller doesn't have the required right to do this. This error will also be reported if the user tried to increase the number of values handled by a property above the maximum number of values it can handle. Therefore before resizing a property check if the new size might exceeds this maximum value by calling the appropriate function. |
| -2006 | PROPHANDLING_INCOMPATIBLE_COMPONENTS | The two involved components are not compatible. | The two involved components are not compatible. An operation requiring two compatible components has been called with two components, which are not compatible. |
| -2008 | PROPHANDLING_UNSUPPORTED_PARAMETER | One or more of the specified parameters are not supported by the function. | One or more of the specified parameters are not supported by the function. This error might also be generated if a certain feature is not available on the current platform. |
| -2009 | PROPHANDLING_SIZE_MISMATCH | Different sized value buffers have been passed. | Different sized value buffers have been passed. While trying to read value pairs the caller passed two different sized value buffers to a function while one is too small to hold all the information. |
| -2010 | PROPHANDLING_IMPLEMENTATION_MISSING | A feature that is not implemented so far has been requested. | A feature that is not implemented so far has been requested. The caller requested a feature, that hasn't been implemented so far. This error code is only provided for compatibility and will be set in very rare cases only. |
| -2011 | PROPHANDLING_ACCESSTOKEN_CREATION_FAILED | An access token object couldn't be created. | An access token object couldn't be created. This can either happen, because the caller has not the rights required to create an access token or because the system runs very low on memory. Deprecated: This error code currently is not used anywhere within this framework. It might be removed in a future version. |
| -2012 | PROPHANDLING_INVALID_PROP_VALUE | It has been tried to assign an invalid value to a property. | It has been tried to assign an invalid value to a property. This can either happen if the value lies above or below the min. or max. value for a property or when it has been tried to write a value to a property, which is not in the properties translation dictionary (if it defines one). To find out, which values are allowed for the property in question the user should • Check if the property defines a translation dictionary. • Check the allowed values within a translation dictionary if one is defined. • Check the min and max value for properties, that define limits. |
| -2013 | PROPHANDLING_PROP_TRANSLATION_TABLE_CORRUPTED | The properties translation table has been corrupted. | The properties translation table has been corrupted. The properties translation table has been corrupted for an unknown reason and can't be used anymore. |
| -2014 | PROPHANDLING_PROP_VAL_ID_OUT_OF_BOUNDS | Invalid value index. | Invalid value index. The caller tried to read a value from an invalid index from a property. Most properties store one value only, thus the only valid positive value index will be 0 (some negative index values are reserved for special values like e.g. the min/max value of a property). However some properties might store more than one value, thus the max. allowed index might be higher. The highest index allowed will always be the value count of a property minus one for properties with the mvIMPACT::acquire::cfFixedSize flag set. Other properties will automatically adjust the size once the user writes to an index out of bounds. |
| -2015 | PROPHANDLING_PROP_TRANSLATION_TABLE_NOT_DEFINED | This property doesn't define a translation table. | This property doesn't define a translation table. The caller tried to modify a translation table, that hasn't been defined for this property. |
| -2016 | PROPHANDLING_INVALID_PROP_VALUE_TYPE | An invalid value has been passed to the property. | An invalid value has been passed to the property. Although properties are quite tolerant regarding the allowed assignment for them some value types can't be used to write all properties. As an example assigning a float value to an integer property would result in this error. Another reason for this error might be when a user tried to access e.g. a float property with functions meant to be used for int properties. |
| -2017 | PROPHANDLING_PROP_VAL_TOO_LARGE | A too large value has been passed. | A too large value has been passed. One or more of the values the caller tried to write to the property are larger than the max. allowed value for this property. |
| -2018 | PROPHANDLING_PROP_VAL_TOO_SMALL | A too small value has been passed. | A too small value has been passed. One or more of the values the caller tried to write to the property are smaller than the min. allowed value for this property. |
| -2019 | PROPHANDLING_COMPONENT_NOT_FOUND | The specified component could not be found. | The specified component could not be found. |
| -2020 | PROPHANDLING_LIST_ID_INVALID | An invalid list has been referenced. | An invalid list has been referenced. |
| -2021 | PROPHANDLING_COMPONENT_ID_INVALID | An invalid component within a list has been referenced. | An invalid component within a list has been referenced. |
| -2022 | PROPHANDLING_LIST_ENTRY_OCCUPIED | The specified list index is occupied. | The specified list index is occupied. During the creation of a new component the caller tried the insert the newly created component into a list at a position already used to store another component. |
| -2023 | PROPHANDLING_COMPONENT_HAS_OWNER_ALREADY | The specified component already has an owner. | The specified component already has an owner. The caller tried to assign an owner to a component that already has an owner. An owner once defined can't be modified anymore. |
| -2024 | PROPHANDLING_COMPONENT_ALREADY_REGISTERED | It has been tried to register the same component at twice in the same list. | It has been tried to register the same component at twice in the same list. |
| -2025 | PROPHANDLING_LIST_CANT_ACCESS_DATA | The desired data can't be accessed or found. | The desired data can't be accessed or found. During loading or saving data this error can occur e.g. if it has been tried to import a setting from a location where the desired setting couldn't be found. Another reason for this error might be that the current user is not allowed to perform a certain operation on the desired data (e.g. a user tries to delete a setting that is stored with global scope but does not have elevated access rights). |
| -2026 | PROPHANDLING_METHOD_PTR_INVALID | The function pointer of the referenced method object is invalid. | The function pointer of the referenced method object is invalid. |
| -2027 | PROPHANDLING_METHOD_INVALID_PARAM_LIST | A method object has an invalid parameter list. | A method object has an invalid parameter list. |
| -2028 | PROPHANDLING_SWIG_ERROR | This indicates an internal error occurred within the SWIG generated wrapper code, when working under Python. | This indicates an internal error occurred within the SWIG generated wrapper code, when working under Python. |
| -2029 | PROPHANDLING_INVALID_INPUT_PARAMETER | A invalid input parameter has been passed to a function of this module. | A invalid input parameter has been passed to a function of this module. In most cases this might be a unassigned pointer, where a valid pointer to a user defined storage location was expected. |
| -2030 | PROPHANDLING_COMPONENT_NO_CALLBACK_REGISTERED | The user tried to modify a registered callback, but no callback has been registered for this component. | The user tried to modify a registered callback, but no callback has been registered for this component. |
| -2031 | PROPHANDLING_INPUT_BUFFER_TOO_SMALL | The user tried to read data into a user supplied storage location, but the buffer was too small to accommodate the result. | The user tried to read data into a user supplied storage location, but the buffer was too small to accommodate the result. |
| -2032 | PROPHANDLING_WRONG_PARAM_COUNT | The number of parameters is incorrect. | The number of parameters is incorrect. This error might occur if the user called a function with a variable number of input or output parameters and the number of parameters passed to the function does not match the number of required parameters. |
| -2033 | PROPHANDLING_UNSUPPORTED_OPERATION | The user tried to execute an operation, which is not supported by the component he is referring to. | The user tried to execute an operation, which is not supported by the component he is referring to. |
| -2034 | PROPHANDLING_CANT_SERIALIZE_DATA | The user tried to save(serialize) a property list without having the right to do this. | The user tried to save(serialize) a property list without having the right to do this. |
| -2035 | PROPHANDLING_INVALID_FILE_CONTENT | The user tried to use a file to update or create a component list, that does not contain valid data for this operation. | The user tried to use a file to update or create a component list, that does not contain valid data for this operation. This e.g. might happen, if the file does not contain valid XML data or XML data that is not well formed. |
| -2036 | PROPHANDLING_CANT_ALLOCATE_LIST | This error will occur when the modules internal representation of the tree structure does not allow the allocation of a new list. | This error will occur when the modules internal representation of the tree structure does not allow the allocation of a new list. In this case either new list can't be allocated. The only way to solve this problem is to delete another list. |
| -2037 | PROPHANDLING_CANT_REGISTER_COMPONENT | The referenced list has no space left to register this component at the desired position. | The referenced list has no space left to register this component at the desired position. There might however be an empty space within the list where this element could be registered, but no more components can be registered at the end of this list. |
| -2038 | PROPHANDLING_PROP_VALIDATION_FAILED | The user tried to assign a value to a property, that is invalid. | The user tried to assign a value to a property, that is invalid. This will result in a detailed error message in the log-file. This error might arise e.g. when a string property doesn't allow the string to contain numbers. In this case trying to set the properties value to 'blabla7bla' would cause this error. |
| -2099 | PROPHANDLING_LAST_VALID_ERROR_CODE | Defines the last valid error code value for the property module. | Defines the last valid error code value for the property module. |
| -2100 | DMR_DEV_NOT_FOUND | The specified device can't be found. | 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. |
| -2101 | DMR_INIT_FAILED | The device manager couldn't be initialized. | The device manager couldn't be initialized. This is an internal error. |
| -2102 | DMR_DRV_ALREADY_IN_USE | The device is already in use. | 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. |
| -2103 | DMR_DEV_CANNOT_OPEN | The specified device couldn't be initialized. | The specified device couldn't be initialized. |
| -2104 | DMR_NOT_INITIALIZED | The device manager or another module hasn't been initialized properly. | 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 |
| -2105 | DMR_DRV_CANNOT_OPEN | A device could not be initialized. | A device could not be initialized. In this case the log-file will contain detailed information about the source of the problem. |
| -2106 | DMR_DEV_REQUEST_QUEUE_EMPTY | The devices request queue is empty. | 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. |
| -2107 | DMR_DEV_REQUEST_CREATION_FAILED | A request object couldn't be created. | 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. |
| -2108 | DMR_INVALID_PARAMETER | An invalid parameter has been passed to a function. | 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. |
| -2109 | DMR_EXPORTED_SYMBOL_NOT_FOUND | One or more symbols needed in a detected driver library couldn't be resolved. | 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. |
| -2110 | DEV_UNKNOWN_ERROR | An unknown error occurred while processing a user called driver function. | An unknown error occurred while processing a user called driver function. |
| -2111 | DEV_HANDLE_INVALID | A driver function has been called with an invalid device handle. | A driver function has been called with an invalid device handle. |
| -2112 | DEV_INPUT_PARAM_INVALID | A driver function has been called but one or more of the input parameters are invalid. | 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. |
| -2113 | DEV_WRONG_INPUT_PARAM_COUNT | A function has been called with an invalid number of input parameters. | A function has been called with an invalid number of input parameters. |
| -2114 | DEV_CREATE_SETTING_FAILED | The creation of a setting failed. | 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. |
| -2115 | DEV_REQUEST_CANT_BE_UNLOCKED | The unlock for a mvIMPACT::acquire::Request object failed. | 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. |
| -2116 | DEV_INVALID_REQUEST_NUMBER | The number for the mvIMPACT::acquire::Request object is invalid. | 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. |
| -2117 | DEV_LOCKED_REQUEST_IN_QUEUE | A Request that hasn't been unlocked has been passed back to the driver. | 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. |
| -2118 | DEV_NO_FREE_REQUEST_AVAILABLE | The user requested a new image, but no free mvIMPACT::acquire::Request object is available to process this request. | The user requested a new image, but no free mvIMPACT::acquire::Request object is available to process this request. |
| -2119 | DEV_WAIT_FOR_REQUEST_FAILED | The wait for a request 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 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. |
| -2120 | DEV_UNSUPPORTED_PARAMETER | The user tried to get/set a parameter, which is not supported by this device. | The user tried to get/set a parameter, which is not supported by this device. |
| -2121 | DEV_INVALID_RTC_NUMBER | The requested real time controller is not available for this device. | The requested real time controller is not available for this device. |
| -2122 | DMR_INTERNAL_ERROR | Some kind of internal error occurred. | Some kind of internal error occurred. More information can be found in the *.log-file or the debug output. |
| -2123 | DMR_INPUT_BUFFER_TOO_SMALL | The user allocated input buffer is too small to accommodate the result. | The user allocated input buffer is too small to accommodate the result. |
| -2124 | DEV_INTERNAL_ERROR | Some kind of internal error occurred in the device driver. | Some kind of internal error occurred in the device driver. More information can be found in the *.log-file or the debug output. |
| -2125 | DMR_LIBRARY_NOT_FOUND | One or more needed libraries are not installed on the system. | One or more needed libraries are not installed on the system. |
| -2126 | DMR_FUNCTION_NOT_IMPLEMENTED | A called function or accessed feature is not available for this device. | A called function or accessed feature is not available for this device. |
| -2127 | DMR_FEATURE_NOT_AVAILABLE | The feature in question is (currently) not available for this device or driver. | 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. |
| -2128 | DMR_EXECUTION_PROHIBITED | The user is not permitted to perform the requested operation. | 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. |
| -2129 | DMR_FILE_NOT_FOUND | The specified file can't be found. | The specified file can't be found. This might e.g. happen if the current working directory doesn't contain the file specified. |
| -2130 | DMR_INVALID_LICENCE | The licence doesn't match the device it has been assigned to. | 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. |
| -2131 | DEV_SENSOR_TYPE_ERROR | There is no sensor found or the found sensor type is wrong or not supported. | There is no sensor found or the found sensor type is wrong or not supported. |
| -2132 | DMR_CAMERA_DESCRIPTION_INVALID | A function call was associated with a camera description, that is invalid. | 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?).
|
| -2133 | DMR_NEWER_LIBRARY_REQUIRED | 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. | 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.
|
| -2134 | DMR_TIMEOUT | A general timeout occurred. | 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.
|
| -2135 | DMR_WAIT_ABANDONED | A wait operation has been aborted. | 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::DMR_WAIT_ABANDONED will be returned then.
|
| -2136 | DMR_EXECUTION_FAILED | The execution of a method object or reading/writing to a feature failed. | The execution of a method object or reading/writing to a feature failed. More information can be found in the log-file.
|
| -2137 | DEV_REQUEST_ALREADY_IN_USE | This request is currently used by the driver | 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.
|
| -2138 | DEV_REQUEST_BUFFER_INVALID | A request has been configured to use a user supplied buffer, but the buffer pointer associated with the request is invalid. | A request has been configured to use a user supplied buffer, but the buffer pointer associated with the request is invalid.
|
| -2139 | DEV_REQUEST_BUFFER_MISALIGNED | A request has been configured to use a user supplied buffer, but the buffer pointer associated with the request has an incorrect alignment. | 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
|
| -2140 | DEV_ACCESS_DENIED | The requested access to a device could not be granted. | 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.
|
| -2141 | DMR_PRELOAD_CHECK_FAILED | A pre-load condition for loading a device driver failed. | 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.
|
| -2142 | DMR_CAMERA_DESCRIPTION_INVALID_PARAMETER | One or more of the camera descriptions parameters are invalid for the grabber it is used with. | 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.
|
| -2143 | DMR_FILE_ACCESS_ERROR | A general error returned whenever there has been a problem with accessing a file. | 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. • ...
|
| -2144 | DMR_INVALID_QUEUE_SELECTION | An error returned when the user application attempts to operate on an invalid queue. | An error returned when the user application attempts to operate on an invalid queue.
|
| -2145 | DMR_ACQUISITION_ENGINE_BUSY | An error returned when the user application attempts to start the acquisition engine at a | An error returned when the user application attempts to start the acquisition engine at a
|
| -2146 | DMR_BUSY | 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. | 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.
|
| -2147 | DMR_OUT_OF_MEMORY | An error returned when for any reason internal resources (memory, handles, ...) cannot be allocated. | An error returned when for any reason internal resources (memory, handles, ...) cannot be allocated. The log-output will provide additional information.
|
| -2199 | DMR_LAST_VALID_ERROR_CODE | Defines the last valid error code value for device and device manager related errors. | Defines the last valid error code value for device and device manager related errors. |