Changes for page End Device Frequency Band
Last modified by Edwin Chen on 2024/10/21 20:35
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %) 2 - 2 + **Contents:** 3 3 4 4 {{toc/}} 5 5 ... ... @@ -10,6 +10,8 @@ 10 10 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]] 11 11 * 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]] 12 12 13 + 14 + 13 13 = 2. OTAA Join Behaviour = 14 14 15 15 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. ... ... @@ -21,6 +21,8 @@ 21 21 * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop 22 22 * 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 23 23 26 + 27 + 24 24 = 3. Default Frequency Bands = 25 25 26 26 ... ... @@ -65,6 +65,8 @@ 65 65 ** Uplink channels 1-8 (RX1) 66 66 ** 923.2 - SF10BW125 (RX2) 67 67 72 + 73 + 68 68 === 3.1.3 AS923-2 === 69 69 70 70 * Default Uplink channel: ... ... @@ -126,14 +126,26 @@ 126 126 ** 927.5 - SF7BW500 to SF12BW500 127 127 ** 923.3 - SF12BW500(RX2 downlink only) 128 128 135 +((( 129 129 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. 137 +))) 130 130 139 + 140 +((( 131 131 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. 142 +))) 132 132 144 + 145 +((( 133 133 After Join success, the end node will switch to the correct sub band by: 147 +))) 134 134 135 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 136 -* 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) 149 +* ((( 150 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 151 +))) 152 +* ((( 153 +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) 154 +))) 137 137 138 138 == 3.3 CN470-510 (CN470) == 139 139 ... ... @@ -226,6 +226,8 @@ 226 226 227 227 == 3.8 MA869 == 228 228 247 + Country: Morroco 248 + 229 229 * Uplink: 230 230 ** 869.1 - SF7BW125 to SF12BW125 231 231 ** 869.3 - SF7BW125 to SF12BW125