Skip to Content

Changes for page Notes for ChirpStack

Last modified by Xiaoling on 2025/07/31 17:18
From version 246.5
edited by Xiaoling
on 2025/07/31 17:07
Change comment: There is no comment for this version
To version 247.1
edited by Xiaoling
on 2025/07/31 17:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -374,7 +374,7 @@
374 374  
375 375  (% style="color:blue" %)**Below list the support products and Requirements:**
376 376  
377 -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]]
377 +1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.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]]
378 378  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/]]
379 379  
380 380  (% style="color:blue" %)**What do you need to prepare**
... ... @@ -469,19 +469,13 @@
469 469  
470 470  === Select HEX format for downlink ===
471 471  
472 -
473 473  (% style="color:red" %)**Note: The end node user manual provides HEX format of the downlink commands, so users can directly select HEX format downlink.**
474 474  
475 -
476 476  [[image:image-20231108171112-5.png||height="629" width="1117"]]
477 477  
478 -
479 479  [[image:image-20231108171145-6.png||height="497" width="1101"]]
480 480  
481 481  
482 -
483 -
484 -
485 485  [[image:image-20220531173236-10.png||height="597" width="1215"]]
486 486  
487 487  **Check ChripStack downlink DataRate**
... ... @@ -542,7 +542,6 @@
542 542  **MQTT Connect to ChirpStack**
543 543  
544 544  
545 -
546 546  (((
547 547  Downlink payload encode javescript code.
548 548  
... ... @@ -613,7 +613,6 @@
613 613  
614 614  = 9.  Chirpstack Multicast Configuration =
615 615  
616 -
617 617  == 9.1  Introduction ==
618 618  
619 619  ChirpStack has support for creating multicast-groups to which devices can be assigned. When enqueueing a downlink payload for a multicast-group, ChirpStack will analyze which gateways must be used for broadcasting to cover the complete multicast-group. This means that potentially, a single multicast downlink payload will be emitted multiple times.
... ... @@ -625,7 +625,6 @@
625 625  
626 626  == 9.2  Example to configure chirpstack Multicast ==
627 627  
628 -
629 629  This section illustrates how to configure ChirpStack Multicast. Below is the network structure, we use our LPS8v2 as the LoRaWAN gateway and two SN50v3-LB as the LoRaWAN end-node here.
630 630  
631 631  [[image:image-20240923105725-1.png]]
... ... @@ -960,6 +960,7 @@
960 960  
961 961  = 12.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
962 962  
954 +
963 963  The following example is based on the built-in ChirpStack server for LPS8V2
964 964  
965 965  [[image:image-20231201174640-1.png||height="584" width="1148"]]
... ... @@ -999,7 +999,6 @@
999 999  [[image:image-20231204112107-10.png||height="621" width="1203"]]
1000 1000  
1001 1001  
1002 -
1003 1003  == **12.3 Batch Register** ==
1004 1004  
1005 1005  [[image:image-20231204113136-11.png||height="362" width="1062"]]
... ... @@ -1012,7 +1012,6 @@
1012 1012  [[image:image-20231204113237-13.png||height="558" width="1081"]]
1013 1013  
1014 1014  
1015 -
1016 1016  = 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1017 1017  
1018 1018  
... ... @@ -1045,7 +1045,6 @@
1045 1045  [[image:image-20230527143923-1.png||height="588" width="1132"]]
1046 1046  
1047 1047  
1048 -
1049 1049  (% style="color:blue" %)**2. Enter the MQTT configuration information**
1050 1050  
1051 1051  [[image:image-20230527144206-2.png||height="590" width="1136"]]
... ... @@ -1087,11 +1087,11 @@
1087 1087  If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
1088 1088  
1089 1089  Like that：Both 905.1Mhz and 902.3Mhz appear on uplink
1090 - But they belong to Subband1 and Subband2 of US915 respectively
1079 + But they belong to Subband1 and Subband2 of US915 respectively
1091 1091  
1092 1092  Cause: The server and the gateway use different frequency bands (the server uses Subband1, and the gateway uses Subband2)
1093 1093  
1094 - In server side, it shows the frequency is 905.1Mhz, which is sub-band2. But the RSSI is very low, Because this is not a signal in 905.1Mhz, it is on 902.3Mhz, the signal is too strong and appear a noise in 905.1Mhz.
1083 + In server side, it shows the frequency is 905.1Mhz, which is sub-band2. But the RSSI is very low, Because this is not a signal in 905.1Mhz, it is on 902.3Mhz, the signal is too strong and appear a noise in 905.1Mhz.
1095 1095  
1096 1096  How to check the frequency band used by the server：
1097 1097  
... ... @@ -1167,7 +1167,6 @@
1167 1167  [[image:image-20240117175009-3.png||height="524" width="1076"]]
1168 1168  
1169 1169  
1170 -
1171 1171  After the data collection is completed, you can send this file directly to our technical support personnel for analysis.
1172 1172  
1173 1173