Skip to Content

Changes for page Notes for ChirpStack

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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +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.2 Schedule Downlink via API ==
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 Node
502 +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.3  Add decoder function in Chirpstack for downlink 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  
... ... @@ -633,27 +633,21 @@
633 633  [[image:image-20240923105725-1.png]]
634 634  
635 635  
636 -This example assumes that the user already has the prerequisites:
652 +This example assumes users already have:
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).
654 +* SN50v3-LB register on ChirpStack server already
655 +* The user is able to see the data on the ChirpStack server device page.
640 640  
641 641  (% class="wikigeneratedid" %)
642 - **AT command:** (% style="color:blue" %)**AT+CLASS=C**
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).
643 643  
644 644  (% class="wikigeneratedid" %)
645 - (% style="color:blue" %)**AT+DISFCNTCHECK=1**
661 +AT command: **AT+CLASS=C**
646 646  
647 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]]**
664 + **AT+DISFCNTCHECK=1**
649 649  
650 -* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
651 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  
... ... @@ -749,7 +749,7 @@
749 749  [[image:image-20240923151814-23.png||height="563" width="1255"]]
750 750  
751 751  
752 -= 10.  Multiply Uplink in ChirpStack =
762 += 9.  Multiply Uplink in ChirpStack =
753 753  
754 754  
755 755  (((
... ... @@ -792,7 +792,7 @@
792 792  [[image:image-20220601102430-1.png||height="508" width="1120"]]
793 793  
794 794  
795 -== 10.1  Solution ==
805 +== 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 -= 11.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
924 += 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 -= 12.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
973 += 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 -== **12.1 Generate API Tokens** ==
980 +== **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 -== **12.2 Template file** ==
993 +== **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 -== **12.3 Batch Register** ==
1015 +== **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 -= 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1028 += 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 -== 13.1 Link Node-Red to Local ChirpStack ==
1039 +== 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 -== 13.2 Check result. ==
1073 +== 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 -= 14.  Trouble Shooting =
1083 += 13.  Trouble Shooting =
1074 1074  
1075 -== 14.1  MIC Mismatch or MIC Failed ==
1085 +== 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 -== 14.2  The node is very close to the gateway, but the signal is poor ==
1096 +== 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 -== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1125 +== 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 -== 14.4  How to get the log information of the node？ ==
1156 +== 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