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, 12 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
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -125,11 +125,12 @@ 125 125 126 126 127 127 128 -= 3. 128 += 3. Gateway Registration for Basics Station = 129 129 130 -== 3.1 Introduction == 131 131 131 +== 3.1 Introduction == 132 132 133 + 133 133 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. 134 134 135 135 ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation. ... ... @@ -140,6 +140,9 @@ 140 140 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]] 141 141 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/]] 142 142 144 + 145 + 146 + 143 143 (% style="color:blue" %)**How to set up chirpStack Basic Station** 144 144 145 145 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]] ... ... @@ -150,20 +150,18 @@ 150 150 A gateway that can access the internet normally 151 151 152 152 153 -== 3.2 Add Gateway == 154 154 158 +== 3.2 Add Gateway == 155 155 156 156 [[image:image-20220524164205-10.png]] 157 157 158 158 159 -== 3.3 163 +== 3.3 Access the gateway GUI == 160 160 161 - 162 162 Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station 163 163 164 164 [[image:image-20220524164319-11.png]] 165 165 166 - 167 167 User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate 168 168 169 169 (% class="box" %) ... ... @@ -179,23 +179,20 @@ 179 179 [[image:image-20220524164341-12.png]] 180 180 181 181 182 -== 3.4 184 +== 3.4 Start Station == 183 183 186 +When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack 184 184 185 -When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack. 186 186 189 +== 3.5 Successful Connection == 187 187 188 -== 3.5 Successful Connection == 189 - 190 - 191 191 If user completes the above steps, which will see live date in the ChirpStack. 192 192 193 193 [[image:image-20220524164448-13.png]] 194 194 195 195 196 -== 3.6 196 +== 3.6 Trouble Shooting == 197 197 198 - 199 199 User can check the station log in the logread/system log page. 200 200 201 201 [[image:image-20220531172837-8.png]] ... ... @@ -206,129 +206,31 @@ 206 206 [[image:image-20220531172857-9.png]] 207 207 208 208 209 -= 4. Howthe gateway connects to Chirpstackv4 via gateway-bridge=208 += 4. Downlink = 210 210 210 +== 4.1 Chirpstack Downlink Note == 211 211 212 -(% style="color:blue" %)**Below list the support products and Requirements:** 213 - 214 -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]] 215 -1. Firmware version since: [[Chirpstack-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]] 216 - 217 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge** 218 - 219 -Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]] 220 - 221 - 222 -(% style="color:blue" %)**What do you need to prepare** 223 - 224 -A gateway that can access the internet normally 225 - 226 -== 4.1 Configure Packet Forwarder == 227 - 228 -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 229 - 230 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 231 -* Make sure the following settings are set: 232 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 233 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1// 234 -** **Server port for upstream:** //1700// 235 -** **Server port for downstream:** //1700// 236 - 237 - Click **Save & Apply**. 238 - 239 -[[image:image-20221222114220-2.png||height="748" width="931"]] 240 - 241 - 242 -== 4.2 Configuring gateway frequency == 243 - 244 -Note: Gateway frequencies must match 245 - 246 -[[image:image-20221222134830-3.png||height="408" width="923"]] 247 - 248 - 249 -== 4.3 Modify the gateway-bridge configuration file == 250 - 251 - 252 -Run the gateway command line command to modify the gateway-bridge configuration file: 253 - 254 -(% class="box infomessage" %) 255 -((( 256 -root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 257 -))) 258 - 259 -[[image:image-20221222113302-1.png]] 260 - 261 -[[image:image-20221222140203-4.png||height="875" width="806"]] 262 - 263 - 264 -(% class="wikigeneratedid" id="H" %) 265 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 266 - 267 -== 4.3 (Re)start and stop gateway-bridge == 268 - 269 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: 270 - 271 -(% class="box infomessage" %) 272 -((( 273 -**# start** 274 - 275 -/etc/init.d/chirpstack-gateway-bridge start 276 - 277 -**# stop** 278 - 279 -/etc/init.d/chirpstack-gateway-bridge stop 280 - 281 -**# restart** 282 - 283 -/etc/init.d/chirpstack-gateway-bridge restart 284 -))) 285 - 286 -= 5. Downlink = 287 - 288 -== 5.1 Convert HEX to Base64 == 289 - 290 - 291 -(% 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.** 292 - 293 -**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:** 294 - 295 -[[image:image-20221010193350-1.png]] 296 - 297 - 298 - 299 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]** 300 - 301 -[[image:image-20221010193621-2.png]] 302 - 303 - 304 -== 5.2 Chirpstack Downlink Note == 305 - 306 - 307 307 [[image:image-20220601102543-2.png]] 308 308 309 - **Convert the data to Base64**214 +Convert the data to Base64 310 310 311 -(% style="display:none" %) (%%) 312 312 217 +[[image:image-20220531173236-10.png]] 313 313 314 - [[image:image-20220531173236-10.png||height="597"width="1215"]]219 +Check ChripStack downlink DataRate 315 315 316 -**Check ChripStack downlink DataRate** 317 317 318 - 319 - 320 320 [[image:image-20220525101326-11.png]] 321 321 322 - **Make sure the RX2DR is the same in the end node**224 +Make sure the RX2DR is the same in the end node 323 323 324 324 325 -== 5.3Loraserver Downlink Note ==227 +== 4.2 Loraserver Downlink Note == 326 326 327 - 328 328 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End 329 329 330 330 ((( 331 - **Below is examples:**232 +Below is examples: 332 332 ))) 333 333 334 334 (% class="box" %) ... ... @@ -342,14 +342,13 @@ 342 342 [[image:image-20220531173419-11.png]] 343 343 344 344 ((( 345 - **MQTT Connect to ChirpStack**246 +MQTT Connect to ChirpStack 346 346 347 - 348 348 349 349 ))) 350 350 351 351 ((( 352 - **After connect**252 +After connect 353 353 ))) 354 354 355 355 (% class="box" %) ... ... @@ -369,14 +369,22 @@ 369 369 370 370 [[image:image-20220531173519-12.png]] 371 371 372 - **MQTT Connect to ChirpStack**272 +MQTT Connect to ChirpStack 373 373 374 374 375 -**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB** 275 +((( 276 +(% 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/]] 277 +))) 376 376 377 -[[image:image-202205311736 58-14.png]]279 +[[image:image-20220531173601-13.png]] 378 378 281 +Choose to Use Hex for Encode 379 379 283 + 284 +If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB 285 + 286 +[[image:image-20220531173658-14.png]] 287 + 380 380 ((( 381 381 Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码: 382 382 ))) ... ... @@ -394,15 +394,15 @@ 394 394 { 395 395 if(sha1[n] >= 'A' && sha1[n] <= 'Z') 396 396 { 397 - ascv = sha1.charCodeAt( 305 + ascv = sha1.charCodeAt(n) - 55; 398 398 } 399 399 else if(sha1[n] >= 'a' && sha1[n] <= 'z') 400 400 { 401 - ascv = sha1.charCodeAt( 309 + ascv = sha1.charCodeAt(n) - 87; 402 402 } 403 403 else 404 404 { 405 - ascv = sha1.charCodeAt( 313 + ascv = sha1.charCodeAt(n) - 48; 406 406 } 407 407 \\ bit_arr = (bit_arr << 4) | ascv; 408 408 bit_num += 4; ... ... @@ -439,13 +439,11 @@ 439 439 ))) 440 440 441 441 350 +== 4.3 Add the decode function in Chirpstack for the payload == 442 442 443 -== 4.3 Add the decode function in Chirpstack for the payload == 444 - 445 - 446 446 User enters the payload code according to the steps. 447 447 448 -[[image:image-20220531173754-15.png ||height="474" width="1334"]]354 +[[image:image-20220531173754-15.png]] 449 449 450 450 451 451 [[image:image-20220531173856-16.png]] ... ... @@ -456,9 +456,8 @@ 456 456 [[image:image-20220531174046-19.png]] 457 457 458 458 459 -= 6.365 += 5. Multiply Uplink in ChirpStack = 460 460 461 - 462 462 ((( 463 463 nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data. 464 464 ))) ... ... @@ -465,17 +465,12 @@ 465 465 466 466 ((( 467 467 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]] 468 - 469 - 470 470 ))) 471 471 472 -[[image:image-20220526091912-7.png ||height="241" width="1336"]]375 +[[image:image-20220526091912-7.png]] 473 473 474 - 475 475 ((( 476 476 nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame. 477 - 478 - 479 479 ))) 480 480 481 481 [[image:image-20220525104359-21.png]] ... ... @@ -482,8 +482,6 @@ 482 482 483 483 ((( 484 484 Above behaviour will cause the platform shows below two cases of error: 485 - 486 - 487 487 ))) 488 488 489 489 ((( ... ... @@ -493,36 +493,29 @@ 493 493 [[image:image-20220525104437-22.png]] 494 494 495 495 394 +Duplicate transmission in short time 496 496 497 - **Duplicatetransmission in short time**396 +[[image:image-20220601102430-1.png]] 498 498 499 -[[image:image-20220601102430-1.png||height="598" width="1319"]] 500 500 399 +== 5.1 Solution == 501 501 502 - 503 -== 6.1 Solution == 504 - 505 - 506 506 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]] 507 507 508 - 509 509 ((( 510 -(% 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.** 511 - 512 - 404 +~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. 513 513 ))) 514 514 515 515 [[image:image-20220525104532-24.png]] 516 516 517 517 518 - **installation path:**410 +installation path: 519 519 520 520 [[image:image-20220525104554-25.png]] 521 521 522 522 523 - 524 524 ((( 525 - (% style="color:blue" %)**2.**416 +2. Environment variable settings:. 526 526 ))) 527 527 528 528 ((( ... ... @@ -530,13 +530,13 @@ 530 530 ))) 531 531 532 532 ((( 533 -2) 424 +2)Set the variable name GOROOT and the variable value C:\Go\ (installation directory) 534 534 ))) 535 535 536 536 [[image:image-20220524165433-33.png]] 537 537 538 538 539 -3) 430 +3)Modify the system variable Path and add C:\Go\bin\: 540 540 541 541 [[image:image-20220524165452-34.png]] 542 542 ... ... @@ -546,9 +546,8 @@ 546 546 [[image:image-20220524165517-35.png]] 547 547 548 548 440 +3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file. 549 549 550 -(% 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.** 551 - 552 552 The name of the plugin: Example ADR plugin: 553 553 554 554 [[image:image-20220524165540-36.png]] ... ... @@ -558,9 +558,8 @@ 558 558 [[image:image-20220524165557-37.png]] 559 559 560 560 451 +4. Compile the ADR configuration file and generate the exe file. 561 561 562 -(% style="color:blue" %)**4. Compile the ADR configuration file and generate the exe file.** 563 - 564 564 1) Create a folder named adr-setting 565 565 566 566 2) Open the adr-setting folder ... ... @@ -584,9 +584,8 @@ 584 584 [[image:image-20220524165623-38.png]] 585 585 586 586 476 +5. Add the plugin and run the plugin. 587 587 588 -(% style="color:blue" %)**5. Add the plugin and run the plugin.** 589 - 590 590 ((( 591 591 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: 592 592 ))) ... ... @@ -622,61 +622,11 @@ 622 622 Finish. 623 623 624 624 625 -= 7.Howtostore/getall data traffic for a specific sensor, includingraw payload, and uplink/ downlink history.=513 += 6. Trouble Shooting = 626 626 515 +== 6.1 MIC Mismatch or MIC Failed == 627 627 628 -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. 629 - 630 -This example will be shown how to store/get all the data in two ways: 631 - 632 -**//1). Chirpstack ~-~-> Node-red//** 633 - 634 - 635 -[[image:image-20221012184501-1.png]] 636 - 637 - 638 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file 639 - 640 -[[image:image-20221012174220-2.png]] 641 - 642 - 643 -[[image:image-20221012184655-3.png||height="395" width="1049"]] 644 - 645 - 646 -**Each message is continuously logged to a specified file** 647 - 648 -[[image:image-20221012174352-3.png]] 649 - 650 - 651 -**//2). MQTT Sub//** 652 - 653 -If you don't want to store the information via node-red, you can get the output via the subscribe command. 654 - 655 - 656 -**If connecting from the same machine, you can use the following command to receive data:** 657 - 658 -(% class="box infomessage" %) 659 659 ((( 660 -mosquitto_sub -h localhost -t "application/#" -v 661 -))) 662 - 663 - 664 -**Different host** 665 - 666 -(% class="box infomessage" %) 667 -((( 668 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 669 -))) 670 - 671 -[[image:image-20221012173639-1.png]] 672 - 673 - 674 -= 8. Trouble Shooting = 675 - 676 -== 8.1 MIC Mismatch or MIC Failed == 677 - 678 - 679 -((( 680 680 When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. 681 681 ))) 682 682
- 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