Skip to Content

Changes for page Notes for ChirpStack

Last modified by Xiaoling on 2025/03/22 09:21
From version 222.1
edited by Kilight Cao
on 2024/09/23 10:57
Change comment: Uploaded new attachment "image-20240923105725-1.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
... ... @@ -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,49 +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  
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.
634 +
635 +[[image:image-20240923105725-1.png]]
636 +
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 +
632 632  (% class="wikigeneratedid" %)
633 -= 9.  Chirpstack Multicast Configuration =
644 + **AT command:** (% style="color:blue" %)**AT+CLASS=C**
634 634  
646 +(% class="wikigeneratedid" %)
647 + (% style="color:blue" %)**AT+DISFCNTCHECK=1**
635 635  
636 -== 9.1  Introduction ==
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]]**
637 637  
638 -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.
652 +* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
639 639  
640 -Multicast can be used for the following device-classes:
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]]
641 641  
642 -* Class-B
643 -* Class-C
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]]
644 644  
645 645  
646 -== 9.2 Example to configure chirpstack Multicast ==
659 +=== Step 1. Create the multicast group ===
647 647  
648 648  
649 -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.
662 +Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915
650 650  
664 +[[image:image-20240923141847-3.png||height="620" width="1207"]]
651 651  
652 652  
653 -= 9.  Multiply Uplink in ChirpStack =
667 +Enter the Multicast address,Multicast network session key,Multicast application session key.
654 654  
669 +Use the default LoRaWAN settings, as below:
655 655  
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" %)
656 656  (((
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 +(((
657 657  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
658 658  )))
659 659  
... ... @@ -693,7 +693,7 @@
693 693  [[image:image-20220601102430-1.png||height="508" width="1120"]]
694 694  
695 695  
696 -== 9.1  Solution ==
797 +== 10.1  Solution ==
697 697  
698 698  
699 699  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]]
... ... @@ -812,7 +812,7 @@
812 812  Finish.
813 813  
814 814  
815 -= 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. =
816 816  
817 817  
818 818  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.
... ... @@ -861,7 +861,7 @@
861 861  [[image:image-20221012173639-1.png||height="273" width="1206"]]
862 862  
863 863  
864 -= 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 =
865 865  
866 866  The following example is based on the built-in ChirpStack server for LPS8V2
867 867  
... ... @@ -868,7 +868,7 @@
868 868  [[image:image-20231201174640-1.png||height="584" width="1148"]]
869 869  
870 870  
871 -== **11.1 Generate API Tokens** ==
972 +== **12.1 Generate API Tokens** ==
872 872  
873 873  Access the built-in chirpstack , click "**API Key**" and "**Add API Key**".
874 874  
... ... @@ -881,7 +881,7 @@
881 881  [[image:image-20231204104802-1.png]]
882 882  
883 883  
884 -== **11.2 Template file** ==
985 +== **12.2 Template file** ==
885 885  
886 886  
887 887  Click on **"Template File Download"**, the user will download a **register.csv** template file,
... ... @@ -903,7 +903,7 @@
903 903  
904 904  
905 905  
906 -== **11.3 Batch Register** ==
1007 +== **12.3 Batch Register** ==
907 907  
908 908  [[image:image-20231204113136-11.png||height="362" width="1062"]]
909 909  
... ... @@ -916,7 +916,7 @@
916 916  
917 917  
918 918  
919 -= 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1020 += 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
920 920  
921 921  
922 922  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:
... ... @@ -927,7 +927,7 @@
927 927  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
928 928  
929 929  
930 -== 12.1 Link Node-Red to Local ChirpStack ==
1031 +== 13.1 Link Node-Red to Local ChirpStack ==
931 931  
932 932  
933 933  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"]]**
... ... @@ -961,7 +961,7 @@
961 961  [[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"]]
962 962  
963 963  
964 -== 12.2 Check result. ==
1065 +== 13.2 Check result. ==
965 965  
966 966  
967 967  Users can check logs by adding debug.
... ... @@ -971,9 +971,9 @@
971 971  [[image:image-20230529150923-1.png||height="424" width="1118"]]
972 972  
973 973  
974 -= 13.  Trouble Shooting =
1075 += 14.  Trouble Shooting =
975 975  
976 -== 13.1  MIC Mismatch or MIC Failed ==
1077 +== 14.1  MIC Mismatch or MIC Failed ==
977 977  
978 978  
979 979  (((
... ... @@ -984,7 +984,7 @@
984 984  Under normal circumstances, users need to change the APPKEY to solve this problem.
985 985  
986 986  
987 -== 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 ==
988 988  
989 989  
990 990  If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
... ... @@ -1013,7 +1013,7 @@
1013 1013  **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]]**
1014 1014  
1015 1015  
1016 -== 13.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1117 +== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1017 1017  
1018 1018  
1019 1019  This is because the node's packets are retransmitted, and the Fcnt of these packets is the same.
... ... @@ -1044,7 +1044,7 @@
1044 1044  [[image:image-20240717092428-4.jpeg]]
1045 1045  
1046 1046  
1047 -== 13.4  How to get the log information of the node？ ==
1148 +== 14.4  How to get the log information of the node？ ==
1048 1048  
1049 1049  
1050 1050  ~1. Get information about a single node.
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-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