ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Issues Getting voxl-streamer video stream working through RTSP stream on Doodle Labs Helix Radio

    VOXL 2
    2
    3
    121
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • John Nomikos 0J
      John Nomikos 0
      last edited by

      Good afternoon,

      Recently, I've been attempting to configure a setup on the VOXL2 that uses a doodle labs helix radio and a gremsy gimbal.

      HDMI from the camera on the gremsy is routed through an HDMI capture card to USB-C on top of the naked 5G expander board. And USB from the doodle is going through USB-2 on the board.

      I have been able to successfully get the camera going on voxl-uvc-server and it is outputting frames. I have also been able to view the stream through Ethernet and it looks smooth. It is running on a 640x480 stream at around 1 mbps.

      However, when using the doodle radio, the stream will cut out immediately to the point where it is unviewable.

      I've tried both decreasing and increasing the bitrate and ran into the same problems. I also tried moving one doodle further away from the other and the stream kept cutting out. However, I can still control the gimbal fine.

      Also, here is the output I was getting from voxl-streamer when the stream kept cutting out and not connecting on ATAK:

      voxl2:/$ voxl-streamer --standalone --port 8903 -i gremsy
Waiting for pipe gremsy to appear
Found Pipe
ERROR: object missing width
WARNING: Failed to fetch one or more of width, height, into_format, framerate from pipe info file
WARNING: going to connect to the pipe for 1 frame to inspect it now
WARNING: grabbed the data from the actual pipe and closed it
detected following stats from pipe:
w: 640 h: 480 fps: 0 format: YUV422
Stream available at rtsp://127.0.0.1:8903/live
A new client rtsp://10.223.0.150:46914(null) has connected, total clients: 1
Camera server Connected
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
ERROR:   New frame rejected, status = -2
rtsp client disconnected, total clients: 0
no more rtsp clients, closing source pipe intentionally
A new client rtsp://10.223.0.150:46916(null) has connected, total clients: 1
Camera server Connected
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
ERROR:   New frame rejected, status = -2
rtsp client disconnected, total clients: 0
no more rtsp clients, closing source pipe intentionally
A new client rtsp://10.223.0.150:46918(null) has connected, total clients: 1
Camera server Connected
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
rtsp client disconnected, total clients: 0
no more rtsp clients, closing source pipe intentionally
A new client rtsp://10.223.0.150:46920(null) has connected, total clients: 1
Camera server Connected
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
ERROR:   New frame rejected, status = -2
rtsp client disconnected, total clients: 0
no more rtsp clients, closing source pipe intentionally

      This "new frame rejected" error would continue on and on, over and over again.

      This is on platform 1.0.0
      voxl-streamer is version 1.7.1
      voxl-uvc-server is version 0.1.3

      I was wondering if there are recommended camera settings I should set on voxl-streamer to work with the doodle radio, or if there is insight on the errors voxl-streamer is running into.

      Thank you,

      John Nomikos.

      wilkinsafW 1 Reply Last reply Reply Quote 0
      • wilkinsafW
        wilkinsaf Dev Team @John Nomikos 0
        last edited by

        @John-Nomikos-0

        I bet that we can hook up an hdmi camera camera and try to duplicate this on the bench

        John Nomikos 0J 1 Reply Last reply Reply Quote 0
        • John Nomikos 0J
          John Nomikos 0 @wilkinsaf
          last edited by

          @wilkinsaf I completely agree. We can compare to a normal USB camera as well to see if the issue is with specifically streaming from the HDMI to USB capture card

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Powered by NodeBB | Contributors