Summary

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

Details

Page properties

Content

...	...	@@ -1,8 +1,11 @@
1	1	(% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %)
2		-
	2	+ **Contents：**
3	3
4	4	{{toc/}}
5	5
	6	+
	7	+
	8	+
6	6	= 1. Introduction =
7	7
8	8	This page list the default frequency band for Dragino End Devices. The frequency bands are base on TTN Frequency Bands. User can modify upgrade firmware to support different frequency band or use AT Command to change the sub band in some frequency bands.
...	...	@@ -10,6 +10,7 @@
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
	16	+
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,7 @@
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
	28	+
24	24	= 3. Default Frequency Bands =
25	25
26	26
...	...	@@ -37,7 +37,6 @@
37	37	)))
38	38
39	39
40		-
41	41	=== 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
42	42
43	43	* Default Uplink channel:
...	...	@@ -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:
...	...	@@ -77,6 +77,8 @@
77	77	** Uplink channels 1-8 (RX1)
78	78	** 921.4 - SF10BW125 (RX2)
79	79
	86	+
	87	+
80	80	=== 3.1.4 AS923-3 ===
81	81
82	82	* Default Uplink channel:
...	...	@@ -89,6 +89,8 @@
89	89	** Uplink channels 1-8 (RX1)
90	90	** 916.6 - SF10BW125 (RX2)
91	91
	100	+
	101	+
92	92	=== 3.1.5 AS923-4 ===
93	93
94	94	* Countries : Israel
...	...	@@ -101,6 +101,8 @@
101	101	** Uplink channels 1-8 (RX1)
102	102	** 917.3 - SF10BW125 (RX2)
103	103
	114	+
	115	+
104	104	== 3.2 AU915-928(AU915) ==
105	105
106	106	**Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]** , Default use CHE=2
...	...	@@ -126,15 +126,29 @@
126	126	** 927.5 - SF7BW500 to SF12BW500
127	127	** 923.3 - SF12BW500(RX2 downlink only)
128	128
	141	+(((
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.
	143	+)))
130	130
	145	+
	146	+(((
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.
	148	+)))
132	132
	150	+
	151	+(((
133	133	After Join success, the end node will switch to the correct sub band by:
	153	+)))
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)
	155	+* (((
	156	+Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	157	+)))
	158	+* (((
	159	+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)
137	137
	161	+
	162	+)))
	163	+
138	138	== 3.3 CN470-510 (CN470) ==
139	139
140	140	Used in China, Default use CHE=1
...	...	@@ -160,6 +160,8 @@
160	160	** 508.1 - SF7BW125 to SF12BW125
161	161	** 505.3 - SF12BW125 (RX2 downlink only)
162	162
	189	+
	190	+
163	163	== 3.4 EU863-870 (EU868) ==
164	164
165	165	* Uplink:
...	...	@@ -191,6 +191,8 @@
191	191	** Uplink channels 1-3 (RX1)
192	192	** 866.550 - SF10BW125 (RX2)
193	193
	222	+
	223	+
194	194	== 3.6 KZ865 ==
195	195
196	196	* Uplink ~-~- 125Khz , DR0 - DR5
...	...	@@ -204,6 +204,8 @@
204	204	** The RX1 receive window uses the same channel as the preceding uplink.
205	205	** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz)​
206	206
	237	+
	238	+
207	207	== 3.7 KR920-923 (KR920) ==
208	208
209	209	* Default channel:
...	...	@@ -224,8 +224,12 @@
224	224	** Uplink channels 1-7(RX1)
225	225	** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
226	226
	259	+
	260	+
227	227	== 3.8 MA869 ==
228	228
	263	+ Country: Morroco
	264	+
229	229	* Uplink:
230	230	** 869.1 - SF7BW125 to SF12BW125
231	231	** 869.3 - SF7BW125 to SF12BW125
...	...	@@ -241,10 +241,13 @@
241	241	** Uplink channels 1-9 (RX1)
242	242	** 869.525 - SF12BW125 (RX2 downlink only)
243	243
	280	+
	281	+
244	244	== 3.9 US902-928 (US915) ==
245	245
246	246	Used in USA, Canada and South America.
247	247
	286	+
248	248	=== 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. ===
249	249
250	250	Default use CHE=2, Subband 2
...	...	@@ -272,13 +272,27 @@
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
	314	+(((
275	275	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.
	316	+)))
276	276
	318	+(((
	319	+
	320	+)))
	321	+
	322	+(((
277	277	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:
	324	+)))
278	278
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)
	326	+* (((
	327	+Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
	328	+)))
	329	+* (((
	330	+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)
281	281
	332	+
	333	+)))
	334	+
282	282	= 4. Frequency Bands for different server =
283	283
284	284	* TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]