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, 19 added, 0 removed)
- image-20240717102613-5.png
- 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,6 +629,136 @@ 629 629 [[image:image-20220531174046-19.png]] 630 630 631 631 632 += 9. Chirpstack Multicast Configuration = 633 + 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" %) 742 +((( 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 + 632 632 = 9. Multiply Uplink in ChirpStack = 633 633 634 634 ... ... @@ -999,13 +999,30 @@ 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 1155 + 1009 1009 == 13.4 How to get the log information of the node? == 1010 1010 1011 1011
- image-20240717102613-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +56.1 KB - Content
- 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