Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] {Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND POE Bridged Connection on Seeed ReComputer} #1220

Open
hellkrusher opened this issue Nov 21, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@hellkrusher
Copy link

Check if issue already exists

  • I have read thru all 43 issues mentioning X_LINK_DEVICE_NOT_FOUND but none have addressed the specific problem I am having.

Describe the bug
When I use a bridge connection with network on eth0 and Oak-d POE on eth1 the camera gets assigned IP address 192.168.93.113 and br0 gets IP address 192.168.93.106. I can connect fine using device_manager.py but depthai_demo.py, depthai-vewer, and all the experiment examples fail after I hear the autofocus on the camera click with Failed to connect to device, error message: X_LINK_DEVICE_NOT_FOUND. These programs all work when I setup local link and when I use a POE injector and plug it directly into the switch. However I must have the camera available to all endpoints on the network, not just locally and it must go thru the seeed studio recomputer.

Minimal Reproducible Example

  1. disable all network connections in the gui
  2. Make entries in /etc/udev/rules.d/10-persistent-net.rules and /etc/systemd/network/70-* if necessary.
  3. Disable existing connections if necessary nmcli con delete
    4.Create a bridge nmcli con add type bridge con-name br0 ifname br0
  4. Add workers nmcli con add type ethernet con-name eth0-slave ifname eth0 master br0
    nmcli con add type ethernet con-name eth1-slave ifname eth1 master br0
  5. enable nmcli con up br0

Expected behavior
Network camera should be available thru the network.

Screenshots

Pipeline Graph

N/A

Attach system log
{ "architecture": "64bit ELF", "machine": "aarch64", "platform": "Linux-5.10.192-tegra-aarch64-with-glibc2.31", "processor": "aarch64", "python_build": "default Nov 23 2021 15:27:38", "python_compiler": "GCC 9.3.0", "python_implementation": "CPython", "python_version": "3.9.5", "release": "5.10.192-tegra", "system": "Linux", "version": "#1 SMP PREEMPT Thu Jun 13 20:07:24 PDT 2024", "win32_ver": "", "packages": [ "depthai==2.28.0.0", "maturin==0.14.10", "numpy==2.0.2", "opencv-contrib-python==4.5.5.62", "patchelf==0.17.2.1", "pillow==10.3.0", "pip==24.3.1", "pkg_resources==0.0.0", "psutil==5.9.3", "PySimpleGUI-4-foss==4.60.4.1", "setuptools==44.0.0", "tomli==2.0.2" ], "usb": [ "NoLib" ], "uname": [ "Linux i2lpov 5.10.192-tegra #1 SMP PREEMPT Thu Jun 13 20:07:24 PDT 2024 aarch64 aarch64" ] }
bootloader: 0.0.28
Depthai version: 2.28.0.0

Additional context
ls

@hellkrusher hellkrusher added the bug Something isn't working label Nov 21, 2024
@Erol444
Copy link
Member

Erol444 commented Dec 2, 2024

Hi @hellkrusher , how are you powering the device? Could you share some pics? Seems very much like power issue, perhaps relevant docs here:
https://docs.luxonis.com/hardware/platform/deploy/powering-poe/#Powering%20OAK%20PoE%20devices-Powering%20from%20M8%20connector

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants