• DepthAI-v2Hardware

  • Unable to identify Pro wide poe when connected to raspberry pi through ethernet

The luxonis pro wide poe is powered by Single port 95 Watt 802.2at Compliant Midspan.

It is connected to raspberry pi 5 through ethernet port.

When I run depth ai viewer, it doesnt show any devices but when i check the link connection status through ethtool eth0 , link detected is yes.

I checked this https://docs.luxonis.com/hardware/platform/deploy/poe-deployment-guide#i-can-ping-the-oak-poe-camera-but-can-t-connect-to-it but was unable to manually specify the ip since i dont know where to write the code and the code also seemed incomplete. Kindly suggest.

    Sarvesh
    If you run ifconfig on the PI, which interfaces does it show? Can you ping the camera at it's address?

    Thanks,
    Jaka

      eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

              inet 192.168.0.10  netmask 255.255.255.0  broadcast 192.168.0.255

              ether 2c:cf:67:28:a3:97  txqueuelen 1000  (Ethernet)

              RX packets 0  bytes 0 (0.0 B)

              RX errors 191  dropped 0  overruns 0  frame 191

              TX packets 201  bytes 27261 (26.6 KiB)

              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

              device interrupt 107

      lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

              inet 127.0.0.1  netmask 255.0.0.0

              inet6 ::1  prefixlen 128  scopeid 0x10<host>

              loop  txqueuelen 1000  (Local Loopback)

              RX packets 107  bytes 9291 (9.0 KiB)

              RX errors 0  dropped 0  overruns 0  frame 0

              TX packets 107  bytes 9291 (9.0 KiB)

              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

      wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

              inet 192.168.1.228  netmask 255.255.255.0  broadcast 192.168.1.255

              inet6 fe80::c2f9:9f60:7916:5782  prefixlen 64  scopeid 0x20<link>

              inet6 2600:1700:6910:8010::3e  prefixlen 128  scopeid 0x0<global>

              inet6 2600:1700:6910:8010:ec40:728e:2420:e5c5  prefixlen 64  scopeid 0x0<global>

              inet6 fe80::e1c9:8eed:818c:e6e9  prefixlen 64  scopeid 0x20<link>

              inet6 2600:1700:6910:8010:d60c:7df6:4c2e:28e0  prefixlen 64  scopeid 0x0<global>

              ether 2c:cf:67:28:a3:98  txqueuelen 1000  (Ethernet)

              RX packets 5770  bytes 987386 (964.2 KiB)

              RX errors 0  dropped 0  overruns 0  frame 0

              TX packets 896  bytes 141362 (138.0 KiB)

              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

      ping 192.168.0.10 works. What is next?
      Also, I was using real nvc viewer as a virtual desktop to visualise depth ai viewer. But now all i see is a grey screen. Ive tried reconnecting, rebooting raspberrypi and reinstalling real nvc nothing seems to work. Any suggestions?

      Latest Update:

      Ifconfig out shows

      1. Ip of the camera at eth0 to be inet 192.168.0.10 netmask 255.255.255.0.
      2. Ip of raspberry pi at wlan0 inet 192.168.1.228 netmask 255.255.255.0.

      when i tried to change ip of camera in /etc/dhcpcd.conf to 192.168.1.98, the connection to raspberry pi through real vnc viewer became really slow.

      then i changed the ip in rgb_preview.py as suggested here:

      https://docs.luxonis.com/hardware/platform/deploy/poe-deployment-guide/

      but it says cannot find any device with current device info.

      Ping works for 192.168.0.10.

      Since i dont have a dhcp server, the camera ip should fall back on default static ip (169.254.1.222). ping does not work.

      Q Why isnt the script able to identify the camera even though i can ping the ip shown in ifconfig and even after i specify deviceinfo like suggested? @jakaskerl

        Sarvesh
        You can ping the device but it is not discoverable since it is in a different subnet.

        Looks to me like you connected the device to a DHCP server on 192.168.0 subnet, but your PC wants to route the traffic through your WIFI adapter (.1 subnet).

        So either:
        1 RPI has DHCP server running
        2 Device is configured with the STATIC IP
        3 Some other DHCP server is giving the device an IP

        What to try:

        1. Turn off the RPI DHCP server

        2. Disconnect the WIFI (connnect to RPI via HDMI) device should be discoverable, you can clean the config via device_manager.py.

        3. Recheck your network.

        Thanks,
        Jaka

          Hi @jakaskerl ,

          Thank you for your response.

          I have both my camera and RPI on the same subnet (RPI = 192.168.1.228; Camera = 192.168.1.98):

          # Static IP configuration for eth0:

          interface eth0

          static ip_address=192.168.1.98/24

          static routers=192.168.1.254

          I checked for dnsmasq and it doesn't look like my RPI has a DHCP server running.

          Right now, my camera is connected to ethernet but my laptop is not.

          "Device is configured with the STATIC IP" -> Is it not supposed to be configured with static IP?

          After changing the eth0 config as mentioned above:

          When the camera is physically connected to RPI, I can see the RPI ip on devices on the network (arp -a) from my laptop. But I am unable to reach it when I try to ping it - also unable to connect using RealVNC.

          When I disconnect the camera, everything works fine.

          Any suggestions on how to resolve this would be super helpful. Thanks.

            Sarvesh "Device is configured with the STATIC IP" -> Is it not supposed to be configured with static IP?

            I'd recommend you set it to DYNAMIC for debugging. This will make sure the device is either set to IP via DHCP (which you say is not present) or APIPA fallback address (169....).

            Sarvesh When the camera is physically connected to RPI, I can see the RPI ip on devices on the network (arp -a) from my laptop. But I am unable to reach it when I try to ping it - also unable to connect using RealVNC.

            Physically connected means what? Direct POE connection between RPI and OAK? Or is there a switch inbetween (connected to router)?

            The device should be pingable from PC when it is connected to the router. When it is connected to RPI (directly), it will not be pingable.

            Thanks,
            Jaka

                Q. Physically connected means what? Direct POE connection between RPI and OAK? Or is there a switch inbetween (connected to router)?

                A. Direct POE connection between RPI and OAK.

                -> There is no router.

                  Sarvesh
                  Try a traceroute command to see where the ping goes when you try to ping the OAK device from RPI. I don't think it will work out of the box since the RPI has two network interfaces and won't know which one to use.

                  Can you try to connect to RPI via HDMI and check if the connection works as expected? IP of OAK when connected without router should be 169.254.1.222.

                  ifconfig on RPI should show 2 interfaces (at least), WIFI (with IP 192....) and ETH (with IP 169.254.x.x).

                  Thanks,
                  Jaka