Changes for page Notes for ChirpStack

Last modified by Kilight Cao on 2024/09/24 15:23
<
From version < 108.9 >
edited by Xiaoling
on 2022/07/23 14:21
To version < 130.1 >
edited by Kilight Cao
on 2022/12/22 14:18
>
Change comment: Uploaded new attachment "image-20221222141830-6.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -127,7 +127,6 @@
127 127  
128 128  = 3.  Gateway Registration for Basics Station =
129 129  
130 -
131 131  == 3.1  Introduction ==
132 132  
133 133  
... ... @@ -141,7 +141,6 @@
141 141  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]]
142 142  1. Firmware version since :[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]]
143 143  
144 -
145 145  (% style="color:blue" %)**How to set up chirpStack Basic Station**
146 146  
147 147  Users can check out the ChirpStack Basic Station [[link>>https://www.chirpstack.io/gateway-bridge/backends/basic-station/]] and [[forum>>https://forum.chirpstack.io/search?q=basic%20station]]
... ... @@ -152,7 +152,6 @@
152 152  A gateway that can access the internet normally
153 153  
154 154  
155 -
156 156  == 3.2  Add Gateway ==
157 157  
158 158  
... ... @@ -185,7 +185,7 @@
185 185  == 3.4  Start Station ==
186 186  
187 187  
188 -When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
185 +When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
189 189  
190 190  
191 191  == 3.5  Successful Connection ==
... ... @@ -196,7 +196,6 @@
196 196  [[image:image-20220524164448-13.png]]
197 197  
198 198  
199 -
200 200  == 3.6  Trouble Shooting ==
201 201  
202 202  
... ... @@ -210,31 +210,125 @@
210 210  [[image:image-20220531172857-9.png]]
211 211  
212 212  
209 += 4. How the gateway connects to Chirpstack v4 via gateway-bridge =
213 213  
214 -= 4. Downlink =
215 215  
216 -== 4.1 Chirpstack Downlink Note ==
212 +(% style="color:blue" %)**Below list the support products and Requirements:**
217 217  
214 +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]]
215 +1. Firmware version since: [[Chirpstack-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]]
218 218  
217 +(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
218 +
219 +Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]
220 +
221 +
222 +(% style="color:blue" %)**What do you need to prepare**
223 +
224 +A gateway that can access the internet normally
225 +
226 +== 4.1 Configure Packet Forwarder ==
227 +
228 +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
229 +
230 +* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
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 **Save & Apply**.
238 +
239 +[[image:image-20221222114220-2.png||height="748" width="931"]]
240 +
241 +
242 +== 4.2 Configuring gateway frequency ==
243 +
244 +Note: Gateway frequencies must match
245 +
246 +[[image:image-20221222134830-3.png||height="408" width="923"]]
247 +
248 +
249 +== 4.3 Modify the gateway-bridge configuration file ==
250 +
251 +
252 +Run the gateway command line command to modify the gateway-bridge configuration file:
253 +
254 +(% class="box infomessage" %)
255 +(((
256 +root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
257 +)))
258 +
259 +[[image:image-20221222113302-1.png]]
260 +
261 +[[image:image-20221222140203-4.png||height="875" width="806"]]
262 +
263 +
264 +(% class="wikigeneratedid" id="H" %)
265 +After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
266 +
267 +== 4.3 (Re)start and stop gateway-bridge ==
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 += 5.  Downlink =
287 +
288 +== 5.1 Convert HEX to Base64 ==
289 +
290 +
291 +(% 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.**
292 +
293 +**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
294 +
295 +[[image:image-20221010193350-1.png]]
296 +
297 +
298 +
299 +**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
300 +
301 +[[image:image-20221010193621-2.png]]
302 +
303 +
304 +== 5.2  Chirpstack Downlink Note ==
305 +
306 +
219 219  [[image:image-20220601102543-2.png]]
220 220  
221 -Convert the data to Base64
309 +**Convert the data to Base64**
222 222  
311 +(% style="display:none" %) (%%)
223 223  
224 -[[image:image-20220531173236-10.png]]
225 225  
226 -Check ChripStack downlink DataRate
314 +[[image:image-20220531173236-10.png||height="597" width="1215"]]
227 227  
316 +**Check ChripStack downlink DataRate**
228 228  
229 -[[image:image-20220525101326-11.png]]
230 230  
231 -Make sure the RX2DR is the same in the end node
232 232  
320 +[[image:image-20220525101326-11.png]]
233 233  
322 +**Make sure the RX2DR is the same in the end node**
234 234  
235 -== 4.2  Loraserver Downlink Note ==
236 236  
325 +== 5.3  Loraserver Downlink Note ==
237 237  
327 +
238 238  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
239 239  
240 240  (((
... ... @@ -252,7 +252,7 @@
252 252  [[image:image-20220531173419-11.png]]
253 253  
254 254  (((
255 -MQTT Connect to ChirpStack
345 +**MQTT Connect to ChirpStack**
256 256  
257 257  
258 258  
... ... @@ -279,21 +279,11 @@
279 279  
280 280  [[image:image-20220531173519-12.png]]
281 281  
282 -MQTT Connect to ChirpStack
372 +**MQTT Connect to ChirpStack**
283 283  
284 284  
285 -(((
286 -(% 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/]]**
287 -)))
375 +**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**
288 288  
289 -[[image:image-20220531173601-13.png]]
290 -
291 -Choose to Use Hex for Encode
292 -
293 -
294 -
295 -If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
296 -
297 297  [[image:image-20220531173658-14.png]]
298 298  
299 299  
... ... @@ -314,15 +314,15 @@
314 314   {
315 315   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
316 316   {
317 - ascv = sha1.charCodeAt(n) - 55;
397 + ascv = sha1.charCodeAt( n ) - 55;
318 318   }
319 319   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
320 320   {
321 - ascv = sha1.charCodeAt(n) - 87;
401 + ascv = sha1.charCodeAt( n ) - 87;
322 322   }
323 323   else
324 324   {
325 - ascv = sha1.charCodeAt(n) - 48;
405 + ascv = sha1.charCodeAt( n ) - 48;
326 326   }
327 327  \\ bit_arr = (bit_arr << 4) | ascv;
328 328   bit_num += 4;
... ... @@ -365,7 +365,7 @@
365 365  
366 366  User enters the payload code according to the steps.
367 367  
368 -[[image:image-20220531173754-15.png]]
448 +[[image:image-20220531173754-15.png||height="474" width="1334"]]
369 369  
370 370  
371 371  [[image:image-20220531173856-16.png]]
... ... @@ -376,10 +376,9 @@
376 376  [[image:image-20220531174046-19.png]]
377 377  
378 378  
459 += 6.  Multiply Uplink in ChirpStack =
379 379  
380 -= 5.  Multiply Uplink in ChirpStack =
381 381  
382 -
383 383  (((
384 384  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
385 385  )))
... ... @@ -390,7 +390,7 @@
390 390  
391 391  )))
392 392  
393 -[[image:image-20220526091912-7.png]]
472 +[[image:image-20220526091912-7.png||height="241" width="1336"]]
394 394  
395 395  
396 396  (((
... ... @@ -415,13 +415,13 @@
415 415  
416 416  
417 417  
418 -Duplicate transmission in short time
497 +**Duplicate transmission in short time**
419 419  
420 -[[image:image-20220601102430-1.png]]
499 +[[image:image-20220601102430-1.png||height="598" width="1319"]]
421 421  
422 422  
423 423  
424 -== 5.1  Solution ==
503 +== 6.1  Solution ==
425 425  
426 426  
427 427  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]]
... ... @@ -428,7 +428,7 @@
428 428  
429 429  
430 430  (((
431 -(% style="color:blue" %)**1. Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.**
510 +(% style="color:blue" %)**1.  Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.**
432 432  
433 433  
434 434  )))
... ... @@ -443,7 +443,7 @@
443 443  
444 444  
445 445  (((
446 -(% style="color:blue" %)**2. Environment variable settings:**
525 +(% style="color:blue" %)**2.  Environment variable settings:**
447 447  )))
448 448  
449 449  (((
... ... @@ -468,7 +468,7 @@
468 468  
469 469  
470 470  
471 -(% style="color:blue" %)**3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.**
550 +(% style="color:blue" %)**3.  Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.**
472 472  
473 473  The name of the plugin: Example ADR plugin:
474 474  
... ... @@ -480,7 +480,7 @@
480 480  
481 481  
482 482  
483 -(% style="color:blue" %)**4. Compile the ADR configuration file and generate the exe file.**
562 +(% style="color:blue" %)**4.  Compile the ADR configuration file and generate the exe file.**
484 484  
485 485  1) Create a folder named adr-setting
486 486  
... ... @@ -506,7 +506,7 @@
506 506  
507 507  
508 508  
509 -(% style="color:blue" %)**5. Add the plugin and run the plugin.**
588 +(% style="color:blue" %)**5.  Add the plugin and run the plugin.**
510 510  
511 511  (((
512 512  The exe file generated in the previous step is placed in the same root directory as chirpstack-network-server.toml, and the ADR plugin is added to the toml file. The location of the addition is as follows:
... ... @@ -543,13 +543,61 @@
543 543  Finish.
544 544  
545 545  
625 += 7.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
546 546  
547 -= 6. Trouble Shooting =
548 548  
549 -== 6.1 MIC Mismatch or MIC Failed ==
628 +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.
550 550  
630 +This example will be shown how to store/get all the data in two ways:
551 551  
632 +**//1). Chirpstack ~-~-> Node-red//**
633 +
634 +
635 +[[image:image-20221012184501-1.png]]
636 +
637 +
638 +Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
639 +
640 +[[image:image-20221012174220-2.png]]
641 +
642 +
643 +[[image:image-20221012184655-3.png||height="395" width="1049"]]
644 +
645 +
646 +**Each message is continuously logged to a specified file**
647 +
648 +[[image:image-20221012174352-3.png]]
649 +
650 +
651 +**//2). MQTT  Sub//**
652 +
653 +If you don't want to store the information via node-red, you can get the output via the subscribe command.
654 +
655 +
656 +**If connecting from the same machine, you can use the following command to receive data:**
657 +
658 +(% class="box infomessage" %)
552 552  (((
660 +mosquitto_sub -h localhost -t "application/#" -v
661 +)))
662 +
663 +
664 +**Different host**
665 +
666 +(% class="box infomessage" %)
667 +(((
668 +mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
669 +)))
670 +
671 +[[image:image-20221012173639-1.png]]
672 +
673 +
674 += 8.  Trouble Shooting =
675 +
676 +== 8.1  MIC Mismatch or MIC Failed ==
677 +
678 +
679 +(((
553 553  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
554 554  )))
555 555  
image-20221010193350-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +42.7 KB
Content
image-20221010193621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +34.2 KB
Content
image-20221012173639-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +56.2 KB
Content
image-20221012174220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +14.8 KB
Content
image-20221012174352-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +93.0 KB
Content
image-20221012184501-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +91.3 KB
Content
image-20221012184631-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +32.4 KB
Content
image-20221012184655-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +45.4 KB
Content
image-20221222113302-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +76.3 KB
Content
image-20221222114220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +64.3 KB
Content
image-20221222134830-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +54.5 KB
Content
image-20221222140203-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content
image-20221222141754-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +179.1 KB
Content
image-20221222141830-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +116.7 KB
Content

Applications

Navigation

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