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

Erratic behaviour when other Mavlink systems are sending hearbeats on the same link #1523

Closed
walmis opened this issue Jul 18, 2015 · 1 comment

Comments

@walmis
Copy link

walmis commented Jul 18, 2015

When connecting to a drone (APM:Copter 3.3) which features MAVLink routing, mavlink heartbeats and other packets from other systems are forwarded to DroidPlanner. In my case there are heartbeats from APM:Copter, Storm32 gimbal and Radio controller. When DroidPlanner receives heartbeat messages from different systems it switches modes, changes buttons, and constantly notifies - gps 3d lock, gps lost, gps 3d lock, gps lost and so on. It then becomes unusable.
A simple fix would be to filter out non-autopilot systems based from HEARTBEAT.autopilot messages.

@m4gr3d
Copy link
Member

m4gr3d commented Jul 19, 2015

@walmis this is a duplicate for dronekit/dronekit-android#124
Could you report there instead.
thanks!

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

2 participants