-
Notifications
You must be signed in to change notification settings - Fork 3k
LoRaWAN: Custom FSB selection in US and Australian regions #7802
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
Conversation
@AnttiKauppila @kivaisan @kjbracey-arm Please review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok.
ad0d382
to
15be906
Compare
@kjbracey-arm Please review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine, just still unclear on the difference in mask handling between the two channel types.
@@ -580,6 +578,8 @@ lorawan_status_t LoRaPHYAU915::set_next_channel(channel_selection_params_t* next | |||
if ((current_channel_mask[4] & 0x00FF) == 0) { | |||
// fall back to 500 kHz default channels | |||
current_channel_mask[4] = channel_mask[4]; | |||
} else { | |||
current_channel_mask[4] &= channel_mask[4]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this addition, which doesn't mirror the code for 125kHz channels above? Is it because of the lack of &=
in link_ADR_request
? (I recall previous discussion of that, but don't remember the explanation, and there's no comment in the code).
15be906
to
6502f22
Compare
@kjbracey-arm Please review again. Suggestions entertained. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, two comments;
- I think it would be good to clarify that this library targets PHY 1.0.2 rev B
- I would recommend writing in the documentation to use the FSB mask only on private networks where you know beforehand what FSB is being used and/or in case of ABP. With OTAA, certainly on public networks, it's highly recommended to use the channel probing strategy as defined in PHY
features/lorawan/FSB_Usage.txt
Outdated
@@ -0,0 +1,35 @@ | |||
Frequency sub-bands in US915/US915Hybrid/AU915: | |||
|
|||
US915/US915Hybrid/AU915 PHYs define channel structures which can support up-to 72 channels for upstream. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
US915Hybrid
is gone now
b367c3c
to
f4aec91
Compare
@cmonr need CI here again. Breakage doesn't relate to this PR. |
@kjbracey-arm Please review. |
@hasnainvirk Thanks for the poke. Thought I had gotten them all earlier today. |
@kjbracey-arm Can you please review ? |
/morph build |
Build : FAILUREBuild number : 2868 |
Build issue is known. Will relaunch once corrected. |
/morph build |
Weird. |
Pipeline locked error, restarting /morph export-build |
Exporter Build : FAILUREBuild number : 2500 |
Pausing Test CI until 5.9.6 PR is merged. |
/morph test |
/morph export-build |
Exporter Build : SUCCESSBuild number : 2511 |
This needs rebase ! I am aborting the test run, will restart |
User can now define a custom frequency sub-band for the US915 PHY. FSB_Usage.txt defines how this parameter will be configured.
Just like US915 PHY, user can define a custom FSB mask for AU915 PHY. This helps deployments where base stations do not portray full feature channel sets and choose to stick with sub-bands.
This phy implementation was just to support a single sub-band in US region. As we have decided to make FSBs configurable, we do not need this class anymore.
A few protected member functions are introduced in LoRaPHY class that help manipulate channel masks in various ways.
f4aec91
to
9b2507d
Compare
@0xc0170 Rebased and locally tested once more. |
/morph build |
Build : SUCCESSBuild number : 2897 Triggering tests/morph test |
Exporter Build : FAILUREBuild number : 2522 |
Pipes be closin to soon... /morph export-build |
Exporter Build : SUCCESSBuild number : 2527 |
Test : SUCCESSBuild number : 2648 |
@0xc0170 This can be merged |
Description
We have introduced an Mbed config based method to configure a custom frequency sub-band in US915 and AU915 PHYs. US915Hybrid PHY is removed as it was an attempt to make a similar effort. It only allowed one sub-band as it was hard coded. Now user can choose any set of sub-band or sub-bands.
Pull request type