Hello! I’ve been using two OAK-D Pro W PoE cameras with the ROS1 drivers, running on Ubuntu 18.04 via the provided Docker image. This setup has allowed me to successfully access both cameras initially. The PC I’m using has an integrated PoE card, so there’s no need for a separate injector.

However, I’m encountering an issue where, if I restart the ROS driver, it often fails to detect any devices—even though I can still ping the cameras. According to the documentation, this behavior seems similar to a “soft-bricked” state, but I’ve already confirmed that the bootloader is up to date ( version is 0.0.28 ). Interestingly, after several random attempts and some system restarts, access to both cameras is eventually restored.

Has anyone experienced a similar issue or found a stable workaround? Any insights would be greatly appreciated!

  • jakaskerl replied to this.

  • Hi Jaka,

    Thank you for your suggestions—they were very helpful! After verifying that the network settings were correctly defined and respecting the 15-second delay, I was able to achieve a stable and robust configuration.

    Thanks for you assistance,
    Ioulianos

    Hey Ioulianos
    Do you perhaps have multiple network adapters active at the same time? Also, the devices need about 15s to fully reboot, and generally won't be accessible then.

    Thanks,
    Jaka

      Hello Jaka,

      To clarify, the PC doesn’t have any network adapters; instead, it has a PoE card and four standard Ethernet ports, all of which are configured with static IPs.

      Regarding the 15-second delay, just to confirm, does this mean I should wait 15 seconds between each launch of the ROS driver to ensure the devices are fully accessible ?

      Thanks in advance,
      Ioulianos

        Ioulianos
        The broadcast likely isn't sent correctly. Make sure the subnet mask and IP of PC are set correctly.
        You can also try with python/cpp scripts to see if perhaps the driver is causing issues.

        Ioulianos Regarding the 15-second delay, just to confirm, does this mean I should wait 15 seconds between each launch of the ROS driver to ensure the devices are fully accessible ?

        Yes. When device shuts down, it takes some time for watchdog to kill it and reboot it back to the working state where it can accept connections.

        Thanks,
        jaka

            Hi Jaka,

            Thank you for your suggestions—they were very helpful! After verifying that the network settings were correctly defined and respecting the 15-second delay, I was able to achieve a stable and robust configuration.

            Thanks for you assistance,
            Ioulianos