Changes for page Notes for ChirpStack

Last modified by Edwin Chen on 2025/01/30 09:53
<
From version < 137.1 >
edited by Kilight Cao
on 2023/04/15 17:08
To version < 138.6 >
edited by Xiaoling
on 2023/04/21 16:34
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
Content
... ... @@ -200,17 +200,17 @@
200 200  [[image:image-20220531172857-9.png]]
201 201  
202 202  
203 -= 4.  How the gateway connects to Chirpstack v4 via 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-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/]]
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 v4 [[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]]
... ... @@ -264,7 +264,7 @@
264 264  After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
265 265  
266 266  
267 -== 4.4  (Re)start and stop gateway-bridge ==
386 +== 5.4  (Re)start and stop gateway-bridge ==
268 268  
269 269  
270 270  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -285,7 +285,7 @@
285 285  )))
286 286  
287 287  
288 -== 4.5  Successful Connection ==
407 +== 5.5  Successful Connection ==
289 289  
290 290  
291 291  [[image:image-20221222141754-5.png||height="488" width="1150"]]
... ... @@ -294,9 +294,9 @@
294 294  [[image:image-20221222141830-6.png||height="582" width="1153"]]
295 295  
296 296  
297 -= 5.  Downlink =
416 += 6.  Downlink =
298 298  
299 -== 5.1  Convert HEX to Base64 ==
418 +== 6.1  Convert HEX to Base64 ==
300 300  
301 301  
302 302  (% 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.**
... ... @@ -312,7 +312,7 @@
312 312  [[image:image-20221010193621-2.png]]
313 313  
314 314  
315 -== 5.2  Chirpstack Downlink Note ==
434 +== 6.2  Chirpstack Downlink Note ==
316 316  
317 317  
318 318  [[image:image-20220601102543-2.png]]
... ... @@ -333,7 +333,7 @@
333 333  **Make sure the RX2DR is the same in the end node**
334 334  
335 335  
336 -== 5.3  Loraserver Downlink Note ==
455 +== 6.3  Loraserver Downlink Note ==
337 337  
338 338  
339 339  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
... ... @@ -450,7 +450,7 @@
450 450  )))
451 451  
452 452  
453 -== 4.3  Add the decode function in Chirpstack for the payload ==
572 +== 6.3  Add the decode function in Chirpstack for the payload ==
454 454  
455 455  
456 456  User enters the payload code according to the steps.
... ... @@ -466,7 +466,7 @@
466 466  [[image:image-20220531174046-19.png]]
467 467  
468 468  
469 -= 6.  Multiply Uplink in ChirpStack =
588 += 7.  Multiply Uplink in ChirpStack =
470 470  
471 471  
472 472  (((
... ... @@ -509,7 +509,7 @@
509 509  [[image:image-20220601102430-1.png||height="598" width="1319"]]
510 510  
511 511  
512 -== 6.1  Solution ==
631 +== 7.1  Solution ==
513 513  
514 514  
515 515  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]]
... ... @@ -631,7 +631,7 @@
631 631  Finish.
632 632  
633 633  
634 -= 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. =
635 635  
636 636  
637 637  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.
... ... @@ -638,7 +638,7 @@
638 638  
639 639  This example will be shown how to store/get all the data in two ways:
640 640  
641 -**//1). Chirpstack ~-~-> Node-red//**
760 +(% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//**
642 642  
643 643  
644 644  [[image:image-20221012184501-1.png]]
... ... @@ -657,7 +657,7 @@
657 657  [[image:image-20221012174352-3.png]]
658 658  
659 659  
660 -**//2). MQTT  Sub//**
779 +(% style="color:blue" %)**//2). MQTT  Sub//**
661 661  
662 662  If you don't want to store the information via node-red, you can get the output via the subscribe command.
663 663  
... ... @@ -666,23 +666,23 @@
666 666  
667 667  (% class="box infomessage" %)
668 668  (((
669 -mosquitto_sub -h localhost -t "application/#" -v
788 +**mosquitto_sub -h localhost -t "application/#" -v**
670 670  )))
671 671  
672 672  
673 -**Different host**
792 +(% style="color:blue" %)**Different host**
674 674  
675 675  (% class="box infomessage" %)
676 676  (((
677 -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**
678 678  )))
679 679  
680 680  [[image:image-20221012173639-1.png]]
681 681  
682 682  
683 -= 8.  Trouble Shooting =
802 += 9.  Trouble Shooting =
684 684  
685 -== 8.1  MIC Mismatch or MIC Failed ==
804 +== 9.1  MIC Mismatch or MIC Failed ==
686 686  
687 687  
688 688  (((
... ... @@ -692,7 +692,5 @@
692 692  (((
693 693  Under normal circumstances, users need to change the APPKEY to solve this problem.
694 694  
695 -
696 -
697 697  
698 698  )))

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0