Last modified by Mengting Qiu on 2025/07/03 18:55
From version 131.1
edited by Edwin Chen
on 2024/02/07 00:21
on 2024/02/07 00:21
Change comment:
Uploaded new attachment "image-20240207002129-2.png", version {1}
To version 139.1
edited by Edwin Chen
on 2024/02/08 10:36
on 2024/02/08 10:36
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
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 . ... ... @@ -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. User can lock the band to specify band for its operator to make this faster. 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. 48 48 49 49 (% style="color:#037691" %)**AT+QBAND? **(%%) ~/~/ Check what is the current used frequency band 50 50 ... ... @@ -621,3 +621,89 @@ 621 621 (% style="color:blue" %)**See result in TCP Server:** 622 622 623 623 [[image:image-20230807233631-2.png]] 628 + 629 + 630 += 4. FAQ = 631 + 632 +== 4.1 What is the usage of Multi Sampling and One Uplink? == 633 + 634 +The NB series has the feature for Multi Sampling and one uplink. See one of them 635 + 636 +[[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]] 637 + 638 +User can use this feature for below purpose: 639 + 640 +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. 641 +1. Give more sampling data points. 642 +1. Increase reliable in transmission. For example. If user set 643 +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) 644 +1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 645 +1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 646 +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. 647 + 648 += 5. Trouble Shooting: = 649 + 650 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == 651 + 652 +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. 653 + 654 +If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31) 655 + 656 +[[image:image-20240207002003-1.png]] 657 + 658 + 659 +If fail to attach network, it will shows signal 99. as below: 660 + 661 +[[image:image-20240207002129-2.png]] 662 + 663 + 664 +(% class="lead" %) 665 +When see this issue, below are the checklist: 666 + 667 +* 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. 668 +* 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]]. 669 +* 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]]. 670 +* Check if the device is attached to Carrier network but reject. (need to check with operator). 671 +* Check if the antenna is connected firmly. 672 + 673 +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. 674 + 675 + 676 +== 5.2 Issue: "NBIOT did not respond" == 677 + 678 +(% class="box errormessage" %) 679 +((( 680 +11:24:22.397 [44596]NBIOT did not respond. 681 +11:24:24.315 [46530]NBIOT did not respond. 682 +11:24:26.256 [48464]NBIOT did not respond. 683 +11:24:28.196 [50398]NBIOT did not respond. 684 +11:24:30.115 [52332]NBIOT did not respond. 685 +11:24:32.127 [54266]NBIOT did not respond. 686 +11:24:32.127 [54299]Restart the module... 687 +11:24:39.181 [61332]No response when shutting down 688 +))) 689 + 690 +This issue might due to initiate issue for NB-IoT module. In this case, please try: 691 + 692 +1) Open Enclosure 693 + 694 +2) Power off device by pull out the power on Jumper 695 + 696 +3) Power on device by connect back the power jumper. 697 + 698 +4) push reset button. 699 + 700 +[[image:image-20240208001740-1.png]] 701 + 702 + 703 +== 5.3 Issue: "Failed to readI MSI number" == 704 + 705 +(% class="box errormessage" %) 706 +((( 707 +[18170]Failed to read IMSI:1umber. 708 +[20109]Failed to read IMSI numoer. 709 +[22048]Failed to read IMSI number. 710 +[29842lRestart the module... 711 +))) 712 + 713 +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"]]
- 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