Changes for page Notes for ChirpStack

Last modified by Xiaoling on 2025/03/22 09:21
<
From version < 244.1 >
edited by Kilight Cao
on 2024/09/24 15:23
To version < 238.1 >
edited by Kilight Cao
on 2024/09/23 15:12
>
Change comment: Uploaded new attachment "image-20240923151236-22.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -644,131 +644,21 @@
644 644  == 9.2  Example to configure chirpstack Multicast ==
645 645  
646 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.
647 +This section illustrates how to configure ChirpStack Multicast. Below is the network structure, we use our LPS8v2 as the LoRaWAN gateway and SN50v3-LB as the LoRaWAN end-node here.
648 648  
649 649  [[image:image-20240923105725-1.png]]
650 650  
651 +The LPS8V2 is already set to connect to Chirpstack. So what we need to do now is only configure register these devices to Chirpstack:
651 651  
652 -This example assumes that the user already has the prerequisites:
653 653  
654 -* (% 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.
655 -* (% style="color:blue" %)**SN50v3-LB Configure:   **(%%)Enable CLASS C and DISFCNTCHECK(The downlink fcnt is not compared with the fcnt of the node).
656 -
657 -(% class="wikigeneratedid" %)
658 - **AT command:** (% style="color:blue" %)**AT+CLASS=C**
659 -
660 -(% class="wikigeneratedid" %)
661 - (% style="color:blue" %)**AT+DISFCNTCHECK=1**
662 -
663 -(% class="wikigeneratedid" %)
664 -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]]**
665 -
666 -* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
667 -
668 -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]]
669 -
670 -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]]
671 -
672 -
673 673  === Step 1. Create the multicast group ===
674 674  
675 675  
676 -Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915
677 677  
678 -[[image:image-20240923141847-3.png||height="620" width="1207"]]
658 += 9.  Multiply Uplink in ChirpStack =
679 679  
680 680  
681 -Enter the Multicast address,Multicast network session key,Multicast application session key.
682 -
683 -Use the default LoRaWAN settings, as below:
684 -
685 -* EU868: 869525000hz, DR0
686 -
687 -* US915: 923300000hz, DR8
688 -
689 -* CN470: 505300000hz, DR0
690 -
691 -* AU915: 923300000hz, DR8
692 -
693 -* AS923: 923200000hz, DR2
694 -
695 -* KR920: 921900000hz, DR0
696 -
697 -* IN865: 866550000hz, DR2
698 -
699 -* RU864: 869100000hz, DR0
700 -
701 -Group type: **Class-C**
702 -
703 -Class-C scheduling type : **Delay**
704 -
705 -[[image:image-20240923142446-5.png||height="720" width="1208"]]
706 -
707 -
708 -=== Step 2. Add gateways and devices to the multicast group ===
709 -
710 -
711 -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**.
712 -
713 -[[image:image-20240923144335-6.png||height="619" width="1209"]]
714 -
715 -[[image:image-20240923144418-7.png||height="572" width="1206"]]
716 -
717 -
718 -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
719 -
720 -[[image:image-20240923144749-9.png||height="623" width="1211"]]
721 -
722 -
723 -Access the multicast group to check whether two SN50V3-LBs and gateways are added successfully
724 -
725 -[[image:image-20240923145148-10.png||height="601" width="1218"]]
726 -
727 -
728 -=== Step 3. Use the API for multicast Downlink ===
729 -
730 -
731 -To use API Downlink, user first need to generate an API key
732 -
733 -[[image:image-20240923145624-18.png||height="429" width="1211"]]
734 -
735 -[[image:image-20240923145520-16.png||height="422" width="1212"]]
736 -
737 -
738 -For example:**[[https:~~/~~/www.chirpstack.io/docs/chirpstack/api/index.html>>url:https://www.chirpstack.io/docs/chirpstack/api/index.html]]**
739 -
740 -[[image:image-20240923145953-21.png||height="808" width="1222"]]
741 -
742 -
743 -Users can access the Linux console of the gateway via SSH, and then use the curl command to multicast Downlink
744 -
745 -The format is as follows:
746 -
747 -(% class="box infomessage" %)
748 748  (((
749 -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 '{
750 - "queueItem": {
751 - "data": "EjRWeA==",
752 - "fCnt": 0,
753 - "fPort": 123
754 - }
755 -}'
756 -)))
757 -
758 -In the command,eyJ........._2v4UYPV0w is the API key, which can be obtained from the Chirpstack server and the data format is base64,
759 -
760 -
761 -=== Result ===
762 -
763 -Connecting to the SN50v3-LB using the serial USB-TTL port can check that two SN50v3-LBs are receiving Downlink at the same time
764 -
765 -[[image:image-20240923151814-23.png||height="563" width="1255"]]
766 -
767 -
768 -= 10.  Multiply Uplink in ChirpStack =
769 -
770 -
771 -(((
772 772  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
773 773  )))
774 774  
... ... @@ -808,7 +808,7 @@
808 808  [[image:image-20220601102430-1.png||height="508" width="1120"]]
809 809  
810 810  
811 -== 10.1  Solution ==
701 +== 9.1  Solution ==
812 812  
813 813  
814 814  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]]
... ... @@ -927,7 +927,7 @@
927 927  Finish.
928 928  
929 929  
930 -= 11.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
820 += 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
931 931  
932 932  
933 933  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.
... ... @@ -976,7 +976,7 @@
976 976  [[image:image-20221012173639-1.png||height="273" width="1206"]]
977 977  
978 978  
979 -= 12.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
869 += 11.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
980 980  
981 981  The following example is based on the built-in ChirpStack server for LPS8V2
982 982  
... ... @@ -983,7 +983,7 @@
983 983  [[image:image-20231201174640-1.png||height="584" width="1148"]]
984 984  
985 985  
986 -== **12.1 Generate API Tokens** ==
876 +== **11.1 Generate API Tokens** ==
987 987  
988 988  Access the built-in chirpstack , click "**API Key**" and "**Add API Key**".
989 989  
... ... @@ -996,7 +996,7 @@
996 996  [[image:image-20231204104802-1.png]]
997 997  
998 998  
999 -== **12.2 Template file** ==
889 +== **11.2 Template file** ==
1000 1000  
1001 1001  
1002 1002  Click on **"Template File Download"**, the user will download a **register.csv** template file,
... ... @@ -1018,7 +1018,7 @@
1018 1018  
1019 1019  
1020 1020  
1021 -== **12.3 Batch Register** ==
911 +== **11.3 Batch Register** ==
1022 1022  
1023 1023  [[image:image-20231204113136-11.png||height="362" width="1062"]]
1024 1024  
... ... @@ -1031,7 +1031,7 @@
1031 1031  
1032 1032  
1033 1033  
1034 -= 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
924 += 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1035 1035  
1036 1036  
1037 1037  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:
... ... @@ -1042,7 +1042,7 @@
1042 1042  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
1043 1043  
1044 1044  
1045 -== 13.1 Link Node-Red to Local ChirpStack ==
935 +== 12.1 Link Node-Red to Local ChirpStack ==
1046 1046  
1047 1047  
1048 1048  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"]]**
... ... @@ -1076,7 +1076,7 @@
1076 1076  [[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"]]
1077 1077  
1078 1078  
1079 -== 13.2 Check result. ==
969 +== 12.2 Check result. ==
1080 1080  
1081 1081  
1082 1082  Users can check logs by adding debug.
... ... @@ -1086,9 +1086,9 @@
1086 1086  [[image:image-20230529150923-1.png||height="424" width="1118"]]
1087 1087  
1088 1088  
1089 -= 14.  Trouble Shooting =
979 += 13.  Trouble Shooting =
1090 1090  
1091 -== 14.1  MIC Mismatch or MIC Failed ==
981 +== 13.1  MIC Mismatch or MIC Failed ==
1092 1092  
1093 1093  
1094 1094  (((
... ... @@ -1099,7 +1099,7 @@
1099 1099  Under normal circumstances, users need to change the APPKEY to solve this problem.
1100 1100  
1101 1101  
1102 -== 14.2  The node is very close to the gateway, but the signal is poor ==
992 +== 13.2  The node is very close to the gateway, but the signal is poor ==
1103 1103  
1104 1104  
1105 1105  If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
... ... @@ -1128,7 +1128,7 @@
1128 1128  **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]]**
1129 1129  
1130 1130  
1131 -== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1021 +== 13.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1132 1132  
1133 1133  
1134 1134  This is because the node's packets are retransmitted, and the Fcnt of these packets is the same.
... ... @@ -1159,7 +1159,7 @@
1159 1159  [[image:image-20240717092428-4.jpeg]]
1160 1160  
1161 1161  
1162 -== 14.4  How to get the log information of the node？ ==
1052 +== 13.4  How to get the log information of the node？ ==
1163 1163  
1164 1164  
1165 1165  ~1. Get information about a single node.
SN50v3-LB_协议008（AU915）(1).bin
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -89.2 KB
Content
image-20240923151814-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -115.8 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0