Changes for page Notes for ChirpStack

Last modified by Edwin Chen on 2025/01/30 09:53
<
From version < 108.13 >
edited by Xiaoling
on 2022/07/23 14:30
To version < 121.1 >
edited by Jean-Philippe Gagné
on 2022/11/29 23:31
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.JeanPhilippe
Content
... ... @@ -184,7 +184,7 @@
184 184  == 3.4  Start Station ==
185 185  
186 186  
187 -When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
187 +When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
188 188  
189 189  
190 190  == 3.5  Successful Connection ==
... ... @@ -212,9 +212,24 @@
212 212  
213 213  = 4.  Downlink =
214 214  
215 -== 4.1  Chirpstack Downlink Note ==
215 +== 4.1 Convert HEX to Base64 ==
216 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.**
217 217  
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 +
218 218  [[image:image-20220601102543-2.png]]
219 219  
220 220  Convert the data to Base64
... ... @@ -231,7 +231,7 @@
231 231  
232 232  
233 233  
234 -== 4.2  Loraserver Downlink Note ==
249 +== 4.3  Loraserver Downlink Note ==
235 235  
236 236  
237 237  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
... ... @@ -281,18 +281,8 @@
281 281  MQTT Connect to ChirpStack
282 282  
283 283  
284 -(((
285 -(% 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/]]**
286 -)))
299 +If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB
287 287  
288 -[[image:image-20220531173601-13.png]]
289 -
290 -Choose to Use Hex for Encode
291 -
292 -
293 -
294 -If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
295 -
296 296  [[image:image-20220531173658-14.png]]
297 297  
298 298  
... ... @@ -313,15 +313,15 @@
313 313   {
314 314   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
315 315   {
316 - ascv = sha1.charCodeAt(n) - 55;
321 + ascv = sha1.charCodeAt( n ) - 55;
317 317   }
318 318   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
319 319   {
320 - ascv = sha1.charCodeAt(n) - 87;
325 + ascv = sha1.charCodeAt( n ) - 87;
321 321   }
322 322   else
323 323   {
324 - ascv = sha1.charCodeAt(n) - 48;
329 + ascv = sha1.charCodeAt( n ) - 48;
325 325   }
326 326  \\ bit_arr = (bit_arr << 4) | ascv;
327 327   bit_num += 4;
... ... @@ -542,13 +542,60 @@
542 542  Finish.
543 543  
544 544  
550 += **6. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. ** =
545 545  
546 -= 6.  Trouble Shooting =
547 547  
548 -== 6.1  MIC Mismatch or MIC Failed ==
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.
549 549  
555 +This example will be shown how to store/get all the data in two ways:
550 550  
557 +**//1). Chirpstack ~-~-> Node-red//**
558 +
559 +
560 +[[image:image-20221012184501-1.png]]
561 +
562 +Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
563 +
564 +[[image:image-20221012174220-2.png]]
565 +
566 +
567 +[[image:image-20221012184655-3.png||height="395" width="1049"]]
568 +
569 +
570 +Each message is continuously logged to a specified file
571 +
572 +[[image:image-20221012174352-3.png]]
573 +
574 +
575 +**//2). MQTT  Sub//**
576 +
577 +If you don't want to store the information via node-red, you can get the output via the subscribe command.
578 +
579 +
580 +**If connecting from the same machine, you can use the following command to receive data:**
581 +
582 +(% class="box infomessage" %)
551 551  (((
584 +mosquitto_sub -h localhost -t "application/#" -v
585 +)))
586 +
587 +
588 +**Different host**
589 +
590 +(% class="box infomessage" %)
591 +(((
592 +mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
593 +)))
594 +
595 +[[image:image-20221012173639-1.png]]
596 +
597 +
598 += 7.  Trouble Shooting =
599 +
600 +== 7.1  MIC Mismatch or MIC Failed ==
601 +
602 +
603 +(((
552 552  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
553 553  )))
554 554  
image-20221010193350-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +42.7 KB
Content
image-20221010193621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +34.2 KB
Content
image-20221012173639-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +56.2 KB
Content
image-20221012174220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +14.8 KB
Content
image-20221012174352-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +93.0 KB
Content
image-20221012184501-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +91.3 KB
Content
image-20221012184631-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +32.4 KB
Content
image-20221012184655-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +45.4 KB
Content

Applications

Navigation

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