Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 7 removed)
  • image-20221010193621-2.png
  • image-20221012173639-1.png
  • image-20221012174220-2.png
  • image-20221012174352-3.png
  • image-20221012184501-1.png
  • image-20221012184631-2.png
  • image-20221012184655-3.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.JeanPhilippe
	1	+XWiki.Edwin

Content

...	...	@@ -212,24 +212,9 @@
212	212
213	213	= 4.  Downlink =
214	214
215		-== 4.1 Convert HEX to Base64 ==
	215	+== 4.1  Chirpstack Downlink Note ==
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.**
218	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
...	...	@@ -246,7 +246,7 @@
246	246
247	247
248	248
249		-== 4.3  Loraserver Downlink Note ==
	234	+== 4.2  Loraserver Downlink Note ==
250	250
251	251
252	252	User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
...	...	@@ -296,8 +296,18 @@
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
	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	+)))
300	300
	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	+
301	301	[[image:image-20220531173658-14.png]]
302	302
303	303
...	...	@@ -318,15 +318,15 @@
318	318	{
319	319	if(sha1[n] >= 'A' && sha1[n] <= 'Z')
320	320	{
321		- ascv = sha1.charCodeAt( n ) - 55;
	316	+ ascv = sha1.charCodeAt(n) - 55;
322	322	}
323	323	else if(sha1[n] >= 'a' && sha1[n] <= 'z')
324	324	{
325		- ascv = sha1.charCodeAt( n ) - 87;
	320	+ ascv = sha1.charCodeAt(n) - 87;
326	326	}
327	327	else
328	328	{
329		- ascv = sha1.charCodeAt( n ) - 48;
	324	+ ascv = sha1.charCodeAt(n) - 48;
330	330	}
331	331	\\ bit_arr = (bit_arr << 4) | ascv;
332	332	bit_num += 4;
...	...	@@ -547,60 +547,13 @@
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. ** =
551	551
	546	+= 6.  Trouble Shooting =
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.
	548	+== 6.1  MIC Mismatch or MIC Failed ==
554	554
555		-This example will be shown how to store/get all the data in two ways:
556	556
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" %)
583	583	(((
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		-(((
604	604	When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
605	605	)))
606	606

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