Changes for page Notes for ChirpStack

Last modified by Edwin Chen on 2025/01/30 09:53
<
From version < 132.1 >
edited by Kilight Cao
on 2022/12/30 09:42
To version < 113.1 >
edited by Xiaoye
on 2022/10/12 17:42
>
Change comment: Uploaded new attachment "image-20221012174220-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoye
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  
... ... @@ -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,141 +200,47 @@
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 +(% class="wikigeneratedid" %)
216 +== 4.1 Convert HEX to Base64 ==
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 -
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 -
262 -(% class="wikigeneratedid" id="H" %)
263 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
264 -
265 -
266 -== 4.4  (Re)start and stop gateway-bridge ==
267 -
268 -
269 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
270 -
271 -(% class="box infomessage" %)
272 -(((
273 -**# start**
274 -
275 -/etc/init.d/chirpstack-gateway-bridge start
276 -
277 -**# stop**
278 -
279 -/etc/init.d/chirpstack-gateway-bridge stop
280 -
281 -**# restart**
282 -
283 -/etc/init.d/chirpstack-gateway-bridge restart
284 -)))
285 -
286 -
287 -== 4.5  Successful Connection ==
288 -
289 -
290 -[[image:image-20221222141754-5.png||height="488" width="1150"]]
291 -
292 -
293 -[[image:image-20221222141830-6.png||height="582" width="1153"]]
294 -
295 -
296 -= 5.  Downlink =
297 -
298 -== 5.1  Convert HEX to Base64 ==
299 -
300 -
301 301  (% 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.**
302 302  
303 -**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
220 +[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:
304 304  
305 305  [[image:image-20221010193350-1.png]]
306 306  
307 307  
225 +[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]
308 308  
309 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
310 -
311 311  [[image:image-20221010193621-2.png]]
312 312  
313 313  
314 -== 5.2  Chirpstack Downlink Note ==
315 315  
231 +== 4.2  Chirpstack Downlink Note ==
316 316  
233 +
317 317  [[image:image-20220601102543-2.png]]
318 318  
319 -**Convert the data to Base64**
236 +Convert the data to Base64
320 320  
321 -(% style="display:none" %) (%%)
322 322  
239 +[[image:image-20220531173236-10.png]]
323 323  
324 -[[image:image-20220531173236-10.png||height="597" width="1215"]]
241 +Check ChripStack downlink DataRate
325 325  
326 -**Check ChripStack downlink DataRate**
327 327  
328 -
329 -
330 330  [[image:image-20220525101326-11.png]]
331 331  
332 -**Make sure the RX2DR is the same in the end node**
246 +Make sure the RX2DR is the same in the end node
333 333  
334 334  
335 -== 5.3  Loraserver Downlink Note ==
336 336  
250 +== 4.3  Loraserver Downlink Note ==
337 337  
252 +
338 338  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
339 339  
340 340  (((
... ... @@ -352,7 +352,7 @@
352 352  [[image:image-20220531173419-11.png]]
353 353  
354 354  (((
355 -**MQTT Connect to ChirpStack**
270 +MQTT Connect to ChirpStack
356 356  
357 357  
358 358  
... ... @@ -379,10 +379,10 @@
379 379  
380 380  [[image:image-20220531173519-12.png]]
381 381  
382 -**MQTT Connect to ChirpStack**
297 +MQTT Connect to ChirpStack
383 383  
384 384  
385 -**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**
300 +If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB
386 386  
387 387  [[image:image-20220531173658-14.png]]
388 388  
... ... @@ -404,15 +404,15 @@
404 404   {
405 405   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
406 406   {
407 - ascv = sha1.charCodeAt( n ) - 55;
322 + ascv = sha1.charCodeAt(n) - 55;
408 408   }
409 409   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
410 410   {
411 - ascv = sha1.charCodeAt( n ) - 87;
326 + ascv = sha1.charCodeAt(n) - 87;
412 412   }
413 413   else
414 414   {
415 - ascv = sha1.charCodeAt( n ) - 48;
330 + ascv = sha1.charCodeAt(n) - 48;
416 416   }
417 417  \\ bit_arr = (bit_arr << 4) | ascv;
418 418   bit_num += 4;
... ... @@ -449,12 +449,13 @@
449 449  )))
450 450  
451 451  
367 +
452 452  == 4.3  Add the decode function in Chirpstack for the payload ==
453 453  
454 454  
455 455  User enters the payload code according to the steps.
456 456  
457 -[[image:image-20220531173754-15.png||height="474" width="1334"]]
373 +[[image:image-20220531173754-15.png]]
458 458  
459 459  
460 460  [[image:image-20220531173856-16.png]]
... ... @@ -465,9 +465,10 @@
465 465  [[image:image-20220531174046-19.png]]
466 466  
467 467  
468 -= 6.  Multiply Uplink in ChirpStack =
469 469  
385 += 5.  Multiply Uplink in ChirpStack =
470 470  
387 +
471 471  (((
472 472  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
473 473  )))
... ... @@ -478,7 +478,7 @@
478 478  
479 479  )))
480 480  
481 -[[image:image-20220526091912-7.png||height="241" width="1336"]]
398 +[[image:image-20220526091912-7.png]]
482 482  
483 483  
484 484  (((
... ... @@ -503,14 +503,15 @@
503 503  
504 504  
505 505  
506 -**Duplicate transmission in short time**
423 +Duplicate transmission in short time
507 507  
508 -[[image:image-20220601102430-1.png||height="598" width="1319"]]
425 +[[image:image-20220601102430-1.png]]
509 509  
510 510  
511 -== 6.1  Solution ==
512 512  
429 +== 5.1  Solution ==
513 513  
431 +
514 514  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]]
515 515  
516 516  
... ... @@ -630,68 +630,16 @@
630 630  Finish.
631 631  
632 632  
633 -= 7.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
634 634  
552 += 6.  Trouble Shooting =
635 635  
636 -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.
554 +== 6.1  MIC Mismatch or MIC Failed ==
637 637  
638 -This example will be shown how to store/get all the data in two ways:
639 639  
640 -**//1). Chirpstack ~-~-> Node-red//**
641 -
642 -
643 -[[image:image-20221012184501-1.png]]
644 -
645 -
646 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
647 -
648 -[[image:image-20221012174220-2.png]]
649 -
650 -
651 -[[image:image-20221012184655-3.png||height="395" width="1049"]]
652 -
653 -
654 -**Each message is continuously logged to a specified file**
655 -
656 -[[image:image-20221012174352-3.png]]
657 -
658 -
659 -**//2). MQTT  Sub//**
660 -
661 -If you don't want to store the information via node-red, you can get the output via the subscribe command.
662 -
663 -
664 -**If connecting from the same machine, you can use the following command to receive data:**
665 -
666 -(% class="box infomessage" %)
667 667  (((
668 -mosquitto_sub -h localhost -t "application/#" -v
669 -)))
670 -
671 -
672 -**Different host**
673 -
674 -(% class="box infomessage" %)
675 -(((
676 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
677 -)))
678 -
679 -[[image:image-20221012173639-1.png]]
680 -
681 -
682 -= 8.  Trouble Shooting =
683 -
684 -== 8.1  MIC Mismatch or MIC Failed ==
685 -
686 -
687 -(((
688 688  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
689 689  )))
690 690  
691 691  (((
692 692  Under normal circumstances, users need to change the APPKEY to solve this problem.
693 -
694 -
695 -
696 -
697 697  )))
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-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0