Do not broadcast empty messages #103
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Feb 7, 2023
tridge
force-pushed
the
do_not_broadcast_empty_messages
branch
from
43d9124 to
3451aa7
Compare
tridge
force-pushed
the
do_not_broadcast_empty_messages
branch
from
3451aa7 to
61d3c3f
Compare
Agree. |
tridge
force-pushed
the
do_not_broadcast_empty_messages
branch
from
61d3c3f to
84d8bbf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The BT5. WLAN NaN and WLAN broadcast function use the odid_message_build_pack function of the opendrone ID lib to encode data. That function uses the "valid" vars of each packet (basicID, location, system etc) to determine if it needs to be encoded. The BT4 transmission uses a slightly different approach, not using these "valid" vars
In this PR: