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		-**~ Table of Contents:**
	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
...	...	@@ -336,7 +336,15 @@
336	336	(% class="box infomessage" %)
337	337	(((
338	338	**Change to ABP Mode: AT+NJM=0**
	342	+)))
	343	+
	344	+(% class="box infomessage" %)
	345	+(((
339	339	**Change to fix frequency: AT+CHS=904900000**
	347	+)))
	348	+
	349	+(% class="box infomessage" %)
	350	+(((
340	340	**Change to fix DR: AT+DR=0**
341	341	)))
342	342
...	...	@@ -425,74 +425,39 @@
425	425	* (((
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
	439	+
428	428
429	429	)))
430	430
431	431	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
432	432
433		-(((
434	434	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
435		-)))
436	436
437		-(((
438	438	AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
439		-)))
440	440
441		-(((
442	442	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
443		-)))
444	444
445		-(((
446	446	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
447		-)))
448	448
449		-(((
450	450	AT+APPEUI=00 00 00 00 00 00 00 00
451		-)))
452	452
453		-(((
454		-
455		-)))
456	456
457		-(((
458	458	You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
459		-)))
460	460
461		-(((
462	462	You can rewrites the keys by running commands in AT Console
463		-)))
464	464
465		-(((
466		-**For example：**
467		-)))
	460	+For example：
468	468
469		-(((
470	470	AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
471		-)))
472	472
473		-(((
474	474	AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
475		-)))
476	476
477		-(((
478	478	AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
479		-)))
480	480
481		-(((
482	482	AT+APPEUI=2C 45 47 E3 24 12 23 24
483		-)))
484	484
485		-(((
486	486	(Any combination of 16 bit codes can be used）
487	487
488	488
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		-
497	497	(% class="wikigeneratedid" %)
498	498

image-20220531161828-1.png

Author

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

Size

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

Content