Skip to main content
Error codes help locate SDK, connection, and data-stream problems. Record the error code, SDK version, camera model, and device log before troubleshooting.
Do not troubleshoot by changing only the SDK version. Also confirm compatibility between the camera firmware, data-processing library, and development environment.

​
SDK error codes and development environment

Possible cause Unknown error. Resolution Export the device log and send it to MRDVS technical support.
Possible cause The function is not supported. Resolution The current device does not support this feature.
Possible cause Network communication error. Resolution Check the IP configuration, network cables, switch, and packet loss.
Possible cause An input parameter is invalid. Resolution Check the parameters passed to the interface.
Possible cause The device is reconnecting. Resolution
  1. Wait briefly and retry until the connection is restored.
    2. Check that the camera is powered on and the network connection is normal.
Possible cause The device failed or did not respond. Resolution Restart the application or camera and try again.
Possible cause The device version is too old. Resolution Upgrade the firmware.
Possible cause The API version is too old. Resolution Update the SDK.
Possible cause Exclusive-control permission could not be obtained. Resolution Only one primary client can control a camera. If the camera was not shut down normally, wait 3–5 s for the permission to be released.
Possible cause Device information could not be read. Resolution Check the device firmware version or contact MRDVS support.
Possible cause The requested image size does not match the stream. Resolution Close the device and open it again.
Possible cause Image parsing failed, often because the pixel format is incorrect. Resolution Open the device again.
Possible cause The camera is not connected. Resolution The application attempted to use a camera that was not open. Check the call order and confirm that the camera opened successfully.
Possible cause Camera initialization failed. Resolution Open the camera again.
Possible cause No camera, or no matching camera, was found. Resolution Check that the camera handle passed to the interface is valid.
Possible cause The file name, type, format, or path is invalid, or the file could not be opened. Resolution Check that the path is correct and that the file can be opened manually.
Possible cause CRC or MD5 verification failed during upload or download. Resolution Retry the transfer.
Possible cause The request timed out. Resolution Retry. Packet loss or a low camera frame rate may be responsible.
Possible cause Frames were lost, often in callback mode. Resolution Occasional loss may not require action. For frequent loss, check network bandwidth and buffering.
Possible cause The requested stream configuration could not be enabled. Resolution Versions before 2.4.9 did not allow all streams to be disabled. This error code is obsolete in later versions.
Possible cause No stream data was received. Resolution Use the camera-open troubleshooting steps for a missing data stream.
Possible cause The stream started but could not be parsed. Resolution Check the firmware version or contact MRDVS support.
Possible cause Image processing failed. Resolution Confirm that the Dataprocess image-processing library version is compatible.
Possible cause The requested setting is not allowed in continuous mode. Resolution In continuous mode, stop the stream before changing the ROI, multi-camera mode, alignment, or other stream-related settings. Set the camera mode first, then apply the setting.
Possible cause The image-processing library could not be loaded. Resolution Ensure that the Dataprocess dynamic library/shared object exists and is included in the library path. Run source install.sh.
Possible cause The function call order or prerequisite logic is invalid. Resolution Check the SDK log and adjust the call sequence. Common cases include:
1. Stop the stream before changing a setting that changes the image size.
2. Do not change image size in continuous mode.
3. Algorithm upload and built-in application algorithms are mutually exclusive.
4. Do not enable auto exposure when HDR is enabled.
5. Auto-exposure parameters depend on the auto-exposure state.
6. Trigger parameters depend on the trigger mode.
Possible cause The IP address is unreachable or the network is misconfigured. Resolution Confirm that the SDK host can ping the camera.
Possible cause RGB and ToF frames were not synchronized within the timeout window. Resolution When RGB-D synchronization is enabled, choose whether to discard the frame or ignore the warning based on whether synchronization or real-time data is more important for your application.
Possible cause The frame contains an interference signal from another camera. Resolution Based on the application, discard the frame or ignore the warning.
Possible cause On Linux, the library is not included in the environment path. Resolution Run source install.sh.
Possible cause The displayed image aspect ratio is incorrect.
Resolution Use the wrapper in the util directory. It links the camera SDK indirectly and avoids a direct library conflict.
Resolution Call DcGetBoolValue(handle, LX_BOOL_ENABLE_2D_STREAM, &test_rgb). A Lite camera returns that the feature is not supported.
Resolution The SDK synchronizes with PTP automatically on each interface call. No additional trigger is required.