Summary

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

Details

Page properties

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %)
2		- **Contents：**
	2	+
3	3
4	4	{{toc/}}
5	5
...	...	@@ -10,8 +10,6 @@
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		-
15	15	= 2. OTAA Join Behaviour =
16	16
17	17	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.
...	...	@@ -23,8 +23,6 @@
23	23	* EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
24	24	* 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
25	25
26		-
27		-
28	28	= 3. Default Frequency Bands =
29	29
30	30
...	...	@@ -69,8 +69,6 @@
69	69	** Uplink channels 1-8 (RX1)
70	70	** 923.2 - SF10BW125 (RX2)
71	71
72		-
73		-
74	74	=== 3.1.3 AS923-2 ===
75	75
76	76	* Default Uplink channel:
...	...	@@ -132,26 +132,14 @@
132	132	** 927.5 - SF7BW500 to SF12BW500
133	133	** 923.3 - SF12BW500(RX2 downlink only)
134	134
135		-(((
136	136	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		-)))
138	138
139		-
140		-(((
141	141	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		-)))
143	143
144		-
145		-(((
146	146	After Join success, the end node will switch to the correct sub band by:
147		-)))
148	148
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		-)))
	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)
155	155
156	156	== 3.3 CN470-510 (CN470) ==
157	157
...	...	@@ -244,8 +244,6 @@
244	244
245	245	== 3.8 MA869 ==
246	246
247		- Country: Morroco
248		-
249	249	* Uplink:
250	250	** 869.1 - SF7BW125 to SF12BW125
251	251	** 869.3 - SF7BW125 to SF12BW125
...	...	@@ -292,24 +292,12 @@
292	292
293	293	=== 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
294	294
295		-(((
296	296	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.
297		-)))
298	298
299		-(((
300		-
301		-)))
302		-
303		-(((
304	304	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:
305		-)))
306	306
307		-* (((
308		-Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
309		-)))
310		-* (((
311		-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)
312		-)))
	279	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
	280	+* 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)
313	313
314	314	= 4. Frequency Bands for different server =
315	315