Changes for page Notes for ChirpStack
Last modified by Xiaoling on 2025/03/22 09:21
<
edited by Kilight Cao
on 2024/09/23 15:18
on 2024/09/23 15:18
Change comment:
Uploaded new attachment "image-20240923151814-23.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Kilight - Content
-
... ... @@ -466,12 +466,13 @@ 466 466 467 467 = 8. Downlink = 468 468 469 -== 8.1 Schedule Downlink via Web UI == 470 470 470 +=== 8.1 Chirpstack Downlink Note === 471 471 472 -=== Select HEX format for downlink === 473 473 473 +==== Select HEX format for downlink ==== 474 474 475 + 475 475 (% style="color:red" %)**Note: The end node user manual provides HEX format of the downlink commands, so users can directly select HEX format downlink.** 476 476 477 477 ... ... @@ -495,10 +495,10 @@ 495 495 **Make sure the RX2DR is the same in the end node** 496 496 497 497 498 -== 8. 2Schedule DownlinkviaAPI==499 +== 8.3 Loraserver Downlink Note == 499 499 500 500 501 -User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End Node502 +User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End 502 502 503 503 ((( 504 504 **Below is examples:** ... ... @@ -517,6 +517,7 @@ 517 517 ((( 518 518 **MQTT Connect to ChirpStack** 519 519 521 + 520 520 521 521 ))) 522 522 ... ... @@ -609,10 +609,24 @@ 609 609 ))) 610 610 611 611 612 -== 8. 3Add decoderfunction in Chirpstack fordownlink message==614 +== 8.4 Add the decode function in Chirpstack for the payload == 613 613 614 614 617 +User enters the payload code according to the steps. 615 615 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 + 616 616 = 9. Chirpstack Multicast Configuration = 617 617 618 618 ... ... @@ -628,131 +628,21 @@ 628 628 == 9.2 Example to configure chirpstack Multicast == 629 629 630 630 631 -This section illustrates how to configure ChirpStack Multicast. Below is the network structure, we use our LPS8v2 as the LoRaWAN gateway and twoSN50v3-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. 632 632 633 633 [[image:image-20240923105725-1.png]] 634 634 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: 635 635 636 -This example assumes that the user already has the prerequisites: 637 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 657 === Step 1. Create the multicast group === 658 658 659 659 660 -Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915 661 661 662 - [[image:image-20240923141847-3.png||height="620"width="1207"]]658 += 9. Multiply Uplink in ChirpStack = 663 663 664 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" %) 732 732 ((( 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 -((( 756 756 nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data. 757 757 ))) 758 758 ... ... @@ -792,7 +792,7 @@ 792 792 [[image:image-20220601102430-1.png||height="508" width="1120"]] 793 793 794 794 795 -== 10.1 Solution ==701 +== 9.1 Solution == 796 796 797 797 798 798 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]] ... ... @@ -911,7 +911,7 @@ 911 911 Finish. 912 912 913 913 914 -= 1 1. 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. = 915 915 916 916 917 917 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. ... ... @@ -960,7 +960,7 @@ 960 960 [[image:image-20221012173639-1.png||height="273" width="1206"]] 961 961 962 962 963 -= 1 2. 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 = 964 964 965 965 The following example is based on the built-in ChirpStack server for LPS8V2 966 966 ... ... @@ -967,7 +967,7 @@ 967 967 [[image:image-20231201174640-1.png||height="584" width="1148"]] 968 968 969 969 970 -== **1 2.1 Generate API Tokens** ==876 +== **11.1 Generate API Tokens** == 971 971 972 972 Access the built-in chirpstack , click "**API Key**" and "**Add API Key**". 973 973 ... ... @@ -980,7 +980,7 @@ 980 980 [[image:image-20231204104802-1.png]] 981 981 982 982 983 -== **1 2.2 Template file** ==889 +== **11.2 Template file** == 984 984 985 985 986 986 Click on **"Template File Download"**, the user will download a **register.csv** template file, ... ... @@ -1002,7 +1002,7 @@ 1002 1002 1003 1003 1004 1004 1005 -== **1 2.3 Batch Register** ==911 +== **11.3 Batch Register** == 1006 1006 1007 1007 [[image:image-20231204113136-11.png||height="362" width="1062"]] 1008 1008 ... ... @@ -1015,7 +1015,7 @@ 1015 1015 1016 1016 1017 1017 1018 -= 1 3. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =924 += 12. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 = 1019 1019 1020 1020 1021 1021 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: ... ... @@ -1026,7 +1026,7 @@ 1026 1026 Below are the steps to plot the sensor data on LPS8v2 Node-Red. 1027 1027 1028 1028 1029 -== 1 3.1 Link Node-Red to Local ChirpStack ==935 +== 12.1 Link Node-Red to Local ChirpStack == 1030 1030 1031 1031 1032 1032 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"]]** ... ... @@ -1060,7 +1060,7 @@ 1060 1060 [[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"]] 1061 1061 1062 1062 1063 -== 1 3.2 Check result. ==969 +== 12.2 Check result. == 1064 1064 1065 1065 1066 1066 Users can check logs by adding debug. ... ... @@ -1070,9 +1070,9 @@ 1070 1070 [[image:image-20230529150923-1.png||height="424" width="1118"]] 1071 1071 1072 1072 1073 -= 1 4. Trouble Shooting =979 += 13. Trouble Shooting = 1074 1074 1075 -== 1 4.1 MIC Mismatch or MIC Failed ==981 +== 13.1 MIC Mismatch or MIC Failed == 1076 1076 1077 1077 1078 1078 ((( ... ... @@ -1083,7 +1083,7 @@ 1083 1083 Under normal circumstances, users need to change the APPKEY to solve this problem. 1084 1084 1085 1085 1086 -== 1 4.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 == 1087 1087 1088 1088 1089 1089 If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink ... ... @@ -1112,7 +1112,7 @@ 1112 1112 **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]]** 1113 1113 1114 1114 1115 -== 1 4.3 ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==1021 +== 13.3 ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" == 1116 1116 1117 1117 1118 1118 This is because the node's packets are retransmitted, and the Fcnt of these packets is the same. ... ... @@ -1143,7 +1143,7 @@ 1143 1143 [[image:image-20240717092428-4.jpeg]] 1144 1144 1145 1145 1146 -== 1 4.4 How to get the log information of the node? ==1052 +== 13.4 How to get the log information of the node? == 1147 1147 1148 1148 1149 1149 ~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