Last modified by Mengting Qiu on 2025/07/03 18:55
From version 104.1
edited by Edwin Chen
on 2023/10/02 18:30
on 2023/10/02 18:30
Change comment:
There is no comment for this version
To version 97.1
edited by David Huang
on 2023/08/10 08:40
on 2023/08/10 08:40
Change comment:
Uploaded new attachment "image-20230810084048-2.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +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" %)**A T+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,21 +40,6 @@ 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 -(% class="wikigeneratedid" %) 44 -== == 45 - 46 -== 2.2 Speed Up Network Attach time == 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 -**AT+QBAND?** ~/~/ Check what is the current used frequency band 51 - 52 -**AT+QBAND=1,4** ~/~/ Set to use 1 frequency band. Band4 53 - 54 -**AT+QBAND=2,8,20** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20 55 - 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 ... ... @@ -173,7 +173,7 @@ 173 173 174 174 (% style="color:blue" %)**Result: ** 175 175 176 -[[image:image-20230802112413-11.png ||height="539" width="901"]]156 +[[image:image-20230802112413-11.png]] 177 177 178 178 179 179 === 3.3.3 Configure NB-IoT Sensor for connection === ... ... @@ -183,7 +183,7 @@ 183 183 184 184 In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx 185 185 186 -* (% 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** 187 187 188 188 * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>** 189 189 ... ... @@ -197,8 +197,9 @@ 197 197 198 198 ==== 3.3.3.2 Uplink Examples ==== 199 199 200 -[[image:image-20230816201942-1.png]] 201 201 181 +For S31-NB 182 + 202 202 For SE01-NB 203 203 204 204 For DDS20-NB ... ... @@ -228,9 +228,9 @@ 228 228 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. 229 229 230 230 231 -[[image:image-20230802112413-12.png ||height="504" width="1011"]]212 +[[image:image-20230802112413-12.png]] 232 232 233 -[[image:image-20230802112413-13.png ||height="331" width="978"]]214 +[[image:image-20230802112413-13.png]] 234 234 235 235 236 236 Below is the NB-IoT Product Table show the mapping. ... ... @@ -255,37 +255,21 @@ 255 255 |(% 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" %) 256 256 |(% 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" %) 257 257 258 -== 3.4 [[Datacake>>https://datacake.co/]]==239 +== 3.4 Datacake == 259 259 260 - 261 -(% class="wikigeneratedid" %) 262 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor, 263 - 264 - 265 -(% class="wikigeneratedid" %) 266 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.** 267 - 268 -* (% 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. 269 - 270 -* (% 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. 271 - 272 272 === 3.4.1 Create device === 273 273 274 274 275 - (% style="color:blue" %)**Add Device**(%%) in DataCake.244 +[[image:image-20230808162301-1.png]] 276 276 277 -[[image:image-20230808162301-1.png||height="473" width="994"]] 278 278 279 - 280 280 [[image:image-20230808162342-2.png]] 281 281 282 282 283 -(% style="color:blue" %)**Choose the correct model**(%%) from template. 284 - 285 285 [[image:image-20230808162421-3.png]] 286 286 287 287 288 - (% 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. 289 289 290 290 [[image:image-20230808163612-7.png]] 291 291 ... ... @@ -299,7 +299,7 @@ 299 299 300 300 Users can use their phones or computers to scan QR codes to obtain device data information. 301 301 302 -[[image:image-20230808170051-8.png ||height="255" width="259"]]267 +[[image:image-20230808170051-8.png]] 303 303 304 304 [[image:image-20230808170548-9.png]] 305 305 ... ... @@ -332,7 +332,6 @@ 332 332 333 333 [[image:image-20230809173127-4.png]] 334 334 335 - 336 336 Please select the NB95S31B template. 337 337 338 338 [[image:image-20230809173310-5.png]] ... ... @@ -341,7 +341,6 @@ 341 341 342 342 [[image:image-20230809173800-7.png]] 343 343 344 - 345 345 Successfully imported template. 346 346 347 347 [[image:image-20230809173835-8.png]] ... ... @@ -351,22 +351,19 @@ 351 351 352 352 [[image:image-20230809174053-9.png]] 353 353 354 - 355 355 === 3.5.2 Simulate Connection === 356 356 357 - 358 358 We have completed the configuration of UDP. We can try sending packets to node red. 359 359 360 -[[image:image-202308 10083934-1.png]]321 +[[image:image-20230809180523-10.png]] 361 361 362 -[[image:image-20230810084048-2.png]] 363 363 364 364 === 3.5.3 Configure NB-IoT Sensors === 365 365 366 366 367 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format) **~/~/ Set to UDP Server and Payload327 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)**(%%) **~/~/ Set to UDP Server and Payload** 368 368 369 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port **(%%)**329 +* **AT+SERVADDR=xx.xx.xx.xx,port ** **~/~/ Set Server IP and port** 370 370 371 371 == 3.6 ThingsBoard.Cloud (via MQTT) == 372 372 ... ... @@ -514,13 +514,11 @@ 514 514 515 515 === 3.7.2 Simulate with MQTT.fx === 516 516 517 - 518 518 [[image:image-20230802112413-52.png]] 519 519 520 520 521 521 [[image:image-20230808105300-2.png]] 522 522 523 - 524 524 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**. 525 525 526 526 [[image:image-20230808105217-1.png]] ... ... @@ -536,6 +536,7 @@ 536 536 [[image:image-20230802112413-51.png||height="184" width="696"]] 537 537 538 538 497 + 539 539 == 3.8 TCP Connection == 540 540 541 541 ... ... @@ -555,3 +555,5 @@ 555 555 (% style="color:blue" %)**See result in TCP Server:** 556 556 557 557 [[image:image-20230807233631-2.png]] 517 + 518 +
- image-20230816201942-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -99.8 KB - Content