Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 83.7
edited by Xiaoling
on 2023/08/09 10:50
Change comment: There is no comment for this version
To version 104.2
edited by Xiaoling
on 2023/10/07 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
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,12 +12,13 @@
12 12  
13 13  = 2. Attach Network =
14 14  
19 +== 2.1 General Configure to attach network ==
15 15  
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)
19 19  1. Insert the SIM card to Sensor
20 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (% class="mark" %)(补充 APN 指令(%%))
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>)
21 21  
22 22  [[image:image-20230808205045-1.png||height="293" width="438"]]
23 23  
... ... @@ -26,7 +26,7 @@
26 26  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.
27 27  
28 28  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
29 -|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
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**
30 30  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
31 31  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
32 32  
... ... @@ -35,6 +35,20 @@
35 35  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
36 36  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
37 37  
43 +(% class="wikigeneratedid" %)
44 +== ==
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 +
38 38  = 3. Configure to connect to different servers =
39 39  
40 40  == 3.1 General UDP Connection ==
... ... @@ -98,7 +98,7 @@
98 98  
99 99  [[image:image-20230802112413-4.png]]
100 100  
101 -[[image:image-20230802112413-5.png]]
120 +[[image:image-20230802112413-5.png||height="530" width="987"]]
102 102  
103 103  (% 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.**
104 104  
... ... @@ -110,7 +110,7 @@
110 110  
111 111  [[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.
112 112  
113 -[[image:image-20230802112413-6.png]]
132 +[[image:image-20230802112413-6.png||height="336" width="925"]]
114 114  
115 115  [[image:image-20230802112413-7.png]]
116 116  
... ... @@ -153,7 +153,7 @@
153 153  
154 154  (% style="color:blue" %)**Result: **
155 155  
156 -[[image:image-20230802112413-11.png]]
175 +[[image:image-20230802112413-11.png||height="539" width="901"]]
157 157  
158 158  
159 159  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -175,13 +175,10 @@
175 175  
176 176  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
177 177  
178 -
179 -
180 180  ==== 3.3.3.2 Uplink Examples ====
181 181  
199 +[[image:image-20230816201942-1.png]]
182 182  
183 -For S31-NB
184 -
185 185  For SE01-NB
186 186  
187 187  For DDS20-NB
... ... @@ -211,9 +211,9 @@
211 211  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.
212 212  
213 213  
214 -[[image:image-20230802112413-12.png]]
230 +[[image:image-20230802112413-12.png||height="504" width="1011"]]
215 215  
216 -[[image:image-20230802112413-13.png]]
232 +[[image:image-20230802112413-13.png||height="331" width="978"]]
217 217  
218 218  
219 219  Below is the NB-IoT Product Table show the mapping.
... ... @@ -238,21 +238,37 @@
238 238  |(% 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" %)
239 239  |(% 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" %)
240 240  
241 -== 3.4 Datacake ==
257 +== 3.4 [[Datacake>>https://datacake.co/]] ==
242 242  
259 +
260 +(% class="wikigeneratedid" %)
261 +Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
262 +
263 +
264 +(% class="wikigeneratedid" %)
265 +As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
266 +
267 +* (% 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.
268 +
269 +* (% 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.
270 +
243 243  === 3.4.1 Create device ===
244 244  
245 245  
246 -[[image:image-20230808162301-1.png]]
274 +(% style="color:blue" %)**Add Device**(%%) in DataCake.
247 247  
276 +[[image:image-20230808162301-1.png||height="473" width="994"]]
248 248  
278 +
249 249  [[image:image-20230808162342-2.png]]
250 250  
251 251  
282 +(% style="color:blue" %)**Choose the correct model**(%%) from template.
283 +
252 252  [[image:image-20230808162421-3.png]]
253 253  
254 254  
255 -The device ID needs to be filled in with IMEI, and a prefix of 'f' needs to be added.
287 +(% 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.
256 256  
257 257  [[image:image-20230808163612-7.png]]
258 258  
... ... @@ -266,7 +266,7 @@
266 266  
267 267  Users can use their phones or computers to scan QR codes to obtain device data information.
268 268  
269 -[[image:image-20230808170051-8.png]]
301 +[[image:image-20230808170051-8.png||height="255" width="259"]]
270 270  
271 271  [[image:image-20230808170548-9.png]]
272 272  
... ... @@ -284,33 +284,57 @@
284 284  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
285 285  
286 286  
287 -[[image:image-20230802112413-29.png]]
319 +Take S31-NB UDP protocol as an example.
288 288  
321 +Dragino provides input flow examples for the sensors.
289 289  
290 -[[image:image-20230802112413-30.png]]
323 +User can download the required JSON file through Dragino Node-RED input flow template.
291 291  
325 +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]]
292 292  
293 -=== 3.5.2 Simulate Connection ===
327 +We can directly import the template.
294 294  
329 +The templates for S31-NB and NB95S31B are the same.
295 295  
296 -[[image:image-20230802112413-31.png]]
297 297  
332 +[[image:image-20230809173127-4.png]]
298 298  
299 -=== 3.5.3 Configure NB-IoT Sensors ===
300 300  
335 +Please select the NB95S31B template.
301 301  
302 -* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    ~/~/  Set to mqtt Server and  Payload
337 +[[image:image-20230809173310-5.png]]
303 303  
304 -* (% style="color:blue" %)**AT+CLIENT=any value**
339 +[[image:image-20230809173438-6.png]]
305 305  
306 -* (% style="color:blue" %)**AT+UNAME=any value**
341 +[[image:image-20230809173800-7.png]]
307 307  
308 -* (% style="color:blue" %)**AT+PWD=any value**
309 309  
310 -* (% style="color:blue" %)**AT+PUBTOPIC=any value**
344 +Successfully imported template.
311 311  
312 -* (% style="color:blue" %)**AT+SUBTOPIC=any value**
346 +[[image:image-20230809173835-8.png]]
313 313  
348 +
349 +Users can set UDP port.
350 +
351 +[[image:image-20230809174053-9.png]]
352 +
353 +
354 +=== 3.5.2 Simulate Connection ===
355 +
356 +
357 +We have completed the configuration of UDP. We can try sending packets to node red.
358 +
359 +[[image:image-20230810083934-1.png]]
360 +
361 +[[image:image-20230810084048-2.png]]
362 +
363 +=== 3.5.3 Configure NB-IoT Sensors ===
364 +
365 +
366 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
367 +
368 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
369 +
314 314  == 3.6 ThingsBoard.Cloud (via MQTT) ==
315 315  
316 316  === 3.6.1 Configure ThingsBoard ===
... ... @@ -341,7 +341,7 @@
341 341  
342 342  [[image:image-20230802112413-34.png||height="734" width="1305"]]
343 343  
344 -(% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
400 +(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
345 345  
346 346  
347 347  ==== 3.6.1.3 MQTT Integration Setup ====
... ... @@ -421,29 +421,29 @@
421 421  
422 422  The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
423 423  
424 -On the Connection Profile window, set the following information:
480 +(% style="color:blue" %)**On the Connection Profile window, set the following information:**
425 425  
426 -* (% style="color:blue" %)**Profile Name: “Any name”**
482 +* (% style="color:#037691" %)**Profile Name: “Any name”**
427 427  
428 -* (% style="color:blue" %)**Broker Address: mqtt.tago.io**
484 +* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
429 429  
430 -* (% style="color:blue" %)**Broker Port: 8883**
486 +* (% style="color:#037691" %)**Broker Port: 8883**
431 431  
432 -* (% style="color:blue" %)**Client ID: “Any value”**
488 +* (% style="color:#037691" %)**Client ID: “Any value”**
433 433  
434 -On the section User credentials, set the following information:
490 +(% style="color:blue" %)**On the section User credentials, set the following information:**
435 435  
436 -* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only
492 +* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
437 437  
438 -* (% style="color:blue" %)**Password: “Your device token”**
494 +* (% style="color:#037691" %)**Password: “Your device token”**
439 439  
440 -* (% style="color:blue" %)**PUBTOPIC: “Any value”**
496 +* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
441 441  
442 -* (% style="color:blue" %)**SUBTOPIC: “Any value”**
498 +* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
443 443  
444 444  (% style="color:blue" %)**AT command:**
445 445  
446 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) ~/~/ hex format or json format
502 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
447 447  
448 448  * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
449 449  
... ... @@ -455,16 +455,15 @@
455 455  
456 456  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
457 457  
458 -
459 -
460 -
461 461  === 3.7.2 Simulate with MQTT.fx ===
462 462  
516 +
463 463  [[image:image-20230802112413-52.png]]
464 464  
465 465  
466 466  [[image:image-20230808105300-2.png]]
467 467  
522 +
468 468  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
469 469  
470 470  [[image:image-20230808105217-1.png]]
... ... @@ -480,7 +480,6 @@
480 480  [[image:image-20230802112413-51.png||height="184" width="696"]]
481 481  
482 482  
483 -
484 484  == 3.8 TCP Connection ==
485 485  
486 486  
... ... @@ -490,10 +490,8 @@
490 490  
491 491  * (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
492 492  
493 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
547 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
494 494  
495 -
496 -
497 497  (% style="color:blue" %)**Sensor Console Output when Uplink:**
498 498  
499 499  [[image:image-20230807233631-1.png]]
... ... @@ -502,6 +502,3 @@
502 502  (% style="color:blue" %)**See result in TCP Server:**
503 503  
504 504  [[image:image-20230807233631-2.png]]
505 -
506 -
507 -
image-20230809165928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +74.4 KB
Content
image-20230809170225-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20230809170532-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +38.7 KB
Content
image-20230809173127-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +82.5 KB
Content
image-20230809173310-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
image-20230809173438-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +41.0 KB
Content
image-20230809173800-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +46.8 KB
Content
image-20230809173835-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +88.8 KB
Content
image-20230809174053-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.0 KB
Content
image-20230809180523-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +63.7 KB
Content
image-20230816201942-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content