Changes for page Notes for ChirpStack

Last modified by Edwin Chen on 2025/01/30 09:53
<
From version < 163.1 >
edited by Bei Jinggeng
on 2023/07/02 10:09
To version < 176.2 >
edited by Xiaoling
on 2023/09/26 16:14
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
Content
... ... @@ -20,7 +20,7 @@
20 20  
21 21  **1) Have a Chirstack Server.**
22 22  
23 -[[image:image-20220525100058-1.png]]
23 +[[image:image-20230821114047-4.png||height="524" width="990"]]
24 24  
25 25  ChirpStack home page
26 26  
... ... @@ -38,11 +38,58 @@
38 38  )))
39 39  
40 40  
41 -= 2.  Semtech UDP =
41 += 2.  Node usage introduction =
42 42  
43 -== 2.1  Step 1. Add the Network-servers ==
43 +== 2.1 Register Node ==
44 44  
45 45  
46 +**Step 1: Add application**
47 +
48 +[[image:image-20230702094608-1.png||height="537" width="1015"]]
49 +
50 +
51 +**Step 2：Fill name**
52 +
53 +[[image:image-20230702094852-2.png]]
54 +
55 +
56 +**Step3 ：Add device profile**
57 +
58 +[[image:image-20230702095114-4.png||height="448" width="1061"]]
59 +
60 +
61 +**Step4 ：Configure your device profile**
62 +
63 +[[image:image-20230702095557-5.png||height="648" width="1121"]]
64 +
65 +Does node support class-c
66 +
67 +[[image:image-20230702095641-6.png||height="349" width="1114"]]
68 +
69 +Add node's decoder
70 +
71 +[[image:image-20230702095827-7.png||height="490" width="1138"]]
72 +
73 +
74 +**Step5 ：add device**
75 +
76 +[[image:image-20230702094944-3.png||height="439" width="1153"]]
77 +
78 +
79 +[[image:image-20230702100312-8.png||height="550" width="1106"]]
80 +
81 +
82 +[[image:image-20230702100543-10.png||height="313" width="1099"]]
83 +
84 +
85 +[[image:image-20230702100930-11.png||height="613" width="1098"]]
86 +
87 +
88 += 3.  Semtech UDP for ChirpStack v3 =
89 +
90 +== 3.1  Step 1. Add the Network-servers ==
91 +
92 +
46 46  The network-Servers address varies depending on the ChirpStack server setup environment
47 47  
48 48  (% class="box" %)
... ... @@ -54,13 +54,12 @@
54 54  
55 55  (% style="color:red" %)**If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.**
56 56  
57 -
58 58  [[image:image-20220531171609-1.png||height="638" width="1268"]](% style="display:none" %)
59 59  
60 60  Add the Network-servers
61 61  
62 62  
63 -== 2.2  Step 2. Create Gateway-profiles ==
109 +== 3.2  Step 2. Create Gateway-profiles ==
64 64  
65 65  
66 66  [[image:image-20220531171651-2.png||height="632" width="1264"]](% style="display:none" %)
... ... @@ -68,7 +68,7 @@
68 68  Create Gateway-profiles
69 69  
70 70  
71 -== 2.3  Step 3. Create Service-profiles ==
117 +== 3.3  Step 3. Create Service-profiles ==
72 72  
73 73  
74 74  [[image:image-20220531171809-3.png||height="761" width="1265"]]
... ... @@ -83,7 +83,7 @@
83 83  If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
84 84  
85 85  
86 -== 2.4  Step 4. Add the gateway ==
132 +== 3.4  Step 4. Add the gateway ==
87 87  
88 88  
89 89  The example gateway id is: a840411e96744150
... ... @@ -90,8 +90,6 @@
90 90  
91 91  (((
92 92  (% style="color:red" %)**Note : The Gateway EUI and server addresses must match the ChirpStack configuration.**
93 -
94 -
95 95  )))
96 96  
97 97  [[image:image-20220531171923-4.png||height="745" width="1253"]](% style="display:none" %)
... ... @@ -99,13 +99,12 @@
99 99  Add the gateway
100 100  
101 101  
102 -
103 103  [[image:image-20220531172031-5.png]]
104 104  
105 105  Configure the gateway
106 106  
107 107  
108 -== 2.5  Step 5. Checking gateway Status ==
151 +== 3.5  Step 5. Checking gateway Status ==
109 109  
110 110  
111 111  [[image:image-20220531172158-6.png||height="704" width="1167"]](% style="display:none" %)
... ... @@ -119,11 +119,26 @@
119 119  gateway Status
120 120  
121 121  
122 -= 3.  Gateway Registration for Basics Station =
165 += 4.  Semtech UDP for ChirpStack v4 =
123 123  
124 -== 3.1  Introduction ==
167 +== 4.1  Step 1. Add the gateway ==
125 125  
126 126  
170 +[[image:image-20230926092907-1.png||height="598" width="1007"]]
171 +
172 +
173 +[[image:image-20230926093057-2.png||height="541" width="1002"]]
174 +
175 +
176 +== 4.2  Step 2. Checking gateway Status ==
177 +
178 +[[image:image-20230926093233-3.png||height="581" width="1018"]]
179 +
180 += 5.  Gateway Registration for Basics Station =
181 +
182 +== 5.1  Introduction ==
183 +
184 +
127 127  The [[Semtech Basic Station>>url:https://doc.sm.tc/station/]] backend implements the [[LNS protocol>>url:https://doc.sm.tc/station/tcproto.html]]. It exposes a WebSocket handler to which Basic Station powered gateways can connect.
128 128  
129 129  ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
... ... @@ -144,13 +144,13 @@
144 144  A gateway that can access the internet normally
145 145  
146 146  
147 -== 3.2  Add Gateway ==
205 +== 5.2  Add Gateway ==
148 148  
149 149  
150 150  [[image:image-20220524164205-10.png]]
151 151  
152 152  
153 -== 3.3  Access the gateway GUI ==
211 +== 5.3  Access the gateway GUI ==
154 154  
155 155  
156 156  Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
... ... @@ -164,7 +164,7 @@
164 164  (((
165 165  Service Provider  ~-~->  Choose the ChirpStack/Senet ~-~- Basic Station
166 166  
167 -LNS URI  ~-~->  Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:433 or ws:~/~/xxxx.chirpstack.com:3001
225 +LNS URI  ~-~->  Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:443 or ws:~/~/xxxx.chirpstack.com:3001
168 168  
169 169  LNS TLS trust  ~-~->  Upload the TLS Certificate
170 170  )))
... ... @@ -173,13 +173,13 @@
173 173  [[image:image-20220524164341-12.png]]
174 174  
175 175  
176 -== 3.4  Start Station ==
234 +== 5.4  Start Station ==
177 177  
178 178  
179 179  When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
180 180  
181 181  
182 -== 3.5  Successful Connection ==
240 +== 5.5  Successful Connection ==
183 183  
184 184  
185 185  If user completes the above steps, which will see live date in the ChirpStack.
... ... @@ -187,7 +187,7 @@
187 187  [[image:image-20220524164448-13.png]]
188 188  
189 189  
190 -== 3.6  Trouble Shooting ==
248 +== 5.6  Trouble Shooting ==
191 191  
192 192  
193 193  User can check the station log in the logread/system log page.
... ... @@ -200,7 +200,7 @@
200 200  [[image:image-20220531172857-9.png]]
201 201  
202 202  
203 -= 4.  How the gateway connects to Chirpstack v3 via gateway-bridge =
261 += 6.  How the gateway connects to Chirpstack v3 via gateway-bridge =
204 204  
205 205  
206 206  (% style="color:blue" %)**Below list the support products and Requirements:**
... ... @@ -221,7 +221,7 @@
221 221  The following example does not have configuration certificates:
222 222  
223 223  
224 -== 4.1  Configure Packet Forwarder ==
282 +== 6.1  Configure Packet Forwarder ==
225 225  
226 226  
227 227  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
... ... @@ -239,7 +239,7 @@
239 239  [[image:image-20221222114220-2.png||height="748" width="931"]]
240 240  
241 241  
242 -== 4.2  Configuring gateway frequency ==
300 +== 6.2  Configuring gateway frequency ==
243 243  
244 244  
245 245  (% style="color:red" %)**Note: Gateway frequencies must match**
... ... @@ -247,7 +247,7 @@
247 247  [[image:image-20221222134830-3.png||height="408" width="923"]]
248 248  
249 249  
250 -== 4.3  Generate and modify the gateway-bridge configuration file ==
308 +== 6.3  Generate and modify the gateway-bridge configuration file ==
251 251  
252 252  
253 253  **1）Generate the gateway-bridge configuration file**
... ... @@ -274,7 +274,7 @@
274 274  [[image:image-20230415165254-1.png||height="583" width="956"]]
275 275  
276 276  
277 -== 4.4  Debug ==
335 +== 6.4  Debug ==
278 278  
279 279  
280 280  After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection
... ... @@ -297,7 +297,7 @@
297 297  More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]**
298 298  
299 299  
300 -== 4.5  (Re)start and stop gateway-bridge ==
358 +== 6.5  (Re)start and stop gateway-bridge ==
301 301  
302 302  
303 303  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -318,7 +318,7 @@
318 318  )))
319 319  
320 320  
321 -= 5.  How the gateway connects to Chirpstack v4 via gateway-bridge =
379 += 7.  How the gateway connects to Chirpstack v4 via gateway-bridge =
322 322  
323 323  
324 324  (% style="color:blue" %)**Below list the support products and Requirements:**
... ... @@ -336,7 +336,7 @@
336 336  A gateway that can access the internet normally
337 337  
338 338  
339 -== 5.1  Configure Packet Forwarder ==
397 +== 7.1  Configure Packet Forwarder ==
340 340  
341 341  
342 342  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
... ... @@ -354,7 +354,7 @@
354 354  [[image:image-20221222114220-2.png||height="748" width="931"]]
355 355  
356 356  
357 -== 5.2  Configuring gateway frequency ==
415 +== 7.2  Configuring gateway frequency ==
358 358  
359 359  
360 360  (% style="color:red" %)**Note: Gateway frequencies must match**
... ... @@ -362,7 +362,7 @@
362 362  [[image:image-20221222134830-3.png||height="408" width="923"]]
363 363  
364 364  
365 -== 5.3  Modify the gateway-bridge configuration file ==
423 +== 7.3  Modify the gateway-bridge configuration file ==
366 366  
367 367  
368 368  Run the gateway command line command to modify the gateway-bridge configuration file:
... ... @@ -377,6 +377,7 @@
377 377  
378 378  [[image:image-20221222140203-4.png||height="875" width="806"]]
379 379  
438 +
380 380  [[image:image-20221230094246-1.png||height="768" width="783"]]
381 381  
382 382  (% class="wikigeneratedid" id="H" %)
... ... @@ -383,7 +383,7 @@
383 383  After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
384 384  
385 385  
386 -== 5.4  (Re)start and stop gateway-bridge ==
445 +== 7.4  (Re)start and stop gateway-bridge ==
387 387  
388 388  
389 389  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -404,7 +404,7 @@
404 404  )))
405 405  
406 406  
407 -== 5.5  Successful Connection ==
466 +== 7.5  Successful Connection ==
408 408  
409 409  
410 410  [[image:image-20221222141754-5.png||height="488" width="1150"]]
... ... @@ -413,9 +413,9 @@
413 413  [[image:image-20221222141830-6.png||height="582" width="1153"]]
414 414  
415 415  
416 -= 6.  Downlink =
475 += 8.  Downlink =
417 417  
418 -== 6.1  Convert HEX to Base64 ==
477 +== 8.1  Convert HEX to Base64 ==
419 419  
420 420  
421 421  (% 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.**
... ... @@ -431,7 +431,7 @@
431 431  [[image:image-20221010193621-2.png]]
432 432  
433 433  
434 -== 6.2  Chirpstack Downlink Note ==
493 +== 8.2  Chirpstack Downlink Note ==
435 435  
436 436  
437 437  [[image:image-20220601102543-2.png]]
... ... @@ -452,7 +452,7 @@
452 452  **Make sure the RX2DR is the same in the end node**
453 453  
454 454  
455 -== 6.3  Loraserver Downlink Note ==
514 +== 8.3  Loraserver Downlink Note ==
456 456  
457 457  
458 458  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
... ... @@ -569,7 +569,7 @@
569 569  )))
570 570  
571 571  
572 -== 6.4  Add the decode function in Chirpstack for the payload ==
631 +== 8.4  Add the decode function in Chirpstack for the payload ==
573 573  
574 574  
575 575  User enters the payload code according to the steps.
... ... @@ -587,7 +587,7 @@
587 587  [[image:image-20220531174046-19.png]]
588 588  
589 589  
590 -= 7.  Multiply Uplink in ChirpStack =
649 += 9.  Multiply Uplink in ChirpStack =
591 591  
592 592  
593 593  (((
... ... @@ -627,19 +627,16 @@
627 627  
628 628  **Duplicate transmission in short time**
629 629  
630 -[[image:image-20220601102430-1.png||height="598" width="1319"]]
689 +[[image:image-20220601102430-1.png||height="508" width="1120"]]
631 631  
632 632  
633 -== 7.1  Solution ==
692 +== 9.1  Solution ==
634 634  
635 635  
636 636  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]]
637 637  
638 -
639 639  (((
640 640  (% 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.**
641 -
642 -
643 643  )))
644 644  
645 645  [[image:image-20220525104532-24.png]]
... ... @@ -752,7 +752,7 @@
752 752  Finish.
753 753  
754 754  
755 -= 8.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
811 += 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
756 756  
757 757  
758 758  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.
... ... @@ -762,7 +762,7 @@
762 762  (% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//**
763 763  
764 764  
765 -[[image:image-20221012184501-1.png]]
821 +[[image:image-20221012184501-1.png||height="608" width="1041"]]
766 766  
767 767  
768 768  Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
... ... @@ -798,11 +798,12 @@
798 798  **mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v**
799 799  )))
800 800  
801 -[[image:image-20221012173639-1.png]]
857 +[[image:image-20221012173639-1.png||height="273" width="1206"]]
802 802  
803 -= 9.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
804 804  
860 += 11.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
805 805  
862 +
806 806  LPS8v2 includes a local ChirpStack Server and Node-Red. This example shows how to configure LHT65N to use with the local Node-Red server. This example assumes users already have:
807 807  
808 808  * LHT65N register on LPS8v2 Built-In ChirpStack server already
... ... @@ -811,7 +811,7 @@
811 811  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
812 812  
813 813  
814 -== 9.1 Link Node-Red to Local ChirpStack ==
871 +== 11.1 Link Node-Red to Local ChirpStack ==
815 815  
816 816  
817 817  Users can download the Node-Red decoder from this link and import it into the Node-Red platform:  **[[attach:LHT65N-ChirpStack-node-red.json||target="_blank"]]**
... ... @@ -838,7 +838,7 @@
838 838  [[image:image-20230527144206-2.png||height="590" width="1136"]]
839 839  
840 840  
841 -(% style="color:blue" %)3. **Finally, click "Update" and Deploy**
898 +(% style="color:blue" %)**3.** **Finally, click "Update" and Deploy**
842 842  
843 843  "Connected" indicates that the Link Node-red to Local Chirpstack is normal.
844 844  
... ... @@ -845,7 +845,7 @@
845 845  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Notes%20for%20TTN/WebHome/image-20220914140918-5.png?width=1121&height=602&rev=1.1||alt="image-20220914140918-5.png"]]
846 846  
847 847  
848 -== 9.2 Check result. ==
905 +== 11.2 Check result. ==
849 849  
850 850  
851 851  Users can check logs by adding debug.
... ... @@ -855,9 +855,9 @@
855 855  [[image:image-20230529150923-1.png||height="424" width="1118"]]
856 856  
857 857  
858 -= 10.  Trouble Shooting =
915 += 12.  Trouble Shooting =
859 859  
860 -== 10.1  MIC Mismatch or MIC Failed ==
917 +== 12.1  MIC Mismatch or MIC Failed ==
861 861  
862 862  
863 863  (((
... ... @@ -867,5 +867,34 @@
867 867  (((
868 868  Under normal circumstances, users need to change the APPKEY to solve this problem.
869 869  
927 +
928 +== 12.2  The node is very close to the gateway, but the signal is poor ==
929 +
930 +
931 +If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
932 +
933 +Like that：Both 905.1Mhz and 902.3Mhz appear on uplink
934 + But they belong to Subband1 and Subband2 of US915 respectively
935 +
936 +Cause: The server and the gateway use different frequency bands (the server uses Subband1, and the gateway uses Subband2)
937 +
938 + 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.
939 +
940 +How to check the frequency band used by the server：
941 +
942 +You can view the information sent by the server: ch_mask in Unconfirmdedatadown
943 +
944 +[[image:image-20230821113255-1.png]]
945 +
946 +According to lorawan's protocol, your first ch_mask is 7 for ChMaskCntl = 7 then 125 kHz channels are disabled. Simultaneously the channels 64 to 71 are set according to the ChMask bit mask.
947 +
948 +[[image:image-20230821113539-2.png]]
949 +
950 +In the second message, the channel 0~~7 is true, which means that your server is using subband2.
951 +
952 +[[image:image-20230821113618-3.png]]
953 +
954 +**Note: lorawan's protocol link——[[LoRaWAN® Regional Parameters v1.0.3revA (lora-alliance.org)>>url:https://resources.lora-alliance.org/document/lorawan-regional-parameters-v1-0-3reva]]**
955 +
870 870  
871 871  )))
image-20230821113255-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +115.7 KB
Content
image-20230821113539-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +71.1 KB
Content
image-20230821113618-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +19.0 KB
Content
image-20230821114047-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +125.6 KB
Content
image-20230926092907-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +64.0 KB
Content
image-20230926093057-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +69.6 KB
Content
image-20230926093233-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +95.8 KB
Content

Applications

Navigation

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