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

Add a note for configuring the Factory Preset Frequencies in adding devices documentations. #480

Open
i3mSuperMan opened this issue Jul 26, 2021 · 2 comments
Assignees

Comments

@i3mSuperMan
Copy link
Contributor

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

@github-actions github-actions bot added the needs/triage We still need to triage this label Jul 26, 2021
@NicolasMrad NicolasMrad added this to the 2021 Q3 milestone Jul 27, 2021
@NicolasMrad NicolasMrad removed the needs/triage We still need to triage this label Jul 27, 2021
@benolayinka
Copy link
Contributor

If @KrishnaIyer @adriansmares can provide more information about this, I can include it in #494

@NicolasMrad
Copy link
Contributor

is this still relevant?

@KrishnaIyer KrishnaIyer modified the milestones: 2022 Q1, 2022 Q2 Mar 30, 2022
@NicolasMrad NicolasMrad modified the milestones: 2022 Q2, 2022 Q3 Jun 29, 2022
@NicolasMrad NicolasMrad modified the milestones: 2022 Q3, 2022 Q4 Oct 10, 2022
@NicolasMrad NicolasMrad modified the milestones: 2022 Q4, 2023 Q1 Dec 12, 2022
@NicolasMrad NicolasMrad modified the milestones: 2023 Q1, 2023 Q2 Apr 13, 2023
@KrishnaIyer KrishnaIyer modified the milestones: 2023 Q2, Nov 2023 Oct 1, 2023
@KrishnaIyer KrishnaIyer removed this from the Nov 2023 milestone Dec 5, 2023
@KrishnaIyer KrishnaIyer added this to the Jan 2023 milestone Dec 5, 2023
@KrishnaIyer KrishnaIyer modified the milestones: Jan 2023, Jan 2024 Dec 19, 2023
@KrishnaIyer KrishnaIyer removed this from the Jan 2024 milestone Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants