View my account

D555 camera not detecting over PoE

Follow
shaun mcknight

Hi, 

I have a new D555 camera. I am able to connect using USB-C but I am unable to detect the camera using POE. I have tested the camera using a windows machine and Nvidia Jetson device - I am having the same problem for both computers. I have also tried updating the firmware but this has not had an impact. Please see below for details:

  • Camera: RealSense D555 (brand new)
  • Connection: PC - UbiQuiti USW-LITE-8-POE - D555 camera (Camera is connected to power socket and the computer to data)
  • RealSense SDK v2.57.6
  • PC OS: Windows 11
  • Direct ping from PC to camera IP 192.168.11.55 works
  • Jumbo packet set to 9KB
  • IPv4 Address. . . . . . . . . . . : 192.168.11.100
  • Subnet Mask . . . . . . . . . . . : 255.255.255.0
  • Cables: Using the ethernet cable that came with camera.

rs-enumerate-devices.exe

No devices detected.

rs-dds-config.exe

No devices detected.

Both of these commands find the device when connected with usb.

There are no lights showing on the camera ethernet connection.

Could you please advise on how to resolve this issue and connect the camera successfully over PoE?

Thank you.

0

Comments

3 comments

Date Votes
  • MartyX Grover

    Hi shaun mcknight   D555 users who have a working camera on PoE have stated that the light does not come on during operation, so it is not an indication of a problem if the light is off.

     

    First, please ensure that a USB cable is not connected to the camera when using it in PoE mode, otherwise the camera will not work over ethernet.

     

    PoE support in the RealSense SDK is enabled by building the SDK from source code with CMake and including the flag -DBUILD_WITH_DDS=ON in the CMake build instruction.

     

    On Windows the jumbo packet should be set to 9014 instead of the 9000 value used on Linux. 

     

    There is an illustrated guide to configuring the Windows network settings for PoE at the link below.

    https://github.com/realsenseai/librealsense/issues/14293#issuecomment-3304919513

     

    Another D555 user on Windows has been having similar issues, so you can compare what you have tried with what they have tried.

    https://support.realsenseai.com/hc/en-us/community/posts/49545959849235

     

    The switch or injector should ideally support jumbo frames (i.e an MTU value of 9000), as the common default supported MTU value for switches is 1500 and not all switches support jumbo frames.  It is now possible to configure the D555 for use with low non-jumbo MTU values though.

    0
    Comment actions Permalink
  • shaun mcknight

    Hi MartyX Grover,

    We disconnect the usb-c when using PoE. 

    We are building on windows 11 - could this be a source of the problem? As windows 11 only allows for 4kb and 9kb. Have you had success building on windows 11 before?

    Either way we are still unable to connect to the device on Jetson devices as well. The problem is before streaming frames as we cannot even connect to the device but we are able to ping it.

    We will try a SDK rebuild but we have tried that before.

    If you have any other suggestions or test that we can run, please let us know.

    Thanks

     



    0
    Comment actions Permalink
  • MartyX Grover
    • Edited

    Building on Windows 11 is fine.

     

    I would recommend starting with the illustrated Windows setup guide in the link above if you have not used it already.  For example, following the guide's advice to configure the IP in the Windows network adapter settings to 192.168.11.70 instead of .100

     

    One of my RealSense colleagues has guidance about configuration for Ubuntu at the link below, though it sounds as though you have already implemented its advice.  Again, make sure to build with the -DBUILD_WITH_DDS=ON flag included.

    https://github.com/realsenseai/librealsense/issues/14284#issuecomment-3349204762

     

    The most recent Early Access firmware version for D555 - 7.56.37618.4188 - has improved camera discovery.  So you could try connecting the camera to USB and updating to that latest firmware driver, then unplugging USB and reconnecting the ethernet cable to see whether it makes a difference.

    https://dev.realsenseai.com/docs/firmware-early-access-release-d500

     

    You could also try setting the camera to dynamic DHCP identification with the command below so that it does not rely on the camera's fixed IP to find the camera.

    rs-dds-config --dhcp on

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post