Last modified by Mengting Qiu on 2025/03/08 11:33
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
-
... ... @@ -13,19 +13,28 @@ 13 13 = 2. Network Connection = 14 14 15 15 16 -The -NBand-NS modelssupport (%style="color:blue"%)**LTE CatNB2**(%%), with belowfrequency band: multiple frequency bandsof (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Makesure youusea theNB-IoT SIM card.16 +To attache NB-IoT sensors to NB-IoT Network, You need to: 17 17 18 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 19 -|(% style="background-color:#4f81bd; color:white" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white" %)**APN**|(% style="background-color:#4f81bd; color:white" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white" %)**Comments** 20 -|1NCE| | | 21 -|China Mobile| | | 18 +1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone) 19 +1. Insert the SIM card to Sensor 20 +1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor 22 22 22 +After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network . 23 23 24 +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. 24 24 25 -== 2.1 1NCE SIM Card. == 26 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %) 27 +|(% style="background-color:#4f81bd; color:white; width:114px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:154px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments** 28 +|(% style="width:114px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:154px" %)iot.1nce.net|(% style="width:474px" %)((( 29 +**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]** 26 26 31 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands 32 +)))|(% style="width:135px" %) 33 +|(% style="width:114px" %)China Mobile|(% style="width:154px" %) |(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %) 34 +|(% style="width:114px" %)China Telecom|(% style="width:154px" %) |(% style="width:474px" %)China Mainland|(% style="width:135px" %) 27 27 28 28 37 + 29 29 = 3. Configure to connect to different servers = 30 30 31 31 == 3.1 General UDP Connection == ... ... @@ -126,7 +126,6 @@ 126 126 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 127 127 128 128 129 - 130 130 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 131 131 132 132 ... ... @@ -134,6 +134,7 @@ 134 134 135 135 [[image:image-20230802112413-10.png]] 136 136 145 + 137 137 (% style="color:blue" %)**In MQTT.fx, we can publish below info:** 138 138 139 139 * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish ... ... @@ -230,6 +230,7 @@ 230 230 |(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod5|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %) 231 231 |(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod6|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)count|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:148px" %) |(% colspan="1" style="width:164px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %) 232 232 242 + 233 233 == 3.4 Datacake == 234 234 235 235 === 3.4.1 Define Product === ... ... @@ -239,7 +239,7 @@ 239 239 240 240 By chosing to add the device under a (% style="color:blue" %)**"New Product"**(%%) you are required to give a name for this product. You can name it something like (% style="color:blue" %)**"My First MQTT Product"**. 241 241 242 -[[image:image-20230802112413-14.png]] 252 +[[image:image-20230802112413-14.png||height="1095" width="1302"]] 243 243 244 244 245 245 === 3.4.2 Create Device === ... ... @@ -285,15 +285,17 @@ 285 285 286 286 [[image:image-20230802112413-20.png]] 287 287 298 + 288 288 (% style="color:blue" %)**MQTT Client-ID** 289 289 290 -The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this specification blank. Your client then creates a randomly generated ID. 301 +The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this 302 +specification blank. Your client then creates a randomly generated ID. 291 291 292 -(% style="color:blue" %)**AT+CLIENT=“Any value”** 304 +* (% style="color:blue" %)**AT+CLIENT=“Any value”** 293 293 294 -(% style="color:blue" %)**AT+UNAME=Token** 306 +* (% style="color:blue" %)**AT+UNAME=Token** 295 295 296 -(% style="color:blue" %)**AT+PWD=Token** 308 +* (% style="color:blue" %)**AT+PWD=Token** 297 297 298 298 [[image:image-20230802112413-21.png]] 299 299 ... ... @@ -350,7 +350,7 @@ 350 350 351 351 == 3.5 Node-Red (via MQTT) == 352 352 353 -=== 3.5.1 Configure Node-Red === 365 +=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] === 354 354 355 355 356 356 [[image:image-20230802112413-29.png]] ... ... @@ -381,7 +381,6 @@ 381 381 * (% style="color:blue" %)**AT+SUBTOPIC=any value** 382 382 383 383 384 - 385 385 == 3.6 ThingsBoard.Cloud (via MQTT) == 386 386 387 387 === 3.6.1 Configure ThingsBoard === ... ... @@ -401,7 +401,7 @@ 401 401 402 402 The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported. 403 403 404 -To create an uplink converter go to the **Integrations center** -> **Data converters** page and click **“plus”** 415 +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. 405 405 406 406 [[image:image-20230802112413-33.png||height="732" width="1302"]] 407 407 ... ... @@ -418,7 +418,7 @@ 418 418 ==== 3.6.1.3 MQTT Integration Setup ==== 419 419 420 420 421 -Go to the **Integrations center** -> **Integrations 432 +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**; 422 422 423 423 [[image:image-20230802112413-35.png||height="738" width="1312"]] 424 424 ... ... @@ -432,7 +432,7 @@ 432 432 433 433 (% style="color:blue" %)**Add a topic filter:** 434 434 435 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。 446 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature **固定的? 对的。** 436 436 437 437 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default; 438 438 ... ... @@ -454,11 +454,11 @@ 454 454 455 455 * (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. 456 456 457 -* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 468 +* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的** 458 458 459 -* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 470 +* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的** 460 460 461 -Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely. (软件自动填充为 Device Name 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性) 472 +Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely.** (软件自动填充为 Device Name 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)** 462 462 463 463 (% style="color:blue" %)**CLIENT :“Any value”** 464 464 ... ... @@ -493,7 +493,7 @@ 493 493 [[image:image-20230802112413-46.png]] 494 494 495 495 496 -On the Connection Profile window, set the following information: (这边加一个截图) 507 +On the Connection Profile window, set the following information: **(这边加一个截图)** 497 497 498 498 * (% style="color:blue" %)**Profile Name: “Any name”** 499 499 ... ... @@ -503,7 +503,7 @@ 503 503 504 504 * (% style="color:blue" %)**Client ID: “Any value”** 505 505 506 -On the section User credentials, set the following information:(这边加一个截图) 517 +On the section User credentials, set the following information: **(这边加一个截图)** 507 507 508 508 * (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only 509 509 ... ... @@ -514,8 +514,6 @@ 514 514 * (% style="color:blue" %)**SUBTOPIC: “Any value”** 515 515 516 516 517 - 518 - 519 519 === 3.7.2 Simulate with MQTT.fx === 520 520 521 521 ... ... @@ -523,8 +523,9 @@ 523 523 524 524 [[image:image-20230802112413-48.png]] 525 525 526 -Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format. 535 +Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**. 527 527 537 + 528 528 [[image:image-20230802112413-49.png]] 529 529 530 530 ... ... @@ -553,7 +553,7 @@ 553 553 554 554 * (% style="color:blue" %)**Client ID: “Any value”** 555 555 556 -* (% style="color:blue" %)**User Name: “Any value”** (%%) Tago validates your user by the token only 566 +* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only 557 557 558 558 * (% style="color:blue" %)**Password: “Your device token”** 559 559