Last modified by Mengting Qiu on 2025/07/03 18:55

From version 135.1
edited by Edwin Chen
on 2024/02/08 00:17
Change comment: There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2024/02/29 23:34
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,6 +641,15 @@
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  
646 +
647 +== 4.2 Why the uplink JSON format is not standard? ==
648 +
649 +The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
650 +
651 +[[image:image-20240229233154-1.png]]
652 +
653 +
654 +
644 644  = 5. Trouble Shooting: =
645 645  
646 646  == 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -669,7 +669,7 @@
669 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 670  
671 671  
672 -== 5.2 NBIOT did not respond issue. ==
683 +== 5.2 Issue: "NBIOT did not respond" ==
673 673  
674 674  (% class="box errormessage" %)
675 675  (((
... ... @@ -694,3 +694,26 @@
694 694  4) push reset button.
695 695  
696 696  [[image:image-20240208001740-1.png]]
708 +
709 +
710 +== 5.3 Issue: "Failed to readI MSI number" ==
711 +
712 +(% class="box errormessage" %)
713 +(((
714 +[18170]Failed to read IMSI:1umber.
715 +[20109]Failed to read IMSI numoer.
716 +[22048]Failed to read IMSI number.
717 +[29842lRestart the module...
718 +)))
719 +
720 +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"]].
721 +
722 +
723 +== 5.4 Why sometime the AT Command is slow in reponse? ==
724 +
725 +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.
726 +
727 +[[image:image-20240226111928-1.png]]
728 +
729 +
730 +
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
image-20240229233154-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +39.5 KB
Content