Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.Xiao ye1 +XWiki.Xiaoling - Content
-
... ... @@ -127,7 +127,6 @@ 127 127 128 128 = 3. Gateway Registration for Basics Station = 129 129 130 - 131 131 == 3.1 Introduction == 132 132 133 133 ... ... @@ -151,7 +151,6 @@ 151 151 A gateway that can access the internet normally 152 152 153 153 154 - 155 155 == 3.2 Add Gateway == 156 156 157 157 ... ... @@ -195,7 +195,6 @@ 195 195 [[image:image-20220524164448-13.png]] 196 196 197 197 198 - 199 199 == 3.6 Trouble Shooting == 200 200 201 201 ... ... @@ -212,41 +212,43 @@ 212 212 213 213 = 4. Downlink = 214 214 215 -(% class="wikigeneratedid" %) 216 216 == 4.1 Convert HEX to Base64 == 217 217 214 + 218 218 (% 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.** 219 219 220 -[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]: 217 +**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:** 221 221 222 222 [[image:image-20221010193350-1.png]] 223 223 224 224 225 -[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]] 226 226 223 +**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]** 224 + 227 227 [[image:image-20221010193621-2.png]] 228 228 229 229 230 - 231 231 == 4.2 Chirpstack Downlink Note == 232 232 233 233 234 234 [[image:image-20220601102543-2.png]] 235 235 236 -Convert the data to Base64 233 +**Convert the data to Base64** 237 237 235 +(% style="display:none" %) (%%) 238 238 239 -[[image:image-20220531173236-10.png]] 240 240 241 - Check ChripStackdownlink DataRate238 +[[image:image-20220531173236-10.png||height="597" width="1215"]] 242 242 240 +**Check ChripStack downlink DataRate** 243 243 244 -[[image:image-20220525101326-11.png]] 245 245 246 -Make sure the RX2DR is the same in the end node 247 247 244 +[[image:image-20220525101326-11.png]] 248 248 246 +**Make sure the RX2DR is the same in the end node** 249 249 248 + 250 250 == 4.3 Loraserver Downlink Note == 251 251 252 252 ... ... @@ -267,7 +267,7 @@ 267 267 [[image:image-20220531173419-11.png]] 268 268 269 269 ((( 270 -MQTT Connect to ChirpStack 269 +**MQTT Connect to ChirpStack** 271 271 272 272 273 273 ... ... @@ -294,10 +294,10 @@ 294 294 295 295 [[image:image-20220531173519-12.png]] 296 296 297 -MQTT Connect to ChirpStack 296 +**MQTT Connect to ChirpStack** 298 298 299 299 300 -If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB 299 +**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB** 301 301 302 302 [[image:image-20220531173658-14.png]] 303 303 ... ... @@ -319,15 +319,15 @@ 319 319 { 320 320 if(sha1[n] >= 'A' && sha1[n] <= 'Z') 321 321 { 322 - ascv = sha1.charCodeAt(n) - 55; 321 + ascv = sha1.charCodeAt( n ) - 55; 323 323 } 324 324 else if(sha1[n] >= 'a' && sha1[n] <= 'z') 325 325 { 326 - ascv = sha1.charCodeAt(n) - 87; 325 + ascv = sha1.charCodeAt( n ) - 87; 327 327 } 328 328 else 329 329 { 330 - ascv = sha1.charCodeAt(n) - 48; 329 + ascv = sha1.charCodeAt( n ) - 48; 331 331 } 332 332 \\ bit_arr = (bit_arr << 4) | ascv; 333 333 bit_num += 4; ... ... @@ -370,7 +370,7 @@ 370 370 371 371 User enters the payload code according to the steps. 372 372 373 -[[image:image-20220531173754-15.png]] 372 +[[image:image-20220531173754-15.png||height="474" width="1334"]] 374 374 375 375 376 376 [[image:image-20220531173856-16.png]] ... ... @@ -381,7 +381,6 @@ 381 381 [[image:image-20220531174046-19.png]] 382 382 383 383 384 - 385 385 = 5. Multiply Uplink in ChirpStack = 386 386 387 387 ... ... @@ -395,7 +395,7 @@ 395 395 396 396 ))) 397 397 398 -[[image:image-20220526091912-7.png]] 396 +[[image:image-20220526091912-7.png||height="241" width="1336"]] 399 399 400 400 401 401 ((( ... ... @@ -420,9 +420,9 @@ 420 420 421 421 422 422 423 -Duplicate transmission in short time 421 +**Duplicate transmission in short time** 424 424 425 -[[image:image-20220601102430-1.png]] 423 +[[image:image-20220601102430-1.png||height="598" width="1319"]] 426 426 427 427 428 428 ... ... @@ -548,13 +548,61 @@ 548 548 Finish. 549 549 550 550 549 += 6. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 551 551 552 -= 6. Trouble Shooting = 553 553 554 - ==6.1MICMismatch or MICFailed==552 +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. 555 555 554 +This example will be shown how to store/get all the data in two ways: 556 556 556 +**//1). Chirpstack ~-~-> Node-red//** 557 + 558 + 559 +[[image:image-20221012184501-1.png]] 560 + 561 + 562 +Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file 563 + 564 +[[image:image-20221012174220-2.png]] 565 + 566 + 567 +[[image:image-20221012184655-3.png||height="395" width="1049"]] 568 + 569 + 570 +**Each message is continuously logged to a specified file** 571 + 572 +[[image:image-20221012174352-3.png]] 573 + 574 + 575 +**//2). MQTT Sub//** 576 + 577 +If you don't want to store the information via node-red, you can get the output via the subscribe command. 578 + 579 + 580 +**If connecting from the same machine, you can use the following command to receive data:** 581 + 582 +(% class="box infomessage" %) 557 557 ((( 584 +mosquitto_sub -h localhost -t "application/#" -v 585 +))) 586 + 587 + 588 +**Different host** 589 + 590 +(% class="box infomessage" %) 591 +((( 592 +mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 593 +))) 594 + 595 +[[image:image-20221012173639-1.png]] 596 + 597 + 598 += 7. Trouble Shooting = 599 + 600 +== 7.1 MIC Mismatch or MIC Failed == 601 + 602 + 603 +((( 558 558 When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. 559 559 ))) 560 560
- image-20221012184501-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoye - Size
-
... ... @@ -1,0 +1,1 @@ 1 +91.3 KB - Content
- image-20221012184631-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoye - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.4 KB - Content
- image-20221012184655-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoye - Size
-
... ... @@ -1,0 +1,1 @@ 1 +45.4 KB - Content