Last modified by Mengting Qiu on 2025/07/03 18:55
From version 104.3
edited by Xiaoling
on 2023/10/07 10:15
on 2023/10/07 10:15
Change comment:
There is no comment for this version
To version 107.1
edited by Edwin Chen
on 2023/12/30 17:09
on 2023/12/30 17:09
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. Xiaoling1 +XWiki.Edwin - 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,20 +40,24 @@ 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 43 -(% class="wikigeneratedid" %) 44 -== == 45 - 46 46 == 2.2 Speed Up Network Attach time == 47 47 48 48 49 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 50 51 -(% style="color:#037691" %)**AT+QBAND? ** 49 +(% style="color:#037691" %)**AT+QBAND? **(%%) ~/~/ Check what is the current used frequency band 52 52 53 -(% style="color:#037691" %)**AT+QBAND=1,4 ** 51 +(% style="color:#037691" %)**AT+QBAND=1,4 **(%%) ~/~/ Set to use 1 frequency band. Band4 54 54 55 -(% style="color:#037691" %)**AT+QBAND=2,8,20** 53 +(% style="color:#037691" %)**AT+QBAND=2,8,20 **(%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20 56 56 55 + 56 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used. 57 + 58 + 59 +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/]]** 60 + 61 + 57 57 = 3. Configure to connect to different servers = 58 58 59 59 == 3.1 General UDP Connection == ... ... @@ -67,7 +67,7 @@ 67 67 68 68 We can use PC tool to simulate UDP connection to make sure server works ok. 69 69 70 -[[image:image-20230802112413-1.png]] 75 +[[image:image-20230802112413-1.png||height="468" width="1024"]] 71 71 72 72 73 73 === 3.1.2 Configure NB-IoT Sensor === ... ... @@ -196,6 +196,7 @@ 196 196 197 197 ==== 3.3.3.2 Uplink Examples ==== 198 198 204 + 199 199 [[image:image-20230816201942-1.png]] 200 200 201 201 For SE01-NB ... ... @@ -273,10 +273,10 @@ 273 273 274 274 (% style="color:blue" %)**Add Device**(%%) in DataCake. 275 275 276 -[[image:image-20230808162301-1.png||height="4 73" width="994"]]282 +[[image:image-20230808162301-1.png||height="453" width="952"]] 277 277 278 278 279 -[[image:image-20230808162342-2.png]] 285 +[[image:image-20230808162342-2.png||height="541" width="952"]] 280 280 281 281 282 282 (% style="color:blue" %)**Choose the correct model**(%%) from template. ... ... @@ -286,11 +286,11 @@ 286 286 287 287 (% 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. 288 288 289 -[[image:image-20230808163612-7.png]] 295 +[[image:image-20230808163612-7.png||height="549" width="952"]] 290 290 291 291 [[image:image-20230808163035-5.png]] 292 292 293 -[[image:image-20230808163049-6.png]] 299 +[[image:image-20230808163049-6.png||height="544" width="926"]] 294 294 295 295 296 296 === 3.4.2 Scan QR code to obtain data === ... ... @@ -334,7 +334,7 @@ 334 334 335 335 Please select the NB95S31B template. 336 336 337 -[[image:image-20230809173310-5.png]] 343 +[[image:image-20230809173310-5.png||height="558" width="926"]] 338 338 339 339 [[image:image-20230809173438-6.png]] 340 340 ... ... @@ -343,7 +343,7 @@ 343 343 344 344 Successfully imported template. 345 345 346 -[[image:image-20230809173835-8.png]] 352 +[[image:image-20230809173835-8.png||height="515" width="860"]] 347 347 348 348 349 349 Users can set UDP port. ... ... @@ -358,15 +358,19 @@ 358 358 359 359 [[image:image-20230810083934-1.png]] 360 360 361 -[[image:image-20230810084048-2.png]] 367 +[[image:image-20230810084048-2.png||height="535" width="1052"]] 362 362 369 + 363 363 === 3.5.3 Configure NB-IoT Sensors === 364 364 365 365 366 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format) **(%%)** **~/~/ Set to UDP Server and Payload 373 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format** 374 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined** 375 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined** 376 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined** 377 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 378 +* (% style="color:#037691" %)**AT+PWD=“Your device token”** 367 367 368 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port **(%%)** **~/~/ Set Server IP and port 369 - 370 370 == 3.6 ThingsBoard.Cloud (via MQTT) == 371 371 372 372 === 3.6.1 Configure ThingsBoard === ... ... @@ -376,7 +376,7 @@ 376 376 377 377 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection. 378 378 379 -[[image:image-20230802112413-32.png]] 389 +[[image:image-20230802112413-32.png||height="583" width="1066"]] 380 380 381 381 382 382 ==== 3.6.1.2 Create Uplink & Downlink Converter ==== ... ... @@ -388,7 +388,7 @@ 388 388 389 389 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. 390 390 391 -[[image:image-20230802112413-33.png||height="7 32" width="1302"]]401 +[[image:image-20230802112413-33.png||height="597" width="1061"]] 392 392 393 393 394 394 (% style="color:blue" %)**Downlink Converter** ... ... @@ -395,7 +395,7 @@ 395 395 396 396 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke 397 397 398 -[[image:image-20230802112413-34.png||height=" 734" width="1305"]]408 +[[image:image-20230802112413-34.png||height="598" width="1063"]] 399 399 400 400 (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.** 401 401 ... ... @@ -405,14 +405,14 @@ 405 405 406 406 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**; 407 407 408 -[[image:image-20230802112413-35.png||height="7 38" width="1312"]]418 +[[image:image-20230802112413-35.png||height="597" width="1062"]] 409 409 410 410 411 411 * The next steps is to add the recently created uplink and downlink converters; 412 412 413 -[[image:image-20230802112413-36.png||height=" 736" width="1308"]]423 +[[image:image-20230802112413-36.png||height="598" width="1062"]] 414 414 415 -[[image:image-20230802112413-37.png||height=" 735" width="1307"]]425 +[[image:image-20230802112413-37.png||height="598" width="1064"]] 416 416 417 417 418 418 (% style="color:blue" %)**Add a topic filter:** ... ... @@ -421,7 +421,7 @@ 421 421 422 422 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default; 423 423 424 -[[image:image-20230802112413-38.png||height=" 731" width="1300"]]434 +[[image:image-20230802112413-38.png||height="598" width="1064"]] 425 425 426 426 427 427 === 3.6.2 Simulate with MQTT.fx === ... ... @@ -429,7 +429,7 @@ 429 429 430 430 [[image:image-20230802112413-39.png]] 431 431 432 -[[image:image-20230802112413-40.png]] 442 +[[image:image-20230802112413-40.png||height="525" width="980"]] 433 433 434 434 435 435 === 3.6.3 Configure NB-IoT Sensor === ... ... @@ -451,11 +451,11 @@ 451 451 452 452 Test Uplink by click the button for 1 second 453 453 454 -[[image:image-20230802112413-41.png]] 464 +[[image:image-20230802112413-41.png||height="496" width="828"]] 455 455 456 456 [[image:image-20230802112413-42.png]] 457 457 458 -[[image:image-20230802112413-43.png]] 468 +[[image:image-20230802112413-43.png||height="407" width="825"]] 459 459 460 460 461 461 == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == ... ... @@ -517,12 +517,12 @@ 517 517 [[image:image-20230802112413-52.png]] 518 518 519 519 520 -[[image:image-20230808105300-2.png]] 530 +[[image:image-20230808105300-2.png||height="553" width="1026"]] 521 521 522 522 523 523 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**. 524 524 525 -[[image:image-20230808105217-1.png]] 535 +[[image:image-20230808105217-1.png||height="556" width="1031"]] 526 526 527 527 [[image:image-20230808105329-3.png]] 528 528 ... ... @@ -530,7 +530,7 @@ 530 530 === 3.7.3 tago data === 531 531 532 532 533 -[[image:image-20230802112413-50.png]] 543 +[[image:image-20230802112413-50.png||height="242" width="1037"]] 534 534 535 535 [[image:image-20230802112413-51.png||height="184" width="696"]] 536 536