Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 100.1
edited by Edwin Chen
on 2023/08/12 22:37
Change comment: There is no comment for this version
To version 105.2
edited by Xiaoling
on 2023/11/06 16:16
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,10 @@
4 4  {{toc/}}
5 5  
6 6  
7 +
8 +
9 +
10 +
7 7  = 1. The use of this guideline =
8 8  
9 9  
... ... @@ -12,7 +12,9 @@
12 12  
13 13  = 2. Attach Network =
14 14  
19 +== 2.1 General Configure to attach network ==
15 15  
21 +
16 16  To attache NB-IoT sensors to NB-IoT Network, You need to:
17 17  
18 18  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
... ... @@ -36,6 +36,22 @@
36 36  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
37 37  
38 38  
45 +
46 +== 2.2 Speed Up Network Attach time ==
47 +
48 +
49 +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.
50 +
51 +(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
52 +
53 +(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
54 +
55 +(% style="color:#037691" %)**AT+QBAND=2,8,20**  (%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
56 +
57 +
58 +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/]]**
59 +
60 +
39 39  = 3. Configure to connect to different servers =
40 40  
41 41  == 3.1 General UDP Connection ==
... ... @@ -49,7 +49,7 @@
49 49  
50 50  We can use PC tool to simulate UDP connection to make sure server works ok.
51 51  
52 -[[image:image-20230802112413-1.png]]
74 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
53 53  
54 54  
55 55  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -99,7 +99,7 @@
99 99  
100 100  [[image:image-20230802112413-4.png]]
101 101  
102 -[[image:image-20230802112413-5.png]]
124 +[[image:image-20230802112413-5.png||height="530" width="987"]]
103 103  
104 104  (% 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.**
105 105  
... ... @@ -111,7 +111,7 @@
111 111  
112 112  [[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.
113 113  
114 -[[image:image-20230802112413-6.png]]
136 +[[image:image-20230802112413-6.png||height="336" width="925"]]
115 115  
116 116  [[image:image-20230802112413-7.png]]
117 117  
... ... @@ -136,6 +136,7 @@
136 136  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
137 137  
138 138  
161 +
139 139  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
140 140  
141 141  
... ... @@ -155,7 +155,7 @@
155 155  
156 156  (% style="color:blue" %)**Result: **
157 157  
158 -[[image:image-20230802112413-11.png]]
181 +[[image:image-20230802112413-11.png||height="539" width="901"]]
159 159  
160 160  
161 161  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -178,10 +178,11 @@
178 178  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
179 179  
180 180  
204 +
181 181  ==== 3.3.3.2 Uplink Examples ====
182 182  
183 183  
184 -For S31-NB
208 +[[image:image-20230816201942-1.png]]
185 185  
186 186  For SE01-NB
187 187  
... ... @@ -212,9 +212,9 @@
212 212  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.
213 213  
214 214  
215 -[[image:image-20230802112413-12.png]]
239 +[[image:image-20230802112413-12.png||height="504" width="1011"]]
216 216  
217 -[[image:image-20230802112413-13.png]]
241 +[[image:image-20230802112413-13.png||height="331" width="978"]]
218 218  
219 219  
220 220  Below is the NB-IoT Product Table show the mapping.
... ... @@ -240,6 +240,7 @@
240 240  |(% 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" %)
241 241  
242 242  
267 +
243 243  == 3.4 [[Datacake>>https://datacake.co/]] ==
244 244  
245 245  
... ... @@ -248,35 +248,37 @@
248 248  
249 249  
250 250  (% class="wikigeneratedid" %)
251 -As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
276 +As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
252 252  
253 -* **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.
254 -* **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.
278 +* (% 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.
255 255  
280 +* (% 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.
256 256  
282 +
283 +
257 257  === 3.4.1 Create device ===
258 258  
259 259  
260 -**Add Device** in DataCake.
287 +(% style="color:blue" %)**Add Device**(%%) in DataCake.
261 261  
262 -[[image:image-20230808162301-1.png]]
289 +[[image:image-20230808162301-1.png||height="453" width="952"]]
263 263  
264 264  
265 -[[image:image-20230808162342-2.png]]
292 +[[image:image-20230808162342-2.png||height="541" width="952"]]
266 266  
267 267  
268 -**Choose the correct model** from template.
295 +(% style="color:blue" %)**Choose the correct model**(%%) from template.
269 269  
270 270  [[image:image-20230808162421-3.png]]
271 271  
272 272  
273 -**Fill Device ID**. The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
300 +(% 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.
274 274  
275 -[[image:image-20230808163612-7.png]]
302 +[[image:image-20230808163612-7.png||height="549" width="952"]]
276 276  
277 277  [[image:image-20230808163035-5.png]]
278 278  
279 -[[image:image-20230808163049-6.png]]
306 +[[image:image-20230808163049-6.png||height="544" width="926"]]
280 280  
281 281  
282 282  === 3.4.2 Scan QR code to obtain data ===
... ... @@ -320,7 +320,7 @@
320 320  
321 321  Please select the NB95S31B template.
322 322  
323 -[[image:image-20230809173310-5.png]]
350 +[[image:image-20230809173310-5.png||height="558" width="926"]]
324 324  
325 325  [[image:image-20230809173438-6.png]]
326 326  
... ... @@ -329,7 +329,7 @@
329 329  
330 330  Successfully imported template.
331 331  
332 -[[image:image-20230809173835-8.png]]
359 +[[image:image-20230809173835-8.png||height="515" width="860"]]
333 333  
334 334  
335 335  Users can set UDP port.
... ... @@ -344,8 +344,9 @@
344 344  
345 345  [[image:image-20230810083934-1.png]]
346 346  
347 -[[image:image-20230810084048-2.png]]
374 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
348 348  
376 +
349 349  === 3.5.3 Configure NB-IoT Sensors ===
350 350  
351 351  
... ... @@ -354,6 +354,7 @@
354 354  * (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
355 355  
356 356  
385 +
357 357  == 3.6 ThingsBoard.Cloud (via MQTT) ==
358 358  
359 359  === 3.6.1 Configure ThingsBoard ===
... ... @@ -363,7 +363,7 @@
363 363  
364 364  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
365 365  
366 -[[image:image-20230802112413-32.png]]
395 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
367 367  
368 368  
369 369  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -375,7 +375,7 @@
375 375  
376 376  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.
377 377  
378 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
407 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
379 379  
380 380  
381 381  (% style="color:blue" %)**Downlink Converter**
... ... @@ -382,7 +382,7 @@
382 382  
383 383  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
384 384  
385 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
414 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
386 386  
387 387  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
388 388  
... ... @@ -392,14 +392,14 @@
392 392  
393 393  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**;
394 394  
395 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
424 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
396 396  
397 397  
398 398  * The next steps is to add the recently created uplink and downlink converters;
399 399  
400 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
429 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
401 401  
402 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
431 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
403 403  
404 404  
405 405  (% style="color:blue" %)**Add a topic filter:**
... ... @@ -408,7 +408,7 @@
408 408  
409 409  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
410 410  
411 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
440 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
412 412  
413 413  
414 414  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -416,7 +416,7 @@
416 416  
417 417  [[image:image-20230802112413-39.png]]
418 418  
419 -[[image:image-20230802112413-40.png]]
448 +[[image:image-20230802112413-40.png||height="525" width="980"]]
420 420  
421 421  
422 422  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -438,11 +438,11 @@
438 438  
439 439  Test Uplink by click the button for 1 second
440 440  
441 -[[image:image-20230802112413-41.png]]
470 +[[image:image-20230802112413-41.png||height="496" width="828"]]
442 442  
443 443  [[image:image-20230802112413-42.png]]
444 444  
445 -[[image:image-20230802112413-43.png]]
474 +[[image:image-20230802112413-43.png||height="407" width="825"]]
446 446  
447 447  
448 448  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -499,6 +499,7 @@
499 499  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
500 500  
501 501  
531 +
502 502  === 3.7.2 Simulate with MQTT.fx ===
503 503  
504 504  
... ... @@ -505,12 +505,12 @@
505 505  [[image:image-20230802112413-52.png]]
506 506  
507 507  
508 -[[image:image-20230808105300-2.png]]
538 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
509 509  
510 510  
511 511  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
512 512  
513 -[[image:image-20230808105217-1.png]]
543 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
514 514  
515 515  [[image:image-20230808105329-3.png]]
516 516  
... ... @@ -518,7 +518,7 @@
518 518  === 3.7.3 tago data ===
519 519  
520 520  
521 -[[image:image-20230802112413-50.png]]
551 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
522 522  
523 523  [[image:image-20230802112413-51.png||height="184" width="696"]]
524 524  
... ... @@ -534,6 +534,8 @@
534 534  
535 535  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
536 536  
567 +
568 +
537 537  (% style="color:blue" %)**Sensor Console Output when Uplink:**
538 538  
539 539  [[image:image-20230807233631-1.png]]
... ... @@ -542,3 +542,4 @@
542 542  (% style="color:blue" %)**See result in TCP Server:**
543 543  
544 544  [[image:image-20230807233631-2.png]]
577 +
image-20230816201942-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content