Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 143.1 >
edited by Edwin Chen
on 2024/02/26 19:13
To version < 129.1 >
edited by Edwin Chen
on 2024/02/04 00:08
>
Change comment: There is no comment for this version

Summary

Details

Page properties
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,7 +48,7 @@
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  
... ... @@ -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  
93 +* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
94 +
97 97  [[image:image-20230802112413-2.png]]
98 98  
99 99  
... ... @@ -623,99 +623,3 @@
623 623  (% style="color:blue" %)**See result in TCP Server:**
624 624  
625 625  [[image:image-20230807233631-2.png]]
626 -
627 -
628 -= 4. FAQ =
629 -
630 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
631 -
632 -The NB series has the feature for Multi Sampling and one uplink. See one of them
633 -
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]]
635 -
636 -User can use this feature for below purpose:
637 -
638 -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.
639 -1. Give more sampling data points.
640 -1. Increase reliable in transmission. For example. If user set
641 -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)
642 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
643 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
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 -
646 -= 5. Trouble Shooting: =
647 -
648 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
649 -
650 -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.
651 -
652 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
653 -
654 -[[image:image-20240207002003-1.png]]
655 -
656 -
657 -If fail to attach network, it will shows signal 99. as below:
658 -
659 -[[image:image-20240207002129-2.png]]
660 -
661 -
662 -(% class="lead" %)
663 -When see this issue, below are the checklist:
664 -
665 -* 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.
666 -* 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]].
667 -* 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]].
668 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
669 -* Check if the antenna is connected firmly.
670 -
671 -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.
672 -
673 -
674 -== 5.2 Issue: "NBIOT did not respond" ==
675 -
676 -(% class="box errormessage" %)
677 -(((
678 -11:24:22.397 [44596]NBIOT did not respond.
679 -11:24:24.315 [46530]NBIOT did not respond.
680 -11:24:26.256 [48464]NBIOT did not respond.
681 -11:24:28.196 [50398]NBIOT did not respond.
682 -11:24:30.115 [52332]NBIOT did not respond.
683 -11:24:32.127 [54266]NBIOT did not respond.
684 -11:24:32.127 [54299]Restart the module...
685 -11:24:39.181 [61332]No response when shutting down
686 -)))
687 -
688 -This issue might due to initiate issue for NB-IoT module. In this case, please try:
689 -
690 -1) Open Enclosure
691 -
692 -2) Power off device by pull out the power on Jumper
693 -
694 -3) Power on device by connect back the power jumper.
695 -
696 -4) push reset button.
697 -
698 -[[image:image-20240208001740-1.png]]
699 -
700 -
701 -== 5.3 Issue: "Failed to readI MSI number" ==
702 -
703 -(% class="box errormessage" %)
704 -(((
705 -[18170]Failed to read IMSI:1umber.
706 -[20109]Failed to read IMSI numoer.
707 -[22048]Failed to read IMSI number.
708 -[29842lRestart the module...
709 -)))
710 -
711 -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"]].
712 -
713 -
714 -== 5.4 Why sometime the AT Command is slow in reponse? ==
715 -
716 -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.
717 -
718 -[[image:image-20240226111928-1.png]]
719 -
720 -
721 -
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

Applications

Navigation

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