Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -14,23 +14,30 @@
14	14	* TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
15	15	* 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]]
16	16
	17	+
	18	+
	19	+
17	17	= 2. OTAA Join Behaviour =
18	18
19		-Since 005 LoRaWAN stack: One device boot or reset, it will
20	20
21		-* First make 200 Join Requestes for OTAA Join, the interval of two Join Requests will depends on the DR and the airtime requirement.
22		-* 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) .
23		-* If device reboot, it will do above loop again.
	23	+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.
24	24
25		-Since 005 LoRaWAN Stack:
	25	+(((
	26	+For 005 LoRaWAN Stack:
	27	+)))
26	26
27		-* **EU868 OTAA Join DR Logic**. SF7->SF8->SF9->SF10->SF11->SF12; Each SF will make 3 attempts and then loop
28		-* **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
	29	+* EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
	30	+* 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
29	29
	32	+
	33	+
	34	+
30	30	= 3. Default Frequency Bands =
31	31
	37	+
32	32	== 3.1 AS923 ==
33	33
	40	+
34	34	=== 3.1.1 Notice for AS923 Frequency Bands ===
35	35
36	36
...	...	@@ -43,6 +43,7 @@
43	43	)))
44	44
45	45
	53	+
46	46	=== 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
47	47
48	48
...	...	@@ -72,6 +72,9 @@
72	72	** Uplink channels 1-8 (RX1)
73	73	** 923.2 - SF10BW125 (RX2)
74	74
	83	+
	84	+
	85	+
75	75	=== 3.1.3 AS923-2 ===
76	76
77	77
...	...	@@ -85,6 +85,9 @@
85	85	** Uplink channels 1-8 (RX1)
86	86	** 921.4 - SF10BW125 (RX2)
87	87
	99	+
	100	+
	101	+
88	88	=== 3.1.4 AS923-3 ===
89	89
90	90
...	...	@@ -98,6 +98,9 @@
98	98	** Uplink channels 1-8 (RX1)
99	99	** 916.6 - SF10BW125 (RX2)
100	100
	115	+
	116	+
	117	+
101	101	=== 3.1.5 AS923-4 ===
102	102
103	103
...	...	@@ -111,6 +111,9 @@
111	111	** Uplink channels 1-8 (RX1)
112	112	** 917.3 - SF10BW125 (RX2)
113	113
	131	+
	132	+
	133	+
114	114	== 3.2 AU915-928(AU915) ==
115	115
116	116
...	...	@@ -137,6 +137,7 @@
137	137	** 927.5 - SF7BW500 to SF12BW500
138	138	** 923.3 - SF12BW500(RX2 downlink only)
139	139
	160	+
140	140	(((
141	141	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.
142	142	)))
...	...	@@ -155,9 +155,10 @@
155	155	Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
156	156	)))
157	157	* (((
158		-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)
	179	+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)
159	159
160	160
	182	+
161	161
162	162	)))
163	163
...	...	@@ -187,6 +187,9 @@
187	187	** 508.1 - SF7BW125 to SF12BW125
188	188	** 505.3 - SF12BW125 (RX2 downlink only)
189	189
	212	+
	213	+
	214	+
190	190	== 3.4 EU863-870 (EU868) ==
191	191
192	192
...	...	@@ -208,6 +208,7 @@
208	208	OTAA RX2DR is set to DR0, SF12BW125 since 2021,Mar for Dragino Devices.
209	209
210	210
	236	+
211	211	== 3.5 IN865-867 (IN865) ==
212	212
213	213
...	...	@@ -220,17 +220,9 @@
220	220	** Uplink channels 1-3 (RX1)
221	221	** 866.550 - SF10BW125 (RX2)
222	222
223		-Gateway has below eight channels in IN865 bands.
224	224
225		-* 865.0625 - SF7BW125 to SF12BW125
226		-* 865.4025 - SF7BW125 to SF12BW125
227		-* 865.6025 - SF7BW125 to SF12BW125
228		-* 865.9850 - SF7BW125 to SF12BW125
229		-* 866.1850 - SF7BW125 to SF12BW125
230		-* 866.3850 - SF7BW125 to SF12BW125
231		-* 866.5850 - SF7BW125 to SF12BW125
232		-* 866.7850 - SF7BW125 to SF12BW125
233	233
	251	+
234	234	== 3.6 KZ865 ==
235	235
236	236
...	...	@@ -245,6 +245,9 @@
245	245	** The RX1 receive window uses the same channel as the preceding uplink.
246	246	** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz)​
247	247
	266	+
	267	+
	268	+
248	248	== 3.7 KR920-923 (KR920) ==
249	249
250	250
...	...	@@ -266,6 +266,9 @@
266	266	** Uplink channels 1-7(RX1)
267	267	** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
268	268
	290	+
	291	+
	292	+
269	269	== 3.8 MA869 ==
270	270
271	271
...	...	@@ -286,6 +286,9 @@
286	286	** Uplink channels 1-9 (RX1)
287	287	** 869.525 - SF12BW125 (RX2 downlink only)
288	288
	313	+
	314	+
	315	+
289	289	== 3.9 US902-928 (US915) ==
290	290
291	291
...	...	@@ -292,6 +292,7 @@
292	292	Used in USA, Canada and South America.
293	293
294	294
	322	+
295	295	=== 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. ===
296	296
297	297
...	...	@@ -318,17 +318,23 @@
318	318	** 927.5 - SF7BW500 to SF12BW500
319	319	** 923.3 - SF12BW500(RX2 downlink only)
320	320
321		-=== 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
322	322
323	323
	351	+
	352	+=== 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
	353	+
324	324	(((
325	325	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.
326	326	)))
327	327
328	328	(((
329		-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:
	359	+
330	330	)))
331	331
	362	+(((
	363	+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:
	364	+)))
	365	+
332	332	* (((
333	333	Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
334	334	)))
...	...	@@ -336,39 +336,11 @@
336	336	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)
337	337
338	338
	373	+
339	339
340	340	)))
341	341
342	342	= 4. Frequency Bands for different server =
343	343
344		-
345	345	* TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
346	346	* Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
347		-
348		-= 5. Subband Related questiones in US915, AU915, CN470 bands. =
349		-
350		-
351		-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?
352		-
353		-
354		-== 5.1 Set Subband in Gateway. ==
355		-
356		-
357		-* 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.
358		-
359		-* 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.
360		-
361		-== 5.2 Set Subband in End Node ==
362		-
363		-
364		-* 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.
365		-
366		-* 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.
367		-
368		-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]]?
369		-
370		-
371		-
372		-
373		-
374		-