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.

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

SF5 and SF6 supported only for private 0x12 syncword #124

Open
reissjason opened this issue Jun 17, 2024 · 3 comments
Open

SF5 and SF6 supported only for private 0x12 syncword #124

reissjason opened this issue Jun 17, 2024 · 3 comments

Comments

@reissjason
Copy link

Would there be any issue changing SF5 and SF6 to use the public 0x34 syncword?

@mcoracin
Copy link
Contributor

Yes, the 0x34 syncword cannot be coded for SF5, and for SF6 the sensitivity is degraded. That's why we kept 0x12 for public for SF5/SF6 in the hal.

@rsoss
Copy link

rsoss commented Jun 17, 2024

Hi @mcoracin does it mean that we must use the 0x12 (private syncword) for SF5/6? How would this interact with public syncword (0x34) for SF7...12 on the same gateway?

@mcoracin
Copy link
Contributor

Yes, you must use 0x12 for SF5/SF6.
The syncword configuration is per SF so it is not an issue to have SF5-6 with 0x12, and SF7-12 with 0x34.
The end-device has to use the proper syncword depending on the SF used for transmission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants