Changes for page Notes for ChirpStack

Last modified by Kilight Cao on 2024/09/24 15:23
<
From version < 243.1 >
edited by Kilight Cao
on 2024/09/24 15:05
To version < 232.1 >
edited by Kilight Cao
on 2024/09/23 14:55
>
Change comment: Uploaded new attachment "image-20240923145506-12.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -644,125 +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 users already have:
653 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 667  === Step 1. Create the multicast group ===
668 668  
669 669  
670 -Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915
671 671  
672 -[[image:image-20240923141847-3.png||height="620" width="1207"]]
658 += 9.  Multiply Uplink in ChirpStack =
673 673  
674 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 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 -
762 -= 10.  Multiply Uplink in ChirpStack =
763 -
764 -
765 -(((
766 766  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
767 767  )))
768 768  
... ... @@ -802,7 +802,7 @@
802 802  [[image:image-20220601102430-1.png||height="508" width="1120"]]
803 803  
804 804  
805 -== 10.1  Solution ==
701 +== 9.1  Solution ==
806 806  
807 807  
808 808  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]]
... ... @@ -921,7 +921,7 @@
921 921  Finish.
922 922  
923 923  
924 -= 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. =
925 925  
926 926  
927 927  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.
... ... @@ -970,7 +970,7 @@
970 970  [[image:image-20221012173639-1.png||height="273" width="1206"]]
971 971  
972 972  
973 -= 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 =
974 974  
975 975  The following example is based on the built-in ChirpStack server for LPS8V2
976 976  
... ... @@ -977,7 +977,7 @@
977 977  [[image:image-20231201174640-1.png||height="584" width="1148"]]
978 978  
979 979  
980 -== **12.1 Generate API Tokens** ==
876 +== **11.1 Generate API Tokens** ==
981 981  
982 982  Access the built-in chirpstack , click "**API Key**" and "**Add API Key**".
983 983  
... ... @@ -990,7 +990,7 @@
990 990  [[image:image-20231204104802-1.png]]
991 991  
992 992  
993 -== **12.2 Template file** ==
889 +== **11.2 Template file** ==
994 994  
995 995  
996 996  Click on **"Template File Download"**, the user will download a **register.csv** template file,
... ... @@ -1012,7 +1012,7 @@
1012 1012  
1013 1013  
1014 1014  
1015 -== **12.3 Batch Register** ==
911 +== **11.3 Batch Register** ==
1016 1016  
1017 1017  [[image:image-20231204113136-11.png||height="362" width="1062"]]
1018 1018  
... ... @@ -1025,7 +1025,7 @@
1025 1025  
1026 1026  
1027 1027  
1028 -= 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
924 += 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1029 1029  
1030 1030  
1031 1031  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:
... ... @@ -1036,7 +1036,7 @@
1036 1036  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
1037 1037  
1038 1038  
1039 -== 13.1 Link Node-Red to Local ChirpStack ==
935 +== 12.1 Link Node-Red to Local ChirpStack ==
1040 1040  
1041 1041  
1042 1042  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"]]**
... ... @@ -1070,7 +1070,7 @@
1070 1070  [[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"]]
1071 1071  
1072 1072  
1073 -== 13.2 Check result. ==
969 +== 12.2 Check result. ==
1074 1074  
1075 1075  
1076 1076  Users can check logs by adding debug.
... ... @@ -1080,9 +1080,9 @@
1080 1080  [[image:image-20230529150923-1.png||height="424" width="1118"]]
1081 1081  
1082 1082  
1083 -= 14.  Trouble Shooting =
979 += 13.  Trouble Shooting =
1084 1084  
1085 -== 14.1  MIC Mismatch or MIC Failed ==
981 +== 13.1  MIC Mismatch or MIC Failed ==
1086 1086  
1087 1087  
1088 1088  (((
... ... @@ -1093,7 +1093,7 @@
1093 1093  Under normal circumstances, users need to change the APPKEY to solve this problem.
1094 1094  
1095 1095  
1096 -== 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 ==
1097 1097  
1098 1098  
1099 1099  If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
... ... @@ -1122,7 +1122,7 @@
1122 1122  **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]]**
1123 1123  
1124 1124  
1125 -== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1021 +== 13.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1126 1126  
1127 1127  
1128 1128  This is because the node's packets are retransmitted, and the Fcnt of these packets is the same.
... ... @@ -1153,7 +1153,7 @@
1153 1153  [[image:image-20240717092428-4.jpeg]]
1154 1154  
1155 1155  
1156 -== 14.4  How to get the log information of the node？ ==
1052 +== 13.4  How to get the log information of the node？ ==
1157 1157  
1158 1158  
1159 1159  ~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-20240923145520-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -76.6 KB
Content
image-20240923145624-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -52.9 KB
Content
image-20240923145945-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -61.4 KB
Content
image-20240923145949-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -61.4 KB
Content
image-20240923145953-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -61.4 KB
Content
image-20240923151236-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -70.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-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0