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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Saxer
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  
... ... @@ -42,21 +42,7 @@
42 42  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
43 43  
44 44  
45 -== 2.2 Speed Up Network Attach time ==
46 46  
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 -
60 60  = 3. Configure to connect to different servers =
61 61  
62 62  == 3.1 General UDP Connection ==
... ... @@ -70,7 +70,7 @@
70 70  
71 71  We can use PC tool to simulate UDP connection to make sure server works ok.
72 72  
73 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
53 +[[image:image-20230802112413-1.png]]
74 74  
75 75  
76 76  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -120,7 +120,7 @@
120 120  
121 121  [[image:image-20230802112413-4.png]]
122 122  
123 -[[image:image-20230802112413-5.png||height="530" width="987"]]
103 +[[image:image-20230802112413-5.png]]
124 124  
125 125  (% 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.**
126 126  
... ... @@ -132,7 +132,7 @@
132 132  
133 133  [[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.
134 134  
135 -[[image:image-20230802112413-6.png||height="336" width="925"]]
115 +[[image:image-20230802112413-6.png]]
136 136  
137 137  [[image:image-20230802112413-7.png]]
138 138  
... ... @@ -157,6 +157,7 @@
157 157  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
158 158  
159 159  
140 +
160 160  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
161 161  
162 162  
... ... @@ -176,7 +176,7 @@
176 176  
177 177  (% style="color:blue" %)**Result: **
178 178  
179 -[[image:image-20230802112413-11.png||height="539" width="901"]]
160 +[[image:image-20230802112413-11.png]]
180 180  
181 181  
182 182  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -186,7 +186,7 @@
186 186  
187 187  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
188 188  
189 -* (% 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**
190 190  
191 191  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
192 192  
... ... @@ -199,10 +199,11 @@
199 199  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
200 200  
201 201  
183 +
202 202  ==== 3.3.3.2 Uplink Examples ====
203 203  
204 204  
205 -[[image:image-20230816201942-1.png]]
187 +For S31-NB
206 206  
207 207  For SE01-NB
208 208  
... ... @@ -233,9 +233,9 @@
233 233  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.
234 234  
235 235  
236 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
218 +[[image:image-20230802112413-12.png]]
237 237  
238 -[[image:image-20230802112413-13.png||height="331" width="978"]]
220 +[[image:image-20230802112413-13.png]]
239 239  
240 240  
241 241  Below is the NB-IoT Product Table show the mapping.
... ... @@ -261,44 +261,28 @@
261 261  |(% 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" %)
262 262  
263 263  
264 -== 3.4 [[Datacake>>https://datacake.co/]] ==
265 265  
247 +== 3.4 Datacake ==
266 266  
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 -
279 279  === 3.4.1 Create device ===
280 280  
281 281  
282 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
252 +[[image:image-20230808162301-1.png]]
283 283  
284 -[[image:image-20230808162301-1.png||height="453" width="952"]]
285 285  
255 +[[image:image-20230808162342-2.png]]
286 286  
287 -[[image:image-20230808162342-2.png||height="541" width="952"]]
288 288  
289 -
290 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
291 -
292 292  [[image:image-20230808162421-3.png]]
293 293  
294 294  
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.
261 +The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
296 296  
297 -[[image:image-20230808163612-7.png||height="549" width="952"]]
263 +[[image:image-20230808163612-7.png]]
298 298  
299 299  [[image:image-20230808163035-5.png]]
300 300  
301 -[[image:image-20230808163049-6.png||height="544" width="926"]]
267 +[[image:image-20230808163049-6.png]]
302 302  
303 303  
304 304  === 3.4.2 Scan QR code to obtain data ===
... ... @@ -306,7 +306,7 @@
306 306  
307 307  Users can use their phones or computers to scan QR codes to obtain device data information.
308 308  
309 -[[image:image-20230808170051-8.png||height="255" width="259"]]
275 +[[image:image-20230808170051-8.png]]
310 310  
311 311  [[image:image-20230808170548-9.png]]
312 312  
... ... @@ -324,62 +324,35 @@
324 324  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
325 325  
326 326  
327 -Take S31-NB UDP protocol as an example.
293 +[[image:image-20230802112413-29.png]]
328 328  
329 -Dragino provides input flow examples for the sensors.
330 330  
331 -User can download the required JSON file through Dragino Node-RED input flow template.
296 +[[image:image-20230802112413-30.png]]
332 332  
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]]
334 334  
335 -We can directly import the template.
299 +=== 3.5.2 Simulate Connection ===
336 336  
337 -The templates for S31-NB and NB95S31B are the same.
338 338  
302 +[[image:image-20230802112413-31.png]]
339 339  
340 -[[image:image-20230809173127-4.png]]
341 341  
305 +=== 3.5.3 Configure NB-IoT Sensors ===
342 342  
343 -Please select the NB95S31B template.
344 344  
345 -[[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**
346 346  
347 -[[image:image-20230809173438-6.png]]
310 +* (% style="color:blue" %)**AT+CLIENT=any value**
348 348  
349 -[[image:image-20230809173800-7.png]]
312 +* (% style="color:blue" %)**AT+UNAME=any value**
350 350  
314 +* (% style="color:blue" %)**AT+PWD=any value**
351 351  
352 -Successfully imported template.
316 +* (% style="color:blue" %)**AT+PUBTOPIC=any value**
353 353  
354 -[[image:image-20230809173835-8.png||height="515" width="860"]]
318 +* (% style="color:blue" %)**AT+SUBTOPIC=any value**
355 355  
356 356  
357 -Users can set UDP port.
358 358  
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 -
383 383  == 3.6 ThingsBoard.Cloud (via MQTT) ==
384 384  
385 385  === 3.6.1 Configure ThingsBoard ===
... ... @@ -389,7 +389,7 @@
389 389  
390 390  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
391 391  
392 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
331 +[[image:image-20230802112413-32.png]]
393 393  
394 394  
395 395  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -401,7 +401,7 @@
401 401  
402 402  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.
403 403  
404 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
343 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
405 405  
406 406  
407 407  (% style="color:blue" %)**Downlink Converter**
... ... @@ -408,7 +408,7 @@
408 408  
409 409  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
410 410  
411 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
350 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
412 412  
413 413  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
414 414  
... ... @@ -418,14 +418,14 @@
418 418  
419 419  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**;
420 420  
421 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
360 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
422 422  
423 423  
424 424  * The next steps is to add the recently created uplink and downlink converters;
425 425  
426 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
365 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
427 427  
428 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
367 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
429 429  
430 430  
431 431  (% style="color:blue" %)**Add a topic filter:**
... ... @@ -434,7 +434,7 @@
434 434  
435 435  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
436 436  
437 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
376 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
438 438  
439 439  
440 440  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -442,7 +442,7 @@
442 442  
443 443  [[image:image-20230802112413-39.png]]
444 444  
445 -[[image:image-20230802112413-40.png||height="525" width="980"]]
384 +[[image:image-20230802112413-40.png]]
446 446  
447 447  
448 448  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -462,13 +462,15 @@
462 462  
463 463  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
464 464  
404 +
405 +
465 465  Test Uplink by click the button for 1 second
466 466  
467 -[[image:image-20230802112413-41.png||height="496" width="828"]]
408 +[[image:image-20230802112413-41.png]]
468 468  
469 469  [[image:image-20230802112413-42.png]]
470 470  
471 -[[image:image-20230802112413-43.png||height="407" width="825"]]
412 +[[image:image-20230802112413-43.png]]
472 472  
473 473  
474 474  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -500,6 +500,8 @@
500 500  
501 501  * (% style="color:#037691" %)**Client ID: “Any value”**
502 502  
444 +
445 +
503 503  (% style="color:blue" %)**On the section User credentials, set the following information:**
504 504  
505 505  * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
... ... @@ -510,6 +510,8 @@
510 510  
511 511  * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
512 512  
456 +
457 +
513 513  (% style="color:blue" %)**AT command:**
514 514  
515 515  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -525,18 +525,17 @@
525 525  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
526 526  
527 527  
473 +
528 528  === 3.7.2 Simulate with MQTT.fx ===
529 529  
530 -
531 531  [[image:image-20230802112413-52.png]]
532 532  
533 533  
534 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
479 +[[image:image-20230808105300-2.png]]
535 535  
536 -
537 537  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
538 538  
539 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
483 +[[image:image-20230808105217-1.png]]
540 540  
541 541  [[image:image-20230808105329-3.png]]
542 542  
... ... @@ -544,11 +544,12 @@
544 544  === 3.7.3 tago data ===
545 545  
546 546  
547 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
491 +[[image:image-20230802112413-50.png]]
548 548  
549 549  [[image:image-20230802112413-51.png||height="184" width="696"]]
550 550  
551 551  
496 +
552 552  == 3.8 TCP Connection ==
553 553  
554 554  
... ... @@ -561,6 +561,7 @@
561 561  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
562 562  
563 563  
509 +
564 564  (% style="color:blue" %)**Sensor Console Output when Uplink:**
565 565  
566 566  [[image:image-20230807233631-1.png]]
... ... @@ -569,3 +569,6 @@
569 569  (% style="color:blue" %)**See result in TCP Server:**
570 570  
571 571  [[image:image-20230807233631-2.png]]
518 +
519 +
520 +
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