Hide last authors
Xiaoling 83.3 1 (% class="wikigeneratedid" id="HTableofContents:" %)
2 **Table of Contents:**
Xiaoling 53.3 3
4 {{toc/}}
5
6
Xiaoling 100.2 7
8
9
10
Edwin Chen 1.1 11 = 1. The use of this guideline =
12
Xiaoling 1.2 13
Edwin Chen 1.1 14 This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module **[[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
15
16
Edwin Chen 55.1 17 = 2. Attach Network =
Edwin Chen 1.1 18
Edwin Chen 103.1 19 == 2.1 General Configure to attach network ==
Edwin Chen 1.1 20
Xiaoling 104.4 21
Edwin Chen 54.1 22 To attache NB-IoT sensors to NB-IoT Network, You need to:
23
24 1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
Edwin Chen 137.1 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
Edwin Chen 99.1 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>)
Edwin Chen 54.1 29
Edwin Chen 137.1 30 [[image:image-20240208102804-1.png||height="286" width="696"]]
31
Edwin Chen 83.1 32 [[image:image-20230808205045-1.png||height="293" width="438"]]
Edwin Chen 60.1 33
Edwin Chen 54.1 34 After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
35
Xiaoling 1.3 36 The -NB and -NS models support (% style="color:blue" %)**LTE Cat NB2**(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Make sure you use a the NB-IoT SIM card.
Edwin Chen 1.1 37
Edwin Chen 54.1 38 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
Edwin Chen 99.1 39 |(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+APN=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
Xiaoling 56.2 40 |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
Edwin Chen 54.1 41 **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
Edwin Chen 1.1 42
Edwin Chen 54.1 43 Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
44 )))|(% style="width:135px" %)
Edwin Chen 57.1 45 |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
David Huang 66.1 46 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
Xiaoling 53.27 47
Edwin Chen 103.1 48 == 2.2 Speed Up Network Attach time ==
Xiaoling 99.3 49
Xiaoling 104.2 50
Edwin Chen 132.1 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.
Xiaoling 102.2 52
Edwin Chen 107.1 53 (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
Edwin Chen 103.1 54
Edwin Chen 107.1 55 (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
Edwin Chen 103.1 56
Edwin Chen 129.1 57 (% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
Edwin Chen 104.1 58
Edwin Chen 129.1 59 (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
60 (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
61 (% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
62 (% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
Xiaoling 104.4 63
Edwin Chen 107.1 64 After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
65
66
Edwin Chen 105.1 67 See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
68
69
Edwin Chen 1.1 70 = 3. Configure to connect to different servers =
71
Xiaoling 53.3 72 == 3.1 General UDP Connection ==
Xiaoling 53.2 73
74
75 The NB-IoT Sensor can send packet to server use UDP protocol.
76
77
Xiaoling 53.3 78 === 3.1.1 Simulate UDP Connection by PC tool ===
79
80
Xiaoling 53.2 81 We can use PC tool to simulate UDP connection to make sure server works ok.
82
Xiaoling 105.2 83 [[image:image-20230802112413-1.png||height="468" width="1024"]]
Xiaoling 53.2 84
85
Xiaoling 53.3 86 === 3.1.2 Configure NB-IoT Sensor ===
Xiaoling 53.2 87
Xiaoling 53.3 88 ==== 3.1.2.1 AT Commands ====
Xiaoling 53.2 89
Xiaoling 53.3 90
Xiaoling 53.4 91 (% style="color:blue" %)**AT Commands:**
Xiaoling 53.3 92
Xiaoling 53.5 93 * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
Xiaoling 53.8 94
Xiaoling 53.5 95 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
Xiaoling 53.8 96
Xiaoling 53.2 97 [[image:image-20230802112413-2.png]]
98
99
Xiaoling 53.3 100 ==== 3.1.2.2 Uplink Example ====
Xiaoling 53.2 101
Xiaoling 53.3 102
Xiaoling 53.2 103 [[image:image-20230802112413-3.png]]
104
105
Xiaoling 53.7 106 == 3.2 General MQTT Connection ==
Xiaoling 53.2 107
Xiaoling 53.6 108
Xiaoling 53.2 109 The NB-IoT Sensor can send packet to server use MQTT protocol.
110
Xiaoling 53.6 111 Below are the commands.
Xiaoling 53.2 112
Xiaoling 53.8 113 (% style="color:blue" %)**AT Commands:**
Xiaoling 53.2 114
Xiaoling 53.9 115 * (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
Xiaoling 53.2 116
Xiaoling 53.9 117 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
Xiaoling 53.8 118
Xiaoling 53.9 119 * (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
Xiaoling 53.8 120
Xiaoling 53.9 121 * (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
Xiaoling 53.8 122
Xiaoling 53.9 123 * (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
Xiaoling 53.8 124
125 * (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
126
127 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/  Set the subscription topic of MQTT
128
Xiaoling 53.2 129 [[image:image-20230802112413-4.png]]
130
Edwin Chen 102.1 131 [[image:image-20230802112413-5.png||height="530" width="987"]]
Xiaoling 53.2 132
Xiaoling 53.9 133 (% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink  period to a suitable interval.**
Xiaoling 53.2 134
135
Xiaoling 53.7 136 == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
Xiaoling 53.2 137
Xiaoling 53.9 138 === 3.3.1 Get MQTT Credentials ===
Xiaoling 53.2 139
Xiaoling 53.9 140
Xiaoling 53.2 141 [[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.
142
Edwin Chen 102.1 143 [[image:image-20230802112413-6.png||height="336" width="925"]]
Xiaoling 53.2 144
145 [[image:image-20230802112413-7.png]]
146
147
Xiaoling 53.27 148 === 3.3.2 Simulate with MQTT.fx ===
Xiaoling 53.2 149
Xiaoling 53.27 150 ==== 3.3.2.1 Establish MQTT Connection ====
Xiaoling 53.2 151
Xiaoling 53.9 152
Xiaoling 53.2 153 After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
154
155 [[image:image-20230802112413-8.png]]
156
Xiaoling 53.9 157 * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
Xiaoling 53.2 158
Xiaoling 53.9 159 * (% style="color:#037691" %)**Broker Port:**(%%) 1883
Xiaoling 53.10 160
Xiaoling 53.9 161 * (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
Xiaoling 53.10 162
Xiaoling 53.9 163 * (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
Xiaoling 53.10 164
Xiaoling 53.9 165 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
Xiaoling 53.2 166
Xiaoling 53.28 167 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
168
169
Xiaoling 53.2 170 [[image:image-20230802112413-9.png]]
171
172 [[image:image-20230802112413-10.png]]
173
Xiaoling 53.43 174
Xiaoling 53.10 175 (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
Xiaoling 53.2 176
Xiaoling 53.10 177 * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
Xiaoling 53.2 178
Xiaoling 53.10 179 * (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
180
Xiaoling 53.2 181 Where 63 and 67 are the value to be published to field1 & field2.
182
183
Xiaoling 53.10 184 (% style="color:blue" %)**Result: **
Xiaoling 53.2 185
Edwin Chen 102.1 186 [[image:image-20230802112413-11.png||height="539" width="901"]]
Xiaoling 53.2 187
188
Xiaoling 53.28 189 === 3.3.3 Configure NB-IoT Sensor for connection ===
Xiaoling 53.2 190
Xiaoling 53.28 191 ==== 3.3.3.1 AT Commands: ====
Xiaoling 53.2 192
Xiaoling 53.10 193
Xiaoling 53.2 194 In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
195
Xiaoling 99.3 196 * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
Xiaoling 53.9 197
Xiaoling 53.26 198 * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
Xiaoling 53.9 199
Xiaoling 53.26 200 * (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
Xiaoling 53.9 201
Xiaoling 53.26 202 * (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
Xiaoling 53.9 203
Xiaoling 53.26 204 * (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
Xiaoling 53.9 205
Xiaoling 53.26 206 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
Xiaoling 53.2 207
Xiaoling 53.28 208 ==== 3.3.3.2 Uplink Examples ====
Xiaoling 53.10 209
Xiaoling 104.4 210
Edwin Chen 102.1 211 [[image:image-20230816201942-1.png]]
Xiaoling 53.10 212
Xiaoling 53.2 213 For SE01-NB
214
215 For DDS20-NB
216
217 For DDS45-NB
218
219 For DDS75-NB
220
221 For NMDS120-NB
222
223 For SPH01-NB
224
225 For NLM01-NB
226
227 For NMDS200-NB
228
229 For CPN01-NB
230
231 For DS03A-NB
232
233 For SN50V3-NB
234
235
Xiaoling 53.28 236 ==== 3.3.3.3 Map fields to sensor value ====
Xiaoling 53.2 237
Xiaoling 53.10 238
Xiaoling 53.2 239 When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
240
241
Edwin Chen 102.1 242 [[image:image-20230802112413-12.png||height="504" width="1011"]]
Xiaoling 53.2 243
Edwin Chen 102.1 244 [[image:image-20230802112413-13.png||height="331" width="978"]]
Xiaoling 53.2 245
246
247 Below is the NB-IoT Product Table show the mapping.
248
Xiaoling 83.4 249 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
250 |(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:154px" %)Field4|(% style="background-color:#4f81bd; color:white; width:153px" %)Field5|(% style="background-color:#4f81bd; color:white; width:151px" %)Field6|(% style="background-color:#4f81bd; color:white; width:160px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:67px" %)Field9|(% style="background-color:#4f81bd; color:white; width:69px" %)Field10
251 |(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
252 |(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:154px" %)dielectric_constant|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
253 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
254 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
255 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
256 |(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
257 |(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
258 |(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
259 |(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
260 |(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:154px" %)calc flag|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
261 |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:67px" %)Battery|(% colspan="1" rowspan="1" style="width:69px" %)RSSI
262 |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:151px" %)adc0|(% colspan="1" rowspan="1" style="width:160px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
263 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc0|(% colspan="1" style="width:160px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
264 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)adc0|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc1|(% colspan="1" style="width:160px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:67px" %)adc4|(% colspan="1" style="width:69px" %)
265 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
266 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
267 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
Xiaoling 53.2 268
Edwin Chen 100.1 269 == 3.4 [[Datacake>>https://datacake.co/]] ==
Xiaoling 99.3 270
Xiaoling 53.2 271
Edwin Chen 100.1 272 (% class="wikigeneratedid" %)
273 Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
274
275
276 (% class="wikigeneratedid" %)
Xiaoling 100.5 277 As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
Edwin Chen 100.1 278
Xiaoling 100.2 279 * (% style="color:blue" %)**S31B-NB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
Edwin Chen 100.1 280
Xiaoling 100.2 281 * (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
Edwin Chen 100.1 282
Edwin Chen 109.1 283 === 3.4.1 For device Already has template ===
Xiaoling 53.2 284
Edwin Chen 109.1 285 ==== 3.4.1.1 Create Device ====
Xiaoling 83.4 286
Xiaoling 100.4 287 (% style="color:blue" %)**Add Device**(%%) in DataCake.
Edwin Chen 100.1 288
Xiaoling 105.2 289 [[image:image-20230808162301-1.png||height="453" width="952"]]
Xiaoling 53.11 290
291
Xiaoling 105.2 292 [[image:image-20230808162342-2.png||height="541" width="952"]]
David Huang 78.1 293
294
Xiaoling 100.3 295 (% style="color:blue" %)**Choose the correct model**(%%) from template.
Edwin Chen 100.1 296
David Huang 78.1 297 [[image:image-20230808162421-3.png]]
298
Xiaoling 83.4 299
Xiaoling 100.3 300 (% style="color:blue" %)**Fill Device ID**(%%). The device ID needs to be filled in with IMEI, and a prefix of(% style="color:blue" %)** 'f' **(%%)needs to be added.
David Huang 78.1 301
Xiaoling 105.2 302 [[image:image-20230808163612-7.png||height="549" width="952"]]
David Huang 78.1 303
304 [[image:image-20230808163035-5.png]]
305
Xiaoling 105.2 306 [[image:image-20230808163049-6.png||height="544" width="926"]]
David Huang 78.1 307
Xiaoling 83.4 308
Edwin Chen 109.1 309 === 3.4.2 For Device already registered in DataCake before shipped ===
David Huang 81.1 310
Edwin Chen 126.1 311 ==== 3.4.2.1 Scan QR Code to get the device info ====
Xiaoling 83.4 312
David Huang 81.1 313 Users can use their phones or computers to scan QR codes to obtain device data information.
314
Edwin Chen 100.1 315 [[image:image-20230808170051-8.png||height="255" width="259"]]
David Huang 81.1 316
317 [[image:image-20230808170548-9.png]]
318
Xiaoling 83.4 319
Edwin Chen 126.1 320 ==== 3.4.2.2 Claim Device to User Account ====
321
322 By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
323
324
325
Edwin Chen 109.1 326 === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
David Huang 81.1 327
Bei Jinggeng 123.1 328 **Step1:Add a device**
David Huang 81.1 329
Bei Jinggeng 123.1 330 [[image:image-20240129170024-1.png||height="330" width="900"]]
331
332 **Step2:Choose your device type,please select dragino NB-IOT device**
333
334 [[image:image-20240129170216-2.png||height="534" width="643"]]
335
336 **Step3:Choose to create a new device**
337
338 [[image:image-20240129170539-3.png||height="459" width="646"]]
339
340 **Step4:Fill in the device ID of your NB device**
341
Bei Jinggeng 125.1 342 [[image:image-20240202111546-1.png||height="378" width="651"]]
Bei Jinggeng 123.1 343
344 **Step5:Please select your device plan according to your needs and complete the creation of the device**
345
346 [[image:image-20240129171236-6.png||height="450" width="648"]]
347
348 **Step6:Please add the decoder at the payload decoder of the device configuration.**
349
Bei Jinggeng 127.1 350 **Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
351
Bei Jinggeng 123.1 352 [[image:image-20240129172056-7.png||height="457" width="816"]]
353
354 [[image:image-20240129173116-9.png||height="499" width="814"]]
355
356 **Step6:Add the output of the decoder as a field**
357
358 [[image:image-20240129173541-10.png||height="592" width="968"]]
359
360 **Step7:Customize the dashboard and use fields as parameters of the dashboard**
361
362 [[image:image-20240129174518-11.png||height="147" width="1042"]]
363
364 [[image:image-20240129174657-12.png||height="538" width="916"]]
365
366 [[image:image-20240129174840-13.png||height="536" width="750"]]
367
368
Edwin Chen 109.1 369 === 3.4.4 For device have not configured to connect to DataCake ===
370
371 (% class="lead" %)
372 Use AT command for connecting to DataCake
373
Xiaoling 83.4 374 (% style="color:blue" %)**AT+PRO=2,0**
David Huang 81.1 375
Xiaoling 83.4 376 (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
David Huang 81.1 377
Xiaoling 83.4 378
Xiaoling 53.21 379 == 3.5 Node-Red (via MQTT) ==
Xiaoling 53.2 380
Xiaoling 53.48 381 === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
Xiaoling 53.2 382
Xiaoling 53.32 383
David Huang 93.1 384 Take S31-NB UDP protocol as an example.
Xiaoling 53.2 385
David Huang 93.1 386 Dragino provides input flow examples for the sensors.
Xiaoling 53.32 387
David Huang 93.1 388 User can download the required JSON file through Dragino Node-RED input flow template.
Xiaoling 53.2 389
David Huang 93.1 390 Download sample JSON file link: [[https:~~/~~/www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0>>url:https://www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0]]
Xiaoling 53.24 391
David Huang 93.1 392 We can directly import the template.
Xiaoling 53.2 393
David Huang 93.1 394 The templates for S31-NB and NB95S31B are the same.
Xiaoling 53.21 395
Xiaoling 53.2 396
David Huang 93.1 397 [[image:image-20230809173127-4.png]]
Xiaoling 53.2 398
Xiaoling 99.3 399
David Huang 93.1 400 Please select the NB95S31B template.
Xiaoling 53.2 401
Xiaoling 105.2 402 [[image:image-20230809173310-5.png||height="558" width="926"]]
Xiaoling 53.2 403
David Huang 93.1 404 [[image:image-20230809173438-6.png]]
Xiaoling 53.2 405
David Huang 93.1 406 [[image:image-20230809173800-7.png]]
Xiaoling 53.21 407
Xiaoling 99.3 408
David Huang 93.1 409 Successfully imported template.
Xiaoling 53.21 410
Xiaoling 105.2 411 [[image:image-20230809173835-8.png||height="515" width="860"]]
Xiaoling 53.21 412
413
David Huang 93.1 414 Users can set UDP port.
Xiaoling 53.21 415
David Huang 93.1 416 [[image:image-20230809174053-9.png]]
Xiaoling 83.8 417
Xiaoling 99.3 418
David Huang 93.1 419 === 3.5.2 Simulate Connection ===
Xiaoling 83.8 420
Xiaoling 99.3 421
David Huang 93.1 422 We have completed the configuration of UDP. We can try sending packets to node red.
423
David Huang 98.1 424 [[image:image-20230810083934-1.png]]
David Huang 93.1 425
Xiaoling 105.2 426 [[image:image-20230810084048-2.png||height="535" width="1052"]]
David Huang 93.1 427
Xiaoling 105.2 428
David Huang 93.1 429 === 3.5.3 Configure NB-IoT Sensors ===
430
431
Saxer Lin 106.1 432 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
433 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
434 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
435 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
436 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
437 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
David Huang 93.1 438
Xiaoling 53.21 439 == 3.6 ThingsBoard.Cloud (via MQTT) ==
440
441 === 3.6.1 Configure ThingsBoard ===
442
Xiaoling 53.22 443 ==== 3.6.1.1 Create Device ====
Xiaoling 53.2 444
Xiaoling 53.32 445
Edwin Chen 59.1 446 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
Xiaoling 53.2 447
Xiaoling 105.2 448 [[image:image-20230802112413-32.png||height="583" width="1066"]]
Xiaoling 53.2 449
450
Xiaoling 53.23 451 ==== 3.6.1.2 Create Uplink & Downlink Converter ====
452
Xiaoling 53.32 453
Xiaoling 53.22 454 (% style="color:blue" %)**Uplink Converter**
Xiaoling 53.2 455
456 The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
457
Xiaoling 53.42 458 To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
Xiaoling 53.2 459
Xiaoling 105.2 460 [[image:image-20230802112413-33.png||height="597" width="1061"]]
Xiaoling 53.2 461
462
Xiaoling 53.22 463 (% style="color:blue" %)**Downlink Converter**
Xiaoling 53.2 464
465 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
466
Xiaoling 105.2 467 [[image:image-20230802112413-34.png||height="598" width="1063"]]
Xiaoling 53.2 468
Xiaoling 83.8 469 (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
Xiaoling 53.2 470
Xiaoling 53.22 471
Xiaoling 53.23 472 ==== 3.6.1.3 MQTT Integration Setup ====
Xiaoling 53.2 473
474
Xiaoling 53.44 475 Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
Xiaoling 53.24 476
Xiaoling 105.2 477 [[image:image-20230802112413-35.png||height="597" width="1062"]]
Xiaoling 53.2 478
Xiaoling 53.32 479
Xiaoling 53.2 480 * The next steps is to add the recently created uplink and downlink converters;
481
Xiaoling 105.2 482 [[image:image-20230802112413-36.png||height="598" width="1062"]]
Xiaoling 53.2 483
Xiaoling 105.2 484 [[image:image-20230802112413-37.png||height="598" width="1064"]]
Xiaoling 53.2 485
Xiaoling 53.33 486
Xiaoling 53.24 487 (% style="color:blue" %)**Add a topic filter:**
Xiaoling 53.2 488
Mengting Qiu 108.1 489 Consistent with the theme of the node setting.
Xiaoling 53.2 490
491 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
492
Xiaoling 105.2 493 [[image:image-20230802112413-38.png||height="598" width="1064"]]
Xiaoling 53.2 494
495
Xiaoling 53.23 496 === 3.6.2 Simulate with MQTT.fx ===
497
Xiaoling 53.32 498
Xiaoling 53.2 499 [[image:image-20230802112413-39.png]]
500
Xiaoling 105.2 501 [[image:image-20230802112413-40.png||height="525" width="980"]]
Xiaoling 53.2 502
503
Xiaoling 53.23 504 === 3.6.3 Configure NB-IoT Sensor ===
Xiaoling 53.2 505
Xiaoling 53.25 506
Xiaoling 53.23 507 (% style="color:blue" %)**AT Commands**
Xiaoling 53.2 508
Edwin Chen 59.1 509 * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
Xiaoling 53.2 510
Xiaoling 83.4 511 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
512
Edwin Chen 59.1 513 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
Xiaoling 83.4 514
Edwin Chen 59.1 515 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
Xiaoling 83.4 516
Edwin Chen 59.1 517 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
Xiaoling 83.4 518
Edwin Chen 59.1 519 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
Xiaoling 53.2 520
521 Test Uplink by click the button for 1 second
522
Xiaoling 105.2 523 [[image:image-20230802112413-41.png||height="496" width="828"]]
Xiaoling 53.2 524
525 [[image:image-20230802112413-42.png]]
526
Xiaoling 105.2 527 [[image:image-20230802112413-43.png||height="407" width="825"]]
Xiaoling 53.2 528
529
Xiaoling 53.23 530 == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
Xiaoling 53.2 531
Xiaoling 53.23 532 === 3.7.1 Create device & Get Credentials ===
Xiaoling 53.2 533
Xiaoling 53.23 534
Xiaoling 53.2 535 We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
536
537 [[image:image-20230802112413-44.png]]
538
539 [[image:image-20230802112413-45.png]]
540
541
542 Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
543
544 [[image:image-20230802112413-46.png]]
545
546
David Huang 70.1 547 The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
Xiaoling 53.2 548
Xiaoling 83.8 549 (% style="color:blue" %)**On the Connection Profile window, set the following information:**
David Huang 70.1 550
Xiaoling 83.8 551 * (% style="color:#037691" %)**Profile Name: “Any name”**
Xiaoling 53.2 552
Xiaoling 83.8 553 * (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
Xiaoling 53.23 554
Xiaoling 83.8 555 * (% style="color:#037691" %)**Broker Port: 8883**
Xiaoling 53.23 556
Xiaoling 83.8 557 * (% style="color:#037691" %)**Client ID: “Any value”**
Xiaoling 53.23 558
Xiaoling 83.8 559 (% style="color:blue" %)**On the section User credentials, set the following information:**
Xiaoling 53.2 560
Xiaoling 83.8 561 * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
Xiaoling 53.2 562
Xiaoling 83.8 563 * (% style="color:#037691" %)**Password: “Your device token”**
Xiaoling 53.2 564
Xiaoling 83.8 565 * (% style="color:#037691" %)**PUBTOPIC: “Any value”**
Xiaoling 53.23 566
Xiaoling 83.8 567 * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
Xiaoling 53.23 568
David Huang 70.1 569 (% style="color:blue" %)**AT command:**
570
Xiaoling 83.8 571 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
David Huang 70.1 572
Xiaoling 83.5 573 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
David Huang 70.1 574
Xiaoling 83.5 575 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
576
577 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
578
579 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
580
581 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
582
Xiaoling 53.23 583 === 3.7.2 Simulate with MQTT.fx ===
584
Xiaoling 99.3 585
David Huang 70.1 586 [[image:image-20230802112413-52.png]]
Xiaoling 53.23 587
Xiaoling 53.2 588
Xiaoling 105.2 589 [[image:image-20230808105300-2.png||height="553" width="1026"]]
Xiaoling 53.2 590
Xiaoling 99.3 591
Xiaoling 53.38 592 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
Xiaoling 53.2 593
Xiaoling 105.2 594 [[image:image-20230808105217-1.png||height="556" width="1031"]]
Xiaoling 53.44 595
David Huang 70.1 596 [[image:image-20230808105329-3.png]]
Xiaoling 53.2 597
598
Xiaoling 53.23 599 === 3.7.3 tago data ===
Xiaoling 53.2 600
Xiaoling 53.23 601
Xiaoling 105.2 602 [[image:image-20230802112413-50.png||height="242" width="1037"]]
Xiaoling 53.2 603
Edwin Chen 59.1 604 [[image:image-20230802112413-51.png||height="184" width="696"]]
Xiaoling 53.2 605
606
Edwin Chen 65.1 607 == 3.8 TCP Connection ==
Edwin Chen 63.1 608
Xiaoling 83.6 609
Xiaoling 83.5 610 (% style="color:blue" %)**AT command:**
Edwin Chen 63.1 611
Xiaoling 83.5 612 * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
Edwin Chen 63.1 613
Xiaoling 83.5 614 * (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
Edwin Chen 63.1 615
Xiaoling 83.8 616 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
Xiaoling 83.5 617
Xiaoling 83.6 618 (% style="color:blue" %)**Sensor Console Output when Uplink:**
Xiaoling 83.5 619
Edwin Chen 63.1 620 [[image:image-20230807233631-1.png]]
621
622
Xiaoling 83.6 623 (% style="color:blue" %)**See result in TCP Server:**
Edwin Chen 63.1 624
625 [[image:image-20230807233631-2.png]]
Edwin Chen 132.1 626
627
Edwin Chen 133.1 628 = 4. FAQ =
Edwin Chen 132.1 629
Edwin Chen 133.1 630 == 4.1 What is the usage of Multi Sampling and One Uplink? ==
Edwin Chen 132.1 631
Edwin Chen 133.1 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
Edwin Chen 132.1 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
652 If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
653
654 [[image:image-20240207002003-1.png]]
655
656
657 If fail to attach network, it will shows signal 99. as below:
658
659 [[image:image-20240207002129-2.png]]
660
661
662 (% class="lead" %)
663 When see this issue, below are the checklist:
664
665 * 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.
666 * 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]].
667 * 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]].
668 * Check if the device is attached to Carrier network but reject. (need to check with operator).
669 * Check if the antenna is connected firmly.
670
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
Edwin Chen 135.1 673
Edwin Chen 138.1 674 == 5.2 Issue: "NBIOT did not respond" ==
Edwin Chen 135.1 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]]
Edwin Chen 138.1 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
Edwin Chen 141.1 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
Mengting Qiu 142.1 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.
Edwin Chen 141.1 717
718 [[image:image-20240226111928-1.png]]
719
720
721
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0