Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.Edwin

Content

...	...	@@ -6,6 +6,7 @@
6	6
7	7	= 1. OTAA Join Process Debug =
8	8
	9	+
9	9	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.
10	10	\\**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:**
11	11
...	...	@@ -15,8 +15,9 @@
15	15	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
16	16	* 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)
17	17
18		-**~1. End Device Join Screen shot, we can check:**
19	19
	20	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	21	+
20	20	* If the device is sending join request to server?
21	21	* What frequency the device is sending?
22	22
...	...	@@ -25,8 +25,9 @@
25	25	Console Output from End device to see the transmit frequency
26	26
27	27
28		-**2. Gateway packet traffic in gateway web or ssh. we can check:**
29	29
	31	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
	32	+
30	30	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
31	31	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
32	32
...	...	@@ -35,7 +35,7 @@
35	35	Console Output from Gateway to see packets between end node and server.
36	36
37	37
38		-**3. Gateway Traffic Page in LoRaWAN Server**
	41	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
39	39
40	40	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
41	41	* 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.
...	...	@@ -46,7 +46,7 @@
46	46	The Traffic for the End node in the server, use TTN as example
47	47
48	48
49		-**4. Data Page in LoRaWAN server**
	52	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
50	50
51	51	* 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.
52	52
...	...	@@ -59,8 +59,10 @@
59	59	Check if OTAA Keys match the keys in device
60	60
61	61
	65	+
62	62	= 2. Notice of US915/CN470/AU915 Frequency band =
63	63
	68	+
64	64	(((
65	65	If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
66	66	)))
...	...	@@ -103,10 +103,13 @@
103	103
104	104	AU915 Channels
105	105
	111	+
106	106	[[image:image-20220526163941-8.png]]
107	107
108	108	(((
109	109	CN470 Channels
	116	+
	117	+
110	110	)))
111	111
112	112	(((
...	...	@@ -117,6 +117,8 @@
117	117
118	118	(((
119	119	TTN FREQUENCY PLAN
	128	+
	129	+
120	120	)))
121	121
122	122	(((
...	...	@@ -124,8 +124,10 @@
124	124	)))
125	125
126	126
	137	+
127	127	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
128	128
	140	+
129	129	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:
130	130
131	131	* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
...	...	@@ -145,8 +145,10 @@
145	145	)))
146	146
147	147
	160	+
148	148	= 4. Transmision on ABP Mode =
149	149
	163	+
150	150	(((
151	151	In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
152	152	)))
...	...	@@ -172,10 +172,12 @@
172	172	Disable Frame Counter Check in ABP Mode
173	173
174	174
	189	+
175	175	= 5. Downstream Debug =
176	176
177	177	== 5.1 How it work ==
178	178
	194	+
179	179	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.
180	180
181	181	(((
...	...	@@ -186,6 +186,7 @@
186	186
187	187	receive windows for Class A and Class C
188	188
	205	+
189	189	Below are the requirement for the End Device to receive the packets.
190	190
191	191	* The End Device must open the receive windows: RX1 or RX2
...	...	@@ -192,12 +192,15 @@
192	192	* The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
193	193	* This downstream packet must arrive to the end node while RX1 or RX2 is open.
194	194	* This packet must match the frequency of the RX1 or RX2 window.
195		-* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **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.**
	212	+* 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.**
196	196
	214	+
	215	+
197	197	== 5.2 See Debug Info ==
198	198
	218	+
199	199	(((
200		-**For LoRaWAN Server**
	220	+(% style="color:blue" %)**For LoRaWAN Server**
201	201	)))
202	202
203	203	(((
...	...	@@ -226,8 +226,9 @@
226	226	)))
227	227
228	228
	249	+
229	229	(((
230		-**For LoRaWAN Gateway**
	251	+(% style="color:blue" %)**For LoRaWAN Gateway**
231	231	)))
232	232
233	233	(((
...	...	@@ -241,8 +241,9 @@
241	241	)))
242	242
243	243
	265	+
244	244	(((
245		-**For End Node**
	267	+(% style="color:blue" %)**For End Node**
246	246	)))
247	247
248	248	(((
...	...	@@ -250,23 +250,19 @@
250	250	)))
251	251
252	252	(((
	275	+(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
	276	+(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
	277	+(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
	278	+(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
	279	+
	280	+
253	253
254	254	)))
255	255
256	256	(((
257		-(% class="box infomessage" %)
258		-(((
259		-AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
260		-AT+RX2DR=3      ~-~--> The RX2 DataRate
261		-AT+RX1DL=1000   ~-~--> Receive Delay 1
262		-AT+RX2DL=2000   ~-~--> Receive Delay 2
	285	+(% style="color:blue" %)**when the device running, we can see below info:**
263	263	)))
264		-)))
265	265
266		-(((
267		-**when the device running, we can see below info:**
268		-)))
269		-
270	270	{{{ [12502]***** UpLinkCounter= 0 *****
271	271	[12503]TX on freq 868500000 Hz at DR 0
272	272	[13992]txDone
...	...	@@ -277,10 +277,12 @@
277	277
278	278	(((
279	279
	298	+
	299	+
280	280	)))
281	281
282	282	(((
283		-**Another message:**
	303	+(% style="color:blue" %)**Another message:**
284	284	)))
285	285
286	286	{{{ [12502]***** UpLinkCounter= 0 *****
...	...	@@ -295,8 +295,10 @@
295	295	1:0012345678}}}
296	296
297	297
298		-== 5.3 If problem doesn’t solve ==
299	299
	319	+== 5.3 If problem doesn't solve ==
	320	+
	321	+
300	300	(% style="color:red" %)**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:**
301	301
302	302	* End node console to show the transmit freuqency and DR.
...	...	@@ -304,8 +304,11 @@
304	304	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
305	305	* End Node traffic (from server UI) to shows end node activity in server.
306	306
	329	+
	330	+
307	307	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
308	308
	333	+
309	309	(((
310	310	In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
311	311	)))
...	...	@@ -329,22 +329,23 @@
329	329	)))
330	330
331	331
	357	+
332	332	= 7. Decrypt a LoRaWAN Packet =
333	333
334		-~1. LHT65 End device configure:
335	335
336		-(% class="box infomessage" %)
337		-(((
338		-**Change to ABP Mode: AT+NJM=0**
339		-**Change to fix frequency: AT+CHS=904900000**
340		-**Change to fix DR: AT+DR=0**
341		-)))
	361	+(% style="color:blue" %)**1. LHT65 End device configure:**
342	342
	363	+**Change to ABP Mode:  AT+NJM=0**
	364	+**Change to fix frequency:  AT+CHS=904900000**
	365	+**Change to fix DR:  AT+DR=0**
	366	+
	367	+
343	343	[[image:image-20220526165525-16.png]]
344	344
345	345
346		-2. In LG02 , configure to receive above message
347	347
	372	+(% style="color:blue" %)**2. In LG02 , configure to receive above message**
	373	+
348	348	[[image:image-20220526165612-17.png]]
349	349
350	350
...	...	@@ -353,8 +353,9 @@
353	353	[[image:image-20220526171112-21.png]]
354	354
355	355
356		-3. Decode the info in web
357	357
	383	+(% style="color:blue" %)**3. Decode the info in web**
	384	+
358	358	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
359	359
360	360	Need these three fields:
...	...	@@ -365,6 +365,7 @@
365	365
366	366	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
367	367
	395	+
368	368	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
369	369
370	370	[[image:image-20220526171029-20.png]]
...	...	@@ -374,15 +374,19 @@
374	374	)))
375	375
376	376
	405	+
377	377	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
378	378
	408	+
379	379	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.
380	380
381	381
	412	+
382	382	= 9. Why do I see a "MIC Mismatch" error message from the server? =
383	383
	415	+
384	384	(((
385		-1)If the user receives a "MIC Mismatch" message after registering the node on the server.
	417	+1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
386	386	)))
387	387
388	388	(((
...	...	@@ -404,32 +404,29 @@
404	404	* (((
405	405	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
406	406
	439	+
	440	+
407	407
408	408	)))
409	409
410	410	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
411	411
412		-* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
413	413
414		-(((
415		-When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
416		-)))
	447	+* If you are using US915, AU915 or AS923 frequencies.It is possible because: .
417	417
418		-(((
	449	+When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
	450	+
419	419	When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
420		-)))
421	421
422		-* (((
423	423	Solution: Use the decoder to filter out this 00 packet.
424		-)))
425		-* (((
	454	+
426	426	Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
427	427
428		-
429		-)))
430	430
	458	+
431	431	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
432	432
	461	+
433	433	(((
434	434	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
435	435	)))
...	...	@@ -460,6 +460,8 @@
460	460
461	461	(((
462	462	You can rewrites the keys by running commands in AT Console
	492	+
	493	+
463	463	)))
464	464
465	465	(((
...	...	@@ -486,6 +486,7 @@
486	486	(Any combination of 16 bit codes can be used）
487	487
488	488
	520	+
489	489	= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
490	490	)))
491	491