Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

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

Content

...	...	@@ -310,6 +310,7 @@
310	310
311	311	==== 3.4.2.1 Scan QR Code to get the device info ====
312	312
	313	+
313	313	Users can use their phones or computers to scan QR codes to obtain device data information.
314	314
315	315	[[image:image-20230808170051-8.png||height="255" width="259"]]
...	...	@@ -319,34 +319,40 @@
319	319
320	320	==== 3.4.2.2 Claim Device to User Account ====
321	321
	323	+
322	322	By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
323	323
324	324
325		-
326	326	=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
327	327
328		-**Step1:Add a device**
329	329
	330	+**Step1: Add a device**
	331	+
330	330	[[image:image-20240129170024-1.png||height="330" width="900"]]
331	331
332		-**Step2:Choose your device type,please select dragino NB-IOT device**
333	333
	335	+**Step2: Choose your device type,please select dragino NB-IOT device**
	336	+
334	334	[[image:image-20240129170216-2.png||height="534" width="643"]]
335	335
336		-**Step3:Choose to create a new device**
337	337
	340	+**Step3: Choose to create a new device**
	341	+
338	338	[[image:image-20240129170539-3.png||height="459" width="646"]]
339	339
340		-**Step4:Fill in the device ID of your NB device**
341	341
	345	+**Step4: Fill in the device ID of your NB device**
	346	+
342	342	[[image:image-20240202111546-1.png||height="378" width="651"]]
343	343
344		-**Step5:Please select your device plan according to your needs and complete the creation of the device**
345	345
	350	+**Step5: Please select your device plan according to your needs and complete the creation of the device**
	351	+
346	346	[[image:image-20240129171236-6.png||height="450" width="648"]]
347	347
348		-**Step6:Please add the decoder at the payload decoder of the device configuration.**
349	349
	355	+**Step6: Please add the decoder at the payload decoder of the device configuration.**
	356	+
350	350	**Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
351	351
352	352	[[image:image-20240129172056-7.png||height="457" width="816"]]
...	...	@@ -353,12 +353,14 @@
353	353
354	354	[[image:image-20240129173116-9.png||height="499" width="814"]]
355	355
356		-**Step6:Add the output of the decoder as a field**
357	357
	364	+**Step7: Add the output of the decoder as a field**
	365	+
358	358	[[image:image-20240129173541-10.png||height="592" width="968"]]
359	359
360		-**Step7:Customize the dashboard and use fields as parameters of the dashboard**
361	361
	369	+**Step8: Customize the dashboard and use fields as parameters of the dashboard**
	370	+
362	362	[[image:image-20240129174518-11.png||height="147" width="1042"]]
363	363
364	364	[[image:image-20240129174657-12.png||height="538" width="916"]]
...	...	@@ -368,6 +368,7 @@
368	368
369	369	=== 3.4.4 For device have not configured to connect to DataCake ===
370	370
	380	+
371	371	(% class="lead" %)
372	372	Use AT command for connecting to DataCake
373	373
...	...	@@ -629,6 +629,7 @@
629	629
630	630	== 4.1 What is the usage of Multi Sampling and One Uplink? ==
631	631
	642	+
632	632	The NB series has the feature for Multi Sampling and one uplink. See one of them
633	633
634	634	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
...	...	@@ -644,18 +644,20 @@
644	644	1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn;t lost 6 continue data. There will not data lost.
645	645
646	646
	658	+
647	647	== 4.2 Why the uplink JSON format is not standard? ==
648	648
	661	+
649	649	The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
650	650
651	651	[[image:image-20240229233154-1.png]]
652	652
653	653
654		-
655	655	= 5. Trouble Shooting: =
656	656
657	657	== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
658	658
	671	+
659	659	There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.
660	660
661	661	If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
...	...	@@ -682,6 +682,7 @@
682	682
683	683	== 5.2 Issue: "NBIOT did not respond" ==
684	684
	698	+
685	685	(% class="box errormessage" %)
686	686	(((
687	687	11:24:22.397 [44596]NBIOT did not respond.
...	...	@@ -709,6 +709,7 @@
709	709
710	710	== 5.3 Issue: "Failed to readI MSI number" ==
711	711
	726	+
712	712	(% class="box errormessage" %)
713	713	(((
714	714	[18170]Failed to read IMSI:1umber.
...	...	@@ -722,6 +722,7 @@
722	722
723	723	== 5.4 Why sometime the AT Command is slow in reponse? ==
724	724
	740	+
725	725	When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
726	726
727	727	[[image:image-20240226111928-1.png]]