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

Mavlink telemetry stream rates #4052

Conversation

@raul-ortega
Copy link
Contributor

commented Dec 3, 2018

This will allow users to decide which telemetry data stremas will be sent, and its frequency, to ground station. It will be very useful for people who only needs to send gps data to one tracker for aplications where the fluidity in movement is important.

mavlink_extended_status_rate
mavlink_rc_channels_rate
mavlink_position_rate
mavlink_extra1_rate
mavlink_extra2_rate

If the value is 0 the data stream will not be sent, however if the value is 1 or higer it will be sent with that frequency, e.g.:

set mavlink_extended_status_rate=0
set mavlink_rc_channels_rate=0
set mavlink_position_rate=5
set mavlink_extra1_rate=0
set mavlink_extra2_rate=0

Only position data stremas will be sent at a frequency of 5Hz.

raul-ortega and others added some commits Dec 2, 2018

Added 5 new variables to CLI for configuring the frequency of mavlink
telemetry streams. This will allow users to decide which telemetry data
will be sent to ground station. It will be very useful for people that
only needs to send gps data to one tracker for aplications where the
fluidity in movement is important
  
mavlink_extended_status_rate 
mavlink_rc_channels_rate
mavlink_position_rate
mavlink_extra1_rate
mavlink_extra2_rate

@shellixyz shellixyz added this to the 2.1 milestone Dec 17, 2018

utsxumiao and others added some commits Dec 30, 2018

@digitalentity digitalentity modified the milestones: 2.1, Future Jan 5, 2019

@Schakus

This comment has been minimized.

Copy link

commented Jan 27, 2019

Is it implemented in the current version? I want to use it via FPORT Telemetry.

Kurtoid and others added some commits Jan 31, 2019

Merge pull request #4292 from Kurtoid/kurtoid-documentation
add DSHOT settings to cli documentation
Merge pull request #4294 from iNavFlight/revert-4292-kurtoid-document…
…ation

Revert "add DSHOT settings to cli documentation"
Merge pull request #3 from raul-ortega/master
Master to mavlink_telemetry_frequency

@digitalentity digitalentity modified the milestones: Future, 2.2 Feb 25, 2019

@shellixyz

This comment has been minimized.

Copy link
Collaborator

commented May 25, 2019

Superseded by #4741, closing

@shellixyz shellixyz closed this May 25, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.