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. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -13,28 +13,19 @@ 13 13 = 2. Network Connection = 14 14 15 15 16 -T o attache NB-IoTsensorsto NB-IoTNetwork,Youneedto:16 +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. 17 17 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 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| | | 21 21 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. 25 25 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]]** 25 +== 2.1 1NCE SIM Card. == 30 30 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" %) 35 35 36 36 37 - 38 38 = 3. Configure to connect to different servers = 39 39 40 40 == 3.1 General UDP Connection == ... ... @@ -135,6 +135,7 @@ 135 135 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 136 136 137 137 129 + 138 138 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 139 139 140 140 ... ... @@ -142,7 +142,6 @@ 142 142 143 143 [[image:image-20230802112413-10.png]] 144 144 145 - 146 146 (% style="color:blue" %)**In MQTT.fx, we can publish below info:** 147 147 148 148 * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish ... ... @@ -239,7 +239,6 @@ 239 239 |(% 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" %) 240 240 |(% 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" %) 241 241 242 - 243 243 == 3.4 Datacake == 244 244 245 245 === 3.4.1 Define Product === ... ... @@ -249,7 +249,7 @@ 249 249 250 250 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"**. 251 251 252 -[[image:image-20230802112413-14.png ||height="1095" width="1302"]]242 +[[image:image-20230802112413-14.png]] 253 253 254 254 255 255 === 3.4.2 Create Device === ... ... @@ -295,17 +295,15 @@ 295 295 296 296 [[image:image-20230802112413-20.png]] 297 297 298 - 299 299 (% style="color:blue" %)**MQTT Client-ID** 300 300 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. 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. 303 303 304 - *(% style="color:blue" %)**AT+CLIENT=“Any value”**292 +(% style="color:blue" %)**AT+CLIENT=“Any value”** 305 305 306 - *(% style="color:blue" %)**AT+UNAME=Token**294 +(% style="color:blue" %)**AT+UNAME=Token** 307 307 308 - *(% style="color:blue" %)**AT+PWD=Token**296 +(% style="color:blue" %)**AT+PWD=Token** 309 309 310 310 [[image:image-20230802112413-21.png]] 311 311 ... ... @@ -362,7 +362,7 @@ 362 362 363 363 == 3.5 Node-Red (via MQTT) == 364 364 365 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]]===353 +=== 3.5.1 Configure Node-Red === 366 366 367 367 368 368 [[image:image-20230802112413-29.png]] ... ... @@ -393,6 +393,7 @@ 393 393 * (% style="color:blue" %)**AT+SUBTOPIC=any value** 394 394 395 395 384 + 396 396 == 3.6 ThingsBoard.Cloud (via MQTT) == 397 397 398 398 === 3.6.1 Configure ThingsBoard === ... ... @@ -412,7 +412,7 @@ 412 412 413 413 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. 414 414 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.404 +To create an uplink converter go to the **Integrations center** -> **Data converters** page and click **“plus”** button. Name it **“MQTT Uplink Converter”** and select type "**Uplink"**. Use debug mode for now. 416 416 417 417 [[image:image-20230802112413-33.png||height="732" width="1302"]] 418 418 ... ... @@ -429,7 +429,7 @@ 429 429 ==== 3.6.1.3 MQTT Integration Setup ==== 430 430 431 431 432 -Go to the (% style="color:blue" %)**Integrations center**(%%)**->**(% style="color:blue" %)**Integrations(%%)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**;421 +Go to the **Integrations center** -> **Integrations page** and click **“plus”** icon to add a new integration. Name it **“MQTT Integration”**, select type MQTT; 433 433 434 434 [[image:image-20230802112413-35.png||height="738" width="1312"]] 435 435 ... ... @@ -440,11 +440,11 @@ 440 440 441 441 [[image:image-20230802112413-37.png||height="735" width="1307"]] 442 442 443 - 444 444 (% style="color:blue" %)**Add a topic filter:** 445 445 446 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature **固定的? 对的。** 447 447 435 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。 436 + 448 448 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default; 449 449 450 450 [[image:image-20230802112413-38.png||height="731" width="1300"]] ... ... @@ -465,11 +465,11 @@ 465 465 466 466 * (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. 467 467 468 -* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的**457 +* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 469 469 470 -* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的**459 +* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 471 471 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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)**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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性) 473 473 474 474 (% style="color:blue" %)**CLIENT :“Any value”** 475 475 ... ... @@ -504,7 +504,7 @@ 504 504 [[image:image-20230802112413-46.png]] 505 505 506 506 507 -On the Connection Profile window, set the following information: **(这边加一个截图)**496 +On the Connection Profile window, set the following information: (这边加一个截图) 508 508 509 509 * (% style="color:blue" %)**Profile Name: “Any name”** 510 510 ... ... @@ -514,17 +514,16 @@ 514 514 515 515 * (% style="color:blue" %)**Client ID: “Any value”** 516 516 517 -On the section User credentials, set the following information: **(这边加一个截图)**506 +On the section User credentials, set the following information:(这边加一个截图) 518 518 519 -* (% style="color:blue" %)**User Name: “Any value”**(%%)~/~/Tago validates your user by the token only508 +* **User Name: “Any value”** Tago validates your user by the token only 520 520 521 -* (% style="color:blue" %)**Password: “Your device token”**510 +* **Password: “Your device token”** 522 522 523 -* (% style="color:blue" %)**PUBTOPIC: “Any value”**512 +* **PUBTOPIC: “Any value”** 524 524 525 -* (% style="color:blue" %)**SUBTOPIC: “Any value”**514 +* **SUBTOPIC: “Any value”** 526 526 527 - 528 528 === 3.7.2 Simulate with MQTT.fx === 529 529 530 530 ... ... @@ -532,9 +532,8 @@ 532 532 533 533 [[image:image-20230802112413-48.png]] 534 534 535 -Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%)command, and the payload will be converted to**JSON format**.523 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format. 536 536 537 - 538 538 [[image:image-20230802112413-49.png]] 539 539 540 540 ... ... @@ -563,7 +563,7 @@ 563 563 564 564 * (% style="color:blue" %)**Client ID: “Any value”** 565 565 566 -* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/Tago validates your user by the token only553 +* (% style="color:blue" %)**User Name: “Any value”** (%%) Tago validates your user by the token only 567 567 568 568 * (% style="color:blue" %)**Password: “Your device token”** 569 569