Changes for page Notes for ChirpStack

Last modified by Xiaoling on 2025/03/22 09:21
<
From version < 245.2 >
edited by Xiaoling
on 2025/03/22 09:12
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -467,10 +467,10 @@
467 467  = 8.  Downlink =
468 468  
469 469  
470 -== 8.1 Schedule Downlink via Web UI ==
470 +=== 8.1 Chirpstack Downlink Note ===
471 471  
472 472  
473 -=== Select HEX format for downlink ===
473 +==== Select HEX format for downlink ====
474 474  
475 475  
476 476  (% style="color:red" %)**Note: The end node user manual provides HEX format of the downlink commands, so users can directly select HEX format downlink.**
... ... @@ -496,10 +496,10 @@
496 496  **Make sure the RX2DR is the same in the end node**
497 497  
498 498  
499 -== 8.2 Schedule Downlink via API ==
499 +== 8.3  Loraserver Downlink Note ==
500 500  
501 501  
502 -User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End Node
502 +User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
503 503  
504 504  (((
505 505  **Below is examples:**
... ... @@ -518,6 +518,7 @@
518 518  (((
519 519  **MQTT Connect to ChirpStack**
520 520  
521 +
521 521  
522 522  )))
523 523  
... ... @@ -610,10 +610,24 @@
610 610  )))
611 611  
612 612  
613 -== 8.3  Add decoder function in Chirpstack for downlink message ==
614 +== 8.4  Add the decode function in Chirpstack for the payload ==
614 614  
615 615  
617 +User enters the payload code according to the steps.
616 616  
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]]**
620 +
621 +[[image:image-20220531173754-15.png||height="474" width="1334"]]
622 +
623 +
624 +[[image:image-20220531173856-16.png]]
625 +
626 +
627 +[[image:image-20220531174120-20.png]]
628 +
629 +[[image:image-20220531174046-19.png]]
630 +
631 +
617 617  = 9.  Chirpstack Multicast Configuration =
618 618  
619 619  
... ... @@ -629,131 +629,21 @@
629 629  == 9.2  Example to configure chirpstack Multicast ==
630 630  
631 631  
632 -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.
633 633  
634 634  [[image:image-20240923105725-1.png]]
635 635  
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:
636 636  
637 -This example assumes that the user already has the prerequisites:
638 638  
639 -* (% 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.
640 -* (% style="color:blue" %)**SN50v3-LB Configure:   **(%%)Enable CLASS C and DISFCNTCHECK(The downlink fcnt is not compared with the fcnt of the node).
641 -
642 -(% class="wikigeneratedid" %)
643 - **AT command:** (% style="color:blue" %)**AT+CLASS=C**
644 -
645 -(% class="wikigeneratedid" %)
646 - (% style="color:blue" %)**AT+DISFCNTCHECK=1**
647 -
648 -(% class="wikigeneratedid" %)
649 -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]]**
650 -
651 -* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
652 -
653 -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]]
654 -
655 -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]]
656 -
657 -
658 658  === Step 1. Create the multicast group ===
659 659  
660 660  
661 -Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915
662 662  
663 -[[image:image-20240923141847-3.png||height="620" width="1207"]]
658 += 9.  Multiply Uplink in ChirpStack =
664 664  
665 665  
666 -Enter the Multicast address,Multicast network session key,Multicast application session key.
667 -
668 -Use the default LoRaWAN settings, as below:
669 -
670 -* EU868: 869525000hz, DR0
671 -
672 -* US915: 923300000hz, DR8
673 -
674 -* CN470: 505300000hz, DR0
675 -
676 -* AU915: 923300000hz, DR8
677 -
678 -* AS923: 923200000hz, DR2
679 -
680 -* KR920: 921900000hz, DR0
681 -
682 -* IN865: 866550000hz, DR2
683 -
684 -* RU864: 869100000hz, DR0
685 -
686 -Group type: **Class-C**
687 -
688 -Class-C scheduling type : **Delay**
689 -
690 -[[image:image-20240923142446-5.png||height="720" width="1208"]]
691 -
692 -
693 -=== Step 2. Add gateways and devices to the multicast group ===
694 -
695 -
696 -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**.
697 -
698 -[[image:image-20240923144335-6.png||height="619" width="1209"]]
699 -
700 -[[image:image-20240923144418-7.png||height="572" width="1206"]]
701 -
702 -
703 -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
704 -
705 -[[image:image-20240923144749-9.png||height="623" width="1211"]]
706 -
707 -
708 -Access the multicast group to check whether two SN50V3-LBs and gateways are added successfully
709 -
710 -[[image:image-20240923145148-10.png||height="601" width="1218"]]
711 -
712 -
713 -=== Step 3. Use the API for multicast Downlink ===
714 -
715 -
716 -To use API Downlink, user first need to generate an API key
717 -
718 -[[image:image-20240923145624-18.png||height="429" width="1211"]]
719 -
720 -[[image:image-20240923145520-16.png||height="422" width="1212"]]
721 -
722 -
723 -For example:**[[https:~~/~~/www.chirpstack.io/docs/chirpstack/api/index.html>>url:https://www.chirpstack.io/docs/chirpstack/api/index.html]]**
724 -
725 -[[image:image-20240923145953-21.png||height="808" width="1222"]]
726 -
727 -
728 -Users can access the Linux console of the gateway via SSH, and then use the curl command to multicast Downlink
729 -
730 -The format is as follows:
731 -
732 -(% class="box infomessage" %)
733 733  (((
734 -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 '{
735 - "queueItem": {
736 - "data": "EjRWeA==",
737 - "fCnt": 0,
738 - "fPort": 123
739 - }
740 -}'
741 -)))
742 -
743 -In the command,eyJ........._2v4UYPV0w is the API key, which can be obtained from the Chirpstack server and the data format is base64,
744 -
745 -
746 -=== Result ===
747 -
748 -Connecting to the SN50v3-LB using the serial USB-TTL port can check that two SN50v3-LBs are receiving Downlink at the same time
749 -
750 -[[image:image-20240923151814-23.png||height="563" width="1255"]]
751 -
752 -
753 -= 10.  Multiply Uplink in ChirpStack =
754 -
755 -
756 -(((
757 757  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
758 758  )))
759 759  
... ... @@ -793,7 +793,7 @@
793 793  [[image:image-20220601102430-1.png||height="508" width="1120"]]
794 794  
795 795  
796 -== 10.1  Solution ==
701 +== 9.1  Solution ==
797 797  
798 798  
799 799  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]]
... ... @@ -912,7 +912,7 @@
912 912  Finish.
913 913  
914 914  
915 -= 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. =
916 916  
917 917  
918 918  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.
... ... @@ -961,7 +961,7 @@
961 961  [[image:image-20221012173639-1.png||height="273" width="1206"]]
962 962  
963 963  
964 -= 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 =
965 965  
966 966  The following example is based on the built-in ChirpStack server for LPS8V2
967 967  
... ... @@ -968,7 +968,7 @@
968 968  [[image:image-20231201174640-1.png||height="584" width="1148"]]
969 969  
970 970  
971 -== **12.1 Generate API Tokens** ==
876 +== **11.1 Generate API Tokens** ==
972 972  
973 973  Access the built-in chirpstack , click "**API Key**" and "**Add API Key**".
974 974  
... ... @@ -981,7 +981,7 @@
981 981  [[image:image-20231204104802-1.png]]
982 982  
983 983  
984 -== **12.2 Template file** ==
889 +== **11.2 Template file** ==
985 985  
986 986  
987 987  Click on **"Template File Download"**, the user will download a **register.csv** template file,
... ... @@ -1003,7 +1003,7 @@
1003 1003  
1004 1004  
1005 1005  
1006 -== **12.3 Batch Register** ==
911 +== **11.3 Batch Register** ==
1007 1007  
1008 1008  [[image:image-20231204113136-11.png||height="362" width="1062"]]
1009 1009  
... ... @@ -1016,7 +1016,7 @@
1016 1016  
1017 1017  
1018 1018  
1019 -= 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
924 += 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1020 1020  
1021 1021  
1022 1022  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:
... ... @@ -1027,7 +1027,7 @@
1027 1027  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
1028 1028  
1029 1029  
1030 -== 13.1 Link Node-Red to Local ChirpStack ==
935 +== 12.1 Link Node-Red to Local ChirpStack ==
1031 1031  
1032 1032  
1033 1033  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"]]**
... ... @@ -1061,7 +1061,7 @@
1061 1061  [[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"]]
1062 1062  
1063 1063  
1064 -== 13.2 Check result. ==
969 +== 12.2 Check result. ==
1065 1065  
1066 1066  
1067 1067  Users can check logs by adding debug.
... ... @@ -1071,9 +1071,9 @@
1071 1071  [[image:image-20230529150923-1.png||height="424" width="1118"]]
1072 1072  
1073 1073  
1074 -= 14.  Trouble Shooting =
979 += 13.  Trouble Shooting =
1075 1075  
1076 -== 14.1  MIC Mismatch or MIC Failed ==
981 +== 13.1  MIC Mismatch or MIC Failed ==
1077 1077  
1078 1078  
1079 1079  (((
... ... @@ -1084,7 +1084,7 @@
1084 1084  Under normal circumstances, users need to change the APPKEY to solve this problem.
1085 1085  
1086 1086  
1087 -== 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 ==
1088 1088  
1089 1089  
1090 1090  If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
... ... @@ -1113,7 +1113,7 @@
1113 1113  **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]]**
1114 1114  
1115 1115  
1116 -== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1021 +== 13.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1117 1117  
1118 1118  
1119 1119  This is because the node's packets are retransmitted, and the Fcnt of these packets is the same.
... ... @@ -1144,7 +1144,7 @@
1144 1144  [[image:image-20240717092428-4.jpeg]]
1145 1145  
1146 1146  
1147 -== 14.4  How to get the log information of the node？ ==
1052 +== 13.4  How to get the log information of the node？ ==
1148 1148  
1149 1149  
1150 1150  ~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