Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 135.1
edited by Edwin Chen
on 2024/02/08 00:17
Change comment: There is no comment for this version
To version 145.2
edited by Xiaoling
on 2024/03/01 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -22,9 +22,13 @@
22 22  To attache NB-IoT sensors to NB-IoT Network, You need to:
23 23  
24 24  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
25 -1. Insert the SIM card to Sensor
25 +1. Power Off End Node ( See below for the power off/on position)
26 +1. Insert the SIM card to Sensor. ( See below for direction)
27 +1. Power On End Node
26 26  1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
27 27  
30 +[[image:image-20240208102804-1.png||height="286" width="696"]]
31 +
28 28  [[image:image-20230808205045-1.png||height="293" width="438"]]
29 29  
30 30  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -90,8 +90,6 @@
90 90  
91 91  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
92 92  
93 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
94 -
95 95  [[image:image-20230802112413-2.png]]
96 96  
97 97  
... ... @@ -308,6 +308,7 @@
308 308  
309 309  ==== 3.4.2.1 Scan QR Code to get the device info ====
310 310  
313 +
311 311  Users can use their phones or computers to scan QR codes to obtain device data information.
312 312  
313 313  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -317,34 +317,40 @@
317 317  
318 318  ==== 3.4.2.2 Claim Device to User Account ====
319 319  
323 +
320 320  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
321 321  
322 322  
323 -
324 324  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
325 325  
326 -**Step1:Add a device**
327 327  
330 +**Step1: Add a device**
331 +
328 328  [[image:image-20240129170024-1.png||height="330" width="900"]]
329 329  
330 -**Step2:Choose your device type,please select dragino NB-IOT device**
331 331  
335 +**Step2: Choose your device type,please select dragino NB-IOT device**
336 +
332 332  [[image:image-20240129170216-2.png||height="534" width="643"]]
333 333  
334 -**Step3:Choose to create a new device**
335 335  
340 +**Step3: Choose to create a new device**
341 +
336 336  [[image:image-20240129170539-3.png||height="459" width="646"]]
337 337  
338 -**Step4:Fill in the device ID of your NB device**
339 339  
345 +**Step4: Fill in the device ID of your NB device**
346 +
340 340  [[image:image-20240202111546-1.png||height="378" width="651"]]
341 341  
342 -**Step5:Please select your device plan according to your needs and complete the creation of the device**
343 343  
350 +**Step5: Please select your device plan according to your needs and complete the creation of the device**
351 +
344 344  [[image:image-20240129171236-6.png||height="450" width="648"]]
345 345  
346 -**Step6:Please add the decoder at the payload decoder of the device configuration.**
347 347  
355 +**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 +
348 348  **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]]
349 349  
350 350  [[image:image-20240129172056-7.png||height="457" width="816"]]
... ... @@ -351,12 +351,14 @@
351 351  
352 352  [[image:image-20240129173116-9.png||height="499" width="814"]]
353 353  
354 -**Step6:Add the output of the decoder as a field**
355 355  
364 +**Step7: Add the output of the decoder as a field**
365 +
356 356  [[image:image-20240129173541-10.png||height="592" width="968"]]
357 357  
358 -**Step7:Customize the dashboard and use fields as parameters of the dashboard**
359 359  
369 +**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 +
360 360  [[image:image-20240129174518-11.png||height="147" width="1042"]]
361 361  
362 362  [[image:image-20240129174657-12.png||height="538" width="916"]]
... ... @@ -366,6 +366,7 @@
366 366  
367 367  === 3.4.4 For device have not configured to connect to DataCake ===
368 368  
380 +
369 369  (% class="lead" %)
370 370  Use AT command for connecting to DataCake
371 371  
... ... @@ -627,6 +627,7 @@
627 627  
628 628  == 4.1 What is the usage of Multi Sampling and One Uplink? ==
629 629  
642 +
630 630  The NB series has the feature for Multi Sampling and one uplink. See one of them
631 631  
632 632  [[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]]
... ... @@ -641,10 +641,21 @@
641 641  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
642 642  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.
643 643  
657 +
658 +
659 +== 4.2 Why the uplink JSON format is not standard? ==
660 +
661 +
662 +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.
663 +
664 +[[image:image-20240229233154-1.png]]
665 +
666 +
644 644  = 5. Trouble Shooting: =
645 645  
646 646  == 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
647 647  
671 +
648 648  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.
649 649  
650 650  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -669,8 +669,9 @@
669 669  If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.
670 670  
671 671  
672 -== 5.2 NBIOT did not respond issue. ==
696 +== 5.2 Issue: "NBIOT did not respond" ==
673 673  
698 +
674 674  (% class="box errormessage" %)
675 675  (((
676 676  11:24:22.397 [44596]NBIOT did not respond.
... ... @@ -694,3 +694,28 @@
694 694  4) push reset button.
695 695  
696 696  [[image:image-20240208001740-1.png]]
722 +
723 +
724 +== 5.3 Issue: "Failed to readI MSI number" ==
725 +
726 +
727 +(% class="box errormessage" %)
728 +(((
729 +[18170]Failed to read IMSI:1umber.
730 +[20109]Failed to read IMSI numoer.
731 +[22048]Failed to read IMSI number.
732 +[29842lRestart the module...
733 +)))
734 +
735 +Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
736 +
737 +
738 +== 5.4 Why sometime the AT Command is slow in reponse? ==
739 +
740 +
741 +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.
742 +
743 +[[image:image-20240226111928-1.png]]
744 +
745 +
746 +
image-20240208102804-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +39.5 KB
Content