Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
Uploaded new attachment "image-20221012173639-1.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.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 ... ... @@ -206,71 +206,47 @@ 206 206 [[image:image-20220531172857-9.png]] 207 207 208 208 209 -= 4. How the gateway connects to Chirpstack v4 via gateway-bridge = 210 210 213 += 4. Downlink = 211 211 212 -=== 4.1 Configure Packet Forwarder === 215 +(% class="wikigeneratedid" %) 216 +== 4.1 Convert HEX to Base64 == 213 213 214 -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 215 - 216 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 217 -* Make sure the following settings are set: 218 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 219 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1// 220 -** **Server port for upstream:** //1700// 221 -** **Server port for downstream:** //1700// 222 - 223 - Click **Save & Apply**. 224 - 225 -[[image:image-20221222114220-2.png||height="748" width="931"]] 226 - 227 - 228 -4.2 229 - 230 -[[image:image-20221222113302-1.png]] 231 - 232 -= 5. Downlink = 233 - 234 -== 5.1 Convert HEX to Base64 == 235 - 236 - 237 237 (% 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.** 238 238 239 - **[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**220 +[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]: 240 240 241 241 [[image:image-20221010193350-1.png]] 242 242 243 243 225 +[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]] 244 244 245 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]** 246 - 247 247 [[image:image-20221010193621-2.png]] 248 248 249 249 250 -== 5.2 Chirpstack Downlink Note == 251 251 231 +== 4.2 Chirpstack Downlink Note == 252 252 233 + 253 253 [[image:image-20220601102543-2.png]] 254 254 255 - **Convert the data to Base64**236 +Convert the data to Base64 256 256 257 -(% style="display:none" %) (%%) 258 258 239 +[[image:image-20220531173236-10.png]] 259 259 260 - [[image:image-20220531173236-10.png||height="597"width="1215"]]241 +Check ChripStack downlink DataRate 261 261 262 -**Check ChripStack downlink DataRate** 263 263 264 - 265 - 266 266 [[image:image-20220525101326-11.png]] 267 267 268 - **Make sure the RX2DR is the same in the end node**246 +Make sure the RX2DR is the same in the end node 269 269 270 270 271 -== 5.3 Loraserver Downlink Note == 272 272 250 +== 4.3 Loraserver Downlink Note == 273 273 252 + 274 274 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End 275 275 276 276 ((( ... ... @@ -288,7 +288,7 @@ 288 288 [[image:image-20220531173419-11.png]] 289 289 290 290 ((( 291 - **MQTT Connect to ChirpStack**270 +MQTT Connect to ChirpStack 292 292 293 293 294 294 ... ... @@ -315,10 +315,10 @@ 315 315 316 316 [[image:image-20220531173519-12.png]] 317 317 318 - **MQTT Connect to ChirpStack**297 +MQTT Connect to ChirpStack 319 319 320 320 321 - **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 322 322 323 323 [[image:image-20220531173658-14.png]] 324 324 ... ... @@ -340,15 +340,15 @@ 340 340 { 341 341 if(sha1[n] >= 'A' && sha1[n] <= 'Z') 342 342 { 343 - ascv = sha1.charCodeAt( 322 + ascv = sha1.charCodeAt(n) - 55; 344 344 } 345 345 else if(sha1[n] >= 'a' && sha1[n] <= 'z') 346 346 { 347 - ascv = sha1.charCodeAt( 326 + ascv = sha1.charCodeAt(n) - 87; 348 348 } 349 349 else 350 350 { 351 - ascv = sha1.charCodeAt( 330 + ascv = sha1.charCodeAt(n) - 48; 352 352 } 353 353 \\ bit_arr = (bit_arr << 4) | ascv; 354 354 bit_num += 4; ... ... @@ -391,7 +391,7 @@ 391 391 392 392 User enters the payload code according to the steps. 393 393 394 -[[image:image-20220531173754-15.png ||height="474" width="1334"]]373 +[[image:image-20220531173754-15.png]] 395 395 396 396 397 397 [[image:image-20220531173856-16.png]] ... ... @@ -402,9 +402,10 @@ 402 402 [[image:image-20220531174046-19.png]] 403 403 404 404 405 -= 6. Multiply Uplink in ChirpStack = 406 406 385 += 5. Multiply Uplink in ChirpStack = 407 407 387 + 408 408 ((( 409 409 nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data. 410 410 ))) ... ... @@ -415,7 +415,7 @@ 415 415 416 416 ))) 417 417 418 -[[image:image-20220526091912-7.png ||height="241" width="1336"]]398 +[[image:image-20220526091912-7.png]] 419 419 420 420 421 421 ((( ... ... @@ -440,13 +440,13 @@ 440 440 441 441 442 442 443 - **Duplicate transmission in short time**423 +Duplicate transmission in short time 444 444 445 -[[image:image-20220601102430-1.png ||height="598" width="1319"]]425 +[[image:image-20220601102430-1.png]] 446 446 447 447 448 448 449 -== 6.1 Solution ==429 +== 5.1 Solution == 450 450 451 451 452 452 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]] ... ... @@ -568,61 +568,13 @@ 568 568 Finish. 569 569 570 570 571 -= 7. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 572 572 552 += 6. Trouble Shooting = 573 573 574 - 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 == 575 575 576 -This example will be shown how to store/get all the data in two ways: 577 577 578 -**//1). Chirpstack ~-~-> Node-red//** 579 - 580 - 581 -[[image:image-20221012184501-1.png]] 582 - 583 - 584 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file 585 - 586 -[[image:image-20221012174220-2.png]] 587 - 588 - 589 -[[image:image-20221012184655-3.png||height="395" width="1049"]] 590 - 591 - 592 -**Each message is continuously logged to a specified file** 593 - 594 -[[image:image-20221012174352-3.png]] 595 - 596 - 597 -**//2). MQTT Sub//** 598 - 599 -If you don't want to store the information via node-red, you can get the output via the subscribe command. 600 - 601 - 602 -**If connecting from the same machine, you can use the following command to receive data:** 603 - 604 -(% class="box infomessage" %) 605 605 ((( 606 -mosquitto_sub -h localhost -t "application/#" -v 607 -))) 608 - 609 - 610 -**Different host** 611 - 612 -(% class="box infomessage" %) 613 -((( 614 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 615 -))) 616 - 617 -[[image:image-20221012173639-1.png]] 618 - 619 - 620 -= 8. Trouble Shooting = 621 - 622 -== 8.1 MIC Mismatch or MIC Failed == 623 - 624 - 625 -((( 626 626 When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. 627 627 ))) 628 628
- 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