Changes for page End Device Frequency Band

Last modified by Edwin Chen on 2024/10/21 20:35

From version < 11.4 >

edited by Xiaoling
on 2022/05/31 08:57

To version < 3.1 >

edited by Xiaoling
on 2022/05/10 14:17

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -1,11 +1,13 @@
  (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %)
--     **Contents：**
++
--{{toc/}}
++(% class="wikigeneratedid" id="HContents" %)
++Contents
++ ~[[[hide>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#]]]
++{{toc/}}
--
  = 1. Introduction =
  This page list the default frequency band for Dragino End Devices. The frequency bands are base on TTN Frequency Bands. User can modify upgrade firmware to support different frequency band or use AT Command to change the sub band in some frequency bands.
@@ -13,19 +13,15 @@
  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
  * Frequency Bands vs Country List : Page 11 of [[LoRaWAN Regional Parameters RP2-1.0.3>>url:https://resources.lora-alliance.org/technical-specifications/rp2-1-0-3-lorawan-regional-parameters]]
--
  = 2. OTAA Join Behaviour =
  For 005 LoRaWAN stack: to save battery, once boot, device will make first make 200 tries for OTAA Join, the time period of two Join Requests will depends on the DR and the airtime requirement. After this 200 Join finish, device will send a join request every 20 minutes. If device reboot, it will do above loop again.
--(((
  For 005 LoRaWAN Stack:
--)))
  * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
  * US915 and AU915 OTAA Join procedure,. End node by default will use all 72 channels to join and it will be set to use the proper sub-band after Join success
--
  = 3. Default Frequency Bands =
@@ -33,15 +33,12 @@
  === 3.1.1 Notice for AS923 Frequency Bands ===
--(((
  Since [[RP002-1.0.1LoRaWAN Regional Parameters>>url:https://lora-alliance.org/sites/default/files/2020-02/rp_2-1.0.1.pdf]], AS923 include three different default settings for different countries: AS923-1, AS923-2 and AS923-3.
--)))
--(((
  AS923-1 use the same default uplink frequency as previous AS923 firmware. AS923-2 and AS923-3 are new with different default uplink frequency. User need to know exactly the frequency bands from the LoRaWAN server and choose the right firmware version for the end node.
--)))
++
  === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
  * Default Uplink channel:
@@ -69,7 +69,6 @@
  ** Uplink channels 1-8 (RX1)
  ** 923.2 - SF10BW125 (RX2)
--
  === 3.1.3 AS923-2 ===
  * Default Uplink channel:
@@ -82,7 +82,6 @@
  ** Uplink channels 1-8 (RX1)
  ** 921.4 - SF10BW125 (RX2)
--
  === 3.1.4 AS923-3 ===
  * Default Uplink channel:
@@ -132,29 +132,15 @@
  ** 927.5 - SF7BW500 to SF12BW500
  ** 923.3 - SF12BW500(RX2 downlink only)
--(((
  There is a issue if the end node is fixed at sub-band2. The sensor won't be able to register to other sub-band and can only works for the LoRaWAN server use sub-band2 , such as TTN. To solve this, user need to use a USB-TTL adapter to connect to the end node to manually set the sub-band which is very inconvinient.
--)))
--
--(((
  So since **Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]**, To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
--)))
--
--(((
  After Join success, the end node will switch to the correct sub band by:
--)))
--* (((
--Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
--)))
--* (((
--Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
++* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
++* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
--
--)))
--
  == 3.3 CN470-510 (CN470) ==
  Used in China, Default use CHE=1
@@ -180,7 +180,6 @@
  ** 508.1 - SF7BW125 to SF12BW125
  ** 505.3 - SF12BW125 (RX2 downlink only)
--
  == 3.4 EU863-870 (EU868) ==
  * Uplink:
@@ -212,7 +212,6 @@
  ** Uplink channels 1-3 (RX1)
  ** 866.550 - SF10BW125 (RX2)
--
  == 3.6 KZ865 ==
  * Uplink ~-~- 125Khz , DR0 - DR5
@@ -226,7 +226,6 @@
  ** The RX1 receive window uses the same channel as the preceding uplink.
  ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz)
--
  == 3.7 KR920-923 (KR920) ==
  * Default channel:
@@ -247,11 +247,8 @@
  ** Uplink channels 1-7(RX1)
  ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
--
  == 3.8 MA869 ==
--       Country: Morroco
--
  * Uplink:
  ** 869.1 - SF7BW125 to SF12BW125
  ** 869.3 - SF7BW125 to SF12BW125
@@ -267,12 +267,10 @@
  ** Uplink channels 1-9 (RX1)
  ** 869.525 - SF12BW125 (RX2 downlink only)
--
  == 3.9 US902-928 (US915) ==
  Used in USA, Canada and South America.
--
  === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. ===
  Default use CHE=2, Subband 2
@@ -298,30 +298,15 @@
  ** 927.5 - SF7BW500 to SF12BW500
  ** 923.3 - SF12BW500(RX2 downlink only)
--
  === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
--(((
  There is an issue if the end node is fixed at sub-band2. The sensor won't be able to register to other sub-band and can only work for the LoRaWAN server use sub-band2 , such as TTN. To solve this, the user needs to use a USB-TTL adapter to connect to the end node to manually set the sub-band which is very inconvenient.
--)))
--(((
--
--)))
--
--(((
  So since **Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]**, we have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
--)))
--* (((
--Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
--)))
--* (((
--Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
++* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
++* Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
--
--)))
--
  = 4. Frequency Bands for different server =
  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]

Changes for page End Device Frequency Band

Summary

Details

Applications

Navigation