Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
Uploaded new attachment "image-20230926093233-3.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Kilight - Content
-
... ... @@ -37,28 +37,24 @@ 37 37 ))) 38 38 ))) 39 39 40 - 41 41 = 2. Node usage introduction = 42 42 43 43 == 2.1 Register Node == 44 44 44 +Step 1: Add application 45 45 46 -**Step 1: Add application** 47 - 48 48 [[image:image-20230702094608-1.png||height="537" width="1015"]] 49 49 48 +Step 2:Fill name 50 50 51 -**Step 2:Fill name** 52 - 53 53 [[image:image-20230702094852-2.png]] 54 54 52 +Step4 :Add device profile 55 55 56 -**Step3 :Add device profile** 57 - 58 58 [[image:image-20230702095114-4.png||height="448" width="1061"]] 59 59 60 60 61 - **Step4:Configure your device profile**57 +Step5 :Configure your device profile 62 62 63 63 [[image:image-20230702095557-5.png||height="648" width="1121"]] 64 64 ... ... @@ -71,21 +71,20 @@ 71 71 [[image:image-20230702095827-7.png||height="490" width="1138"]] 72 72 73 73 74 - **Step5:add device**70 +Step6 :add device 75 75 76 76 [[image:image-20230702094944-3.png||height="439" width="1153"]] 77 77 78 78 79 -[[image:image-20230702100312-8.png||height="550" width="1106"]] 80 80 76 +[[image:image-20230702100312-8.png||height="585" width="1176"]] 81 81 82 82 [[image:image-20230702100543-10.png||height="313" width="1099"]] 83 83 84 - 85 85 [[image:image-20230702100930-11.png||height="613" width="1098"]] 86 86 87 87 88 -= 3. Semtech UDP for ChirpStack v3=83 += 3. Semtech UDP = 89 89 90 90 == 3.1 Step 1. Add the Network-servers == 91 91 ... ... @@ -101,6 +101,7 @@ 101 101 102 102 (% style="color:red" %)**If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.** 103 103 99 + 104 104 [[image:image-20220531171609-1.png||height="638" width="1268"]](% style="display:none" %) 105 105 106 106 Add the Network-servers ... ... @@ -136,6 +136,8 @@ 136 136 137 137 ((( 138 138 (% style="color:red" %)**Note : The Gateway EUI and server addresses must match the ChirpStack configuration.** 135 + 136 + 139 139 ))) 140 140 141 141 [[image:image-20220531171923-4.png||height="745" width="1253"]](% style="display:none" %) ... ... @@ -143,6 +143,7 @@ 143 143 Add the gateway 144 144 145 145 144 + 146 146 [[image:image-20220531172031-5.png]] 147 147 148 148 Configure the gateway ... ... @@ -162,26 +162,11 @@ 162 162 gateway Status 163 163 164 164 165 -= 4. SemtechUDPforChirpStackv4=164 += 4. Gateway Registration for Basics Station = 166 166 167 -== 4.1 Step 1. Addthegateway==166 +== 4.1 Introduction == 168 168 169 169 170 -[[image:image-20230926092907-1.png||height="598" width="1007"]] 171 - 172 - 173 -[[image:image-20230926093057-2.png||height="541" width="1002"]] 174 - 175 - 176 -== 4.2 Step 2. Checking gateway Status == 177 - 178 -[[image:image-20230926093233-3.png||height="581" width="1018"]] 179 - 180 -= 5. Gateway Registration for Basics Station = 181 - 182 -== 5.1 Introduction == 183 - 184 - 185 185 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. 186 186 187 187 ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation. ... ... @@ -202,13 +202,13 @@ 202 202 A gateway that can access the internet normally 203 203 204 204 205 -== 5.2 Add Gateway ==189 +== 4.2 Add Gateway == 206 206 207 207 208 208 [[image:image-20220524164205-10.png]] 209 209 210 210 211 -== 5.3 Access the gateway GUI ==195 +== 4.3 Access the gateway GUI == 212 212 213 213 214 214 Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station ... ... @@ -231,13 +231,13 @@ 231 231 [[image:image-20220524164341-12.png]] 232 232 233 233 234 -== 5.4 Start Station ==218 +== 4.4 Start Station == 235 235 236 236 237 237 When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack. 238 238 239 239 240 -== 5.5 Successful Connection ==224 +== 4.5 Successful Connection == 241 241 242 242 243 243 If user completes the above steps, which will see live date in the ChirpStack. ... ... @@ -245,7 +245,7 @@ 245 245 [[image:image-20220524164448-13.png]] 246 246 247 247 248 -== 5.6 Trouble Shooting ==232 +== 4.6 Trouble Shooting == 249 249 250 250 251 251 User can check the station log in the logread/system log page. ... ... @@ -258,7 +258,7 @@ 258 258 [[image:image-20220531172857-9.png]] 259 259 260 260 261 -= 6. How the gateway connects to Chirpstack v3 via gateway-bridge =245 += 5. How the gateway connects to Chirpstack v3 via gateway-bridge = 262 262 263 263 264 264 (% style="color:blue" %)**Below list the support products and Requirements:** ... ... @@ -279,7 +279,7 @@ 279 279 The following example does not have configuration certificates: 280 280 281 281 282 -== 6.1 Configure Packet Forwarder ==266 +== 5.1 Configure Packet Forwarder == 283 283 284 284 285 285 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 ... ... @@ -297,7 +297,7 @@ 297 297 [[image:image-20221222114220-2.png||height="748" width="931"]] 298 298 299 299 300 -== 6.2 Configuring gateway frequency ==284 +== 5.2 Configuring gateway frequency == 301 301 302 302 303 303 (% style="color:red" %)**Note: Gateway frequencies must match** ... ... @@ -305,7 +305,7 @@ 305 305 [[image:image-20221222134830-3.png||height="408" width="923"]] 306 306 307 307 308 -== 6.3 Generate and modify the gateway-bridge configuration file ==292 +== 5.3 Generate and modify the gateway-bridge configuration file == 309 309 310 310 311 311 **1)Generate the gateway-bridge configuration file** ... ... @@ -332,7 +332,7 @@ 332 332 [[image:image-20230415165254-1.png||height="583" width="956"]] 333 333 334 334 335 -== 6.4 Debug ==319 +== 5.4 Debug == 336 336 337 337 338 338 After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection ... ... @@ -355,7 +355,7 @@ 355 355 More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]** 356 356 357 357 358 -== 6.5 (Re)start and stop gateway-bridge ==342 +== 5.5 (Re)start and stop gateway-bridge == 359 359 360 360 361 361 Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: ... ... @@ -376,7 +376,7 @@ 376 376 ))) 377 377 378 378 379 -= 7. How the gateway connects to Chirpstack v4 via gateway-bridge =363 += 6. How the gateway connects to Chirpstack v4 via gateway-bridge = 380 380 381 381 382 382 (% style="color:blue" %)**Below list the support products and Requirements:** ... ... @@ -394,7 +394,7 @@ 394 394 A gateway that can access the internet normally 395 395 396 396 397 -== 7.1 Configure Packet Forwarder ==381 +== 6.1 Configure Packet Forwarder == 398 398 399 399 400 400 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 ... ... @@ -412,7 +412,7 @@ 412 412 [[image:image-20221222114220-2.png||height="748" width="931"]] 413 413 414 414 415 -== 7.2 Configuring gateway frequency ==399 +== 6.2 Configuring gateway frequency == 416 416 417 417 418 418 (% style="color:red" %)**Note: Gateway frequencies must match** ... ... @@ -420,7 +420,7 @@ 420 420 [[image:image-20221222134830-3.png||height="408" width="923"]] 421 421 422 422 423 -== 7.3 Modify the gateway-bridge configuration file ==407 +== 6.3 Modify the gateway-bridge configuration file == 424 424 425 425 426 426 Run the gateway command line command to modify the gateway-bridge configuration file: ... ... @@ -435,7 +435,6 @@ 435 435 436 436 [[image:image-20221222140203-4.png||height="875" width="806"]] 437 437 438 - 439 439 [[image:image-20221230094246-1.png||height="768" width="783"]] 440 440 441 441 (% class="wikigeneratedid" id="H" %) ... ... @@ -442,7 +442,7 @@ 442 442 After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 443 443 444 444 445 -== 7.4 (Re)start and stop gateway-bridge ==428 +== 6.4 (Re)start and stop gateway-bridge == 446 446 447 447 448 448 Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: ... ... @@ -463,7 +463,7 @@ 463 463 ))) 464 464 465 465 466 -== 7.5 Successful Connection ==449 +== 6.5 Successful Connection == 467 467 468 468 469 469 [[image:image-20221222141754-5.png||height="488" width="1150"]] ... ... @@ -472,24 +472,27 @@ 472 472 [[image:image-20221222141830-6.png||height="582" width="1153"]] 473 473 474 474 475 -= 8. Downlink =458 += 7. Downlink = 476 476 477 -== =8.1 ChirpstackDownlinkNote ===460 +== 7.1 Convert HEX to Base64 == 478 478 479 -==== 8.1.1 Select HEX format for downlink ==== 480 480 463 +(% 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.** 481 481 482 - (% style="color:red" %)**Note: The end node user manualprovidesHEXformatfthedownlink commands, so userscandirectly select HEX formatdownlink.**465 +**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:** 483 483 484 -[[image:image-202 31108140540-1.png||height="502" width="973"]]467 +[[image:image-20221010193350-1.png]] 485 485 486 486 487 487 471 +**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]** 488 488 473 +[[image:image-20221010193621-2.png]] 489 489 490 -== 8.2 Chirpstack Downlink Note == 491 491 476 +== 7.2 Chirpstack Downlink Note == 492 492 478 + 493 493 [[image:image-20220601102543-2.png]] 494 494 495 495 **Convert the data to Base64** ... ... @@ -508,7 +508,7 @@ 508 508 **Make sure the RX2DR is the same in the end node** 509 509 510 510 511 -== 8.3 Loraserver Downlink Note ==497 +== 7.3 Loraserver Downlink Note == 512 512 513 513 514 514 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End ... ... @@ -558,11 +558,13 @@ 558 558 **MQTT Connect to ChirpStack** 559 559 560 560 547 +**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB** 561 561 562 -((( 563 -Downlink payload encode javescript code. 549 +[[image:image-20220531173658-14.png]] 564 564 565 -We can run the following Javsscript code on the site: 551 + 552 +((( 553 +Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码: 566 566 ))) 567 567 568 568 (% class="box" %) ... ... @@ -623,7 +623,7 @@ 623 623 ))) 624 624 625 625 626 -== 8.4 Add the decode function in Chirpstack for the payload ==614 +== 7.4 Add the decode function in Chirpstack for the payload == 627 627 628 628 629 629 User enters the payload code according to the steps. ... ... @@ -641,7 +641,7 @@ 641 641 [[image:image-20220531174046-19.png]] 642 642 643 643 644 -= 9. Multiply Uplink in ChirpStack =632 += 8. Multiply Uplink in ChirpStack = 645 645 646 646 647 647 ((( ... ... @@ -681,16 +681,19 @@ 681 681 682 682 **Duplicate transmission in short time** 683 683 684 -[[image:image-20220601102430-1.png||height="5 08" width="1120"]]672 +[[image:image-20220601102430-1.png||height="598" width="1319"]] 685 685 686 686 687 -== 9.1 Solution ==675 +== 8.1 Solution == 688 688 689 689 690 690 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]] 691 691 680 + 692 692 ((( 693 693 (% 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.** 683 + 684 + 694 694 ))) 695 695 696 696 [[image:image-20220525104532-24.png]] ... ... @@ -803,7 +803,7 @@ 803 803 Finish. 804 804 805 805 806 -= 10. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =797 += 9. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 807 807 808 808 809 809 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. ... ... @@ -813,7 +813,7 @@ 813 813 (% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//** 814 814 815 815 816 -[[image:image-20221012184501-1.png ||height="608" width="1041"]]807 +[[image:image-20221012184501-1.png]] 817 817 818 818 819 819 Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file ... ... @@ -849,12 +849,11 @@ 849 849 **mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v** 850 850 ))) 851 851 852 -[[image:image-20221012173639-1.png ||height="273" width="1206"]]843 +[[image:image-20221012173639-1.png]] 853 853 845 += 10. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 = 854 854 855 -= 11. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 = 856 856 857 - 858 858 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: 859 859 860 860 * LHT65N register on LPS8v2 Built-In ChirpStack server already ... ... @@ -863,7 +863,7 @@ 863 863 Below are the steps to plot the sensor data on LPS8v2 Node-Red. 864 864 865 865 866 -== 1 1.1 Link Node-Red to Local ChirpStack ==856 +== 10.1 Link Node-Red to Local ChirpStack == 867 867 868 868 869 869 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"]]** ... ... @@ -890,7 +890,7 @@ 890 890 [[image:image-20230527144206-2.png||height="590" width="1136"]] 891 891 892 892 893 -(% style="color:blue" %) **3.****Finally, click "Update" and Deploy**883 +(% style="color:blue" %)3. **Finally, click "Update" and Deploy** 894 894 895 895 "Connected" indicates that the Link Node-red to Local Chirpstack is normal. 896 896 ... ... @@ -897,7 +897,7 @@ 897 897 [[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"]] 898 898 899 899 900 -== 1 1.2 Check result. ==890 +== 10.2 Check result. == 901 901 902 902 903 903 Users can check logs by adding debug. ... ... @@ -907,9 +907,9 @@ 907 907 [[image:image-20230529150923-1.png||height="424" width="1118"]] 908 908 909 909 910 -= 1 2. Trouble Shooting =900 += 11. Trouble Shooting = 911 911 912 -== 1 2.1 MIC Mismatch or MIC Failed ==902 +== 11.1 MIC Mismatch or MIC Failed == 913 913 914 914 915 915 ((( ... ... @@ -920,9 +920,8 @@ 920 920 Under normal circumstances, users need to change the APPKEY to solve this problem. 921 921 922 922 923 -== 1 2.2 The node is very close to the gateway, but the signal is poor ==913 +== 11.2 The node is very close to the gateway, but the signal is poor == 924 924 925 - 926 926 If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink 927 927 928 928 Like that:Both 905.1Mhz and 902.3Mhz appear on uplink ... ... @@ -946,7 +946,5 @@ 946 946 947 947 [[image:image-20230821113618-3.png]] 948 948 949 -**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]]** 950 - 951 - 938 +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]] 952 952 )))
- image-20231108140540-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.3 KB - Content