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

Beacon format doesn't match LoRaWAN Regional Parameters 1.02 #18

Closed
terrillmoore opened this issue Jul 9, 2017 · 4 comments
Closed

Beacon format doesn't match LoRaWAN Regional Parameters 1.02 #18

terrillmoore opened this issue Jul 9, 2017 · 4 comments
Labels
bug

Comments

@terrillmoore
Copy link
Member

Neither the EU868 nor the US915 beacon offsets match the offsets in the spec. The EU868 code looks for a one-byte CRC on the time, but the regional params now clearly require a 2-byte CRC in that case. Probably everything needs a close look, and of course there's the small matter of testing....
@terrillmoore
Copy link
Member Author

This was a bug in the spec, fixed apparently in 1.0.2a. We need to review spec against code.

@terrillmoore
Copy link
Member Author

See 1.0.3 rev of spec. We should use that as our reference.

@terrillmoore
Copy link
Member Author

Although Class B is not yet supported, these have been updated in the big Class A certification update.

@terrillmoore
Copy link
Member Author

Updated to match 1.0.3 as part of #378.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@terrillmoore