-
Notifications
You must be signed in to change notification settings - Fork 993
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
Low publish rate on Mavros topics #1685
Comments
Did you try to use set_stream_rate / set_message_interval? |
Yah i have tried using stream rate but nothing helped...(rosservice call /mavros/set_stream_rate 1 200 1) |
https://github.com/PX4/PX4-Autopilot/blob/master/src/modules/mavlink/mavlink_receiver.h Seems PX4 doesn't support set_stream_rate anymore, could you please try |
Hey thanks for help! |
Hi @vooon I facing the same issue again!! But this time the topic /mavros/local_positon/odom and pose is working fine on 100hz but in QGC mavlink inspector the rate is again very slow.. it's 1hz there. |
@bhaskar-glitch @vooon can you help me please! PX4/PX4-Autopilot#21504 |
maybe you can try |
This is only bug and feature tracker, please use it
to report bugs or request features.
Issue details
Hii @vooon ,
I'm working on an indoor autonomous drone project and recently I found an issue in
the topics of MAVROS because the topics are being updated at a very low rate (at 1Hz) the topics I've noticed of having low update rate are: /mavros/local_position/odom , /mavros/local_position/pose
Now let me tell you the full procedure I'm doing...I'm using VINS_FUSION as odometry with d453i camera and using VIO(realsense bridge)to connect VINS and MAVROS(FCU)now the issue is that the drone doesn't know its correct altitude in real-time coz of the slow update rate I'm getting some sort of disturbance in my autonomous flight also I'm using JETSON XAVIER on edge of the drone to process everything.
MAVROS version and platform
Mavros: ?latest?
ROS: ?melodic?
Ubuntu: ?18.04?
Autopilot type and version
[ ] ArduPilot
[X] PX4
Version: ?latest?
Node logs
Diagnostics
Check ID
The text was updated successfully, but these errors were encountered: