roslaunch realsense2_camera rs_camera.launch error #1191
Comments
|
The error get_device_time_ms() took too long (more then 2 mSecs) has been a well documented error with SDK 2.34.0. I would recommend using the previous Librealsense version 2.33.1 if possible until the error is fixed. I do apologise for the inconvenience. |
So how can I change it to Librealsense version 2.33.1 by a commend or link ?? Edit : |
|
I haven't done this process of installing a specific SDK on Linux myself, so I apologise in advance for any mistakes. I would speculate that it could be done in the following way:
https://github.com/IntelRealSense/librealsense/releases/tag/v2.33.1 If you scroll down to the page, you should come to a section titled Assets where the source code zip file for 2.33.1 can be downloaded from.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
I note that you added an edit that you tried the 2.33.1 link. What happened when you did so, please? |
Thank you for your efforts in the project and the issues fixing but please write down in SDK 2.34 it’s have a bug until you solve it to avoid any loss in time and efforts . |
|
There is a fix that has been created for the error but it has not passed review by the developers for implementation into the SDK yet, unfortunately. IntelRealSense/librealsense#6150 A new version of the Librealsense SDK should be released soon, so it may be worth @doronhi the RealSense ROS wrapper developer adding a note about the error to the wrapper release notes if the new SDK release does not correct the get_device_time_ms error. |
I removed every thing from SDK 2.34 and reinstall SDK 2.33 by your links but I have the same problem and realsense-viwer is on SDK 2.34 after I install SDK 2.33 !!!! eslam@root:~/catkin_ws$ roslaunch realsense2_camera rs_d435_camera_with_model.launch xacro: in-order processing became default in ROS Melodic. You can drop the option. started roslaunch server http://root:39707/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 9bbfb072-9145-11ea-acda-64006afb8a06 [ INFO] [1588953905.261270121]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/video4linux/video2 was found.
|
|
I'm very sorry that using the previous Librealsense version did not solve your problem. Are you able to view the output of camera topics in RViz, please? That would indicate that the topics are being published correctly despite the error messages. |
Unfortunately it can’t load the camera or run it including the topics ... |
|
There was a case a month ago who had almost identical errors to yours when their process died. There was not a successful resolution in that case, unfortunately. The logs suggest that you are using the camera in a USB 2 port. If so, do you have an available USB 3 port that you can try the camera in please to see if it makes a difference? |
Definitely it’s not the same error and already I connect it by USB 3 because I read the previous issues with the cameras |
|
Please try a different launch instruction and see if it publishes a pointcloud: roslaunch realsense2_camera demo_pointcloud.launch |
I found the seme error !! |
|
When you say that you "got the same error", do you mean that you got the same errors as before when using the different point cloud launch instruction that I suggested, please? |
Yes that’s what I mean .. |
|
Same result if you drop 'filters' from the launch instruction and just do roslaunch realsense2_camera rs_camera.launch ? If that does not work, try deleting your workspace build folder and building again. |
I did all of this and what I revived : eslam@root:~/catkin_ws$ roslaunch realsense2_camera rs_camera.launch started roslaunch server http://root:46575/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 6a288564-91fb-11ea-99da-64006afb8a06 [ INFO] [1589031996.406947149]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/video4linux/video2 was found. |
|
I notice that the log referred to T265 this time, and your other new case on the main GitHub also mentioned T265. Do you have both a T265 and a D435 attached to the computer at the same time? |
Firstly I tried without T265 then I found the old error with types.h after that I connected the both cameras and tried and the previous error what I got . |
|
Using the T265 and D435 on the same computer together in ROS can cause problems, because if the D435 is recognised by the computer first then it can stop the T265 from working. A launch file for using the D435 and T265 together was created: roslaunch realsense2_camera rs_d400_and_t265.launch |
when I tried : roslaunch realsense2_camera rs_d400_and_t265.launch : eslam@root:~/catkin_ws$ roslaunch realsense2_camera rs_d400_and_t265.launch started roslaunch server http://root:33519/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 36cd1824-9200-11ea-99da-64006afb8a06 [ INFO] [1589034056.948350646]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/video4linux/video2 was found. [ INFO] [1589034056.948964318]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/video4linux/video2 was found. [ INFO] [1589034066.002891211]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/video4linux/video2 was found. |
|
I'm sorry that the roslaunch realsense2_camera rs_d400_and_t265.launch launch instruction did not solve your problem. At this point, because the case now involves the T265 I will have to refer it to a support manager to see what they say, as I am not a T265 engineer. I apologise very much for the delay this will cause in the meantime. |
but my problem in the both cameras not only T265 !!! |
|
I am sorry, if a case involves T265 at all then I cannot take it on and would not have been able to start this case if I had known that a T265 was being used. I understand how frustrating this is for you. I have referred the case to a support manager above me. |
Thank you for your efforts and support and I hope he can replay on me as fast as he can because I’m working by this two cameras on my graduation project so I don’t have any time to wait. |
|
I will emphasise to them that speed of answering is important due to your graduation project. I have an engineering degree, so I remember what graduation projects are like! |
that's great , all we can found from this project only errors in the cameras also in objectdetection by the depth camera. |
|
Please do not wait at the computer for a response as I do not know when they will reply. It might not even be today. You should receive an email when somebody replies in the same way that you do when I make a comment. I hope that you can find another aspect of your project to work on in the meantime. |
yes, I know I'll leave it . |
|
Thanks very much for your understanding. I wish the very best for you too. Good luck! :) |
|
Hi @Eslamrady42 , Assuming v.2.33.1, using D435 camera alone, running Can you check T265 alone, without D435 or any other node (Using |
First of all thank you for your fast response, secondly I don’t know how to clean up my machine from SDK 3.34 if you have a method or link to follow up I’ll do it now, this command what I used for clean up my machine (Remove all RealSense™ SDK-related packages with: @doronhi I’m waiting for your answer please..! |
PARAMETERS
NODES auto-starting new master setting /run_id to d5fe6fdc-9bf7-11ea-873c-80a58951a411 [ INFO] [1590129934.912518905]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:1.0/video4linux/video0 was found. |
|
@Eslamrady42 , Sorry for the late response. Hopefully I'll be more available in the next couple of days. You referred to Librealsense issue 6374. In the log there I can see "Running with LibRealSense v2.33.1" The method you showed to remove librealsense2 seems good. If you built from source you also need to remove this version : You've create another issue for the T265 error ("SLAM_ERROR"). I don't know how to help with that one yet but it is a good thing to try and separate the issues. |
|
@zustwangmingjun Finally, I will appreciate it if you opened a new, specific issue, with details regarding your machine and OS, if needs further assistance. |
|
I'm running into the launch issue with similar error message as OP. The launch file worked before but I recently updated to I enabled this=<optimized out>) at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/types.h:415
#34 librealsense::sensor_base::get_stream_profiles (this=<optimized out>, tag=<optimized out>)
at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/sensor.cpp:196
#35 0x00007fffda494e6c in rs2_get_stream_profiles (sensor=0x7fffa4091570, error=0x7fffa8b2c238)
at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/rs.cpp:306
#36 0x00007fffdb4f1a4b in rs2::sensor::get_stream_profiles (this=0x7fffa4090f28)
at /usr/include/librealsense2/hpp/rs_sensor.hpp:228
#37 0x00007fffdb4d6594 in realsense2_camera::BaseRealSenseNode::enable_devices (this=0x7fffa401e130)
at /home/truhoang/1-Project_Code/ubtech_ws/src/realsense-ros/realsense2_camera/src/base_realsense_node.cpp:903
#38 0x00007fffdb4c9aa5 in realsense2_camera::BaseRealSenseNode::publishTopics (this=0x7fffa401e130)
at /home/truhoang/1-Project_Code/ubtech_ws/src/realsense-ros/realsense2_camera/src/base_realsense_node.cpp:191
#39 0x00007fffdb490d1f in realsense2_camera::RealSenseNodeFactory::StartDevice (this=0x55555624c940)
at /home/truhoang/1-Project_Code/ubtech_ws/src/realsense-ros/realsense2_camera/src/realsense_node_factory.cpp:320@doronhi @MartyG-RealSense Does this provide any clue to you? |
|
Downgraded [ INFO] [1591148280.396089253]:
02/06 18:38:00,406 ERROR [140402921432832] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
02/06 18:38:00,427 WARNING [140403035809536] (rs.cpp:283) null pointer passed for argument "device"
[ WARN] [1591148280.427877974]: Device 1/1 failed with exception: failed to set power state
[ERROR] [1591148280.427915510]: The requested device with device name containing d435 is NOT found. Will Try again.On |
|
@truhoang-ubtrobot , |
|
Does this issue still occur with the latest SDK and ROS updates? *If we don’t hear from you in 7 days, this issue will be closed. |
|
Thank you for your late reply but all of the problems solved by changing the Ubuntu 18 to Ubuntu 16 and ROS melodic to ROS Kinetic.. |
|
I offer sincere apologies for the delays that you experienced on this particular case @Eslamrady42 ... as you have found a solution yourself, I will close this case now. Thanks again! |
roslaunch realsense2_camera rs_camera.launch filters:=pointcloud /////// I have error with this command:
eslam@root:~/catkin_ws$ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud
... logging to /home/eslam/.ros/log/41c06a78-910c-11ea-acda-64006afb8a06/roslaunch-root-3896.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://root:40451/
SUMMARY
PARAMETERS
NODES
/camera/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
auto-starting new master
process[master]: started with pid [3906]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 41c06a78-910c-11ea-acda-64006afb8a06
process[rosout-1]: started with pid [3917]
started core service [/rosout]
process[camera/realsense2_camera_manager-2]: started with pid [3924]
process[camera/realsense2_camera-3]: started with pid [3925]
[ INFO] [1588929252.264289140]: Initializing nodelet with 4 worker threads.
[ INFO] [1588929272.557688200]: RealSense ROS v2.2.13
[ INFO] [1588929272.557787898]: Running with LibRealSense v2.34.0
[ INFO] [1588929272.583431094]:
[ INFO] [1588929272.597819765]: Device with serial number 944122071903 was found.
[ INFO] [1588929272.597875863]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/video4linux/video2 was found.
[ INFO] [1588929272.597896405]: Device with name Intel RealSense D435 was found.
[ INFO] [1588929272.598413755]: Device with port number 2-1 was found.
[ INFO] [1588929272.600727501]: getParameters...
[ INFO] [1588929272.637379972]: setupDevice...
[ INFO] [1588929272.637419626]: JSON file is not provided
[ INFO] [1588929272.637453452]: ROS Node Namespace: camera
[ INFO] [1588929272.637472675]: Device Name: Intel RealSense D435
[ INFO] [1588929272.637489932]: Device Serial No: 944122071903
[ INFO] [1588929272.637508621]: Device physical port: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/video4linux/video2
[ INFO] [1588929272.637525629]: Device FW version: 05.12.03.00
[ INFO] [1588929272.637541777]: Device Product ID: 0x0B07
[ INFO] [1588929272.637557813]: Enable PointCloud: On
[ INFO] [1588929272.637575102]: Align Depth: Off
[ INFO] [1588929272.637590461]: Sync Mode: On
[ INFO] [1588929272.637639875]: Device Sensors:
[ INFO] [1588929272.637681500]: Stereo Module was found.
[ INFO] [1588929272.637706417]: RGB Camera was found.
[ INFO] [1588929272.637773652]: (Fisheye, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1588929272.637790204]: (Fisheye, 1) sensor isn't supported by current device! -- Skipping...
[ INFO] [1588929272.637808843]: (Fisheye, 2) sensor isn't supported by current device! -- Skipping...
[ INFO] [1588929272.637825506]: (Gyro, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1588929272.637842054]: (Accel, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1588929272.637857771]: (Pose, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1588929272.637882562]: Add Filter: pointcloud
[ INFO] [1588929272.638352255]: num_filters: 1
[ INFO] [1588929272.638371332]: Setting Dynamic reconfig parameters.
[ INFO] [1588929272.665594617]: Done Setting Dynamic reconfig parameters.
[ INFO] [1588929272.667652466]: depth stream is enabled - width: 640, height: 480, fps: 30, Format: Z16
[ INFO] [1588929272.667835338]: infra1 stream is enabled - width: 640, height: 480, fps: 30, Format: Y8
[ INFO] [1588929272.667999758]: infra2 stream is enabled - width: 640, height: 480, fps: 30, Format: Y8
[ INFO] [1588929272.671682819]: color stream is enabled - width: 640, height: 480, fps: 30, Format: RGB8
[ INFO] [1588929272.671714724]: setupPublishers...
[ INFO] [1588929272.673530542]: Expected frequency for depth = 30.00000
[ INFO] [1588929272.695807088]: Expected frequency for infra1 = 30.00000
[ INFO] [1588929272.707848730]: Expected frequency for infra2 = 30.00000
[ INFO] [1588929272.722153323]: Expected frequency for color = 30.00000
[ INFO] [1588929272.737794460]: setupStreams...
[ INFO] [1588929272.738547885]: insert Depth to Stereo Module
[ INFO] [1588929272.738594438]: insert Color to RGB Camera
[ INFO] [1588929272.738618780]: insert Infrared to Stereo Module
[ INFO] [1588929272.738642169]: insert Infrared to Stereo Module
[ INFO] [1588929272.744466230]: SELECTED BASE:Depth, 0
[ INFO] [1588929272.801163125]: RealSense Node Is Up!
08/05 11:14:32,968 ERROR [140683238541056] (types.h:307) get_device_time_ms() took too long (more then 2 mSecs)
08/05 11:14:33,170 ERROR [140683238541056] (types.h:307) get_device_time_ms() took too long (more then 2 mSecs)
08/05 11:14:33,439 ERROR [140683238541056] (types.h:307) get_device_time_ms() took too long (more then 2 mSecs)
08/05 11:14:33,641 ERROR [140683238541056] (types.h:307) get_device_time_ms() took too long (more then 2 mSecs)
08/05 11:14:39,102 ERROR [140683238541056] (types.h:307) get_device_time_ms() took too long (more then 2 mSecs)
[camera/realsense2_camera_manager-2] process has died [pid 3924, exit code -11, cmd /opt/ros/melodic/lib/nodelet/nodelet manager __name:=realsense2_camera_manager __log:=/home/eslam/.ros/log/41c06a78-910c-11ea-acda-64006afb8a06/camera-realsense2_camera_manager-2.log].
log file: /home/eslam/.ros/log/41c06a78-910c-11ea-acda-64006afb8a06/camera-realsense2_camera_manager-2*.log
^C[camera/realsense2_camera-3] killing on exit
[rosout-1] killing on exit
[rosout-1] escalating to SIGTERM
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
The text was updated successfully, but these errors were encountered: