Changes for page Notes for ChirpStack

Last modified by Edwin Chen on 2025/01/30 09:53
<
From version < 183.1 >
edited by Mengting Qiu
on 2023/11/08 18:01
To version < 163.1 >
edited by Bei Jinggeng
on 2023/07/02 10:09
>
Change comment: Uploaded new attachment "image-20230702100930-11.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Bei
Content
... ... @@ -20,7 +20,7 @@
20 20  
21 21  **1) Have a Chirstack Server.**
22 22  
23 -[[image:image-20230821114047-4.png||height="524" width="990"]]
23 +[[image:image-20220525100058-1.png]]
24 24  
25 25  ChirpStack home page
26 26  
... ... @@ -38,58 +38,11 @@
38 38  )))
39 39  
40 40  
41 -= 2.  Node usage introduction =
41 += 2.  Semtech UDP =
42 42  
43 -== 2.1 Register Node ==
43 +== 2.1  Step 1. Add the Network-servers ==
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 -
93 93  The network-Servers address varies depending on the ChirpStack server setup environment
94 94  
95 95  (% class="box" %)
... ... @@ -101,12 +101,13 @@
101 101  
102 102  (% style="color:red" %)**If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.**
103 103  
57 +
104 104  [[image:image-20220531171609-1.png||height="638" width="1268"]](% style="display:none" %)
105 105  
106 106  Add the Network-servers
107 107  
108 108  
109 -== 3.2  Step 2. Create Gateway-profiles ==
63 +== 2.2  Step 2. Create Gateway-profiles ==
110 110  
111 111  
112 112  [[image:image-20220531171651-2.png||height="632" width="1264"]](% style="display:none" %)
... ... @@ -114,7 +114,7 @@
114 114  Create Gateway-profiles
115 115  
116 116  
117 -== 3.3  Step 3. Create Service-profiles ==
71 +== 2.3  Step 3. Create Service-profiles ==
118 118  
119 119  
120 120  [[image:image-20220531171809-3.png||height="761" width="1265"]]
... ... @@ -129,7 +129,7 @@
129 129  If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
130 130  
131 131  
132 -== 3.4  Step 4. Add the gateway ==
86 +== 2.4  Step 4. Add the gateway ==
133 133  
134 134  
135 135  The example gateway id is: a840411e96744150
... ... @@ -136,6 +136,8 @@
136 136  
137 137  (((
138 138  (% style="color:red" %)**Note : The Gateway EUI and server addresses must match the ChirpStack configuration.**
93 +
94 +
139 139  )))
140 140  
141 141  [[image:image-20220531171923-4.png||height="745" width="1253"]](% style="display:none" %)
... ... @@ -143,12 +143,13 @@
143 143  Add the gateway
144 144  
145 145  
102 +
146 146  [[image:image-20220531172031-5.png]]
147 147  
148 148  Configure the gateway
149 149  
150 150  
151 -== 3.5  Step 5. Checking gateway Status ==
108 +== 2.5  Step 5. Checking gateway Status ==
152 152  
153 153  
154 154  [[image:image-20220531172158-6.png||height="704" width="1167"]](% style="display:none" %)
... ... @@ -162,26 +162,11 @@
162 162  gateway Status
163 163  
164 164  
165 -= 4.  Semtech UDP for ChirpStack v4 =
122 += 3.  Gateway Registration for Basics Station =
166 166  
167 -== 4.1  Step 1. Add the gateway ==
124 +== 3.1  Introduction ==
168 168  
169 169  
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 -
185 185  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.
186 186  
187 187  ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
... ... @@ -202,13 +202,13 @@
202 202  A gateway that can access the internet normally
203 203  
204 204  
205 -== 5.2  Add Gateway ==
147 +== 3.2  Add Gateway ==
206 206  
207 207  
208 208  [[image:image-20220524164205-10.png]]
209 209  
210 210  
211 -== 5.3  Access the gateway GUI ==
153 +== 3.3  Access the gateway GUI ==
212 212  
213 213  
214 214  Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
... ... @@ -222,7 +222,7 @@
222 222  (((
223 223  Service Provider  ~-~->  Choose the ChirpStack/Senet ~-~- Basic Station
224 224  
225 -LNS URI  ~-~->  Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:443 or ws:~/~/xxxx.chirpstack.com:3001
167 +LNS URI  ~-~->  Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:433 or ws:~/~/xxxx.chirpstack.com:3001
226 226  
227 227  LNS TLS trust  ~-~->  Upload the TLS Certificate
228 228  )))
... ... @@ -231,13 +231,13 @@
231 231  [[image:image-20220524164341-12.png]]
232 232  
233 233  
234 -== 5.4  Start Station ==
176 +== 3.4  Start Station ==
235 235  
236 236  
237 237  When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
238 238  
239 239  
240 -== 5.5  Successful Connection ==
182 +== 3.5  Successful Connection ==
241 241  
242 242  
243 243  If user completes the above steps, which will see live date in the ChirpStack.
... ... @@ -245,7 +245,7 @@
245 245  [[image:image-20220524164448-13.png]]
246 246  
247 247  
248 -== 5.6  Trouble Shooting ==
190 +== 3.6  Trouble Shooting ==
249 249  
250 250  
251 251  User can check the station log in the logread/system log page.
... ... @@ -258,7 +258,7 @@
258 258  [[image:image-20220531172857-9.png]]
259 259  
260 260  
261 -= 6.  How the gateway connects to Chirpstack v3 via gateway-bridge =
203 += 4.  How the gateway connects to Chirpstack v3 via gateway-bridge =
262 262  
263 263  
264 264  (% style="color:blue" %)**Below list the support products and Requirements:**
... ... @@ -279,7 +279,7 @@
279 279  The following example does not have configuration certificates:
280 280  
281 281  
282 -== 6.1  Configure Packet Forwarder ==
224 +== 4.1  Configure Packet Forwarder ==
283 283  
284 284  
285 285  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
... ... @@ -297,7 +297,7 @@
297 297  [[image:image-20221222114220-2.png||height="748" width="931"]]
298 298  
299 299  
300 -== 6.2  Configuring gateway frequency ==
242 +== 4.2  Configuring gateway frequency ==
301 301  
302 302  
303 303  (% style="color:red" %)**Note: Gateway frequencies must match**
... ... @@ -305,7 +305,7 @@
305 305  [[image:image-20221222134830-3.png||height="408" width="923"]]
306 306  
307 307  
308 -== 6.3  Generate and modify the gateway-bridge configuration file ==
250 +== 4.3  Generate and modify the gateway-bridge configuration file ==
309 309  
310 310  
311 311  **1）Generate the gateway-bridge configuration file**
... ... @@ -332,7 +332,7 @@
332 332  [[image:image-20230415165254-1.png||height="583" width="956"]]
333 333  
334 334  
335 -== 6.4  Debug ==
277 +== 4.4  Debug ==
336 336  
337 337  
338 338  After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection
... ... @@ -355,7 +355,7 @@
355 355  More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]**
356 356  
357 357  
358 -== 6.5  (Re)start and stop gateway-bridge ==
300 +== 4.5  (Re)start and stop gateway-bridge ==
359 359  
360 360  
361 361  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -376,7 +376,7 @@
376 376  )))
377 377  
378 378  
379 -= 7.  How the gateway connects to Chirpstack v4 via gateway-bridge =
321 += 5.  How the gateway connects to Chirpstack v4 via gateway-bridge =
380 380  
381 381  
382 382  (% style="color:blue" %)**Below list the support products and Requirements:**
... ... @@ -394,7 +394,7 @@
394 394  A gateway that can access the internet normally
395 395  
396 396  
397 -== 7.1  Configure Packet Forwarder ==
339 +== 5.1  Configure Packet Forwarder ==
398 398  
399 399  
400 400  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
... ... @@ -412,7 +412,7 @@
412 412  [[image:image-20221222114220-2.png||height="748" width="931"]]
413 413  
414 414  
415 -== 7.2  Configuring gateway frequency ==
357 +== 5.2  Configuring gateway frequency ==
416 416  
417 417  
418 418  (% style="color:red" %)**Note: Gateway frequencies must match**
... ... @@ -420,7 +420,7 @@
420 420  [[image:image-20221222134830-3.png||height="408" width="923"]]
421 421  
422 422  
423 -== 7.3  Modify the gateway-bridge configuration file ==
365 +== 5.3  Modify the gateway-bridge configuration file ==
424 424  
425 425  
426 426  Run the gateway command line command to modify the gateway-bridge configuration file:
... ... @@ -435,7 +435,6 @@
435 435  
436 436  [[image:image-20221222140203-4.png||height="875" width="806"]]
437 437  
438 -
439 439  [[image:image-20221230094246-1.png||height="768" width="783"]]
440 440  
441 441  (% class="wikigeneratedid" id="H" %)
... ... @@ -442,7 +442,7 @@
442 442  After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
443 443  
444 444  
445 -== 7.4  (Re)start and stop gateway-bridge ==
386 +== 5.4  (Re)start and stop gateway-bridge ==
446 446  
447 447  
448 448  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -463,7 +463,7 @@
463 463  )))
464 464  
465 465  
466 -== 7.5  Successful Connection ==
407 +== 5.5  Successful Connection ==
467 467  
468 468  
469 469  [[image:image-20221222141754-5.png||height="488" width="1150"]]
... ... @@ -472,27 +472,34 @@
472 472  [[image:image-20221222141830-6.png||height="582" width="1153"]]
473 473  
474 474  
475 -= 8.  Downlink =
416 += 6.  Downlink =
476 476  
418 +== 6.1  Convert HEX to Base64 ==
477 477  
478 -=== 8.1 Chirpstack Downlink Note ===
479 479  
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.**
480 480  
481 -==== Select HEX format for downlink ====
423 +**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
482 482  
425 +[[image:image-20221010193350-1.png]]
483 483  
484 -(% style="color:red" %)**Note: The end node user manual provides HEX format of the downlink commands, so users can directly select HEX format downlink.**
485 485  
486 486  
487 -[[image:image-20231108171112-5.png||height="629" width="1117"]]
429 +**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
488 488  
431 +[[image:image-20221010193621-2.png]]
489 489  
490 -[[image:image-20231108171145-6.png||height="497" width="1101"]]
491 491  
434 +== 6.2  Chirpstack Downlink Note ==
492 492  
493 493  
437 +[[image:image-20220601102543-2.png]]
494 494  
439 +**Convert the data to Base64**
495 495  
441 +(% style="display:none" %) (%%)
442 +
443 +
496 496  [[image:image-20220531173236-10.png||height="597" width="1215"]]
497 497  
498 498  **Check ChripStack downlink DataRate**
... ... @@ -504,7 +504,7 @@
504 504  **Make sure the RX2DR is the same in the end node**
505 505  
506 506  
507 -== 8.3  Loraserver Downlink Note ==
455 +== 6.3  Loraserver Downlink Note ==
508 508  
509 509  
510 510  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
... ... @@ -554,11 +554,13 @@
554 554  **MQTT Connect to ChirpStack**
555 555  
556 556  
505 +**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**
557 557  
558 -(((
559 -Downlink payload encode javescript code.
507 +[[image:image-20220531173658-14.png]]
560 560  
561 -We can run the following Javsscript code on the site:
509 +
510 +(((
511 +Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码：
562 562  )))
563 563  
564 564  (% class="box" %)
... ... @@ -619,7 +619,7 @@
619 619  )))
620 620  
621 621  
622 -== 8.4  Add the decode function in Chirpstack for the payload ==
572 +== 6.4  Add the decode function in Chirpstack for the payload ==
623 623  
624 624  
625 625  User enters the payload code according to the steps.
... ... @@ -637,7 +637,7 @@
637 637  [[image:image-20220531174046-19.png]]
638 638  
639 639  
640 -= 9.  Multiply Uplink in ChirpStack =
590 += 7.  Multiply Uplink in ChirpStack =
641 641  
642 642  
643 643  (((
... ... @@ -677,16 +677,19 @@
677 677  
678 678  **Duplicate transmission in short time**
679 679  
680 -[[image:image-20220601102430-1.png||height="508" width="1120"]]
630 +[[image:image-20220601102430-1.png||height="598" width="1319"]]
681 681  
682 682  
683 -== 9.1  Solution ==
633 +== 7.1  Solution ==
684 684  
685 685  
686 686  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]]
687 687  
638 +
688 688  (((
689 689  (% 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 +
690 690  )))
691 691  
692 692  [[image:image-20220525104532-24.png]]
... ... @@ -799,7 +799,7 @@
799 799  Finish.
800 800  
801 801  
802 -= 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
755 += 8.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
803 803  
804 804  
805 805  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.
... ... @@ -809,7 +809,7 @@
809 809  (% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//**
810 810  
811 811  
812 -[[image:image-20221012184501-1.png||height="608" width="1041"]]
765 +[[image:image-20221012184501-1.png]]
813 813  
814 814  
815 815  Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
... ... @@ -845,12 +845,11 @@
845 845  **mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v**
846 846  )))
847 847  
848 -[[image:image-20221012173639-1.png||height="273" width="1206"]]
801 +[[image:image-20221012173639-1.png]]
849 849  
803 += 9.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
850 850  
851 -= 11.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
852 852  
853 -
854 854  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:
855 855  
856 856  * LHT65N register on LPS8v2 Built-In ChirpStack server already
... ... @@ -859,7 +859,7 @@
859 859  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
860 860  
861 861  
862 -== 11.1 Link Node-Red to Local ChirpStack ==
814 +== 9.1 Link Node-Red to Local ChirpStack ==
863 863  
864 864  
865 865  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"]]**
... ... @@ -886,7 +886,7 @@
886 886  [[image:image-20230527144206-2.png||height="590" width="1136"]]
887 887  
888 888  
889 -(% style="color:blue" %)**3.** **Finally, click "Update" and Deploy**
841 +(% style="color:blue" %)3. **Finally, click "Update" and Deploy**
890 890  
891 891  "Connected" indicates that the Link Node-red to Local Chirpstack is normal.
892 892  
... ... @@ -893,7 +893,7 @@
893 893  [[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"]]
894 894  
895 895  
896 -== 11.2 Check result. ==
848 +== 9.2 Check result. ==
897 897  
898 898  
899 899  Users can check logs by adding debug.
... ... @@ -903,9 +903,9 @@
903 903  [[image:image-20230529150923-1.png||height="424" width="1118"]]
904 904  
905 905  
906 -= 12.  Trouble Shooting =
858 += 10.  Trouble Shooting =
907 907  
908 -== 12.1  MIC Mismatch or MIC Failed ==
860 +== 10.1  MIC Mismatch or MIC Failed ==
909 909  
910 910  
911 911  (((
... ... @@ -915,34 +915,5 @@
915 915  (((
916 916  Under normal circumstances, users need to change the APPKEY to solve this problem.
917 917  
918 -
919 -== 12.2  The node is very close to the gateway, but the signal is poor ==
920 -
921 -
922 -If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
923 -
924 -Like that：Both 905.1Mhz and 902.3Mhz appear on uplink
925 - But they belong to Subband1 and Subband2 of US915 respectively
926 -
927 -Cause: The server and the gateway use different frequency bands (the server uses Subband1, and the gateway uses Subband2)
928 -
929 - 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.
930 -
931 -How to check the frequency band used by the server：
932 -
933 -You can view the information sent by the server: ch_mask in Unconfirmdedatadown
934 -
935 -[[image:image-20230821113255-1.png]]
936 -
937 -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.
938 -
939 -[[image:image-20230821113539-2.png]]
940 -
941 -In the second message, the channel 0~~7 is true, which means that your server is using subband2.
942 -
943 -[[image:image-20230821113618-3.png]]
944 -
945 -**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]]**
946 -
947 947  
948 948  )))
image-20230821113255-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -115.7 KB
Content
image-20230821113539-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -71.1 KB
Content
image-20230821113618-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.0 KB
Content
image-20230821114047-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -125.6 KB
Content
image-20230926092907-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -64.0 KB
Content
image-20230926093057-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -69.6 KB
Content
image-20230926093233-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -95.8 KB
Content
image-20231108140540-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20231108164914-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -37.2 KB
Content
image-20231108165128-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -43.3 KB
Content
image-20231108165158-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -60.8 KB
Content
image-20231108171112-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -47.7 KB
Content
image-20231108171145-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.1 KB
Content

Applications

Navigation

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