Summary

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

Details

Page properties

Content

...	...	@@ -18,10 +18,10 @@
18	18	= 2. OTAA Join Behaviour =
19	19
20	20
21		-Since 005 LoRaWAN stack: to save battery, once boot, device will 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	+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.
22	22
23	23	(((
24		-Since 005 LoRaWAN Stack:
	24	+For 005 LoRaWAN Stack:
25	25	)))
26	26
27	27	* EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
...	...	@@ -337,6 +337,10 @@
337	337	)))
338	338
339	339	(((
	340	+
	341	+)))
	342	+
	343	+(((
340	340	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:
341	341	)))
342	342
...	...	@@ -359,23 +359,16 @@
359	359
360	360	= 5. Subband Related questiones in US915, AU915, CN470 bands. =
361	361
362		-
363	363	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?
364	364
365		-
366	366	== 5.1 Set Subband in Gateway. ==
367	367
	370	+* If Gateway choose **Semtech UDP packet** forwarder to Connect to LoRaWAN server. User need to manually set the match Subband in the gateway web UI.
	371	+* If Gateway choose **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.
368	368
369		-* 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.
370		-
371		-* 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.
372		-
373		-
374	374	== 5.2 Set Subband in End Node ==
375	375
376		-
377	377	* 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.
378		-
379	379	* 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.
380	380
381	381	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]]?