-
Notifications
You must be signed in to change notification settings - Fork 317
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
Fine grained ADR NbTrans controls #6962
Conversation
8bba752
to
b936589
Compare
b936589
to
9524f26
Compare
Would it be too complex/out of scope to be able to set this on all devices on an application? |
Yes, because we don't have any mechanism at NS level for MAC settings grouping. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM. For the feature review, I'll defer to @johanstokking.
Summary
This PR introduces the capability to limit the NbTrans of an end device on a per data rate basis. This allows lower data rates to have a limited NbTrans while higher data rates can benefit from additional transmissions when needed.
Refs #6966
Changes
Testing
app1
and a deviceeui-1231231231231231
we start by setting the minimum NbTrans override to 2.We then attempt to set the max NbTrans to 1, expecting an error.
We then set the max NbTrans to 3, expecting this to succeed.
Finally, we check that the values have been stored.
The above test can be done on any data rate index.
LinkADRReq
events. This assumes that the device operates in a band where SF7 is data rate index 5. Adjust accordingly if that's not the case.Regressions
The overrides have no effect on existing devices. As such, no specific regressions are expected.
Notes for Reviewers
@KrishnaIyer please take a look.
Checklist
README.md
for the chosen target branch.CHANGELOG.md
.CONTRIBUTING.md
, there are no fixup commits left.