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
...	...	@@ -126,26 +126,14 @@
126	126	** 927.5 - SF7BW500 to SF12BW500
127	127	** 923.3 - SF12BW500(RX2 downlink only)
128	128
129		-(((
130	130	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.
131		-)))
132	132
133		-
134		-(((
135	135	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.
136		-)))
137	137
138		-
139		-(((
140	140	After Join success, the end node will switch to the correct sub band by:
141		-)))
142	142
143		-* (((
144		-Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
145		-)))
146		-* (((
147		-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)
148		-)))
	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)
149	149
150	150	== 3.3 CN470-510 (CN470) ==
151	151