You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
To use Guidance-SDK-ROS v1.4.0,I used the guidance assistance on windows to update the guidance firmware version to v1.4.0 ,calibrate the camera and upload parameters. However, I encoutered the following questions:
after rosrun guidance guidanceNode,there are only the output of the ultrasonic and IMU data, and IMU data is 0, no other data such as obstacle distance, etc. I'm sure I have selected data in guidanceNode.cpp: select_obstacle_distance(); select_velocity();
Besides, the left and right image can be published except depth image .
So, I tried changing the firmware vision back to v1.3.7, and use the corresponding Guidance -SDK v1.3.7, which could publish all data and image normally before. However it didn't work,and the same output as above,no depth image,no velocity data, no obstacle distance, the imu data are all 0.
Kindly help me solve the problem.
The text was updated successfully, but these errors were encountered:
Hi,
To use Guidance-SDK-ROS v1.4.0,I used the guidance assistance on windows to update the guidance firmware version to v1.4.0 ,calibrate the camera and upload parameters. However, I encoutered the following questions:
after rosrun guidance guidanceNode,there are only the output of the ultrasonic and IMU data, and IMU data is 0, no other data such as obstacle distance, etc. I'm sure I have selected data in guidanceNode.cpp: select_obstacle_distance(); select_velocity();
Besides, the left and right image can be published except depth image .
So, I tried changing the firmware vision back to v1.3.7, and use the corresponding Guidance -SDK v1.3.7, which could publish all data and image normally before. However it didn't work,and the same output as above,no depth image,no velocity data, no obstacle distance, the imu data are all 0.
Kindly help me solve the problem.
The text was updated successfully, but these errors were encountered: