Changes for page Notes for ChirpStack

Last modified by Kilight Cao on 2024/02/03 14:38
<
From version < 176.1 >
edited by Kilight Cao
on 2023/09/26 09:32
To version < 175.1 >
edited by Kilight Cao
on 2023/09/26 09:32
>
Change comment: Uploaded new attachment "image-20230926093233-3.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -80,7 +80,7 @@
80 80  [[image:image-20230702100930-11.png||height="613" width="1098"]]
81 81  
82 82  
83 -= 3.  Semtech UDP for ChirpStack v3 =
83 += 3.  Semtech UDP =
84 84  
85 85  == 3.1  Step 1. Add the Network-servers ==
86 86  
... ... @@ -160,26 +160,12 @@
160 160  
161 161  gateway Status
162 162  
163 -= 4.  Semtech UDP for ChirpStack v4 =
164 164  
164 += 4.  Gateway Registration for Basics Station =
165 165  
166 -== 4.1  Step 1. Add the gateway ==
166 +== 4.1  Introduction ==
167 167  
168 -[[image:image-20230926092907-1.png||height="598" width="1007"]]
169 169  
170 -
171 -[[image:image-20230926093057-2.png||height="541" width="1002"]]
172 -
173 -
174 -== 4.2  Step 2. Checking gateway Status ==
175 -
176 -[[image:image-20230926093233-3.png||height="581" width="1018"]]
177 -
178 -= 5.  Gateway Registration for Basics Station =
179 -
180 -== 5.1  Introduction ==
181 -
182 -
183 183  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.
184 184  
185 185  ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
... ... @@ -200,13 +200,13 @@
200 200  A gateway that can access the internet normally
201 201  
202 202  
203 -== 5.2  Add Gateway ==
189 +== 4.2  Add Gateway ==
204 204  
205 205  
206 206  [[image:image-20220524164205-10.png]]
207 207  
208 208  
209 -== 5.3  Access the gateway GUI ==
195 +== 4.3  Access the gateway GUI ==
210 210  
211 211  
212 212  Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
... ... @@ -229,13 +229,13 @@
229 229  [[image:image-20220524164341-12.png]]
230 230  
231 231  
232 -== 5.4  Start Station ==
218 +== 4.4  Start Station ==
233 233  
234 234  
235 235  When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
236 236  
237 237  
238 -== 5.5  Successful Connection ==
224 +== 4.5  Successful Connection ==
239 239  
240 240  
241 241  If user completes the above steps, which will see live date in the ChirpStack.
... ... @@ -243,7 +243,7 @@
243 243  [[image:image-20220524164448-13.png]]
244 244  
245 245  
246 -== 5.6  Trouble Shooting ==
232 +== 4.6  Trouble Shooting ==
247 247  
248 248  
249 249  User can check the station log in the logread/system log page.
... ... @@ -256,7 +256,7 @@
256 256  [[image:image-20220531172857-9.png]]
257 257  
258 258  
259 -= 6.  How the gateway connects to Chirpstack v3 via gateway-bridge =
245 += 5.  How the gateway connects to Chirpstack v3 via gateway-bridge =
260 260  
261 261  
262 262  (% style="color:blue" %)**Below list the support products and Requirements:**
... ... @@ -277,7 +277,7 @@
277 277  The following example does not have configuration certificates:
278 278  
279 279  
280 -== 6.1  Configure Packet Forwarder ==
266 +== 5.1  Configure Packet Forwarder ==
281 281  
282 282  
283 283  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
... ... @@ -295,7 +295,7 @@
295 295  [[image:image-20221222114220-2.png||height="748" width="931"]]
296 296  
297 297  
298 -== 6.2  Configuring gateway frequency ==
284 +== 5.2  Configuring gateway frequency ==
299 299  
300 300  
301 301  (% style="color:red" %)**Note: Gateway frequencies must match**
... ... @@ -303,7 +303,7 @@
303 303  [[image:image-20221222134830-3.png||height="408" width="923"]]
304 304  
305 305  
306 -== 6.3  Generate and modify the gateway-bridge configuration file ==
292 +== 5.3  Generate and modify the gateway-bridge configuration file ==
307 307  
308 308  
309 309  **1）Generate the gateway-bridge configuration file**
... ... @@ -330,7 +330,7 @@
330 330  [[image:image-20230415165254-1.png||height="583" width="956"]]
331 331  
332 332  
333 -== 6.4  Debug ==
319 +== 5.4  Debug ==
334 334  
335 335  
336 336  After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection
... ... @@ -353,7 +353,7 @@
353 353  More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]**
354 354  
355 355  
356 -== 6.5  (Re)start and stop gateway-bridge ==
342 +== 5.5  (Re)start and stop gateway-bridge ==
357 357  
358 358  
359 359  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -374,7 +374,7 @@
374 374  )))
375 375  
376 376  
377 -= 7.  How the gateway connects to Chirpstack v4 via gateway-bridge =
363 += 6.  How the gateway connects to Chirpstack v4 via gateway-bridge =
378 378  
379 379  
380 380  (% style="color:blue" %)**Below list the support products and Requirements:**
... ... @@ -392,7 +392,7 @@
392 392  A gateway that can access the internet normally
393 393  
394 394  
395 -== 7.1  Configure Packet Forwarder ==
381 +== 6.1  Configure Packet Forwarder ==
396 396  
397 397  
398 398  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
... ... @@ -410,7 +410,7 @@
410 410  [[image:image-20221222114220-2.png||height="748" width="931"]]
411 411  
412 412  
413 -== 7.2  Configuring gateway frequency ==
399 +== 6.2  Configuring gateway frequency ==
414 414  
415 415  
416 416  (% style="color:red" %)**Note: Gateway frequencies must match**
... ... @@ -418,7 +418,7 @@
418 418  [[image:image-20221222134830-3.png||height="408" width="923"]]
419 419  
420 420  
421 -== 7.3  Modify the gateway-bridge configuration file ==
407 +== 6.3  Modify the gateway-bridge configuration file ==
422 422  
423 423  
424 424  Run the gateway command line command to modify the gateway-bridge configuration file:
... ... @@ -439,7 +439,7 @@
439 439  After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
440 440  
441 441  
442 -== 7.4  (Re)start and stop gateway-bridge ==
428 +== 6.4  (Re)start and stop gateway-bridge ==
443 443  
444 444  
445 445  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -460,7 +460,7 @@
460 460  )))
461 461  
462 462  
463 -== 7.5  Successful Connection ==
449 +== 6.5  Successful Connection ==
464 464  
465 465  
466 466  [[image:image-20221222141754-5.png||height="488" width="1150"]]
... ... @@ -469,9 +469,9 @@
469 469  [[image:image-20221222141830-6.png||height="582" width="1153"]]
470 470  
471 471  
472 -= 8.  Downlink =
458 += 7.  Downlink =
473 473  
474 -== 8.1  Convert HEX to Base64 ==
460 +== 7.1  Convert HEX to Base64 ==
475 475  
476 476  
477 477  (% 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.**
... ... @@ -487,7 +487,7 @@
487 487  [[image:image-20221010193621-2.png]]
488 488  
489 489  
490 -== 8.2  Chirpstack Downlink Note ==
476 +== 7.2  Chirpstack Downlink Note ==
491 491  
492 492  
493 493  [[image:image-20220601102543-2.png]]
... ... @@ -508,7 +508,7 @@
508 508  **Make sure the RX2DR is the same in the end node**
509 509  
510 510  
511 -== 8.3  Loraserver Downlink Note ==
497 +== 7.3  Loraserver Downlink Note ==
512 512  
513 513  
514 514  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
... ... @@ -625,7 +625,7 @@
625 625  )))
626 626  
627 627  
628 -== 8.4  Add the decode function in Chirpstack for the payload ==
614 +== 7.4  Add the decode function in Chirpstack for the payload ==
629 629  
630 630  
631 631  User enters the payload code according to the steps.
... ... @@ -643,7 +643,7 @@
643 643  [[image:image-20220531174046-19.png]]
644 644  
645 645  
646 -= 9.  Multiply Uplink in ChirpStack =
632 += 8.  Multiply Uplink in ChirpStack =
647 647  
648 648  
649 649  (((
... ... @@ -686,7 +686,7 @@
686 686  [[image:image-20220601102430-1.png||height="598" width="1319"]]
687 687  
688 688  
689 -== 9.1  Solution ==
675 +== 8.1  Solution ==
690 690  
691 691  
692 692  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]]
... ... @@ -808,7 +808,7 @@
808 808  Finish.
809 809  
810 810  
811 -= 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
797 += 9.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
812 812  
813 813  
814 814  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.
... ... @@ -856,7 +856,7 @@
856 856  
857 857  [[image:image-20221012173639-1.png]]
858 858  
859 -= 11.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
845 += 10.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
860 860  
861 861  
862 862  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:
... ... @@ -867,7 +867,7 @@
867 867  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
868 868  
869 869  
870 -== 11.1 Link Node-Red to Local ChirpStack ==
856 +== 10.1 Link Node-Red to Local ChirpStack ==
871 871  
872 872  
873 873  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"]]**
... ... @@ -901,7 +901,7 @@
901 901  [[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"]]
902 902  
903 903  
904 -== 11.2 Check result. ==
890 +== 10.2 Check result. ==
905 905  
906 906  
907 907  Users can check logs by adding debug.
... ... @@ -911,9 +911,9 @@
911 911  [[image:image-20230529150923-1.png||height="424" width="1118"]]
912 912  
913 913  
914 -= 12.  Trouble Shooting =
900 += 11.  Trouble Shooting =
915 915  
916 -== 12.1  MIC Mismatch or MIC Failed ==
902 +== 11.1  MIC Mismatch or MIC Failed ==
917 917  
918 918  
919 919  (((
... ... @@ -924,7 +924,7 @@
924 924  Under normal circumstances, users need to change the APPKEY to solve this problem.
925 925  
926 926  
927 -== 12.2  The node is very close to the gateway, but the signal is poor ==
913 +== 11.2  The node is very close to the gateway, but the signal is poor ==
928 928  
929 929  If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
930 930  

Applications

Navigation

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