Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
There is no comment for this version
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. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -200,17 +200,17 @@ 200 200 [[image:image-20220531172857-9.png]] 201 201 202 202 203 -= 4. 4via gateway-bridge =203 += 4. How the gateway connects to Chirpstack v3 via gateway-bridge = 204 204 205 205 206 206 (% style="color:blue" %)**Below list the support products and Requirements:** 207 207 208 208 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]] 209 -1. Firmware version since: [[Chirpstack- gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]]209 +1. Firmware version since: [[Chirpstack-Bridge-V3.14.6>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V3.14.6-Bridge--build-v5.4.1679487778-20230322-2024/]] 210 210 211 211 (% style="color:blue" %)**How to set up chirpStack Gateway-bridge** 212 212 213 -Users can check out the ChirpStack gateway-bridge v 4[[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]213 +Users can check out the ChirpStack gateway-bridge v3 [[link>>https://www.chirpstack.io/gateway-bridge/gateway/dragino/]] 214 214 215 215 216 216 (% style="color:blue" %)**What do you need to prepare** ... ... @@ -218,12 +218,16 @@ 218 218 A gateway that can access the internet normally 219 219 220 220 221 +The following example does not have configuration certificates: 222 + 223 + 221 221 == 4.1 Configure Packet Forwarder == 222 222 223 223 224 224 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 225 225 226 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 229 +* In the (% style="color:blue" %)**LoRaWAN** (%%)menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP** 230 + 227 227 * Make sure the following settings are set: 228 228 ** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 229 229 ** **LoRaWAN Server Address:** //localhost or 127.0.0.1// ... ... @@ -230,7 +230,7 @@ 230 230 ** **Server port for upstream:** //1700// 231 231 ** **Server port for downstream:** //1700// 232 232 233 - Click **Save & Apply**. 237 + Click (% style="color:blue" %)**Save & Apply**. 234 234 235 235 [[image:image-20221222114220-2.png||height="748" width="931"]] 236 236 ... ... @@ -243,14 +243,129 @@ 243 243 [[image:image-20221222134830-3.png||height="408" width="923"]] 244 244 245 245 246 -== 4.3 Modify the gateway-bridge configuration file ==250 +== 4.3 Generate and modify the gateway-bridge configuration file == 247 247 248 248 253 +**1)Generate the gateway-bridge configuration file** 254 + 255 +By default, the configuration file is not up-to-date,so the user needs to rebuild the gateway-bridge configuration file. 256 + 257 +Users need to access the command line of the gateway through SSH,Then type the following command: 258 + 259 +(% class="box infomessage" %) 260 +((( 261 +**/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml ** 262 +))) 263 + 264 + 265 +**2)modify the gateway-bridge configuration file** 266 + 267 +The user needs to modify the server address in line 252 in the configuration file 268 + 269 +(% class="box infomessage" %) 270 +((( 271 +**vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml ** 272 +))) 273 + 274 +[[image:image-20230415165254-1.png||height="583" width="956"]] 275 + 276 + 277 +== 4.4 Debug == 278 + 279 + 280 +After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection 281 + 282 +(% class="box infomessage" %) 283 +((( 284 +**/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml** 285 +))) 286 + 287 +If the gateway-bridge connection is normal, the debug log displays **"connected to mqtt broker"**. 288 + 289 +[[image:image-20230415170404-2.png]] 290 + 291 + 292 +If the debug log shows "**connection error**", check that the server port or server is correct 293 + 294 +[[image:image-20230415170854-3.png]] 295 + 296 + 297 +More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]** 298 + 299 + 300 +== 4.5 (Re)start and stop gateway-bridge == 301 + 302 + 303 +Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: 304 + 305 +(% class="box infomessage" %) 306 +((( 307 +**# start** 308 + 309 +/etc/init.d/chirpstack-gateway-bridge start 310 + 311 +**# stop** 312 + 313 +/etc/init.d/chirpstack-gateway-bridge stop 314 + 315 +**# restart** 316 + 317 +/etc/init.d/chirpstack-gateway-bridge restart 318 +))) 319 + 320 + 321 += 5. How the gateway connects to Chirpstack v4 via gateway-bridge = 322 + 323 + 324 +(% style="color:blue" %)**Below list the support products and Requirements:** 325 + 326 +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]] 327 +1. Firmware version since: [[Chirpstack-Bridge-V4>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V4--build-v5.4.1670655072-20221210-1452/]] 328 + 329 +(% style="color:blue" %)**How to set up chirpStack Gateway-bridge** 330 + 331 +Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]] 332 + 333 + 334 +(% style="color:blue" %)**What do you need to prepare** 335 + 336 +A gateway that can access the internet normally 337 + 338 + 339 +== 5.1 Configure Packet Forwarder == 340 + 341 + 342 +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 343 + 344 +* In the (% style="color:blue" %)**LoRaWAN**(%%) menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP** 345 + 346 +* Make sure the following settings are set: 347 +** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 348 +** **LoRaWAN Server Address:** //localhost or 127.0.0.1// 349 +** **Server port for upstream:** //1700// 350 +** **Server port for downstream:** //1700// 351 + 352 + Click (% style="color:blue" %)**Save & Apply**. 353 + 354 +[[image:image-20221222114220-2.png||height="748" width="931"]] 355 + 356 + 357 +== 5.2 Configuring gateway frequency == 358 + 359 + 360 +(% style="color:red" %)**Note: Gateway frequencies must match** 361 + 362 +[[image:image-20221222134830-3.png||height="408" width="923"]] 363 + 364 + 365 +== 5.3 Modify the gateway-bridge configuration file == 366 + 367 + 249 249 Run the gateway command line command to modify the gateway-bridge configuration file: 250 250 251 251 (% class="box infomessage" %) 252 252 ((( 253 -root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 372 +**root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml ** 254 254 ))) 255 255 256 256 [[image:image-20221222113302-1.png]] ... ... @@ -258,12 +258,13 @@ 258 258 259 259 [[image:image-20221222140203-4.png||height="875" width="806"]] 260 260 380 +[[image:image-20221230094246-1.png||height="768" width="783"]] 261 261 262 262 (% class="wikigeneratedid" id="H" %) 263 263 After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 264 264 265 265 266 -== 4.4 (Re)start and stop gateway-bridge ==386 +== 5.4 (Re)start and stop gateway-bridge == 267 267 268 268 269 269 Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: ... ... @@ -284,7 +284,7 @@ 284 284 ))) 285 285 286 286 287 -== 4.5 Successful Connection ==407 +== 5.5 Successful Connection == 288 288 289 289 290 290 [[image:image-20221222141754-5.png||height="488" width="1150"]] ... ... @@ -293,9 +293,9 @@ 293 293 [[image:image-20221222141830-6.png||height="582" width="1153"]] 294 294 295 295 296 -= 5. Downlink =416 += 6. Downlink = 297 297 298 -== 5.1 Convert HEX to Base64 ==418 +== 6.1 Convert HEX to Base64 == 299 299 300 300 301 301 (% 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.** ... ... @@ -311,7 +311,7 @@ 311 311 [[image:image-20221010193621-2.png]] 312 312 313 313 314 -== 5.2 Chirpstack Downlink Note ==434 +== 6.2 Chirpstack Downlink Note == 315 315 316 316 317 317 [[image:image-20220601102543-2.png]] ... ... @@ -332,7 +332,7 @@ 332 332 **Make sure the RX2DR is the same in the end node** 333 333 334 334 335 -== 5.3 Loraserver Downlink Note ==455 +== 6.3 Loraserver Downlink Note == 336 336 337 337 338 338 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End ... ... @@ -449,7 +449,7 @@ 449 449 ))) 450 450 451 451 452 -== 4.3 Add the decode function in Chirpstack for the payload ==572 +== 6.3 Add the decode function in Chirpstack for the payload == 453 453 454 454 455 455 User enters the payload code according to the steps. ... ... @@ -465,7 +465,7 @@ 465 465 [[image:image-20220531174046-19.png]] 466 466 467 467 468 -= 6. Multiply Uplink in ChirpStack =588 += 7. Multiply Uplink in ChirpStack = 469 469 470 470 471 471 ((( ... ... @@ -508,7 +508,7 @@ 508 508 [[image:image-20220601102430-1.png||height="598" width="1319"]] 509 509 510 510 511 -== 6.1 Solution ==631 +== 7.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,7 +630,7 @@ 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. =753 += 8. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 634 634 635 635 636 636 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. ... ... @@ -637,7 +637,7 @@ 637 637 638 638 This example will be shown how to store/get all the data in two ways: 639 639 640 -**//1). Chirpstack ~-~-> Node-red//** 760 +(% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//** 641 641 642 642 643 643 [[image:image-20221012184501-1.png]] ... ... @@ -656,7 +656,7 @@ 656 656 [[image:image-20221012174352-3.png]] 657 657 658 658 659 -**//2). MQTT Sub//** 779 +(% style="color:blue" %)**//2). MQTT Sub//** 660 660 661 661 If you don't want to store the information via node-red, you can get the output via the subscribe command. 662 662 ... ... @@ -665,23 +665,23 @@ 665 665 666 666 (% class="box infomessage" %) 667 667 ((( 668 -mosquitto_sub -h localhost -t "application/#" -v 788 +**mosquitto_sub -h localhost -t "application/#" -v** 669 669 ))) 670 670 671 671 672 -**Different host** 792 +(% style="color:blue" %)**Different host** 673 673 674 674 (% class="box infomessage" %) 675 675 ((( 676 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 796 +**mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v** 677 677 ))) 678 678 679 679 [[image:image-20221012173639-1.png]] 680 680 681 681 682 -= 8. Trouble Shooting =802 += 9. Trouble Shooting = 683 683 684 -== 8.1 MIC Mismatch or MIC Failed ==804 +== 9.1 MIC Mismatch or MIC Failed == 685 685 686 686 687 687 ((( ... ... @@ -691,7 +691,5 @@ 691 691 ((( 692 692 Under normal circumstances, users need to change the APPKEY to solve this problem. 693 693 694 - 695 - 696 696 697 697 )))
- image-20230415165254-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +67.2 KB - Content
- image-20230415170404-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +17.9 KB - Content
- image-20230415170854-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +48.4 KB - Content