Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 100.2
edited by Xiaoling
on 2023/08/15 17:03
Change comment: There is no comment for this version
To version 105.2
edited by Xiaoling
on 2023/11/06 16:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,9 @@
16 16  
17 17  = 2. Attach Network =
18 18  
19 +== 2.1 General Configure to attach network ==
19 19  
21 +
20 20  To attache NB-IoT sensors to NB-IoT Network, You need to:
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)
... ... @@ -41,6 +41,21 @@
41 41  
42 42  
43 43  
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 +
44 44  = 3. Configure to connect to different servers =
45 45  
46 46  == 3.1 General UDP Connection ==
... ... @@ -54,7 +54,7 @@
54 54  
55 55  We can use PC tool to simulate UDP connection to make sure server works ok.
56 56  
57 -[[image:image-20230802112413-1.png]]
74 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
58 58  
59 59  
60 60  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -104,7 +104,7 @@
104 104  
105 105  [[image:image-20230802112413-4.png]]
106 106  
107 -[[image:image-20230802112413-5.png]]
124 +[[image:image-20230802112413-5.png||height="530" width="987"]]
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]]
136 +[[image:image-20230802112413-6.png||height="336" width="925"]]
120 120  
121 121  [[image:image-20230802112413-7.png]]
122 122  
... ... @@ -161,7 +161,7 @@
161 161  
162 162  (% style="color:blue" %)**Result: **
163 163  
164 -[[image:image-20230802112413-11.png]]
181 +[[image:image-20230802112413-11.png||height="539" width="901"]]
165 165  
166 166  
167 167  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -188,7 +188,7 @@
188 188  ==== 3.3.3.2 Uplink Examples ====
189 189  
190 190  
191 -For S31-NB
208 +[[image:image-20230816201942-1.png]]
192 192  
193 193  For SE01-NB
194 194  
... ... @@ -219,9 +219,9 @@
219 219  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.
220 220  
221 221  
222 -[[image:image-20230802112413-12.png]]
239 +[[image:image-20230802112413-12.png||height="504" width="1011"]]
223 223  
224 -[[image:image-20230802112413-13.png]]
241 +[[image:image-20230802112413-13.png||height="331" width="978"]]
225 225  
226 226  
227 227  Below is the NB-IoT Product Table show the mapping.
... ... @@ -256,7 +256,7 @@
256 256  
257 257  
258 258  (% class="wikigeneratedid" %)
259 -As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
276 +As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
260 260  
261 261  * (% 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.
262 262  
... ... @@ -267,26 +267,26 @@
267 267  === 3.4.1 Create device ===
268 268  
269 269  
270 -**Add Device** in DataCake.
287 +(% style="color:blue" %)**Add Device**(%%) in DataCake.
271 271  
272 -[[image:image-20230808162301-1.png]]
289 +[[image:image-20230808162301-1.png||height="453" width="952"]]
273 273  
274 274  
275 -[[image:image-20230808162342-2.png]]
292 +[[image:image-20230808162342-2.png||height="541" width="952"]]
276 276  
277 277  
278 -**Choose the correct model** from template.
295 +(% style="color:blue" %)**Choose the correct model**(%%) from template.
279 279  
280 280  [[image:image-20230808162421-3.png]]
281 281  
282 282  
283 -**Fill Device ID**. The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
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.
284 284  
285 -[[image:image-20230808163612-7.png]]
302 +[[image:image-20230808163612-7.png||height="549" width="952"]]
286 286  
287 287  [[image:image-20230808163035-5.png]]
288 288  
289 -[[image:image-20230808163049-6.png]]
306 +[[image:image-20230808163049-6.png||height="544" width="926"]]
290 290  
291 291  
292 292  === 3.4.2 Scan QR code to obtain data ===
... ... @@ -330,7 +330,7 @@
330 330  
331 331  Please select the NB95S31B template.
332 332  
333 -[[image:image-20230809173310-5.png]]
350 +[[image:image-20230809173310-5.png||height="558" width="926"]]
334 334  
335 335  [[image:image-20230809173438-6.png]]
336 336  
... ... @@ -339,7 +339,7 @@
339 339  
340 340  Successfully imported template.
341 341  
342 -[[image:image-20230809173835-8.png]]
359 +[[image:image-20230809173835-8.png||height="515" width="860"]]
343 343  
344 344  
345 345  Users can set UDP port.
... ... @@ -354,8 +354,9 @@
354 354  
355 355  [[image:image-20230810083934-1.png]]
356 356  
357 -[[image:image-20230810084048-2.png]]
374 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
358 358  
376 +
359 359  === 3.5.3 Configure NB-IoT Sensors ===
360 360  
361 361  
... ... @@ -363,6 +363,8 @@
363 363  
364 364  * (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
365 365  
384 +
385 +
366 366  == 3.6 ThingsBoard.Cloud (via MQTT) ==
367 367  
368 368  === 3.6.1 Configure ThingsBoard ===
... ... @@ -372,7 +372,7 @@
372 372  
373 373  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
374 374  
375 -[[image:image-20230802112413-32.png]]
395 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
376 376  
377 377  
378 378  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -384,7 +384,7 @@
384 384  
385 385  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.
386 386  
387 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
407 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
388 388  
389 389  
390 390  (% style="color:blue" %)**Downlink Converter**
... ... @@ -391,7 +391,7 @@
391 391  
392 392  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
393 393  
394 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
414 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
395 395  
396 396  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
397 397  
... ... @@ -401,14 +401,14 @@
401 401  
402 402  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**;
403 403  
404 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
424 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
405 405  
406 406  
407 407  * The next steps is to add the recently created uplink and downlink converters;
408 408  
409 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
429 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
410 410  
411 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
431 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
412 412  
413 413  
414 414  (% style="color:blue" %)**Add a topic filter:**
... ... @@ -417,7 +417,7 @@
417 417  
418 418  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
419 419  
420 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
440 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
421 421  
422 422  
423 423  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -425,7 +425,7 @@
425 425  
426 426  [[image:image-20230802112413-39.png]]
427 427  
428 -[[image:image-20230802112413-40.png]]
448 +[[image:image-20230802112413-40.png||height="525" width="980"]]
429 429  
430 430  
431 431  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -447,11 +447,11 @@
447 447  
448 448  Test Uplink by click the button for 1 second
449 449  
450 -[[image:image-20230802112413-41.png]]
470 +[[image:image-20230802112413-41.png||height="496" width="828"]]
451 451  
452 452  [[image:image-20230802112413-42.png]]
453 453  
454 -[[image:image-20230802112413-43.png]]
474 +[[image:image-20230802112413-43.png||height="407" width="825"]]
455 455  
456 456  
457 457  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -507,6 +507,8 @@
507 507  
508 508  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
509 509  
530 +
531 +
510 510  === 3.7.2 Simulate with MQTT.fx ===
511 511  
512 512  
... ... @@ -513,12 +513,12 @@
513 513  [[image:image-20230802112413-52.png]]
514 514  
515 515  
516 -[[image:image-20230808105300-2.png]]
538 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
517 517  
518 518  
519 519  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
520 520  
521 -[[image:image-20230808105217-1.png]]
543 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
522 522  
523 523  [[image:image-20230808105329-3.png]]
524 524  
... ... @@ -526,7 +526,7 @@
526 526  === 3.7.3 tago data ===
527 527  
528 528  
529 -[[image:image-20230802112413-50.png]]
551 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
530 530  
531 531  [[image:image-20230802112413-51.png||height="184" width="696"]]
532 532  
... ... @@ -542,6 +542,8 @@
542 542  
543 543  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
544 544  
567 +
568 +
545 545  (% style="color:blue" %)**Sensor Console Output when Uplink:**
546 546  
547 547  [[image:image-20230807233631-1.png]]
... ... @@ -550,3 +550,4 @@
550 550  (% style="color:blue" %)**See result in TCP Server:**
551 551  
552 552  [[image:image-20230807233631-2.png]]
577 +
image-20230816201942-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content