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
Great work on Express LRS - it's now my default radio link.
The issue:
What we see with HM 2.4 is quiet a number of people having issues with the JR connector (esp. early models).
The humble request:
Propose to show in LUA the last (intermittent) disconnection or communication interruption date & time. If your quad falls out of the sky and you see there was a communication disconnect seconds ago, you at least know you have to troubleshoot your radio-TX module link rather than your quad-RX combination or betaflight fs settings. Of course using this concept you could also create a proper warning message in LUA. After reconnection the issue may otherwise be unnoticed (esp. if the quad survived the crash and the battery, fc and RX are still ok - you would only get a 'telemetry lost' / 'telemetry recovered' message).
Instead of commenting "I want this too", consider leaving a 👍 instead, to reduce spam and clutter
This discussion was converted from issue #936 on January 24, 2022 21:36.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Great work on Express LRS - it's now my default radio link.
The issue:
What we see with HM 2.4 is quiet a number of people having issues with the JR connector (esp. early models).
The humble request:
Propose to show in LUA the last (intermittent) disconnection or communication interruption date & time. If your quad falls out of the sky and you see there was a communication disconnect seconds ago, you at least know you have to troubleshoot your radio-TX module link rather than your quad-RX combination or betaflight fs settings. Of course using this concept you could also create a proper warning message in LUA. After reconnection the issue may otherwise be unnoticed (esp. if the quad survived the crash and the battery, fc and RX are still ok - you would only get a 'telemetry lost' / 'telemetry recovered' message).
Instead of commenting "I want this too", consider leaving a 👍 instead, to reduce spam and clutter
Beta Was this translation helpful? Give feedback.
All reactions