Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 11 added, 0 removed)
  • image-20220526141116-30.png
  • image-20220526141149-31.png
  • image-20220526141236-32.png
  • image-20220526141308-33.png
  • image-20220526141350-34.png
  • image-20220526141612-36.png
  • image-20220526141739-37.png
  • image-20220526141823-38.png
  • image-20220526141917-39.png
  • image-20220526141956-40.png
  • image-20220526142033-41.png

Details

Page properties

Content

...	...	@@ -435,16 +435,18 @@
435	435	Downlink command:01 00 00 5A
436	436	)))
437	437
438		-[[image:image-20220525091752-29.png]]
	438	+[[image:image-20220526141021-28.png]]
439	439
440	440	downlink
441	441
	442	+
442	442	After sending, you can view it in live data.
443	443
444		-[[image:image-20220525091816-30.png]]
	445	+[[image:image-20220526141052-29.png]]
445	445
446	446	downlink
447	447
	449	+
448	448	(((
449	449	When downlink is successfully sent, the downlink information can be received on the serial port.
450	450	)))
...	...	@@ -453,10 +453,11 @@
453	453	**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
454	454	)))
455	455
456		-[[image:image-20220525091855-31.png]]
	458	+[[image:image-20220526141116-30.png]]
457	457
458	458	downlink
459	459
	462	+
460	460	(((
461	461	(((
462	462	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
...	...	@@ -481,10 +481,11 @@
481	481	)))
482	482	)))
483	483
484		-[[image:image-20220525091925-32.png]]
	487	+[[image:image-20220526141149-31.png]]
485	485
486	486	downlink
487	487
	491	+
488	488	= 6. Request Remote Support =
489	489
490	490	(((
...	...	@@ -503,7 +503,7 @@
503	503	* If the device is sending join request to server?
504	504	* What frequency the device is sending?
505	505
506		-[[image:image-20220525092012-33.png]]
	510	+[[image:image-20220526141308-33.png]]
507	507
508	508	Console Output from End device to see the transmit frequency
509	509
...	...	@@ -511,10 +511,12 @@
511	511
512	512	* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
513	513
514		-[[image:image-20220525092043-34.png]]
	518	+[[image:image-20220526141612-36.png]]
515	515
	520	+
516	516	Console Output from End device to see the transmit frequency
517	517
	523	+
518	518	**2. Gateway packet traffic in gateway web or ssh. we can check:**
519	519
520	520	* (((
...	...	@@ -524,7 +524,7 @@
524	524	If the gateway gets the Join Accept message from server and transmit it via LoRa?
525	525	)))
526	526
527		-[[image:image-20220525092124-35.png]]
	533	+[[image:image-20220526141739-37.png]]
528	528
529	529	Console Output from Gateway to see packets between end node and server.
530	530
...	...	@@ -541,15 +541,16 @@
541	541	If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
542	542	)))
543	543
544		-[[image:image-20220525092157-36.png]]
	550	+[[image:image-20220526141823-38.png||height="501" width="1144"]]
545	545
546	546	The Traffic for the End node in the server, use TTNv3 as example
547	547
548	548
549		-[[image:image-20220525092231-37.png]]
	555	+[[image:image-20220526141917-39.png]]
550	550
551	551	The Traffic for the End node in the server, use TTNv3 as example
552	552
	559	+
553	553	**4. Data Page in LoRaWAN server**
554	554
555	555	(((
...	...	@@ -557,7 +557,7 @@
557	557	(((
558	558	If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
559	559
560		-[[image:image-20220525092546-1.png]]
	567	+[[image:image-20220526141956-40.png]]
561	561	)))
562	562	)))
563	563	)))
...	...	@@ -564,6 +564,7 @@
564	564
565	565	The data for the end device set in server
566	566
567		-[[image:image-20220525092430-40.png]]
568	568
	575	+[[image:image-20220526142033-41.png]]
	576	+
569	569	Check if OTAA Keys match the keys in device

image-20220526141116-30.png

Author

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

Size

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

Content

image-20220526141149-31.png

Author

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

Size

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

Content

image-20220526141236-32.png

Author

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

Size

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

Content

image-20220526141308-33.png

Author

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

Size

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

Content

image-20220526141350-34.png

Author

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

Size

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

Content

image-20220526141612-36.png

Author

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

Size

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

Content

image-20220526141739-37.png

Author

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

Size

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

Content

image-20220526141823-38.png

Author

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

Size

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

Content

image-20220526141917-39.png

Author

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

Size

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

Content

image-20220526141956-40.png

Author

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

Size

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

Content

image-20220526142033-41.png

Author

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

Size

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

Content