depthai-python icon indicating copy to clipboard operation
depthai-python copied to clipboard
verified publisher icon luxonis

Oak-FFC-6P Not Working

Open dcharlot65-aurasense opened this issue 2 years ago • 8 comments

Hi Purchased 4 Oak-FFC-6P for a project. I'm unable to get them to work. I've reviewed the Getting Started Guide and the Google Doc Primer for advanced use:

https://docs.luxonis.com/projects/hardware/en/latest/pages/DM3390/#getting-started https://docs.google.com/document/d/1r3en4EqgDG3hum8o5yS1DJ5vSCb6aNqyA38tIM8723U/edit

I have successfully gained access via ssh to the Oak-FFC-6p and performed the OS upgrade and firmware upgrade on Ubuntu and Windows. You must manually set the IP address for the device.

For Windows 11 Pro I used to establish the ethernet connection (192.168.197.10 did not work on Windows 11): IP: 192.168.197.59 mask: 255.255.255.0

For Ubuntu 22.04 I used to establish the ethernet connection: IP: 192.168.197.10 mask: 255.255.255.0

I copied the new OS releases and I updated the OS following instructions to: luxonisos-1.9.dm-verity.mender luxonisos-1.10.dm-verity.mender luxonisos-1.11.dm-verity.mender

mender -install [path/or/url/to/dm-verity.mender] ; reboot

For the OS I see the OS installed by typing on the the Oak-FFC-6p via SSH: cat /etc/os-release (lsb_release -a does not work)

I updated the FIP (“firmware/bootloader” image update): fip-oak-ffc-6p-rvc3-1.2.0.bin fip-oak-ffc-6p-kb-1.5.0.bin

movisoc-fwu -a [path/to/fip.bin] ; reboot

How does one verify the FIP Bootloader is updated correctly?

This step went well.

For my setup I have installed 6 cameras on all of the ports: CAM_A (RGB): OAK-FFC IMX378 FF CAM_B (Left): OAK-FFC OV9282 CAM_C (Right): OAK-FFC OV9282 CAM_D: OAK-FFC IMX378 FF CAM_E: OAK-FFC OV9282 CAM_F: OAK-FFC OV9282

When I then attempt to run the camera test python code (debug mode enabled): cam_test.py --cameras rgb,c left,m right,m

C:\Users\david\Downloads\depthai\depthai-python-rvc3_develop>python .\utilities\cam_test.py --cameras rgb,c left,m right,m
[2023-07-16 10:06:28.022] [depthai] [debug] Python bindings - version: 2.22.0.0 from 2023-06-13 02:13:35 +0200 build: 2023-06-13 01:34:29 +0000 [2023-07-16 10:06:28.023] [depthai] [debug] Library information - version: 2.22.0, commit: 82ab07d037c02f56042d1d2d55a718f379651ed9 from 2023-06-13 02:13:14 +0200, build: 2023-06-13 01:34:17 +0000 [2023-07-16 10:06:28.031] [depthai] [debug] Initialize - finished Enabled cameras: rgb : color left : mono right : mono DepthAI version: 2.22.0.0 DepthAI path: C:\Users\david\AppData\Roaming\Python\Python39\site-packages\depthai.cp39-win_amd64.pyd C:\Users\david\Downloads\depthai\depthai-python-rvc3_develop\utilities\cam_test.py:86: DeprecationWarning: RGB is deprecated, use CAM_A or address camera by name instead. 'rgb' : dai.CameraBoardSocket.RGB, # Or CAM_A C:\Users\david\Downloads\depthai\depthai-python-rvc3_develop\utilities\cam_test.py:87: DeprecationWarning: LEFT is deprecated, use CAM_B or address camera by name instead. 'left' : dai.CameraBoardSocket.LEFT, # Or CAM_B C:\Users\david\Downloads\depthai\depthai-python-rvc3_develop\utilities\cam_test.py:88: DeprecationWarning: RIGHT is deprecated, use CAM_C or address camera by name instead. 'right': dai.CameraBoardSocket.RIGHT, # Or CAM_C [2023-07-16 10:06:28.104] [depthai] [debug] Resources - Archive 'depthai-bootloader-fwp-0.0.26.tar.xz' open: 2ms, archive read: 76ms [2023-07-16 10:06:28.407] [depthai] [debug] Resources - Archive 'depthai-device-fwp-f033fd9c7eb0b3578d12f90302e87759c78cfb36.tar.xz' open: 1ms, archive read: 380ms Traceback (most recent call last): File "C:\Users\david\Downloads\depthai\depthai-python-rvc3_develop\utilities\cam_test.py", line 206, in with dai.Device() as device: RuntimeError: No available devices

I believe I correctly downloaded the rvc3_develop branch from github and installed the requirements properly. How would I know if this is the case? How do I know I'm running the develop branch and not the main branch?

Can someone give me a hand? I'm about 3 hours into playing around and finding what the error could be.

dcharlot65-aurasense avatar Jul 16 '23 14:07 dcharlot65-aurasense

Hi @dcharlot65-aurasense you are in fact not running the rvc3_develop branch, but the main branch. You can check the depthai version by running python3 -c "import depthai;print(depthai.__version__)". if you have already downloaded the rvc3_develop branch, you can install it by running examples/install_requirements.py from the root of the repo. as for the fip version, you can get the current version by ssh-ing to the device and typing fip-version into the terminal

JanLipovsek avatar Jul 17 '23 13:07 JanLipovsek

Hi,

Thanks for the information. I will check. I do have a follow up question.

My plan is to use an Nvidia Jetson as my main computer to use the oak-ffc-6p. What I'm planning is to use 2x oak-ffc-6p and 1x OAK-D-IOT-75 all connected to the same PC and running in parallel. I've already confirmed that multiple OAK-D-IOT-75 can run on the Nvidia Jetson at the same time. I wanted to make sure the same is true for the oak-ffc-6p. Each individual oak-ffc-6p will run 2 separate stereo-pairs simultaneously.

Our application calls for looking at the same object from 5 different vantage points in a compact footprint. We got the Oak-FFC-6p to reduce the number of USB cables we need to connect to the computer. We are using the OAK-D-IOT-75 because we already have a bunch available. We will be upgrading to the Oak-D-S2 or Oak-D-Pro once we verify functionality.

Will this setup work? I notice the Oak-FFC-6p creates an USB ethernet bridge and the IP address seems fixed. Is it possible to connect 2 of them to the same computer without an IP address conflict?

  1. Stereo Pair 1: OAK-D-IOT-75

    1. RGB: OAK-FFC IMX378 FF

    2. Left: OAK-FFC OV9282

    3. Right: OAK-FFC OV9282

    4. Stereo Pair 2:

  2. Oak-FFC-6p - 1 - CAM_A (RGB): OAK-FFC IMX378 FF 2. Oak-FFC-6p - 1 - CAM_B (Left): OAK-FFC OV9282 3. Oak-FFC-6p - 1 - CAM_C (Right): OAK-FFC OV9282

    1. Stereo Pair 3:

    2. Oak-FFC-6p - 1 - CAM_D: OAK-FFC IMX378 FF

    3. Oak-FFC-6p - 1 - CAM_E: OAK-FFC OV9282

    4. Oak-FFC-6p - 1 - CAM_F: OAK-FFC OV9282

    5. Stereo Pair 4:

    6. Oak-FFC-6p - 2 - CAM_A (RGB): OAK-FFC IMX378 FF

    7. Oak-FFC-6p - 2 - CAM_B (Left): OAK-FFC OV9282

    8. Oak-FFC-6p - 2 - CAM_C (Right): OAK-FFC OV9282

    9. Stereo Pair 5:

    10. Oak-FFC-6p - 2 - CAM_D: OAK-FFC IMX378 FF

    11. Oak-FFC-6p -2 - CAM_E: OAK-FFC OV9282

    12. Oak-FFC-6p - 2 - CAM_F: OAK-FFC OV9282

dcharlot65-aurasense avatar Jul 17 '23 14:07 dcharlot65-aurasense

Hi @dcharlot65-aurasense , Currently there would be 2 challenges:

  1. RVC3 will try to have static IP, so to have 2 devices, you'd need to SSH into one and change the IP.
  2. Mixing RVC2 and RVC3: RVC3 requires custom depthai library atm (mainlining RVC3 ETA would be 1-2 months). As a workaround, you could open a TCP server on RVC3 (on arm cores), and on your jetson you would connect to the server. So instead of using depthai library to handle communication between Jetson and RVC3, you'd use TCP socket, but you'd still have depthai running on the RVC3.

Thoughts?

Erol444 avatar Jul 17 '23 15:07 Erol444

Hi,

Can you walk me through installing?

I downloaded the rvc3_develop branch. I ran the code: python ./examples/install_requirements.py. I went on to download the depthai 2.22.0.0 wheel file from:

https://files.pythonhosted.org/packages/a2/b2/7656a49d55f445501c3ebb3f8e10251f84afa74ee683705adc96b6e1cf4b/depthai-2.22.0.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata

I assume this is the problem.

Cheers!!!

[image: Logo] https://www.blazingaudio.com/ [image: Logo] David Charlot, PhD Head of Product | Exec. Chair & Co-Founder M: (858) 692-5939 E: @.*** | www.aurasense.health 965 W. Chicago Ave., Chicago, IL 60642

On Mon, Jul 17, 2023 at 9:53 AM JanLipovsek @.***> wrote:

Hi @dcharlot65-aurasense https://github.com/dcharlot65-aurasense you are in fact not running the rvc3_develop branch, but the main branch. You can check the depthai version by running python3 -c "import depthai;print(depthai.version)". if you have already downloaded the rvc3_develop branch, you can install it by running examples/install_requirements.py from the root of the repo. as for the fip version, you can get the current version by ssh-ing to the device and typing fip-version into the terminal

— Reply to this email directly, view it on GitHub https://github.com/luxonis/depthai-python/issues/865#issuecomment-1638194366, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6PXNUQU3SRVRO5D65OHX6TXQU7T3ANCNFSM6AAAAAA2L67IPQ . You are receiving this because you were mentioned.Message ID: @.***>

dcharlot65-aurasense avatar Jul 17 '23 15:07 dcharlot65-aurasense

@dcharlot65-aurasense You need to clone the repository, then checkout rvc3_develop branch, otherwise if you "download" then install_requirements.py will download wheel from latest pypi release, which is not compatible with RVC3.

SzabolcsGergely avatar Jul 17 '23 16:07 SzabolcsGergely

Thanks,

I was just downloading the repository and thought I was getting the rvc3_develop branch. Is numpy-1.25.1 actually required? Can numpy-1.22.0 also work? I use sci-py and numba (they work with numpy-1.22.0).

I used the following command to get the correct repository:

git clone --branch rvc3_develop https://github.com/luxonis/depthai-python.git

after installing the requirements and checking the version of depthai I find the following version is installed: depthai-2.19.1.0.dev0+3e9c7195d49f0613c2a24653ae67f91fd1748b9a. For my previous attempts I had depthai-2.22.0.0 installed. Super easy thing to overlook for all who also had issues using the Oak-FFC-6p.

C:\Users\david\Downloads\depthai-python>python Python 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information.

import depthai print(depthai.version) 2.19.1.0.dev+3e9c7195d49f0613c2a24653ae67f91fd1748b9a

Cheers!!!

[image: Logo] https://www.blazingaudio.com/ [image: Logo] David Charlot, PhD Head of Product | Exec. Chair & Co-Founder M: (858) 692-5939 E: @.*** | www.aurasense.health 965 W. Chicago Ave., Chicago, IL 60642

On Mon, Jul 17, 2023 at 10:05 AM szabi-luxonis @.***> wrote:

@dcharlot65-aurasense https://github.com/dcharlot65-aurasense You need to clone the repository, then checkout rvc3_develop branch, otherwise install_requirements.py will download wheel from latest pypi release, which is not compatible with RVC3.

— Reply to this email directly, view it on GitHub https://github.com/luxonis/depthai-python/issues/865#issuecomment-1638440408, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6PXNUQRDUFKNGJNO5MY4Y3XQVPDBANCNFSM6AAAAAA2L67IPQ . You are receiving this because you were mentioned.Message ID: @.***>

dcharlot65-aurasense avatar Jul 17 '23 22:07 dcharlot65-aurasense

@dcharlot65-aurasense I believe that is the correct version, and that 1.22 numpy should work as well.

Erol444 avatar Jul 18 '23 08:07 Erol444

Hi,

You mention changing the static IP via SSH on one of the devices. What does that entail?

Cheers!!!

[image: Logo] https://www.blazingaudio.com/ [image: Logo] David Charlot, PhD Head of Product | Exec. Chair & Co-Founder M: (858) 692-5939 E: @.*** | www.aurasense.health 965 W. Chicago Ave., Chicago, IL 60642

On Mon, Jul 17, 2023 at 10:13 AM Erol444 @.***> wrote:

Hi @dcharlot65-aurasense https://github.com/dcharlot65-aurasense , Currently there would be 2 challenges:

  1. RVC3 will try to have static IP, so to have 2 devices, you'd need to SSH into one and change the IP.
  2. Mixing RVC2 and RVC3: RVC3 requires custom depthai library atm (mainlining RVC3 ETA would be 1-2 months). As a workaround, you could open a TCP server on RVC3 (on arm cores), and on your jetson you would connect to the server. So instead of using depthai library to handle communication between Jetson and RVC3, you'd use TCP socket, but you'd still have depthai running on the RVC3.

Thoughts?

— Reply to this email directly, view it on GitHub https://github.com/luxonis/depthai-python/issues/865#issuecomment-1638353054, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6PXNUVEC3G254UMSMTPDH3XQVJCDANCNFSM6AAAAAA2L67IPQ . You are receiving this because you were mentioned.Message ID: @.***>

dcharlot65-aurasense avatar Jul 18 '23 08:07 dcharlot65-aurasense