Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 91.1
edited by David Huang
on 2023/08/09 17:38
Change comment: Uploaded new attachment "image-20230809173835-8.png", version {1}
To version 106.1
edited by Saxer Lin
on 2023/11/25 17:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Saxer
Content
... ... @@ -4,6 +4,10 @@
4 4  {{toc/}}
5 5  
6 6  
7 +
8 +
9 +
10 +
7 7  = 1. The use of this guideline =
8 8  
9 9  
... ... @@ -12,12 +12,14 @@
12 12  
13 13  = 2. Attach Network =
14 14  
19 +== 2.1 General Configure to attach network ==
15 15  
21 +
16 16  To attache NB-IoT sensors to NB-IoT Network, You need to:
17 17  
18 18  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
19 19  1. Insert the SIM card to Sensor
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 指令(%%))
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>)
21 21  
22 22  [[image:image-20230808205045-1.png||height="293" width="438"]]
23 23  
... ... @@ -26,7 +26,7 @@
26 26  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.
27 27  
28 28  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
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**
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**
30 30  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
31 31  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
32 32  
... ... @@ -36,7 +36,21 @@
36 36  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
37 37  
38 38  
45 +== 2.2 Speed Up Network Attach time ==
39 39  
47 +
48 +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.
49 +
50 +(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
51 +
52 +(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
53 +
54 +(% style="color:#037691" %)**AT+QBAND=2,8,20**  (%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
55 +
56 +
57 +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/]]**
58 +
59 +
40 40  = 3. Configure to connect to different servers =
41 41  
42 42  == 3.1 General UDP Connection ==
... ... @@ -50,7 +50,7 @@
50 50  
51 51  We can use PC tool to simulate UDP connection to make sure server works ok.
52 52  
53 -[[image:image-20230802112413-1.png]]
73 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
54 54  
55 55  
56 56  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -100,7 +100,7 @@
100 100  
101 101  [[image:image-20230802112413-4.png]]
102 102  
103 -[[image:image-20230802112413-5.png]]
123 +[[image:image-20230802112413-5.png||height="530" width="987"]]
104 104  
105 105  (% 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.**
106 106  
... ... @@ -112,7 +112,7 @@
112 112  
113 113  [[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.
114 114  
115 -[[image:image-20230802112413-6.png]]
135 +[[image:image-20230802112413-6.png||height="336" width="925"]]
116 116  
117 117  [[image:image-20230802112413-7.png]]
118 118  
... ... @@ -137,7 +137,6 @@
137 137  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
138 138  
139 139  
140 -
141 141  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
142 142  
143 143  
... ... @@ -157,7 +157,7 @@
157 157  
158 158  (% style="color:blue" %)**Result: **
159 159  
160 -[[image:image-20230802112413-11.png]]
179 +[[image:image-20230802112413-11.png||height="539" width="901"]]
161 161  
162 162  
163 163  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -167,7 +167,7 @@
167 167  
168 168  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
169 169  
170 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) **~/~/ Set to use ThingSpeak Server and Related Payload**
189 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
171 171  
172 172  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
173 173  
... ... @@ -180,11 +180,10 @@
180 180  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
181 181  
182 182  
183 -
184 184  ==== 3.3.3.2 Uplink Examples ====
185 185  
186 186  
187 -For S31-NB
205 +[[image:image-20230816201942-1.png]]
188 188  
189 189  For SE01-NB
190 190  
... ... @@ -215,9 +215,9 @@
215 215  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.
216 216  
217 217  
218 -[[image:image-20230802112413-12.png]]
236 +[[image:image-20230802112413-12.png||height="504" width="1011"]]
219 219  
220 -[[image:image-20230802112413-13.png]]
238 +[[image:image-20230802112413-13.png||height="331" width="978"]]
221 221  
222 222  
223 223  Below is the NB-IoT Product Table show the mapping.
... ... @@ -243,28 +243,44 @@
243 243  |(% 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" %)
244 244  
245 245  
264 +== 3.4 [[Datacake>>https://datacake.co/]] ==
246 246  
247 -== 3.4 Datacake ==
248 248  
267 +(% class="wikigeneratedid" %)
268 +Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
269 +
270 +
271 +(% class="wikigeneratedid" %)
272 +As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
273 +
274 +* (% 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.
275 +
276 +* (% 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.
277 +
278 +
249 249  === 3.4.1 Create device ===
250 250  
251 251  
252 -[[image:image-20230808162301-1.png]]
282 +(% style="color:blue" %)**Add Device**(%%) in DataCake.
253 253  
284 +[[image:image-20230808162301-1.png||height="453" width="952"]]
254 254  
255 -[[image:image-20230808162342-2.png]]
256 256  
287 +[[image:image-20230808162342-2.png||height="541" width="952"]]
257 257  
289 +
290 +(% style="color:blue" %)**Choose the correct model**(%%) from template.
291 +
258 258  [[image:image-20230808162421-3.png]]
259 259  
260 260  
261 -The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
295 +(% 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.
262 262  
263 -[[image:image-20230808163612-7.png]]
297 +[[image:image-20230808163612-7.png||height="549" width="952"]]
264 264  
265 265  [[image:image-20230808163035-5.png]]
266 266  
267 -[[image:image-20230808163049-6.png]]
301 +[[image:image-20230808163049-6.png||height="544" width="926"]]
268 268  
269 269  
270 270  === 3.4.2 Scan QR code to obtain data ===
... ... @@ -272,7 +272,7 @@
272 272  
273 273  Users can use their phones or computers to scan QR codes to obtain device data information.
274 274  
275 -[[image:image-20230808170051-8.png]]
309 +[[image:image-20230808170051-8.png||height="255" width="259"]]
276 276  
277 277  [[image:image-20230808170548-9.png]]
278 278  
... ... @@ -290,35 +290,62 @@
290 290  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
291 291  
292 292  
293 -[[image:image-20230802112413-29.png]]
327 +Take S31-NB UDP protocol as an example.
294 294  
329 +Dragino provides input flow examples for the sensors.
295 295  
296 -[[image:image-20230802112413-30.png]]
331 +User can download the required JSON file through Dragino Node-RED input flow template.
297 297  
333 +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]]
298 298  
299 -=== 3.5.2 Simulate Connection ===
335 +We can directly import the template.
300 300  
337 +The templates for S31-NB and NB95S31B are the same.
301 301  
302 -[[image:image-20230802112413-31.png]]
303 303  
340 +[[image:image-20230809173127-4.png]]
304 304  
305 -=== 3.5.3 Configure NB-IoT Sensors ===
306 306  
343 +Please select the NB95S31B template.
307 307  
308 -* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    **~/~/  Set to mqtt Server and  Payload**
345 +[[image:image-20230809173310-5.png||height="558" width="926"]]
309 309  
310 -* (% style="color:blue" %)**AT+CLIENT=any value**
347 +[[image:image-20230809173438-6.png]]
311 311  
312 -* (% style="color:blue" %)**AT+UNAME=any value**
349 +[[image:image-20230809173800-7.png]]
313 313  
314 -* (% style="color:blue" %)**AT+PWD=any value**
315 315  
316 -* (% style="color:blue" %)**AT+PUBTOPIC=any value**
352 +Successfully imported template.
317 317  
318 -* (% style="color:blue" %)**AT+SUBTOPIC=any value**
354 +[[image:image-20230809173835-8.png||height="515" width="860"]]
319 319  
320 320  
357 +Users can set UDP port.
321 321  
359 +[[image:image-20230809174053-9.png]]
360 +
361 +
362 +=== 3.5.2 Simulate Connection ===
363 +
364 +
365 +We have completed the configuration of UDP. We can try sending packets to node red.
366 +
367 +[[image:image-20230810083934-1.png]]
368 +
369 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
370 +
371 +
372 +=== 3.5.3 Configure NB-IoT Sensors ===
373 +
374 +
375 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
376 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
377 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
378 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
379 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
380 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
381 +
382 +
322 322  == 3.6 ThingsBoard.Cloud (via MQTT) ==
323 323  
324 324  === 3.6.1 Configure ThingsBoard ===
... ... @@ -328,7 +328,7 @@
328 328  
329 329  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
330 330  
331 -[[image:image-20230802112413-32.png]]
392 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
332 332  
333 333  
334 334  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -340,7 +340,7 @@
340 340  
341 341  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.
342 342  
343 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
404 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
344 344  
345 345  
346 346  (% style="color:blue" %)**Downlink Converter**
... ... @@ -347,7 +347,7 @@
347 347  
348 348  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
349 349  
350 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
411 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
351 351  
352 352  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
353 353  
... ... @@ -357,14 +357,14 @@
357 357  
358 358  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**;
359 359  
360 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
421 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
361 361  
362 362  
363 363  * The next steps is to add the recently created uplink and downlink converters;
364 364  
365 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
426 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
366 366  
367 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
428 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
368 368  
369 369  
370 370  (% style="color:blue" %)**Add a topic filter:**
... ... @@ -373,7 +373,7 @@
373 373  
374 374  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
375 375  
376 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
437 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
377 377  
378 378  
379 379  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -381,7 +381,7 @@
381 381  
382 382  [[image:image-20230802112413-39.png]]
383 383  
384 -[[image:image-20230802112413-40.png]]
445 +[[image:image-20230802112413-40.png||height="525" width="980"]]
385 385  
386 386  
387 387  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -401,15 +401,13 @@
401 401  
402 402  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
403 403  
404 -
405 -
406 406  Test Uplink by click the button for 1 second
407 407  
408 -[[image:image-20230802112413-41.png]]
467 +[[image:image-20230802112413-41.png||height="496" width="828"]]
409 409  
410 410  [[image:image-20230802112413-42.png]]
411 411  
412 -[[image:image-20230802112413-43.png]]
471 +[[image:image-20230802112413-43.png||height="407" width="825"]]
413 413  
414 414  
415 415  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -441,8 +441,6 @@
441 441  
442 442  * (% style="color:#037691" %)**Client ID: “Any value”**
443 443  
444 -
445 -
446 446  (% style="color:blue" %)**On the section User credentials, set the following information:**
447 447  
448 448  * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
... ... @@ -453,8 +453,6 @@
453 453  
454 454  * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
455 455  
456 -
457 -
458 458  (% style="color:blue" %)**AT command:**
459 459  
460 460  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -470,17 +470,18 @@
470 470  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
471 471  
472 472  
473 -
474 474  === 3.7.2 Simulate with MQTT.fx ===
475 475  
530 +
476 476  [[image:image-20230802112413-52.png]]
477 477  
478 478  
479 -[[image:image-20230808105300-2.png]]
534 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
480 480  
536 +
481 481  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
482 482  
483 -[[image:image-20230808105217-1.png]]
539 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
484 484  
485 485  [[image:image-20230808105329-3.png]]
486 486  
... ... @@ -488,12 +488,11 @@
488 488  === 3.7.3 tago data ===
489 489  
490 490  
491 -[[image:image-20230802112413-50.png]]
547 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
492 492  
493 493  [[image:image-20230802112413-51.png||height="184" width="696"]]
494 494  
495 495  
496 -
497 497  == 3.8 TCP Connection ==
498 498  
499 499  
... ... @@ -506,7 +506,6 @@
506 506  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
507 507  
508 508  
509 -
510 510  (% style="color:blue" %)**Sensor Console Output when Uplink:**
511 511  
512 512  [[image:image-20230807233631-1.png]]
... ... @@ -515,6 +515,3 @@
515 515  (% style="color:blue" %)**See result in TCP Server:**
516 516  
517 517  [[image:image-20230807233631-2.png]]
518 -
519 -
520 -
image-20230809174053-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.0 KB
Content
image-20230809180523-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +63.7 KB
Content
image-20230816201942-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content