View my account

RTSP Play D415 Camera

Comments

9 comments

  • MartyG

    Hi Juan Diezyanguas  A RealSense user at the link below replaced the RTSP protocol with ROS networking protocols.

    https://github.com/IntelRealSense/librealsense/issues/6841#issuecomment-660859774

     

    If the librealsense SDK is built from source code in V4L2 backend mode (also known as a Native build or RSUSB = false) then its raw streams should be accessible by standard Linux tools, as advised here:

    https://github.com/IntelRealSense/librealsense/issues/6841#issuecomment-660859774

     

    There is also a RealSense plugin for streaming data through GStreamer.

    https://github.com/WKDSMRT/realsense-gstreamer

    0
    Comment actions Permalink
  • Juan Diezyanguas

    Hi MartyG

    I'm using direcly the Raspberry Pi image available in the following manual.

    https://dev.intelrealsense.com/docs/open-source-ethernet-networking-for-intel-realsense-depth-cameras

    https://librealsense.intel.com/rs-tests/ethernet/pi-small.zip

    So I don't know how is compiled the SDK installed in the raspberry pi image.

    With regards,

    0
    Comment actions Permalink
  • MartyG

    Information about how the pre-made Raspberry Pi network-equipped SDK image is not available. In addition, networking support was removed from the SDK in version 2.54.1 onwards.  This means that the SDK would have to be built from source code using version 2.53.1 or older (such as 2.51.1).

     

    My understanding is that the pre-made SD card image is based around Raspberry Pi OS (formerly called Rapbian).  

     

    Intel have instructions at the link below for installing on Raspbian, though the guide is very old now and out of date in some of its instructions.  For example, a newer version of Protobuf than the one listed in the instructions should be used, such as version 3.12 or newer.  The pyrealsense2 section of the instructions can be skipped over if you do not plan to do Python programming.

    https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_raspbian.md

     

    In the section linked to below, change the cmake instruction to the following one in order to build the SDK with networking support and example programs and the RealSense Viewer included:

    cmake .. -DBUILD_NETWORK_DEVICE=ON -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true -DCMAKE_BUILD_TYPE=Release -DFORCE_LIBUVC=true

    https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_raspbian.md

     

    Installing librealsense on Raspberry Pi and getting it working can be a complicated process, unfortunately.

    0
    Comment actions Permalink
  • Juan Diezyanguas

    Do you know why network  support is removed from last version? In the changelog  says that it will return in newer versions.

    Regarding this type of things I have doubts about these cameras. The software are beeing maintained? Are these cameras good? or Intel won't continue with them?

     

    With regards,

    0
    Comment actions Permalink
  • MartyG

    The rs-server network interface was removed because it was an experimental 'proof of concept'.  Intel plan to introduce a new networking interface in an upcoming version of the SDK.

     

    Yes, the RealSense SDK software and the RealSense camera product range is being actively maintained and continued.

     

    0
    Comment actions Permalink
  • Juan Diezyanguas

    Hi MartyX Grover

    I have managed to get the raspberri pi working with rs-server but after many hours of trying and testing. I have used the libuv_install.sh script but adding the DBUILD_NETWORK_DEVICE=ON option.

    What is the meaning of the option DFORCE_LIBUVC? It says that it is a deprecated option replaced by DFORCE_RUSB_BACKEND=ON

    Using raspberry pi server I'm not able to connect the raspberry using VLC player. Only using Intel.RealSense SDK, I don't understand why, because under the hood it is using RTSP protocol for transmission.

    Also it seems that rs-server doesn't support multicasting, I have opened two instances of my software using Intel.RealSense SDK and the first one is stopped when second connects.

    Do you know what type of solution will be implemented in next release and when it will be available?

    Do you know other options than raspberri pi to support RealSense camera over network interface? I have read something about UP boards but I don't have many information on that and I don't know if this is a good option or another unsupported or old option.

    With regards,

    0
    Comment actions Permalink
  • MartyG

    When a function is labelled as deprecated it means that while that function is currently supported, it may be removed in the future and it is recommended that an alternative function is used instead in case removal does happen.  For some functions that are labelled deprecated though, they are never removed.  So the 'libuvc backend' and the newer 'RSUSB backend', which perform the same kernel bypass action, continue to exist side by side and either one can be used.

     

    In general I would recommend using RSUSB backend, but there are situations where it can be more convenient to use libuvc backend, especially if installing on Raspberry Pi boards or you want to perform a quick test installation with the libuvc backend installation script at the link below to see whether a kernel bypass build of the SDK can resolve kernel related problems.

    https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

     

    At the time of writing this information is not available about the form that the next generation of RealSense network support will take.

     

    Other than rs-server, the other main networking tool (which continues to be available) is a Python-based one developed before rs-server that is called EtherSense and uses UP boards.

    https://github.com/IntelRealSense/librealsense/tree/master/wrappers/python/examples/ethernet_client_server

    https://dev.intelrealsense.com/docs/depth-camera-over-ethernet-whitepaper

     

     

     

    0
    Comment actions Permalink
  • Juan Diezyanguas

    Hi MartyG,

    It seems that the UP Board option it's also an old option, for example the link to the UP board model says that is Phase out.

    In the white paper I don't see so much instructions to get it working. Do you know if there is a detailed manual on how to get it working? Do you know if this option supports multicast (receive camera signal in multiple devices).

    Regarding to the cmake command what do you mean with kernel bypass? What is doing the RSUSB backend option or the other one?

    With regards,

    0
    Comment actions Permalink
  • MartyG

    It does not have to be the original model of UP board.  Another board in the current UP range or a similar 'x86' architecture board such as Lattepanda should be fine.

     

    The 'depth camera over ethernet-whitepaper' link above is the most detailed documentation available for the EtherSense tool.   Within that documentation, it states "The Client application sends a specific multicast message to the network.  This is a message all servers are programmed to listen for.  On receipt of the multicast message the servers respond with a request to open a connection to the client using TCP".

     

    The RealSense SDK, when used on Linux computers, interacts with the Linux kernel in order to operate, but the SDK may not work correctly if the kernel is one that is not officially supported by the SDK or it is an unusual kernel that differs from the kernel on a typical consumer PC.  When the SDK is built from source code with the libuvc backend or RSUSB backend enabled though, the SDK is not dependent on specific Linux versions or kernel versions and the kernel does not need to have a patch applied to it.  This is useful, for example, if you want to use a flavor of Linux other than Ubuntu.

    0
    Comment actions Permalink

Please sign in to leave a comment.