Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 103.1
edited by Edwin Chen
on 2023/10/02 18:27
Change comment: There is no comment for this version
To version 93.1
edited by David Huang
on 2023/08/09 18:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.David
Content
... ... @@ -4,10 +4,6 @@
4 4  {{toc/}}
5 5  
6 6  
7 -
8 -
9 -
10 -
11 11  = 1. The use of this guideline =
12 12  
13 13  
... ... @@ -16,13 +16,12 @@
16 16  
17 17  = 2. Attach Network =
18 18  
19 -== 2.1 General Configure to attach network ==
20 20  
21 21  To attache NB-IoT sensors to NB-IoT Network, You need to:
22 22  
23 23  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
24 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>)
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 指令(%%))
26 26  
27 27  [[image:image-20230808205045-1.png||height="293" width="438"]]
28 28  
... ... @@ -31,7 +31,7 @@
31 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 32  
33 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**
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**
35 35  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
36 36  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
37 37  
... ... @@ -40,12 +40,7 @@
40 40  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
41 41  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
42 42  
43 -== 2.2 Speed Up Network Attach time ==
44 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 49  = 3. Configure to connect to different servers =
50 50  
51 51  == 3.1 General UDP Connection ==
... ... @@ -109,7 +109,7 @@
109 109  
110 110  [[image:image-20230802112413-4.png]]
111 111  
112 -[[image:image-20230802112413-5.png||height="530" width="987"]]
102 +[[image:image-20230802112413-5.png]]
113 113  
114 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 115  
... ... @@ -121,7 +121,7 @@
121 121  
122 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 123  
124 -[[image:image-20230802112413-6.png||height="336" width="925"]]
114 +[[image:image-20230802112413-6.png]]
125 125  
126 126  [[image:image-20230802112413-7.png]]
127 127  
... ... @@ -165,7 +165,7 @@
165 165  
166 166  (% style="color:blue" %)**Result: **
167 167  
168 -[[image:image-20230802112413-11.png||height="539" width="901"]]
158 +[[image:image-20230802112413-11.png]]
169 169  
170 170  
171 171  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -175,7 +175,7 @@
175 175  
176 176  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
177 177  
178 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
168 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) **~/~/ Set to use ThingSpeak Server and Related Payload**
179 179  
180 180  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
181 181  
... ... @@ -190,8 +190,9 @@
190 190  
191 191  ==== 3.3.3.2 Uplink Examples ====
192 192  
193 -[[image:image-20230816201942-1.png]]
194 194  
184 +For S31-NB
185 +
195 195  For SE01-NB
196 196  
197 197  For DDS20-NB
... ... @@ -221,9 +221,9 @@
221 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 222  
223 223  
224 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
215 +[[image:image-20230802112413-12.png]]
225 225  
226 -[[image:image-20230802112413-13.png||height="331" width="978"]]
217 +[[image:image-20230802112413-13.png]]
227 227  
228 228  
229 229  Below is the NB-IoT Product Table show the mapping.
... ... @@ -249,38 +249,21 @@
249 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 250  
251 251  
252 -== 3.4 [[Datacake>>https://datacake.co/]] ==
243 +== 3.4 Datacake ==
253 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 267  === 3.4.1 Create device ===
268 268  
269 269  
270 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
248 +[[image:image-20230808162301-1.png]]
271 271  
272 -[[image:image-20230808162301-1.png||height="473" width="994"]]
273 273  
274 -
275 275  [[image:image-20230808162342-2.png]]
276 276  
277 277  
278 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
279 -
280 280  [[image:image-20230808162421-3.png]]
281 281  
282 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.
257 +The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
284 284  
285 285  [[image:image-20230808163612-7.png]]
286 286  
... ... @@ -294,7 +294,7 @@
294 294  
295 295  Users can use their phones or computers to scan QR codes to obtain device data information.
296 296  
297 -[[image:image-20230808170051-8.png||height="255" width="259"]]
271 +[[image:image-20230808170051-8.png]]
298 298  
299 299  [[image:image-20230808170548-9.png]]
300 300  
... ... @@ -327,7 +327,6 @@
327 327  
328 328  [[image:image-20230809173127-4.png]]
329 329  
330 -
331 331  Please select the NB95S31B template.
332 332  
333 333  [[image:image-20230809173310-5.png]]
... ... @@ -336,7 +336,6 @@
336 336  
337 337  [[image:image-20230809173800-7.png]]
338 338  
339 -
340 340  Successfully imported template.
341 341  
342 342  [[image:image-20230809173835-8.png]]
... ... @@ -346,22 +346,18 @@
346 346  
347 347  [[image:image-20230809174053-9.png]]
348 348  
349 -
350 350  === 3.5.2 Simulate Connection ===
351 351  
352 -
353 353  We have completed the configuration of UDP. We can try sending packets to node red.
354 354  
355 -[[image:image-20230810083934-1.png]]
356 356  
357 -[[image:image-20230810084048-2.png]]
358 358  
359 359  === 3.5.3 Configure NB-IoT Sensors ===
360 360  
361 361  
362 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
330 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)**(%%)    **~/~/  Set to UDP Server and  Payload**
363 363  
364 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
332 +* **AT+SERVADDR=xx.xx.xx.xx,port  ** **~/~/  Set Server IP and  port**
365 365  
366 366  
367 367  == 3.6 ThingsBoard.Cloud (via MQTT) ==
... ... @@ -446,6 +446,7 @@
446 446  
447 447  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
448 448  
417 +
449 449  Test Uplink by click the button for 1 second
450 450  
451 451  [[image:image-20230802112413-41.png]]
... ... @@ -484,6 +484,7 @@
484 484  
485 485  * (% style="color:#037691" %)**Client ID: “Any value”**
486 486  
456 +
487 487  (% style="color:blue" %)**On the section User credentials, set the following information:**
488 488  
489 489  * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
... ... @@ -494,6 +494,7 @@
494 494  
495 495  * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
496 496  
467 +
497 497  (% style="color:blue" %)**AT command:**
498 498  
499 499  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -511,13 +511,11 @@
511 511  
512 512  === 3.7.2 Simulate with MQTT.fx ===
513 513  
514 -
515 515  [[image:image-20230802112413-52.png]]
516 516  
517 517  
518 518  [[image:image-20230808105300-2.png]]
519 519  
520 -
521 521  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
522 522  
523 523  [[image:image-20230808105217-1.png]]
... ... @@ -533,6 +533,7 @@
533 533  [[image:image-20230802112413-51.png||height="184" width="696"]]
534 534  
535 535  
505 +
536 536  == 3.8 TCP Connection ==
537 537  
538 538  
... ... @@ -544,6 +544,7 @@
544 544  
545 545  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
546 546  
517 +
547 547  (% style="color:blue" %)**Sensor Console Output when Uplink:**
548 548  
549 549  [[image:image-20230807233631-1.png]]
... ... @@ -552,3 +552,6 @@
552 552  (% style="color:blue" %)**See result in TCP Server:**
553 553  
554 554  [[image:image-20230807233631-2.png]]
526 +
527 +
528 +
image-20230809180523-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -63.7 KB
Content
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content