• OAK-D PoE getting started

Is there some guide about how to get going with the PoE version.
All guides etc. seems to be with the USB cable.
I have tried to power my new "toy" OAK-1 and OAK-D PoE up with a poe-injector
but I have no clue how to connect to it ?
running the deptai-demo result in : can not find device ?

Any help

EDIT (from Brandon). The guide for getting started on POE is here:
https://docs.luxonis.com/en/latest/pages/tutorials/getting-started-with-poe/

    Hi damgaarderik ,

    Sorry about the confusion here. These shipped way faster this time then any previous rounds (which itself is great) but caught us a bit offguard in terms of having the official release out (we planned it for this Wednesday, to allow it to soak a bit more).

    So in the meantime, you can actually run using a specific branch (that is in the process of being pushed to main and as a formal depthai release tomorrow):

    If not done already:
    git clone depthai-python
    Then after that:
    git checkout bootloader_improvements_eth_desync_fix
    git pull
    python3 examples/install_requirements.py

    And then run examples like:
    python3 examples/rgb_preview.py

    And after tomorrow you'll be able to run the standard depthai_demo.py and it will automatically find the devices over POE and ask you which one you'd like to run it on (and automatically run if only 1 is available). It will list all USB and POE devices found.

    Thoughts?

    Thanks,
    Brandon

      And it looks like the release will go live likely today, so later today you'll be able to run any example that works on USB, over POE. So all the same documents apply, all the same examples/etc.

      And sorry about this not being available prior to the unit arriving. All the shipments took 3-4 days fewer than the last round. (We have since discovered why - and it was because we were able to electronically file the customs docs this time - which apparently means the shipments get through 3-4 days faster. So we know the timing for next time. :-))

      Best,
      Brandon

      Hi Brandon,
      Great. Thanks for your swift answer.
      At the end you will become an expert in logistic 😀

      I will give it a try when the release is out. Looks like a great device.

      btw , is there any LED or anything which should light up when the device is active?

      bR
      Erik D

      Thanks @Brandon for your help on discord getting my OAK-D PoE going and the quickstart guide. It is really an awesome piece of hardware.

      So great to get my hands on the

      So great to get my hands on the OAK-D
      POE. Fantastic job!
      One of my main customers has bought 50
      OAK-D's. But the POE is the one for the plant floor with IP66, POE etc.

      I have the unit powered up with a POE switch.
      What is the default ethernet configuration of the OAK-D POE?
      DHCP?
      Fixed IP?

        Hello stevefs,
        it's DHCP by default, but if there is no DHCP the POE device will get a static IP 169.254.1.222.
        Thanks, Erik

          8 days later

          I have a OAK-1 and OAK-D both with PoE.
          I have no clue what I am doing wrong but in either device the LED is flashing when I connect them to PoE ports of my switch ?
          There is no connection at all ????
          I have also tried with a ubiquity PoE injector with the same result ?
          I have an accesspoint on another PoE which I have tried also, but it do not flash or connect...nothing happens...on both devices ?

          Any suggestions ?

            damgaarderik

            I just wanted to check - was this resolved? The reason I ask is I think we resolved this together on Discord (as the description sounds the same), but just wanted to check.

            And for the resolution (for posterity), the solution was having DHCP on the network (and if not, connecting to the static IP w/in the same subnet, as per here).

              Hi Brando,
              yes, thanks for your concern. Same as on Discord.
              Issues with dip-switches on my PoE Switch.
              Regarding DHCP it behaved as described in your description

              a year later