USB 2.0 USB 3.x GigE |
USB 2.0 USB 3.x GigE |
Syntax
INT is_FreeImageMem (HIDS hCam, char* pcMem, INT nMemId)
Description
is_FreeImageMem() releases an image memory that was allocated using is_AllocImageMem() and removes it from the driver management.
If the memory was not allocated using an SDK function, you need to call is_FreeImageMem() as well. Otherwise, there may be errors when the driver keeps trying to access this memory. This does however not release the memory. So you need to make sure that the memory will be released again. |
If image memories are locked by the user and are thus signaled as used, the image memories cannot be released. Therefore, before calling is_FreeImageMem(), image memories locked using is_LockSeqBuf() has to be unlocked using is_UnlockSeqBuf() first.
Input parameters
hCam |
Camera handle |
pcMem |
Points to the starting address of the memory (e.g. set in the is_AllocImageMem() function) |
nMemId |
ID of this memory |
Return values
IS_CANT_ADD_TO_SEQUENCE |
The image memory is already included in the sequence and cannot be added again. |
IS_CANT_CLEANUP_MEMORY |
The driver could not release the allocated memory. |
IS_CANT_COMMUNICATE_WITH_DRIVER |
Communication with the driver failed because no driver has been loaded. |
IS_CANT_OPEN_DEVICE |
An attempt to initialize or select the camera failed (no camera connected or initialization error). |
IS_INVALID_CAMERA_HANDLE |
Invalid camera handle |
IS_INVALID_MEMORY_POINTER |
Invalid pointer or invalid memory ID |
IS_INVALID_PARAMETER |
One of the submitted parameters is outside the valid range or is not supported for this sensor or is not available in this mode. |
IS_IO_REQUEST_FAILED |
An IO request from the uEye driver failed. Possibly the versions of the ueye_api.dll (API) and the driver file (ueye_usb.sys or ueye_eth.sys) do not match. |
IS_NO_SUCCESS |
General error message |
IS_SUCCESS |
Function executed successfully |
Related functions