Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 133.1
edited by Edwin Chen
on 2024/02/07 23:40
Change comment: There is no comment for this version
To version 146.1
edited by Edwin Chen
on 2024/03/03 16:50
Change comment: There is no comment for this version

Summary

Details

Page properties
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 .
... ... @@ -47,10 +47,9 @@
47 47  BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show Signal Strenght:99. User can lock the band to specify band for its operator to make this faster.
48 48  
49 49  (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
50 -
51 51  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
52 -
53 53  (% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
56 +(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=11,8,20,28,2,4,12,13,66,85,5,4**
54 54  
55 55  (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
56 56  (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
... ... @@ -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  
312 +
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  
322 +
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  
329 +**Step1: Add a device**
330 +
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  
334 +**Step2: Choose your device type,please select dragino NB-IOT device**
335 +
332 332  [[image:image-20240129170216-2.png||height="534" width="643"]]
333 333  
334 -**Step3:Choose to create a new device**
335 335  
339 +**Step3: Choose to create a new device**
340 +
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  
344 +**Step4: Fill in the device ID of your NB device**
345 +
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  
349 +**Step5: Please select your device plan according to your needs and complete the creation of the device**
350 +
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  
354 +**Step6: Please add the decoder at the payload decoder of the device configuration.**
355 +
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  
363 +**Step7: Add the output of the decoder as a field**
364 +
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  
368 +**Step8: Customize the dashboard and use fields as parameters of the dashboard**
369 +
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  
379 +
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  
641 +
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]]
... ... @@ -642,10 +642,19 @@
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  
644 644  
657 +== 4.2 Why the uplink JSON format is not standard? ==
658 +
659 +
660 +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.
661 +
662 +[[image:image-20240229233154-1.png]]
663 +
664 +
645 645  = 5. Trouble Shooting: =
646 646  
647 647  == 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
648 648  
669 +
649 649  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.
650 650  
651 651  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -669,4 +669,55 @@
669 669  
670 670  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.
671 671  
693 +
694 +== 5.2 Issue: "NBIOT did not respond" ==
695 +
696 +
697 +(% class="box errormessage" %)
698 +(((
699 +11:24:22.397 [44596]NBIOT did not respond.
700 +11:24:24.315 [46530]NBIOT did not respond.
701 +11:24:26.256 [48464]NBIOT did not respond.
702 +11:24:28.196 [50398]NBIOT did not respond.
703 +11:24:30.115 [52332]NBIOT did not respond.
704 +11:24:32.127 [54266]NBIOT did not respond.
705 +11:24:32.127 [54299]Restart the module...
706 +11:24:39.181 [61332]No response when shutting down
707 +)))
708 +
709 +This issue might due to initiate issue for NB-IoT module. In this case, please try:
710 +
711 +1) Open Enclosure
712 +
713 +2) Power off device by pull out the power on Jumper
714 +
715 +3) Power on device by connect back the power jumper.
716 +
717 +4) push reset button.
718 +
719 +[[image:image-20240208001740-1.png]]
720 +
721 +
722 +== 5.3 Issue: "Failed to readI MSI number" ==
723 +
724 +
725 +(% class="box errormessage" %)
726 +(((
727 +[18170]Failed to read IMSI:1umber.
728 +[20109]Failed to read IMSI numoer.
729 +[22048]Failed to read IMSI number.
730 +[29842lRestart the module...
731 +)))
732 +
733 +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"]].
734 +
735 +
736 +== 5.4 Why sometime the AT Command is slow in reponse? ==
737 +
738 +
739 +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.
740 +
741 +[[image:image-20240226111928-1.png]]
742 +
743 +
672 672  
image-20240208001740-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +487.1 KB
Content
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