Changes for page Notes for ChirpStack

Last modified by Kilight Cao on 2024/09/24 15:23
<
From version < 138.4 >
edited by Xiaoling
on 2023/04/21 15:51
To version < 103.1 >
edited by Xiaoling
on 2022/05/31 17:39
>
Change comment: Uploaded new attachment "image-20220531173939-17.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -5,20 +5,17 @@
5 5  
6 6  
7 7  
8 -= 1.  Introduction =
8 += 1. Introduction =
9 9  
10 -
11 11  (% style="color:black" %)The ChirpStack open-source LoRaWAN Network Server stack provides open-source components for LoRaWAN networks And the Chirpstack supports the users in building a private LoRaWAN Server. For more info please refer to this [[link>>url:https://www.chirpstack.io/]]
12 12  
13 13  (((
14 14  (% style="color:black" %)The dragino gateway can connect the ChirpStack server via Semtech UDP or Semtech Basic Station.
15 -
16 -
17 17  )))
18 18  
19 -(% style="color:blue" %)**Prerequisite:**
16 +**Prerequisite**
20 20  
21 -**1) Have a Chirstack Server.**
18 +1) Have a Chirstack Server.
22 22  
23 23  [[image:image-20220525100058-1.png]]
24 24  
... ... @@ -25,52 +25,47 @@
25 25  ChirpStack home page
26 26  
27 27  
25 +2) Gateway model support
28 28  
29 -**2) Gateway model support**
30 -
31 31  (% class="box" %)
32 32  (((
33 33  (((
34 34  Semtech UDP : **All Model**
35 -Basic Station : [[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]]
36 -(% style="color:red" %)**Note** (%%): the firmware needs >[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]  if use the Bais station
31 +Basic Station : , , 
32 +**Note** : the firmware needs >  if use the Bais station
37 37  )))
38 38  )))
39 39  
40 40  
41 -= 2.  Semtech UDP =
42 42  
43 -== 2.1  Step 1. Add the Network-servers ==
38 += 2. Semtech UDP =
44 44  
40 +== 2.1 Step 1. Add the Network-servers ==
45 45  
46 46  The network-Servers address varies depending on the ChirpStack server setup environment
47 47  
48 48  (% class="box" %)
49 49  (((
50 - Windows       ~-~->  Network-server server *  :  localhost:8000
51 - Linux  ~-~->  Network-server server *  :  chirpstack-network-server:8000
46 + Windows       ~-~->Network-server server * : localhost:8000
47 + Linux         ~-~->Network-server server * : chirpstack-network-server:8000
52 52  )))
53 53  
50 +If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.
54 54  
55 -(% style="color:red" %)**If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.**
56 -
57 -
58 58  [[image:image-20220531171609-1.png]]
59 59  
60 60  Add the Network-servers
61 61  
62 62  
63 -== 2.2  Step 2. Create Gateway-profiles ==
57 +== 2.2 Step 2. Create Gateway-profiles ==
64 64  
65 -
66 66  [[image:image-20220531171651-2.png]]
67 67  
68 68  Create Gateway-profiles
69 69  
70 70  
71 -== 2.3  Step 3. Create Service-profiles ==
64 +== 2.3 Step 3. Create Service-profiles ==
72 72  
73 -
74 74  [[image:image-20220531171809-3.png]]
75 75  
76 76  Create Service-profiles
... ... @@ -83,35 +83,29 @@
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 ==
78 +== 2.4 Step 4. Add the gateway ==
87 87  
88 -
89 89  The example gateway id is: a840411e96744150
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]](% style="display:none" %)
98 98  
88 +
99 99  Add the gateway
100 100  
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 ==
96 +== 2.5 Step 5. Checking gateway Status ==
109 109  
110 -
111 111  [[image:image-20220531172158-6.png]](% style="display:none" %)
112 112  
113 113  
114 -
115 115  gateway Status
116 116  
117 117  [[image:image-20220531172304-7.png]]
... ... @@ -119,45 +119,39 @@
119 119  gateway Status
120 120  
121 121  
122 -= 3.  Gateway Registration for Basics Station =
108 += 3. Gateway Registration for Basics Station =
123 123  
124 -== 3.1  Introduction ==
110 +== 3.1 Introduction ==
125 125  
126 -
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.
130 130  
116 +**Below list the support products and Requirements:**
131 131  
132 -(% style="color:blue" %)**Below list the support products and Requirements:**
133 -
134 134  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]]
135 135  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/]]
136 136  
137 -(% style="color:blue" %)**How to set up chirpStack Basic Station**
121 +**How to set up chirpStack Basic Station**
138 138  
139 139  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]]
140 140  
125 +**What do you need to prepare**
141 141  
142 -(% style="color:blue" %)**What do you need to prepare**
143 -
144 144  A gateway that can access the internet normally
145 145  
146 146  
147 -== 3.2  Add Gateway ==
130 +== 3.2 Add Gateway ==
148 148  
149 -
150 150  [[image:image-20220524164205-10.png]]
151 151  
152 152  
153 -== 3.3  Access the gateway GUI ==
135 +== 3.3 Access the gateway GUI ==
154 154  
155 -
156 156  Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
157 157  
158 158  [[image:image-20220524164319-11.png]]
159 159  
160 -
161 161  User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate
162 162  
163 163  (% class="box" %)
... ... @@ -173,23 +173,20 @@
173 173  [[image:image-20220524164341-12.png]]
174 174  
175 175  
176 -== 3.4  Start Station ==
156 +== 3.4 Start Station ==
177 177  
158 +When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
178 178  
179 -When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
180 180  
161 +== 3.5 Successful Connection ==
181 181  
182 -== 3.5  Successful Connection ==
183 -
184 -
185 185  If user completes the above steps, which will see live date in the ChirpStack.
186 186  
187 187  [[image:image-20220524164448-13.png]]
188 188  
189 189  
190 -== 3.6  Trouble Shooting ==
168 +== 3.6 Trouble Shooting ==
191 191  
192 -
193 193  User can check the station log in the logread/system log page.
194 194  
195 195  [[image:image-20220531172837-8.png]]
... ... @@ -200,264 +200,31 @@
200 200  [[image:image-20220531172857-9.png]]
201 201  
202 202  
203 -= 4.  How the gateway connects to Chirpstack v3 via gateway-bridge =
180 += 4. Downlink =
204 204  
182 +== 4.1 Chirpstack Downlink Note ==
205 205  
206 -(% style="color:blue" %)**Below list the support products and Requirements:**
184 +[[image:image-20220525101223-9.png]]
207 207  
208 -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]],[[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]]
209 -1. Firmware version since: [[Chirpstack-Bridge-V3.14.6>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V3.14.6-Bridge--build-v5.4.1679487778-20230322-2024/]]
186 +Convert the data to Base64
210 210  
211 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
212 212  
213 -Users can check out the ChirpStack gateway-bridge v3 [[link>>https://www.chirpstack.io/gateway-bridge/gateway/dragino/]]
189 +[[image:image-20220531173236-10.png]]
214 214  
191 +Check ChripStack downlink DataRate
215 215  
216 -(% style="color:blue" %)**What do you need to prepare**
217 217  
218 -A gateway that can access the internet normally
219 -
220 -
221 -The following example does not have configuration certificates:
222 -
223 -
224 -== 4.1  Configure Packet Forwarder ==
225 -
226 -
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
228 -
229 -* In the (% style="color:blue" %)**LoRaWAN** (%%)menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP**
230 -
231 -* Make sure the following settings are set:
232 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
233 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
234 -** **Server port for upstream:** //1700//
235 -** **Server port for downstream:** //1700//
236 -
237 - Click (% style="color:blue" %)**Save & Apply**.
238 -
239 -[[image:image-20221222114220-2.png||height="748" width="931"]]
240 -
241 -
242 -== 4.2  Configuring gateway frequency ==
243 -
244 -
245 -(% style="color:red" %)**Note: Gateway frequencies must match**
246 -
247 -[[image:image-20221222134830-3.png||height="408" width="923"]]
248 -
249 -
250 -== 4.3  Generate and modify the gateway-bridge configuration file ==
251 -
252 -
253 -**1）Generate the gateway-bridge configuration file**
254 -
255 -By default, the configuration file is not up-to-date,so the user needs to rebuild the gateway-bridge configuration file.
256 -
257 -Users need to access the command line of the gateway through SSH,Then type the following command:
258 -
259 -(% class="box infomessage" %)
260 -(((
261 -/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
262 -)))
263 -
264 -
265 -**2）modify the gateway-bridge configuration file**
266 -
267 -The user needs to modify the server address in line 252 in the configuration file
268 -
269 -(% class="box infomessage" %)
270 -(((
271 -vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
272 -)))
273 -
274 -[[image:image-20230415165254-1.png||height="583" width="956"]]
275 -
276 -
277 -== 4.4  Debug ==
278 -
279 -
280 -After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection
281 -
282 -(% class="box infomessage" %)
283 -(((
284 -/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
285 -)))
286 -
287 -If the gateway-bridge connection is normal, the debug log displays **"connected to mqtt broker"**.
288 -
289 -[[image:image-20230415170404-2.png]]
290 -
291 -
292 -If the debug log shows "**connection error**", check that the server port or server is correct
293 -
294 -[[image:image-20230415170854-3.png]]
295 -
296 -
297 -More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]**
298 -
299 -
300 -== 4.5  (Re)start and stop gateway-bridge ==
301 -
302 -
303 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
304 -
305 -(% class="box infomessage" %)
306 -(((
307 -**# start**
308 -
309 -/etc/init.d/chirpstack-gateway-bridge start
310 -
311 -**# stop**
312 -
313 -/etc/init.d/chirpstack-gateway-bridge stop
314 -
315 -**# restart**
316 -
317 -/etc/init.d/chirpstack-gateway-bridge restart
318 -)))
319 -
320 -
321 -= 5.  How the gateway connects to Chirpstack v4 via gateway-bridge =
322 -
323 -
324 -(% style="color:blue" %)**Below list the support products and Requirements:**
325 -
326 -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]],[[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]]
327 -1. Firmware version since: [[Chirpstack-Bridge-V4>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V4--build-v5.4.1670655072-20221210-1452/]]
328 -
329 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
330 -
331 -Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]
332 -
333 -
334 -(% style="color:blue" %)**What do you need to prepare**
335 -
336 -A gateway that can access the internet normally
337 -
338 -
339 -== 5.1  Configure Packet Forwarder ==
340 -
341 -
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
343 -
344 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
345 -* Make sure the following settings are set:
346 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
347 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
348 -** **Server port for upstream:** //1700//
349 -** **Server port for downstream:** //1700//
350 -
351 - Click **Save & Apply**.
352 -
353 -[[image:image-20221222114220-2.png||height="748" width="931"]]
354 -
355 -
356 -== 5.2  Configuring gateway frequency ==
357 -
358 -
359 -(% style="color:red" %)**Note: Gateway frequencies must match**
360 -
361 -[[image:image-20221222134830-3.png||height="408" width="923"]]
362 -
363 -
364 -== 5.3  Modify the gateway-bridge configuration file ==
365 -
366 -
367 -Run the gateway command line command to modify the gateway-bridge configuration file:
368 -
369 -(% class="box infomessage" %)
370 -(((
371 -root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
372 -)))
373 -
374 -[[image:image-20221222113302-1.png]]
375 -
376 -
377 -[[image:image-20221222140203-4.png||height="875" width="806"]]
378 -
379 -[[image:image-20221230094246-1.png||height="768" width="783"]]
380 -
381 -(% class="wikigeneratedid" id="H" %)
382 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
383 -
384 -
385 -== 5.4  (Re)start and stop gateway-bridge ==
386 -
387 -
388 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
389 -
390 -(% class="box infomessage" %)
391 -(((
392 -**# start**
393 -
394 -/etc/init.d/chirpstack-gateway-bridge start
395 -
396 -**# stop**
397 -
398 -/etc/init.d/chirpstack-gateway-bridge stop
399 -
400 -**# restart**
401 -
402 -/etc/init.d/chirpstack-gateway-bridge restart
403 -)))
404 -
405 -
406 -== 5.5  Successful Connection ==
407 -
408 -
409 -[[image:image-20221222141754-5.png||height="488" width="1150"]]
410 -
411 -
412 -[[image:image-20221222141830-6.png||height="582" width="1153"]]
413 -
414 -
415 -= 6.  Downlink =
416 -
417 -== 6.1  Convert HEX to Base64 ==
418 -
419 -
420 -(% 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.**
421 -
422 -**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
423 -
424 -[[image:image-20221010193350-1.png]]
425 -
426 -
427 -
428 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
429 -
430 -[[image:image-20221010193621-2.png]]
431 -
432 -
433 -== 6.2  Chirpstack Downlink Note ==
434 -
435 -
436 -[[image:image-20220601102543-2.png]]
437 -
438 -**Convert the data to Base64**
439 -
440 -(% style="display:none" %) (%%)
441 -
442 -
443 -[[image:image-20220531173236-10.png||height="597" width="1215"]]
444 -
445 -**Check ChripStack downlink DataRate**
446 -
447 -
448 -
449 449  [[image:image-20220525101326-11.png]]
450 450  
451 -**Make sure the RX2DR is the same in the end node**
196 +Make sure the RX2DR is the same in the end node
452 452  
453 453  
454 -== 6.3  Loraserver Downlink Note ==
199 +== 4.2 Loraserver Downlink Note ==
455 455  
456 -
457 457  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
458 458  
459 459  (((
460 -**Below is examples:**
204 +Below is examples:
461 461  )))
462 462  
463 463  (% class="box" %)
... ... @@ -471,14 +471,13 @@
471 471  [[image:image-20220531173419-11.png]]
472 472  
473 473  (((
474 -**MQTT Connect to ChirpStack**
218 +MQTT Connect to ChirpStack
475 475  
476 -
477 477  
478 478  )))
479 479  
480 480  (((
481 -**After connect**
224 +After connect
482 482  )))
483 483  
484 484  (% class="box" %)
... ... @@ -498,14 +498,22 @@
498 498  
499 499  [[image:image-20220531173519-12.png]]
500 500  
501 -**MQTT Connect to ChirpStack**
244 +MQTT Connect to ChirpStack
502 502  
503 503  
504 -**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**
247 +(((
248 +(% 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/]]
249 +)))
505 505  
506 -[[image:image-20220531173658-14.png]]
251 +[[image:image-20220531173601-13.png]]
507 507  
253 +Choose to Use Hex for Encode
508 508  
255 +
256 +If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
257 +
258 +[[image:image-20220531173658-14.png]]
259 +
509 509  (((
510 510  Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码：
511 511  )))
... ... @@ -523,15 +523,15 @@
523 523   {
524 524   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
525 525   {
526 - ascv = sha1.charCodeAt( n ) - 55;
277 + ascv = sha1.charCodeAt(n) - 55;
527 527   }
528 528   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
529 529   {
530 - ascv = sha1.charCodeAt( n ) - 87;
281 + ascv = sha1.charCodeAt(n) - 87;
531 531   }
532 532   else
533 533   {
534 - ascv = sha1.charCodeAt( n ) - 48;
285 + ascv = sha1.charCodeAt(n) - 48;
535 535   }
536 536  \\ bit_arr = (bit_arr << 4) | ascv;
537 537   bit_num += 4;
... ... @@ -568,25 +568,23 @@
568 568  )))
569 569  
570 570  
571 -== 6.3  Add the decode function in Chirpstack for the payload ==
322 +== 4.3 Add the decode function in Chirpstack for the payload ==
572 572  
573 -
574 574  User enters the payload code according to the steps.
575 575  
576 -[[image:image-20220531173754-15.png||height="474" width="1334"]]
326 +[[image:image-20220531173754-15.png]]
577 577  
578 578  
579 579  [[image:image-20220531173856-16.png]]
580 580  
581 581  
582 -[[image:image-20220531174120-20.png]]
332 +[[image:image-20220526091602-5.png]]
583 583  
584 -[[image:image-20220531174046-19.png]]
334 +[[image:image-20220526091801-6.png]]
585 585  
586 586  
587 -= 7.  Multiply Uplink in ChirpStack =
337 += 5. Multiply Uplink in ChirpStack =
588 588  
589 -
590 590  (((
591 591  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
592 592  )))
... ... @@ -593,17 +593,12 @@
593 593  
594 594  (((
595 595  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]]
596 -
597 -
598 598  )))
599 599  
600 -[[image:image-20220526091912-7.png||height="241" width="1336"]]
347 +[[image:image-20220526091912-7.png]]
601 601  
602 -
603 603  (((
604 604  nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame.
605 -
606 -
607 607  )))
608 608  
609 609  [[image:image-20220525104359-21.png]]
... ... @@ -610,8 +610,6 @@
610 610  
611 611  (((
612 612  Above behaviour will cause the platform shows below two cases of error:
613 -
614 -
615 615  )))
616 616  
617 617  (((
... ... @@ -621,35 +621,29 @@
621 621  [[image:image-20220525104437-22.png]]
622 622  
623 623  
366 +Duplicate transmission in short time
624 624  
625 -**Duplicate transmission in short time**
368 +[[image:image-20220525104502-23.png]]
626 626  
627 -[[image:image-20220601102430-1.png||height="598" width="1319"]]
628 628  
371 +== 5.1 Solution ==
629 629  
630 -== 7.1  Solution ==
631 -
632 -
633 633  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]]
634 634  
635 -
636 636  (((
637 -(% 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.**
638 -
639 -
376 +~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.
640 640  )))
641 641  
642 642  [[image:image-20220525104532-24.png]]
643 643  
644 644  
645 -**installation path:**
382 +installation path:
646 646  
647 647  [[image:image-20220525104554-25.png]]
648 648  
649 649  
650 -
651 651  (((
652 -(% style="color:blue" %)**2.  Environment variable settings:**
388 +2. Environment variable settings:.
653 653  )))
654 654  
655 655  (((
... ... @@ -657,25 +657,23 @@
657 657  )))
658 658  
659 659  (((
660 -2) Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
396 +2)Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
661 661  )))
662 662  
663 663  [[image:image-20220524165433-33.png]]
664 664  
665 665  
666 -3) Modify the system variable Path and add C:\Go\bin\:
402 +3)Modify the system variable Path and add C:\Go\bin\:
667 667  
668 668  [[image:image-20220524165452-34.png]]
669 669  
670 -
671 671  User variable setting file generation directory: D:\go:
672 672  
673 673  [[image:image-20220524165517-35.png]]
674 674  
675 675  
411 +3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.
676 676  
677 -(% 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.**
678 -
679 679  The name of the plugin: Example ADR plugin:
680 680  
681 681  [[image:image-20220524165540-36.png]]
... ... @@ -685,9 +685,8 @@
685 685  [[image:image-20220524165557-37.png]]
686 686  
687 687  
422 +4. Compile the ADR configuration file and generate the exe file.
688 688  
689 -(% style="color:blue" %)**4.  Compile the ADR configuration file and generate the exe file.**
690 -
691 691  1) Create a folder named adr-setting
692 692  
693 693  2) Open the adr-setting folder
... ... @@ -711,9 +711,8 @@
711 711  [[image:image-20220524165623-38.png]]
712 712  
713 713  
447 +5. Add the plugin and run the plugin.
714 714  
715 -(% style="color:blue" %)**5.  Add the plugin and run the plugin.**
716 -
717 717  (((
718 718  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:
719 719  )))
... ... @@ -749,68 +749,14 @@
749 749  Finish.
750 750  
751 751  
752 -= 8.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
484 += 6. Trouble Shooting =
753 753  
486 +== 6.1 MIC Mismatch or MIC Failed ==
754 754  
755 -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.
756 -
757 -This example will be shown how to store/get all the data in two ways:
758 -
759 -**//1). Chirpstack ~-~-> Node-red//**
760 -
761 -
762 -[[image:image-20221012184501-1.png]]
763 -
764 -
765 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
766 -
767 -[[image:image-20221012174220-2.png]]
768 -
769 -
770 -[[image:image-20221012184655-3.png||height="395" width="1049"]]
771 -
772 -
773 -**Each message is continuously logged to a specified file**
774 -
775 -[[image:image-20221012174352-3.png]]
776 -
777 -
778 -**//2). MQTT  Sub//**
779 -
780 -If you don't want to store the information via node-red, you can get the output via the subscribe command.
781 -
782 -
783 -**If connecting from the same machine, you can use the following command to receive data:**
784 -
785 -(% class="box infomessage" %)
786 786  (((
787 -mosquitto_sub -h localhost -t "application/#" -v
788 -)))
789 -
790 -
791 -**Different host**
792 -
793 -(% class="box infomessage" %)
794 -(((
795 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
796 -)))
797 -
798 -[[image:image-20221012173639-1.png]]
799 -
800 -
801 -= 9.  Trouble Shooting =
802 -
803 -== 9.1  MIC Mismatch or MIC Failed ==
804 -
805 -
806 -(((
807 807  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
808 808  )))
809 809  
810 810  (((
811 811  Under normal circumstances, users need to change the APPKEY to solve this problem.
812 -
813 -
814 -
815 -
816 816  )))
image-20220531174015-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.4 KB
Content
image-20220531174046-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.2 KB
Content
image-20220531174120-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -41.4 KB
Content
image-20220601102430-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -139.4 KB
Content
image-20220601102543-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.5 KB
Content
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
image-20221012184631-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -32.4 KB
Content
image-20221012184655-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221222113302-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -76.3 KB
Content
image-20221222114220-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -64.3 KB
Content
image-20221222134830-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -54.5 KB
Content
image-20221222140203-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content
image-20221222141754-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -179.1 KB
Content
image-20221222141830-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -116.7 KB
Content
image-20221230094246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -84.9 KB
Content
image-20230415165254-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -67.2 KB
Content
image-20230415170404-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20230415170854-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -48.4 KB
Content

Applications

Navigation

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