Summary

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

Details

Page properties

Content

...	...	@@ -1,6 +1,14 @@
1	1	(% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %)
2	2
3	3
	4	+= Contents ~[[[hide>>http://8.211.40.43:8080/xwiki/bin/view/Main/End%20Device%20Frequency%20Band]]] =
	5	+
	6	+== Contents ==
	7	+
	8	+ ~[[[hide>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#]]]
	9	+
	10	+* [[1 Introduction>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#Introduction]]
	11	+
4	4	{{toc/}}
5	5
6	6	= 1. Introduction =
...	...	@@ -14,9 +14,7 @@
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.
16	16
17		-(((
18	18	For 005 LoRaWAN Stack:
19		-)))
20	20
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
...	...	@@ -28,13 +28,9 @@
28	28
29	29	=== 3.1.1 Notice for AS923 Frequency Bands ===
30	30
31		-(((
32	32	Since [[RP002-1.0.1LoRaWAN Regional Parameters>>url:https://lora-alliance.org/sites/default/files/2020-02/rp_2-1.0.1.pdf]], AS923 include three different default settings for different countries: AS923-1, AS923-2 and AS923-3.
33		-)))
34	34
35		-(((
36	36	AS923-1 use the same default uplink frequency as previous AS923 firmware. AS923-2 and AS923-3 are new with different default uplink frequency. User need to know exactly the frequency bands from the LoRaWAN server and choose the right firmware version for the end node.
37		-)))
38	38
39	39
40	40
...	...	@@ -272,24 +272,12 @@
272	272
273	273	=== 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
274	274
275		-(((
276	276	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.
277		-)))
278	278
279		-(((
280		-
281		-)))
282		-
283		-(((
284	284	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:
285		-)))
286	286
287		-* (((
288		-Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
289		-)))
290		-* (((
291		-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)
292		-)))
	281	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
	282	+* 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)
293	293
294	294	= 4. Frequency Bands for different server =
295	295