Changes for page Notes for ChirpStack

Last modified by Kilight Cao on 2024/02/03 14:38
<
From version < 175.1 >
edited by Kilight Cao
on 2023/09/26 09:32
To version < 176.1 >
edited by Kilight Cao
on 2023/09/26 09:32
>
Change comment: There is no comment for this version

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 =
83 += 3.  Semtech UDP for ChirpStack v3 =
84 84  
85 85  == 3.1  Step 1. Add the Network-servers ==
86 86  
... ... @@ -160,12 +160,26 @@
160 160  
161 161  gateway Status
162 162  
163 += 4.  Semtech UDP for ChirpStack v4 =
163 163  
164 -= 4.  Gateway Registration for Basics Station =
165 165  
166 -== 4.1  Introduction ==
166 +== 4.1  Step 1. Add the gateway ==
167 167  
168 +[[image:image-20230926092907-1.png||height="598" width="1007"]]
168 168  
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 +
169 169  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.
170 170  
171 171  ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
... ... @@ -186,13 +186,13 @@
186 186  A gateway that can access the internet normally
187 187  
188 188  
189 -== 4.2  Add Gateway ==
203 +== 5.2  Add Gateway ==
190 190  
191 191  
192 192  [[image:image-20220524164205-10.png]]
193 193  
194 194  
195 -== 4.3  Access the gateway GUI ==
209 +== 5.3  Access the gateway GUI ==
196 196  
197 197  
198 198  Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
... ... @@ -215,13 +215,13 @@
215 215  [[image:image-20220524164341-12.png]]
216 216  
217 217  
218 -== 4.4  Start Station ==
232 +== 5.4  Start Station ==
219 219  
220 220  
221 221  When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
222 222  
223 223  
224 -== 4.5  Successful Connection ==
238 +== 5.5  Successful Connection ==
225 225  
226 226  
227 227  If user completes the above steps, which will see live date in the ChirpStack.
... ... @@ -229,7 +229,7 @@
229 229  [[image:image-20220524164448-13.png]]
230 230  
231 231  
232 -== 4.6  Trouble Shooting ==
246 +== 5.6  Trouble Shooting ==
233 233  
234 234  
235 235  User can check the station log in the logread/system log page.
... ... @@ -242,7 +242,7 @@
242 242  [[image:image-20220531172857-9.png]]
243 243  
244 244  
245 -= 5.  How the gateway connects to Chirpstack v3 via gateway-bridge =
259 += 6.  How the gateway connects to Chirpstack v3 via gateway-bridge =
246 246  
247 247  
248 248  (% style="color:blue" %)**Below list the support products and Requirements:**
... ... @@ -263,7 +263,7 @@
263 263  The following example does not have configuration certificates:
264 264  
265 265  
266 -== 5.1  Configure Packet Forwarder ==
280 +== 6.1  Configure Packet Forwarder ==
267 267  
268 268  
269 269  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
... ... @@ -281,7 +281,7 @@
281 281  [[image:image-20221222114220-2.png||height="748" width="931"]]
282 282  
283 283  
284 -== 5.2  Configuring gateway frequency ==
298 +== 6.2  Configuring gateway frequency ==
285 285  
286 286  
287 287  (% style="color:red" %)**Note: Gateway frequencies must match**
... ... @@ -289,7 +289,7 @@
289 289  [[image:image-20221222134830-3.png||height="408" width="923"]]
290 290  
291 291  
292 -== 5.3  Generate and modify the gateway-bridge configuration file ==
306 +== 6.3  Generate and modify the gateway-bridge configuration file ==
293 293  
294 294  
295 295  **1）Generate the gateway-bridge configuration file**
... ... @@ -316,7 +316,7 @@
316 316  [[image:image-20230415165254-1.png||height="583" width="956"]]
317 317  
318 318  
319 -== 5.4  Debug ==
333 +== 6.4  Debug ==
320 320  
321 321  
322 322  After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection
... ... @@ -339,7 +339,7 @@
339 339  More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]**
340 340  
341 341  
342 -== 5.5  (Re)start and stop gateway-bridge ==
356 +== 6.5  (Re)start and stop gateway-bridge ==
343 343  
344 344  
345 345  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -360,7 +360,7 @@
360 360  )))
361 361  
362 362  
363 -= 6.  How the gateway connects to Chirpstack v4 via gateway-bridge =
377 += 7.  How the gateway connects to Chirpstack v4 via gateway-bridge =
364 364  
365 365  
366 366  (% style="color:blue" %)**Below list the support products and Requirements:**
... ... @@ -378,7 +378,7 @@
378 378  A gateway that can access the internet normally
379 379  
380 380  
381 -== 6.1  Configure Packet Forwarder ==
395 +== 7.1  Configure Packet Forwarder ==
382 382  
383 383  
384 384  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
... ... @@ -396,7 +396,7 @@
396 396  [[image:image-20221222114220-2.png||height="748" width="931"]]
397 397  
398 398  
399 -== 6.2  Configuring gateway frequency ==
413 +== 7.2  Configuring gateway frequency ==
400 400  
401 401  
402 402  (% style="color:red" %)**Note: Gateway frequencies must match**
... ... @@ -404,7 +404,7 @@
404 404  [[image:image-20221222134830-3.png||height="408" width="923"]]
405 405  
406 406  
407 -== 6.3  Modify the gateway-bridge configuration file ==
421 +== 7.3  Modify the gateway-bridge configuration file ==
408 408  
409 409  
410 410  Run the gateway command line command to modify the gateway-bridge configuration file:
... ... @@ -425,7 +425,7 @@
425 425  After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
426 426  
427 427  
428 -== 6.4  (Re)start and stop gateway-bridge ==
442 +== 7.4  (Re)start and stop gateway-bridge ==
429 429  
430 430  
431 431  Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
... ... @@ -446,7 +446,7 @@
446 446  )))
447 447  
448 448  
449 -== 6.5  Successful Connection ==
463 +== 7.5  Successful Connection ==
450 450  
451 451  
452 452  [[image:image-20221222141754-5.png||height="488" width="1150"]]
... ... @@ -455,9 +455,9 @@
455 455  [[image:image-20221222141830-6.png||height="582" width="1153"]]
456 456  
457 457  
458 -= 7.  Downlink =
472 += 8.  Downlink =
459 459  
460 -== 7.1  Convert HEX to Base64 ==
474 +== 8.1  Convert HEX to Base64 ==
461 461  
462 462  
463 463  (% 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.**
... ... @@ -473,7 +473,7 @@
473 473  [[image:image-20221010193621-2.png]]
474 474  
475 475  
476 -== 7.2  Chirpstack Downlink Note ==
490 +== 8.2  Chirpstack Downlink Note ==
477 477  
478 478  
479 479  [[image:image-20220601102543-2.png]]
... ... @@ -494,7 +494,7 @@
494 494  **Make sure the RX2DR is the same in the end node**
495 495  
496 496  
497 -== 7.3  Loraserver Downlink Note ==
511 +== 8.3  Loraserver Downlink Note ==
498 498  
499 499  
500 500  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
... ... @@ -611,7 +611,7 @@
611 611  )))
612 612  
613 613  
614 -== 7.4  Add the decode function in Chirpstack for the payload ==
628 +== 8.4  Add the decode function in Chirpstack for the payload ==
615 615  
616 616  
617 617  User enters the payload code according to the steps.
... ... @@ -629,7 +629,7 @@
629 629  [[image:image-20220531174046-19.png]]
630 630  
631 631  
632 -= 8.  Multiply Uplink in ChirpStack =
646 += 9.  Multiply Uplink in ChirpStack =
633 633  
634 634  
635 635  (((
... ... @@ -672,7 +672,7 @@
672 672  [[image:image-20220601102430-1.png||height="598" width="1319"]]
673 673  
674 674  
675 -== 8.1  Solution ==
689 +== 9.1  Solution ==
676 676  
677 677  
678 678  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]]
... ... @@ -794,7 +794,7 @@
794 794  Finish.
795 795  
796 796  
797 -= 9.  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. =
798 798  
799 799  
800 800  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.
... ... @@ -842,7 +842,7 @@
842 842  
843 843  [[image:image-20221012173639-1.png]]
844 844  
845 -= 10.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
859 += 11.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
846 846  
847 847  
848 848  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:
... ... @@ -853,7 +853,7 @@
853 853  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
854 854  
855 855  
856 -== 10.1 Link Node-Red to Local ChirpStack ==
870 +== 11.1 Link Node-Red to Local ChirpStack ==
857 857  
858 858  
859 859  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"]]**
... ... @@ -887,7 +887,7 @@
887 887  [[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"]]
888 888  
889 889  
890 -== 10.2 Check result. ==
904 +== 11.2 Check result. ==
891 891  
892 892  
893 893  Users can check logs by adding debug.
... ... @@ -897,9 +897,9 @@
897 897  [[image:image-20230529150923-1.png||height="424" width="1118"]]
898 898  
899 899  
900 -= 11.  Trouble Shooting =
914 += 12.  Trouble Shooting =
901 901  
902 -== 11.1  MIC Mismatch or MIC Failed ==
916 +== 12.1  MIC Mismatch or MIC Failed ==
903 903  
904 904  
905 905  (((
... ... @@ -910,7 +910,7 @@
910 910  Under normal circumstances, users need to change the APPKEY to solve this problem.
911 911  
912 912  
913 -== 11.2  The node is very close to the gateway, but the signal is poor ==
927 +== 12.2  The node is very close to the gateway, but the signal is poor ==
914 914  
915 915  If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
916 916  

Applications

Navigation

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