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		-**~ Contents:**
	1	+**~ Table of 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
...	...	@@ -339,15 +339,7 @@
339	339	(% class="box infomessage" %)
340	340	(((
341	341	**Change to ABP Mode: AT+NJM=0**
342		-)))
343		-
344		-(% class="box infomessage" %)
345		-(((
346	346	**Change to fix frequency: AT+CHS=904900000**
347		-)))
348		-
349		-(% class="box infomessage" %)
350		-(((
351	351	**Change to fix DR: AT+DR=0**
352	352	)))
353	353
...	...	@@ -436,39 +436,74 @@
436	436	* (((
437	437	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]]
438	438
439		-
440	440
441	441	)))
442	442
443	443	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
444	444
	433	+(((
445	445	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
	435	+)))
446	446
	437	+(((
447	447	AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	439	+)))
448	448
	441	+(((
449	449	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	443	+)))
450	450
	445	+(((
451	451	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	447	+)))
452	452
	449	+(((
453	453	AT+APPEUI=00 00 00 00 00 00 00 00
	451	+)))
454	454
	453	+(((
	454	+
	455	+)))
455	455
	457	+(((
456	456	You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
	459	+)))
457	457
	461	+(((
458	458	You can rewrites the keys by running commands in AT Console
	463	+)))
459	459
460		-For example：
	465	+(((
	466	+**For example：**
	467	+)))
461	461
	469	+(((
462	462	AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
	471	+)))
463	463
	473	+(((
464	464	AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
	475	+)))
465	465
	477	+(((
466	466	AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
	479	+)))
467	467
	481	+(((
468	468	AT+APPEUI=2C 45 47 E3 24 12 23 24
	483	+)))
469	469
	485	+(((
470	470	(Any combination of 16 bit codes can be used）
471	471
472	472
	489	+= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
	490	+)))
	491	+
	492	+
	493	+Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
	494	+
	495	+
	496	+
473	473	(% class="wikigeneratedid" %)
474	474

image-20220531161828-1.png

Author

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

Size

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

Content