Changes for page Notes for ChirpStack
Last modified by Kilight Cao on 2024/09/24 15:23
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 18 added, 0 removed)
- image-20240831154333-1.png
- image-20240923105725-1.png
- image-20240923141847-3.png
- image-20240923142441-4.png
- image-20240923142446-5.png
- image-20240923144335-6.png
- image-20240923144418-7.png
- image-20240923144744-8.png
- image-20240923144749-9.png
- image-20240923145148-10.png
- image-20240923145506-12.png
- image-20240923145520-16.png
- image-20240923145624-18.png
- image-20240923145945-19.png
- image-20240923145949-20.png
- image-20240923145953-21.png
- image-20240923151236-22.png
- image-20240923151814-23.png
Details
- Page properties
-
- Content
-
... ... @@ -45,7 +45,7 @@ 45 45 46 46 **Step 1: Add application** 47 47 48 -[[image:image-202 30702094608-1.png||height="537" width="1015"]]48 +[[image:image-20240831154333-1.png||height="553" width="1074"]] 49 49 50 50 51 51 **Step 2:Fill name** ... ... @@ -629,10 +629,140 @@ 629 629 [[image:image-20220531174046-19.png]] 630 630 631 631 632 -= 9. Multi plyUplinkin ChirpStack=632 += 9. Chirpstack Multicast Configuration = 633 633 634 634 635 +== 9.1 Introduction == 636 + 637 +ChirpStack has support for creating multicast-groups to which devices can be assigned. When enqueueing a downlink payload for a multicast-group, ChirpStack will analyze which gateways must be used for broadcasting to cover the complete multicast-group. This means that potentially, a single multicast downlink payload will be emitted multiple times. 638 + 639 +Multicast can be used for the following device-classes: 640 + 641 +* Class-B 642 +* Class-C 643 + 644 +== 9.2 Example to configure chirpstack Multicast == 645 + 646 + 647 +This section illustrates how to configure ChirpStack Multicast. Below is the network structure, we use our LPS8v2 as the LoRaWAN gateway and two SN50v3-LB as the LoRaWAN end-node here. 648 + 649 +[[image:image-20240923105725-1.png]] 650 + 651 + 652 +This example assumes users already have: 653 + 654 +* SN50v3-LB register on ChirpStack server already 655 +* The user is able to see the data on the ChirpStack server device page. 656 + 657 +(% class="wikigeneratedid" %) 658 +(% style="color:red" %)**Note: **(%%)SN50v3-LB must enable CLASS C and DISFCNTCHECK(The downlink fcnt is not compared with the fcnt of the node). 659 + 660 +(% class="wikigeneratedid" %) 661 +AT command: **AT+CLASS=C** 662 + 663 +(% class="wikigeneratedid" %) 664 + **AT+DISFCNTCHECK=1** 665 + 666 + 667 +=== Step 1. Create the multicast group === 668 + 669 + 670 +Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915 671 + 672 +[[image:image-20240923141847-3.png||height="620" width="1207"]] 673 + 674 + 675 +Enter the Multicast address,Multicast network session key,Multicast application session key. 676 + 677 +Use the default LoRaWAN settings, as below: 678 + 679 +* EU868: 869525000hz, DR0 680 + 681 +* US915: 923300000hz, DR8 682 + 683 +* CN470: 505300000hz, DR0 684 + 685 +* AU915: 923300000hz, DR8 686 + 687 +* AS923: 923200000hz, DR2 688 + 689 +* KR920: 921900000hz, DR0 690 + 691 +* IN865: 866550000hz, DR2 692 + 693 +* RU864: 869100000hz, DR0 694 + 695 +Group type: **Class-C** 696 + 697 +Class-C scheduling type : **Delay** 698 + 699 +[[image:image-20240923142446-5.png||height="720" width="1208"]] 700 + 701 + 702 +=== Step 2. Add gateways and devices to the multicast group === 703 + 704 + 705 +Select a gateway on the "**Gateways**" screen, click "**selected gateways"**, and click "**Add to multicast-group**" to add the gateway to the corresponding multicast group, for example, **multicast_test01_au915**. 706 + 707 +[[image:image-20240923144335-6.png||height="619" width="1209"]] 708 + 709 +[[image:image-20240923144418-7.png||height="572" width="1206"]] 710 + 711 + 712 +On the **Application->Devices** interface, select two SN50v3-LB nodes registered with multicast support, and then click "**Selected devices**". and click "**Add to multicast-group**" to add the node to the corresponding multicast group 713 + 714 +[[image:image-20240923144749-9.png||height="623" width="1211"]] 715 + 716 + 717 +Access the multicast group to check whether two SN50V3-LBs and gateways are added successfully 718 + 719 +[[image:image-20240923145148-10.png||height="601" width="1218"]] 720 + 721 + 722 +=== Step 3. Use the API for multicast Downlink === 723 + 724 + 725 +To use API Downlink, user first need to generate an API key 726 + 727 +[[image:image-20240923145624-18.png||height="429" width="1211"]] 728 + 729 +[[image:image-20240923145520-16.png||height="422" width="1212"]] 730 + 731 + 732 +For example:**[[https:~~/~~/www.chirpstack.io/docs/chirpstack/api/index.html>>url:https://www.chirpstack.io/docs/chirpstack/api/index.html]]** 733 + 734 +[[image:image-20240923145953-21.png||height="808" width="1222"]] 735 + 736 + 737 +Users can access the Linux console of the gateway via SSH, and then use the curl command to multicast Downlink 738 + 739 +The format is as follows: 740 + 741 +(% class="box infomessage" %) 635 635 ((( 743 +curl -X POST 'http:~/~/**Chirpstack_Server_Address**:8090/api/multicast-groups/**Multicast_Groups_ID**/queue' -H "Content-Type: application/json" -H "Authorization: Bearer **eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhdWQiOiJjaGlycHN0YWNrIiwiaXNzIjoiY2hpcnBzdGFjayIsInN1YiI6IjM3YmRiNzBjLTNjODgtNDFjMi04YmQ2LTgyMDI4ZjdkNzY3NyIsInR5cCI6ImtleSJ9.p1xvRP1PAdwLnLAJn9w6ef612KM8oPZSa_2v4UYPV0w**" -d '{ 744 + "queueItem": { 745 + "data": "EjRWeA==", 746 + "fCnt": 0, 747 + "fPort": 123 748 + } 749 +}' 750 +))) 751 + 752 +In the command,eyJ........._2v4UYPV0w is the API key, which can be obtained from the Chirpstack server and the data format is base64, 753 + 754 + 755 +=== Result === 756 + 757 +Connecting to the SN50v3-LB using the serial USB-TTL port can check that two SN50v3-LBs are receiving Downlink at the same time 758 + 759 +[[image:image-20240923151814-23.png||height="563" width="1255"]] 760 + 761 + 762 += 10. Multiply Uplink in ChirpStack = 763 + 764 + 765 +((( 636 636 nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data. 637 637 ))) 638 638 ... ... @@ -672,7 +672,7 @@ 672 672 [[image:image-20220601102430-1.png||height="508" width="1120"]] 673 673 674 674 675 -== 9.1 Solution ==805 +== 10.1 Solution == 676 676 677 677 678 678 This example uses the Windows version as a template, other versions can refer to this. Similiar reference: [[https:~~/~~/confluence.alitecs.de/plugins/servlet/mobile?contentId=79790102#content/view/79790102>>url:https://confluence.alitecs.de/plugins/servlet/mobile?contentId=79790102#content/view/79790102]] ... ... @@ -791,7 +791,7 @@ 791 791 Finish. 792 792 793 793 794 -= 1 0. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =924 += 11. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 795 795 796 796 797 797 All data is published to the MQTT topics. if you want to store/get the data, you would have to create an MQTT handler and store the data yourself. ... ... @@ -840,7 +840,7 @@ 840 840 [[image:image-20221012173639-1.png||height="273" width="1206"]] 841 841 842 842 843 -= 1 1. How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =973 += 12. How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server = 844 844 845 845 The following example is based on the built-in ChirpStack server for LPS8V2 846 846 ... ... @@ -847,7 +847,7 @@ 847 847 [[image:image-20231201174640-1.png||height="584" width="1148"]] 848 848 849 849 850 -== **1 1.1 Generate API Tokens** ==980 +== **12.1 Generate API Tokens** == 851 851 852 852 Access the built-in chirpstack , click "**API Key**" and "**Add API Key**". 853 853 ... ... @@ -860,7 +860,7 @@ 860 860 [[image:image-20231204104802-1.png]] 861 861 862 862 863 -== **1 1.2 Template file** ==993 +== **12.2 Template file** == 864 864 865 865 866 866 Click on **"Template File Download"**, the user will download a **register.csv** template file, ... ... @@ -882,7 +882,7 @@ 882 882 883 883 884 884 885 -== **1 1.3 Batch Register** ==1015 +== **12.3 Batch Register** == 886 886 887 887 [[image:image-20231204113136-11.png||height="362" width="1062"]] 888 888 ... ... @@ -895,7 +895,7 @@ 895 895 896 896 897 897 898 -= 1 2. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =1028 += 13. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 = 899 899 900 900 901 901 LPS8v2 includes a local ChirpStack Server and Node-Red. This example shows how to configure LHT65N to use with the local Node-Red server. This example assumes users already have: ... ... @@ -906,7 +906,7 @@ 906 906 Below are the steps to plot the sensor data on LPS8v2 Node-Red. 907 907 908 908 909 -== 1 2.1 Link Node-Red to Local ChirpStack ==1039 +== 13.1 Link Node-Red to Local ChirpStack == 910 910 911 911 912 912 Users can download the Node-Red decoder from this link and import it into the Node-Red platform: **[[attach:LHT65N-ChirpStack-node-red.json||target="_blank"]]** ... ... @@ -940,7 +940,7 @@ 940 940 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Notes%20for%20TTN/WebHome/image-20220914140918-5.png?width=1121&height=602&rev=1.1||alt="image-20220914140918-5.png"]] 941 941 942 942 943 -== 1 2.2 Check result. ==1073 +== 13.2 Check result. == 944 944 945 945 946 946 Users can check logs by adding debug. ... ... @@ -950,9 +950,9 @@ 950 950 [[image:image-20230529150923-1.png||height="424" width="1118"]] 951 951 952 952 953 -= 1 3. Trouble Shooting =1083 += 14. Trouble Shooting = 954 954 955 -== 1 3.1 MIC Mismatch or MIC Failed ==1085 +== 14.1 MIC Mismatch or MIC Failed == 956 956 957 957 958 958 ((( ... ... @@ -963,7 +963,7 @@ 963 963 Under normal circumstances, users need to change the APPKEY to solve this problem. 964 964 965 965 966 -== 1 3.2 The node is very close to the gateway, but the signal is poor ==1096 +== 14.2 The node is very close to the gateway, but the signal is poor == 967 967 968 968 969 969 If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink ... ... @@ -992,7 +992,7 @@ 992 992 **Note: lorawan's protocol link——[[LoRaWAN® Regional Parameters v1.0.3revA (lora-alliance.org)>>url:https://resources.lora-alliance.org/document/lorawan-regional-parameters-v1-0-3reva]]** 993 993 994 994 995 -== 1 3.3 ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==1125 +== 14.3 ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" == 996 996 997 997 998 998 This is because the node's packets are retransmitted, and the Fcnt of these packets is the same. ... ... @@ -999,16 +999,33 @@ 999 999 1000 1000 The user can Disable frame-counter validation on the chirpstack node and this warning message will not appear in the logs. 1001 1001 1002 -[[image:https://qiye.aliyun.com/attachment/downloadex?ri=%2Falimail%2FinternalLinks%2FrefreshToken&o=1&et=normal&ext=png&e=kilight%40dragino.cc&f=008dd83c-c893-43e6-8ad3-731d3b8d7be0&m=2_0%3ADzzzzyNOXCB%24---.YRE7agI&n=image001.png]][[image:image-20240717085339-1.jpeg]] 1003 1003 1004 - [[image:image-20240717090537-2.jpeg||height="589"width="1078"]]1133 +The packet is retransmitted because the node device has enabled the acknowledgment uplink packet mode and the node cannot receive the ACK acknowledgment packet delivered by the gateway. 1005 1005 1006 1006 1136 +**The possible reasons are: ** 1137 + 1138 +~1. The signal of the node device and the gateway is not good 1139 + 1140 +2. Too many node devices affect the downlink of the gateway 1141 + 1142 + 1143 +[[image:image-20240717085339-1.jpeg]] 1144 + 1145 + 1146 +* **Disable frame-counter validation** 1147 + 1148 +[[image:image-20240717102613-5.png||height="803" width="1211"]] 1149 + 1150 + 1151 +* **Result** 1152 + 1007 1007 [[image:image-20240717092428-4.jpeg]] 1008 1008 1009 -== 13.4 How to get the log information of the node? == 1010 1010 1156 +== 14.4 How to get the log information of the node? == 1011 1011 1158 + 1012 1012 ~1. Get information about a single node. 1013 1013 1014 1014 * Download this file in the node's live data interface.
- image-20240831154333-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +83.4 KB - Content
- image-20240923105725-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +104.9 KB - Content
- image-20240923141847-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +82.3 KB - Content
- image-20240923142441-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.0 KB - Content
- image-20240923142446-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.0 KB - Content
- image-20240923144335-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +92.4 KB - Content
- image-20240923144418-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +61.1 KB - Content
- image-20240923144744-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +99.1 KB - Content
- image-20240923144749-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +99.1 KB - Content
- image-20240923145148-10.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +42.7 KB - Content
- image-20240923145506-12.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.6 KB - Content
- image-20240923145520-16.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.6 KB - Content
- image-20240923145624-18.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +52.9 KB - Content
- image-20240923145945-19.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +61.4 KB - Content
- image-20240923145949-20.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +61.4 KB - Content
- image-20240923145953-21.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +61.4 KB - Content
- image-20240923151236-22.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +70.2 KB - Content
- image-20240923151814-23.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +115.8 KB - Content