Error Codes

error: -1001

The possible causes and corresponding solutions are as follows:

  • Unable to find the specified camera

    The program could not find the camera with the specified serial number.

    There are various phenomena that can cause error: -1001, and the problem needs to be investigated based on the error message.

error: -1005

The possible causes and corresponding solutions are as follows:

  • The camera is occupied

    Please check if there are any other processes occupying the camera (such as the Percipio Viewer tool). If there are other processes occupying the camera, close the processes.

  • The USB cable is too long

    It is not recommended to use a USB cable that is too long (over 3 meters). Please try opening the camera after replacing it with a shorter cable.

  • The camera IP address and the host computer IP address are not in the same network segment

    If the IP address of the camera is not in the same network segment as the IP address of the host computer, the host computer can discover the camera across network segments, but may not be able to open it. In this case, you can modify the IP address of the camera or the IP address of the host computer. If you need to modify the IP address of the camera, please refer to Application Example: Set Camera IP.

error: -1014

Phenomenon 1

error: -1014 occurred when the camera was opened.

Possible causes and solutions

The possible causes and corresponding solutions are as follows:

  • The camera is occupied

    Please close any processes (like Percipio Viewer) that are occupying the camera on this computer or other host computers.

  • Third-party programs have been written into the camera

    Please contact Percipio technical support.

  • The camera IP address and the host computer IP address are not in the same network segment

    If the IP address of the camera is not in the same network segment as the IP address of the host computer, the host computer can discover the camera across network segments, but may not be able to open it. In this case, you can modify the IP address of the camera or the IP address of the host computer. If you need to modify the IP address of the camera, please refer to Application Example: Set Camera IP.

Phenomenon 2

error: -1014 occurred during image acquisition.

Possible causes and solutions

The possible causes and corresponding solutions are as follows:

  • The timeout in TYFetchFrame function is set too short.

    Please set the timeout time according to the camera’s image delay time, and it is recommended to be above 7000, unit: milliseconds.

    TYFetchFrame(hDevice, &frame, 7000);

  • Camera drops frames

    The troubleshooting method is the same as the abnormal camera frame rate. Please refer to What to do if the frame rate of a network camera is abnormal?

error: -1016

The possible causes and corresponding solutions are as follows:

  • The network camera is occupied

Please check if any other processes on the local computer (such as the Percipio Viewer Software) or other host computers are connecting to and occupying the camera. If the camera is being occupied, resolve the issue by releasing the camera.

  • Camera feature configuration error

For example, the features with writableAtRun≠"1" in the fetch_config.xml file of the camera must be set before calling TYStartCapture(), such as image resolution, work modes, etc.

If such features are set after TYStartCapture(), an error: -1016 will be reported when running the program.

  • Send a soft trigger command during busy time

    TL460-S1-E1 and FM851-S1-E2 will have a busy time after starting to capture images with TYStartCapture(). During this time, sending a software trigger command will result in an error: -1016.

    To solve the problem, choose one of the following methods:

    • Add a delay after calling TYStartCapture().

      MSLEEP(7000)

    • Modify the code as follows:

      while(TY_STATUS_BUSY == TYSendSoftTrigger(hDevice));

error: -1024

Identify the causes and the solutions

When encountering error: -1024, please troubleshoot the issue using the following methods:

  1. Choose one of the following ways to read the fw_err code:

    Method 1: Use SDK to read it

    1. Call the TYOpenDevice() interface, set as follows, and print fw_err code

      TY_FW_ERRORCODE fw_err;
TYOpenDevice(hIface, selectedDev.id, &hDevice,&fw_err);
LOGD("%x", fw_err);

    2. Compile and run the modified program, and read out the fw_err code.

    Method 2: Use Percipio Viewer to read it

    Please refer to the steps in Select the camera.

  2. Find the corresponding error message based on the fw_error code.

    typedef enum TY_FW_ERRORCODE_LIST:uint32_t
{
    TY_FW_ERRORCODE_CAM0_NOT_DETECTED       = 0x00000001,
    TY_FW_ERRORCODE_CAM1_NOT_DETECTED       = 0x00000002,
    TY_FW_ERRORCODE_CAM2_NOT_DETECTED       = 0x00000004,
    TY_FW_ERRORCODE_POE_NOT_INIT            = 0x00000008,
    TY_FW_ERRORCODE_RECMAP_NOT_CORRECT      = 0x00000010,
    TY_FW_ERRORCODE_LOOKUPTABLE_NOT_CORRECT = 0x00000020,
    TY_FW_ERRORCODE_DRV8899_NOT_INIT        = 0x00000040,
    TY_FW_ERRORCODE_CONFIG_NOT_FOUND        = 0x00010000,
    TY_FW_ERRORCODE_CONFIG_NOT_CORRECT      = 0x00020000,
    TY_FW_ERRORCODE_XML_NOT_FOUND           = 0x00040000,
    TY_FW_ERRORCODE_XML_NOT_CORRECT         = 0x00080000,
    TY_FW_ERRORCODE_XML_OVERRIDE_FAILED     = 0x00100000,
    TY_FW_ERRORCODE_CAM_INIT_FAILED         = 0x00200000,
    TY_FW_ERRORCODE_LASER_INIT_FAILED       = 0x00400000,
}TY_FW_ERRORCODE_LIST;
typedef uint32_t TY_FW_ERRORCODE;

    Tip

    • 0x00000001 indicates that the left monochrome camera was not found.

    • 0x00000002 indicates that the right monochrome camera was not found.

    • 0x00000004 indicates that the RGB camera was not found.

    • 0x00000008 indicates a PoE error; please check if the PoE model complies with the protocol standard.

    • 0x00000010 indicates a calibration table error.

    • 0x00000020 indicates a parallax error.

    • 0x00000040 indicates a motor initialization error.

    • 0x00010000 indicates that the configuration file was not found.

    • 0x00020000 indicates that the configuration file is corrupted.

    • 0x00040000 indicates that the Config.xml file was not found.

    • 0x00080000 indicates that the Config.xml file is corrupted.

    • 0x00100000 indicates an error in rewriting the Config.xml file.

    • 0x00200000 indicates a camera initialization failure; 0x00200001 indicates that the initialization failure was due to the left monochrome camera not being found; 0x00200002 indicates that the initialization failure was due to the right monochrome camera not being found; 0x00200004 indicates that the initialization failure was due to the RGB camera not being found.

    • 0x00400000 indicates a laser initialization failure.