Changes for page Notes for TTN
Last modified by Mengting Qiu on 2024/08/20 17:29
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -84,16 +84,15 @@ 84 84 The Dragino gateway has supports the Secondary server settings. 85 85 86 86 87 - 88 88 === 2.2.2 Below list the support products and Requirements: === 89 89 90 90 91 91 ((( 92 -1. 91 +~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]] 93 93 ))) 94 94 95 95 ((( 96 -2. 95 +2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]] 97 97 ))) 98 98 99 99 ... ... @@ -110,7 +110,6 @@ 110 110 111 111 The users is needing to download and install the helium gateway-rs then click the button of Save&Apply 112 112 113 - 114 114 [[image:image-20220526135049-6.png]] 115 115 116 116 Download and Install gateway-rs ... ... @@ -122,7 +122,6 @@ 122 122 123 123 Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply 124 124 125 - 126 126 [[image:image-20220526135125-7.png]] 127 127 128 128 Configuration of helium ... ... @@ -601,7 +601,6 @@ 601 601 602 602 = 6. Request Remote Support = 603 603 604 - 605 605 ((( 606 606 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. 607 607 \\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:** ... ... @@ -613,24 +613,19 @@ 613 613 * End Node traffic (from server UI) to shows end node activity in server. (Normally possible) 614 614 * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI) 615 615 612 +**~1. End Device Join Screen shot, we can check:** 616 616 617 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:** 618 - 619 619 * If the device is sending join request to server? 620 620 * What frequency the device is sending? 621 621 622 - 623 623 [[image:image-20220526141308-33.png]] 624 624 625 625 Console Output from End device to see the transmit frequency 626 626 621 +User can run **AT+CFG **command to print configuration information. 627 627 628 - Usercanrun(%style="color:blue"%)**AT+CFG**(%%)commandtoprintconfiguration information.623 +* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode) 629 629 630 -* Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode) 631 - 632 - 633 - 634 634 [[image:image-20220526141612-36.png]] 635 635 636 636 ... ... @@ -637,17 +637,13 @@ 637 637 Console Output from End device to see the transmit frequency 638 638 639 639 631 +**2. Gateway packet traffic in gateway web or ssh. we can check:** 640 640 641 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:** 642 - 643 643 * ((( 644 644 If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency) 645 645 ))) 646 646 * ((( 647 647 If the gateway gets the Join Accept message from server and transmit it via LoRa? 648 - 649 - 650 - 651 651 ))) 652 652 653 653 [[image:image-20220526141739-37.png]] ... ... @@ -655,9 +655,8 @@ 655 655 Console Output from Gateway to see packets between end node and server. 656 656 657 657 645 +**3. Gateway Traffic Page in LoRaWAN Server** 658 658 659 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server** 660 - 661 661 * ((( 662 662 If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings. 663 663 ))) ... ... @@ -666,9 +666,6 @@ 666 666 ))) 667 667 * ((( 668 668 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. 669 - 670 - 671 - 672 672 ))) 673 673 674 674 [[image:image-20220526141823-38.png||height="501" width="1144"]] ... ... @@ -676,21 +676,18 @@ 676 676 The Traffic for the End node in the server, use TTNv3 as example 677 677 678 678 679 - 680 680 [[image:image-20220526141917-39.png]] 681 681 682 682 The Traffic for the End node in the server, use TTNv3 as example 683 683 684 684 667 +**4. Data Page in LoRaWAN server** 685 685 686 -(% style="color:blue" %)**4. Data Page in LoRaWAN server** 687 - 688 688 ((( 689 689 ((( 690 690 ((( 691 691 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. 692 692 693 - 694 694 [[image:image-20220526141956-40.png]] 695 695 ))) 696 696 ))) ... ... @@ -699,7 +699,6 @@ 699 699 The data for the end device set in server 700 700 701 701 702 - 703 703 [[image:image-20220526142033-41.png]] 704 704 705 705 Check if OTAA Keys match the keys in device