Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
Uploaded new attachment "image-20230702100930-11.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 7 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Bei - Content
-
... ... @@ -20,7 +20,7 @@ 20 20 21 21 **1) Have a Chirstack Server.** 22 22 23 -[[image:image-202 30821114047-4.png||height="524" width="990"]]23 +[[image:image-20220525100058-1.png]] 24 24 25 25 ChirpStack home page 26 26 ... ... @@ -37,54 +37,12 @@ 37 37 ))) 38 38 ))) 39 39 40 -= 2. Node usage introduction = 41 41 42 -= =2.1RegisterNode==41 += 2. Semtech UDP = 43 43 44 -Step 1 :Addapplication43 +== 2.1 Step 1. Add the Network-servers == 45 45 46 -[[image:image-20230702094608-1.png||height="537" width="1015"]] 47 47 48 -Step 2:Fill name 49 - 50 -[[image:image-20230702094852-2.png]] 51 - 52 -Step4 :Add device profile 53 - 54 -[[image:image-20230702095114-4.png||height="448" width="1061"]] 55 - 56 - 57 -Step5 :Configure your device profile 58 - 59 -[[image:image-20230702095557-5.png||height="648" width="1121"]] 60 - 61 -Does node support class-c 62 - 63 -[[image:image-20230702095641-6.png||height="349" width="1114"]] 64 - 65 -Add node's decoder 66 - 67 -[[image:image-20230702095827-7.png||height="490" width="1138"]] 68 - 69 - 70 -Step6 :add device 71 - 72 -[[image:image-20230702094944-3.png||height="439" width="1153"]] 73 - 74 - 75 - 76 -[[image:image-20230702100312-8.png||height="585" width="1176"]] 77 - 78 -[[image:image-20230702100543-10.png||height="313" width="1099"]] 79 - 80 -[[image:image-20230702100930-11.png||height="613" width="1098"]] 81 - 82 - 83 -= 3. Semtech UDP for ChirpStack v3 = 84 - 85 -== 3.1 Step 1. Add the Network-servers == 86 - 87 - 88 88 The network-Servers address varies depending on the ChirpStack server setup environment 89 89 90 90 (% class="box" %) ... ... @@ -102,7 +102,7 @@ 102 102 Add the Network-servers 103 103 104 104 105 -== 3.2 Step 2. Create Gateway-profiles ==63 +== 2.2 Step 2. Create Gateway-profiles == 106 106 107 107 108 108 [[image:image-20220531171651-2.png||height="632" width="1264"]](% style="display:none" %) ... ... @@ -110,7 +110,7 @@ 110 110 Create Gateway-profiles 111 111 112 112 113 -== 3.3 Step 3. Create Service-profiles ==71 +== 2.3 Step 3. Create Service-profiles == 114 114 115 115 116 116 [[image:image-20220531171809-3.png||height="761" width="1265"]] ... ... @@ -125,7 +125,7 @@ 125 125 If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %) 126 126 127 127 128 -== 3.4 Step 4. Add the gateway ==86 +== 2.4 Step 4. Add the gateway == 129 129 130 130 131 131 The example gateway id is: a840411e96744150 ... ... @@ -147,7 +147,7 @@ 147 147 Configure the gateway 148 148 149 149 150 -== 3.5 Step 5. Checking gateway Status ==108 +== 2.5 Step 5. Checking gateway Status == 151 151 152 152 153 153 [[image:image-20220531172158-6.png||height="704" width="1167"]](% style="display:none" %) ... ... @@ -160,26 +160,12 @@ 160 160 161 161 gateway Status 162 162 163 -= 4. Semtech UDP for ChirpStack v4 = 164 164 122 += 3. Gateway Registration for Basics Station = 165 165 166 -== 4.1Step 1. Addthegateway==124 +== 3.1 Introduction == 167 167 168 -[[image:image-20230926092907-1.png||height="598" width="1007"]] 169 169 170 - 171 -[[image:image-20230926093057-2.png||height="541" width="1002"]] 172 - 173 - 174 -== 4.2 Step 2. Checking gateway Status == 175 - 176 -[[image:image-20230926093233-3.png||height="581" width="1018"]] 177 - 178 -= 5. Gateway Registration for Basics Station = 179 - 180 -== 5.1 Introduction == 181 - 182 - 183 183 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. 184 184 185 185 ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation. ... ... @@ -200,13 +200,13 @@ 200 200 A gateway that can access the internet normally 201 201 202 202 203 -== 5.2 Add Gateway ==147 +== 3.2 Add Gateway == 204 204 205 205 206 206 [[image:image-20220524164205-10.png]] 207 207 208 208 209 -== 5.3 Access the gateway GUI ==153 +== 3.3 Access the gateway GUI == 210 210 211 211 212 212 Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station ... ... @@ -220,7 +220,7 @@ 220 220 ((( 221 221 Service Provider ~-~-> Choose the ChirpStack/Senet ~-~- Basic Station 222 222 223 -LNS URI ~-~-> Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:4 43 or ws:~/~/xxxx.chirpstack.com:3001167 +LNS URI ~-~-> Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:433 or ws:~/~/xxxx.chirpstack.com:3001 224 224 225 225 LNS TLS trust ~-~-> Upload the TLS Certificate 226 226 ))) ... ... @@ -229,13 +229,13 @@ 229 229 [[image:image-20220524164341-12.png]] 230 230 231 231 232 -== 5.4 Start Station ==176 +== 3.4 Start Station == 233 233 234 234 235 235 When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack. 236 236 237 237 238 -== 5.5 Successful Connection ==182 +== 3.5 Successful Connection == 239 239 240 240 241 241 If user completes the above steps, which will see live date in the ChirpStack. ... ... @@ -243,7 +243,7 @@ 243 243 [[image:image-20220524164448-13.png]] 244 244 245 245 246 -== 5.6 Trouble Shooting ==190 +== 3.6 Trouble Shooting == 247 247 248 248 249 249 User can check the station log in the logread/system log page. ... ... @@ -256,7 +256,7 @@ 256 256 [[image:image-20220531172857-9.png]] 257 257 258 258 259 -= 6. How the gateway connects to Chirpstack v3 via gateway-bridge =203 += 4. How the gateway connects to Chirpstack v3 via gateway-bridge = 260 260 261 261 262 262 (% style="color:blue" %)**Below list the support products and Requirements:** ... ... @@ -277,7 +277,7 @@ 277 277 The following example does not have configuration certificates: 278 278 279 279 280 -== 6.1 Configure Packet Forwarder ==224 +== 4.1 Configure Packet Forwarder == 281 281 282 282 283 283 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 ... ... @@ -295,7 +295,7 @@ 295 295 [[image:image-20221222114220-2.png||height="748" width="931"]] 296 296 297 297 298 -== 6.2 Configuring gateway frequency ==242 +== 4.2 Configuring gateway frequency == 299 299 300 300 301 301 (% style="color:red" %)**Note: Gateway frequencies must match** ... ... @@ -303,7 +303,7 @@ 303 303 [[image:image-20221222134830-3.png||height="408" width="923"]] 304 304 305 305 306 -== 6.3 Generate and modify the gateway-bridge configuration file ==250 +== 4.3 Generate and modify the gateway-bridge configuration file == 307 307 308 308 309 309 **1)Generate the gateway-bridge configuration file** ... ... @@ -330,7 +330,7 @@ 330 330 [[image:image-20230415165254-1.png||height="583" width="956"]] 331 331 332 332 333 -== 6.4 Debug ==277 +== 4.4 Debug == 334 334 335 335 336 336 After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection ... ... @@ -353,7 +353,7 @@ 353 353 More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]** 354 354 355 355 356 -== 6.5 (Re)start and stop gateway-bridge ==300 +== 4.5 (Re)start and stop gateway-bridge == 357 357 358 358 359 359 Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: ... ... @@ -374,7 +374,7 @@ 374 374 ))) 375 375 376 376 377 -= 7. How the gateway connects to Chirpstack v4 via gateway-bridge =321 += 5. How the gateway connects to Chirpstack v4 via gateway-bridge = 378 378 379 379 380 380 (% style="color:blue" %)**Below list the support products and Requirements:** ... ... @@ -392,7 +392,7 @@ 392 392 A gateway that can access the internet normally 393 393 394 394 395 -== 7.1 Configure Packet Forwarder ==339 +== 5.1 Configure Packet Forwarder == 396 396 397 397 398 398 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 ... ... @@ -410,7 +410,7 @@ 410 410 [[image:image-20221222114220-2.png||height="748" width="931"]] 411 411 412 412 413 -== 7.2 Configuring gateway frequency ==357 +== 5.2 Configuring gateway frequency == 414 414 415 415 416 416 (% style="color:red" %)**Note: Gateway frequencies must match** ... ... @@ -418,7 +418,7 @@ 418 418 [[image:image-20221222134830-3.png||height="408" width="923"]] 419 419 420 420 421 -== 7.3 Modify the gateway-bridge configuration file ==365 +== 5.3 Modify the gateway-bridge configuration file == 422 422 423 423 424 424 Run the gateway command line command to modify the gateway-bridge configuration file: ... ... @@ -439,7 +439,7 @@ 439 439 After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 440 440 441 441 442 -== 7.4 (Re)start and stop gateway-bridge ==386 +== 5.4 (Re)start and stop gateway-bridge == 443 443 444 444 445 445 Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: ... ... @@ -460,7 +460,7 @@ 460 460 ))) 461 461 462 462 463 -== 7.5 Successful Connection ==407 +== 5.5 Successful Connection == 464 464 465 465 466 466 [[image:image-20221222141754-5.png||height="488" width="1150"]] ... ... @@ -469,9 +469,9 @@ 469 469 [[image:image-20221222141830-6.png||height="582" width="1153"]] 470 470 471 471 472 -= 8. Downlink =416 += 6. Downlink = 473 473 474 -== 8.1 Convert HEX to Base64 ==418 +== 6.1 Convert HEX to Base64 == 475 475 476 476 477 477 (% 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.** ... ... @@ -487,7 +487,7 @@ 487 487 [[image:image-20221010193621-2.png]] 488 488 489 489 490 -== 8.2 Chirpstack Downlink Note ==434 +== 6.2 Chirpstack Downlink Note == 491 491 492 492 493 493 [[image:image-20220601102543-2.png]] ... ... @@ -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 ==455 +== 6.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 ... ... @@ -625,7 +625,7 @@ 625 625 ))) 626 626 627 627 628 -== 8.4 Add the decode function in Chirpstack for the payload ==572 +== 6.4 Add the decode function in Chirpstack for the payload == 629 629 630 630 631 631 User enters the payload code according to the steps. ... ... @@ -643,7 +643,7 @@ 643 643 [[image:image-20220531174046-19.png]] 644 644 645 645 646 -= 9. Multiply Uplink in ChirpStack =590 += 7. Multiply Uplink in ChirpStack = 647 647 648 648 649 649 ((( ... ... @@ -686,7 +686,7 @@ 686 686 [[image:image-20220601102430-1.png||height="598" width="1319"]] 687 687 688 688 689 -== 9.1 Solution ==633 +== 7.1 Solution == 690 690 691 691 692 692 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]] ... ... @@ -808,7 +808,7 @@ 808 808 Finish. 809 809 810 810 811 -= 10. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =755 += 8. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 812 812 813 813 814 814 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. ... ... @@ -856,7 +856,7 @@ 856 856 857 857 [[image:image-20221012173639-1.png]] 858 858 859 -= 11. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =803 += 9. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 = 860 860 861 861 862 862 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: ... ... @@ -867,7 +867,7 @@ 867 867 Below are the steps to plot the sensor data on LPS8v2 Node-Red. 868 868 869 869 870 -== 11.1 Link Node-Red to Local ChirpStack ==814 +== 9.1 Link Node-Red to Local ChirpStack == 871 871 872 872 873 873 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"]]** ... ... @@ -901,7 +901,7 @@ 901 901 [[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"]] 902 902 903 903 904 -== 11.2 Check result. ==848 +== 9.2 Check result. == 905 905 906 906 907 907 Users can check logs by adding debug. ... ... @@ -911,9 +911,9 @@ 911 911 [[image:image-20230529150923-1.png||height="424" width="1118"]] 912 912 913 913 914 -= 1 2. Trouble Shooting =858 += 10. Trouble Shooting = 915 915 916 -== 1 2.1 MIC Mismatch or MIC Failed ==860 +== 10.1 MIC Mismatch or MIC Failed == 917 917 918 918 919 919 ((( ... ... @@ -923,31 +923,5 @@ 923 923 ((( 924 924 Under normal circumstances, users need to change the APPKEY to solve this problem. 925 925 926 - 927 -== 12.2 The node is very close to the gateway, but the signal is poor == 928 - 929 -If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink 930 - 931 -Like that:Both 905.1Mhz and 902.3Mhz appear on uplink 932 - But they belong to Subband1 and Subband2 of US915 respectively 933 - 934 -Cause: The server and the gateway use different frequency bands (the server uses Subband1, and the gateway uses Subband2) 935 - 936 - In server side, it shows the frequency is 905.1Mhz, which is sub-band2. But the RSSI is very low, Because this is not a signal in 905.1Mhz, it is on 902.3Mhz, the signal is too strong and appear a noise in 905.1Mhz. 937 - 938 -How to check the frequency band used by the server: 939 - 940 -You can view the information sent by the server: ch_mask in Unconfirmdedatadown 941 - 942 -[[image:image-20230821113255-1.png]] 943 - 944 -According to lorawan's protocol, your first ch_mask is 7 for ChMaskCntl = 7 then 125 kHz channels are disabled. Simultaneously the channels 64 to 71 are set according to the ChMask bit mask. 945 - 946 -[[image:image-20230821113539-2.png]] 947 - 948 -In the second message, the channel 0~~7 is true, which means that your server is using subband2. 949 - 950 -[[image:image-20230821113618-3.png]] 951 - 952 -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]] 870 + 953 953 )))
- image-20230821113255-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -115.7 KB - Content
- image-20230821113539-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -71.1 KB - Content
- image-20230821113618-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -19.0 KB - Content
- image-20230821114047-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -125.6 KB - Content
- image-20230926092907-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.0 KB - Content
- image-20230926093057-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -69.6 KB - Content
- image-20230926093233-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -95.8 KB - Content