Skip to content
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

Driver Node publish topics at different Interval #100

Open
zhouzhiqian opened this issue May 29, 2019 · 6 comments
Open

Driver Node publish topics at different Interval #100

zhouzhiqian opened this issue May 29, 2019 · 6 comments

Comments

@zhouzhiqian
Copy link

When I use MTI300 on Ubunty 16.04 + ROS kinetic, the intervals between every two topics don't keep 5ms (its frequency is 200 Hz).
Just like this figure:
16 04

But when I use it on Ubunty 14.04 + ROS indigo, it shows a totally different result.
mti300

)

@fcolas
Copy link
Contributor

fcolas commented Aug 25, 2019

That's a new issue for me.
Does it happen consistently or just sometimes (and if so, in which condition)?
I assume you checked it was not a CPU performance issue and only run the mtnode to reduce outside influences.
Is it the same system with two different installs or are there differences in the CPU/USB bus?

@MichalNowicki
Copy link

I experienced this issue on a similar configuration and in our case, it was caused by the latency settings of the Ubuntu driver for FTDI. The solution was to set the low_latency mode of the driver and thus prevent it from accumulating multiple measurements.

The command to execute after the device was plugged in:
setserial /dev/<tty_name> low_latency

The setting resets once the device is disconnected but udev rules can be used to make it permanent.

@zhouzhiqian
Copy link
Author

@MichalNowicki Thank you very much. I will try your solution quickly.

@artemiialessandrini
Copy link

Hi, I am having the same issue of publisjing with different interval partially:

image

While trying to setserial /dev/ttyUSB0 low_latency, I get:
Cannot get serial info: Inappropriate ioctl for device

@artemiialessandrini
Copy link

@zhouzhiqian was it a solution for you?

@artemiialessandrini
Copy link

Apparently, rosbag_validate displays the same ERROR:
E1008 14:32:31.060365 31665 rosbag_validate_main.cc:389] IMU data (frame_id: "imu_link") has a large gap, largest is 0.660078 s, recommended is [0.0005, 0.005] s with no jitter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants