Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
Uploaded new attachment "image-20221012174352-3.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 5 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Xiaoye - Content
-
... ... @@ -127,6 +127,7 @@ 127 127 128 128 = 3. Gateway Registration for Basics Station = 129 129 130 + 130 130 == 3.1 Introduction == 131 131 132 132 ... ... @@ -150,6 +150,7 @@ 150 150 A gateway that can access the internet normally 151 151 152 152 154 + 153 153 == 3.2 Add Gateway == 154 154 155 155 ... ... @@ -193,6 +193,7 @@ 193 193 [[image:image-20220524164448-13.png]] 194 194 195 195 198 + 196 196 == 3.6 Trouble Shooting == 197 197 198 198 ... ... @@ -209,43 +209,41 @@ 209 209 210 210 = 4. Downlink = 211 211 215 +(% class="wikigeneratedid" %) 212 212 == 4.1 Convert HEX to Base64 == 213 213 214 - 215 215 (% 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.** 216 216 217 - **[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**220 +[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]: 218 218 219 219 [[image:image-20221010193350-1.png]] 220 220 221 221 225 +[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]] 222 222 223 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]** 224 - 225 225 [[image:image-20221010193621-2.png]] 226 226 227 227 230 + 228 228 == 4.2 Chirpstack Downlink Note == 229 229 230 230 231 231 [[image:image-20220601102543-2.png]] 232 232 233 - **Convert the data to Base64**236 +Convert the data to Base64 234 234 235 -(% style="display:none" %) (%%) 236 236 239 +[[image:image-20220531173236-10.png]] 237 237 238 - [[image:image-20220531173236-10.png||height="597"width="1215"]]241 +Check ChripStack downlink DataRate 239 239 240 -**Check ChripStack downlink DataRate** 241 241 242 - 243 - 244 244 [[image:image-20220525101326-11.png]] 245 245 246 - **Make sure the RX2DR is the same in the end node**246 +Make sure the RX2DR is the same in the end node 247 247 248 248 249 + 249 249 == 4.3 Loraserver Downlink Note == 250 250 251 251 ... ... @@ -266,7 +266,7 @@ 266 266 [[image:image-20220531173419-11.png]] 267 267 268 268 ((( 269 - **MQTT Connect to ChirpStack**270 +MQTT Connect to ChirpStack 270 270 271 271 272 272 ... ... @@ -293,10 +293,10 @@ 293 293 294 294 [[image:image-20220531173519-12.png]] 295 295 296 - **MQTT Connect to ChirpStack**297 +MQTT Connect to ChirpStack 297 297 298 298 299 - **If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**300 +If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB 300 300 301 301 [[image:image-20220531173658-14.png]] 302 302 ... ... @@ -318,15 +318,15 @@ 318 318 { 319 319 if(sha1[n] >= 'A' && sha1[n] <= 'Z') 320 320 { 321 - ascv = sha1.charCodeAt( 322 + ascv = sha1.charCodeAt(n) - 55; 322 322 } 323 323 else if(sha1[n] >= 'a' && sha1[n] <= 'z') 324 324 { 325 - ascv = sha1.charCodeAt( 326 + ascv = sha1.charCodeAt(n) - 87; 326 326 } 327 327 else 328 328 { 329 - ascv = sha1.charCodeAt( 330 + ascv = sha1.charCodeAt(n) - 48; 330 330 } 331 331 \\ bit_arr = (bit_arr << 4) | ascv; 332 332 bit_num += 4; ... ... @@ -369,7 +369,7 @@ 369 369 370 370 User enters the payload code according to the steps. 371 371 372 -[[image:image-20220531173754-15.png ||height="474" width="1334"]]373 +[[image:image-20220531173754-15.png]] 373 373 374 374 375 375 [[image:image-20220531173856-16.png]] ... ... @@ -380,6 +380,7 @@ 380 380 [[image:image-20220531174046-19.png]] 381 381 382 382 384 + 383 383 = 5. Multiply Uplink in ChirpStack = 384 384 385 385 ... ... @@ -393,7 +393,7 @@ 393 393 394 394 ))) 395 395 396 -[[image:image-20220526091912-7.png ||height="241" width="1336"]]398 +[[image:image-20220526091912-7.png]] 397 397 398 398 399 399 ((( ... ... @@ -418,9 +418,9 @@ 418 418 419 419 420 420 421 - **Duplicate transmission in short time**423 +Duplicate transmission in short time 422 422 423 -[[image:image-20220601102430-1.png ||height="598" width="1319"]]425 +[[image:image-20220601102430-1.png]] 424 424 425 425 426 426 ... ... @@ -546,61 +546,13 @@ 546 546 Finish. 547 547 548 548 549 -= 6. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 550 550 552 += 6. Trouble Shooting = 551 551 552 - Alldatais published to theMQTTtopics. if you wantto store/get thedata, you would have to createanMQTThandler andstore the data yourself.554 +== 6.1 MIC Mismatch or MIC Failed == 553 553 554 -This example will be shown how to store/get all the data in two ways: 555 555 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" %) 583 583 ((( 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 -((( 604 604 When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. 605 605 ))) 606 606
- 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