Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 59.1 >
edited by Edwin Chen
on 2023/08/07 10:07
To version < 53.25 >
edited by Xiaoling
on 2023/08/02 14:46
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -4,6 +4,7 @@
4 4  {{toc/}}
5 5  
6 6  
7 +
7 7  = 1. The use of this guideline =
8 8  
9 9  
... ... @@ -10,29 +10,20 @@
10 10  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.
11 11  
12 12  
13 -= 2. Attach Network =
14 += 2. Network Connection =
14 14  
15 15  
16 -To attache NB-IoT sensors to NB-IoT Network, You need to:
17 +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 (% class="mark" %)(补充 APN 指令(%%))
19 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
20 +|(% 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**
21 +|1NCE| | |
22 +|China Mobile| | |
21 21  
22 -After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
24 +== 2.1 1NCE SIM Card. ==
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: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**
28 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
29 -**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
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:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
34 -|(% style="width:117px" %)China Telecom|(% style="width:151px" %) |(% style="width:474px" %)China Mainland|(% style="width:135px" %)
35 -
36 36  = 3. Configure to connect to different servers =
37 37  
38 38  == 3.1 General UDP Connection ==
... ... @@ -113,9 +113,9 @@
113 113  [[image:image-20230802112413-7.png]]
114 114  
115 115  
116 -=== 3.3.2 Simulate with MQTT.fx ===
108 +== 3.3.2 Simulate with MQTT.fx ==
117 117  
118 -==== 3.3.2.1 Establish MQTT Connection ====
110 +=== 3.3.2.1 Establish MQTT Connection ===
119 119  
120 120  
121 121  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
... ... @@ -132,14 +132,12 @@
132 132  
133 133  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
134 134  
135 -==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
127 +=== 3.3.2.2 Publish Data to ThingSpeak Channel ===
136 136  
137 -
138 138  [[image:image-20230802112413-9.png]]
139 139  
140 140  [[image:image-20230802112413-10.png]]
141 141  
142 -
143 143  (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
144 144  
145 145  * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
... ... @@ -154,26 +154,26 @@
154 154  [[image:image-20230802112413-11.png]]
155 155  
156 156  
157 -=== 3.3.3 Configure NB-IoT Sensor for connection ===
147 +== 3.3 Configure NB-IoT Sensor for connection ==
158 158  
159 -==== 3.3.3.1 AT Commands: ====
149 +=== 3.3.1 AT Commands: ===
160 160  
161 161  
162 162  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
163 163  
164 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
154 +* **AT+PRO=3,1**   ~/~/ Set to use ThingSpeak Server and Related Payload
165 165  
166 -* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
156 +* **AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
167 167  
168 -* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
158 +* **AT+UNAME=<Your ThingSpeak MQTT User Name>**
169 169  
170 -* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
160 +* **AT+PWD=<Your ThingSpeak MQTT Password>**
171 171  
172 -* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
162 +* **AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
173 173  
174 -* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
164 +* **AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
175 175  
176 -==== 3.3.3.2 Uplink Examples ====
166 +=== 3.3.2 Uplink Examples ===
177 177  
178 178  
179 179  For S31-NB
... ... @@ -201,7 +201,7 @@
201 201  For SN50V3-NB
202 202  
203 203  
204 -==== 3.3.3.3 Map fields to sensor value ====
194 +=== 3.3.3 Map fields to sensor value ===
205 205  
206 206  
207 207  When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
... ... @@ -227,26 +227,144 @@
227 227  |(% 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" %)
228 228  |(% 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" %)
229 229  |(% 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
230 -|(% 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" %)
231 -|(% 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" %)
232 -|(% 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" %)
233 -|(% 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" %)
234 -|(% 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" %)
235 -|(% 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" %)
220 +|(% 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" %)
221 +|(% 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" %)
222 +|(% 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" %)
223 +|(% 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" %)
224 +|(% 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" %)
225 +|(% 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" %)
226 +|(% 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" %)
236 236  
228 +
237 237  == 3.4 Datacake ==
238 238  
231 +== 3.4.1 Define Product ==
239 239  
240 240  
234 +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.
241 241  
242 -== 3.5 Node-Red (via MQTT) ==
243 243  
244 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
237 +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  
239 +[[image:image-20230802112413-14.png]]
246 246  
247 -[[image:image-20230802112413-29.png]]
248 248  
242 +=== 3.4.2 Create Device ===
249 249  
244 +
245 +In the second step you have to define the device which should be added to the product.
246 +
247 +[[image:image-20230802112413-15.png]]
248 +
249 +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.
250 +
251 +
252 +=== 3.4.3 Create Database Fields ===
253 +
254 +
255 +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.
256 +
257 +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"**.
258 +
259 +[[image:image-20230802112413-16.png]]
260 +
261 +[[image:image-20230802112413-17.png]]
262 +
263 +To create a first database field, please click on the (% style="color:blue" %)**"Add Field"**(%%) button as marked in the screenshot above.
264 +
265 +This will open another modal asking for some required input for your first field.
266 +
267 +[[image:image-20230802112413-18.png]]
268 +
269 +[[image:image-20230802112413-19.png]]
270 +
271 +
272 +=== 3.4.4 Set up Broker ===
273 +
274 +
275 +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.
276 +
277 +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.
278 +
279 +View your Personal Access Token
280 +
281 +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:
282 +
283 +[[image:image-20230802112413-20.png]]
284 +
285 +(% style="color:blue" %)**MQTT Client-ID**
286 +
287 +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.
288 +
289 +(% style="color:blue" %)**AT+CLIENT=“Any value”**
290 +
291 +(% style="color:blue" %)**AT+UNAME=Token**
292 +
293 +(% style="color:blue" %)**AT+PWD=Token**
294 +
295 +[[image:image-20230802112413-21.png]]
296 +
297 +
298 +=== 3.4.5 Create your first Subscription ===
299 +
300 +
301 +(% style="color:blue" %)**Subscribe**
302 +
303 +Data is published according to the following structure:
304 +
305 +dtck~/~//
306 +
307 +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.
308 +
309 +
310 +[[image:image-20230802112413-22.png]]
311 +
312 +
313 +[[image:image-20230802112413-23.png]]
314 +
315 +
316 +[[image:image-20230802112413-24.png]]
317 +
318 +
319 +(% style="color:blue" %)**example:**
320 +
321 +AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
322 +
323 +[[image:image-20230802112413-25.png]]
324 +
325 +
326 +=== 3.4.6 Define Publish Topic ===
327 +
328 +
329 +(% style="color:blue" %)**Publish**
330 +
331 +To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
332 +
333 +Due to the nature of MQTT, the topic prefix differs as follows:
334 +
335 +dtck-pub~/~//
336 +
337 +(% style="color:blue" %)**example:**
338 +
339 +AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
340 +
341 +
342 +=== 3.4.7 upload data ===
343 +
344 +
345 +[[image:image-20230802112413-26.png]]
346 +
347 +[[image:image-20230802112413-27.png]]
348 +
349 +[[image:image-20230802112413-28.png]]
350 +
351 +
352 +== 3.5 Node-Red (via MQTT) ==
353 +
354 +=== 3.5.1 Configure Node-Red ===
355 +
356 +[[image:image-20230802112413-29.png]]
357 +
250 250  [[image:image-20230802112413-30.png]]
251 251  
252 252  
... ... @@ -259,7 +259,7 @@
259 259  === 3.5.3 Configure NB-IoT Sensors ===
260 260  
261 261  
262 -* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    ~/~/  Set to mqtt Server and  Payload
370 +* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    ~/~/Set to mqtt Server and  Payload
263 263  
264 264  * (% style="color:blue" %)**AT+CLIENT=any value**
265 265  
... ... @@ -277,22 +277,20 @@
277 277  
278 278  ==== 3.6.1.1 Create Device ====
279 279  
388 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
280 280  
281 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
282 -
283 283  [[image:image-20230802112413-32.png]]
284 284  
285 285  
286 286  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
287 287  
288 -
289 289  (% style="color:blue" %)**Uplink Converter**
290 290  
291 291  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.
292 292  
293 -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.
399 +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.
294 294  
295 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
401 +[[image:image-20230802112413-33.png]]
296 296  
297 297  
298 298  (% style="color:blue" %)**Downlink Converter**
... ... @@ -299,7 +299,7 @@
299 299  
300 300  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
301 301  
302 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
408 +[[image:image-20230802112413-34.png]]
303 303  
304 304  (% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
305 305  
... ... @@ -307,30 +307,28 @@
307 307  ==== 3.6.1.3 MQTT Integration Setup ====
308 308  
309 309  
310 -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**;
416 +Go to the Integrations center -> Integrations page and click **“plus”** icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
311 311  
312 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
418 +[[image:image-20230802112413-35.png]]
313 313  
314 -
315 315  * The next steps is to add the recently created uplink and downlink converters;
316 316  
317 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
422 +[[image:image-20230802112413-36.png]]
318 318  
319 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
424 +[[image:image-20230802112413-37.png]]
320 320  
321 -
322 322  (% style="color:blue" %)**Add a topic filter:**
323 323  
324 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
325 325  
429 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
430 +
326 326  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
327 327  
328 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
433 +[[image:image-20230802112413-38.png]]
329 329  
330 330  
331 331  === 3.6.2 Simulate with MQTT.fx ===
332 332  
333 -
334 334  [[image:image-20230802112413-39.png]]
335 335  
336 336  [[image:image-20230802112413-40.png]]
... ... @@ -341,16 +341,22 @@
341 341  
342 342  (% style="color:blue" %)**AT Commands**
343 343  
344 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
448 +* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard.
345 345  
346 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>** (%%)
347 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
348 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
349 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
350 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
450 +* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的
351 351  
352 -
452 +* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的
353 353  
454 +
455 +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 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）
456 +
457 +(% style="color:blue" %)**CLIENT :“Any value”**
458 +
459 +(% style="color:blue" %)**User Name:“Any value”**
460 +
461 +(% style="color:blue" %)**Password:“Any value”**
462 +
463 +
354 354  Test Uplink by click the button for 1 second
355 355  
356 356  [[image:image-20230802112413-41.png]]
... ... @@ -377,7 +377,7 @@
377 377  [[image:image-20230802112413-46.png]]
378 378  
379 379  
380 -On the Connection Profile window, set the following information: **(这边加一个截图)**
490 +On the Connection Profile window, set the following information: (这边加一个截图)
381 381  
382 382  * (% style="color:blue" %)**Profile Name: “Any name”**
383 383  
... ... @@ -387,16 +387,18 @@
387 387  
388 388  * (% style="color:blue" %)**Client ID: “Any value”**
389 389  
390 -On the section User credentials, set the following information: **(这边加一个截图)**
500 +On the section User credentials, set the following information:(这边加一个截图)
391 391  
392 -* (% style="color:blue" %)**User Name: “Any value”**  (%%) ~/~/  Tago validates your user by the token only
502 +* **User Name: “Any value”**  Tago validates your user by the token only
393 393  
394 -* (% style="color:blue" %)**Password: “Your device token”**
504 +* **Password: “Your device token”**
395 395  
396 -* (% style="color:blue" %)**PUBTOPIC: “Any value”**
506 +* **PUBTOPIC: “Any value”**
397 397  
398 -* (% style="color:blue" %)**SUBTOPIC: “Any value”**
508 +* **SUBTOPIC: “Any value”**
399 399  
510 +
511 +
400 400  === 3.7.2 Simulate with MQTT.fx ===
401 401  
402 402  
... ... @@ -404,9 +404,8 @@
404 404  
405 405  [[image:image-20230802112413-48.png]]
406 406  
407 -Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
519 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
408 408  
409 -
410 410  [[image:image-20230802112413-49.png]]
411 411  
412 412  
... ... @@ -415,7 +415,7 @@
415 415  
416 416  [[image:image-20230802112413-50.png]]
417 417  
418 -[[image:image-20230802112413-51.png||height="184" width="696"]]
529 +[[image:image-20230802112413-51.png]]
419 419  
420 420  
421 421  === 3.7.4 TLS mode ===
... ... @@ -435,7 +435,7 @@
435 435  
436 436  * (% style="color:blue" %)**Client ID: “Any value”**
437 437  
438 -* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only
549 +* (% style="color:blue" %)**User Name: “Any value”** (%%) Tago validates your user by the token only
439 439  
440 440  * (% style="color:blue" %)**Password: “Your device token”**
441 441  

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0