Summary

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

Details

Page properties

Content

...	...	@@ -17,6 +17,7 @@
17	17	* End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
18	18
19	19
	20	+
20	20	(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
21	21
22	22	* If the device is sending join request to server?
...	...	@@ -216,6 +216,7 @@
216	216	* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
217	217
218	218
	220	+
219	219	== 5.2 See Debug Info ==
220	220
221	221
...	...	@@ -330,6 +330,7 @@
330	330	* End Node traffic (from server UI) to shows end node activity in server.
331	331
332	332
	335	+
333	333	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
334	334
335	335
...	...	@@ -532,30 +532,6 @@
532	532	Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
533	533
534	534
535		-= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
536	536
537		-
538		-In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
539		-
540		-
541		-In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
542		-
543		-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:
544		-
545		-* (((
546		-Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
547		-)))
548		-* (((
549		-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)
550		-)))
551		-
552		-This change will make the activation time a littler longer but make sure the device can be used in any subband.
553		-
554		-
555		-Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
556		-
557		-
558		-[[image:image-20221215223215-1.png||height="584" width="1280"]]
559		-
560	560	(% class="wikigeneratedid" %)
561	561