Changes for page Notes for ChirpStack

Last modified by Edwin Chen on 2025/01/30 09:53
<
From version < 116.1 >
edited by Xiaoye
on 2022/10/12 18:45
To version < 108.7 >
edited by Xiaoling
on 2022/07/23 13:57
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoye
1 +XWiki.Xiaoling
Content
... ... @@ -109,14 +109,11 @@
109 109  Configure the gateway
110 110  
111 111  
112 +== 2.5 Step 5. Checking gateway Status ==
112 112  
113 -== 2.5  Step 5. Checking gateway Status ==
114 -
115 -
116 116  [[image:image-20220531172158-6.png]](% style="display:none" %)
117 117  
118 118  
119 -
120 120  gateway Status
121 121  
122 122  [[image:image-20220531172304-7.png]]
... ... @@ -124,48 +124,39 @@
124 124  gateway Status
125 125  
126 126  
124 += 3. Gateway Registration for Basics Station =
127 127  
128 -= 3.  Gateway Registration for Basics Station =
126 +== 3.1 Introduction ==
129 129  
130 -
131 -== 3.1  Introduction ==
132 -
133 -
134 134  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.
135 135  
136 136  ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
137 137  
132 +**Below list the support products and Requirements:**
138 138  
139 -(% style="color:blue" %)**Below list the support products and Requirements:**
140 -
141 141  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]]
142 142  1. Firmware version since :[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]]
143 143  
144 -(% style="color:blue" %)**How to set up chirpStack Basic Station**
137 +**How to set up chirpStack Basic Station**
145 145  
146 146  Users can check out the ChirpStack Basic Station [[link>>https://www.chirpstack.io/gateway-bridge/backends/basic-station/]] and [[forum>>https://forum.chirpstack.io/search?q=basic%20station]]
147 147  
141 +**What do you need to prepare**
148 148  
149 -(% style="color:blue" %)**What do you need to prepare**
150 -
151 151  A gateway that can access the internet normally
152 152  
153 153  
146 +== 3.2 Add Gateway ==
154 154  
155 -== 3.2  Add Gateway ==
156 -
157 -
158 158  [[image:image-20220524164205-10.png]]
159 159  
160 160  
161 -== 3.3  Access the gateway GUI ==
151 +== 3.3 Access the gateway GUI ==
162 162  
163 -
164 164  Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
165 165  
166 166  [[image:image-20220524164319-11.png]]
167 167  
168 -
169 169  User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate
170 170  
171 171  (% class="box" %)
... ... @@ -181,24 +181,20 @@
181 181  [[image:image-20220524164341-12.png]]
182 182  
183 183  
184 -== 3.4  Start Station ==
172 +== 3.4 Start Station ==
185 185  
174 +When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
186 186  
187 -When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
188 188  
177 +== 3.5 Successful Connection ==
189 189  
190 -== 3.5  Successful Connection ==
191 -
192 -
193 193  If user completes the above steps, which will see live date in the ChirpStack.
194 194  
195 195  [[image:image-20220524164448-13.png]]
196 196  
197 197  
184 +== 3.6 Trouble Shooting ==
198 198  
199 -== 3.6  Trouble Shooting ==
200 -
201 -
202 202  User can check the station log in the logread/system log page.
203 203  
204 204  [[image:image-20220531172837-8.png]]
... ... @@ -209,27 +209,10 @@
209 209  [[image:image-20220531172857-9.png]]
210 210  
211 211  
196 += 4. Downlink =
212 212  
213 -= 4.  Downlink =
198 +== 4.1 Chirpstack Downlink Note ==
214 214  
215 -== 4.1 Convert HEX to Base64 ==
216 -
217 -(% 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.**
218 -
219 -[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:
220 -
221 -[[image:image-20221010193350-1.png]]
222 -
223 -
224 -[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]
225 -
226 -[[image:image-20221010193621-2.png]]
227 -
228 -
229 -
230 -== 4.2  Chirpstack Downlink Note ==
231 -
232 -
233 233  [[image:image-20220601102543-2.png]]
234 234  
235 235  Convert the data to Base64
... ... @@ -245,14 +245,12 @@
245 245  Make sure the RX2DR is the same in the end node
246 246  
247 247  
215 +== 4.2 Loraserver Downlink Note ==
248 248  
249 -== 4.3  Loraserver Downlink Note ==
250 -
251 -
252 252  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
253 253  
254 254  (((
255 -**Below is examples:**
220 +Below is examples:
256 256  )))
257 257  
258 258  (% class="box" %)
... ... @@ -268,12 +268,11 @@
268 268  (((
269 269  MQTT Connect to ChirpStack
270 270  
271 -
272 272  
273 273  )))
274 274  
275 275  (((
276 -**After connect**
240 +After connect
277 277  )))
278 278  
279 279  (% class="box" %)
... ... @@ -296,11 +296,19 @@
296 296  MQTT Connect to ChirpStack
297 297  
298 298  
299 -If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB
263 +(((
264 +(% style="color:red" %)Note: Chirpstack use base64 to downlink, so need to convert the downlink payload from HEX to base64 [[https:~~/~~/base64.us/>>url:https://base64.us/]]
265 +)))
300 300  
301 -[[image:image-20220531173658-14.png]]
267 +[[image:image-20220531173601-13.png]]
302 302  
269 +Choose to Use Hex for Encode
303 303  
271 +
272 +If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
273 +
274 +[[image:image-20220531173658-14.png]]
275 +
304 304  (((
305 305  Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码：
306 306  )))
... ... @@ -363,10 +363,8 @@
363 363  )))
364 364  
365 365  
338 +== 4.3 Add the decode function in Chirpstack for the payload ==
366 366  
367 -== 4.3  Add the decode function in Chirpstack for the payload ==
368 -
369 -
370 370  User enters the payload code according to the steps.
371 371  
372 372  [[image:image-20220531173754-15.png]]
... ... @@ -380,10 +380,8 @@
380 380  [[image:image-20220531174046-19.png]]
381 381  
382 382  
353 += 5. Multiply Uplink in ChirpStack =
383 383  
384 -= 5.  Multiply Uplink in ChirpStack =
385 -
386 -
387 387  (((
388 388  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
389 389  )))
... ... @@ -390,17 +390,12 @@
390 390  
391 391  (((
392 392  ChirpStack will auto adjust nbtrans according to uplink rssi. [[link to source>>url:https://github.com/brocaar/chirpstack-network-server/blob/master/internal/adr/adr.go]]
393 -
394 -
395 395  )))
396 396  
397 397  [[image:image-20220526091912-7.png]]
398 398  
399 -
400 400  (((
401 401  nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame.
402 -
403 -
404 404  )))
405 405  
406 406  [[image:image-20220525104359-21.png]]
... ... @@ -407,8 +407,6 @@
407 407  
408 408  (((
409 409  Above behaviour will cause the platform shows below two cases of error:
410 -
411 -
412 412  )))
413 413  
414 414  (((
... ... @@ -418,36 +418,29 @@
418 418  [[image:image-20220525104437-22.png]]
419 419  
420 420  
421 -
422 422  Duplicate transmission in short time
423 423  
424 424  [[image:image-20220601102430-1.png]]
425 425  
426 426  
387 +== 5.1 Solution ==
427 427  
428 -== 5.1  Solution ==
429 -
430 -
431 431  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]]
432 432  
433 -
434 434  (((
435 -(% 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.**
436 -
437 -
392 +~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.
438 438  )))
439 439  
440 440  [[image:image-20220525104532-24.png]]
441 441  
442 442  
443 -**installation path:**
398 +installation path:
444 444  
445 445  [[image:image-20220525104554-25.png]]
446 446  
447 447  
448 -
449 449  (((
450 -(% style="color:blue" %)**2.  Environment variable settings:**
404 +2. Environment variable settings:.
451 451  )))
452 452  
453 453  (((
... ... @@ -455,13 +455,13 @@
455 455  )))
456 456  
457 457  (((
458 -2) Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
412 +2)Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
459 459  )))
460 460  
461 461  [[image:image-20220524165433-33.png]]
462 462  
463 463  
464 -3) Modify the system variable Path and add C:\Go\bin\:
418 +3)Modify the system variable Path and add C:\Go\bin\:
465 465  
466 466  [[image:image-20220524165452-34.png]]
467 467  
... ... @@ -471,9 +471,8 @@
471 471  [[image:image-20220524165517-35.png]]
472 472  
473 473  
428 +3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.
474 474  
475 -(% style="color:blue" %)**3.  Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.**
476 -
477 477  The name of the plugin: Example ADR plugin:
478 478  
479 479  [[image:image-20220524165540-36.png]]
... ... @@ -483,9 +483,8 @@
483 483  [[image:image-20220524165557-37.png]]
484 484  
485 485  
439 +4. Compile the ADR configuration file and generate the exe file.
486 486  
487 -(% style="color:blue" %)**4.  Compile the ADR configuration file and generate the exe file.**
488 -
489 489  1) Create a folder named adr-setting
490 490  
491 491  2) Open the adr-setting folder
... ... @@ -509,9 +509,8 @@
509 509  [[image:image-20220524165623-38.png]]
510 510  
511 511  
464 +5. Add the plugin and run the plugin.
512 512  
513 -(% style="color:blue" %)**5.  Add the plugin and run the plugin.**
514 -
515 515  (((
516 516  The exe file generated in the previous step is placed in the same root directory as chirpstack-network-server.toml, and the ADR plugin is added to the toml file. The location of the addition is as follows:
517 517  )))
... ... @@ -547,57 +547,11 @@
547 547  Finish.
548 548  
549 549  
550 -= **6. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. ** =
501 += 6. Trouble Shooting =
551 551  
503 +== 6.1 MIC Mismatch or MIC Failed ==
552 552  
553 -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.
554 -
555 -This example will be shown how to store/get all the data in two ways:
556 -
557 -**//1). Chirpstack ~-~-> Node-red//**
558 -
559 -[[image:https://github.com/chirpstack/node-red-contrib-chirpstack/blob/master/example_flow.png?raw=true||alt="example_flow.png"]]
560 -
561 -
562 -Use MQTT in Nore-red to subscribe to topics published by chirpstack-application and then continuously write to a file
563 -
564 -[[image:image-20221012174220-2.png]]
565 -
566 -
567 -Each message is continuously logged to a specified file
568 -
569 -[[image:image-20221012174352-3.png]]
570 -
571 -
572 -**//2). MQTT  Sub//**
573 -
574 -If you don't want to store the information via node-red, you can get the output via the subscribe command.
575 -
576 -
577 -**If connecting from the same machine, you can use the following command to receive data:**
578 -
579 -(% class="box infomessage" %)
580 580  (((
581 -mosquitto_sub -h localhost -t "application/#" -v
582 -)))
583 -
584 -
585 -**Different host**
586 -
587 -(% class="box infomessage" %)
588 -(((
589 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
590 -)))
591 -
592 -[[image:image-20221012173639-1.png]]
593 -
594 -
595 -= 7.  Trouble Shooting =
596 -
597 -== 7.1  MIC Mismatch or MIC Failed ==
598 -
599 -
600 -(((
601 601  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
602 602  )))
603 603  
image-20221010193350-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -42.7 KB
Content
image-20221010193621-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -34.2 KB
Content
image-20221012173639-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -56.2 KB
Content
image-20221012174220-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -14.8 KB
Content
image-20221012174352-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -93.0 KB
Content
image-20221012184501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content

Applications

Navigation

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