Last modified by Mengting Qiu on 2025/07/03 18:55

From version 102.2
edited by Xiaoling
on 2023/09/07 16:14
Change comment: There is no comment for this version
To version 94.1
edited by David Huang
on 2023/08/09 18:05
Change comment: Uploaded new attachment "image-20230809180523-10.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
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  
... ... @@ -21,7 +21,7 @@
21 21  
22 22  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
23 23  1. Insert the SIM card to Sensor
24 -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 指令(%%))
25 25  
26 26  [[image:image-20230808205045-1.png||height="293" width="438"]]
27 27  
... ... @@ -30,7 +30,7 @@
30 30  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.
31 31  
32 32  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
33 -|(% 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**
34 34  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
35 35  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
36 36  
... ... @@ -40,7 +40,6 @@
40 40  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
41 41  
42 42  
43 -
44 44  = 3. Configure to connect to different servers =
45 45  
46 46  == 3.1 General UDP Connection ==
... ... @@ -104,7 +104,7 @@
104 104  
105 105  [[image:image-20230802112413-4.png]]
106 106  
107 -[[image:image-20230802112413-5.png||height="530" width="987"]]
102 +[[image:image-20230802112413-5.png]]
108 108  
109 109  (% 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.**
110 110  
... ... @@ -116,7 +116,7 @@
116 116  
117 117  [[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.
118 118  
119 -[[image:image-20230802112413-6.png||height="336" width="925"]]
114 +[[image:image-20230802112413-6.png]]
120 120  
121 121  [[image:image-20230802112413-7.png]]
122 122  
... ... @@ -141,7 +141,6 @@
141 141  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
142 142  
143 143  
144 -
145 145  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
146 146  
147 147  
... ... @@ -161,7 +161,7 @@
161 161  
162 162  (% style="color:blue" %)**Result: **
163 163  
164 -[[image:image-20230802112413-11.png||height="539" width="901"]]
158 +[[image:image-20230802112413-11.png]]
165 165  
166 166  
167 167  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -171,7 +171,7 @@
171 171  
172 172  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
173 173  
174 -* (% 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**
175 175  
176 176  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
177 177  
... ... @@ -184,11 +184,11 @@
184 184  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
185 185  
186 186  
187 -
188 188  ==== 3.3.3.2 Uplink Examples ====
189 189  
190 -[[image:image-20230816201942-1.png]]
191 191  
184 +For S31-NB
185 +
192 192  For SE01-NB
193 193  
194 194  For DDS20-NB
... ... @@ -218,9 +218,9 @@
218 218  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.
219 219  
220 220  
221 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
215 +[[image:image-20230802112413-12.png]]
222 222  
223 -[[image:image-20230802112413-13.png||height="331" width="978"]]
217 +[[image:image-20230802112413-13.png]]
224 224  
225 225  
226 226  Below is the NB-IoT Product Table show the mapping.
... ... @@ -246,40 +246,21 @@
246 246  |(% 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" %)
247 247  
248 248  
243 +== 3.4 Datacake ==
249 249  
250 -== 3.4 [[Datacake>>https://datacake.co/]] ==
251 -
252 -
253 -(% class="wikigeneratedid" %)
254 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
255 -
256 -
257 -(% class="wikigeneratedid" %)
258 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
259 -
260 -* (% 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.
261 -
262 -* (% 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.
263 -
264 -
265 -
266 266  === 3.4.1 Create device ===
267 267  
268 268  
269 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
248 +[[image:image-20230808162301-1.png]]
270 270  
271 -[[image:image-20230808162301-1.png||height="473" width="994"]]
272 272  
273 -
274 274  [[image:image-20230808162342-2.png]]
275 275  
276 276  
277 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
278 -
279 279  [[image:image-20230808162421-3.png]]
280 280  
281 281  
282 -(% 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.
283 283  
284 284  [[image:image-20230808163612-7.png]]
285 285  
... ... @@ -293,7 +293,7 @@
293 293  
294 294  Users can use their phones or computers to scan QR codes to obtain device data information.
295 295  
296 -[[image:image-20230808170051-8.png||height="255" width="259"]]
271 +[[image:image-20230808170051-8.png]]
297 297  
298 298  [[image:image-20230808170548-9.png]]
299 299  
... ... @@ -326,7 +326,6 @@
326 326  
327 327  [[image:image-20230809173127-4.png]]
328 328  
329 -
330 330  Please select the NB95S31B template.
331 331  
332 332  [[image:image-20230809173310-5.png]]
... ... @@ -335,7 +335,6 @@
335 335  
336 336  [[image:image-20230809173800-7.png]]
337 337  
338 -
339 339  Successfully imported template.
340 340  
341 341  [[image:image-20230809173835-8.png]]
... ... @@ -345,25 +345,20 @@
345 345  
346 346  [[image:image-20230809174053-9.png]]
347 347  
348 -
349 349  === 3.5.2 Simulate Connection ===
350 350  
351 -
352 352  We have completed the configuration of UDP. We can try sending packets to node red.
353 353  
354 -[[image:image-20230810083934-1.png]]
355 355  
356 -[[image:image-20230810084048-2.png]]
357 357  
358 358  === 3.5.3 Configure NB-IoT Sensors ===
359 359  
360 360  
361 -* (% 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**
362 362  
363 -* (% 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**
364 364  
365 365  
366 -
367 367  == 3.6 ThingsBoard.Cloud (via MQTT) ==
368 368  
369 369  === 3.6.1 Configure ThingsBoard ===
... ... @@ -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**
... ... @@ -509,16 +509,13 @@
509 509  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
510 510  
511 511  
512 -
513 513  === 3.7.2 Simulate with MQTT.fx ===
514 514  
515 -
516 516  [[image:image-20230802112413-52.png]]
517 517  
518 518  
519 519  [[image:image-20230808105300-2.png]]
520 520  
521 -
522 522  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
523 523  
524 524  [[image:image-20230808105217-1.png]]
... ... @@ -534,6 +534,7 @@
534 534  [[image:image-20230802112413-51.png||height="184" width="696"]]
535 535  
536 536  
505 +
537 537  == 3.8 TCP Connection ==
538 538  
539 539  
... ... @@ -545,6 +545,7 @@
545 545  
546 546  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
547 547  
517 +
548 548  (% style="color:blue" %)**Sensor Console Output when Uplink:**
549 549  
550 550  [[image:image-20230807233631-1.png]]
... ... @@ -553,3 +553,6 @@
553 553  (% style="color:blue" %)**See result in TCP Server:**
554 554  
555 555  [[image:image-20230807233631-2.png]]
526 +
527 +
528 +
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