Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 1 removed)
  • image-20220531161828-1.png

Details

Page properties

Author

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

Content

...	...	@@ -1,9 +1,12 @@
1	1	**~ Contents:**
2	2
	3	+(((
	4	+
	5	+)))
	6	+
3	3	{{toc/}}
4	4
5	5
6		-
7	7	= 1. OTAA Join Process Debug =
8	8
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.
...	...	@@ -182,7 +182,7 @@
182	182	Depends on Class A or Class C, the receive windows will be a little difference,
183	183	)))
184	184
185		-[[image:image-20220531161828-1.png]]
	188	+[[image:image-20220526164547-11.png]]
186	186
187	187	receive windows for Class A and Class C
188	188
...	...	@@ -194,7 +194,6 @@
194	194	* This packet must match the frequency of the RX1 or RX2 window.
195	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.**
196	196
197		-
198	198	== 5.2 See Debug Info ==
199	199
200	200	(((
...	...	@@ -305,7 +305,6 @@
305	305	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
306	306	* End Node traffic (from server UI) to shows end node activity in server.
307	307
308		-
309	309	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310	310
311	311	(((
...	...	@@ -338,7 +338,15 @@
338	338	(% class="box infomessage" %)
339	339	(((
340	340	**Change to ABP Mode: AT+NJM=0**
	342	+)))
	343	+
	344	+(% class="box infomessage" %)
	345	+(((
341	341	**Change to fix frequency: AT+CHS=904900000**
	347	+)))
	348	+
	349	+(% class="box infomessage" %)
	350	+(((
342	342	**Change to fix DR: AT+DR=0**
343	343	)))
344	344
...	...	@@ -380,7 +380,6 @@
380	380
381	381	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.
382	382
383		-
384	384	= 9. Why do I see a "MIC Mismatch" error message from the server? =
385	385
386	386	(((
...	...	@@ -427,74 +427,37 @@
427	427	* (((
428	428	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]]
429	429
	438	+
430	430
431	431	)))
432	432
433	433	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
434	434
435		-(((
436	436	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
437		-)))
438	438
439		-(((
440	440	AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
441		-)))
442	442
443		-(((
444	444	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
445		-)))
446	446
447		-(((
448	448	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
449		-)))
450	450
451		-(((
452	452	AT+APPEUI=00 00 00 00 00 00 00 00
453		-)))
454	454
455		-(((
456		-
457		-)))
458	458
459		-(((
460	460	You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
461		-)))
462	462
463		-(((
464	464	You can rewrites the keys by running commands in AT Console
465		-)))
466	466
467		-(((
468		-**For example：**
469		-)))
	459	+For example：
470	470
471		-(((
472	472	AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
473		-)))
474	474
475		-(((
476	476	AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
477		-)))
478	478
479		-(((
480	480	AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
481		-)))
482	482
483		-(((
484	484	AT+APPEUI=2C 45 47 E3 24 12 23 24
485		-)))
486	486
487		-(((
488	488	(Any combination of 16 bit codes can be used）
489	489
490	490
491		-= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
492		-)))
493		-
494		-
495		-Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
496		-
497		-
498		-
499		-(% class="wikigeneratedid" %)
500		-

image-20220531161828-1.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-98.6 KB

Content