You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: