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
on 2023/11/05 08:49
Change comment:
There is no comment for this version
To version 100.1
edited by Edwin Chen
on 2023/08/12 22:37
on 2023/08/12 22:37
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
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) ... ... @@ -42,21 +42,6 @@ 42 42 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %) 43 43 44 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"]]102 +[[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"]]114 +[[image:image-20230802112413-6.png]] 136 136 137 137 [[image:image-20230802112413-7.png]] 138 138 ... ... @@ -176,7 +176,7 @@ 176 176 177 177 (% style="color:blue" %)**Result: ** 178 178 179 -[[image:image-20230802112413-11.png ||height="539" width="901"]]158 +[[image:image-20230802112413-11.png]] 180 180 181 181 182 182 === 3.3.3 Configure NB-IoT Sensor for connection === ... ... @@ -202,7 +202,7 @@ 202 202 ==== 3.3.3.2 Uplink Examples ==== 203 203 204 204 205 - [[image:image-20230816201942-1.png]]184 +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"]]215 +[[image:image-20230802112413-12.png]] 237 237 238 -[[image:image-20230802112413-13.png ||height="331" width="978"]]217 +[[image:image-20230802112413-13.png]] 239 239 240 240 241 241 Below is the NB-IoT Product Table show the mapping. ... ... @@ -269,30 +269,29 @@ 269 269 270 270 271 271 (% class="wikigeneratedid" %) 272 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**251 +As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE. 273 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. 253 +* **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. 254 +* **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. 275 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 277 278 - 279 279 === 3.4.1 Create device === 280 280 281 281 282 - (% style="color:blue" %)**Add Device**(%%)in DataCake.260 +**Add Device** in DataCake. 283 283 284 -[[image:image-20230808162301-1.png ||height="473" width="994"]]262 +[[image:image-20230808162301-1.png]] 285 285 286 286 287 287 [[image:image-20230808162342-2.png]] 288 288 289 289 290 - (% style="color:blue" %)**Choose the correct model**(%%)from template.268 +**Choose the correct model** from template. 291 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.273 +**Fill Device ID**. 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
- image-20230816201942-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -99.8 KB - Content