Changes for page Notes for ChirpStack

Last modified by Edwin Chen on 2025/01/30 09:53
<
From version < 138.4 >
edited by Xiaoling
on 2023/04/21 15:51
To version < 108.11 >
edited by Xiaoling
on 2022/07/23 14:22
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -38,6 +38,7 @@
38 38  )))
39 39  
40 40  
41 +
41 41  = 2.  Semtech UDP =
42 42  
43 43  == 2.1  Step 1. Add the Network-servers ==
... ... @@ -60,6 +60,7 @@
60 60  Add the Network-servers
61 61  
62 62  
64 +
63 63  == 2.2  Step 2. Create Gateway-profiles ==
64 64  
65 65  
... ... @@ -68,6 +68,7 @@
68 68  Create Gateway-profiles
69 69  
70 70  
73 +
71 71  == 2.3  Step 3. Create Service-profiles ==
72 72  
73 73  
... ... @@ -83,6 +83,7 @@
83 83  If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
84 84  
85 85  
89 +
86 86  == 2.4  Step 4. Add the gateway ==
87 87  
88 88  
... ... @@ -105,6 +105,7 @@
105 105  Configure the gateway
106 106  
107 107  
112 +
108 108  == 2.5  Step 5. Checking gateway Status ==
109 109  
110 110  
... ... @@ -119,8 +119,10 @@
119 119  gateway Status
120 120  
121 121  
127 +
122 122  = 3.  Gateway Registration for Basics Station =
123 123  
130 +
124 124  == 3.1  Introduction ==
125 125  
126 126  
... ... @@ -144,6 +144,7 @@
144 144  A gateway that can access the internet normally
145 145  
146 146  
154 +
147 147  == 3.2  Add Gateway ==
148 148  
149 149  
... ... @@ -176,7 +176,7 @@
176 176  == 3.4  Start Station ==
177 177  
178 178  
179 -When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
187 +When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
180 180  
181 181  
182 182  == 3.5  Successful Connection ==
... ... @@ -187,6 +187,7 @@
187 187  [[image:image-20220524164448-13.png]]
188 188  
189 189  
198 +
190 190  == 3.6  Trouble Shooting ==
191 191  
192 192  
... ... @@ -200,260 +200,31 @@
200 200  [[image:image-20220531172857-9.png]]
201 201  
202 202  
203 -= 4.  How the gateway connects to Chirpstack v3 via gateway-bridge =
204 204  
213 += 4. Downlink =
205 205  
206 -(% style="color:blue" %)**Below list the support products and Requirements:**
215 +== 4.1 Chirpstack Downlink Note ==
207 207  
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-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 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
212 -
213 -Users can check out the ChirpStack gateway-bridge v3 [[link>>https://www.chirpstack.io/gateway-bridge/gateway/dragino/]]
214 -
215 -
216 -(% style="color:blue" %)**What do you need to prepare**
217 -
218 -A gateway that can access the internet normally
219 -
220 -
221 -The following example does not have configuration certificates:
222 -
223 -
224 -== 4.1  Configure Packet Forwarder ==
225 -
226 -
227 -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
228 -
229 -* In the (% style="color:blue" %)**LoRaWAN** (%%)menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP**
230 -
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 (% style="color:blue" %)**Save & Apply**.
238 -
239 -[[image:image-20221222114220-2.png||height="748" width="931"]]
240 -
241 -
242 -== 4.2  Configuring gateway frequency ==
243 -
244 -
245 -(% style="color:red" %)**Note: Gateway frequencies must match**
246 -
247 -[[image:image-20221222134830-3.png||height="408" width="923"]]
248 -
249 -
250 -== 4.3  Generate and modify the gateway-bridge configuration file ==
251 -
252 -
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 **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
345 -* Make sure the following settings are set:
346 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
347 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
348 -** **Server port for upstream:** //1700//
349 -** **Server port for downstream:** //1700//
350 -
351 - Click **Save & Apply**.
352 -
353 -[[image:image-20221222114220-2.png||height="748" width="931"]]
354 -
355 -
356 -== 5.2  Configuring gateway frequency ==
357 -
358 -
359 -(% style="color:red" %)**Note: Gateway frequencies must match**
360 -
361 -[[image:image-20221222134830-3.png||height="408" width="923"]]
362 -
363 -
364 -== 5.3  Modify the gateway-bridge configuration file ==
365 -
366 -
367 -Run the gateway command line command to modify the gateway-bridge configuration file:
368 -
369 -(% class="box infomessage" %)
370 -(((
371 -root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
372 -)))
373 -
374 -[[image:image-20221222113302-1.png]]
375 -
376 -
377 -[[image:image-20221222140203-4.png||height="875" width="806"]]
378 -
379 -[[image:image-20221230094246-1.png||height="768" width="783"]]
380 -
381 -(% class="wikigeneratedid" id="H" %)
382 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
383 -
384 -
385 -== 5.4  (Re)start and stop gateway-bridge ==
386 -
387 -
388 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
389 -
390 -(% class="box infomessage" %)
391 -(((
392 -**# start**
393 -
394 -/etc/init.d/chirpstack-gateway-bridge start
395 -
396 -**# stop**
397 -
398 -/etc/init.d/chirpstack-gateway-bridge stop
399 -
400 -**# restart**
401 -
402 -/etc/init.d/chirpstack-gateway-bridge restart
403 -)))
404 -
405 -
406 -== 5.5  Successful Connection ==
407 -
408 -
409 -[[image:image-20221222141754-5.png||height="488" width="1150"]]
410 -
411 -
412 -[[image:image-20221222141830-6.png||height="582" width="1153"]]
413 -
414 -
415 -= 6.  Downlink =
416 -
417 -== 6.1  Convert HEX to Base64 ==
418 -
419 -
420 -(% 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.**
421 -
422 -**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
423 -
424 -[[image:image-20221010193350-1.png]]
425 -
426 -
427 -
428 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
429 -
430 -[[image:image-20221010193621-2.png]]
431 -
432 -
433 -== 6.2  Chirpstack Downlink Note ==
434 -
435 -
436 436  [[image:image-20220601102543-2.png]]
437 437  
438 -**Convert the data to Base64**
220 +Convert the data to Base64
439 439  
440 -(% style="display:none" %) (%%)
441 441  
223 +[[image:image-20220531173236-10.png]]
442 442  
443 -[[image:image-20220531173236-10.png||height="597" width="1215"]]
225 +Check ChripStack downlink DataRate
444 444  
445 -**Check ChripStack downlink DataRate**
446 446  
447 -
448 -
449 449  [[image:image-20220525101326-11.png]]
450 450  
451 -**Make sure the RX2DR is the same in the end node**
230 +Make sure the RX2DR is the same in the end node
452 452  
453 453  
454 -== 6.3  Loraserver Downlink Note ==
455 455  
234 +== 4.2  Loraserver Downlink Note ==
456 456  
236 +
457 457  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
458 458  
459 459  (((
... ... @@ -471,7 +471,7 @@
471 471  [[image:image-20220531173419-11.png]]
472 472  
473 473  (((
474 -**MQTT Connect to ChirpStack**
254 +MQTT Connect to ChirpStack
475 475  
476 476  
477 477  
... ... @@ -498,11 +498,21 @@
498 498  
499 499  [[image:image-20220531173519-12.png]]
500 500  
501 -**MQTT Connect to ChirpStack**
281 +MQTT Connect to ChirpStack
502 502  
503 503  
504 -**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**
284 +(((
285 +(% style="color:red" %)**Note: Chirpstack use base64 to downlink, so need to convert the downlink payload from HEX to base64 [[https:~~/~~/base64.us/>>url:https://base64.us/]]**
286 +)))
505 505  
288 +[[image:image-20220531173601-13.png]]
289 +
290 +Choose to Use Hex for Encode
291 +
292 +
293 +
294 +If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
295 +
506 506  [[image:image-20220531173658-14.png]]
507 507  
508 508  
... ... @@ -523,15 +523,15 @@
523 523   {
524 524   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
525 525   {
526 - ascv = sha1.charCodeAt( n ) - 55;
316 + ascv = sha1.charCodeAt(n) - 55;
527 527   }
528 528   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
529 529   {
530 - ascv = sha1.charCodeAt( n ) - 87;
320 + ascv = sha1.charCodeAt(n) - 87;
531 531   }
532 532   else
533 533   {
534 - ascv = sha1.charCodeAt( n ) - 48;
324 + ascv = sha1.charCodeAt(n) - 48;
535 535   }
536 536  \\ bit_arr = (bit_arr << 4) | ascv;
537 537   bit_num += 4;
... ... @@ -568,12 +568,13 @@
568 568  )))
569 569  
570 570  
571 -== 6.3  Add the decode function in Chirpstack for the payload ==
572 572  
362 +== 4.3  Add the decode function in Chirpstack for the payload ==
573 573  
364 +
574 574  User enters the payload code according to the steps.
575 575  
576 -[[image:image-20220531173754-15.png||height="474" width="1334"]]
367 +[[image:image-20220531173754-15.png]]
577 577  
578 578  
579 579  [[image:image-20220531173856-16.png]]
... ... @@ -584,9 +584,10 @@
584 584  [[image:image-20220531174046-19.png]]
585 585  
586 586  
587 -= 7.  Multiply Uplink in ChirpStack =
588 588  
379 += 5.  Multiply Uplink in ChirpStack =
589 589  
381 +
590 590  (((
591 591  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
592 592  )))
... ... @@ -597,7 +597,7 @@
597 597  
598 598  )))
599 599  
600 -[[image:image-20220526091912-7.png||height="241" width="1336"]]
392 +[[image:image-20220526091912-7.png]]
601 601  
602 602  
603 603  (((
... ... @@ -622,14 +622,15 @@
622 622  
623 623  
624 624  
625 -**Duplicate transmission in short time**
417 +Duplicate transmission in short time
626 626  
627 -[[image:image-20220601102430-1.png||height="598" width="1319"]]
419 +[[image:image-20220601102430-1.png]]
628 628  
629 629  
630 -== 7.1  Solution ==
631 631  
423 +== 5.1  Solution ==
632 632  
425 +
633 633  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]]
634 634  
635 635  
... ... @@ -749,68 +749,16 @@
749 749  Finish.
750 750  
751 751  
752 -= 8.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
753 753  
546 += 6.  Trouble Shooting =
754 754  
755 -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.
548 +== 6.1  MIC Mismatch or MIC Failed ==
756 756  
757 -This example will be shown how to store/get all the data in two ways:
758 758  
759 -**//1). Chirpstack ~-~-> Node-red//**
760 -
761 -
762 -[[image:image-20221012184501-1.png]]
763 -
764 -
765 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
766 -
767 -[[image:image-20221012174220-2.png]]
768 -
769 -
770 -[[image:image-20221012184655-3.png||height="395" width="1049"]]
771 -
772 -
773 -**Each message is continuously logged to a specified file**
774 -
775 -[[image:image-20221012174352-3.png]]
776 -
777 -
778 -**//2). MQTT  Sub//**
779 -
780 -If you don't want to store the information via node-red, you can get the output via the subscribe command.
781 -
782 -
783 -**If connecting from the same machine, you can use the following command to receive data:**
784 -
785 -(% class="box infomessage" %)
786 786  (((
787 -mosquitto_sub -h localhost -t "application/#" -v
788 -)))
789 -
790 -
791 -**Different host**
792 -
793 -(% class="box infomessage" %)
794 -(((
795 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
796 -)))
797 -
798 -[[image:image-20221012173639-1.png]]
799 -
800 -
801 -= 9.  Trouble Shooting =
802 -
803 -== 9.1  MIC Mismatch or MIC Failed ==
804 -
805 -
806 -(((
807 807  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
808 808  )))
809 809  
810 810  (((
811 811  Under normal circumstances, users need to change the APPKEY to solve this problem.
812 -
813 -
814 -
815 -
816 816  )))
image-20221010193350-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -42.7 KB
Content
image-20221010193621-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -34.2 KB
Content
image-20221012173639-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -56.2 KB
Content
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
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
image-20221230094246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -84.9 KB
Content
image-20230415165254-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -67.2 KB
Content
image-20230415170404-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20230415170854-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -48.4 KB
Content

Applications

Navigation

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