Summary

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

Details

Page properties

Content

...	...	@@ -4,9 +4,8 @@
4	4
5	5
6	6
7		-= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
	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
...	...	@@ -44,17 +44,17 @@
44	44
45	45
46	46
47		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
	46	+(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
48	48
49		-* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	48	+* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
50	50
51		-* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
	50	+* Does the server send back a Join Accept for the Join Request? If not, check that the key from the device matches the key you put into the server, or try to choose a different server route for that end device.
52	52
53	53	* If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
54	54
55	55	[[image:image-20220526163633-3.png]]
56	56
57		-The Traffic for the End node in the server, use TTN as example
	56	+The Traffic for the End node in the server, use TTN as example.
58	58
59	59
60	60
...	...	@@ -62,14 +62,14 @@
62	62
63	63	* If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
64	64
65		-[[image:image-20220526163704-4.png]]
	64	+[[image:image-20240123150720-1.png||height="459" width="1182"]]
66	66
67	67	The data for the end device set in server
68	68
69	69
70		-[[image:image-20220526163732-5.png]]
	69	+[[image:image-20240123150943-2.png||height="556" width="1179"]]
71	71
72		-Check if OTAA Keys match the keys in device
	71	+Check if OTAA Keys match the keys in device.
73	73
74	74
75	75	= 2. Notice of US915/CN470/AU915 Frequency band =
...	...	@@ -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]]
...	...	@@ -131,7 +131,7 @@
131	131	If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
132	132	)))
133	133
134		-[[image:image-20220526164052-9.png]]
	133	+[[image:image-20240123151225-3.png||height="434" width="902"]]
135	135
136	136	(((
137	137	TTN FREQUENCY PLAN
...	...	@@ -145,7 +145,7 @@
145	145
146	146	(% style="display:none" %) (%%)
147	147
148		-= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
	147	+= 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
149	149
150	150
151	151	In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
...	...	@@ -179,9 +179,11 @@
179	179
180	180	(((
181	181	To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
	181	+
	182	+[[image:image-20240123161737-4.png||height="395" width="763"]]
182	182	)))
183	183
184		-[[image:image-20220526164508-10.png]]
	185	+[[image:image-20240123161853-6.png||height="599" width="771"]]
185	185
186	186	Disable Frame Counter Check in ABP Mode
187	187
...	...	@@ -194,7 +194,7 @@
194	194	LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
195	195
196	196	(((
197		-Depends on Class A or Class C, the receive windows will be a little difference,
	198	+Depends on Class A or Class C, the receive windows will be a little difference.
198	198	)))
199	199
200	200	[[image:image-20220531161828-1.png]]
...	...	@@ -214,6 +214,8 @@
214	214
215	215	* 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.**
216	216
	218	+== ==
	219	+
217	217	== 5.2 See Debug Info ==
218	218
219	219
...	...	@@ -226,10 +226,10 @@
226	226	)))
227	227
228	228	(((
229		-Configure a downstream to the end device
	232	+Configure a downlink to the end device
230	230	)))
231	231
232		-[[image:image-20220526164623-12.png]]
	235	+[[image:image-20240123163307-7.png||height="330" width="1125"]]
233	233
234	234	(((
235	235	Set a downstream in TTN and see it is sent
...	...	@@ -404,7 +404,7 @@
404	404	)))
405	405
406	406
407		-= 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 =
408	408
409	409
410	410	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.
...	...	@@ -553,24 +553,24 @@
553	553	= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
554	554
555	555
556		-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.
557	557
558	558
559		-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:
560	560
561		-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:
562	562
563	563	* (((
564		-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.
565	565	)))
566	566	* (((
567		-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).
568	568	)))
569	569
570		-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.
571	571
572	572
573		-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.
574	574
575	575
576	576	[[image:image-20221215223215-1.png||height="584" width="1280"]]