Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 104.4
edited by Xiaoling
on 2023/10/07 10:25
Change comment: There is no comment for this version
To version 99.2
edited by Xiaoling
on 2023/08/11 11:43
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,20 +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 -
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 -
57 -
58 58  = 3. Configure to connect to different servers =
59 59  
60 60  == 3.1 General UDP Connection ==
... ... @@ -118,7 +118,7 @@
118 118  
119 119  [[image:image-20230802112413-4.png]]
120 120  
121 -[[image:image-20230802112413-5.png||height="530" width="987"]]
101 +[[image:image-20230802112413-5.png]]
122 122  
123 123  (% 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.**
124 124  
... ... @@ -130,7 +130,7 @@
130 130  
131 131  [[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.
132 132  
133 -[[image:image-20230802112413-6.png||height="336" width="925"]]
113 +[[image:image-20230802112413-6.png]]
134 134  
135 135  [[image:image-20230802112413-7.png]]
136 136  
... ... @@ -154,8 +154,6 @@
154 154  
155 155  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
156 156  
157 -
158 -
159 159  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
160 160  
161 161  
... ... @@ -175,7 +175,7 @@
175 175  
176 176  (% style="color:blue" %)**Result: **
177 177  
178 -[[image:image-20230802112413-11.png||height="539" width="901"]]
156 +[[image:image-20230802112413-11.png]]
179 179  
180 180  
181 181  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -185,7 +185,7 @@
185 185  
186 186  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
187 187  
188 -* (% 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**
189 189  
190 190  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
191 191  
... ... @@ -197,12 +197,10 @@
197 197  
198 198  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
199 199  
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,41 +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 -
265 -== 3.4 [[Datacake>>https://datacake.co/]] ==
266 -
267 -
268 -(% class="wikigeneratedid" %)
269 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
270 -
271 -
272 -(% class="wikigeneratedid" %)
273 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
274 -
275 -* (% 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.
276 -
277 -* (% 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.
278 -
279 -
280 -
281 281  === 3.4.1 Create device ===
282 282  
283 283  
284 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
244 +[[image:image-20230808162301-1.png]]
285 285  
286 -[[image:image-20230808162301-1.png||height="473" width="994"]]
287 287  
288 -
289 289  [[image:image-20230808162342-2.png]]
290 290  
291 291  
292 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
293 -
294 294  [[image:image-20230808162421-3.png]]
295 295  
296 296  
297 -(% 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.
298 298  
299 299  [[image:image-20230808163612-7.png]]
300 300  
... ... @@ -308,7 +308,7 @@
308 308  
309 309  Users can use their phones or computers to scan QR codes to obtain device data information.
310 310  
311 -[[image:image-20230808170051-8.png||height="255" width="259"]]
267 +[[image:image-20230808170051-8.png]]
312 312  
313 313  [[image:image-20230808170548-9.png]]
314 314  
... ... @@ -341,7 +341,6 @@
341 341  
342 342  [[image:image-20230809173127-4.png]]
343 343  
344 -
345 345  Please select the NB95S31B template.
346 346  
347 347  [[image:image-20230809173310-5.png]]
... ... @@ -350,7 +350,6 @@
350 350  
351 351  [[image:image-20230809173800-7.png]]
352 352  
353 -
354 354  Successfully imported template.
355 355  
356 356  [[image:image-20230809173835-8.png]]
... ... @@ -360,10 +360,8 @@
360 360  
361 361  [[image:image-20230809174053-9.png]]
362 362  
363 -
364 364  === 3.5.2 Simulate Connection ===
365 365  
366 -
367 367  We have completed the configuration of UDP. We can try sending packets to node red.
368 368  
369 369  [[image:image-20230810083934-1.png]]
... ... @@ -373,12 +373,13 @@
373 373  === 3.5.3 Configure NB-IoT Sensors ===
374 374  
375 375  
376 -* (% 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**
377 377  
378 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
330 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   (%%) ~/~/  Set Server IP and  port**
379 379  
380 380  
381 381  
334 +
382 382  == 3.6 ThingsBoard.Cloud (via MQTT) ==
383 383  
384 384  === 3.6.1 Configure ThingsBoard ===
... ... @@ -523,17 +523,13 @@
523 523  
524 524  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
525 525  
526 -
527 -
528 528  === 3.7.2 Simulate with MQTT.fx ===
529 529  
530 -
531 531  [[image:image-20230802112413-52.png]]
532 532  
533 533  
534 534  [[image:image-20230808105300-2.png]]
535 535  
536 -
537 537  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
538 538  
539 539  [[image:image-20230808105217-1.png]]
... ... @@ -549,6 +549,7 @@
549 549  [[image:image-20230802112413-51.png||height="184" width="696"]]
550 550  
551 551  
501 +
552 552  == 3.8 TCP Connection ==
553 553  
554 554  
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content