Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 126.1 >
edited by Edwin Chen
on 2024/02/02 11:48
To version < 100.3 >
edited by Xiaoling
on 2023/08/15 17:05
>
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
... ... @@ -16,9 +16,7 @@
16 16  
17 17  = 2. Attach Network =
18 18  
19 -== 2.1 General Configure to attach network ==
20 20  
21 -
22 22  To attache NB-IoT sensors to NB-IoT Network, You need to:
23 23  
24 24  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
... ... @@ -41,24 +41,8 @@
41 41  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
42 42  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
43 43  
44 -== 2.2 Speed Up Network Attach time ==
45 45  
46 46  
47 -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.
48 -
49 -(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
50 -
51 -(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
52 -
53 -(% style="color:#037691" %)**AT+QBAND=2,8,20 **(%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
54 -
55 -
56 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
57 -
58 -
59 -See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
60 -
61 -
62 62  = 3. Configure to connect to different servers =
63 63  
64 64  == 3.1 General UDP Connection ==
... ... @@ -72,7 +72,7 @@
72 72  
73 73  We can use PC tool to simulate UDP connection to make sure server works ok.
74 74  
75 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
57 +[[image:image-20230802112413-1.png]]
76 76  
77 77  
78 78  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -122,7 +122,7 @@
122 122  
123 123  [[image:image-20230802112413-4.png]]
124 124  
125 -[[image:image-20230802112413-5.png||height="530" width="987"]]
107 +[[image:image-20230802112413-5.png]]
126 126  
127 127  (% 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.**
128 128  
... ... @@ -134,7 +134,7 @@
134 134  
135 135  [[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.
136 136  
137 -[[image:image-20230802112413-6.png||height="336" width="925"]]
119 +[[image:image-20230802112413-6.png]]
138 138  
139 139  [[image:image-20230802112413-7.png]]
140 140  
... ... @@ -158,6 +158,8 @@
158 158  
159 159  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
160 160  
143 +
144 +
161 161  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
162 162  
163 163  
... ... @@ -177,7 +177,7 @@
177 177  
178 178  (% style="color:blue" %)**Result: **
179 179  
180 -[[image:image-20230802112413-11.png||height="539" width="901"]]
164 +[[image:image-20230802112413-11.png]]
181 181  
182 182  
183 183  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -199,10 +199,12 @@
199 199  
200 200  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
201 201  
186 +
187 +
202 202  ==== 3.3.3.2 Uplink Examples ====
203 203  
204 204  
205 -[[image:image-20230816201942-1.png]]
191 +For S31-NB
206 206  
207 207  For SE01-NB
208 208  
... ... @@ -233,9 +233,9 @@
233 233  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.
234 234  
235 235  
236 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
222 +[[image:image-20230802112413-12.png]]
237 237  
238 -[[image:image-20230802112413-13.png||height="331" width="978"]]
224 +[[image:image-20230802112413-13.png]]
239 239  
240 240  
241 241  Below is the NB-IoT Product Table show the mapping.
... ... @@ -260,6 +260,8 @@
260 260  |(% 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" %)
261 261  |(% 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" %)
262 262  
249 +
250 +
263 263  == 3.4 [[Datacake>>https://datacake.co/]] ==
264 264  
265 265  
... ... @@ -268,24 +268,25 @@
268 268  
269 269  
270 270  (% class="wikigeneratedid" %)
271 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
259 +As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
272 272  
273 273  * (% 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.
274 274  
275 275  * (% 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.
276 276  
277 -=== 3.4.1 For device Already has template ===
278 278  
279 -==== 3.4.1.1 Create Device ====
280 280  
281 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
267 +=== 3.4.1 Create device ===
282 282  
283 -[[image:image-20230808162301-1.png||height="453" width="952"]]
284 284  
270 +**Add Device** in DataCake.
285 285  
286 -[[image:image-20230808162342-2.png||height="541" width="952"]]
272 +[[image:image-20230808162301-1.png]]
287 287  
288 288  
275 +[[image:image-20230808162342-2.png]]
276 +
277 +
289 289  (% style="color:blue" %)**Choose the correct model**(%%) from template.
290 290  
291 291  [[image:image-20230808162421-3.png]]
... ... @@ -293,16 +293,15 @@
293 293  
294 294  (% 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.
295 295  
296 -[[image:image-20230808163612-7.png||height="549" width="952"]]
285 +[[image:image-20230808163612-7.png]]
297 297  
298 298  [[image:image-20230808163035-5.png]]
299 299  
300 -[[image:image-20230808163049-6.png||height="544" width="926"]]
289 +[[image:image-20230808163049-6.png]]
301 301  
302 302  
303 -=== 3.4.2 For Device already registered in DataCake before shipped ===
292 +=== 3.4.2 Scan QR code to obtain data ===
304 304  
305 -==== 3.4.2.1 Scan QR Code to get the device info ====
306 306  
307 307  Users can use their phones or computers to scan QR codes to obtain device data information.
308 308  
... ... @@ -311,58 +311,9 @@
311 311  [[image:image-20230808170548-9.png]]
312 312  
313 313  
314 -==== 3.4.2.2 Claim Device to User Account ====
302 +=== 3.4.2 AT command for connecting to DataCake ===
315 315  
316 -By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
317 317  
318 -
319 -
320 -=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
321 -
322 -**Step1:Add a device**
323 -
324 -[[image:image-20240129170024-1.png||height="330" width="900"]]
325 -
326 -**Step2:Choose your device type,please select dragino NB-IOT device**
327 -
328 -[[image:image-20240129170216-2.png||height="534" width="643"]]
329 -
330 -**Step3:Choose to create a new device**
331 -
332 -[[image:image-20240129170539-3.png||height="459" width="646"]]
333 -
334 -**Step4:Fill in the device ID of your NB device**
335 -
336 -[[image:image-20240202111546-1.png||height="378" width="651"]]
337 -
338 -**Step5:Please select your device plan according to your needs and complete the creation of the device**
339 -
340 -[[image:image-20240129171236-6.png||height="450" width="648"]]
341 -
342 -**Step6:Please add the decoder at the payload decoder of the device configuration.**
343 -
344 -[[image:image-20240129172056-7.png||height="457" width="816"]]
345 -
346 -[[image:image-20240129173116-9.png||height="499" width="814"]]
347 -
348 -**Step6:Add the output of the decoder as a field**
349 -
350 -[[image:image-20240129173541-10.png||height="592" width="968"]]
351 -
352 -**Step7:Customize the dashboard and use fields as parameters of the dashboard**
353 -
354 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
355 -
356 -[[image:image-20240129174657-12.png||height="538" width="916"]]
357 -
358 -[[image:image-20240129174840-13.png||height="536" width="750"]]
359 -
360 -
361 -=== 3.4.4 For device have not configured to connect to DataCake ===
362 -
363 -(% class="lead" %)
364 -Use AT command for connecting to DataCake
365 -
366 366  (% style="color:blue" %)**AT+PRO=2,0**
367 367  
368 368  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -391,7 +391,7 @@
391 391  
392 392  Please select the NB95S31B template.
393 393  
394 -[[image:image-20230809173310-5.png||height="558" width="926"]]
333 +[[image:image-20230809173310-5.png]]
395 395  
396 396  [[image:image-20230809173438-6.png]]
397 397  
... ... @@ -400,7 +400,7 @@
400 400  
401 401  Successfully imported template.
402 402  
403 -[[image:image-20230809173835-8.png||height="515" width="860"]]
342 +[[image:image-20230809173835-8.png]]
404 404  
405 405  
406 406  Users can set UDP port.
... ... @@ -415,19 +415,15 @@
415 415  
416 416  [[image:image-20230810083934-1.png]]
417 417  
418 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
357 +[[image:image-20230810084048-2.png]]
419 419  
420 -
421 421  === 3.5.3 Configure NB-IoT Sensors ===
422 422  
423 423  
424 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
425 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
426 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
427 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
428 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
429 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
362 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
430 430  
364 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
365 +
431 431  == 3.6 ThingsBoard.Cloud (via MQTT) ==
432 432  
433 433  === 3.6.1 Configure ThingsBoard ===
... ... @@ -437,7 +437,7 @@
437 437  
438 438  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
439 439  
440 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
375 +[[image:image-20230802112413-32.png]]
441 441  
442 442  
443 443  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -449,7 +449,7 @@
449 449  
450 450  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.
451 451  
452 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
387 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
453 453  
454 454  
455 455  (% style="color:blue" %)**Downlink Converter**
... ... @@ -456,7 +456,7 @@
456 456  
457 457  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
458 458  
459 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
394 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
460 460  
461 461  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
462 462  
... ... @@ -466,23 +466,23 @@
466 466  
467 467  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**;
468 468  
469 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
404 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
470 470  
471 471  
472 472  * The next steps is to add the recently created uplink and downlink converters;
473 473  
474 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
409 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
475 475  
476 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
411 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
477 477  
478 478  
479 479  (% style="color:blue" %)**Add a topic filter:**
480 480  
481 -Consistent with the theme of the node setting.
416 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
482 482  
483 483  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
484 484  
485 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
420 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
486 486  
487 487  
488 488  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -490,7 +490,7 @@
490 490  
491 491  [[image:image-20230802112413-39.png]]
492 492  
493 -[[image:image-20230802112413-40.png||height="525" width="980"]]
428 +[[image:image-20230802112413-40.png]]
494 494  
495 495  
496 496  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -512,11 +512,11 @@
512 512  
513 513  Test Uplink by click the button for 1 second
514 514  
515 -[[image:image-20230802112413-41.png||height="496" width="828"]]
450 +[[image:image-20230802112413-41.png]]
516 516  
517 517  [[image:image-20230802112413-42.png]]
518 518  
519 -[[image:image-20230802112413-43.png||height="407" width="825"]]
454 +[[image:image-20230802112413-43.png]]
520 520  
521 521  
522 522  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -578,12 +578,12 @@
578 578  [[image:image-20230802112413-52.png]]
579 579  
580 580  
581 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
516 +[[image:image-20230808105300-2.png]]
582 582  
583 583  
584 584  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
585 585  
586 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
521 +[[image:image-20230808105217-1.png]]
587 587  
588 588  [[image:image-20230808105329-3.png]]
589 589  
... ... @@ -591,7 +591,7 @@
591 591  === 3.7.3 tago data ===
592 592  
593 593  
594 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
529 +[[image:image-20230802112413-50.png]]
595 595  
596 596  [[image:image-20230802112413-51.png||height="184" width="696"]]
597 597  
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content
image-20240129170024-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -33.3 KB
Content

Applications

Navigation

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