mavlink / qgroundcontrol

Cross-platform ground control station for drones (Android, iOS, Mac OS, Linux, Windows)
http://qgroundcontrol.io
3.2k stars 3.54k forks source link

"Communication Lost/Regained" pop up should be removed! #9839

Closed DavidMCampbell closed 3 months ago

DavidMCampbell commented 3 years ago

Imagine you are constantly losing and regaining signal. You don't want to constantly dismiss that annoying pop up! There are already other visual and audible cues. No need for the pop up!

https://discuss.ardupilot.org/t/constant-connection-lost-connection-restored-pop-ups-on-android-bluetooth/74306

jafrado commented 3 years ago

It used to just annunciate … I guess your point is that removing all those modal windows is a real pain in the ass while flying 😀

Normally, that should only ever really be an issue if you’re facing radio problems or the FC firmware is right on the edge of the 1 second heartbeat time out (e.g. keep alive packet delayed because Firmware is overloaded). I’ve seen this a few times with balloons over 100,000 feet (on the edge of the fresnel zone) and in other cases it generally indicated a radio or antenna problem.

Can you modify your firmware to send keepalives every 950 ms or are you flying right at the edge and just getting a deluge of pop-ups?

DavidMCampbell commented 3 years ago

There are many scenarios where there could be periods of time (greater than 1 second) where there are no mavlink messages. For example, you have a waypoint mission that goes around a mountain or hill, or have a few waypoints that will be blocked by a land mass, or flying right on the edge, like you said.

Yes, it's annoying to have to click on the modals/popups while flying. Usually it has announced that it has lost in regained connection multiple times and I have to rapidly tap ok to clear everything out so I can see the map again.

On Tue, Aug 24, 2021, 7:38 AM James F. Dougherty @.***> wrote:

It used to just annunciate … I guess your point is that removing all those modal windows is a real pain in the ass while flying 😀

Normally, that should only ever really be an issue if you’re facing radio problems or the FC firmware is right on the edge of the 1 second heartbeat time out (e.g. keep alive packet delayed because Firmware is overloaded). I’ve seen this a few times with balloons over 100,000 feet (on the edge of the fresnel zone) and in other cases it generally indicated a radio or antenna problem.

Can you modify your firmware to send keepalives every 950 ms or are you flying right at the edge and just getting a deluge of pop-ups?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/9839#issuecomment-904701443, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2T6RLOOD6QRRI62B22XALT6OVHZANCNFSM5CWBRCGQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

louisrm commented 3 years ago

It looks like this was discussed a few months ago here: https://github.com/mavlink/qgroundcontrol/issues/9486. Does your build contain this update?

DavidMCampbell commented 3 years ago

@louisrm I think so. I'm using v4.1.1 64bit on Android.

edit: Actually, on google play, the app was last updated on Jan 27, 2021. I had to DL manually from https://qgroundcontrol.s3-us-west-2.amazonaws.com/latest/QGroundControl64.apk