Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 105.1
edited by Edwin Chen
on 2023/11/05 08:49
Change comment: There is no comment for this version
To version 99.1
edited by Edwin Chen
on 2023/08/10 12:36
Change comment: There is no comment for this version

Summary

Details

Page properties
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,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,22 +41,6 @@
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 -
45 -== 2.2 Speed Up Network Attach time ==
46 -
47 -
48 -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.
49 -
50 -(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
51 -
52 -(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
53 -
54 -(% style="color:#037691" %)**AT+QBAND=2,8,20**  (%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
55 -
56 -
57 -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/]]**
58 -
59 -
60 60  = 3. Configure to connect to different servers =
61 61  
62 62  == 3.1 General UDP Connection ==
... ... @@ -120,7 +120,7 @@
120 120  
121 121  [[image:image-20230802112413-4.png]]
122 122  
123 -[[image:image-20230802112413-5.png||height="530" width="987"]]
101 +[[image:image-20230802112413-5.png]]
124 124  
125 125  (% 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.**
126 126  
... ... @@ -132,7 +132,7 @@
132 132  
133 133  [[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.
134 134  
135 -[[image:image-20230802112413-6.png||height="336" width="925"]]
113 +[[image:image-20230802112413-6.png]]
136 136  
137 137  [[image:image-20230802112413-7.png]]
138 138  
... ... @@ -156,7 +156,6 @@
156 156  
157 157  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
158 158  
159 -
160 160  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
161 161  
162 162  
... ... @@ -176,7 +176,7 @@
176 176  
177 177  (% style="color:blue" %)**Result: **
178 178  
179 -[[image:image-20230802112413-11.png||height="539" width="901"]]
156 +[[image:image-20230802112413-11.png]]
180 180  
181 181  
182 182  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -186,7 +186,7 @@
186 186  
187 187  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
188 188  
189 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
166 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) **~/~/ Set to use ThingSpeak Server and Related Payload**
190 190  
191 191  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
192 192  
... ... @@ -198,11 +198,10 @@
198 198  
199 199  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
200 200  
201 -
202 202  ==== 3.3.3.2 Uplink Examples ====
203 203  
204 204  
205 -[[image:image-20230816201942-1.png]]
181 +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"]]
212 +[[image:image-20230802112413-12.png]]
237 237  
238 -[[image:image-20230802112413-13.png||height="331" width="978"]]
214 +[[image:image-20230802112413-13.png]]
239 239  
240 240  
241 241  Below is the NB-IoT Product Table show the mapping.
... ... @@ -260,39 +260,21 @@
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  
239 +== 3.4 Datacake ==
263 263  
264 -== 3.4 [[Datacake>>https://datacake.co/]] ==
265 -
266 -
267 -(% class="wikigeneratedid" %)
268 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
269 -
270 -
271 -(% class="wikigeneratedid" %)
272 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
273 -
274 -* (% 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.
275 -
276 -* (% 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.
277 -
278 -
279 279  === 3.4.1 Create device ===
280 280  
281 281  
282 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
244 +[[image:image-20230808162301-1.png]]
283 283  
284 -[[image:image-20230808162301-1.png||height="473" width="994"]]
285 285  
286 -
287 287  [[image:image-20230808162342-2.png]]
288 288  
289 289  
290 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
291 -
292 292  [[image:image-20230808162421-3.png]]
293 293  
294 294  
295 -(% 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.
253 +The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
296 296  
297 297  [[image:image-20230808163612-7.png]]
298 298  
... ... @@ -306,7 +306,7 @@
306 306  
307 307  Users can use their phones or computers to scan QR codes to obtain device data information.
308 308  
309 -[[image:image-20230808170051-8.png||height="255" width="259"]]
267 +[[image:image-20230808170051-8.png]]
310 310  
311 311  [[image:image-20230808170548-9.png]]
312 312  
... ... @@ -339,7 +339,6 @@
339 339  
340 340  [[image:image-20230809173127-4.png]]
341 341  
342 -
343 343  Please select the NB95S31B template.
344 344  
345 345  [[image:image-20230809173310-5.png]]
... ... @@ -348,7 +348,6 @@
348 348  
349 349  [[image:image-20230809173800-7.png]]
350 350  
351 -
352 352  Successfully imported template.
353 353  
354 354  [[image:image-20230809173835-8.png]]
... ... @@ -358,10 +358,8 @@
358 358  
359 359  [[image:image-20230809174053-9.png]]
360 360  
361 -
362 362  === 3.5.2 Simulate Connection ===
363 363  
364 -
365 365  We have completed the configuration of UDP. We can try sending packets to node red.
366 366  
367 367  [[image:image-20230810083934-1.png]]
... ... @@ -371,11 +371,10 @@
371 371  === 3.5.3 Configure NB-IoT Sensors ===
372 372  
373 373  
374 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
328 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)**(%%)    **~/~/  Set to UDP Server and  Payload**
375 375  
376 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
330 +* **AT+SERVADDR=xx.xx.xx.xx,port   ** **~/~/  Set Server IP and  port**
377 377  
378 -
379 379  == 3.6 ThingsBoard.Cloud (via MQTT) ==
380 380  
381 381  === 3.6.1 Configure ThingsBoard ===
... ... @@ -520,16 +520,13 @@
520 520  
521 521  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
522 522  
523 -
524 524  === 3.7.2 Simulate with MQTT.fx ===
525 525  
526 -
527 527  [[image:image-20230802112413-52.png]]
528 528  
529 529  
530 530  [[image:image-20230808105300-2.png]]
531 531  
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 535  [[image:image-20230808105217-1.png]]
... ... @@ -545,6 +545,7 @@
545 545  [[image:image-20230802112413-51.png||height="184" width="696"]]
546 546  
547 547  
498 +
548 548  == 3.8 TCP Connection ==
549 549  
550 550  
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content