Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 134.1
edited by Edwin Chen
on 2024/02/08 00:17
Change comment: Uploaded new attachment "image-20240208001740-1.png", version {1}
To version 143.1
edited by Edwin Chen
on 2024/02/26 19:13
Change comment: There is no comment for this version

Summary

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 .
... ... @@ -90,8 +90,6 @@
90 90  
91 91  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
92 92  
93 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
94 -
95 95  [[image:image-20230802112413-2.png]]
96 96  
97 97  
... ... @@ -641,7 +641,6 @@
641 641  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
642 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 643  
644 -
645 645  = 5. Trouble Shooting: =
646 646  
647 647  == 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -669,4 +669,52 @@
669 669  
670 670  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.
671 671  
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 +
672 672  
image-20240208102804-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +52.0 KB
Content