Changes for page End Device Frequency Band

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

From version < 12.3 >

edited by Xiaoling
on 2022/07/13 11:29

To version < 18.1

edited by Edwin Chen
on 2024/10/21 20:35

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.Edwin

Content

@@ -14,30 +14,23 @@
  * 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 =
++Since 005 LoRaWAN stack: One device boot or reset, it will
--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.
++* First make 200 Join Requestes for OTAA Join, the interval of two Join Requests will depends on the DR and the airtime requirement.
++* After 200 Join Requestes, if end node still not join successful, to save battery life, it will keep sending join request at the default uplink interval ( 20 minutes) .
++* If device reboot, it will do above loop again.
--(((
--For 005 LoRaWAN Stack:
--)))
++Since 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
++* **EU868 OTAA Join DR Logic**. SF7->SF8->SF9->SF10->SF11->SF12; Each SF will make 3 attempts and then loop
++* **US915 and AU915 OTAA Join procedure**,. End node by default will use all 72 channels (All sub-bands) to join and it will be set to use the proper sub-band after Join success
--
--
--
  = 3. Default Frequency Bands =
--
  == 3.1 AS923 ==
--
  === 3.1.1 Notice for AS923 Frequency Bands ===
@@ -50,7 +50,6 @@
  )))
--
  === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
@@ -80,9 +80,6 @@
  ** Uplink channels 1-8 (RX1)
  ** 923.2 - SF10BW125 (RX2)
--
--
--
  === 3.1.3 AS923-2 ===
@@ -96,9 +96,6 @@
  ** Uplink channels 1-8 (RX1)
  ** 921.4 - SF10BW125 (RX2)
--
--
--
  === 3.1.4 AS923-3 ===
@@ -112,9 +112,6 @@
  ** Uplink channels 1-8 (RX1)
  ** 916.6 - SF10BW125 (RX2)
--
--
--
  === 3.1.5 AS923-4 ===
@@ -128,9 +128,6 @@
  ** Uplink channels 1-8 (RX1)
  ** 917.3 - SF10BW125 (RX2)
--
--
--
  == 3.2 AU915-928(AU915) ==
@@ -157,7 +157,6 @@
  ** 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.
  )))
@@ -176,10 +176,9 @@
  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)
++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)
--
  )))
@@ -209,9 +209,6 @@
  ** 508.1 - SF7BW125 to SF12BW125
  ** 505.3 - SF12BW125 (RX2 downlink only)
--
--
--
  == 3.4 EU863-870 (EU868) ==
@@ -233,7 +233,6 @@
  OTAA RX2DR is set to DR0, SF12BW125 since 2021,Mar for Dragino Devices.
--
  == 3.5 IN865-867 (IN865) ==
@@ -246,9 +246,17 @@
  ** Uplink channels 1-3 (RX1)
  ** 866.550 - SF10BW125 (RX2)
++Gateway has below eight channels in IN865 bands.
++* 865.0625 - SF7BW125 to SF12BW125
++* 865.4025 - SF7BW125 to SF12BW125
++* 865.6025 - SF7BW125 to SF12BW125
++* 865.9850 - SF7BW125 to SF12BW125
++* 866.1850 - SF7BW125 to SF12BW125
++* 866.3850 - SF7BW125 to SF12BW125
++* 866.5850 - SF7BW125 to SF12BW125
++* 866.7850 - SF7BW125 to SF12BW125
--
  == 3.6 KZ865 ==
@@ -263,9 +263,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) ==
@@ -287,9 +287,6 @@
  ** Uplink channels 1-7(RX1)
  ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
--
--
--
  == 3.8 MA869 ==
@@ -310,9 +310,6 @@
  ** Uplink channels 1-9 (RX1)
  ** 869.525 - SF12BW125 (RX2 downlink only)
--
--
--
  == 3.9 US902-928 (US915) ==
@@ -319,7 +319,6 @@
  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]]. ===
@@ -346,23 +346,17 @@
  ** 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, 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:
  )))
--(((
--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
  )))
@@ -370,11 +370,47 @@
  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]]
  * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
++
++
++= 5. Subband Related questiones in US915, AU915, CN470 bands. =
++
++
++Frequency band US915, AU915 and CN470 supports totally 72 frequency in 8 sub-bands, Normally Gateway only support 8 channels ( one subband). So how does the gateway and end nodes work in such frequency?
++
++
++== 5.1 Set Subband in Gateway. ==
++
++
++* If Gateway choose (% style="color:blue" %)**Semtech UDP packet**(%%) forwarder to Connect to LoRaWAN server. User need to manually set the match Subband in the gateway web UI.
++
++* If Gateway choose (% style="color:blue" %)**Basic Station Mode**(%%) to connect to the LoRaWAN server. User can set the subband in the Server side and gateway will the correct subband from server. no need to set this in gateway. AWS-IoT, TTN, ChirpStack all supports Basic Station Connection.
++
++== 5.2 Set Subband in End Node ==
++
++
++* In early End Node firmware, it is pre-set to subband 2 , user need to manually set to proper subband if they don;t use subband 2.
++
++* In new end node firmware , it supports all sub-bands, and will swtich to the proper subband after OTAA join. So user can use the end node with all sub-band.
++
++Reference: [[How it affects the OTAA Join when end node is set to support all subbands>>http://wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H13.WhyittakeslongertimeforOTAAjoinedinUS9152FCN4702FAU915band3F]]?
++
++
++= 6. Data Rate and TXP auto-adjust logic. =
++
++In below cases the sensor end node will auto-adjust. (ADR must set to 1)
++
++* Auto-just according to the server ADR request change downlink command.
++* If there is no adr_req_ack arrive the sensor end node for more than 64 uplinks, end node will set the output to maximum power (AT+TXP=0).
++* If there is no adr_req_ack arrive the sensor end node for more than 96 uplinks, end node will reduce the Data Rate by 1.
++
++
++
++

Changes for page End Device Frequency Band

Summary

Details

Applications

Navigation