Changes for page Notes for ChirpStack

Last modified by Kilight Cao on 2024/09/24 15:23
<
From version < 133.1 >
edited by Kilight Cao
on 2022/12/30 09:43
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
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,142 +200,31 @@
200 200  [[image:image-20220531172857-9.png]]
201 201  
202 202  
203 -= 4.  How the gateway connects to Chirpstack v4 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-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]]
210 210  
211 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
212 -
213 -Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]
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 -== 4.1  Configure Packet Forwarder ==
222 -
223 -
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 -
226 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
227 -* Make sure the following settings are set:
228 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
229 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
230 -** **Server port for upstream:** //1700//
231 -** **Server port for downstream:** //1700//
232 -
233 - Click **Save & Apply**.
234 -
235 -[[image:image-20221222114220-2.png||height="748" width="931"]]
236 -
237 -
238 -== 4.2  Configuring gateway frequency ==
239 -
240 -
241 -(% style="color:red" %)**Note: Gateway frequencies must match**
242 -
243 -[[image:image-20221222134830-3.png||height="408" width="923"]]
244 -
245 -
246 -== 4.3  Modify the gateway-bridge configuration file ==
247 -
248 -
249 -Run the gateway command line command to modify the gateway-bridge configuration file:
250 -
251 -(% class="box infomessage" %)
252 -(((
253 -root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
254 -)))
255 -
256 -[[image:image-20221222113302-1.png]]
257 -
258 -
259 -[[image:image-20221222140203-4.png||height="875" width="806"]]
260 -
261 -[[image:image-20221230094246-1.png||height="768" width="783"]]
262 -
263 -(% class="wikigeneratedid" id="H" %)
264 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
265 -
266 -
267 -== 4.4  (Re)start and stop gateway-bridge ==
268 -
269 -
270 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
271 -
272 -(% class="box infomessage" %)
273 -(((
274 -**# start**
275 -
276 -/etc/init.d/chirpstack-gateway-bridge start
277 -
278 -**# stop**
279 -
280 -/etc/init.d/chirpstack-gateway-bridge stop
281 -
282 -**# restart**
283 -
284 -/etc/init.d/chirpstack-gateway-bridge restart
285 -)))
286 -
287 -
288 -== 4.5  Successful Connection ==
289 -
290 -
291 -[[image:image-20221222141754-5.png||height="488" width="1150"]]
292 -
293 -
294 -[[image:image-20221222141830-6.png||height="582" width="1153"]]
295 -
296 -
297 -= 5.  Downlink =
298 -
299 -== 5.1  Convert HEX to Base64 ==
300 -
301 -
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.**
303 -
304 -**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
305 -
306 -[[image:image-20221010193350-1.png]]
307 -
308 -
309 -
310 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
311 -
312 -[[image:image-20221010193621-2.png]]
313 -
314 -
315 -== 5.2  Chirpstack Downlink Note ==
316 -
317 -
318 318  [[image:image-20220601102543-2.png]]
319 319  
320 -**Convert the data to Base64**
220 +Convert the data to Base64
321 321  
322 -(% style="display:none" %) (%%)
323 323  
223 +[[image:image-20220531173236-10.png]]
324 324  
325 -[[image:image-20220531173236-10.png||height="597" width="1215"]]
225 +Check ChripStack downlink DataRate
326 326  
327 -**Check ChripStack downlink DataRate**
328 328  
329 -
330 -
331 331  [[image:image-20220525101326-11.png]]
332 332  
333 -**Make sure the RX2DR is the same in the end node**
230 +Make sure the RX2DR is the same in the end node
334 334  
335 335  
336 -== 5.3  Loraserver Downlink Note ==
337 337  
234 +== 4.2  Loraserver Downlink Note ==
338 338  
236 +
339 339  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
340 340  
341 341  (((
... ... @@ -353,7 +353,7 @@
353 353  [[image:image-20220531173419-11.png]]
354 354  
355 355  (((
356 -**MQTT Connect to ChirpStack**
254 +MQTT Connect to ChirpStack
357 357  
358 358  
359 359  
... ... @@ -380,11 +380,21 @@
380 380  
381 381  [[image:image-20220531173519-12.png]]
382 382  
383 -**MQTT Connect to ChirpStack**
281 +MQTT Connect to ChirpStack
384 384  
385 385  
386 -**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 +)))
387 387  
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 +
388 388  [[image:image-20220531173658-14.png]]
389 389  
390 390  
... ... @@ -405,15 +405,15 @@
405 405   {
406 406   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
407 407   {
408 - ascv = sha1.charCodeAt( n ) - 55;
316 + ascv = sha1.charCodeAt(n) - 55;
409 409   }
410 410   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
411 411   {
412 - ascv = sha1.charCodeAt( n ) - 87;
320 + ascv = sha1.charCodeAt(n) - 87;
413 413   }
414 414   else
415 415   {
416 - ascv = sha1.charCodeAt( n ) - 48;
324 + ascv = sha1.charCodeAt(n) - 48;
417 417   }
418 418  \\ bit_arr = (bit_arr << 4) | ascv;
419 419   bit_num += 4;
... ... @@ -450,12 +450,13 @@
450 450  )))
451 451  
452 452  
361 +
453 453  == 4.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.
457 457  
458 -[[image:image-20220531173754-15.png||height="474" width="1334"]]
367 +[[image:image-20220531173754-15.png]]
459 459  
460 460  
461 461  [[image:image-20220531173856-16.png]]
... ... @@ -466,9 +466,10 @@
466 466  [[image:image-20220531174046-19.png]]
467 467  
468 468  
469 -= 6.  Multiply Uplink in ChirpStack =
470 470  
379 += 5.  Multiply Uplink in ChirpStack =
471 471  
381 +
472 472  (((
473 473  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
474 474  )))
... ... @@ -479,7 +479,7 @@
479 479  
480 480  )))
481 481  
482 -[[image:image-20220526091912-7.png||height="241" width="1336"]]
392 +[[image:image-20220526091912-7.png]]
483 483  
484 484  
485 485  (((
... ... @@ -504,14 +504,15 @@
504 504  
505 505  
506 506  
507 -**Duplicate transmission in short time**
417 +Duplicate transmission in short time
508 508  
509 -[[image:image-20220601102430-1.png||height="598" width="1319"]]
419 +[[image:image-20220601102430-1.png]]
510 510  
511 511  
512 -== 6.1  Solution ==
513 513  
423 +== 5.1  Solution ==
514 514  
425 +
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]]
516 516  
517 517  
... ... @@ -631,68 +631,16 @@
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. =
635 635  
546 += 6.  Trouble Shooting =
636 636  
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.
548 +== 6.1  MIC Mismatch or MIC Failed ==
638 638  
639 -This example will be shown how to store/get all the data in two ways:
640 640  
641 -**//1). Chirpstack ~-~-> Node-red//**
642 -
643 -
644 -[[image:image-20221012184501-1.png]]
645 -
646 -
647 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
648 -
649 -[[image:image-20221012174220-2.png]]
650 -
651 -
652 -[[image:image-20221012184655-3.png||height="395" width="1049"]]
653 -
654 -
655 -**Each message is continuously logged to a specified file**
656 -
657 -[[image:image-20221012174352-3.png]]
658 -
659 -
660 -**//2). MQTT  Sub//**
661 -
662 -If you don't want to store the information via node-red, you can get the output via the subscribe command.
663 -
664 -
665 -**If connecting from the same machine, you can use the following command to receive data:**
666 -
667 -(% class="box infomessage" %)
668 668  (((
669 -mosquitto_sub -h localhost -t "application/#" -v
670 -)))
671 -
672 -
673 -**Different host**
674 -
675 -(% class="box infomessage" %)
676 -(((
677 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
678 -)))
679 -
680 -[[image:image-20221012173639-1.png]]
681 -
682 -
683 -= 8.  Trouble Shooting =
684 -
685 -== 8.1  MIC Mismatch or MIC Failed ==
686 -
687 -
688 -(((
689 689  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
690 690  )))
691 691  
692 692  (((
693 693  Under normal circumstances, users need to change the APPKEY to solve this problem.
694 -
695 -
696 -
697 -
698 698  )))
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

Applications

Navigation

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