-
Notifications
You must be signed in to change notification settings - Fork 69
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
Add a note for configuring the Factory Preset Frequencies in adding devices documentations. #480
Labels
Comments
If @KrishnaIyer @adriansmares can provide more information about this, I can include it in #494 |
is this still relevant? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
An ABP device should transmit uplinks only in default frequencies until the Network Server communicates the other non-default channels via MAC Commands. However, most of the devices transmit uplinks in the non-default frequencies, resulting in the drop of these packets by the Network Server. It might result in an inconsistent device state following unexpected issues.
To avoid this, the user needs to configure the
Factory Preset Frequencies
so that the NS will accept uplinks in all the channels. It is valid only for non 64-channel frequency plans (EU868/IN865/AS923/...).CC: @adriansmares to confirm and add any missing inputs.
Why do we need this ?
To let users be aware of the setting as most of the users are not aware of this behavior and in the assumption that there might be an issue at the NS end.
What is already there? What do you see now?
In the MAC Settings guide, it was mentioned how to configure Factory Preset Frequencies for ABP devices.
Ref: https://www.thethingsindustries.com/docs/devices/mac-settings/#configure-factory-preset-frequencies-for-abp-devices
What is missing? What do you want to see?
Add a note point in Adding devices documentation to configure
Factory Preset Frequencies
while creating an ABP device of non 64-channel band.How do you propose to document this?
...
Can you do this yourself and submit a Pull Request?
No
The text was updated successfully, but these errors were encountered: