Summary

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

Details

Page properties

Content

...	...	@@ -1,12 +1,9 @@
1	1	**~ Contents:**
2	2
3		-(((
4		-
5		-)))
6		-
7	7	{{toc/}}
8	8
9	9
	6	+
10	10	= 1. OTAA Join Process Debug =
11	11
12	12	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.
...	...	@@ -185,7 +185,7 @@
185	185	Depends on Class A or Class C, the receive windows will be a little difference,
186	186	)))
187	187
188		-[[image:image-20220526164547-11.png]]
	185	+[[image:image-20220531161828-1.png]]
189	189
190	190	receive windows for Class A and Class C
191	191
...	...	@@ -197,6 +197,8 @@
197	197	* This packet must match the frequency of the RX1 or RX2 window.
198	198	* 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.**
199	199
	197	+
	198	+
200	200	== 5.2 See Debug Info ==
201	201
202	202	(((
...	...	@@ -389,6 +389,7 @@
389	389
390	390	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.
391	391
	391	+
392	392	= 9. Why do I see a "MIC Mismatch" error message from the server? =
393	393
394	394	(((
...	...	@@ -435,37 +435,67 @@
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		-
439	439
440	440	)))
441	441
442	442	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
443	443
	443	+(((
444	444	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
	445	+)))
445	445
	447	+(((
446	446	AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	449	+)))
447	447
	451	+(((
448	448	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	453	+)))
449	449
	455	+(((
450	450	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	457	+)))
451	451
	459	+(((
452	452	AT+APPEUI=00 00 00 00 00 00 00 00
	461	+)))
453	453
	463	+(((
	464	+
	465	+)))
454	454
	467	+(((
455	455	You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
	469	+)))
456	456
	471	+(((
457	457	You can rewrites the keys by running commands in AT Console
	473	+)))
458	458
459		-For example：
	475	+(((
	476	+**For example：**
	477	+)))
460	460
	479	+(((
461	461	AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
	481	+)))
462	462
	483	+(((
463	463	AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
	485	+)))
464	464
	487	+(((
465	465	AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
	489	+)))
466	466
	491	+(((
467	467	AT+APPEUI=2C 45 47 E3 24 12 23 24
	493	+)))
468	468
	495	+(((
469	469	(Any combination of 16 bit codes can be used）
	497	+)))
470	470
471	471
	500	+(% class="wikigeneratedid" %)
	501	+

image-20220531161828-1.png

Author

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

Size

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

Content