6 Replies Latest reply on Jan 16, 2017 6:34 AM by Intel Corporation

    intel realsense r200 rdk VIDIOC_DQBUF error 19

    MateuszR

      Hi,

      I am trying to get my intel realsense RDK with R200 and up board working, but i'm constantly failing.

      I am using Ubuntu 16.04 LTS desktop with 4.4.0-2-upboard kernel, and supplies that came with the kit: power adapter (5V 4A), USB3 male to microusb3 male cable and usb3 female to micro male adatper.

       

      1 I followed steps in Intel RealSense Robotic Development Kit | Developer Journey  till step 8 where i get

      mateusz@mateusz-UP-CHT01:~$ roscore &

      [1] 2161

      mateusz@mateusz-UP-CHT01:~$ ... logging to /home/mateusz/.ros/log/d9cc3536-d7f1-11e6-b223-243c200a98cb/roslaunch-mateusz-UP-CHT01-2161.log

      Checking log directory for disk usage. This may take awhile.

      Press Ctrl-C to interrupt

      Done checking log file disk usage. Usage is <1GB.

       

      started roslaunch server http://mateusz-UP-CHT01:43859/

      ros_comm version 1.12.6

       

       

      SUMMARY

      ========

       

      PARAMETERS

      * /rosdistro: kinetic

      * /rosversion: 1.12.6

       

      NODES

       

      auto-starting new master

      process[master]: started with pid [2176]

      ROS_MASTER_URI=http://mateusz-UP-CHT01:11311/

       

      setting /run_id to d9cc3536-d7f1-11e6-b223-243c200a98cb

      process[rosout-1]: started with pid [2190]

      started core service [/rosout]

       

       

      mateusz@mateusz-UP-CHT01:~$ roscd realsense_camera

      mateusz@mateusz-UP-CHT01:/opt/ros/kinetic/share/realsense_camera$

       

       

       

      roslaunch realsense_camera r200_nodelet_default.launch &

      [2] 2300

      mateusz@mateusz-UP-CHT01:/opt/ros/kinetic/share/realsense_camera$ ... logging to /home/mateusz/.ros/log/d9cc3536-d7f1-11e6-b223-243c200a98cb/roslaunch-mateusz-UP-CHT01-2300.log

      Checking log directory for disk usage. This may take awhile.

      Press Ctrl-C to interrupt

      Done checking log file disk usage. Usage is <1GB.

       

      started roslaunch server http://mateusz-UP-CHT01:39941/

       

      SUMMARY

      ========

       

      PARAMETERS

      * /camera/driver/base_frame_id: camera_link

      * /camera/driver/camera_type: R200

      * /camera/driver/color_frame_id: camera_rgb_frame

      * /camera/driver/color_optical_frame_id: camera_rgb_optica...

      * /camera/driver/depth_frame_id: camera_depth_frame

      * /camera/driver/depth_optical_frame_id: camera_depth_opti...

      * /camera/driver/fisheye_frame_id: camera_fisheye_frame

      * /camera/driver/fisheye_optical_frame_id: camera_fisheye_op...

      * /camera/driver/imu_frame_id: camera_imu_frame

      * /camera/driver/imu_optical_frame_id: camera_imu_optica...

      * /camera/driver/ir2_frame_id: camera_ir2_frame

      * /camera/driver/ir2_optical_frame_id: camera_ir2_optica...

      * /camera/driver/ir_frame_id: camera_ir_frame

      * /camera/driver/ir_optical_frame_id: camera_ir_optical...

      * /camera/driver/serial_no:

      * /camera/driver/usb_port_id:

      * /rosdistro: kinetic

      * /rosversion: 1.12.6

       

      NODES

        /camera/

          camera_nodelet_manager (nodelet/nodelet)

          driver (nodelet/nodelet)

       

      ROS_MASTER_URI=http://localhost:11311

       

      core service [/rosout] found

      process[camera/camera_nodelet_manager-1]: started with pid [2318]

      process[camera/driver-2]: started with pid [2319]

      [ INFO] [1484134517.879248746]: Initializing nodelet with 4 worker threads.

      [ INFO] [1484134518.412208723]: /camera/driver - Detected the following cameras:

                      - Serial No: 2381006343, USB Port ID: 2-1, Name: Intel RealSense R200, Camera FW: 1.0.72.10

      [ INFO] [1484134518.412340641]: /camera/driver - Connecting to camera with Serial No: 2381006343, USB Port ID: 2-1

      [ INFO] [1484134520.537622405]: /camera/driver - Setting static camera options

      [ INFO] [1484134520.580378392]: /camera/driver - Enabling Color in preset mode

      [ INFO] [1484134520.589616723]: /camera/driver - Enabling Depth in preset mode

      [ INFO] [1484134520.590238391]: /camera/driver - Starting camera

      [ INFO] [1484134520.620979953]: /camera/driver - Publishing camera transforms

      [ INFO] [1484134520.621355734]: /camera/driver - Setting dynamic camera options (r200_dc_preset=5)

      [ INFO] [1484134521.378504337]: /camera/driver - Initializing Depth Control Preset to 5

      [ INFO] [1484134521.379234838]: /camera/driver - NOTICE: Individual Depth Control values set by params will be ignored; set r200_dc_preset=-1 to override.

      [ INFO] [1484134524.214534130]: /camera/driver - Setting dynamic camera options

      terminate called after throwing an instance of 'std::runtime_error'

        what():  VIDIOC_DQBUF error 19, No such device

      [camera/camera_nodelet_manager-1] process has died [pid 2318, exit code -6, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=camera_nodelet_manager __log:=/home/mateusz/.ros/log/d9cc3536-d7f1-11e6-b223-243c200a98cb/camera-camera_nodelet_manager-1.log].

      log file: /home/mateusz/.ros/log/d9cc3536-d7f1-11e6-b223-243c200a98cb/camera-camera_nodelet_manager-1*.log

      [camera/driver-2] process has finished cleanly

      log file: /home/mateusz/.ros/log/d9cc3536-d7f1-11e6-b223-243c200a98cb/camera-driver-2*.log

      all processes on machine have died, roslaunch will exit

      shutting down processing monitor...

      ... shutting down processing monitor complete

      done

       

      ... as this stupid form just erased the rest of my post. no details will be provided

       

      2 installed librealsense. examples are working for few seconds and then stop with VIDIOC_DQBUF error 19, No such device

      3 powered usb 3 hub didnt work, as up board cannot see the camera: 'no camera detected. is it plugged in?'. hub seems to be working as i can insert pendrive or mouse and use them.

      4 changing cable for a different usb3 male to microusb male made no difference

      5 switching places of usb3 cable and usb3 male a to microusb adater made no difference

      6 can run the camera on win7 machine for a long time, but the output is distorted (probably due to wrong windows)

      7 can see camera info:

      Serial number: 2381006343

      Firmware version: 1.0.72.10

      USB Port ID: 2-1

      Camera info:

          DEVICE_NAME         :     Intel RealSense R200

          DEVICE_SERIAL_NUMBER:     2381006343

          CAMERA_FIRMWARE_VERSION:     1.0.72.10

          CAMERA_TYPE         :     Non-PRQ type (0)

          OEM_ID              :     OEM None

          ISP_FW_VERSION      :     0x0

          CONTENT_VERSION     :     12

          MODULE_VERSION      :     4.2.5.4

          IMAGER_MODEL_NUMBER :     31

          CALIBRATION_DATE    :     2014-07-04 08:18:35 UTC

          EMITTER_TYPE        :     Laser Driver 3

          FOCUS_VALUE         :     0

          LENS_TYPE           :     Newmax 58.9 x 45.9 degs in VGA

          3RD_LENS_TYPE       :     Newmax 71.7 x 44.2 degs in 1080p

          LENS_COATING__TYPE  :     Visible-light block / IR pass 43 nm width

          3RD_LENS_COATING_TYPE:     IR coating

          NOMINAL_BASELINE    :     70 mm

          3RD_NOMINAL_BASELINE:     58 mm

       

      how to fix this error?

       

      edit:

      I tried to power the board with lipo battery through a DC-DC converter and still having that error.

        • 1. Re: intel realsense r200 rdk VIDIOC_DQBUF error 19
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hi MateuszR,

           

          Thank you for contacting us.

           

          This issue has been reported before here https://github.com/IntelRealSense/librealsense/issues/71 . It seems to be due to the camera not receiving enough power from the USB port. I’d recommend you to use only the USB cable provided with the kit and to plug it into the MicroB adapter next to the HDMI port next to the power port, as shown in the pictures below:

           

           

          Let us know if this works for you.

           

          Regards,

          -Sergio

          • 2. Re: intel realsense r200 rdk VIDIOC_DQBUF error 19
            MateuszR

            Hi, sergio.

            yes, I have seen the topic and also thought that the reason is in power supply, but changing cable/power adapter or using powered usb3 hub did not help.

            My rdk kit does not have usb3 micro B to micro cable B. Mine has usb3 A to micro B cable and usb3 to micro adapter as shown on attached photointelrealsense.jpg

            • 3. Re: intel realsense r200 rdk VIDIOC_DQBUF error 19
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              I noticed from the commands you ran on step 8 that roslaunch realsense_camera r200_nodelet_default.launch was the last command you used before receiving the VIDIOC_DQBUF error 19, No such device error.

              There’s a troubleshooting tip at the end of section 8 that says:
              “If you are having problems running the `roslaunch realsense_camera r200_nodelet_default.launch` command, verify that your camera was detected by the UP board”


              Please run the following commands and let me know their output.
              ls /dev/video*
              lsmod | grep -q uvcvideo && echo "Kernel module found."


              We’ll be waiting for your response.

              -Sergio
               

              • 4. Re: intel realsense r200 rdk VIDIOC_DQBUF error 19
                MateuszR

                mateusz@mateusz-UP-CHT01:~$ ls /dev/video*

                /dev/video0  /dev/video1  /dev/video2

                mateusz@mateusz-UP-CHT01:~$ lsmod | grep -q uvcvideo && echo "Kernel module found."

                Kernel module found.

                mateusz@mateusz-UP-CHT01:~$ roscore &

                [1] 2767

                mateusz@mateusz-UP-CHT01:~$ ... logging to /home/mateusz/.ros/log/3f841286-da4f-11e6-a22c-243c200a98cb/roslaunch-mateusz-UP-CHT01-2767.log

                Checking log directory for disk usage. This may take awhile.

                Press Ctrl-C to interrupt

                Done checking log file disk usage. Usage is <1GB.

                 

                started roslaunch server http://mateusz-UP-CHT01:36116/

                ros_comm version 1.12.6

                 

                 

                SUMMARY

                ========

                 

                PARAMETERS

                * /rosdistro: kinetic

                * /rosversion: 1.12.6

                 

                NODES

                 

                auto-starting new master

                process[master]: started with pid [2780]

                ROS_MASTER_URI=http://mateusz-UP-CHT01:11311/

                 

                setting /run_id to 3f841286-da4f-11e6-a22c-243c200a98cb

                process[rosout-1]: started with pid [2793]

                started core service [/rosout]

                roscd realsense_camera

                mateusz@mateusz-UP-CHT01:/opt/ros/kinetic/share/realsense_camera$ roslaunch realsense_camera r200_nodelet_default.launch &

                [2] 2834

                mateusz@mateusz-UP-CHT01:/opt/ros/kinetic/share/realsense_camera$ ... logging to /home/mateusz/.ros/log/3f841286-da4f-11e6-a22c-243c200a98cb/roslaunch-mateusz-UP-CHT01-2834.log

                Checking log directory for disk usage. This may take awhile.

                Press Ctrl-C to interrupt

                Done checking log file disk usage. Usage is <1GB.

                 

                started roslaunch server http://mateusz-UP-CHT01:46378/

                 

                SUMMARY

                ========

                 

                PARAMETERS

                * /camera/driver/base_frame_id: camera_link

                * /camera/driver/camera_type: R200

                * /camera/driver/color_frame_id: camera_rgb_frame

                * /camera/driver/color_optical_frame_id: camera_rgb_optica...

                * /camera/driver/depth_frame_id: camera_depth_frame

                * /camera/driver/depth_optical_frame_id: camera_depth_opti...

                * /camera/driver/fisheye_frame_id: camera_fisheye_frame

                * /camera/driver/fisheye_optical_frame_id: camera_fisheye_op...

                * /camera/driver/imu_frame_id: camera_imu_frame

                * /camera/driver/imu_optical_frame_id: camera_imu_optica...

                * /camera/driver/ir2_frame_id: camera_ir2_frame

                * /camera/driver/ir2_optical_frame_id: camera_ir2_optica...

                * /camera/driver/ir_frame_id: camera_ir_frame

                * /camera/driver/ir_optical_frame_id: camera_ir_optical...

                * /camera/driver/serial_no:

                * /camera/driver/usb_port_id:

                * /rosdistro: kinetic

                * /rosversion: 1.12.6

                 

                NODES

                  /camera/

                    camera_nodelet_manager (nodelet/nodelet)

                    driver (nodelet/nodelet)

                 

                ROS_MASTER_URI=http://localhost:11311

                 

                core service [/rosout] found

                process[camera/camera_nodelet_manager-1]: started with pid [2852]

                process[camera/driver-2]: started with pid [2853]

                [ INFO] [1484394479.333345250]: Initializing nodelet with 4 worker threads.

                [ INFO] [1484394479.838339157]: /camera/driver - Detected the following cameras:

                                - Serial No: 2381006343, USB Port ID: 2-1, Name: Intel RealSense R200, Camera FW: 1.0.72.10

                [ INFO] [1484394479.838452631]: /camera/driver - Connecting to camera with Serial No: 2381006343, USB Port ID: 2-1

                [ INFO] [1484394481.980436443]: /camera/driver - Setting static camera options

                [ INFO] [1484394482.024932618]: /camera/driver - Enabling Color in preset mode

                [ INFO] [1484394482.035653030]: /camera/driver - Enabling Depth in preset mode

                [ INFO] [1484394482.036438710]: /camera/driver - Starting camera

                [ INFO] [1484394482.066168496]: /camera/driver - Publishing camera transforms

                [ INFO] [1484394482.067110750]: /camera/driver - Setting dynamic camera options (r200_dc_preset=5)

                [ INFO] [1484394482.830740282]: /camera/driver - Initializing Depth Control Preset to 5

                [ INFO] [1484394482.830876368]: /camera/driver - NOTICE: Individual Depth Control values set by params will be ignored; set r200_dc_preset=-1 to override.

                [ INFO] [1484394485.583908526]: /camera/driver - Setting dynamic camera options

                terminate called after throwing an instance of 'std::runtime_error'

                  what():  VIDIOC_DQBUF error 19, No such device

                [camera/driver-2] process has finished cleanly

                log file: /home/mateusz/.ros/log/3f841286-da4f-11e6-a22c-243c200a98cb/camera-driver-2*.log

                [camera/camera_nodelet_manager-1] process has died [pid 2852, exit code -6, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=camera_nodelet_manager __log:=/home/mateusz/.ros/log/3f841286-da4f-11e6-a22c-243c200a98cb/camera-camera_nodelet_manager-1.log].

                log file: /home/mateusz/.ros/log/3f841286-da4f-11e6-a22c-243c200a98cb/camera-camera_nodelet_manager-1*.log

                all processes on machine have died, roslaunch will exit

                shutting down processing monitor...

                ... shutting down processing monitor complete

                done

                 

                [2]+  Done                    roslaunch realsense_camera r200_nodelet_default.launch

                 

                same thing got on video:

                R200 error - YouTube

                 

                I've check the camera on a proper win10 machine - it works normally

                the only thing left to check is this damn blue usb3 adapter

                • 5. Re: intel realsense r200 rdk VIDIOC_DQBUF error 19
                  MateuszR

                  ok, changing the cable to usb3 microB to microB (without adapter) worked. camera is working for over 10 minutes now and everything seems ok.

                  • 6. Re: intel realsense r200 rdk VIDIOC_DQBUF error 19
                    Intel Corporation
                    This message was posted on behalf of Intel Corporation

                    It’s great to hear you managed to solve this problem. Don’t hesitate to contact us again if help is needed, we’d be happy to assist you.

                    -Sergio