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, 9 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,133 +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 -(% style="color:blue" %)**Below list the support products and Requirements:** 213 - 214 -1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]],[[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]] 215 -1. Firmware version since: [[Chirpstack-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]] 216 - 217 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge** 218 - 219 -Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]] 220 - 221 - 222 -(% style="color:blue" %)**What do you need to prepare** 223 - 224 -A gateway that can access the internet normally 225 - 226 -== 4.1 Configure Packet Forwarder == 227 - 228 -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 229 - 230 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 231 -* Make sure the following settings are set: 232 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 233 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1// 234 -** **Server port for upstream:** //1700// 235 -** **Server port for downstream:** //1700// 236 - 237 - Click **Save & Apply**. 238 - 239 -[[image:image-20221222114220-2.png||height="748" width="931"]] 240 - 241 - 242 -== 4.2 Configuring gateway frequency == 243 - 244 -Note: Gateway frequencies must match 245 - 246 -[[image:image-20221222134830-3.png||height="408" width="923"]] 247 - 248 - 249 -== 4.3 Modify the gateway-bridge configuration file == 250 - 251 - 252 -Run the gateway command line command to modify the gateway-bridge configuration file: 253 - 254 -(% class="box infomessage" %) 255 -((( 256 -root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 257 -))) 258 - 259 -[[image:image-20221222113302-1.png]] 260 - 261 -[[image:image-20221222140203-4.png||height="875" width="806"]] 262 - 263 - 264 -(% class="wikigeneratedid" id="H" %) 265 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 266 - 267 -== 4.3 (Re)start and stop gateway-bridge == 268 - 269 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: 270 - 271 -(% class="box infomessage" %) 272 -((( 273 -**# start** 274 - 275 -/etc/init.d/chirpstack-gateway-bridge start 276 - 277 -**# stop** 278 - 279 -/etc/init.d/chirpstack-gateway-bridge stop 280 - 281 -**# restart** 282 - 283 -/etc/init.d/chirpstack-gateway-bridge restart 284 -))) 285 - 286 - 287 287 (% class="wikigeneratedid" %) 288 -== 4. 4 SuccessfulConnection==216 +== 4.1 Convert HEX to Base64 == 289 289 290 -[[image:image-20221222141754-5.png||height="488" width="1150"]] 291 - 292 -[[image:image-20221222141830-6.png||height="582" width="1153"]] 293 - 294 -= 5. Downlink = 295 - 296 -== 5.1 Convert HEX to Base64 == 297 - 298 - 299 299 (% 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.** 300 300 301 - **[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**220 +[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]: 302 302 303 303 [[image:image-20221010193350-1.png]] 304 304 305 305 225 +[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]] 306 306 307 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]** 308 - 309 309 [[image:image-20221010193621-2.png]] 310 310 311 311 312 -== 5.2 Chirpstack Downlink Note == 313 313 231 +== 4.2 Chirpstack Downlink Note == 314 314 233 + 315 315 [[image:image-20220601102543-2.png]] 316 316 317 - **Convert the data to Base64**236 +Convert the data to Base64 318 318 319 -(% style="display:none" %) (%%) 320 320 239 +[[image:image-20220531173236-10.png]] 321 321 322 - [[image:image-20220531173236-10.png||height="597"width="1215"]]241 +Check ChripStack downlink DataRate 323 323 324 -**Check ChripStack downlink DataRate** 325 325 326 - 327 - 328 328 [[image:image-20220525101326-11.png]] 329 329 330 - **Make sure the RX2DR is the same in the end node**246 +Make sure the RX2DR is the same in the end node 331 331 332 332 333 -== 5.3 Loraserver Downlink Note == 334 334 250 +== 4.3 Loraserver Downlink Note == 335 335 252 + 336 336 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End 337 337 338 338 ((( ... ... @@ -350,7 +350,7 @@ 350 350 [[image:image-20220531173419-11.png]] 351 351 352 352 ((( 353 - **MQTT Connect to ChirpStack**270 +MQTT Connect to ChirpStack 354 354 355 355 356 356 ... ... @@ -377,10 +377,10 @@ 377 377 378 378 [[image:image-20220531173519-12.png]] 379 379 380 - **MQTT Connect to ChirpStack**297 +MQTT Connect to ChirpStack 381 381 382 382 383 - **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 384 384 385 385 [[image:image-20220531173658-14.png]] 386 386 ... ... @@ -402,15 +402,15 @@ 402 402 { 403 403 if(sha1[n] >= 'A' && sha1[n] <= 'Z') 404 404 { 405 - ascv = sha1.charCodeAt( 322 + ascv = sha1.charCodeAt(n) - 55; 406 406 } 407 407 else if(sha1[n] >= 'a' && sha1[n] <= 'z') 408 408 { 409 - ascv = sha1.charCodeAt( 326 + ascv = sha1.charCodeAt(n) - 87; 410 410 } 411 411 else 412 412 { 413 - ascv = sha1.charCodeAt( 330 + ascv = sha1.charCodeAt(n) - 48; 414 414 } 415 415 \\ bit_arr = (bit_arr << 4) | ascv; 416 416 bit_num += 4; ... ... @@ -453,7 +453,7 @@ 453 453 454 454 User enters the payload code according to the steps. 455 455 456 -[[image:image-20220531173754-15.png ||height="474" width="1334"]]373 +[[image:image-20220531173754-15.png]] 457 457 458 458 459 459 [[image:image-20220531173856-16.png]] ... ... @@ -464,9 +464,10 @@ 464 464 [[image:image-20220531174046-19.png]] 465 465 466 466 467 -= 6. Multiply Uplink in ChirpStack = 468 468 385 += 5. Multiply Uplink in ChirpStack = 469 469 387 + 470 470 ((( 471 471 nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data. 472 472 ))) ... ... @@ -477,7 +477,7 @@ 477 477 478 478 ))) 479 479 480 -[[image:image-20220526091912-7.png ||height="241" width="1336"]]398 +[[image:image-20220526091912-7.png]] 481 481 482 482 483 483 ((( ... ... @@ -502,13 +502,13 @@ 502 502 503 503 504 504 505 - **Duplicate transmission in short time**423 +Duplicate transmission in short time 506 506 507 -[[image:image-20220601102430-1.png ||height="598" width="1319"]]425 +[[image:image-20220601102430-1.png]] 508 508 509 509 510 510 511 -== 6.1 Solution ==429 +== 5.1 Solution == 512 512 513 513 514 514 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]] ... ... @@ -630,61 +630,13 @@ 630 630 Finish. 631 631 632 632 633 -= 7. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 634 634 552 += 6. Trouble Shooting = 635 635 636 - 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 == 637 637 638 -This example will be shown how to store/get all the data in two ways: 639 639 640 -**//1). Chirpstack ~-~-> Node-red//** 641 - 642 - 643 -[[image:image-20221012184501-1.png]] 644 - 645 - 646 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file 647 - 648 -[[image:image-20221012174220-2.png]] 649 - 650 - 651 -[[image:image-20221012184655-3.png||height="395" width="1049"]] 652 - 653 - 654 -**Each message is continuously logged to a specified file** 655 - 656 -[[image:image-20221012174352-3.png]] 657 - 658 - 659 -**//2). MQTT Sub//** 660 - 661 -If you don't want to store the information via node-red, you can get the output via the subscribe command. 662 - 663 - 664 -**If connecting from the same machine, you can use the following command to receive data:** 665 - 666 -(% class="box infomessage" %) 667 667 ((( 668 -mosquitto_sub -h localhost -t "application/#" -v 669 -))) 670 - 671 - 672 -**Different host** 673 - 674 -(% class="box infomessage" %) 675 -((( 676 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 677 -))) 678 - 679 -[[image:image-20221012173639-1.png]] 680 - 681 - 682 -= 8. Trouble Shooting = 683 - 684 -== 8.1 MIC Mismatch or MIC Failed == 685 - 686 - 687 -((( 688 688 When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. 689 689 ))) 690 690
- 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
- image-20221222134830-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -54.5 KB - Content
- image-20221222140203-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.4 KB - Content
- image-20221222141754-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -179.1 KB - Content
- image-20221222141830-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -116.7 KB - Content