Summary

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

Details

Page properties

Content

...	...	@@ -4,9 +4,8 @@
4	4
5	5
6	6
7		-= z =
	7	+= 1.Join process page check =
8	8
9		-
10	10	These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
11	11	\\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
12	12
...	...	@@ -76,17 +76,17 @@
76	76
77	77
78	78	(((
79		-If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
	78	+If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
80	80	)))
81	81
82	82	* (((
83		-What **sub-band** the server support ?
	82	+What **sub-band** the server support?
84	84	)))
85	85	* (((
86		-What is the **sub-band** the gateway support ?
	85	+What is the **sub-band** the gateway support?
87	87	)))
88	88	* (((
89		-What is the **sub-band** the end node is using ?
	88	+What is the **sub-band** the end node is using?
90	90	)))
91	91
92	92	(((
...	...	@@ -98,7 +98,7 @@
98	98	)))
99	99
100	100	(((
101		-In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn,t support.
	100	+In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn't support.
102	102	)))
103	103
104	104	(((
...	...	@@ -106,7 +106,7 @@
106	106	)))
107	107
108	108	(((
109		-Here are the freuqency tables for these bands as reference:
	108	+Here are the frequency tables for these bands as reference:
110	110	)))
111	111
112	112	[[image:image-20220526163801-6.png]]
...	...	@@ -216,7 +216,6 @@
216	216
217	217	* 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.**
218	218
219		-(% class="wikigeneratedid" %)
220	220	== ==
221	221
222	222	== 5.2 See Debug Info ==
...	...	@@ -409,7 +409,7 @@
409	409	)))
410	410
411	411
412		-= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
	410	+= 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
413	413
414	414
415	415	Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
...	...	@@ -558,24 +558,24 @@
558	558	= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
559	559
560	560
561		-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.
	559	+In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
562	562
563	563
564		-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:
	562	+In Dragino Sensors old version firmware (before early 2022), the sub-band is fixed the sub-band 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:
565	565
566		-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:
	564	+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 sub-bands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
567	567
568	568	* (((
569		-Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
	567	+Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
570	570	)))
571	571	* (((
572		-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)
	570	+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).
573	573	)))
574	574
575		-This change will make the activation time a littler longer but make sure the device can be used in any subband.
	573	+This change will make the activation time a little longer but make sure the device can be used in any sub-band.
576	576
577	577
578		-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.
	576	+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 sub-band he uses.
579	579
580	580
581	581	[[image:image-20221215223215-1.png||height="584" width="1280"]]