<
From version < 78.1 >
edited by David Huang
on 2023/08/08 16:50
To version < 53.34 >
edited by Xiaoling
on 2023/08/02 15:12
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Xiaoling
Content
... ... @@ -1,4 +1,5 @@
1 -== **Table of Contents:** ==
1 +(% class="wikigeneratedid" %)
2 +**Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -9,30 +9,21 @@
9 9  This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module **[[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
10 10  
11 11  
12 -= 2. Attach Network =
13 += 2. Network Connection =
13 13  
14 14  
15 -To attache NB-IoT sensors to NB-IoT Network, You need to:
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.
16 16  
17 -1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
18 -1. Insert the SIM card to Sensor
19 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (% class="mark" %)(补充 APN 指令(%%))
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| | |
20 20  
21 -(% class="mark" %)插入 SIM 卡图片
22 22  
23 -After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
24 24  
25 -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 +== 2.1 1NCE SIM Card. ==
26 26  
27 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
28 -|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
29 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
30 -**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
31 31  
32 -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
33 -)))|(% style="width:135px" %)
34 -|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
35 -|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
36 36  
37 37  = 3. Configure to connect to different servers =
38 38  
... ... @@ -133,6 +133,8 @@
133 133  
134 134  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
135 135  
128 +
129 +
136 136  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
137 137  
138 138  
... ... @@ -140,7 +140,6 @@
140 140  
141 141  [[image:image-20230802112413-10.png]]
142 142  
143 -
144 144  (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
145 145  
146 146  * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
... ... @@ -174,6 +174,7 @@
174 174  
175 175  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
176 176  
170 +
177 177  ==== 3.3.3.2 Uplink Examples ====
178 178  
179 179  
... ... @@ -228,34 +228,135 @@
228 228  |(% style="background-color:#4f81bd; color:white; width:124px" %)NMDS200-NB|(% style="width:91px" %)distance1|(% style="width:102px" %)distance2|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
229 229  |(% style="background-color:#4f81bd; color:white; width:124px" %)CPN01-NB|(% style="width:91px" %)alarm|(% style="width:102px" %)count|(% style="width:159px" %)door open duration|(% style="width:153px" %)calc flag|(% style="width:152px" %)Battery|(% style="width:148px" %)RSSI|(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
230 230  |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:91px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:159px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:153px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:152px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:148px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:164px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:66px" %)Battery|(% colspan="1" rowspan="1" style="width:66px" %)RSSI
231 -|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:91px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:159px" %)RSSI|(% colspan="1" rowspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:148px" %)adc0|(% colspan="1" rowspan="1" style="width:164px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
232 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod2|(% 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" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc0|(% colspan="1" style="width:164px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
233 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod3|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc1|(% colspan="1" style="width:164px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:66px" %)adc4|(% colspan="1" style="width:66px" %)
234 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB mod4|(% 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" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
235 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB 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" %)
236 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB 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" %)
225 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB|(% colspan="1" rowspan="1" style="width:91px" %) |(% colspan="1" rowspan="1" style="width:102px" %) |(% colspan="1" rowspan="1" style="width:159px" %) |(% colspan="1" rowspan="1" style="width:153px" %) |(% colspan="1" rowspan="1" style="width:152px" %) |(% colspan="1" rowspan="1" style="width:148px" %) |(% colspan="1" rowspan="1" style="width:164px" %) |(% colspan="1" rowspan="1" style="width:152px" %) |(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
226 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod1|(% colspan="1" rowspan="1" style="width:91px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:159px" %)RSSI|(% colspan="1" rowspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:148px" %)adc0|(% colspan="1" rowspan="1" style="width:164px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
227 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod2|(% 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" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc0|(% colspan="1" style="width:164px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
228 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod3|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc1|(% colspan="1" style="width:164px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:66px" %)adc4|(% colspan="1" style="width:66px" %)
229 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod4|(% 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" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
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 +|(% 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" %)
237 237  
238 238  == 3.4 Datacake ==
239 239  
235 +=== 3.4.1 Define Product ===
240 240  
241 -[[image:image-20230808162301-1.png]]
242 242  
238 +Firstly, we need to set the MQTT mode to datacake, and we need to run(% style="color:blue" %)** AT+PRO=3,2**(%%). This command is set to datacake. After running the command, the device automatically sets the server address, port.
243 243  
244 -[[image:image-20230808162342-2.png]]
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"**.
245 245  
242 +[[image:image-20230802112413-14.png]]
246 246  
247 -[[image:image-20230808162421-3.png]]
248 248  
245 +=== 3.4.2 Create Device ===
249 249  
250 -[[image:image-20230808163612-7.png]]
251 251  
252 -[[image:image-20230808163035-5.png]]
248 +In the second step you have to define the device which should be added to the product.
253 253  
254 -[[image:image-20230808163049-6.png]]
250 +[[image:image-20230802112413-15.png||height="859" width="1290"]]
255 255  
252 +Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the (% style="color:blue" %)**"Next"**(%%) button.
253 +
254 +
255 +=== 3.4.3 Create Database Fields ===
256 +
257 +
258 +After creating the device, it is listed in the table of the fleet view. Now open the device by clicking on the entry in the list.
259 +
260 +You will then see a device view with an empty dashboard. Now, the first thing we want to do is navigate to the Device configuration. To do this, use the tab bar and click on (% style="color:blue" %)**"Configuration"**.
261 +
262 +[[image:image-20230802112413-16.png||height="495" width="1310"]]
263 +
264 +[[image:image-20230802112413-17.png||height="741" width="1303"]]
265 +
266 +To create a first database field, please click on the (% style="color:blue" %)**"Add Field"**(%%) button as marked in the screenshot above.
267 +
268 +This will open another modal asking for some required input for your first field.
269 +
270 +[[image:image-20230802112413-18.png||height="878" width="1305"]]
271 +
272 +[[image:image-20230802112413-19.png]]
273 +
274 +
275 +=== 3.4.4 Set up Broker ===
276 +
277 +
278 +The broker is running on mqtt.datacake.co on ports (% style="color:blue" %)**1883 and 8883**(%%). Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate.
279 +
280 +You will need an access token to log into the Datacake MQTT Broker. You can use your own personal token or create a token explicitly for individual devices or groups of devices.
281 +
282 +View your Personal Access Token
283 +
284 +You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on (% style="color:blue" %)**"Edit Profile"**(%%) at the end of the list using the Workspace Selector:
285 +
286 +[[image:image-20230802112413-20.png]]
287 +
288 +(% style="color:blue" %)**MQTT Client-ID**
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.
291 +
292 +(% style="color:blue" %)**AT+CLIENT=“Any value”**
293 +
294 +(% style="color:blue" %)**AT+UNAME=Token**
295 +
296 +(% style="color:blue" %)**AT+PWD=Token**
297 +
298 +[[image:image-20230802112413-21.png]]
299 +
300 +
301 +=== 3.4.5 Create your first Subscription ===
302 +
303 +
304 +(% style="color:blue" %)**Subscribe**
305 +
306 +Data is published according to the following structure: (% style="color:blue" %)**dtck~/~//**(%%)** **
307 +
308 +Subscribe to topics using this structure to receive messages via MQTT when readings (via API or MQTT) arrive in the Datacake Cloud. Messages are published whenever there is a change to a corresponding database field.
309 +
310 +
311 +[[image:image-20230802112413-22.png]]
312 +
313 +
314 +[[image:image-20230802112413-23.png]]
315 +
316 +
317 +[[image:image-20230802112413-24.png]]
318 +
319 +
320 +(% style="color:blue" %)**example:**
321 +
322 +AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
323 +
324 +[[image:image-20230802112413-25.png]]
325 +
326 +
327 +=== 3.4.6 Define Publish Topic ===
328 +
329 +
330 +(% style="color:blue" %)**Publish**
331 +
332 +To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
333 +
334 +Due to the nature of MQTT, the topic prefix differs as follows: (% style="color:blue" %)**dtck-pub~/~//**
335 +
336 +(% style="color:blue" %)**example:**
337 +
338 +AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
339 +
340 +
341 +=== 3.4.7 upload data ===
342 +
343 +
344 +[[image:image-20230802112413-26.png]]
345 +
346 +[[image:image-20230802112413-27.png]]
347 +
348 +[[image:image-20230802112413-28.png]]
349 +
350 +
256 256  == 3.5 Node-Red (via MQTT) ==
257 257  
258 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
353 +=== 3.5.1 Configure Node-Red ===
259 259  
260 260  
261 261  [[image:image-20230802112413-29.png]]
... ... @@ -285,6 +285,8 @@
285 285  
286 286  * (% style="color:blue" %)**AT+SUBTOPIC=any value**
287 287  
383 +
384 +
288 288  == 3.6 ThingsBoard.Cloud (via MQTT) ==
289 289  
290 290  === 3.6.1 Configure ThingsBoard ===
... ... @@ -292,7 +292,7 @@
292 292  ==== 3.6.1.1 Create Device ====
293 293  
294 294  
295 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
392 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
296 296  
297 297  [[image:image-20230802112413-32.png]]
298 298  
... ... @@ -304,7 +304,7 @@
304 304  
305 305  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.
306 306  
307 -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.
308 308  
309 309  [[image:image-20230802112413-33.png||height="732" width="1302"]]
310 310  
... ... @@ -321,7 +321,7 @@
321 321  ==== 3.6.1.3 MQTT Integration Setup ====
322 322  
323 323  
324 -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**;
421 +Go to the **Integrations center** -> **Integrations page** and click **“plus”** icon to add a new integration. Name it **“MQTT Integration”**, select type MQTT;
325 325  
326 326  [[image:image-20230802112413-35.png||height="738" width="1312"]]
327 327  
... ... @@ -335,7 +335,7 @@
335 335  
336 336  (% style="color:blue" %)**Add a topic filter:**
337 337  
338 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
435 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
339 339  
340 340  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
341 341  
... ... @@ -355,14 +355,21 @@
355 355  
356 356  (% style="color:blue" %)**AT Commands**
357 357  
358 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
455 +* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard.
359 359  
360 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>** (%%)
361 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
362 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
363 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
364 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
457 +* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的
365 365  
459 +* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的
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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)
462 +
463 +(% style="color:blue" %)**CLIENT :“Any value”**
464 +
465 +(% style="color:blue" %)**User Name:“Any value”**
466 +
467 +(% style="color:blue" %)**Password:“Any value”**
468 +
469 +
366 366  Test Uplink by click the button for 1 second
367 367  
368 368  [[image:image-20230802112413-41.png]]
... ... @@ -389,21 +389,19 @@
389 389  [[image:image-20230802112413-46.png]]
390 390  
391 391  
392 -The device needs to enable the TLS modand set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
496 +On the Connection Profilwindow, set the following information: (这边加一个截图)
393 393  
394 -On the Connection Profile window, set the following information:
395 -
396 396  * (% style="color:blue" %)**Profile Name: “Any name”**
397 397  
398 398  * (% style="color:blue" %)**Broker Address: mqtt.tago.io**
399 399  
400 -* (% style="color:blue" %)**Broker Port: 8883**
502 +* (% style="color:blue" %)**Broker Port: 1883**
401 401  
402 402  * (% style="color:blue" %)**Client ID: “Any value”**
403 403  
404 -On the section User credentials, set the following information:
506 +On the section User credentials, set the following information:(这边加一个截图)
405 405  
406 -* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only
508 +* (% style="color:blue" %)**User Name: “Any value”**  (%%) ~/~/  Tago validates your user by the token only
407 407  
408 408  * (% style="color:blue" %)**Password: “Your device token”**
409 409  
... ... @@ -411,54 +411,55 @@
411 411  
412 412  * (% style="color:blue" %)**SUBTOPIC: “Any value”**
413 413  
414 -(% style="color:blue" %)**AT command:**
415 415  
416 -* **AT+PRO=3,0 or 3,5   **~/~/ hex format or json format
417 417  
418 -* **AT+SUBTOPIC=<device name>** **or User Defined**
419 -* **AT+PUBTOPIC=<device name>or User Defined**
420 -* **AT+CLIENT=<device name> or User Defined**
421 -* **AT+UNAME=<device name> or User Defined**
422 -* **AT+PWD=“Your device token”**
423 423  
424 424  === 3.7.2 Simulate with MQTT.fx ===
425 425  
426 -[[image:image-20230802112413-52.png]]
427 427  
522 +[[image:image-20230802112413-47.png]]
428 428  
429 -[[image:image-20230808105300-2.png]]
524 +[[image:image-20230802112413-48.png]]
430 430  
431 -Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
526 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
432 432  
433 -[[image:image-20230808105217-1.png]]
528 +[[image:image-20230802112413-49.png]]
434 434  
435 -[[image:image-20230808105329-3.png]]
436 436  
437 -
438 438  === 3.7.3 tago data ===
439 439  
440 440  
441 441  [[image:image-20230802112413-50.png]]
442 442  
443 -[[image:image-20230802112413-51.png||height="184" width="696"]]
536 +[[image:image-20230802112413-51.png]]
444 444  
445 445  
539 +=== 3.7.4 TLS mode ===
446 446  
447 -== 3.8 TCP Connection ==
448 448  
542 +Users can choose to use (% style="color:blue" %)**SSL/TLS**(%%) mode.
449 449  
450 -* **AT+PRO=4,0   ** ~/~/ Set to use TCP protocol to uplink(HEX format)
451 -* **AT+PRO=4,1   ** ~/~/ Set to use TCP protocol to uplink(JSON format)
452 -* **AT+SERVADDR=120.24.4.116,5600   **~/~/ to set TCP server address and port
544 +On the SSL/TLS section, check the option **Enable SSL/TLS**, and click OK.
453 453  
454 -**Sensor Console Output when Uplink**
546 +The device needs to enable the TLS mode anset the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
455 455  
456 -[[image:image-20230807233631-1.png]]
548 +* (% style="color:blue" %)**Profile Name: “Any name”**
457 457  
550 +* (% style="color:blue" %)**Broker Address: mqtt.tago.io**
458 458  
459 -**See result in TCP Server**
552 +* (% style="color:blue" %)**Broker Port: 8883**
460 460  
461 -[[image:image-20230807233631-2.png]]
554 +* (% style="color:blue" %)**Client ID: “Any value”**
462 462  
556 +* (% style="color:blue" %)**User Name: “Any value”** (%%) Tago validates your user by the token only
463 463  
558 +* (% style="color:blue" %)**Password: “Your device token”**
464 464  
560 +* (% style="color:blue" %)**PUBTOPIC: “Any value”**
561 +
562 +* (% style="color:blue" %)**SUBTOPIC: “Any value”**
563 +
564 +[[image:image-20230802112413-52.png]]
565 +
566 +
567 +
image-20230807233631-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -21.9 KB
Content
image-20230807233631-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -9.6 KB
Content
image-20230808105217-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -68.5 KB
Content
image-20230808105300-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -70.1 KB
Content
image-20230808105329-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -21.1 KB
Content
image-20230808162301-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -76.9 KB
Content
image-20230808162342-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -63.8 KB
Content
image-20230808162421-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -59.2 KB
Content
image-20230808162727-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -54.2 KB
Content
image-20230808163035-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -71.6 KB
Content
image-20230808163049-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -61.5 KB
Content
image-20230808163612-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -53.4 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0