Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 145.2 >
edited by Xiaoling
on 2024/03/01 10:15
To version < 113.1 >
edited by Bei Jinggeng
on 2024/01/29 17:10
>
Change comment: Uploaded new attachment "image-20240129171029-4.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -22,13 +22,9 @@
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. 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
25 +1. Insert the SIM card to Sensor
28 28  1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
29 29  
30 -[[image:image-20240208102804-1.png||height="286" width="696"]]
31 -
32 32  [[image:image-20230808205045-1.png||height="293" width="438"]]
33 33  
34 34  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -48,18 +48,14 @@
48 48  == 2.2 Speed Up Network Attach time ==
49 49  
50 50  
51 -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.
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. User can lock the band to specify band for its operator to make this faster.
52 52  
53 53  (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 54  
55 55  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 56  
57 -(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
53 +(% style="color:#037691" %)**AT+QBAND=2,8,20 **(%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
58 58  
59 -(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
60 -(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
61 -(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
62 -(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
63 63  
64 64  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
65 65  
... ... @@ -94,6 +94,8 @@
94 94  
95 95  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
96 96  
89 +* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
90 +
97 97  [[image:image-20230802112413-2.png]]
98 98  
99 99  
... ... @@ -308,9 +308,8 @@
308 308  
309 309  === 3.4.2 For Device already registered in DataCake before shipped ===
310 310  
311 -==== 3.4.2.1 Scan QR Code to get the device info ====
305 +**Scan QR Code to get the device info.**
312 312  
313 -
314 314  Users can use their phones or computers to scan QR codes to obtain device data information.
315 315  
316 316  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -318,66 +318,11 @@
318 318  [[image:image-20230808170548-9.png]]
319 319  
320 320  
321 -==== 3.4.2.2 Claim Device to User Account ====
322 -
323 -
324 -By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 -
326 -
327 327  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
328 328  
329 329  
330 -**Step1: Add a device**
331 -
332 -[[image:image-20240129170024-1.png||height="330" width="900"]]
333 -
334 -
335 -**Step2: Choose your device type,please select dragino NB-IOT device**
336 -
337 -[[image:image-20240129170216-2.png||height="534" width="643"]]
338 -
339 -
340 -**Step3: Choose to create a new device**
341 -
342 -[[image:image-20240129170539-3.png||height="459" width="646"]]
343 -
344 -
345 -**Step4: Fill in the device ID of your NB device**
346 -
347 -[[image:image-20240202111546-1.png||height="378" width="651"]]
348 -
349 -
350 -**Step5: Please select your device plan according to your needs and complete the creation of the device**
351 -
352 -[[image:image-20240129171236-6.png||height="450" width="648"]]
353 -
354 -
355 -**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 -
357 -**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]]
358 -
359 -[[image:image-20240129172056-7.png||height="457" width="816"]]
360 -
361 -[[image:image-20240129173116-9.png||height="499" width="814"]]
362 -
363 -
364 -**Step7: Add the output of the decoder as a field**
365 -
366 -[[image:image-20240129173541-10.png||height="592" width="968"]]
367 -
368 -
369 -**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 -
371 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
372 -
373 -[[image:image-20240129174657-12.png||height="538" width="916"]]
374 -
375 -[[image:image-20240129174840-13.png||height="536" width="750"]]
376 -
377 -
378 378  === 3.4.4 For device have not configured to connect to DataCake ===
379 379  
380 -
381 381  (% class="lead" %)
382 382  Use AT command for connecting to DataCake
383 383  
... ... @@ -633,114 +633,3 @@
633 633  (% style="color:blue" %)**See result in TCP Server:**
634 634  
635 635  [[image:image-20230807233631-2.png]]
636 -
637 -
638 -= 4. FAQ =
639 -
640 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
641 -
642 -
643 -The NB series has the feature for Multi Sampling and one uplink. See one of them
644 -
645 -[[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]]
646 -
647 -User can use this feature for below purpose:
648 -
649 -1. **Reduce power consumption**. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.
650 -1. Give more sampling data points.
651 -1. Increase reliable in transmission. For example. If user set
652 -1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
653 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
654 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
655 -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.
656 -
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 -
667 -= 5. Trouble Shooting: =
668 -
669 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
670 -
671 -
672 -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.
673 -
674 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
675 -
676 -[[image:image-20240207002003-1.png]]
677 -
678 -
679 -If fail to attach network, it will shows signal 99. as below:
680 -
681 -[[image:image-20240207002129-2.png]]
682 -
683 -
684 -(% class="lead" %)
685 -When see this issue, below are the checklist:
686 -
687 -* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
688 -* Do you configure the correct APN? [[Check here for APN settings>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
689 -* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
690 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
691 -* Check if the antenna is connected firmly.
692 -
693 -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.
694 -
695 -
696 -== 5.2 Issue: "NBIOT did not respond" ==
697 -
698 -
699 -(% class="box errormessage" %)
700 -(((
701 -11:24:22.397 [44596]NBIOT did not respond.
702 -11:24:24.315 [46530]NBIOT did not respond.
703 -11:24:26.256 [48464]NBIOT did not respond.
704 -11:24:28.196 [50398]NBIOT did not respond.
705 -11:24:30.115 [52332]NBIOT did not respond.
706 -11:24:32.127 [54266]NBIOT did not respond.
707 -11:24:32.127 [54299]Restart the module...
708 -11:24:39.181 [61332]No response when shutting down
709 -)))
710 -
711 -This issue might due to initiate issue for NB-IoT module. In this case, please try:
712 -
713 -1) Open Enclosure
714 -
715 -2) Power off device by pull out the power on Jumper
716 -
717 -3) Power on device by connect back the power jumper.
718 -
719 -4) push reset button.
720 -
721 -[[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-20240129171113-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -39.5 KB
Content

Applications

Navigation

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