Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 7 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -38,7 +38,6 @@ 38 38 ))) 39 39 40 40 41 - 42 42 = 2. Semtech UDP = 43 43 44 44 == 2.1 Step 1. Add the Network-servers == ... ... @@ -61,7 +61,6 @@ 61 61 Add the Network-servers 62 62 63 63 64 - 65 65 == 2.2 Step 2. Create Gateway-profiles == 66 66 67 67 ... ... @@ -70,7 +70,6 @@ 70 70 Create Gateway-profiles 71 71 72 72 73 - 74 74 == 2.3 Step 3. Create Service-profiles == 75 75 76 76 ... ... @@ -86,7 +86,6 @@ 86 86 If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %) 87 87 88 88 89 - 90 90 == 2.4 Step 4. Add the gateway == 91 91 92 92 ... ... @@ -109,7 +109,6 @@ 109 109 Configure the gateway 110 110 111 111 112 - 113 113 == 2.5 Step 5. Checking gateway Status == 114 114 115 115 ... ... @@ -124,7 +124,6 @@ 124 124 gateway Status 125 125 126 126 127 - 128 128 = 3. Gateway Registration for Basics Station = 129 129 130 130 == 3.1 Introduction == ... ... @@ -206,14 +206,34 @@ 206 206 [[image:image-20220531172857-9.png]] 207 207 208 208 209 -= 4. 4via gateway-bridge =203 += 4. How the gateway connects to Chirpstack v3 via gateway-bridge = 210 210 211 211 212 - ===4.1 ConfigurePacketForwarder===206 +(% style="color:blue" %)**Below list the support products and Requirements:** 213 213 208 +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]] 209 +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/]] 210 + 211 +(% style="color:blue" %)**How to set up chirpStack Gateway-bridge** 212 + 213 +Users can check out the ChirpStack gateway-bridge v3 [[link>>https://www.chirpstack.io/gateway-bridge/gateway/dragino/]] 214 + 215 + 216 +(% style="color:blue" %)**What do you need to prepare** 217 + 218 +A gateway that can access the internet normally 219 + 220 + 221 +The following example does not have configuration certificates: 222 + 223 + 224 +== 4.1 Configure Packet Forwarder == 225 + 226 + 214 214 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 215 215 216 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 229 +* In the (% style="color:blue" %)**LoRaWAN** (%%)menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP** 230 + 217 217 * Make sure the following settings are set: 218 218 ** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 219 219 ** **LoRaWAN Server Address:** //localhost or 127.0.0.1// ... ... @@ -220,20 +220,190 @@ 220 220 ** **Server port for upstream:** //1700// 221 221 ** **Server port for downstream:** //1700// 222 222 223 - Click **Save & Apply**. 237 + Click (% style="color:blue" %)**Save & Apply**. 224 224 225 225 [[image:image-20221222114220-2.png||height="748" width="931"]] 226 226 227 227 228 -4.2 242 +== 4.2 Configuring gateway frequency == 229 229 244 + 245 +(% style="color:red" %)**Note: Gateway frequencies must match** 246 + 247 +[[image:image-20221222134830-3.png||height="408" width="923"]] 248 + 249 + 250 +== 4.3 Generate and modify the gateway-bridge configuration file == 251 + 252 + 253 +**1)Generate the gateway-bridge configuration file** 254 + 255 +By default, the configuration file is not up-to-date,so the user needs to rebuild the gateway-bridge configuration file. 256 + 257 +Users need to access the command line of the gateway through SSH,Then type the following command: 258 + 259 +(% class="box infomessage" %) 260 +((( 261 +**/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml ** 262 +))) 263 + 264 + 265 +**2)modify the gateway-bridge configuration file** 266 + 267 +The user needs to modify the server address in line 252 in the configuration file 268 + 269 +(% class="box infomessage" %) 270 +((( 271 +**vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml ** 272 +))) 273 + 274 +[[image:image-20230415165254-1.png||height="583" width="956"]] 275 + 276 + 277 +== 4.4 Debug == 278 + 279 + 280 +After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection 281 + 282 +(% class="box infomessage" %) 283 +((( 284 +**/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml** 285 +))) 286 + 287 +If the gateway-bridge connection is normal, the debug log displays **"connected to mqtt broker"**. 288 + 289 +[[image:image-20230415170404-2.png]] 290 + 291 + 292 +If the debug log shows "**connection error**", check that the server port or server is correct 293 + 294 +[[image:image-20230415170854-3.png]] 295 + 296 + 297 +More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]** 298 + 299 + 300 +== 4.5 (Re)start and stop gateway-bridge == 301 + 302 + 303 +Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: 304 + 305 +(% class="box infomessage" %) 306 +((( 307 +**# start** 308 + 309 +/etc/init.d/chirpstack-gateway-bridge start 310 + 311 +**# stop** 312 + 313 +/etc/init.d/chirpstack-gateway-bridge stop 314 + 315 +**# restart** 316 + 317 +/etc/init.d/chirpstack-gateway-bridge restart 318 +))) 319 + 320 + 321 += 5. How the gateway connects to Chirpstack v4 via gateway-bridge = 322 + 323 + 324 +(% style="color:blue" %)**Below list the support products and Requirements:** 325 + 326 +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]] 327 +1. 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/]] 328 + 329 +(% style="color:blue" %)**How to set up chirpStack Gateway-bridge** 330 + 331 +Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]] 332 + 333 + 334 +(% style="color:blue" %)**What do you need to prepare** 335 + 336 +A gateway that can access the internet normally 337 + 338 + 339 +== 5.1 Configure Packet Forwarder == 340 + 341 + 342 +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 343 + 344 +* In the (% style="color:blue" %)**LoRaWAN**(%%) menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP** 345 + 346 +* Make sure the following settings are set: 347 +** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 348 +** **LoRaWAN Server Address:** //localhost or 127.0.0.1// 349 +** **Server port for upstream:** //1700// 350 +** **Server port for downstream:** //1700// 351 + 352 + Click (% style="color:blue" %)**Save & Apply**. 353 + 354 +[[image:image-20221222114220-2.png||height="748" width="931"]] 355 + 356 + 357 +== 5.2 Configuring gateway frequency == 358 + 359 + 360 +(% style="color:red" %)**Note: Gateway frequencies must match** 361 + 362 +[[image:image-20221222134830-3.png||height="408" width="923"]] 363 + 364 + 365 +== 5.3 Modify the gateway-bridge configuration file == 366 + 367 + 368 +Run the gateway command line command to modify the gateway-bridge configuration file: 369 + 370 +(% class="box infomessage" %) 371 +((( 372 +**root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml ** 373 +))) 374 + 230 230 [[image:image-20221222113302-1.png]] 231 231 232 -= 5. Downlink = 233 233 234 - == 5.1ConvertHEXto Base64==378 +[[image:image-20221222140203-4.png||height="875" width="806"]] 235 235 380 +[[image:image-20221230094246-1.png||height="768" width="783"]] 236 236 382 +(% class="wikigeneratedid" id="H" %) 383 +After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 384 + 385 + 386 +== 5.4 (Re)start and stop gateway-bridge == 387 + 388 + 389 +Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: 390 + 391 +(% class="box infomessage" %) 392 +((( 393 +**# start** 394 + 395 +/etc/init.d/chirpstack-gateway-bridge start 396 + 397 +**# stop** 398 + 399 +/etc/init.d/chirpstack-gateway-bridge stop 400 + 401 +**# restart** 402 + 403 +/etc/init.d/chirpstack-gateway-bridge restart 404 +))) 405 + 406 + 407 +== 5.5 Successful Connection == 408 + 409 + 410 +[[image:image-20221222141754-5.png||height="488" width="1150"]] 411 + 412 + 413 +[[image:image-20221222141830-6.png||height="582" width="1153"]] 414 + 415 + 416 += 6. Downlink = 417 + 418 +== 6.1 Convert HEX to Base64 == 419 + 420 + 237 237 (% 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.** 238 238 239 239 **[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:** ... ... @@ -247,7 +247,7 @@ 247 247 [[image:image-20221010193621-2.png]] 248 248 249 249 250 -== 5.2 Chirpstack Downlink Note ==434 +== 6.2 Chirpstack Downlink Note == 251 251 252 252 253 253 [[image:image-20220601102543-2.png]] ... ... @@ -268,7 +268,7 @@ 268 268 **Make sure the RX2DR is the same in the end node** 269 269 270 270 271 -== 5.3 Loraserver Downlink Note ==455 +== 6.3 Loraserver Downlink Note == 272 272 273 273 274 274 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End ... ... @@ -385,10 +385,9 @@ 385 385 ))) 386 386 387 387 572 +== 6.3 Add the decode function in Chirpstack for the payload == 388 388 389 -== 4.3 Add the decode function in Chirpstack for the payload == 390 390 391 - 392 392 User enters the payload code according to the steps. 393 393 394 394 [[image:image-20220531173754-15.png||height="474" width="1334"]] ... ... @@ -402,7 +402,7 @@ 402 402 [[image:image-20220531174046-19.png]] 403 403 404 404 405 -= 6. Multiply Uplink in ChirpStack =588 += 7. Multiply Uplink in ChirpStack = 406 406 407 407 408 408 ((( ... ... @@ -445,10 +445,9 @@ 445 445 [[image:image-20220601102430-1.png||height="598" width="1319"]] 446 446 447 447 631 +== 7.1 Solution == 448 448 449 -== 6.1 Solution == 450 450 451 - 452 452 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]] 453 453 454 454 ... ... @@ -568,7 +568,7 @@ 568 568 Finish. 569 569 570 570 571 -= 7. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =753 += 8. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 572 572 573 573 574 574 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. ... ... @@ -575,7 +575,7 @@ 575 575 576 576 This example will be shown how to store/get all the data in two ways: 577 577 578 -**//1). Chirpstack ~-~-> Node-red//** 760 +(% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//** 579 579 580 580 581 581 [[image:image-20221012184501-1.png]] ... ... @@ -594,7 +594,7 @@ 594 594 [[image:image-20221012174352-3.png]] 595 595 596 596 597 -**//2). MQTT Sub//** 779 +(% style="color:blue" %)**//2). MQTT Sub//** 598 598 599 599 If you don't want to store the information via node-red, you can get the output via the subscribe command. 600 600 ... ... @@ -603,23 +603,23 @@ 603 603 604 604 (% class="box infomessage" %) 605 605 ((( 606 -mosquitto_sub -h localhost -t "application/#" -v 788 +**mosquitto_sub -h localhost -t "application/#" -v** 607 607 ))) 608 608 609 609 610 -**Different host** 792 +(% style="color:blue" %)**Different host** 611 611 612 612 (% class="box infomessage" %) 613 613 ((( 614 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 796 +**mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v** 615 615 ))) 616 616 617 617 [[image:image-20221012173639-1.png]] 618 618 619 619 620 -= 8. Trouble Shooting =802 += 9. Trouble Shooting = 621 621 622 -== 8.1 MIC Mismatch or MIC Failed ==804 +== 9.1 MIC Mismatch or MIC Failed == 623 623 624 624 625 625 ((( ... ... @@ -628,4 +628,6 @@ 628 628 629 629 ((( 630 630 Under normal circumstances, users need to change the APPKEY to solve this problem. 813 + 814 + 631 631 )))
- image-20221222140203-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +91.4 KB - Content
- image-20221222141754-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +179.1 KB - Content
- image-20221222141830-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +116.7 KB - Content
- image-20221230094246-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +84.9 KB - Content
- image-20230415165254-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +67.2 KB - Content
- image-20230415170404-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +17.9 KB - Content
- image-20230415170854-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +48.4 KB - Content