hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready ) : error on Jetson AGX Xavior #3026
Comments
Muhammadjunaidmalik1
changed the title
|
Hi @Muhammadjunaidmalik1 Using camera firmware driver 5.15.1.0 with librealsense SDK version 2.50.0 can cause errors. The recommended firmware for 2.50.0 is 5.13.0.50. |
|
Thanks for your reply. How can I move back to previous version ? |
|
If you have access to the realsense-viewer tool then you can use it to downgrade to an older firmware with its the Update Firmware option.
https://dev.intelrealsense.com/docs/firmware-releases#d400-series-firmware-downloads
|
|
Hi I am running into the same error I am using RealSense-Ros 4.51.1 on Ubuntu 20.04 and SDK version 2.54.2 which recommends firmware 5.15.1.0. I realized if I have to downgrade it to 5.13.0.5 then the SDK version has to be downgraded to 2.51.1. Since I assumed the only way to install SDK 2.51.1 is through |
thanks Marty for the guidance. That solved the major issue and the node is now working also the imu is also working for 435i in realsense viewer. But now there is another issue, I am getting this error :
When i did |
|
If the node is working normally and performance does not appear to be negatively impacted by the control_transfer returned warning then it can be safely ignored. |
|
There is an issue that its not publishing the colored point cloud : when i run when i try to see that using pointcloud2 in rviz i am geting this : |
|
The warning No stream match for pointcloud chosen texture Process - Color typically means that there are frame drops occurring on the color stream. Are you able to achieve a textured pointcloud if you add the command below to your roslaunch instruction to texture the cloud with the infrared stream instead of color?
|
|
You could also try obtaining a textured pointcloud by using the rs_rgbd launch file instead of rs_camera. Before using this launch file, support for an RGBD launch must first be installed with the instruction below. Please use the one that corresponds to the ROS1 branch that you are using. Kinetic Melodic Noetic Once RGBD support has been installed then run the launch command.
You do not need to enable the pointcloud filter with this launch file as it is already enabled by default. The pointcloud should be published to |
|
You are very welcome. I'm pleased to hear that you were successful! |
|
I am sorry for the trouble but the issue is not solved yet. I have done some tests with the camera, i have the same versions of ROS and SDK installed on my laptop and Jetson AGX Xavior. There are several issues that i am facing :) :
but it works perfectly fine for my laptop with the same versions.
it also work fine for my laptop ,but when it comes to my Jetson AGX xavior, i have to use the other launch file.
I am getting an error : method 2: i am getting an error : in this case also infrared camera is not working for both. |
|
Also in jetsonAGX xaior , sometimes even RGBD camera stream in rviz is also stopping. |
|
It's no problem at all. :)
|
|
1. i have tried various times and still the same issue. It is able to find the motion module , but it fails a bit later , here is a bit detailed version: 3,4 As it turns out not enabling infra-rgb to true makes it to work perfectly fine with all the resolutions in image:
using |
3,4. Yes, do not set infra_rgb to true when using the infrared streams. Also, I suggest using enable_infra1:=true instead of enable_infra so that only the Infra1 stream enables, otherwise it may try to enable Infra2 too and fail if the USB connection type is being detected as 2.1. |
|
|
Is the Motion Module more reliable on an RGBD launch on your Jetson?
|
|
Also getting the same error :
|
|
When you first reported the motion module problem at #3026 (comment) the warning
|
|
Hi Marty ! sorry for the delay in my response. I did not have access to my camera. Setting it to true doesn't seem to solve the issue. |
|
Is the motion module failure still present if you have both global time and sync set to true?
|
|
Altough i am getting the same error as before : its not publishing the accelerometer and gyroscope data but It is publishing a topic |
|
Another four RealSense ROS users reported this motion module failure with Jetson in particular at #2213 and IntelRealSense/librealsense#10749 (comment) so it is not just an issue with your Jetson alone. One of those users reported at IntelRealSense/librealsense#10749 (comment) that an uninstall and reinstall of the ROS wrapper resolved their motion module failure. |
|
Got it. Before closing this issue i am facing another problem as well. , I am using the camera for detection of aruco markers. But the problem is that the when I run the camera it starts giving an error:
and the camera node gives an error : the common thing between both errors is error code number 11. What do you suggest the issue is in this case ? |
|
The two messages are not related despite both having the number 11. The The aruco problem sounds like a case of the same exit code -11 with a RealSense camera at UbiquityRobotics/fiducials#144 |
|
I understand. But the weird thing about this is that the node doesn't give any error when i run it without the camera, but as soon as i run the camera it gives this error. Also, when I run the camera node it keeps on throwing this error when the call the topic related to the aruco marker. If the camera node is call seperately, it continuously publishes this error. Otherwise, There is no issue with the code for aruco maker as I have tested it on my laptop before and didnot get an issues while running. |
|
I am not familiar with this aruco detection tool. I note from the case that I linked to that the aruco launch file seems to try to access RealSense topics. For some tools, the RealSense ROS wrapper has to be launched first before the other tool that you want to use (such as your aruco detector) is then launched secondly after the RealSense launch has completed and published its topics. As you are using ROS1 Noetic, the wrapper launch instruction would be:
|
|
Yes, I have tried that as well and that case the Aruco node dies immediately with the same error. I have consulted a senior engineer as well and according to him this error is camera related issue. |
|
So your main suspect of the problem cause is that the realsense2_camera ROS wrapper node is continuously generating the |
|
Yea i suppose. |
|
You mentioned earlier at #3026 (comment) that |
|
I have tried it but unfortunately, It didn't solve the issue. The error :
is actually creating the problem. Can you please help me solve this ? |
|
When control_transfer returned warnings occur, it is rare that they can be eliminated. The best that can be hoped for is that the streams are published successfully in RViz despite the warnings, and that the rate at which the warnings are being generated in the log is reduced. Does your Xavier have a different USB port that the camera could be tried in if you have not done so already? |
|
Hi @Muhammadjunaidmalik1 Do you require further assistance with this case, please? Thanks! |
|
Hi ! I just need to ask a question, Actually I need it for pose estimation of the aruco markers , I found that realsense-viewer does not have the calibration parameters of the RGBD camera. Is there any way as well to self-calibrate it ? I have tried using the intrinsic parameters in the /camera_info node but those parameters are not giving very realistic results. |
|
The RGB sensor can be calibrated with the RealSense Dynamic Calibration software tool. It can be installed on Ubuntu using the instructions on page 14 onwards of the tool's user guide at the link below. |
|
As i understand , on page 12 it says : |
|
The tool does calibrate both the depth and RGB sensors, but only calibrates extrinsics. Calibrating intrinsics as well requires a special OEM version of the Dynamic Calibration software supplied with the $1500 USD Calibration Target Board product. https://store.intelrealsense.com/buy-intel-realsense-d400-cameras-calibration-target.html |
|
Got it thanks alot for the guidance. |
Issue Description
<Describe your issue / question / feature request / etc..>
Hi !
I just have installed Librealsense and ROS wrapper.
realsense-vieweris working perfectly fine and also SDK examples work just fine.For Jetson I have followed these intsructions for installing librealsense.
After installation of the ros wrapper , when I run :
roslaunch realsense2_camera rs_camera.launchI am getting this weird error. here is the detailed terminal output :
The text was updated successfully, but these errors were encountered: