AU915 LoraWAN channels not to spec #1307
-
G'day all, I'm using an SX1276 with my Chirpstack gateway running a RAK5146 concentrator. On startup with the AU915 region selected the node often selects the wrong frequency bands for up/down links. I have set AU915 in my config.h:
Below is a comparison of a log between two startups, no code changes or flashes, just the difference after pressing the reset button. You can see the successful activation on the left using the correct channels for AU915, but incorrect channels for AU915 on the right (https://www.thethingsnetwork.org/docs/lorawan/frequency-plans/#au915-928) Does the AU915 band need modifying? Or is there a switch somewhere I'm missing to restrict it to the LoRaWAN spec? Regards, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
The comment in
AU915 consists of multiple subbands, just like US915. If you leave it on 0, RadioLib follows the spec by selecting a random channel from each subband to see if it can join on any of the subbands. But you are definitely better off selecting the configured subband from your gateway & device console (which is subband 2, judging from the JoinAccept). |
Beta Was this translation helpful? Give feedback.
-
Legend! For some reason I wasn't thinking of the different subbands as, well.... subbands. Here I was editing the Tx and Rx frequencies haha. Thanks Steven! |
Beta Was this translation helpful? Give feedback.
-
Also, turns out I just needed to RTFM! (I did read this really early on, but never made the link back) https://github.com/jgromes/RadioLib/blob/master/examples/LoRaWAN/LoRaWAN_Starter/notes.md#region |
Beta Was this translation helpful? Give feedback.
The comment in
config.h
should be slightly modified (although one could argue that you might've been able to fill it in yourself 😉):AU915 consists of multiple subbands, just like US915. If you leave it on 0, RadioLib follows the spec by selecting a random channel from each subband to see if it can join on any of the subbands. But you are definitely better off selecting the configured subband from your gateway & device console (which is subband 2, judging from the JoinAccept).