Changes for page Notes for ChirpStack

Last modified by Xiaoling on 2025/03/22 09:21

From 238.1 to 239.1

From version 239.1

edited by Kilight Cao
on 2024/09/23 15:18

Change comment: Uploaded new attachment "image-20240923151814-23.png", version {1}

To version 246.1

edited by Xiaoling
on 2025/03/22 09:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- SN50v3-LB_协议008（AU915）(1).bin

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Kilight
++XWiki.Xiaoling

Content

@@ -466,13 +466,12 @@
  = 8.  Downlink =
++== 8.1 Schedule Downlink via Web UI ==
--=== 8.1 Chirpstack Downlink Note ===
++=== Select HEX format for downlink ===
--==== Select HEX format for downlink ====
--
  (% 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 @@
  **Make sure the RX2DR is the same in the end node**
--== 8.3  Loraserver Downlink Note ==
++== 8.2 Schedule Downlink via API ==
--User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
++User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End Node
  (((
  **Below is examples:**
@@ -518,7 +518,6 @@
  (((
  **MQTT Connect to ChirpStack**
--
  )))
@@ -611,24 +611,10 @@
  )))
--== 8.4  Add the decode function in Chirpstack for the payload ==
++== 8.3  Add decoder function in Chirpstack for downlink message ==
--User enters the payload code according to the steps.
--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]]**
--
--[[image:image-20220531173754-15.png||height="474" width="1334"]]
--
--
--[[image:image-20220531173856-16.png]]
--
--
--[[image:image-20220531174120-20.png]]
--
--[[image:image-20220531174046-19.png]]
--
--
  = 9.  Chirpstack Multicast Configuration =
@@ -644,21 +644,131 @@
  == 9.2  Example to configure chirpstack Multicast ==
--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.
++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.
  [[image:image-20240923105725-1.png]]
--The LPS8V2 is already set to connect to Chirpstack. So what we need to do now is only configure register these devices to Chirpstack:
++This example assumes that the user already has the prerequisites:
++* (% 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.
++* (% style="color:blue" %)**SN50v3-LB Configure:   **(%%)Enable CLASS C and DISFCNTCHECK(The downlink fcnt is not compared with the fcnt of the node).
++
++(% class="wikigeneratedid" %)
++          **AT command:** (% style="color:blue" %)**AT+CLASS=C**
++
++(% class="wikigeneratedid" %)
++                                  (% style="color:blue" %)**AT+DISFCNTCHECK=1**
++
++(% class="wikigeneratedid" %)
++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]]**
++
++* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
++
++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]]
++
++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]]
++
++
  === Step 1. Create the multicast group ===
++Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915
--= 9.  Multiply Uplink in ChirpStack =
++[[image:image-20240923141847-3.png||height="620" width="1207"]]
++Enter the Multicast address,Multicast network session key,Multicast application session key.
++
++Use the default LoRaWAN settings, as below:
++
++* EU868: 869525000hz, DR0
++
++* US915: 923300000hz, DR8
++
++* CN470: 505300000hz, DR0
++
++* AU915: 923300000hz, DR8
++
++* AS923: 923200000hz, DR2
++
++* KR920: 921900000hz, DR0
++
++* IN865: 866550000hz, DR2
++
++* RU864: 869100000hz, DR0
++
++Group type: **Class-C**
++
++Class-C scheduling type : **Delay**
++
++[[image:image-20240923142446-5.png||height="720" width="1208"]]
++
++
++=== Step 2. Add gateways and devices to the multicast group ===
++
++
++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**.
++
++[[image:image-20240923144335-6.png||height="619" width="1209"]]
++
++[[image:image-20240923144418-7.png||height="572" width="1206"]]
++
++
++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
++
++[[image:image-20240923144749-9.png||height="623" width="1211"]]
++
++
++Access the multicast group to check whether two SN50V3-LBs and gateways are added successfully
++
++[[image:image-20240923145148-10.png||height="601" width="1218"]]
++
++
++=== Step 3. Use the API for multicast Downlink ===
++
++
++To use API Downlink, user first need to generate an API key
++
++[[image:image-20240923145624-18.png||height="429" width="1211"]]
++
++[[image:image-20240923145520-16.png||height="422" width="1212"]]
++
++
++For example:**[[https:~~/~~/www.chirpstack.io/docs/chirpstack/api/index.html>>url:https://www.chirpstack.io/docs/chirpstack/api/index.html]]**
++
++[[image:image-20240923145953-21.png||height="808" width="1222"]]
++
++
++Users can access the Linux console of the gateway via SSH, and then use the curl command to multicast Downlink
++
++The format is as follows:
++
++(% class="box infomessage" %)
  (((
++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 '{
++   "queueItem": {
++    "data": "EjRWeA==",
++    "fCnt": 0,
++    "fPort": 123
++  }
++}'
++)))
++
++In the command,eyJ........._2v4UYPV0w is the API key, which can be obtained from the Chirpstack server and the data format is base64,
++
++
++=== Result ===
++
++Connecting to the SN50v3-LB using the serial USB-TTL port can check that two SN50v3-LBs are receiving Downlink at the same time
++
++[[image:image-20240923151814-23.png||height="563" width="1255"]]
++
++
++= 10.  Multiply Uplink in ChirpStack =
++
++
++(((
  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
  )))
@@ -698,7 +698,7 @@
  [[image:image-20220601102430-1.png||height="508" width="1120"]]
--== 9.1  Solution ==
++== 10.1  Solution ==
  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]]
@@ -817,7 +817,7 @@
  Finish.
--= 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
++= 11.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
  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.
@@ -866,7 +866,7 @@
  [[image:image-20221012173639-1.png||height="273" width="1206"]]
--= 11.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
++= 12.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
  The following example is based on the built-in ChirpStack server for LPS8V2
@@ -873,7 +873,7 @@
  [[image:image-20231201174640-1.png||height="584" width="1148"]]
--== **11.1 Generate API Tokens** ==
++== **12.1 Generate API Tokens** ==
  Access the built-in chirpstack , click "**API Key**" and "**Add API Key**".
@@ -886,7 +886,7 @@
  [[image:image-20231204104802-1.png]]
--== **11.2 Template file** ==
++== **12.2 Template file** ==
  Click on **"Template File Download"**, the user will download a **register.csv** template file,
@@ -908,7 +908,7 @@
--== **11.3 Batch Register** ==
++== **12.3 Batch Register** ==
  [[image:image-20231204113136-11.png||height="362" width="1062"]]
@@ -921,7 +921,7 @@
--= 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
++= 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
  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:
@@ -932,7 +932,7 @@
  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
--== 12.1 Link Node-Red to Local ChirpStack ==
++== 13.1 Link Node-Red to Local ChirpStack ==
  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"]]**
@@ -966,7 +966,7 @@
  [[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"]]
--== 12.2 Check result. ==
++== 13.2 Check result. ==
  Users can check logs by adding debug.
@@ -976,9 +976,9 @@
  [[image:image-20230529150923-1.png||height="424" width="1118"]]
--= 13.  Trouble Shooting =
++= 14.  Trouble Shooting =
--== 13.1  MIC Mismatch or MIC Failed ==
++== 14.1  MIC Mismatch or MIC Failed ==
  (((
@@ -989,7 +989,7 @@
  Under normal circumstances, users need to change the APPKEY to solve this problem.
--== 13.2  The node is very close to the gateway, but the signal is poor ==
++== 14.2  The node is very close to the gateway, but the signal is poor ==
  If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
@@ -1018,7 +1018,7 @@
  **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]]**
--== 13.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
++== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
  This is because the node's packets are retransmitted, and the Fcnt of these packets is the same.
@@ -1049,7 +1049,7 @@
  [[image:image-20240717092428-4.jpeg]]
--== 13.4  How to get the log information of the node？ ==
++== 14.4  How to get the log information of the node？ ==
  ~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

Changes for page Notes for ChirpStack

Summary

Details

Applications

Navigation