Last modified by Mengting Qiu on 2025/03/08 11:33
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 4 removed)
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 . ... ... @@ -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 ... ... @@ -625,28 +625,10 @@ 625 625 [[image:image-20230807233631-2.png]] 626 626 627 627 628 -= 4. FAQ=626 += 4. Trouble Shooting: = 629 629 630 -== 4.1 WhatisheusageofMulti SamplingandOneUplink?==628 +== 4.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == 631 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 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 651 652 652 If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31) ... ... @@ -670,52 +670,4 @@ 670 670 671 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 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 721
- 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