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

Could I get both gyroscope and accelemeter topic more than 100hz? #1041

Closed
jinwandou opened this issue Dec 30, 2019 · 2 comments
Closed

Could I get both gyroscope and accelemeter topic more than 100hz? #1041

jinwandou opened this issue Dec 30, 2019 · 2 comments

Comments

@jinwandou
Copy link

No description provided.

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Dec 30, 2019

The FPS rates of the T265 are fixed.

IntelRealSense/librealsense#4103 (comment)

IntelRealSense/librealsense#4592 (comment)

There are workarounds that some users have successfully applied to achieve custom FPS rates though. This includes:

(1) Getting every nth frame instead of all frames in order to simulate a certain frame rate. Or:
(2) Instead using some form of timer to achieve the desired frequency.

In September 2019, one user's workaround that worked for them was to write a RealSense ROS node in C++ that is controlled by a 'rate' They tried to write a node in Python too but found it to be ineffective.

The link below provides an explanation about rates in ROS.

https://roboticsbackend.com/ros-rate-roscpy-roscpp/

Another user achieved the same effect by setting up a timer in QT instead of using ROS. The timer fired every 100 ms to get a 10hz frequency.

@RealSenseCustomerSupport
Copy link
Collaborator


Thanks MartyG-RealSense for the links and info

Hi @jinwandou
Is there anything further needed on this thread? The FPS rates for T265 are indeed fixed.

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

No branches or pull requests

3 participants