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.

Sign up for GitHub

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

Jump to bottom

HIGH_LATENCY link switches to V2 #51

Open
mantelt opened this issue Dec 14, 2018 · 0 comments
Open

HIGH_LATENCY link switches to V2 #51

mantelt opened this issue Dec 14, 2018 · 0 comments
Assignees
@acfloria

Comments

@mantelt
Copy link

mantelt commented Dec 14, 2018

Setup:

  • LTE link using MAVLink V2
  • SATCOM Link

Scenario

  • Satcom link sends first message in V1.
  • QGC receives other messages over LTE link in V2, therefore setting ALL links to V2
  • when forcing to use SATCOM link, MAV_CMD_CONTROL_HIGH_LATENCY message is sent as V2 message over satcom, and PX4 switches to V2 for sending all following HIGH_LATENCY2 messages.

way forward
I made a small workaround, fixing a link that is set as high_latency link to not use V2:
b4ec373

quick test on terrace was giving the expected results. BUT, this might need yet another look, as I don't have in-depth knowledge on SATCOM functionality.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acfloria acfloria

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mantelt @acfloria