Last modified by Mengting Qiu on 2025/07/03 18:55

From version 103.1
edited by Edwin Chen
on 2023/10/02 18:27
Change comment: There is no comment for this version
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.Edwin
1 +XWiki.Saxer
Content
... ... @@ -18,6 +18,7 @@
18 18  
19 19  == 2.1 General Configure to attach network ==
20 20  
21 +
21 21  To attache NB-IoT sensors to NB-IoT Network, You need to:
22 22  
23 23  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
... ... @@ -40,12 +40,22 @@
40 40  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
41 41  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
42 42  
44 +
43 43  == 2.2 Speed Up Network Attach time ==
44 44  
47 +
45 45  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.
46 46  
50 +(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
47 47  
52 +(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
48 48  
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 +
49 49  = 3. Configure to connect to different servers =
50 50  
51 51  == 3.1 General UDP Connection ==
... ... @@ -59,7 +59,7 @@
59 59  
60 60  We can use PC tool to simulate UDP connection to make sure server works ok.
61 61  
62 -[[image:image-20230802112413-1.png]]
73 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
63 63  
64 64  
65 65  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -190,6 +190,7 @@
190 190  
191 191  ==== 3.3.3.2 Uplink Examples ====
192 192  
204 +
193 193  [[image:image-20230816201942-1.png]]
194 194  
195 195  For SE01-NB
... ... @@ -269,10 +269,10 @@
269 269  
270 270  (% style="color:blue" %)**Add Device**(%%) in DataCake.
271 271  
272 -[[image:image-20230808162301-1.png||height="473" width="994"]]
284 +[[image:image-20230808162301-1.png||height="453" width="952"]]
273 273  
274 274  
275 -[[image:image-20230808162342-2.png]]
287 +[[image:image-20230808162342-2.png||height="541" width="952"]]
276 276  
277 277  
278 278  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -282,11 +282,11 @@
282 282  
283 283  (% 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]]
297 +[[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]]
301 +[[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]]
345 +[[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]]
354 +[[image:image-20230809173835-8.png||height="515" width="860"]]
343 343  
344 344  
345 345  Users can set UDP port.
... ... @@ -354,16 +354,20 @@
354 354  
355 355  [[image:image-20230810083934-1.png]]
356 356  
357 -[[image:image-20230810084048-2.png]]
369 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
358 358  
371 +
359 359  === 3.5.3 Configure NB-IoT Sensors ===
360 360  
361 361  
362 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
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”**
363 363  
364 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
365 365  
366 -
367 367  == 3.6 ThingsBoard.Cloud (via MQTT) ==
368 368  
369 369  === 3.6.1 Configure ThingsBoard ===
... ... @@ -373,7 +373,7 @@
373 373  
374 374  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
375 375  
376 -[[image:image-20230802112413-32.png]]
392 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
377 377  
378 378  
379 379  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -385,7 +385,7 @@
385 385  
386 386  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.
387 387  
388 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
404 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
389 389  
390 390  
391 391  (% style="color:blue" %)**Downlink Converter**
... ... @@ -392,7 +392,7 @@
392 392  
393 393  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
394 394  
395 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
411 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
396 396  
397 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.**
398 398  
... ... @@ -402,14 +402,14 @@
402 402  
403 403  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**;
404 404  
405 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
421 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
406 406  
407 407  
408 408  * The next steps is to add the recently created uplink and downlink converters;
409 409  
410 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
426 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
411 411  
412 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
428 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
413 413  
414 414  
415 415  (% style="color:blue" %)**Add a topic filter:**
... ... @@ -418,7 +418,7 @@
418 418  
419 419  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
420 420  
421 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
437 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
422 422  
423 423  
424 424  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -426,7 +426,7 @@
426 426  
427 427  [[image:image-20230802112413-39.png]]
428 428  
429 -[[image:image-20230802112413-40.png]]
445 +[[image:image-20230802112413-40.png||height="525" width="980"]]
430 430  
431 431  
432 432  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -448,11 +448,11 @@
448 448  
449 449  Test Uplink by click the button for 1 second
450 450  
451 -[[image:image-20230802112413-41.png]]
467 +[[image:image-20230802112413-41.png||height="496" width="828"]]
452 452  
453 453  [[image:image-20230802112413-42.png]]
454 454  
455 -[[image:image-20230802112413-43.png]]
471 +[[image:image-20230802112413-43.png||height="407" width="825"]]
456 456  
457 457  
458 458  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -515,12 +515,12 @@
515 515  [[image:image-20230802112413-52.png]]
516 516  
517 517  
518 -[[image:image-20230808105300-2.png]]
534 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
519 519  
520 520  
521 521  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
522 522  
523 -[[image:image-20230808105217-1.png]]
539 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
524 524  
525 525  [[image:image-20230808105329-3.png]]
526 526  
... ... @@ -528,7 +528,7 @@
528 528  === 3.7.3 tago data ===
529 529  
530 530  
531 -[[image:image-20230802112413-50.png]]
547 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
532 532  
533 533  [[image:image-20230802112413-51.png||height="184" width="696"]]
534 534  
... ... @@ -544,6 +544,7 @@
544 544  
545 545  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
546 546  
563 +
547 547  (% style="color:blue" %)**Sensor Console Output when Uplink:**
548 548  
549 549  [[image:image-20230807233631-1.png]]