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
on 2023/11/25 17:22
Change comment:
There is no comment for this version
To version 103.1
edited by Edwin Chen
on 2023/10/02 18:27
on 2023/10/02 18:27
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Saxer1 +XWiki.Edwin - Content
-
... ... @@ -18,7 +18,6 @@ 18 18 19 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) ... ... @@ -41,22 +41,12 @@ 41 41 |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %) 42 42 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %) 43 43 44 - 45 45 == 2.2 Speed Up Network Attach time == 46 46 47 - 48 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 49 50 -(% style="color:#037691" %)**AT+QBAND? ** (%%) ~/~/ Check what is the current used frequency band 51 51 52 -(% style="color:#037691" %)**AT+QBAND=1,4 ** (%%) ~/~/ Set to use 1 frequency band. Band4 53 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"]]62 +[[image:image-20230802112413-1.png]] 74 74 75 75 76 76 === 3.1.2 Configure NB-IoT Sensor === ... ... @@ -201,7 +201,6 @@ 201 201 202 202 ==== 3.3.3.2 Uplink Examples ==== 203 203 204 - 205 205 [[image:image-20230816201942-1.png]] 206 206 207 207 For SE01-NB ... ... @@ -281,10 +281,10 @@ 281 281 282 282 (% style="color:blue" %)**Add Device**(%%) in DataCake. 283 283 284 -[[image:image-20230808162301-1.png||height="4 53" width="952"]]272 +[[image:image-20230808162301-1.png||height="473" width="994"]] 285 285 286 286 287 -[[image:image-20230808162342-2.png ||height="541" width="952"]]275 +[[image:image-20230808162342-2.png]] 288 288 289 289 290 290 (% style="color:blue" %)**Choose the correct model**(%%) from template. ... ... @@ -294,11 +294,11 @@ 294 294 295 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. 296 296 297 -[[image:image-20230808163612-7.png ||height="549" width="952"]]285 +[[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"]]289 +[[image:image-20230808163049-6.png]] 302 302 303 303 304 304 === 3.4.2 Scan QR code to obtain data === ... ... @@ -342,7 +342,7 @@ 342 342 343 343 Please select the NB95S31B template. 344 344 345 -[[image:image-20230809173310-5.png ||height="558" width="926"]]333 +[[image:image-20230809173310-5.png]] 346 346 347 347 [[image:image-20230809173438-6.png]] 348 348 ... ... @@ -351,7 +351,7 @@ 351 351 352 352 Successfully imported template. 353 353 354 -[[image:image-20230809173835-8.png ||height="515" width="860"]]342 +[[image:image-20230809173835-8.png]] 355 355 356 356 357 357 Users can set UDP port. ... ... @@ -366,20 +366,16 @@ 366 366 367 367 [[image:image-20230810083934-1.png]] 368 368 369 -[[image:image-20230810084048-2.png ||height="535" width="1052"]]357 +[[image:image-20230810084048-2.png]] 370 370 371 - 372 372 === 3.5.3 Configure NB-IoT Sensors === 373 373 374 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”** 362 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format) **(%%)** **~/~/ Set to UDP Server and Payload 381 381 364 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port **(%%)** **~/~/ Set Server IP and port 382 382 366 + 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"]]376 +[[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"]]388 +[[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"]]395 +[[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"]]405 +[[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"]]410 +[[image:image-20230802112413-36.png||height="736" width="1308"]] 427 427 428 -[[image:image-20230802112413-37.png||height="5 98" width="1064"]]412 +[[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"]]421 +[[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"]]429 +[[image:image-20230802112413-40.png]] 446 446 447 447 448 448 === 3.6.3 Configure NB-IoT Sensor === ... ... @@ -464,11 +464,11 @@ 464 464 465 465 Test Uplink by click the button for 1 second 466 466 467 -[[image:image-20230802112413-41.png ||height="496" width="828"]]451 +[[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"]]455 +[[image:image-20230802112413-43.png]] 472 472 473 473 474 474 == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == ... ... @@ -531,12 +531,12 @@ 531 531 [[image:image-20230802112413-52.png]] 532 532 533 533 534 -[[image:image-20230808105300-2.png ||height="553" width="1026"]]518 +[[image:image-20230808105300-2.png]] 535 535 536 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"]]523 +[[image:image-20230808105217-1.png]] 540 540 541 541 [[image:image-20230808105329-3.png]] 542 542 ... ... @@ -544,7 +544,7 @@ 544 544 === 3.7.3 tago data === 545 545 546 546 547 -[[image:image-20230802112413-50.png ||height="242" width="1037"]]531 +[[image:image-20230802112413-50.png]] 548 548 549 549 [[image:image-20230802112413-51.png||height="184" width="696"]] 550 550 ... ... @@ -560,7 +560,6 @@ 560 560 561 561 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port 562 562 563 - 564 564 (% style="color:blue" %)**Sensor Console Output when Uplink:** 565 565 566 566 [[image:image-20230807233631-1.png]]