Skip to Content

Changes for page Notes for ChirpStack

Last modified by Xiaoling on 2025/03/22 09:21
From version 217.1
edited by Kilight Cao
on 2024/07/17 10:26
Change comment: Uploaded new attachment "image-20240717102613-5.png", version {1}
To version 245.1
edited by Edwin Chen
on 2025/01/30 09:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Edwin
Content
... ... @@ -45,7 +45,7 @@
45 45  
46 46  **Step 1: Add application**
47 47  
48 -[[image:image-20230702094608-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**
... ... @@ -467,7 +467,7 @@
467 467  = 8.  Downlink =
468 468  
469 469  
470 -=== 8.1 Chirpstack Downlink Note ===
470 +== 8.1 Schedule Downlink via Web UI ==
471 471  
472 472  
473 473  ==== Select HEX format for downlink ====
... ... @@ -496,10 +496,10 @@
496 496  **Make sure the RX2DR is the same in the end node**
497 497  
498 498  
499 -== 8.3  Loraserver Downlink Note ==
499 +== 8.2 Schedule Downlink via API ==
500 500  
501 501  
502 -User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
502 +User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End Node
503 503  
504 504  (((
505 505  **Below is examples:**
... ... @@ -518,7 +518,6 @@
518 518  (((
519 519  **MQTT Connect to ChirpStack**
520 520  
521 -
522 522  
523 523  )))
524 524  
... ... @@ -611,28 +611,151 @@
611 611  )))
612 612  
613 613  
614 -== 8.4  Add the decode function in Chirpstack for the payload ==
613 +== 8.3  Add decoder function in Chirpstack for downlink message ==
615 615  
616 616  
617 -User enters the payload code according to the steps.
616 +
618 618  
619 -Add the node device decoder you are using. The decoder for each node device is different. The decoder is found in this link: **[[decoder for dragino end node>>https://github.com/dragino/dragino-end-node-decoder]]**
618 += 9.  Chirpstack Multicast Configuration =
620 620  
621 -[[image:image-20220531173754-15.png||height="474" width="1334"]]
622 622  
621 +== 9.1  Introduction ==
623 623  
624 -[[image:image-20220531173856-16.png]]
623 +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.
625 625  
625 +Multicast can be used for the following device-classes:
626 626  
627 -[[image:image-20220531174120-20.png]]
627 +* Class-B
628 +* Class-C
628 628  
629 -[[image:image-20220531174046-19.png]]
630 +== 9.2  Example to configure chirpstack Multicast ==
630 630  
631 631  
632 -= 9.  Multiply Uplink in ChirpStack =
633 +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.
633 633  
635 +[[image:image-20240923105725-1.png]]
634 634  
637 +
638 +This example assumes that the user already has the prerequisites:
639 +
640 +* (% style="color:blue" %)**SN50v3-LB Software Location:   **(%%)**[[SN50v3-LB_protocol_008(AU915).bin>>attach:https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-LB/#H3.ConfigureSN50v3-LB2FLS||target="_blank"]] .**Users need to flash them with the firmware support Multicast.
641 +* (% style="color:blue" %)**SN50v3-LB Configure:   **(%%)Enable CLASS C and DISFCNTCHECK(The downlink fcnt is not compared with the fcnt of the node).
642 +
643 +(% class="wikigeneratedid" %)
644 + **AT command:** (% style="color:blue" %)**AT+CLASS=C**
645 +
646 +(% class="wikigeneratedid" %)
647 + (% style="color:blue" %)**AT+DISFCNTCHECK=1**
648 +
649 +(% class="wikigeneratedid" %)
650 +For details on how to configure the SN50v3-LB, please refer to the link:** [[Configure SN50v3-LB>>https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-LB/#H3.ConfigureSN50v3-LB2FLS]]**
651 +
652 +* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
653 +
654 +Register LPS8v2 gateway to Chirpstack. See section :[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0SemtechUDPforChirpStackv4>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0SemtechUDPforChirpStackv4]]
655 +
656 +Register SN50v3-LB to Chirpstack. See section :[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H2.A0Nodeusageintroduction>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H2.A0Nodeusageintroduction]]
657 +
658 +
659 +=== Step 1. Create the multicast group ===
660 +
661 +
662 +Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915
663 +
664 +[[image:image-20240923141847-3.png||height="620" width="1207"]]
665 +
666 +
667 +Enter the Multicast address,Multicast network session key,Multicast application session key.
668 +
669 +Use the default LoRaWAN settings, as below:
670 +
671 +* EU868: 869525000hz, DR0
672 +
673 +* US915: 923300000hz, DR8
674 +
675 +* CN470: 505300000hz, DR0
676 +
677 +* AU915: 923300000hz, DR8
678 +
679 +* AS923: 923200000hz, DR2
680 +
681 +* KR920: 921900000hz, DR0
682 +
683 +* IN865: 866550000hz, DR2
684 +
685 +* RU864: 869100000hz, DR0
686 +
687 +Group type: **Class-C**
688 +
689 +Class-C scheduling type : **Delay**
690 +
691 +[[image:image-20240923142446-5.png||height="720" width="1208"]]
692 +
693 +
694 +=== Step 2. Add gateways and devices to the multicast group ===
695 +
696 +
697 +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**.
698 +
699 +[[image:image-20240923144335-6.png||height="619" width="1209"]]
700 +
701 +[[image:image-20240923144418-7.png||height="572" width="1206"]]
702 +
703 +
704 +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
705 +
706 +[[image:image-20240923144749-9.png||height="623" width="1211"]]
707 +
708 +
709 +Access the multicast group to check whether two SN50V3-LBs and gateways are added successfully
710 +
711 +[[image:image-20240923145148-10.png||height="601" width="1218"]]
712 +
713 +
714 +=== Step 3. Use the API for multicast Downlink ===
715 +
716 +
717 +To use API Downlink, user first need to generate an API key
718 +
719 +[[image:image-20240923145624-18.png||height="429" width="1211"]]
720 +
721 +[[image:image-20240923145520-16.png||height="422" width="1212"]]
722 +
723 +
724 +For example:**[[https:~~/~~/www.chirpstack.io/docs/chirpstack/api/index.html>>url:https://www.chirpstack.io/docs/chirpstack/api/index.html]]**
725 +
726 +[[image:image-20240923145953-21.png||height="808" width="1222"]]
727 +
728 +
729 +Users can access the Linux console of the gateway via SSH, and then use the curl command to multicast Downlink
730 +
731 +The format is as follows:
732 +
733 +(% class="box infomessage" %)
635 635  (((
735 +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 '{
736 + "queueItem": {
737 + "data": "EjRWeA==",
738 + "fCnt": 0,
739 + "fPort": 123
740 + }
741 +}'
742 +)))
743 +
744 +In the command,eyJ........._2v4UYPV0w is the API key, which can be obtained from the Chirpstack server and the data format is base64,
745 +
746 +
747 +=== Result ===
748 +
749 +Connecting to the SN50v3-LB using the serial USB-TTL port can check that two SN50v3-LBs are receiving Downlink at the same time
750 +
751 +[[image:image-20240923151814-23.png||height="563" width="1255"]]
752 +
753 +
754 += 10.  Multiply Uplink in ChirpStack =
755 +
756 +
757 +(((
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 ==
797 +== 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 -= 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
916 += 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 -= 11.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
965 += 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 -== **11.1 Generate API Tokens** ==
972 +== **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 -== **11.2 Template file** ==
985 +== **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 -== **11.3 Batch Register** ==
1007 +== **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 -= 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1020 += 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 -== 12.1 Link Node-Red to Local ChirpStack ==
1031 +== 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 -== 12.2 Check result. ==
1065 +== 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 -= 13.  Trouble Shooting =
1075 += 14.  Trouble Shooting =
954 954  
955 -== 13.1  MIC Mismatch or MIC Failed ==
1077 +== 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 -== 13.2  The node is very close to the gateway, but the signal is poor ==
1088 +== 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 -== 13.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1117 +== 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"]]
1125 +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  
1128 +**The possible reasons are: **
1129 +
1130 +~1. The signal of the node device and the gateway is not good
1131 +
1132 +2. Too many node devices affect the downlink of the gateway
1133 +
1134 +
1135 +[[image:image-20240717085339-1.jpeg]]
1136 +
1137 +
1138 +* **Disable frame-counter validation**
1139 +
1140 +[[image:image-20240717102613-5.png||height="803" width="1211"]]
1141 +
1142 +
1143 +* **Result**
1144 +
1007 1007  [[image:image-20240717092428-4.jpeg]]
1008 1008  
1009 -== 13.4  How to get the log information of the node？ ==
1010 1010  
1148 +== 14.4  How to get the log information of the node？ ==
1011 1011  
1150 +
1012 1012  ~1. Get information about a single node.
1013 1013  
1014 1014  * Download this file in the node's live data interface.
SN50v3-LB_协议008（AU915）(1).bin
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +89.2 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