New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
librealsense / ros-wrapper issue - Failed to read busnum/devnum. #1095
Comments
Suggest to use L4T 28.2 BSP instead of the L4T 28.1 BSP which has the stability issue. Probably, you see sometimes the librealsense app can run at the 2nd try. You can also apply the patch for 28.2. |
Hello @compiaffe, thank you for the detailed information. |
@freemanlo I am using 28.2 already: https://github.com/aivero/buildJetsonTX2Kernel/blob/fix/jetson_tx2/scripts/getKernelSources_noGUI.sh#L6 @icarpis great that you could already identify a firmware bug, is this relate to #1086 ? However, it does not work around the issues when starting a ROS node: Did you reproduce the ROS behaviour or the |
I reproduced the ROS behavior and I have w/o it by replugging the camera every time before using the Launch file. |
OK, I have not been able to work around it on the Jetson TX2. However, thinking about it I was already using that workaround on the laptop. Still the issues on the Jetson is a bit of a mystery. Could it be connected to the |
I am running on a J120 carrier board by Auvidea: https://auvidea.com/j120/ so trying a PCI USB controller card is not a quick option. I re-installed the kernel patches by running the following three commands from the new branch
And installed the newest wrapper As mentioned in your workaround - replugging the camera or simply restarting the rosnode works now. So that is fixed. However, I still get the same
|
I also get frame didn't arrived in 5seconds wanrings. And there is no streaming GUI for me to see if I get images. Does this means it is publishing empty image? My project requires me to subscribe to publisher and record stream of images. Please let me know how this can be done. Thank you! |
If I'm not getthing those warnings, does that mean it is publishing image topics? There isn't supposed to be streaming GUI, correct? Thank you! |
@ykim104 What do you mean by
In ROS, you can check if data arrives by first starting the node with i.e.
and then checking the rate of messages on one of the topics:
If you are looking for a pointcloud keep in mind that those are turned off in most of the launch files. |
@icarpis Coming back to the original issue here, the
Do you have suggestions on how this can be fixed? |
@compiaffe, as I already mentioned, the message of |
@icarpis Replugging or restarting works. However, I cannot not open the fisheye and UYVY is missing. I will open a new issue for this though. Thank you for the help :) |
The device path: /sys/bus/iio/devices/iio:device0 (actually iio:device0 through ii:device3) is the ina3221x power monitor on board the Jetson module. The library code here makes the assumption that there is an associated bus number and device number in the directory structure, and issues the warning when it can not find it. I believe that the power monitor is on an internal i2c bus which is not advertised. The warning can be ignored, or guard code can be placed for that particular instance. |
Join query thread
Issue Description
I am not 100% sure this is a librealsense or a ros-wrapper issue:
When starting the the basic
roslaunch realsense_ros_camera rs_aligned_depth.launch
the node starts, but does not publish any images and warns about:or in full beauty:
The
librealsense
has been build from source and enumerates,and measure distance. However, it sometimes hangs/works on second execution
The udev rules are installed:
The user is in the right groups:
The kernel patches were installed using a modified
patch-realsense-ubuntu-xenial.sh
script as per the instructions indocs/install_jetson.md
:https://github.com/aivero/librealsense/blob/jetson-tx2-install/scripts/patch-realsense-ubuntu-xenial.sh#L26
It is based on a slightly modified version of the install script by JetsonHacks (now also a submodule in above mentioned repo): https://github.com/aivero/buildJetsonTX2Kernel/blob/fix/jetson_tx2/scripts/getKernelSources_noGUI.sh
The 2 differences are that I am now pulling v2.0 of the r28 L4T and that I am skipping the (GUI) kernel configuration. We only want the kernel sources I understand.
Any ideas what this could be?
Thanks a lot :)
The text was updated successfully, but these errors were encountered: