Skip to content
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.

Sign up for GitHub

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

Jump to bottom

US Data Rate Decay testing fails #388

Closed
terrillmoore opened this issue Aug 24, 2019 · 0 comments
Closed

US Data Rate Decay testing fails #388

terrillmoore opened this issue Aug 24, 2019 · 0 comments
Assignees
@terrillmoore
Labels
bug

Comments

@terrillmoore
Copy link
Member

RWC5020A test 9.4 watches the device as it reduces data rate in the face of no feedback from the network. At the minimum data rate, the device is expected not to set ADRack request. The current LMIC leaves it set.

There's a tension here, but I guess we should depend on the network to notice that we've gone to the highest data rate and send us parameters.
@terrillmoore terrillmoore self-assigned this Aug 24, 2019
@terrillmoore terrillmoore mentioned this issue Aug 24, 2019
Closed
terrillmoore added a commit that referenced this issue Sep 1, 2019
@terrillmoore
Fix #388: Fix #389: Fix #390: honor uplink max frame size
5fba364
terrillmoore added a commit that referenced this issue Sep 3, 2019
@terrillmoore
Version is 3.0.99.0
17f2854 
Semantic Versions require that we bump the version on a breaking
change, and #388 is certainly that; many apps may stop working
unless they really accomodate the packet size changing based on
the current data rate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@terrillmoore terrillmoore

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@terrillmoore