Last modified by Mengting Qiu on 2025/03/08 11:33
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Edwin - Content
-
... ... @@ -4,6 +4,10 @@ 4 4 {{toc/}} 5 5 6 6 7 + 8 + 9 + 10 + 7 7 = 1. The use of this guideline = 8 8 9 9 ... ... @@ -12,12 +12,13 @@ 12 12 13 13 = 2. Attach Network = 14 14 19 +== 2.1 General Configure to attach network == 15 15 16 16 To attache NB-IoT sensors to NB-IoT Network, You need to: 17 17 18 18 1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone) 19 19 1. Insert the SIM card to Sensor 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 +1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>) 21 21 22 22 [[image:image-20230808205045-1.png||height="293" width="438"]] 23 23 ... ... @@ -26,7 +26,7 @@ 26 26 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. 27 27 28 28 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %) 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 +|(% 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** 30 30 |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)((( 31 31 **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]** 32 32 ... ... @@ -35,6 +35,12 @@ 35 35 |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %) 36 36 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %) 37 37 43 +== 2.2 Speed Up Network Attach time == 44 + 45 +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. 46 + 47 + 48 + 38 38 = 3. Configure to connect to different servers = 39 39 40 40 == 3.1 General UDP Connection == ... ... @@ -98,7 +98,7 @@ 98 98 99 99 [[image:image-20230802112413-4.png]] 100 100 101 -[[image:image-20230802112413-5.png]] 112 +[[image:image-20230802112413-5.png||height="530" width="987"]] 102 102 103 103 (% 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.** 104 104 ... ... @@ -110,7 +110,7 @@ 110 110 111 111 [[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. 112 112 113 -[[image:image-20230802112413-6.png]] 124 +[[image:image-20230802112413-6.png||height="336" width="925"]] 114 114 115 115 [[image:image-20230802112413-7.png]] 116 116 ... ... @@ -134,6 +134,7 @@ 134 134 135 135 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 136 136 148 + 137 137 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 138 138 139 139 ... ... @@ -153,7 +153,7 @@ 153 153 154 154 (% style="color:blue" %)**Result: ** 155 155 156 -[[image:image-20230802112413-11.png]] 168 +[[image:image-20230802112413-11.png||height="539" width="901"]] 157 157 158 158 159 159 === 3.3.3 Configure NB-IoT Sensor for connection === ... ... @@ -163,7 +163,7 @@ 163 163 164 164 In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx 165 165 166 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) **~/~/ Set to use ThingSpeak Server and Related Payload**178 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload 167 167 168 168 * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>** 169 169 ... ... @@ -175,11 +175,11 @@ 175 175 176 176 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 177 177 190 + 178 178 ==== 3.3.3.2 Uplink Examples ==== 179 179 193 +[[image:image-20230816201942-1.png]] 180 180 181 -For S31-NB 182 - 183 183 For SE01-NB 184 184 185 185 For DDS20-NB ... ... @@ -209,9 +209,9 @@ 209 209 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. 210 210 211 211 212 -[[image:image-20230802112413-12.png]] 224 +[[image:image-20230802112413-12.png||height="504" width="1011"]] 213 213 214 -[[image:image-20230802112413-13.png]] 226 +[[image:image-20230802112413-13.png||height="331" width="978"]] 215 215 216 216 217 217 Below is the NB-IoT Product Table show the mapping. ... ... @@ -236,21 +236,39 @@ 236 236 |(% 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" %) 237 237 |(% 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" %) 238 238 239 -== 3.4 Datacake == 240 240 252 +== 3.4 [[Datacake>>https://datacake.co/]] == 253 + 254 + 255 +(% class="wikigeneratedid" %) 256 +Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor, 257 + 258 + 259 +(% class="wikigeneratedid" %) 260 +As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.** 261 + 262 +* (% 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. 263 + 264 +* (% 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. 265 + 266 + 241 241 === 3.4.1 Create device === 242 242 243 243 244 - [[image:image-20230808162301-1.png]]270 +(% style="color:blue" %)**Add Device**(%%) in DataCake. 245 245 272 +[[image:image-20230808162301-1.png||height="473" width="994"]] 246 246 274 + 247 247 [[image:image-20230808162342-2.png]] 248 248 249 249 278 +(% style="color:blue" %)**Choose the correct model**(%%) from template. 279 + 250 250 [[image:image-20230808162421-3.png]] 251 251 252 252 253 -The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added. 283 +(% 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. 254 254 255 255 [[image:image-20230808163612-7.png]] 256 256 ... ... @@ -264,7 +264,7 @@ 264 264 265 265 Users can use their phones or computers to scan QR codes to obtain device data information. 266 266 267 -[[image:image-20230808170051-8.png]] 297 +[[image:image-20230808170051-8.png||height="255" width="259"]] 268 268 269 269 [[image:image-20230808170548-9.png]] 270 270 ... ... @@ -297,6 +297,7 @@ 297 297 298 298 [[image:image-20230809173127-4.png]] 299 299 330 + 300 300 Please select the NB95S31B template. 301 301 302 302 [[image:image-20230809173310-5.png]] ... ... @@ -305,6 +305,7 @@ 305 305 306 306 [[image:image-20230809173800-7.png]] 307 307 339 + 308 308 Successfully imported template. 309 309 310 310 [[image:image-20230809173835-8.png]] ... ... @@ -314,20 +314,24 @@ 314 314 315 315 [[image:image-20230809174053-9.png]] 316 316 349 + 317 317 === 3.5.2 Simulate Connection === 318 318 352 + 319 319 We have completed the configuration of UDP. We can try sending packets to node red. 320 320 321 -[[image:image-202308 09180523-10.png]]355 +[[image:image-20230810083934-1.png]] 322 322 357 +[[image:image-20230810084048-2.png]] 323 323 324 324 === 3.5.3 Configure NB-IoT Sensors === 325 325 326 326 327 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)**(%%) **362 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format) **(%%)** **~/~/ Set to UDP Server and Payload 328 328 329 -* **AT+SERVADDR=xx.xx.xx.xx,port ** **~/~/ Set Server IP and port **364 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port **(%%)** **~/~/ Set Server IP and port 330 330 366 + 331 331 == 3.6 ThingsBoard.Cloud (via MQTT) == 332 332 333 333 === 3.6.1 Configure ThingsBoard === ... ... @@ -472,13 +472,16 @@ 472 472 473 473 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 474 474 511 + 475 475 === 3.7.2 Simulate with MQTT.fx === 476 476 514 + 477 477 [[image:image-20230802112413-52.png]] 478 478 479 479 480 480 [[image:image-20230808105300-2.png]] 481 481 520 + 482 482 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**. 483 483 484 484 [[image:image-20230808105217-1.png]] ... ... @@ -494,7 +494,6 @@ 494 494 [[image:image-20230802112413-51.png||height="184" width="696"]] 495 495 496 496 497 - 498 498 == 3.8 TCP Connection == 499 499 500 500 ... ... @@ -514,5 +514,3 @@ 514 514 (% style="color:blue" %)**See result in TCP Server:** 515 515 516 516 [[image:image-20230807233631-2.png]] 517 - 518 -
- image-20230816201942-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +99.8 KB - Content