Changes for page Notes for ChirpStack

Last modified by Xiaoling on 2025/07/31 17:18

From 239.1 to 238.1

From version 247.1

edited by Xiaoling
on 2025/07/31 17:18

Change comment: There is no comment for this version

To version 239.1

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

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

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -32,8 +32,7 @@
  (((
  (((
  Semtech UDP : **All Model**
--Basic Station : [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]], [[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], [[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]]
--
++Basic Station : [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
  (% style="color:red" %)**Note** (%%): the firmware needs >[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]  if use the Bais station
  )))
  )))
@@ -190,8 +190,8 @@
  (% style="color:blue" %)**Below list the support products and Requirements:**
--1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]], [[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], [[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]]
--1. Firmware version since : [[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]]
++1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
++1. Firmware version since :[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]]
  (% style="color:blue" %)**How to set up chirpStack Basic Station**
@@ -205,8 +205,10 @@
  == 5.2  Add Gateway ==
++
  [[image:image-20220524164205-10.png]]
++
  == 5.3  Access the gateway GUI ==
@@ -262,8 +262,8 @@
  (% style="color:blue" %)**Below list the support products and Requirements:**
--1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]], [[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], [[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]]
--1. Firmware version since: [[Chirpstack-Bridge-V3.14.6>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V3.14.6-Bridge--build-v5.4.1679487778-20230322-2024/||style="background-color: rgb(255, 255, 255);"]]
++1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]],[[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]]
++1. Firmware version since: [[Chirpstack-Bridge-V3.14.6>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V3.14.6-Bridge--build-v5.4.1679487778-20230322-2024/]]
  (% style="color:blue" %)**What do you need to prepare**
@@ -272,6 +272,7 @@
  The following example does not have configuration certificates:
++
  == 6.1  Configure Packet Forwarder ==
@@ -374,7 +374,7 @@
  (% style="color:blue" %)**Below list the support products and Requirements:**
--1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]]
++1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]],[[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]]
 . Firmware version since: [[Chirpstack-Bridge-V4>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V4--build-v5.4.1670655072-20221210-1452/]]
  (% style="color:blue" %)**What do you need to prepare**
@@ -464,18 +464,25 @@
  = 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.**
++
  [[image:image-20231108171112-5.png||height="629" width="1117"]]
++
  [[image:image-20231108171145-6.png||height="497" width="1101"]]
++
++
++
  [[image:image-20220531173236-10.png||height="597" width="1215"]]
  **Check ChripStack downlink DataRate**
@@ -487,10 +487,10 @@
  **Make sure the RX2DR is the same in the end node**
--== 8.2 Schedule Downlink via API ==
++== 8.3  Loraserver Downlink Note ==
--User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End Node
++User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
  (((
  **Below is examples:**
@@ -509,6 +509,7 @@
  (((
  **MQTT Connect to ChirpStack**
++
  )))
@@ -536,6 +536,7 @@
  **MQTT Connect to ChirpStack**
++
  (((
  Downlink payload encode javescript code.
@@ -600,148 +600,54 @@
  )))
--== 8.3  Add decoder function in Chirpstack for downlink message ==
++== 8.4  Add the decode function in Chirpstack for the payload ==
++User enters the payload code according to the steps.
--= 9.  Chirpstack Multicast Configuration =
++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]]**
--== 9.1  Introduction ==
++[[image:image-20220531173754-15.png||height="474" width="1334"]]
--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.
--Multicast can be used for the following device-classes:
++[[image:image-20220531173856-16.png]]
--* Class-B
--* Class-C
--== 9.2  Example to configure chirpstack Multicast ==
++[[image:image-20220531174120-20.png]]
--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-20220531174046-19.png]]
--[[image:image-20240923105725-1.png]]
++= 9.  Chirpstack Multicast Configuration =
--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).
++== 9.1  Introduction ==
--(% class="wikigeneratedid" %)
--          **AT command:** (% style="color:blue" %)**AT+CLASS=C**
++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.
--(% class="wikigeneratedid" %)
--                                  (% style="color:blue" %)**AT+DISFCNTCHECK=1**
++Multicast can be used for the following device-classes:
--(% 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]]**
++* Class-B
++* Class-C
--* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
++== 9.2  Example to configure chirpstack Multicast ==
--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]]
++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.
++[[image:image-20240923105725-1.png]]
--=== Step 1. Create the multicast group ===
++The LPS8V2 is already set to connect to Chirpstack. So what we need to do now is only configure register these devices to Chirpstack:
--Create the multicast group on the corresponding **Application~-~->multicast groups~-~->Add multicast-group** interface, For example, multicast_test01_au915
++=== Step 1. Create the multicast group ===
--[[image:image-20240923141847-3.png||height="620" width="1207"]]
--Enter the Multicast address,Multicast network session key,Multicast application session key.
++= 9.  Multiply Uplink in ChirpStack =
--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.
  )))
@@ -781,7 +781,7 @@
  [[image:image-20220601102430-1.png||height="508" width="1120"]]
--== 10.1  Solution ==
++== 9.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]]
@@ -900,7 +900,7 @@
  Finish.
--= 11.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
++= 10.  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.
@@ -949,15 +949,14 @@
  [[image:image-20221012173639-1.png||height="273" width="1206"]]
--= 12.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
++= 11.  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
  [[image:image-20231201174640-1.png||height="584" width="1148"]]
--== **12.1 Generate API Tokens** ==
++== **11.1 Generate API Tokens** ==
  Access the built-in chirpstack , click "**API Key**" and "**Add API Key**".
@@ -970,7 +970,7 @@
  [[image:image-20231204104802-1.png]]
--== **12.2 Template file** ==
++== **11.2 Template file** ==
  Click on **"Template File Download"**, the user will download a **register.csv** template file,
@@ -991,8 +991,9 @@
  [[image:image-20231204112107-10.png||height="621" width="1203"]]
--== **12.3 Batch Register** ==
++== **11.3 Batch Register** ==
++
  [[image:image-20231204113136-11.png||height="362" width="1062"]]
@@ -1003,9 +1003,10 @@
  [[image:image-20231204113237-13.png||height="558" width="1081"]]
--= 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
++= 12.  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:
  * LHT65N register on LPS8v2 Built-In ChirpStack server already
@@ -1014,7 +1014,7 @@
  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
--== 13.1 Link Node-Red to Local ChirpStack ==
++== 12.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"]]**
@@ -1035,6 +1035,7 @@
  [[image:image-20230527143923-1.png||height="588" width="1132"]]
++
  (% style="color:blue" %)**2. Enter the MQTT configuration information**
  [[image:image-20230527144206-2.png||height="590" width="1136"]]
@@ -1047,7 +1047,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"]]
--== 13.2 Check result. ==
++== 12.2 Check result. ==
  Users can check logs by adding debug.
@@ -1057,9 +1057,9 @@
  [[image:image-20230529150923-1.png||height="424" width="1118"]]
--= 14.  Trouble Shooting =
++= 13.  Trouble Shooting =
--== 14.1  MIC Mismatch or MIC Failed ==
++== 13.1  MIC Mismatch or MIC Failed ==
  (((
@@ -1070,17 +1070,17 @@
  Under normal circumstances, users need to change the APPKEY to solve this problem.
--== 14.2  The node is very close to the gateway, but the signal is poor ==
++== 13.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
  Like that：Both 905.1Mhz and 902.3Mhz appear on uplink
--                   But they belong to Subband1 and Subband2 of US915 respectively
++                 But they belong to Subband1 and Subband2 of US915 respectively
  Cause: The server and the gateway use different frequency bands (the server uses Subband1, and the gateway uses Subband2)
--             In server side, it shows the frequency is 905.1Mhz, which is sub-band2. But the RSSI is very low, Because this is not a signal in 905.1Mhz, it is on 902.3Mhz, the signal is too strong and appear a noise in 905.1Mhz.
++            In server side, it shows the frequency is 905.1Mhz, which is sub-band2. But the RSSI is very low, Because this is not a signal in 905.1Mhz, it is on 902.3Mhz, the signal is too strong and appear a noise in 905.1Mhz.
  How to check the frequency band used by the server：
@@ -1099,7 +1099,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]]**
--== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
++== 13.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.
@@ -1130,7 +1130,7 @@
  [[image:image-20240717092428-4.jpeg]]
--== 14.4  How to get the log information of the node？ ==
++== 13.4  How to get the log information of the node？ ==
  ~1. Get information about a single node.
@@ -1156,6 +1156,7 @@
  [[image:image-20240117175009-3.png||height="524" width="1076"]]
++
  After the data collection is completed, you can send this file directly to our technical support personnel for analysis.

SN50v3-LB_协议008（AU915）(1).bin

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-89.2 KB

Content

Changes for page Notes for ChirpStack

Summary

Details

Applications

Navigation