Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
Uploaded new attachment "image-20230415170854-3.png", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -200,17 +200,17 @@ 200 200 [[image:image-20220531172857-9.png]] 201 201 202 202 203 -= 4. 3via gateway-bridge =203 += 4. How the gateway connects to Chirpstack v4 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-Bridge-V 3.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/]]209 +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/]] 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 3[[link>>https://www.chirpstack.io/gateway-bridge/gateway/dragino/]]213 +Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]] 214 214 215 215 216 216 (% style="color:blue" %)**What do you need to prepare** ... ... @@ -218,8 +218,6 @@ 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 223 == 4.1 Configure Packet Forwarder == 224 224 225 225 ... ... @@ -245,123 +245,9 @@ 245 245 [[image:image-20221222134830-3.png||height="408" width="923"]] 246 246 247 247 248 -== 4.3 Generate and modify the gateway-bridge configuration file ==246 +== 4.3 Modify the gateway-bridge configuration file == 249 249 250 250 251 -**1)Generate the gateway-bridge configuration file** 252 - 253 -By default, the configuration file is not up-to-date,so the user needs to rebuild the gateway-bridge configuration file. 254 - 255 -Users need to access the command line of the gateway through SSH,Then type the following command: 256 - 257 -(% class="box infomessage" %) 258 -((( 259 -/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 260 -))) 261 - 262 - 263 -**2)modify the gateway-bridge configuration file** 264 - 265 -The user needs to modify the server address in line 252 in the configuration file 266 - 267 -(% class="box infomessage" %) 268 -((( 269 -vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 270 -))) 271 - 272 -[[image:image-20230415165254-1.png||height="583" width="956"]] 273 - 274 - 275 -== 4.4 Debug == 276 - 277 - 278 -After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection 279 - 280 -(% class="box infomessage" %) 281 -((( 282 -/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 283 -))) 284 - 285 -If the gateway-bridge connection is normal, the debug log displays **"connected to mqtt broker"**. 286 - 287 -[[image:image-20230415170404-2.png]] 288 - 289 - 290 -If the debug log shows "**connection error**", check that the server port or server is correct 291 - 292 -[[image:image-20230415170854-3.png]] 293 - 294 - 295 -More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]** 296 - 297 - 298 -== 4.5 (Re)start and stop gateway-bridge == 299 - 300 - 301 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: 302 - 303 -(% class="box infomessage" %) 304 -((( 305 -**# start** 306 - 307 -/etc/init.d/chirpstack-gateway-bridge start 308 - 309 -**# stop** 310 - 311 -/etc/init.d/chirpstack-gateway-bridge stop 312 - 313 -**# restart** 314 - 315 -/etc/init.d/chirpstack-gateway-bridge restart 316 -))) 317 - 318 - 319 -= 5. How the gateway connects to Chirpstack v4 via gateway-bridge = 320 - 321 - 322 -(% style="color:blue" %)**Below list the support products and Requirements:** 323 - 324 -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]] 325 -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/]] 326 - 327 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge** 328 - 329 -Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]] 330 - 331 - 332 -(% style="color:blue" %)**What do you need to prepare** 333 - 334 -A gateway that can access the internet normally 335 - 336 - 337 -== 5.1 Configure Packet Forwarder == 338 - 339 - 340 -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 341 - 342 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 343 -* Make sure the following settings are set: 344 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 345 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1// 346 -** **Server port for upstream:** //1700// 347 -** **Server port for downstream:** //1700// 348 - 349 - Click **Save & Apply**. 350 - 351 -[[image:image-20221222114220-2.png||height="748" width="931"]] 352 - 353 - 354 -== 5.2 Configuring gateway frequency == 355 - 356 - 357 -(% style="color:red" %)**Note: Gateway frequencies must match** 358 - 359 -[[image:image-20221222134830-3.png||height="408" width="923"]] 360 - 361 - 362 -== 5.3 Modify the gateway-bridge configuration file == 363 - 364 - 365 365 Run the gateway command line command to modify the gateway-bridge configuration file: 366 366 367 367 (% class="box infomessage" %) ... ... @@ -380,7 +380,7 @@ 380 380 After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 381 381 382 382 383 -== 5.4 (Re)start and stop gateway-bridge ==267 +== 4.4 (Re)start and stop gateway-bridge == 384 384 385 385 386 386 Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: ... ... @@ -401,7 +401,7 @@ 401 401 ))) 402 402 403 403 404 -== 5.5 Successful Connection ==288 +== 4.5 Successful Connection == 405 405 406 406 407 407 [[image:image-20221222141754-5.png||height="488" width="1150"]] ... ... @@ -410,9 +410,9 @@ 410 410 [[image:image-20221222141830-6.png||height="582" width="1153"]] 411 411 412 412 413 -= 6. Downlink =297 += 5. Downlink = 414 414 415 -== 6.1 Convert HEX to Base64 ==299 +== 5.1 Convert HEX to Base64 == 416 416 417 417 418 418 (% 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.** ... ... @@ -428,7 +428,7 @@ 428 428 [[image:image-20221010193621-2.png]] 429 429 430 430 431 -== 6.2 Chirpstack Downlink Note ==315 +== 5.2 Chirpstack Downlink Note == 432 432 433 433 434 434 [[image:image-20220601102543-2.png]] ... ... @@ -449,7 +449,7 @@ 449 449 **Make sure the RX2DR is the same in the end node** 450 450 451 451 452 -== 6.3 Loraserver Downlink Note ==336 +== 5.3 Loraserver Downlink Note == 453 453 454 454 455 455 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End ... ... @@ -566,7 +566,7 @@ 566 566 ))) 567 567 568 568 569 -== 6.3 Add the decode function in Chirpstack for the payload ==453 +== 4.3 Add the decode function in Chirpstack for the payload == 570 570 571 571 572 572 User enters the payload code according to the steps. ... ... @@ -582,7 +582,7 @@ 582 582 [[image:image-20220531174046-19.png]] 583 583 584 584 585 -= 7. Multiply Uplink in ChirpStack =469 += 6. Multiply Uplink in ChirpStack = 586 586 587 587 588 588 ((( ... ... @@ -625,7 +625,7 @@ 625 625 [[image:image-20220601102430-1.png||height="598" width="1319"]] 626 626 627 627 628 -== 7.1 Solution ==512 +== 6.1 Solution == 629 629 630 630 631 631 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]] ... ... @@ -747,7 +747,7 @@ 747 747 Finish. 748 748 749 749 750 -= 8. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =634 += 7. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 751 751 752 752 753 753 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. ... ... @@ -796,9 +796,9 @@ 796 796 [[image:image-20221012173639-1.png]] 797 797 798 798 799 -= 9. Trouble Shooting =683 += 8. Trouble Shooting = 800 800 801 -== 9.1 MIC Mismatch or MIC Failed ==685 +== 8.1 MIC Mismatch or MIC Failed == 802 802 803 803 804 804 (((