Summary

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

Details

Page properties

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,8 +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		-
199	199	== 5.2 See Debug Info ==
200	200
201	201	(((
...	...	@@ -388,7 +388,6 @@
388	388
389	389	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.
390	390
391		-
392	392	= 9. Why do I see a "MIC Mismatch" error message from the server? =
393	393
394	394	(((
...	...	@@ -435,67 +435,37 @@
435	435	* (((
436	436	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]]
437	437
	438	+
438	438
439	439	)))
440	440
441	441	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
442	442
443		-(((
444	444	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
445		-)))
446	446
447		-(((
448	448	AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
449		-)))
450	450
451		-(((
452	452	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
453		-)))
454	454
455		-(((
456	456	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
457		-)))
458	458
459		-(((
460	460	AT+APPEUI=00 00 00 00 00 00 00 00
461		-)))
462	462
463		-(((
464		-
465		-)))
466	466
467		-(((
468	468	You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
469		-)))
470	470
471		-(((
472	472	You can rewrites the keys by running commands in AT Console
473		-)))
474	474
475		-(((
476		-**For example：**
477		-)))
	459	+For example：
478	478
479		-(((
480	480	AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
481		-)))
482	482
483		-(((
484	484	AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
485		-)))
486	486
487		-(((
488	488	AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
489		-)))
490	490
491		-(((
492	492	AT+APPEUI=2C 45 47 E3 24 12 23 24
493		-)))
494	494
495		-(((
496	496	(Any combination of 16 bit codes can be used）
497		-)))
498	498
499	499
500		-(% class="wikigeneratedid" %)
501		-

image-20220531161828-1.png

Author

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

Size

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

Content