You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's helpful to have this info all in one nice area as found in the old doc set. It is US915 specific, so perhaps making growth allowance for the same region info for other Non US915 regions would be good as well.
This could perhaps meld in with where the ADR discussion is, although it's not just ADR.
The behavior around what the initial LinkAdrReq is for and that it will repeat if not ack'd is helpful.
Might re-emphasize the initial REQ is not intended to modify Data Rate or Power. I "guess" it does return values that were found in the corresponding uplink??
And that subsequent LinkAdrReq's might be received per ADR.
The text was updated successfully, but these errors were encountered:
A couple of things missing from the new doc set, or if there are not found via search
Regional Channels & Data Rates:
https://github.com/helium/devdocs/blob/master/longfi/regional-channels.md
It's helpful to have this info all in one nice area as found in the old doc set. It is US915 specific, so perhaps making growth allowance for the same region info for other Non US915 regions would be good as well.
MAC Commands, FOpts, ADR, FCnt:
https://github.com/helium/devdocs/blob/master/longfi/mac-commands-fopts-adr.md
This could perhaps meld in with where the ADR discussion is, although it's not just ADR.
The behavior around what the initial LinkAdrReq is for and that it will repeat if not ack'd is helpful.
Might re-emphasize the initial REQ is not intended to modify Data Rate or Power. I "guess" it does return values that were found in the corresponding uplink??
And that subsequent LinkAdrReq's might be received per ADR.
The text was updated successfully, but these errors were encountered: