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

Applications

Navigation

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