DepthAI 2.24.0.0 and AR0234 on OAK-FFC 4P

cniessl

Hi,

I'm currently testing an OAK-FCC4P with single AR0234 M12 camera attached to port CAMD. I had run, as recommended, the depthai-python/examples/install_requirements.py python program to install all required libraries.

When I go to run cam_test.py in utilities, I get the following error output:
python3 cam_test.py --cameras camd,c Enabled cameras: camd : color DepthAI version: 2.24.0.0 DepthAI path: /home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so cam_test.py:320: DeprecationWarning: Use constructor taking 'UsbSpeed' instead with dai.Device(*dai_device_args) as device: [14442C1071CCE6D600] [1.2] [5.834] [ColorCamera(3)] [warning] Unsupported resolution set for detected camera AR0234, needs 1200_P, defaulting to it Connected cameras: -socket CAM_D : AR0234 1920 x 1200 focus:fixed - COLOR MONO USB speed: SUPER IR drivers: [] Cam: camd [host | capture timestamp] FPS: 0.00| 0.00 Communication exception - possible device error/misconfiguration. Original message 'Couldn't read data from stream: 'camd' (X_LINK_ERROR)' Exiting cleanly [14442C1071CCE6D600] [1.2] [1704320972.245] [host] [warning] Device crashed, but no crash dump could be extracted. terminate called without an active exception Stack trace (most recent call last): #24 Object "python3", at 0x599eeb, in #23 Object "/lib/aarch64-linux-gnu/libc.so.6", at 0xffffa025fe0f, in __libc_start_main #22 Object "python3", at 0x69c673, in Py_BytesMain #21 Object "python3", at 0x69be4b, in Py_RunMain #20 Object "python3", at 0x64dc77, in PyRun_SimpleFileExFlags #19 Object "python3", at 0x64d863, in #18 Object "python3", at 0x64d76b, in #17 Object "python3", at 0x64d69f, in #16 Object "python3", at 0x66160f, in PyEval_EvalCode #15 Object "python3", at 0x4fbfd3, in _PyEval_EvalCodeWithName #14 Object "python3", at 0x4ff5a7, in _PyEval_EvalFrameDefault #13 Object "python3", at 0x494e2f, in #12 Object "python3", at 0x592903, in _PyObject_MakeTpCall #11 Object "python3", at 0x592567, in PyCFunction_Call #10 Object "/home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so", at 0xffff8d9f42c3, in #9 Object "/home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so", at 0xffff8da345a3, in #8 Object "/home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so", at 0xffff8dcaad73, in dai::DeviceBase::close() #7 Object "/home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so", at 0xffff8dca43ff, in dai::Device::closeImpl() #6 Object "/home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so", at 0xffff8dcc10b3, in dai::DeviceBase::closeImpl() #5 Object "/home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so", at 0xffff8dcab0ff, in dai::DeviceBase::~DeviceBase() #4 Object "/lib/aarch64-linux-gnu/libstdc++.so.6", at 0xffff9008b26f, in std::terminate() #3 Object "/lib/aarch64-linux-gnu/libstdc++.so.6", at 0xffff9008b20b, in #2 Object "/lib/aarch64-linux-gnu/libstdc++.so.6", at 0xffff9008d82b, in __gnu_cxx::__verbose_terminate_handler() #1 Object "/lib/aarch64-linux-gnu/libc.so.6", at 0xffffa025faab, in abort #0 Object "/lib/aarch64-linux-gnu/libc.so.6", at 0xffffa0272d78, in gsignal Aborted (Signal sent by tkill() 2368 1000) Aborted (core dumped)

Any recommendations on troubleshooting?

jakaskerl

Hi cniessl
Likely a bad connection somewhere. I can confirm the camera works fine on 2.24 with a R5M1E5 4P board.

Thanks,
Jaka

cniessl

I attempted to replug the FFC on both the OAK and camera, and then tried a different AR0234 along with different cable, but got similar issues:

hbcarrier@hbcarrier:~/Software/depthai-python/utilities$ python3 cam_test.py --cameras camd,c Enabled cameras: camd : color DepthAI version: 2.24.0.0 DepthAI path: /home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so cam_test.py:320: DeprecationWarning: Use constructor taking 'UsbSpeed' instead with dai.Device(*dai_device_args) as device: Traceback (most recent call last): File "cam_test.py", line 320, in <module> with dai.Device(*dai_device_args) as device: RuntimeError: Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND

I then took the setup I had, and verified on another machine that the OAK-FCC 4P and AR0234 attached worked. When checking the software version, I got the following:

python3 cam_test.py --cameras camd,c Enabled cameras: cama : color DepthAI version: 2.24.0.0.dev0+7b57b28305368582d004d5c6ec2cffb66562f2e0

I then re-ran the build process in the base directory of depthai-python on the first machine that was causing problems, and was able to get Version: 2.24.0.0.dev0+7b57b28305368582d004d5c6ec2cffb66562f2e0 running when I checked the version of depthai with pip show. When running with this version of depthai, the cam_test utility worked and I was able to get a video feed.

Afterwards, I confirmed when running the install_requirements.py in depthai-python examples, that the software version 'upgraded' it back to 2.24.0.0
hbcarrier@hbcarrier:~/Software/depthai-python/examples$ python install_requirements.py pip 23.3.2 from /home/hbcarrier/.local/lib/python3.8/site-packages/pip (python 3.8) Requirement already satisfied: pip in /home/hbcarrier/.local/lib/python3.8/site-packages (23.3.2) Requirement already satisfied: pyyaml in /home/hbcarrier/.local/lib/python3.8/site-packages (6.0.1) Requirement already satisfied: requests in /home/hbcarrier/.local/lib/python3.8/site-packages (2.31.0) Requirement already satisfied: charset-normalizer<4,>=2 in /home/hbcarrier/.local/lib/python3.8/site-packages (from requests) (3.3.2) Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests) (2.8) Requirement already satisfied: urllib3<3,>=1.21.1 in /home/hbcarrier/.local/lib/python3.8/site-packages (from requests) (1.26.15) Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests) (2019.11.28) Collecting depthai Using cached depthai-2.24.0.0-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (8.7 kB) Using cached depthai-2.24.0.0-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (10.8 MB) Installing collected packages: depthai Attempting uninstall: depthai Found existing installation: depthai 2.24.0.0.dev0+7b57b28305368582d004d5c6ec2cffb66562f2e0 Uninstalling depthai-2.24.0.0.dev0+7b57b28305368582d004d5c6ec2cffb66562f2e0: Successfully uninstalled depthai-2.24.0.0.dev0+7b57b28305368582d004d5c6ec2cffb66562f2e0 Successfully installed depthai-2.24.0.0
Which then causes the issue when I try to run
python3 cam_test.py --cameras cama,c Enabled cameras: cama : color DepthAI version: 2.24.0.0 DepthAI path: /home/hbcarrier/.local/lib/python3.8/site-packages/depthai.cpython-38-aarch64-linux-gnu.so cam_test.py:320: DeprecationWarning: Use constructor taking 'UsbSpeed' instead with dai.Device(*dai_device_args) as device: Traceback (most recent call last): File "cam_test.py", line 320, in <module> with dai.Device(*dai_device_args) as device: RuntimeError: Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND
It seems the one should first run install_dependencies.py in the examples directory before running python3 -m pip install . in the base depthai-python directory, otherwise there may be issues with running code in utilities.

jakaskerl

Hi cniessl
Yes, that is how I do it. /examples/install_requirements.py will install everything needed. Manual installation of requirements.txt is not needed.

Thanks,
Jaka

mmorgan

Hi @jakaskerl ,

I'm still having the same issues as above. I was able to get a camera working one time by running:
python3 cam_test.py --cameras cama,c

I stopped the script and ran it again to test 2 cameras:

python3 cam_test.py --cameras cama,c camb,c

Then I received the same error as above:
RuntimeError: Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND

I power cycled the device and tried my first command again to make sure one camera still worked and received the same error once again. I've never been able to reproduce the video feed a second time.

We have checked all the cables everything seems secure. Do you have any other troubleshooting steps for us to try?

jakaskerl

Hi cniessl
My, bad. Was under the impression none of the USB devices use bootloader. The BOOTLOADER state in your case is correct, just checked on a local 4P.

mmorgan Looks like a power issue, like Martin stated.

cniessl
I checked with Depthai 2.24.0, the AR0234 should work on all four sockets. Which revision of the 4P are you using? It looks like a power issue. Have you checked/swapped the USB cable you are using to connect the PC to the 4P?

Thanks,
Jaka

themarpe

Hi @cnolan @mmorgan

One thing to verify is if 5V power is adequate and remains stable (doesn't drop/brownout). If the device is connected directly to an USB port of eg RPi, etc… (not via USB Y-Splitter), then the USB port must provide adequate power to operate correctly.

Regards, Martin

cniessl

themarpe

Hi @themarpe, we did try plugging in the 5V 3A power supply that comes with the OAK FFC 4P, in order to verify no power sagging or related issues were coming from our board. We still obtained the X_LINK_DEVICE_NOT_FOUND error.

One thing we did try afterwards was running device_manager.py in the utilities folder. It was able to detect the OAK FFC 4P, and confirmed the Current Depthai version installed was the correct one. It also said that the device state was in BOOTLOADER, though I am not sure if that is normal or the problem. I've attached a screen capture of the Device Manager information display.

Any further ideas are appreciated.

jakaskerl

Hi cniessl
Bootloader is used on POE devices and as far as I understand, this is a normal, usb powered FFC-4P?
The device should be in UNBOOTED state when plugged in via USB. It should wait for the host to initialize an application.
I believe that doing a factory reset and choosing USB bootloader should fix this current issue. Then check if it fixes the original issue as well.

Thanks,
Jaka

cniessl

Hi jakaskerl

This is a usb powered and data FCC-4P. We have not seen the device in UNBOOTED state when plugged in via USB using device_manager.

I attempted running device_manager.py and selecting "Factory Calibration" in the "Danger Zone" section. I did this while the power supply was plugged in to make sure it wasn't a lack of power issue from our board.
However, I received the following error when attempting the factory reset:

Any next steps to try or follow?

cniessl

It seems the issue was related to the usb connection on the computer we were testing with. Connecting the OAK FFC 4P with the same cable to a different computer allowed us to run cam_test.py with minimal issues.

Right now I'm attempting to troubleshoot some issues with the depthai calibration program, but I will create a new separate thread if I'm still stuck on those issues.