Version 104.1 by Edwin Chen on 2023/10/02 18:30
Show last authors
1 (% class="wikigeneratedid" id="HTableofContents:" %)
2 **Table of Contents:**
3
4 {{toc/}}
5
6
7
8
9
10
11 = 1. The use of this guideline =
12
13
14 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.
15
16
17 = 2. Attach Network =
18
19 == 2.1 General Configure to attach network ==
20
21 To attache NB-IoT sensors to NB-IoT Network, You need to:
22
23 1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
24 1. Insert the SIM card to Sensor
25 1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
26
27 [[image:image-20230808205045-1.png||height="293" width="438"]]
28
29 After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
30
31 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.
32
33 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
34 |(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+APN=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
35 |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
36 **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
37
38 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
39 )))|(% style="width:135px" %)
40 |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
41 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
42
43 (% class="wikigeneratedid" %)
44 == ==
45
46 == 2.2 Speed Up Network Attach time ==
47
48 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.
49
50 **AT+QBAND?** ~/~/ Check what is the current used frequency band
51
52 **AT+QBAND=1,4** ~/~/ Set to use 1 frequency band. Band4
53
54 **AT+QBAND=2,8,20** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
55
56
57
58 = 3. Configure to connect to different servers =
59
60 == 3.1 General UDP Connection ==
61
62
63 The NB-IoT Sensor can send packet to server use UDP protocol.
64
65
66 === 3.1.1 Simulate UDP Connection by PC tool ===
67
68
69 We can use PC tool to simulate UDP connection to make sure server works ok.
70
71 [[image:image-20230802112413-1.png]]
72
73
74 === 3.1.2 Configure NB-IoT Sensor ===
75
76 ==== 3.1.2.1 AT Commands ====
77
78
79 (% style="color:blue" %)**AT Commands:**
80
81 * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
82
83 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
84
85 * (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
86
87 [[image:image-20230802112413-2.png]]
88
89
90 ==== 3.1.2.2 Uplink Example ====
91
92
93 [[image:image-20230802112413-3.png]]
94
95
96 == 3.2 General MQTT Connection ==
97
98
99 The NB-IoT Sensor can send packet to server use MQTT protocol.
100
101 Below are the commands.
102
103 (% style="color:blue" %)**AT Commands:**
104
105 * (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
106
107 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
108
109 * (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
110
111 * (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
112
113 * (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
114
115 * (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
116
117 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/  Set the subscription topic of MQTT
118
119 [[image:image-20230802112413-4.png]]
120
121 [[image:image-20230802112413-5.png||height="530" width="987"]]
122
123 (% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink  period to a suitable interval.**
124
125
126 == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
127
128 === 3.3.1 Get MQTT Credentials ===
129
130
131 [[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.
132
133 [[image:image-20230802112413-6.png||height="336" width="925"]]
134
135 [[image:image-20230802112413-7.png]]
136
137
138 === 3.3.2 Simulate with MQTT.fx ===
139
140 ==== 3.3.2.1 Establish MQTT Connection ====
141
142
143 After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
144
145 [[image:image-20230802112413-8.png]]
146
147 * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
148
149 * (% style="color:#037691" %)**Broker Port:**(%%) 1883
150
151 * (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
152
153 * (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
154
155 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
156
157 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
158
159
160 [[image:image-20230802112413-9.png]]
161
162 [[image:image-20230802112413-10.png]]
163
164
165 (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
166
167 * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
168
169 * (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
170
171 Where 63 and 67 are the value to be published to field1 & field2.
172
173
174 (% style="color:blue" %)**Result: **
175
176 [[image:image-20230802112413-11.png||height="539" width="901"]]
177
178
179 === 3.3.3 Configure NB-IoT Sensor for connection ===
180
181 ==== 3.3.3.1 AT Commands: ====
182
183
184 In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
185
186 * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
187
188 * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
189
190 * (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
191
192 * (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
193
194 * (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
195
196 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
197
198 ==== 3.3.3.2 Uplink Examples ====
199
200 [[image:image-20230816201942-1.png]]
201
202 For SE01-NB
203
204 For DDS20-NB
205
206 For DDS45-NB
207
208 For DDS75-NB
209
210 For NMDS120-NB
211
212 For SPH01-NB
213
214 For NLM01-NB
215
216 For NMDS200-NB
217
218 For CPN01-NB
219
220 For DS03A-NB
221
222 For SN50V3-NB
223
224
225 ==== 3.3.3.3 Map fields to sensor value ====
226
227
228 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.
229
230
231 [[image:image-20230802112413-12.png||height="504" width="1011"]]
232
233 [[image:image-20230802112413-13.png||height="331" width="978"]]
234
235
236 Below is the NB-IoT Product Table show the mapping.
237
238 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
239 |(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:154px" %)Field4|(% style="background-color:#4f81bd; color:white; width:153px" %)Field5|(% style="background-color:#4f81bd; color:white; width:151px" %)Field6|(% style="background-color:#4f81bd; color:white; width:160px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:67px" %)Field9|(% style="background-color:#4f81bd; color:white; width:69px" %)Field10
240 |(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
241 |(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:154px" %)dielectric_constant|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
242 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
243 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
244 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
245 |(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
246 |(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
247 |(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
248 |(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
249 |(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:154px" %)calc flag|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
250 |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:67px" %)Battery|(% colspan="1" rowspan="1" style="width:69px" %)RSSI
251 |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:151px" %)adc0|(% colspan="1" rowspan="1" style="width:160px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
252 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc0|(% colspan="1" style="width:160px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
253 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)adc0|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc1|(% colspan="1" style="width:160px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:67px" %)adc4|(% colspan="1" style="width:69px" %)
254 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
255 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
256 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
257
258 == 3.4 [[Datacake>>https://datacake.co/]] ==
259
260
261 (% class="wikigeneratedid" %)
262 Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
263
264
265 (% class="wikigeneratedid" %)
266 As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
267
268 * (% style="color:blue" %)**S31B-NB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
269
270 * (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
271
272 === 3.4.1 Create device ===
273
274
275 (% style="color:blue" %)**Add Device**(%%) in DataCake.
276
277 [[image:image-20230808162301-1.png||height="473" width="994"]]
278
279
280 [[image:image-20230808162342-2.png]]
281
282
283 (% style="color:blue" %)**Choose the correct model**(%%) from template.
284
285 [[image:image-20230808162421-3.png]]
286
287
288 (% 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.
289
290 [[image:image-20230808163612-7.png]]
291
292 [[image:image-20230808163035-5.png]]
293
294 [[image:image-20230808163049-6.png]]
295
296
297 === 3.4.2 Scan QR code to obtain data ===
298
299
300 Users can use their phones or computers to scan QR codes to obtain device data information.
301
302 [[image:image-20230808170051-8.png||height="255" width="259"]]
303
304 [[image:image-20230808170548-9.png]]
305
306
307 === 3.4.2 AT command for connecting to DataCake ===
308
309
310 (% style="color:blue" %)**AT+PRO=2,0**
311
312 (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
313
314
315 == 3.5 Node-Red (via MQTT) ==
316
317 === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
318
319
320 Take S31-NB UDP protocol as an example.
321
322 Dragino provides input flow examples for the sensors.
323
324 User can download the required JSON file through Dragino Node-RED input flow template.
325
326 Download sample JSON file link: [[https:~~/~~/www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0>>url:https://www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0]]
327
328 We can directly import the template.
329
330 The templates for S31-NB and NB95S31B are the same.
331
332
333 [[image:image-20230809173127-4.png]]
334
335
336 Please select the NB95S31B template.
337
338 [[image:image-20230809173310-5.png]]
339
340 [[image:image-20230809173438-6.png]]
341
342 [[image:image-20230809173800-7.png]]
343
344
345 Successfully imported template.
346
347 [[image:image-20230809173835-8.png]]
348
349
350 Users can set UDP port.
351
352 [[image:image-20230809174053-9.png]]
353
354
355 === 3.5.2 Simulate Connection ===
356
357
358 We have completed the configuration of UDP. We can try sending packets to node red.
359
360 [[image:image-20230810083934-1.png]]
361
362 [[image:image-20230810084048-2.png]]
363
364 === 3.5.3 Configure NB-IoT Sensors ===
365
366
367 * (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
368
369 * (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
370
371 == 3.6 ThingsBoard.Cloud (via MQTT) ==
372
373 === 3.6.1 Configure ThingsBoard ===
374
375 ==== 3.6.1.1 Create Device ====
376
377
378 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
379
380 [[image:image-20230802112413-32.png]]
381
382
383 ==== 3.6.1.2 Create Uplink & Downlink Converter ====
384
385
386 (% style="color:blue" %)**Uplink Converter**
387
388 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.
389
390 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.
391
392 [[image:image-20230802112413-33.png||height="732" width="1302"]]
393
394
395 (% style="color:blue" %)**Downlink Converter**
396
397 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
398
399 [[image:image-20230802112413-34.png||height="734" width="1305"]]
400
401 (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
402
403
404 ==== 3.6.1.3 MQTT Integration Setup ====
405
406
407 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**;
408
409 [[image:image-20230802112413-35.png||height="738" width="1312"]]
410
411
412 * The next steps is to add the recently created uplink and downlink converters;
413
414 [[image:image-20230802112413-36.png||height="736" width="1308"]]
415
416 [[image:image-20230802112413-37.png||height="735" width="1307"]]
417
418
419 (% style="color:blue" %)**Add a topic filter:**
420
421 tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
422
423 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
424
425 [[image:image-20230802112413-38.png||height="731" width="1300"]]
426
427
428 === 3.6.2 Simulate with MQTT.fx ===
429
430
431 [[image:image-20230802112413-39.png]]
432
433 [[image:image-20230802112413-40.png]]
434
435
436 === 3.6.3 Configure NB-IoT Sensor ===
437
438
439 (% style="color:blue" %)**AT Commands**
440
441 * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
442
443 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
444
445 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
446
447 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
448
449 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
450
451 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
452
453 Test Uplink by click the button for 1 second
454
455 [[image:image-20230802112413-41.png]]
456
457 [[image:image-20230802112413-42.png]]
458
459 [[image:image-20230802112413-43.png]]
460
461
462 == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
463
464 === 3.7.1 Create device & Get Credentials ===
465
466
467 We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
468
469 [[image:image-20230802112413-44.png]]
470
471 [[image:image-20230802112413-45.png]]
472
473
474 Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
475
476 [[image:image-20230802112413-46.png]]
477
478
479 The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
480
481 (% style="color:blue" %)**On the Connection Profile window, set the following information:**
482
483 * (% style="color:#037691" %)**Profile Name: “Any name”**
484
485 * (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
486
487 * (% style="color:#037691" %)**Broker Port: 8883**
488
489 * (% style="color:#037691" %)**Client ID: “Any value”**
490
491 (% style="color:blue" %)**On the section User credentials, set the following information:**
492
493 * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
494
495 * (% style="color:#037691" %)**Password: “Your device token”**
496
497 * (% style="color:#037691" %)**PUBTOPIC: “Any value”**
498
499 * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
500
501 (% style="color:blue" %)**AT command:**
502
503 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
504
505 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
506
507 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
508
509 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
510
511 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
512
513 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
514
515 === 3.7.2 Simulate with MQTT.fx ===
516
517
518 [[image:image-20230802112413-52.png]]
519
520
521 [[image:image-20230808105300-2.png]]
522
523
524 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
525
526 [[image:image-20230808105217-1.png]]
527
528 [[image:image-20230808105329-3.png]]
529
530
531 === 3.7.3 tago data ===
532
533
534 [[image:image-20230802112413-50.png]]
535
536 [[image:image-20230802112413-51.png||height="184" width="696"]]
537
538
539 == 3.8 TCP Connection ==
540
541
542 (% style="color:blue" %)**AT command:**
543
544 * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
545
546 * (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
547
548 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
549
550 (% style="color:blue" %)**Sensor Console Output when Uplink:**
551
552 [[image:image-20230807233631-1.png]]
553
554
555 (% style="color:blue" %)**See result in TCP Server:**
556
557 [[image:image-20230807233631-2.png]]

Applications

Navigation

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