Changes for page Notes for ChirpStack

Last modified by Kilight Cao on 2024/09/24 15:23
<
From version < 138.1 >
edited by Kilight Cao
on 2023/04/15 17:15
To version < 108.13 >
edited by Xiaoling
on 2022/07/23 14:30
>
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
... ... @@ -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,258 +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 -== 4.1  Configure Packet Forwarder ==
224 -
225 -
226 -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
227 -
228 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
229 -* Make sure the following settings are set:
230 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
231 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
232 -** **Server port for upstream:** //1700//
233 -** **Server port for downstream:** //1700//
234 -
235 - Click **Save & Apply**.
236 -
237 -[[image:image-20221222114220-2.png||height="748" width="931"]]
238 -
239 -
240 -== 4.2  Configuring gateway frequency ==
241 -
242 -
243 -(% style="color:red" %)**Note: Gateway frequencies must match**
244 -
245 -[[image:image-20221222134830-3.png||height="408" width="923"]]
246 -
247 -
248 -== 4.3  Generate and modify the gateway-bridge configuration file ==
249 -
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 -Run the gateway command line command to modify the gateway-bridge configuration file:
366 -
367 -(% class="box infomessage" %)
368 -(((
369 -root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
370 -)))
371 -
372 -[[image:image-20221222113302-1.png]]
373 -
374 -
375 -[[image:image-20221222140203-4.png||height="875" width="806"]]
376 -
377 -[[image:image-20221230094246-1.png||height="768" width="783"]]
378 -
379 -(% class="wikigeneratedid" id="H" %)
380 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
381 -
382 -
383 -== 5.4  (Re)start and stop gateway-bridge ==
384 -
385 -
386 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
387 -
388 -(% class="box infomessage" %)
389 -(((
390 -**# start**
391 -
392 -/etc/init.d/chirpstack-gateway-bridge start
393 -
394 -**# stop**
395 -
396 -/etc/init.d/chirpstack-gateway-bridge stop
397 -
398 -**# restart**
399 -
400 -/etc/init.d/chirpstack-gateway-bridge restart
401 -)))
402 -
403 -
404 -== 5.5  Successful Connection ==
405 -
406 -
407 -[[image:image-20221222141754-5.png||height="488" width="1150"]]
408 -
409 -
410 -[[image:image-20221222141830-6.png||height="582" width="1153"]]
411 -
412 -
413 -= 6.  Downlink =
414 -
415 -== 6.1  Convert HEX to Base64 ==
416 -
417 -
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.**
419 -
420 -**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
421 -
422 -[[image:image-20221010193350-1.png]]
423 -
424 -
425 -
426 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
427 -
428 -[[image:image-20221010193621-2.png]]
429 -
430 -
431 -== 6.2  Chirpstack Downlink Note ==
432 -
433 -
434 434  [[image:image-20220601102543-2.png]]
435 435  
436 -**Convert the data to Base64**
220 +Convert the data to Base64
437 437  
438 -(% style="display:none" %) (%%)
439 439  
223 +[[image:image-20220531173236-10.png]]
440 440  
441 -[[image:image-20220531173236-10.png||height="597" width="1215"]]
225 +Check ChripStack downlink DataRate
442 442  
443 -**Check ChripStack downlink DataRate**
444 444  
445 -
446 -
447 447  [[image:image-20220525101326-11.png]]
448 448  
449 -**Make sure the RX2DR is the same in the end node**
230 +Make sure the RX2DR is the same in the end node
450 450  
451 451  
452 -== 6.3  Loraserver Downlink Note ==
453 453  
234 +== 4.2  Loraserver Downlink Note ==
454 454  
236 +
455 455  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
456 456  
457 457  (((
... ... @@ -469,7 +469,7 @@
469 469  [[image:image-20220531173419-11.png]]
470 470  
471 471  (((
472 -**MQTT Connect to ChirpStack**
254 +MQTT Connect to ChirpStack
473 473  
474 474  
475 475  
... ... @@ -496,11 +496,21 @@
496 496  
497 497  [[image:image-20220531173519-12.png]]
498 498  
499 -**MQTT Connect to ChirpStack**
281 +MQTT Connect to ChirpStack
500 500  
501 501  
502 -**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 +)))
503 503  
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 +
504 504  [[image:image-20220531173658-14.png]]
505 505  
506 506  
... ... @@ -521,15 +521,15 @@
521 521   {
522 522   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
523 523   {
524 - ascv = sha1.charCodeAt( n ) - 55;
316 + ascv = sha1.charCodeAt(n) - 55;
525 525   }
526 526   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
527 527   {
528 - ascv = sha1.charCodeAt( n ) - 87;
320 + ascv = sha1.charCodeAt(n) - 87;
529 529   }
530 530   else
531 531   {
532 - ascv = sha1.charCodeAt( n ) - 48;
324 + ascv = sha1.charCodeAt(n) - 48;
533 533   }
534 534  \\ bit_arr = (bit_arr << 4) | ascv;
535 535   bit_num += 4;
... ... @@ -566,12 +566,13 @@
566 566  )))
567 567  
568 568  
569 -== 6.3  Add the decode function in Chirpstack for the payload ==
570 570  
362 +== 4.3  Add the decode function in Chirpstack for the payload ==
571 571  
364 +
572 572  User enters the payload code according to the steps.
573 573  
574 -[[image:image-20220531173754-15.png||height="474" width="1334"]]
367 +[[image:image-20220531173754-15.png]]
575 575  
576 576  
577 577  [[image:image-20220531173856-16.png]]
... ... @@ -582,9 +582,10 @@
582 582  [[image:image-20220531174046-19.png]]
583 583  
584 584  
585 -= 7.  Multiply Uplink in ChirpStack =
586 586  
379 += 5.  Multiply Uplink in ChirpStack =
587 587  
381 +
588 588  (((
589 589  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
590 590  )))
... ... @@ -595,7 +595,7 @@
595 595  
596 596  )))
597 597  
598 -[[image:image-20220526091912-7.png||height="241" width="1336"]]
392 +[[image:image-20220526091912-7.png]]
599 599  
600 600  
601 601  (((
... ... @@ -620,14 +620,15 @@
620 620  
621 621  
622 622  
623 -**Duplicate transmission in short time**
417 +Duplicate transmission in short time
624 624  
625 -[[image:image-20220601102430-1.png||height="598" width="1319"]]
419 +[[image:image-20220601102430-1.png]]
626 626  
627 627  
628 -== 7.1  Solution ==
629 629  
423 +== 5.1  Solution ==
630 630  
425 +
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]]
632 632  
633 633  
... ... @@ -747,68 +747,16 @@
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. =
751 751  
546 += 6.  Trouble Shooting =
752 752  
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.
548 +== 6.1  MIC Mismatch or MIC Failed ==
754 754  
755 -This example will be shown how to store/get all the data in two ways:
756 756  
757 -**//1). Chirpstack ~-~-> Node-red//**
758 -
759 -
760 -[[image:image-20221012184501-1.png]]
761 -
762 -
763 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
764 -
765 -[[image:image-20221012174220-2.png]]
766 -
767 -
768 -[[image:image-20221012184655-3.png||height="395" width="1049"]]
769 -
770 -
771 -**Each message is continuously logged to a specified file**
772 -
773 -[[image:image-20221012174352-3.png]]
774 -
775 -
776 -**//2). MQTT  Sub//**
777 -
778 -If you don't want to store the information via node-red, you can get the output via the subscribe command.
779 -
780 -
781 -**If connecting from the same machine, you can use the following command to receive data:**
782 -
783 -(% class="box infomessage" %)
784 784  (((
785 -mosquitto_sub -h localhost -t "application/#" -v
786 -)))
787 -
788 -
789 -**Different host**
790 -
791 -(% class="box infomessage" %)
792 -(((
793 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
794 -)))
795 -
796 -[[image:image-20221012173639-1.png]]
797 -
798 -
799 -= 9.  Trouble Shooting =
800 -
801 -== 9.1  MIC Mismatch or MIC Failed ==
802 -
803 -
804 -(((
805 805  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
806 806  )))
807 807  
808 808  (((
809 809  Under normal circumstances, users need to change the APPKEY to solve this problem.
810 -
811 -
812 -
813 -
814 814  )))
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-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0