Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 105.2
edited by Xiaoling
on 2023/11/06 16:16
Change comment: There is no comment for this version
To version 89.1
edited by David Huang
on 2023/08/09 17:34
Change comment: Uploaded new attachment "image-20230809173438-6.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
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  
... ... @@ -16,14 +16,12 @@
16 16  
17 17  = 2. Attach Network =
18 18  
19 -== 2.1 General Configure to attach network ==
20 20  
21 -
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 25  1. Insert the SIM card to Sensor
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>)
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 指令(%%))
27 27  
28 28  [[image:image-20230808205045-1.png||height="293" width="438"]]
29 29  
... ... @@ -32,7 +32,7 @@
32 32  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.
33 33  
34 34  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
35 -|(% 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**
36 36  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
37 37  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
38 38  
... ... @@ -43,21 +43,6 @@
43 43  
44 44  
45 45  
46 -== 2.2 Speed Up Network Attach time ==
47 -
48 -
49 -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. User can lock the band to specify band for its operator to make this faster.
50 -
51 -(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
52 -
53 -(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
54 -
55 -(% style="color:#037691" %)**AT+QBAND=2,8,20**  (%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
56 -
57 -
58 -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/]]**
59 -
60 -
61 61  = 3. Configure to connect to different servers =
62 62  
63 63  == 3.1 General UDP Connection ==
... ... @@ -71,7 +71,7 @@
71 71  
72 72  We can use PC tool to simulate UDP connection to make sure server works ok.
73 73  
74 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
53 +[[image:image-20230802112413-1.png]]
75 75  
76 76  
77 77  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -121,7 +121,7 @@
121 121  
122 122  [[image:image-20230802112413-4.png]]
123 123  
124 -[[image:image-20230802112413-5.png||height="530" width="987"]]
103 +[[image:image-20230802112413-5.png]]
125 125  
126 126  (% 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.**
127 127  
... ... @@ -133,7 +133,7 @@
133 133  
134 134  [[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.
135 135  
136 -[[image:image-20230802112413-6.png||height="336" width="925"]]
115 +[[image:image-20230802112413-6.png]]
137 137  
138 138  [[image:image-20230802112413-7.png]]
139 139  
... ... @@ -178,7 +178,7 @@
178 178  
179 179  (% style="color:blue" %)**Result: **
180 180  
181 -[[image:image-20230802112413-11.png||height="539" width="901"]]
160 +[[image:image-20230802112413-11.png]]
182 182  
183 183  
184 184  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -188,7 +188,7 @@
188 188  
189 189  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
190 190  
191 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
170 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) **~/~/ Set to use ThingSpeak Server and Related Payload**
192 192  
193 193  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
194 194  
... ... @@ -205,7 +205,7 @@
205 205  ==== 3.3.3.2 Uplink Examples ====
206 206  
207 207  
208 -[[image:image-20230816201942-1.png]]
187 +For S31-NB
209 209  
210 210  For SE01-NB
211 211  
... ... @@ -236,9 +236,9 @@
236 236  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.
237 237  
238 238  
239 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
218 +[[image:image-20230802112413-12.png]]
240 240  
241 -[[image:image-20230802112413-13.png||height="331" width="978"]]
220 +[[image:image-20230802112413-13.png]]
242 242  
243 243  
244 244  Below is the NB-IoT Product Table show the mapping.
... ... @@ -265,45 +265,27 @@
265 265  
266 266  
267 267  
268 -== 3.4 [[Datacake>>https://datacake.co/]] ==
247 +== 3.4 Datacake ==
269 269  
270 -
271 -(% class="wikigeneratedid" %)
272 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
273 -
274 -
275 -(% class="wikigeneratedid" %)
276 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
277 -
278 -* (% 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.
279 -
280 -* (% 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.
281 -
282 -
283 -
284 284  === 3.4.1 Create device ===
285 285  
286 286  
287 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
252 +[[image:image-20230808162301-1.png]]
288 288  
289 -[[image:image-20230808162301-1.png||height="453" width="952"]]
290 290  
255 +[[image:image-20230808162342-2.png]]
291 291  
292 -[[image:image-20230808162342-2.png||height="541" width="952"]]
293 293  
294 -
295 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
296 -
297 297  [[image:image-20230808162421-3.png]]
298 298  
299 299  
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.
261 +The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
301 301  
302 -[[image:image-20230808163612-7.png||height="549" width="952"]]
263 +[[image:image-20230808163612-7.png]]
303 303  
304 304  [[image:image-20230808163035-5.png]]
305 305  
306 -[[image:image-20230808163049-6.png||height="544" width="926"]]
267 +[[image:image-20230808163049-6.png]]
307 307  
308 308  
309 309  === 3.4.2 Scan QR code to obtain data ===
... ... @@ -311,7 +311,7 @@
311 311  
312 312  Users can use their phones or computers to scan QR codes to obtain device data information.
313 313  
314 -[[image:image-20230808170051-8.png||height="255" width="259"]]
275 +[[image:image-20230808170051-8.png]]
315 315  
316 316  [[image:image-20230808170548-9.png]]
317 317  
... ... @@ -329,60 +329,35 @@
329 329  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
330 330  
331 331  
332 -Take S31-NB UDP protocol as an example.
293 +[[image:image-20230802112413-29.png]]
333 333  
334 -Dragino provides input flow examples for the sensors.
335 335  
336 -User can download the required JSON file through Dragino Node-RED input flow template.
296 +[[image:image-20230802112413-30.png]]
337 337  
338 -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]]
339 339  
340 -We can directly import the template.
299 +=== 3.5.2 Simulate Connection ===
341 341  
342 -The templates for S31-NB and NB95S31B are the same.
343 343  
302 +[[image:image-20230802112413-31.png]]
344 344  
345 -[[image:image-20230809173127-4.png]]
346 346  
305 +=== 3.5.3 Configure NB-IoT Sensors ===
347 347  
348 -Please select the NB95S31B template.
349 349  
350 -[[image:image-20230809173310-5.png||height="558" width="926"]]
308 +* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    **~/~/  Set to mqtt Server and  Payload**
351 351  
352 -[[image:image-20230809173438-6.png]]
310 +* (% style="color:blue" %)**AT+CLIENT=any value**
353 353  
354 -[[image:image-20230809173800-7.png]]
312 +* (% style="color:blue" %)**AT+UNAME=any value**
355 355  
314 +* (% style="color:blue" %)**AT+PWD=any value**
356 356  
357 -Successfully imported template.
316 +* (% style="color:blue" %)**AT+PUBTOPIC=any value**
358 358  
359 -[[image:image-20230809173835-8.png||height="515" width="860"]]
318 +* (% style="color:blue" %)**AT+SUBTOPIC=any value**
360 360  
361 361  
362 -Users can set UDP port.
363 363  
364 -[[image:image-20230809174053-9.png]]
365 -
366 -
367 -=== 3.5.2 Simulate Connection ===
368 -
369 -
370 -We have completed the configuration of UDP. We can try sending packets to node red.
371 -
372 -[[image:image-20230810083934-1.png]]
373 -
374 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
375 -
376 -
377 -=== 3.5.3 Configure NB-IoT Sensors ===
378 -
379 -
380 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
381 -
382 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
383 -
384 -
385 -
386 386  == 3.6 ThingsBoard.Cloud (via MQTT) ==
387 387  
388 388  === 3.6.1 Configure ThingsBoard ===
... ... @@ -392,7 +392,7 @@
392 392  
393 393  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
394 394  
395 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
331 +[[image:image-20230802112413-32.png]]
396 396  
397 397  
398 398  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -404,7 +404,7 @@
404 404  
405 405  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.
406 406  
407 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
343 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
408 408  
409 409  
410 410  (% style="color:blue" %)**Downlink Converter**
... ... @@ -411,7 +411,7 @@
411 411  
412 412  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
413 413  
414 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
350 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
415 415  
416 416  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
417 417  
... ... @@ -421,14 +421,14 @@
421 421  
422 422  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**;
423 423  
424 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
360 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
425 425  
426 426  
427 427  * The next steps is to add the recently created uplink and downlink converters;
428 428  
429 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
365 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
430 430  
431 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
367 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
432 432  
433 433  
434 434  (% style="color:blue" %)**Add a topic filter:**
... ... @@ -437,7 +437,7 @@
437 437  
438 438  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
439 439  
440 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
376 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
441 441  
442 442  
443 443  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -445,7 +445,7 @@
445 445  
446 446  [[image:image-20230802112413-39.png]]
447 447  
448 -[[image:image-20230802112413-40.png||height="525" width="980"]]
384 +[[image:image-20230802112413-40.png]]
449 449  
450 450  
451 451  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -465,13 +465,15 @@
465 465  
466 466  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
467 467  
404 +
405 +
468 468  Test Uplink by click the button for 1 second
469 469  
470 -[[image:image-20230802112413-41.png||height="496" width="828"]]
408 +[[image:image-20230802112413-41.png]]
471 471  
472 472  [[image:image-20230802112413-42.png]]
473 473  
474 -[[image:image-20230802112413-43.png||height="407" width="825"]]
412 +[[image:image-20230802112413-43.png]]
475 475  
476 476  
477 477  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -503,6 +503,8 @@
503 503  
504 504  * (% style="color:#037691" %)**Client ID: “Any value”**
505 505  
444 +
445 +
506 506  (% style="color:blue" %)**On the section User credentials, set the following information:**
507 507  
508 508  * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
... ... @@ -513,6 +513,8 @@
513 513  
514 514  * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
515 515  
456 +
457 +
516 516  (% style="color:blue" %)**AT command:**
517 517  
518 518  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -531,16 +531,14 @@
531 531  
532 532  === 3.7.2 Simulate with MQTT.fx ===
533 533  
534 -
535 535  [[image:image-20230802112413-52.png]]
536 536  
537 537  
538 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
479 +[[image:image-20230808105300-2.png]]
539 539  
540 -
541 541  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
542 542  
543 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
483 +[[image:image-20230808105217-1.png]]
544 544  
545 545  [[image:image-20230808105329-3.png]]
546 546  
... ... @@ -548,11 +548,12 @@
548 548  === 3.7.3 tago data ===
549 549  
550 550  
551 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
491 +[[image:image-20230802112413-50.png]]
552 552  
553 553  [[image:image-20230802112413-51.png||height="184" width="696"]]
554 554  
555 555  
496 +
556 556  == 3.8 TCP Connection ==
557 557  
558 558  
... ... @@ -575,3 +575,5 @@
575 575  
576 576  [[image:image-20230807233631-2.png]]
577 577  
519 +
520 +
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