Changes for page Notes for ChirpStack

Last modified by Kilight Cao on 2024/09/24 15:23

From version < 108.5 >

edited by Xiaoling
on 2022/07/23 13:54

To version < 128.1 >

edited by Kilight Cao
on 2022/12/22 14:15

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 12 added, 0 removed)

Details

Page properties

Author

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

Content

@@ -53,7 +53,7 @@
  )))
--If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.
++(% style="color:red" %)**If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.**
  [[image:image-20220531171609-1.png]]
@@ -62,15 +62,18 @@
--== 2.2 Step 2. Create Gateway-profiles ==
++== 2.2  Step 2. Create Gateway-profiles ==
++
  [[image:image-20220531171651-2.png]]
  Create Gateway-profiles
--== 2.3 Step 3. Create Service-profiles ==
++== 2.3  Step 3. Create Service-profiles ==
++
++
  [[image:image-20220531171809-3.png]]
  Create Service-profiles
@@ -83,29 +83,37 @@
  If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
--== 2.4 Step 4. Add the gateway ==
++== 2.4  Step 4. Add the gateway ==
++
++
  The example gateway id is: a840411e96744150
  (((
  (% style="color:red" %)**Note : The Gateway EUI and server addresses must match the ChirpStack configuration.**
++
++
  )))
  [[image:image-20220531171923-4.png]](% style="display:none" %)
--
  Add the gateway
++
++
  [[image:image-20220531172031-5.png]]
  Configure the gateway
--== 2.5 Step 5. Checking gateway Status ==
++== 2.5  Step 5. Checking gateway Status ==
++
++
  [[image:image-20220531172158-6.png]](% style="display:none" %)
++
  gateway Status
  [[image:image-20220531172304-7.png]]
@@ -113,39 +113,46 @@
  gateway Status
--= 3. Gateway Registration for Basics Station =
--== 3.1 Introduction ==
++= 3.  Gateway Registration for Basics Station =
++== 3.1  Introduction ==
++
++
  The [[Semtech Basic Station>>url:https://doc.sm.tc/station/]] backend implements the [[LNS protocol>>url:https://doc.sm.tc/station/tcproto.html]]. It exposes a WebSocket handler to which Basic Station powered gateways can connect.
  ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
--**Below list the support products and Requirements:**
++(% style="color:blue" %)**Below list the support products and Requirements:**
++
 . 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]]
 . 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/]]
--**How to set up chirpStack Basic Station**
++(% style="color:blue" %)**How to set up chirpStack Basic Station**
  Users can check out the ChirpStack Basic Station [[link>>https://www.chirpstack.io/gateway-bridge/backends/basic-station/]] and [[forum>>https://forum.chirpstack.io/search?q=basic%20station]]
--**What do you need to prepare**
++(% style="color:blue" %)**What do you need to prepare**
++
  A gateway that can access the internet normally
--== 3.2 Add Gateway ==
++== 3.2  Add Gateway ==
++
  [[image:image-20220524164205-10.png]]
--== 3.3 Access the gateway GUI ==
++== 3.3  Access the gateway GUI ==
++
  Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
  [[image:image-20220524164319-11.png]]
++
  User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate
  (% class="box" %)
@@ -161,20 +161,23 @@
  [[image:image-20220524164341-12.png]]
--== 3.4 Start Station ==
++== 3.4  Start Station ==
--When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
++When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
--== 3.5 Successful Connection ==
++== 3.5  Successful Connection ==
++
++
  If user completes the above steps, which will see live date in the ChirpStack.
  [[image:image-20220524164448-13.png]]
--== 3.6 Trouble Shooting ==
++== 3.6  Trouble Shooting ==
++
  User can check the station log in the logread/system log page.
  [[image:image-20220531172837-8.png]]
@@ -185,31 +185,129 @@
  [[image:image-20220531172857-9.png]]
--= 4. Downlink =
++= 4. How the gateway connects to Chirpstack v4 via gateway-bridge =
--== 4.1 Chirpstack Downlink Note ==
++(% 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]], [[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-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]]
++
++(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
++
++Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]
++
++
++(% style="color:blue" %)**What do you need to prepare**
++
++A gateway that can access the internet normally
++
++== 4.1 Configure Packet Forwarder ==
++
++In the Dragino gateway web interface, you need to configure the Packet Forwarder so that it forwards its data to the port. localhost:1700 or 127.0.0.1:1700
++
++* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
++* Make sure the following settings are set:
++** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
++** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
++** **Server port for upstream:** //1700//
++** **Server port for downstream:** //1700//
++
++      Click **Save & Apply**.
++
++[[image:image-20221222114220-2.png||height="748" width="931"]]
++
++
++== 4.2 Configuring gateway frequency ==
++
++Note: Gateway frequencies must match
++
++[[image:image-20221222134830-3.png||height="408" width="923"]]
++
++
++== 4.3 Modify the gateway-bridge configuration file ==
++
++
++Run the gateway command line command to modify the gateway-bridge configuration file:
++
++(% class="box infomessage" %)
++(((
++root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
++)))
++
++[[image:image-20221222113302-1.png]]
++
++[[image:image-20221222140203-4.png||height="875" width="806"]]
++
++
++(% class="wikigeneratedid" id="H" %)
++After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
++
++== 4.3 (Re)start and stop gateway-bridge ==
++
++Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
++
++(% class="box infomessage" %)
++(((
++**# start**
++
++/etc/init.d/chirpstack-gateway-bridge start
++
++**# stop**
++
++/etc/init.d/chirpstack-gateway-bridge stop
++
++**# restart**
++
++/etc/init.d/chirpstack-gateway-bridge restart
++)))
++
++= 5.  Downlink =
++
++== 5.1 Convert HEX to Base64 ==
++
++
++(% style="color:red" %)**Note: Chirpstack uses base64 to downlink, the end node user manual provides HEX format of the downlink commands. So user needs to convert the HEX to Base64.**
++
++**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
++
++[[image:image-20221010193350-1.png]]
++
++
++
++**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
++
++[[image:image-20221010193621-2.png]]
++
++
++== 5.2  Chirpstack Downlink Note ==
++
++
  [[image:image-20220601102543-2.png]]
--Convert the data to Base64
++**Convert the data to Base64**
++(% style="display:none" %) (%%)
--[[image:image-20220531173236-10.png]]
--Check ChripStack downlink DataRate
++[[image:image-20220531173236-10.png||height="597" width="1215"]]
++**Check ChripStack downlink DataRate**
++
++
  [[image:image-20220525101326-11.png]]
--Make sure the RX2DR is the same in the end node
++**Make sure the RX2DR is the same in the end node**
--== 4.2 Loraserver Downlink Note ==
++== 5.3  Loraserver Downlink Note ==
++
  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
  (((
--Below is examples:
++**Below is examples:**
  )))
  (% class="box" %)
@@ -223,13 +223,14 @@
  [[image:image-20220531173419-11.png]]
  (((
--MQTT Connect to ChirpStack
++**MQTT Connect to ChirpStack**
++
  )))
  (((
--After connect
++**After connect**
  )))
  (% class="box" %)
@@ -249,22 +249,14 @@
  [[image:image-20220531173519-12.png]]
--MQTT Connect to ChirpStack
++**MQTT Connect to ChirpStack**
--(((
--(% style="color:red" %)Note: Chirpstack use base64 to downlink, so need to convert the downlink payload from HEX to base64 [[https:~~/~~/base64.us/>>url:https://base64.us/]]
--)))
++**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**
--[[image:image-20220531173601-13.png]]
--
--Choose to Use Hex for Encode
--
--
--If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
--
  [[image:image-20220531173658-14.png]]
++
  (((
  Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码：
  )))
@@ -282,15 +282,15 @@
      {
          if(sha1[n] >= 'A' && sha1[n] <= 'Z')
          {
--            ascv = sha1.charCodeAt(n) - 55;
++            ascv = sha1.charCodeAt( n ) - 55;
          }
          else if(sha1[n] >= 'a' && sha1[n] <= 'z')
          {
--           ascv = sha1.charCodeAt(n) - 87;
++           ascv = sha1.charCodeAt( n ) - 87;
          }
          else
          {
--            ascv = sha1.charCodeAt(n) - 48;
++            ascv = sha1.charCodeAt( n ) - 48;
          }
  \\        bit_arr = (bit_arr << 4) | ascv;
          bit_num += 4;
@@ -327,11 +327,13 @@
  )))
--== 4.3 Add the decode function in Chirpstack for the payload ==
++== 4.3  Add the decode function in Chirpstack for the payload ==
++
++
  User enters the payload code according to the steps.
--[[image:image-20220531173754-15.png]]
++[[image:image-20220531173754-15.png||height="474" width="1334"]]
  [[image:image-20220531173856-16.png]]
@@ -342,8 +342,9 @@
  [[image:image-20220531174046-19.png]]
--= 5. Multiply Uplink in ChirpStack =
++= 6.  Multiply Uplink in ChirpStack =
++
  (((
  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
  )))
@@ -350,12 +350,17 @@
  (((
  ChirpStack will auto adjust nbtrans according to uplink rssi. [[link to source>>url:https://github.com/brocaar/chirpstack-network-server/blob/master/internal/adr/adr.go]]
++
++
  )))
--[[image:image-20220526091912-7.png]]
++[[image:image-20220526091912-7.png||height="241" width="1336"]]
++
  (((
  nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame.
++
++
  )))
  [[image:image-20220525104359-21.png]]
@@ -362,6 +362,8 @@
  (((
  Above behaviour will cause the platform shows below two cases of error:
++
++
  )))
  (((
@@ -371,29 +371,36 @@
  [[image:image-20220525104437-22.png]]
--Duplicate transmission in short time
--[[image:image-20220601102430-1.png]]
++**Duplicate transmission in short time**
++[[image:image-20220601102430-1.png||height="598" width="1319"]]
--== 5.1 Solution ==
++
++== 6.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]]
++
  (((
--~1. Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.
++(% style="color:blue" %)**1.  Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.**
++
++
  )))
  [[image:image-20220525104532-24.png]]
--installation path:
++**installation path:**
  [[image:image-20220525104554-25.png]]
++
  (((
--2. Environment variable settings:.
++(% style="color:blue" %)**2.  Environment variable settings:**
  )))
  (((
@@ -401,13 +401,13 @@
  )))
  (((
--2)Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
++2) Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
  )))
  [[image:image-20220524165433-33.png]]
--3)Modify the system variable Path and add C:\Go\bin\:
++3) Modify the system variable Path and add C:\Go\bin\:
  [[image:image-20220524165452-34.png]]
@@ -417,8 +417,9 @@
  [[image:image-20220524165517-35.png]]
--3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.
++(% style="color:blue" %)**3.  Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.**
++
  The name of the plugin: Example ADR plugin:
  [[image:image-20220524165540-36.png]]
@@ -428,8 +428,9 @@
  [[image:image-20220524165557-37.png]]
--4. Compile the ADR configuration file and generate the exe file.
++(% style="color:blue" %)**4.  Compile the ADR configuration file and generate the exe file.**
++
 ) Create a folder named adr-setting
 ) Open the adr-setting folder
@@ -453,8 +453,9 @@
  [[image:image-20220524165623-38.png]]
--5. Add the plugin and run the plugin.
++(% style="color:blue" %)**5.  Add the plugin and run the plugin.**
++
  (((
  The exe file generated in the previous step is placed in the same root directory as chirpstack-network-server.toml, and the ADR plugin is added to the toml file. The location of the addition is as follows:
  )))
@@ -490,11 +490,61 @@
  Finish.
--= 6. Trouble Shooting =
++= 7.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
--== 6.1 MIC Mismatch or MIC Failed ==
++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.
++
++This example will be shown how to store/get all the data in two ways:
++
++**//1). Chirpstack ~-~-> Node-red//**
++
++
++[[image:image-20221012184501-1.png]]
++
++
++Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
++
++[[image:image-20221012174220-2.png]]
++
++
++[[image:image-20221012184655-3.png||height="395" width="1049"]]
++
++
++**Each message is continuously logged to a specified file**
++
++[[image:image-20221012174352-3.png]]
++
++
++**//2). MQTT  Sub//**
++
++If you don't want to store the information via node-red, you can get the output via the subscribe command.
++
++
++**If connecting from the same machine, you can use the following command to receive data:**
++
++(% class="box infomessage" %)
  (((
++mosquitto_sub -h localhost -t "application/#" -v
++)))
++
++
++**Different host**
++
++(% class="box infomessage" %)
++(((
++mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
++)))
++
++[[image:image-20221012173639-1.png]]
++
++
++= 8.  Trouble Shooting =
++
++== 8.1  MIC Mismatch or MIC Failed ==
++
++
++(((
  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
  )))

image-20221010193350-1.png

Author

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

Size

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

Content

image-20221010193621-2.png

Author

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

Size

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

Content

image-20221012173639-1.png

Author

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

Size

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

Content

image-20221012174220-2.png

Author

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

Size

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

Content

image-20221012174352-3.png

Author

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

Size

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

Content

image-20221012184501-1.png

Author

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

Size

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

Content

image-20221012184631-2.png

Author

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

Size

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

Content

image-20221012184655-3.png

Author

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

Size

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

Content

image-20221222113302-1.png

Author

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

Size

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

Content

image-20221222114220-2.png

Author

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

Size

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

Content

image-20221222134830-3.png

Author

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

Size

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

Content

image-20221222140203-4.png

Author

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

Size

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

Content

Changes for page Notes for ChirpStack

Summary

Details

Applications

Navigation