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, 0 added, 15 removed)
- image-20221010193350-1.png
- image-20221010193621-2.png
- image-20221012173639-1.png
- image-20221012174220-2.png
- image-20221012174352-3.png
- image-20221012184501-1.png
- image-20221012184631-2.png
- image-20221012184655-3.png
- image-20221222113302-1.png
- image-20221222114220-2.png
- image-20221222134830-3.png
- image-20221222140203-4.png
- image-20221222141754-5.png
- image-20221222141830-6.png
- image-20221230094246-1.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -38,6 +38,7 @@ 38 38 ))) 39 39 40 40 41 + 41 41 = 2. Semtech UDP = 42 42 43 43 == 2.1 Step 1. Add the Network-servers == ... ... @@ -60,6 +60,7 @@ 60 60 Add the Network-servers 61 61 62 62 64 + 63 63 == 2.2 Step 2. Create Gateway-profiles == 64 64 65 65 ... ... @@ -68,6 +68,7 @@ 68 68 Create Gateway-profiles 69 69 70 70 73 + 71 71 == 2.3 Step 3. Create Service-profiles == 72 72 73 73 ... ... @@ -83,6 +83,7 @@ 83 83 If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %) 84 84 85 85 89 + 86 86 == 2.4 Step 4. Add the gateway == 87 87 88 88 ... ... @@ -105,13 +105,11 @@ 105 105 Configure the gateway 106 106 107 107 108 -== 2.5 112 +== 2.5 Step 5. Checking gateway Status == 109 109 110 - 111 111 [[image:image-20220531172158-6.png]](% style="display:none" %) 112 112 113 113 114 - 115 115 gateway Status 116 116 117 117 [[image:image-20220531172304-7.png]] ... ... @@ -119,45 +119,39 @@ 119 119 gateway Status 120 120 121 121 122 -= 3. 124 += 3. Gateway Registration for Basics Station = 123 123 124 -== 3.1 126 +== 3.1 Introduction == 125 125 126 - 127 127 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. 128 128 129 129 ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation. 130 130 132 +**Below list the support products and Requirements:** 131 131 132 -(% style="color:blue" %)**Below list the support products and Requirements:** 133 - 134 134 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]] 135 135 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/]] 136 136 137 - (% style="color:blue" %)**How to set up chirpStack Basic Station**137 +**How to set up chirpStack Basic Station** 138 138 139 139 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]] 140 140 141 +**What do you need to prepare** 141 141 142 -(% style="color:blue" %)**What do you need to prepare** 143 - 144 144 A gateway that can access the internet normally 145 145 146 146 147 -== 3.2 146 +== 3.2 Add Gateway == 148 148 149 - 150 150 [[image:image-20220524164205-10.png]] 151 151 152 152 153 -== 3.3 151 +== 3.3 Access the gateway GUI == 154 154 155 - 156 156 Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station 157 157 158 158 [[image:image-20220524164319-11.png]] 159 159 160 - 161 161 User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate 162 162 163 163 (% class="box" %) ... ... @@ -173,23 +173,20 @@ 173 173 [[image:image-20220524164341-12.png]] 174 174 175 175 176 -== 3.4 172 +== 3.4 Start Station == 177 177 174 +When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack 178 178 179 -When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack. 180 180 177 +== 3.5 Successful Connection == 181 181 182 -== 3.5 Successful Connection == 183 - 184 - 185 185 If user completes the above steps, which will see live date in the ChirpStack. 186 186 187 187 [[image:image-20220524164448-13.png]] 188 188 189 189 190 -== 3.6 184 +== 3.6 Trouble Shooting == 191 191 192 - 193 193 User can check the station log in the logread/system log page. 194 194 195 195 [[image:image-20220531172837-8.png]] ... ... @@ -200,146 +200,31 @@ 200 200 [[image:image-20220531172857-9.png]] 201 201 202 202 203 -= 4. Howthe gateway connects to Chirpstackv4 via gateway-bridge=196 += 4. Downlink = 204 204 198 +== 4.1 Chirpstack Downlink Note == 205 205 206 -(% style="color:blue" %)**Below list the support products and Requirements:** 207 - 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-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]] 210 - 211 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge** 212 - 213 -Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]] 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 -== 4.1 Configure Packet Forwarder == 222 - 223 - 224 -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 225 - 226 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 227 -* Make sure the following settings are set: 228 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 229 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1// 230 -** **Server port for upstream:** //1700// 231 -** **Server port for downstream:** //1700// 232 - 233 - Click **Save & Apply**. 234 - 235 -[[image:image-20221222114220-2.png||height="748" width="931"]] 236 - 237 - 238 -== 4.2 Configuring gateway frequency == 239 - 240 - 241 -(% style="color:red" %)**Note: Gateway frequencies must match** 242 - 243 -[[image:image-20221222134830-3.png||height="408" width="923"]] 244 - 245 - 246 -== 4.3 Modify the gateway-bridge configuration file == 247 - 248 - 249 -Run the gateway command line command to modify the gateway-bridge configuration file: 250 - 251 -(% class="box infomessage" %) 252 -((( 253 -root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 254 -))) 255 - 256 -[[image:image-20221222113302-1.png]] 257 - 258 - 259 -[[image:image-20221222140203-4.png||height="875" width="806"]] 260 - 261 -[[image:image-20221230094246-1.png||height="768" width="783"]] 262 - 263 -(% class="wikigeneratedid" id="H" %) 264 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 265 - 266 - 267 -== 4.4 (Re)start and stop gateway-bridge == 268 - 269 - 270 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: 271 - 272 -(% class="box infomessage" %) 273 -((( 274 -**# start** 275 - 276 -/etc/init.d/chirpstack-gateway-bridge start 277 - 278 -**# stop** 279 - 280 -/etc/init.d/chirpstack-gateway-bridge stop 281 - 282 -**# restart** 283 - 284 -/etc/init.d/chirpstack-gateway-bridge restart 285 -))) 286 - 287 - 288 -== 4.5 Successful Connection == 289 - 290 - 291 -[[image:image-20221222141754-5.png||height="488" width="1150"]] 292 - 293 - 294 -[[image:image-20221222141830-6.png||height="582" width="1153"]] 295 - 296 - 297 -= 5. Downlink = 298 - 299 -== 5.1 Convert HEX to Base64 == 300 - 301 - 302 -(% 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.** 303 - 304 -**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:** 305 - 306 -[[image:image-20221010193350-1.png]] 307 - 308 - 309 - 310 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]** 311 - 312 -[[image:image-20221010193621-2.png]] 313 - 314 - 315 -== 5.2 Chirpstack Downlink Note == 316 - 317 - 318 318 [[image:image-20220601102543-2.png]] 319 319 320 - **Convert the data to Base64**202 +Convert the data to Base64 321 321 322 -(% style="display:none" %) (%%) 323 323 205 +[[image:image-20220531173236-10.png]] 324 324 325 - [[image:image-20220531173236-10.png||height="597"width="1215"]]207 +Check ChripStack downlink DataRate 326 326 327 -**Check ChripStack downlink DataRate** 328 328 329 - 330 - 331 331 [[image:image-20220525101326-11.png]] 332 332 333 - **Make sure the RX2DR is the same in the end node**212 +Make sure the RX2DR is the same in the end node 334 334 335 335 336 -== 5.3Loraserver Downlink Note ==215 +== 4.2 Loraserver Downlink Note == 337 337 338 - 339 339 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End 340 340 341 341 ((( 342 - **Below is examples:**220 +Below is examples: 343 343 ))) 344 344 345 345 (% class="box" %) ... ... @@ -353,14 +353,13 @@ 353 353 [[image:image-20220531173419-11.png]] 354 354 355 355 ((( 356 - **MQTT Connect to ChirpStack**234 +MQTT Connect to ChirpStack 357 357 358 - 359 359 360 360 ))) 361 361 362 362 ((( 363 - **After connect**240 +After connect 364 364 ))) 365 365 366 366 (% class="box" %) ... ... @@ -380,14 +380,22 @@ 380 380 381 381 [[image:image-20220531173519-12.png]] 382 382 383 - **MQTT Connect to ChirpStack**260 +MQTT Connect to ChirpStack 384 384 385 385 386 -**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB** 263 +((( 264 +(% 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/]] 265 +))) 387 387 388 -[[image:image-202205311736 58-14.png]]267 +[[image:image-20220531173601-13.png]] 389 389 269 +Choose to Use Hex for Encode 390 390 271 + 272 +If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB 273 + 274 +[[image:image-20220531173658-14.png]] 275 + 391 391 ((( 392 392 Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码: 393 393 ))) ... ... @@ -405,15 +405,15 @@ 405 405 { 406 406 if(sha1[n] >= 'A' && sha1[n] <= 'Z') 407 407 { 408 - ascv = sha1.charCodeAt( 293 + ascv = sha1.charCodeAt(n) - 55; 409 409 } 410 410 else if(sha1[n] >= 'a' && sha1[n] <= 'z') 411 411 { 412 - ascv = sha1.charCodeAt( 297 + ascv = sha1.charCodeAt(n) - 87; 413 413 } 414 414 else 415 415 { 416 - ascv = sha1.charCodeAt( 301 + ascv = sha1.charCodeAt(n) - 48; 417 417 } 418 418 \\ bit_arr = (bit_arr << 4) | ascv; 419 419 bit_num += 4; ... ... @@ -450,12 +450,11 @@ 450 450 ))) 451 451 452 452 453 -== 4.3 338 +== 4.3 Add the decode function in Chirpstack for the payload == 454 454 455 - 456 456 User enters the payload code according to the steps. 457 457 458 -[[image:image-20220531173754-15.png ||height="474" width="1334"]]342 +[[image:image-20220531173754-15.png]] 459 459 460 460 461 461 [[image:image-20220531173856-16.png]] ... ... @@ -466,9 +466,8 @@ 466 466 [[image:image-20220531174046-19.png]] 467 467 468 468 469 -= 6.353 += 5. Multiply Uplink in ChirpStack = 470 470 471 - 472 472 ((( 473 473 nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data. 474 474 ))) ... ... @@ -475,17 +475,12 @@ 475 475 476 476 ((( 477 477 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]] 478 - 479 - 480 480 ))) 481 481 482 -[[image:image-20220526091912-7.png ||height="241" width="1336"]]363 +[[image:image-20220526091912-7.png]] 483 483 484 - 485 485 ((( 486 486 nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame. 487 - 488 - 489 489 ))) 490 490 491 491 [[image:image-20220525104359-21.png]] ... ... @@ -492,8 +492,6 @@ 492 492 493 493 ((( 494 494 Above behaviour will cause the platform shows below two cases of error: 495 - 496 - 497 497 ))) 498 498 499 499 ((( ... ... @@ -503,35 +503,29 @@ 503 503 [[image:image-20220525104437-22.png]] 504 504 505 505 382 +Duplicate transmission in short time 506 506 507 - **Duplicatetransmission in short time**384 +[[image:image-20220601102430-1.png]] 508 508 509 -[[image:image-20220601102430-1.png||height="598" width="1319"]] 510 510 387 +== 5.1 Solution == 511 511 512 -== 6.1 Solution == 513 - 514 - 515 515 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]] 516 516 517 - 518 518 ((( 519 -(% 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.** 520 - 521 - 392 +~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. 522 522 ))) 523 523 524 524 [[image:image-20220525104532-24.png]] 525 525 526 526 527 - **installation path:**398 +installation path: 528 528 529 529 [[image:image-20220525104554-25.png]] 530 530 531 531 532 - 533 533 ((( 534 - (% style="color:blue" %)**2.**404 +2. Environment variable settings:. 535 535 ))) 536 536 537 537 ((( ... ... @@ -539,13 +539,13 @@ 539 539 ))) 540 540 541 541 ((( 542 -2) 412 +2)Set the variable name GOROOT and the variable value C:\Go\ (installation directory) 543 543 ))) 544 544 545 545 [[image:image-20220524165433-33.png]] 546 546 547 547 548 -3) 418 +3)Modify the system variable Path and add C:\Go\bin\: 549 549 550 550 [[image:image-20220524165452-34.png]] 551 551 ... ... @@ -555,9 +555,8 @@ 555 555 [[image:image-20220524165517-35.png]] 556 556 557 557 428 +3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file. 558 558 559 -(% 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.** 560 - 561 561 The name of the plugin: Example ADR plugin: 562 562 563 563 [[image:image-20220524165540-36.png]] ... ... @@ -567,9 +567,8 @@ 567 567 [[image:image-20220524165557-37.png]] 568 568 569 569 439 +4. Compile the ADR configuration file and generate the exe file. 570 570 571 -(% style="color:blue" %)**4. Compile the ADR configuration file and generate the exe file.** 572 - 573 573 1) Create a folder named adr-setting 574 574 575 575 2) Open the adr-setting folder ... ... @@ -593,9 +593,8 @@ 593 593 [[image:image-20220524165623-38.png]] 594 594 595 595 464 +5. Add the plugin and run the plugin. 596 596 597 -(% style="color:blue" %)**5. Add the plugin and run the plugin.** 598 - 599 599 ((( 600 600 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: 601 601 ))) ... ... @@ -631,68 +631,14 @@ 631 631 Finish. 632 632 633 633 634 -= 7.Howtostore/getall data traffic for a specific sensor, includingraw payload, and uplink/ downlink history.=501 += 6. Trouble Shooting = 635 635 503 +== 6.1 MIC Mismatch or MIC Failed == 636 636 637 -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. 638 - 639 -This example will be shown how to store/get all the data in two ways: 640 - 641 -**//1). Chirpstack ~-~-> Node-red//** 642 - 643 - 644 -[[image:image-20221012184501-1.png]] 645 - 646 - 647 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file 648 - 649 -[[image:image-20221012174220-2.png]] 650 - 651 - 652 -[[image:image-20221012184655-3.png||height="395" width="1049"]] 653 - 654 - 655 -**Each message is continuously logged to a specified file** 656 - 657 -[[image:image-20221012174352-3.png]] 658 - 659 - 660 -**//2). MQTT Sub//** 661 - 662 -If you don't want to store the information via node-red, you can get the output via the subscribe command. 663 - 664 - 665 -**If connecting from the same machine, you can use the following command to receive data:** 666 - 667 -(% class="box infomessage" %) 668 668 ((( 669 -mosquitto_sub -h localhost -t "application/#" -v 670 -))) 671 - 672 - 673 -**Different host** 674 - 675 -(% class="box infomessage" %) 676 -((( 677 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 678 -))) 679 - 680 -[[image:image-20221012173639-1.png]] 681 - 682 - 683 -= 8. Trouble Shooting = 684 - 685 -== 8.1 MIC Mismatch or MIC Failed == 686 - 687 - 688 -((( 689 689 When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. 690 690 ))) 691 691 692 692 ((( 693 693 Under normal circumstances, users need to change the APPKEY to solve this problem. 694 - 695 - 696 - 697 - 698 698 )))
- image-20221010193350-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.7 KB - Content
- image-20221010193621-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.2 KB - Content
- image-20221012173639-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.2 KB - Content
- image-20221012174220-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.8 KB - Content
- image-20221012174352-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.0 KB - Content
- image-20221012184501-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.3 KB - Content
- image-20221012184631-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.4 KB - Content
- image-20221012184655-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -45.4 KB - Content
- image-20221222113302-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -76.3 KB - Content
- image-20221222114220-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.3 KB - Content
- image-20221222134830-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -54.5 KB - Content
- image-20221222140203-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.4 KB - Content
- image-20221222141754-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -179.1 KB - Content
- image-20221222141830-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -116.7 KB - Content
- image-20221230094246-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -84.9 KB - Content