Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 107.1
edited by Edwin Chen
on 2023/12/30 17:09
Change comment: There is no comment for this version
To version 100.4
edited by Xiaoling
on 2023/08/15 17:06
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,21 +268,23 @@
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  
265 +
266 +
277 277  === 3.4.1 Create device ===
278 278  
279 279  
280 280  (% style="color:blue" %)**Add Device**(%%) in DataCake.
281 281  
282 -[[image:image-20230808162301-1.png||height="453" width="952"]]
272 +[[image:image-20230808162301-1.png]]
283 283  
284 284  
285 -[[image:image-20230808162342-2.png||height="541" width="952"]]
275 +[[image:image-20230808162342-2.png]]
286 286  
287 287  
288 288  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -292,11 +292,11 @@
292 292  
293 293  (% 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.
294 294  
295 -[[image:image-20230808163612-7.png||height="549" width="952"]]
285 +[[image:image-20230808163612-7.png]]
296 296  
297 297  [[image:image-20230808163035-5.png]]
298 298  
299 -[[image:image-20230808163049-6.png||height="544" width="926"]]
289 +[[image:image-20230808163049-6.png]]
300 300  
301 301  
302 302  === 3.4.2 Scan QR code to obtain data ===
... ... @@ -340,7 +340,7 @@
340 340  
341 341  Please select the NB95S31B template.
342 342  
343 -[[image:image-20230809173310-5.png||height="558" width="926"]]
333 +[[image:image-20230809173310-5.png]]
344 344  
345 345  [[image:image-20230809173438-6.png]]
346 346  
... ... @@ -349,7 +349,7 @@
349 349  
350 350  Successfully imported template.
351 351  
352 -[[image:image-20230809173835-8.png||height="515" width="860"]]
342 +[[image:image-20230809173835-8.png]]
353 353  
354 354  
355 355  Users can set UDP port.
... ... @@ -364,19 +364,15 @@
364 364  
365 365  [[image:image-20230810083934-1.png]]
366 366  
367 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
357 +[[image:image-20230810084048-2.png]]
368 368  
369 -
370 370  === 3.5.3 Configure NB-IoT Sensors ===
371 371  
372 372  
373 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
374 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
375 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
376 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
377 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
378 -* (% 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
379 379  
364 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
365 +
380 380  == 3.6 ThingsBoard.Cloud (via MQTT) ==
381 381  
382 382  === 3.6.1 Configure ThingsBoard ===
... ... @@ -386,7 +386,7 @@
386 386  
387 387  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
388 388  
389 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
375 +[[image:image-20230802112413-32.png]]
390 390  
391 391  
392 392  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -398,7 +398,7 @@
398 398  
399 399  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.
400 400  
401 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
387 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
402 402  
403 403  
404 404  (% style="color:blue" %)**Downlink Converter**
... ... @@ -405,7 +405,7 @@
405 405  
406 406  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
407 407  
408 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
394 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
409 409  
410 410  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
411 411  
... ... @@ -415,14 +415,14 @@
415 415  
416 416  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**;
417 417  
418 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
404 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
419 419  
420 420  
421 421  * The next steps is to add the recently created uplink and downlink converters;
422 422  
423 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
409 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
424 424  
425 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
411 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
426 426  
427 427  
428 428  (% style="color:blue" %)**Add a topic filter:**
... ... @@ -431,7 +431,7 @@
431 431  
432 432  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
433 433  
434 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
420 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
435 435  
436 436  
437 437  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -439,7 +439,7 @@
439 439  
440 440  [[image:image-20230802112413-39.png]]
441 441  
442 -[[image:image-20230802112413-40.png||height="525" width="980"]]
428 +[[image:image-20230802112413-40.png]]
443 443  
444 444  
445 445  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -461,11 +461,11 @@
461 461  
462 462  Test Uplink by click the button for 1 second
463 463  
464 -[[image:image-20230802112413-41.png||height="496" width="828"]]
450 +[[image:image-20230802112413-41.png]]
465 465  
466 466  [[image:image-20230802112413-42.png]]
467 467  
468 -[[image:image-20230802112413-43.png||height="407" width="825"]]
454 +[[image:image-20230802112413-43.png]]
469 469  
470 470  
471 471  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -527,12 +527,12 @@
527 527  [[image:image-20230802112413-52.png]]
528 528  
529 529  
530 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
516 +[[image:image-20230808105300-2.png]]
531 531  
532 532  
533 533  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
534 534  
535 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
521 +[[image:image-20230808105217-1.png]]
536 536  
537 537  [[image:image-20230808105329-3.png]]
538 538  
... ... @@ -540,7 +540,7 @@
540 540  === 3.7.3 tago data ===
541 541  
542 542  
543 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
529 +[[image:image-20230802112413-50.png]]
544 544  
545 545  [[image:image-20230802112413-51.png||height="184" width="696"]]
546 546  
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content