• Hardware

  • For oak-ffc-4p devices, the CAM_D will not respond after restarting the program.

Testing the oak-ffc-4p device, I found that there is a issue at CAM_D.The issue is that the CAM_D will not respond after I restart the program.

Firstly, run the simple testing program:

depthAI version: v2.22.0

#!/usr/bin/env python3

import os
# os.environ["DEPTHAI_LEVEL"] = "debug"
import depthai as dai
import cv2
import queue
import time

pipeline = dai.Pipeline()
camMono = pipeline.createMonoCamera()
xoutMono= pipeline.createXLinkOut()

camMono.setResolution(dai.MonoCameraProperties.SensorResolution.THE_400_P)
camMono.setBoardSocket(dai.CameraBoardSocket.CAM_D)
camMono.setFps(30)
xoutMono.setStreamName("mono")
camMono.out.link(xoutMono.input)

device = dai.Device(pipeline)
test_q = device.getOutputQueue("mono",4,False)

fps_cnt=0
timer = time.time()
while(True):
    data = test_q.tryGet()
    if data is not None:
        fps_cnt+=1
        frame = data.getCvFrame()
        cv2.imshow("preview",frame)
    if time.time()-timer>=1:
        print(f"fps: {fps_cnt}")
        fps_cnt=0
        timer=time.time()
    if cv2.waitKey(1) == ord('q'):
        break
    pass

cv2.destroyAllWindows()

I got:

fps: 29
fps: 30
fps: 30

Then press q or ctrl-c to exit and rerun the program.

fps: 0
fps: 0
fps: 0

The reason why I think this is a hardware issue is that our team had lay a board that refer to the OAK-FFC-4P schematic which don't have this issue.

    Hi cchung
    I don't think this is a hardware issue since the camera works at first.
    Could you check:

    • cam_test.py; does the issue occur there as well?
    • which revision of 4P are you using; it should be written on the PCB

    What solves the CAMD issue: is it the power cycling or does it solve itself with time.

    Thanks,
    Jaka

        jakaskerl

        Hi,

        Sorry for the delay, this issue also occurs when I rerun the cam_test.py. The only way to resume the camera is to unplug the usb and reconnect again.

        The hardware is here:

        • erik replied to this.

            Hi cchung
            The log for when the camd works "correctly" has a lot of entries in the beginning where fps is 0. How long does this last; does anything change (environment wise) that would enable the camera to start working correctly?

            Thanks,
            Jaka

                Hi cchung ,
                Logs look as expected.. Could you also try switching the camera to CAM_A instead?

                    jakaskerl

                    Hi,

                    The way to resume the camera is to unplug the usb and reconnect again.