Last modified by Mengting Qiu on 2025/03/08 11:33
Change comment:
Uploaded new attachment "image-20240207002129-2.png", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -44,7 +44,7 @@ 44 44 == 2.2 Speed Up Network Attach time == 45 45 46 46 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.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. 48 48 49 49 (% style="color:#037691" %)**AT+QBAND? **(%%) ~/~/ Check what is the current used frequency band 50 50 ... ... @@ -621,76 +621,3 @@ 621 621 (% style="color:blue" %)**See result in TCP Server:** 622 622 623 623 [[image:image-20230807233631-2.png]] 624 - 625 - 626 -= 4. FAQ = 627 - 628 -== 4.1 What is the usage of Multi Sampling and One Uplink? == 629 - 630 -The NB series has the feature for Multi Sampling and one uplink. See one of them 631 - 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]] 633 - 634 -User can use this feature for below purpose: 635 - 636 -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. 637 -1. Give more sampling data points. 638 -1. Increase reliable in transmission. For example. If user set 639 -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) 640 -1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 641 -1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 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 - 644 -= 5. Trouble Shooting: = 645 - 646 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == 647 - 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 - 650 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31) 651 - 652 -[[image:image-20240207002003-1.png]] 653 - 654 - 655 -If fail to attach network, it will shows signal 99. as below: 656 - 657 -[[image:image-20240207002129-2.png]] 658 - 659 - 660 -(% class="lead" %) 661 -When see this issue, below are the checklist: 662 - 663 -* 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. 664 -* 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]]. 665 -* 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]]. 666 -* Check if the device is attached to Carrier network but reject. (need to check with operator). 667 -* Check if the antenna is connected firmly. 668 - 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 - 671 - 672 -== 5.2 NBIOT did not respond issue. == 673 - 674 -(% class="box errormessage" %) 675 -((( 676 -11:24:22.397 [44596]NBIOT did not respond. 677 -11:24:24.315 [46530]NBIOT did not respond. 678 -11:24:26.256 [48464]NBIOT did not respond. 679 -11:24:28.196 [50398]NBIOT did not respond. 680 -11:24:30.115 [52332]NBIOT did not respond. 681 -11:24:32.127 [54266]NBIOT did not respond. 682 -11:24:32.127 [54299]Restart the module... 683 -11:24:39.181 [61332]No response when shutting down 684 -))) 685 - 686 -This issue might due to initiate issue for NB-IoT module. In this case, please try: 687 - 688 -1) Open Enclosure 689 - 690 -2) Power off device by pull out the power on Jumper 691 - 692 -3) Power on device by connect back the power jumper. 693 - 694 -4) push reset button. 695 - 696 -[[image:image-20240208001740-1.png]]
- 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