If program issues remain unsolved after the above troubleshooting process, please record issue details or images about program exceptions, client version No., library name, and library version No., which can be accessed in Help > About on the client, and contact technical support.
The camera is not on the camera list of the client.
Possible Cause: Firewall may block the communication data of devices, which leads to the failure to identify the camera.
Solution: Disable all firewalls.
Opening the camera failed.
Possible Cause: The camera owns exclusive permission, and can only be accessed by one program. It may be occupied by a program or an app.
Solution: On the client, check if the camera is accessed by other programs or apps. If yes, close the background program or app to make the camera available.
Possible Cause: The camera is abnormally closed (usually in debug mode) due to the previous failure to close the camera or the previous failure to destroy the camera handle, and the heartbeat time is too long, which makes the camera still in occupied state.
Solution: Power off and restart the camera, or wait for the camera heartbeat to time out to release the resource of camera.
Possible Cause: Connecting the camera to the industrial PC failed. The camera IP address and the industrial PC IP address are not in the same network segment.
Solution: Edit the camera IP address to make it and the industrial PC IP address in the same network segment. In the camera list on the client, right-click the camera, and select Modify IP to edit the IP address.
Starting grabbing image failed.
Possible Cause: The memory of the industrial PC is not enough.
Solution: Check the system memory usage of the industrial PC. If the available memory is small, go to Settings > Buffer to reduce the value of Buffers for Getting Stream.
Possible Cause: The handle resources are not enough.
Solution: Check the handle quantity configuration, and increase the handle limit by executing ulimit –n 65535 command on the terminal.
Software trigger execution fails when executing software trigger command via calling SDK.
Possible Cause: The trigger source is not set to software trigger.
Solution: Before calling the SDK to execute the software trigger command, ensure the camera is in the software trigger mode, and the trigger source is set to software trigger.
The camera does not output the image.
Possible Cause: Camera configuration error. Trigger mode is disabled, or no trigger signal is provided for the camera.
Solution: Check camera configurations. Enable the trigger mode, and set a correct trigger source.
Blurry screen, lost frame, or gained frame is detected.
Possible Cause: There is packet loss due to insufficient bandwidth.
Solution: Use different GigE interfaces for multiple cameras. If one GigE interface is used by multiple cameras, it will lead to high bandwidth usage.
Possible Cause: Jumbo Frame of NIC is disabled, which leads to low data transmission efficiency.
Solution: Check MTU setting of the environment, and increase it to 9000.
Possible Cause: Adaptive Drop Frame is enabled on the client, and there is packet loss due to network issues. After Adaptive Drop Frame is enabled, when frame data loss is detected, the system will automatically drop the frame. If there are network issues such as network congestion, continuous blank screen will occur.
Solution: Go to Settings > Network on the client to disable Adaptive Drop Frame, check bandwidth usage, and optimize the network.
Possible Cause: For line scan cameras, the PartialImageOutPutMode is set to PartialImageDiscard. After PartialImageDiscard is selected, if the output image height is below the set value and the image is incomplete, the system will automatically discard the image.
Solution: Change PartialImageOutPutMode to other options, and check external trigger.
Possible Cause: External trigger is configured for the camera, but the trigger signal quantity is invalid, leading to the inadequate or excessive output images.
Solution: Check camera trigger configuration and trigger source.
Possible Cause: Due to not releasing buffer in time after calling the API for grabbing image, the SDK buffer is inadequate for storage of images sent from the camera, and there is frame loss.
Solution:
Error message is returned after calling MV_CC_GetImageBuffer(), and there is no data.
Possible Cause: Error occurred when the camera outputs images, and no image can be acquired by the API.
Solution: Check camera configuration and trigger source to ensure camera image output.
Possible Cause: API timeout is longer than image output time.
Solution: Increase the nMsec value of MV_CC_GetImageBuffer() to make the API timeout longer than image output time.
Possible Cause: There is not enough memory for SDK use. The image buffer that is used for image acquiring is not timely released.
Solution: After getting the image by calling MV_CC_GetImageBuffer(), timely call MV_CC_FreeImageBuffer() to release the image buffer.
Error occurred when calling MV_CC_HB_Decode().
Possible Cause: The image data sent to SDK is incomplete, which leads to the failure of image HB decoding.
Solution: Before calling MV_CC_HB_Decode(), check if there is packet loss by nLostPacket in MV_FRAME_OUT_INFO_EX . If yes, optimize the network.
The camera is abnormally offline.
Possible Causes: 1) There is network congestion. 2) NIC is in sleep mode. 3) The network interface is loose.
Solution: 1) Check network bandwidth usage, ad optimize the network. 2) Check network bandwidth, and change the power option to “never putting the computer in sleep mode”. 3) Check the network interface conditions.
Compilation error: ld:-lMvCameraControl cannot find libMvCameraControl library.
Possible Cause: After installing, environment variables do not take effect in the current console.
Solution: Troubleshoot if environment variables take effect, and the presence of the Lib library.
Compilation error: ld:-lMvCameraControl (with incompatible symbols)
Possible Cause: SDK version does not match that of hardware, or it is not supported by the toolchain.
Solution:
Check the current hardware environment and SDK version.
Check if the SDK header information matches with the system information.
Check the GCC version. Enter gcc -v in the console to get GCC version. Update the GCC version if it is earlier than the minimum required version. For more details, refer to the technical support.
This page provides the minimum required GCC version of each SDK.
| SDK Version | Minimum GCC Version |
|---|---|
| x86_64 | 4.8.5 |
| i386 | 4.4.7 |
| armhf | 4.8.2 |
| aarch64 | 4.9.4 |
| arm-none | 4.1.1 |
Opening the camera failed.
Possible Cause: Camera driver is not correctly installed, or it is recognized as driver of other manufacturers.
Solution：Check if the driver is correctly installed. If not, reinstall the driver. Input “lsusb” in the console, and check the corresponding device on the list.
Possible Cause: 1) An USB 2.0 cable is used to connect USB (2.0 or 3.0) interface and the device. 2) An USB 3.0 cable is used to connect USB 2.0 interface and the device.
Solution: Check the USB cable and interface to ensure the camera is connected to interface 3.0.
Possible Cause: The camera owns exclusive permission, and can only be accessed by one program.
Solution: On the client, check if the camera is accessed by other programs or apps. If yes, close the background program or app to make the camera available.
Possible Cause: There are libusb library version conflicts and symbol errors in Linux.
Solution: Check the current libusb dependency path of the U3V with ldd libMvUsb3vTL.so.
Abnormal image grabbing / frame loss / frame No. reset.
Possible Cause: There is data loss due to insufficient bandwidth of USB interface.
Solution:
Possible Cause: Stream channel and frame No. are reset due to stream channel data exception caused by EMC interference.
Solution: Check the device environment, reduce static electricity, and enhance anti-interference capability by using ring magnets.