Skip to Content

Changes for page Notes for ChirpStack

Last modified by Xiaoling on 2025/03/22 09:21
From version 220.1
edited by Kilight Cao
on 2024/08/31 15:44
Change comment: There is no comment for this version
To version 246.1
edited by Xiaoling
on 2025/03/22 09:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
Content
... ... @@ -466,13 +466,12 @@
466 466  
467 467  = 8.  Downlink =
468 468  
469 +== 8.1 Schedule Downlink via Web UI ==
469 469  
470 -=== 8.1 Chirpstack Downlink Note ===
471 471  
472 +=== Select HEX format for downlink ===
472 472  
473 -==== Select HEX format for downlink ====
474 474  
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.**
477 477  
478 478  
... ... @@ -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 ==
498 +== 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
501 +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,150 @@
611 611  )))
612 612  
613 613  
614 -== 8.4  Add the decode function in Chirpstack for the payload ==
612 +== 8.3  Add decoder function in Chirpstack for downlink message ==
615 615  
616 616  
617 -User enters the payload code according to the steps.
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]]**
616 += 9.  Chirpstack Multicast Configuration =
620 620  
621 -[[image:image-20220531173754-15.png||height="474" width="1334"]]
622 622  
619 +== 9.1  Introduction ==
623 623  
624 -[[image:image-20220531173856-16.png]]
621 +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  
623 +Multicast can be used for the following device-classes:
626 626  
627 -[[image:image-20220531174120-20.png]]
625 +* Class-B
626 +* Class-C
628 628  
629 -[[image:image-20220531174046-19.png]]
628 +== 9.2  Example to configure chirpstack Multicast ==
630 630  
631 631  
632 -= 9.  Multiply Uplink in ChirpStack =
631 +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  
633 +[[image:image-20240923105725-1.png]]
634 634  
635 +
636 +This example assumes that the user already has the prerequisites:
637 +
638 +* (% 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.
639 +* (% style="color:blue" %)**SN50v3-LB Configure:   **(%%)Enable CLASS C and DISFCNTCHECK(The downlink fcnt is not compared with the fcnt of the node).
640 +
641 +(% class="wikigeneratedid" %)
642 + **AT command:** (% style="color:blue" %)**AT+CLASS=C**
643 +
644 +(% class="wikigeneratedid" %)
645 + (% style="color:blue" %)**AT+DISFCNTCHECK=1**
646 +
647 +(% class="wikigeneratedid" %)
648 +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]]**
649 +
650 +* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
651 +
652 +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]]
653 +
654 +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]]
655 +
656 +
657 +=== Step 1. Create the multicast group ===
658 +
659 +
660 +Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915
661 +
662 +[[image:image-20240923141847-3.png||height="620" width="1207"]]
663 +
664 +
665 +Enter the Multicast address,Multicast network session key,Multicast application session key.
666 +
667 +Use the default LoRaWAN settings, as below:
668 +
669 +* EU868: 869525000hz, DR0
670 +
671 +* US915: 923300000hz, DR8
672 +
673 +* CN470: 505300000hz, DR0
674 +
675 +* AU915: 923300000hz, DR8
676 +
677 +* AS923: 923200000hz, DR2
678 +
679 +* KR920: 921900000hz, DR0
680 +
681 +* IN865: 866550000hz, DR2
682 +
683 +* RU864: 869100000hz, DR0
684 +
685 +Group type: **Class-C**
686 +
687 +Class-C scheduling type : **Delay**
688 +
689 +[[image:image-20240923142446-5.png||height="720" width="1208"]]
690 +
691 +
692 +=== Step 2. Add gateways and devices to the multicast group ===
693 +
694 +
695 +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**.
696 +
697 +[[image:image-20240923144335-6.png||height="619" width="1209"]]
698 +
699 +[[image:image-20240923144418-7.png||height="572" width="1206"]]
700 +
701 +
702 +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
703 +
704 +[[image:image-20240923144749-9.png||height="623" width="1211"]]
705 +
706 +
707 +Access the multicast group to check whether two SN50V3-LBs and gateways are added successfully
708 +
709 +[[image:image-20240923145148-10.png||height="601" width="1218"]]
710 +
711 +
712 +=== Step 3. Use the API for multicast Downlink ===
713 +
714 +
715 +To use API Downlink, user first need to generate an API key
716 +
717 +[[image:image-20240923145624-18.png||height="429" width="1211"]]
718 +
719 +[[image:image-20240923145520-16.png||height="422" width="1212"]]
720 +
721 +
722 +For example:**[[https:~~/~~/www.chirpstack.io/docs/chirpstack/api/index.html>>url:https://www.chirpstack.io/docs/chirpstack/api/index.html]]**
723 +
724 +[[image:image-20240923145953-21.png||height="808" width="1222"]]
725 +
726 +
727 +Users can access the Linux console of the gateway via SSH, and then use the curl command to multicast Downlink
728 +
729 +The format is as follows:
730 +
731 +(% class="box infomessage" %)
635 635  (((
733 +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 '{
734 + "queueItem": {
735 + "data": "EjRWeA==",
736 + "fCnt": 0,
737 + "fPort": 123
738 + }
739 +}'
740 +)))
741 +
742 +In the command,eyJ........._2v4UYPV0w is the API key, which can be obtained from the Chirpstack server and the data format is base64,
743 +
744 +
745 +=== Result ===
746 +
747 +Connecting to the SN50v3-LB using the serial USB-TTL port can check that two SN50v3-LBs are receiving Downlink at the same time
748 +
749 +[[image:image-20240923151814-23.png||height="563" width="1255"]]
750 +
751 +
752 += 10.  Multiply Uplink in ChirpStack =
753 +
754 +
755 +(((
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 ==
795 +== 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. =
914 += 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 =
963 += 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** ==
970 +== **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** ==
983 +== **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** ==
1005 +== **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 =
1018 += 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 ==
1029 +== 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. ==
1063 +== 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 =
1073 += 14.  Trouble Shooting =
954 954  
955 -== 13.1  MIC Mismatch or MIC Failed ==
1075 +== 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 ==
1086 +== 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" ==
1115 +== 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.
... ... @@ -1023,7 +1023,7 @@
1023 1023  [[image:image-20240717092428-4.jpeg]]
1024 1024  
1025 1025  
1026 -== 13.4  How to get the log information of the node？ ==
1146 +== 14.4  How to get the log information of the node？ ==
1027 1027  
1028 1028  
1029 1029  ~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-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