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
{{ message }}
This repository has been archived by the owner on Apr 30, 2024. It is now read-only.
Hi there,
I'm trying to set the rate at which IMU topic is published. I only need IMU, thus I close other streams. Specifically I run these commands:
rosparam set /inertial_sense_node/stream_DID_INS_1 false
rosparam set /inertial_sense_node/stream_DID_INS_2 false
rosparam set /inertial_sense_node/stream_DID_INS_3 false
rosparam set /inertial_sense_node/stream_GPS1 false
rosparam set /inertial_sense_node/stream_GPS2 false
rosparam set /inertial_sense_node/stream_GPS3 false
rosparam set /inertial_sense_node/stream_IMU true
Then I set period multiple of IMU to 100 so that I get IMU data at a rate of 10 fps: rosparam set /inertial_sense_node/imu_period_multiple 100
Then I start inertial_sense_node with the following command: rosrun inertial_sense_ros inertial_sense_node
However, when I echo topics in a separate terminal using the following command, I see that the data is coming at a much fater rate than I expect. rostopic echo /imu
Is this expected behavior ?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
I'm trying to set the rate at which IMU topic is published. I only need IMU, thus I close other streams. Specifically I run these commands:
Then I set period multiple of IMU to 100 so that I get IMU data at a rate of 10 fps:
rosparam set /inertial_sense_node/imu_period_multiple 100
Then I start inertial_sense_node with the following command:
rosrun inertial_sense_ros inertial_sense_node
However, when I echo topics in a separate terminal using the following command, I see that the data is coming at a much fater rate than I expect.
rostopic echo /imu
Is this expected behavior ?
The text was updated successfully, but these errors were encountered: