Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 102.2
edited by Xiaoling
on 2023/09/07 16:14
Change comment: There is no comment for this version
To version 83.6
edited by Xiaoling
on 2023/08/09 10:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,10 +4,6 @@
4 4  {{toc/}}
5 5  
6 6  
7 -
8 -
9 -
10 -
11 11  = 1. The use of this guideline =
12 12  
13 13  
... ... @@ -21,7 +21,7 @@
21 21  
22 22  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
23 23  1. Insert the SIM card to Sensor
24 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
20 +1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (% class="mark" %)(补充 APN 指令(%%))
25 25  
26 26  [[image:image-20230808205045-1.png||height="293" width="438"]]
27 27  
... ... @@ -30,7 +30,7 @@
30 30  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.
31 31  
32 32  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
33 -|(% 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**
29 +|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
34 34  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
35 35  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
36 36  
... ... @@ -39,8 +39,6 @@
39 39  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
40 40  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
41 41  
42 -
43 -
44 44  = 3. Configure to connect to different servers =
45 45  
46 46  == 3.1 General UDP Connection ==
... ... @@ -104,7 +104,7 @@
104 104  
105 105  [[image:image-20230802112413-4.png]]
106 106  
107 -[[image:image-20230802112413-5.png||height="530" width="987"]]
101 +[[image:image-20230802112413-5.png]]
108 108  
109 109  (% 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.**
110 110  
... ... @@ -116,7 +116,7 @@
116 116  
117 117  [[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.
118 118  
119 -[[image:image-20230802112413-6.png||height="336" width="925"]]
113 +[[image:image-20230802112413-6.png]]
120 120  
121 121  [[image:image-20230802112413-7.png]]
122 122  
... ... @@ -140,8 +140,6 @@
140 140  
141 141  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
142 142  
143 -
144 -
145 145  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
146 146  
147 147  
... ... @@ -161,7 +161,7 @@
161 161  
162 162  (% style="color:blue" %)**Result: **
163 163  
164 -[[image:image-20230802112413-11.png||height="539" width="901"]]
156 +[[image:image-20230802112413-11.png]]
165 165  
166 166  
167 167  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -187,8 +187,9 @@
187 187  
188 188  ==== 3.3.3.2 Uplink Examples ====
189 189  
190 -[[image:image-20230816201942-1.png]]
191 191  
183 +For S31-NB
184 +
192 192  For SE01-NB
193 193  
194 194  For DDS20-NB
... ... @@ -218,9 +218,9 @@
218 218  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.
219 219  
220 220  
221 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
214 +[[image:image-20230802112413-12.png]]
222 222  
223 -[[image:image-20230802112413-13.png||height="331" width="978"]]
216 +[[image:image-20230802112413-13.png]]
224 224  
225 225  
226 226  Below is the NB-IoT Product Table show the mapping.
... ... @@ -245,41 +245,21 @@
245 245  |(% 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" %)
246 246  |(% 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" %)
247 247  
241 +== 3.4 Datacake ==
248 248  
249 -
250 -== 3.4 [[Datacake>>https://datacake.co/]] ==
251 -
252 -
253 -(% class="wikigeneratedid" %)
254 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
255 -
256 -
257 -(% class="wikigeneratedid" %)
258 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
259 -
260 -* (% 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.
261 -
262 -* (% 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.
263 -
264 -
265 -
266 266  === 3.4.1 Create device ===
267 267  
268 268  
269 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
246 +[[image:image-20230808162301-1.png]]
270 270  
271 -[[image:image-20230808162301-1.png||height="473" width="994"]]
272 272  
273 -
274 274  [[image:image-20230808162342-2.png]]
275 275  
276 276  
277 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
278 -
279 279  [[image:image-20230808162421-3.png]]
280 280  
281 281  
282 -(% 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.
255 +The device ID needs to be filled in with IMEI, and a prefix of 'f' needs to be added.
283 283  
284 284  [[image:image-20230808163612-7.png]]
285 285  
... ... @@ -293,7 +293,7 @@
293 293  
294 294  Users can use their phones or computers to scan QR codes to obtain device data information.
295 295  
296 -[[image:image-20230808170051-8.png||height="255" width="259"]]
269 +[[image:image-20230808170051-8.png]]
297 297  
298 298  [[image:image-20230808170548-9.png]]
299 299  
... ... @@ -311,59 +311,33 @@
311 311  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
312 312  
313 313  
314 -Take S31-NB UDP protocol as an example.
287 +[[image:image-20230802112413-29.png]]
315 315  
316 -Dragino provides input flow examples for the sensors.
317 317  
318 -User can download the required JSON file through Dragino Node-RED input flow template.
290 +[[image:image-20230802112413-30.png]]
319 319  
320 -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]]
321 321  
322 -We can directly import the template.
323 -
324 -The templates for S31-NB and NB95S31B are the same.
325 -
326 -
327 -[[image:image-20230809173127-4.png]]
328 -
329 -
330 -Please select the NB95S31B template.
331 -
332 -[[image:image-20230809173310-5.png]]
333 -
334 -[[image:image-20230809173438-6.png]]
335 -
336 -[[image:image-20230809173800-7.png]]
337 -
338 -
339 -Successfully imported template.
340 -
341 -[[image:image-20230809173835-8.png]]
342 -
343 -
344 -Users can set UDP port.
345 -
346 -[[image:image-20230809174053-9.png]]
347 -
348 -
349 349  === 3.5.2 Simulate Connection ===
350 350  
351 351  
352 -We have completed the configuration of UDP. We can try sending packets to node red.
296 +[[image:image-20230802112413-31.png]]
353 353  
354 -[[image:image-20230810083934-1.png]]
355 355  
356 -[[image:image-20230810084048-2.png]]
357 -
358 358  === 3.5.3 Configure NB-IoT Sensors ===
359 359  
360 360  
361 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
302 +* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    ~/~/  Set to mqtt Server and  Payload
362 362  
363 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
304 +* (% style="color:blue" %)**AT+CLIENT=any value**
364 364  
306 +* (% style="color:blue" %)**AT+UNAME=any value**
365 365  
308 +* (% style="color:blue" %)**AT+PWD=any value**
366 366  
310 +* (% style="color:blue" %)**AT+PUBTOPIC=any value**
311 +
312 +* (% style="color:blue" %)**AT+SUBTOPIC=any value**
313 +
367 367  == 3.6 ThingsBoard.Cloud (via MQTT) ==
368 368  
369 369  === 3.6.1 Configure ThingsBoard ===
... ... @@ -394,7 +394,7 @@
394 394  
395 395  [[image:image-20230802112413-34.png||height="734" width="1305"]]
396 396  
397 -(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
344 +(% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
398 398  
399 399  
400 400  ==== 3.6.1.3 MQTT Integration Setup ====
... ... @@ -474,29 +474,29 @@
474 474  
475 475  The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
476 476  
477 -(% style="color:blue" %)**On the Connection Profile window, set the following information:**
424 +On the Connection Profile window, set the following information:
478 478  
479 -* (% style="color:#037691" %)**Profile Name: “Any name”**
426 +* (% style="color:blue" %)**Profile Name: “Any name”**
480 480  
481 -* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
428 +* (% style="color:blue" %)**Broker Address: mqtt.tago.io**
482 482  
483 -* (% style="color:#037691" %)**Broker Port: 8883**
430 +* (% style="color:blue" %)**Broker Port: 8883**
484 484  
485 -* (% style="color:#037691" %)**Client ID: “Any value”**
432 +* (% style="color:blue" %)**Client ID: “Any value”**
486 486  
487 -(% style="color:blue" %)**On the section User credentials, set the following information:**
434 +On the section User credentials, set the following information:
488 488  
489 -* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
436 +* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only
490 490  
491 -* (% style="color:#037691" %)**Password: “Your device token”**
438 +* (% style="color:blue" %)**Password: “Your device token”**
492 492  
493 -* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
440 +* (% style="color:blue" %)**PUBTOPIC: “Any value”**
494 494  
495 -* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
442 +* (% style="color:blue" %)**SUBTOPIC: “Any value”**
496 496  
497 497  (% style="color:blue" %)**AT command:**
498 498  
499 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
446 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) ~/~/ hex format or json format
500 500  
501 501  * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
502 502  
... ... @@ -510,15 +510,14 @@
510 510  
511 511  
512 512  
460 +
513 513  === 3.7.2 Simulate with MQTT.fx ===
514 514  
515 -
516 516  [[image:image-20230802112413-52.png]]
517 517  
518 518  
519 519  [[image:image-20230808105300-2.png]]
520 520  
521 -
522 522  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
523 523  
524 524  [[image:image-20230808105217-1.png]]
... ... @@ -534,6 +534,7 @@
534 534  [[image:image-20230802112413-51.png||height="184" width="696"]]
535 535  
536 536  
483 +
537 537  == 3.8 TCP Connection ==
538 538  
539 539  
... ... @@ -543,8 +543,10 @@
543 543  
544 544  * (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
545 545  
546 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
493 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
547 547  
495 +
496 +
548 548  (% style="color:blue" %)**Sensor Console Output when Uplink:**
549 549  
550 550  [[image:image-20230807233631-1.png]]
... ... @@ -553,3 +553,6 @@
553 553  (% style="color:blue" %)**See result in TCP Server:**
554 554  
555 555  [[image:image-20230807233631-2.png]]
505 +
506 +
507 +
image-20230809165928-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -74.4 KB
Content
image-20230809170225-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20230809170532-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -38.7 KB
Content
image-20230809173127-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -82.5 KB
Content
image-20230809173310-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20230809173438-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -41.0 KB
Content
image-20230809173800-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -46.8 KB
Content
image-20230809173835-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -88.8 KB
Content
image-20230809174053-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -58.0 KB
Content
image-20230809180523-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -63.7 KB
Content
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content