Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 11 removed)
Details
- Page properties
-
- Content
-
... ... @@ -54,6 +54,7 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 57 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -81,6 +81,7 @@ 81 81 * Max boost current: 2A, 1 second 82 82 83 83 85 + 84 84 == 1.4 Applications == 85 85 86 86 * Smart Buildings & Home Automation ... ... @@ -130,6 +130,7 @@ 130 130 131 131 132 132 135 + 133 133 = 2. Use N95S31B to communicate with IoT Server = 134 134 135 135 == 2.1 How it works == ... ... @@ -173,6 +173,7 @@ 173 173 * The local NB-IoT network used the band that N95S31B supports. 174 174 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 175 175 179 + 176 176 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 177 177 178 178 N95S31B supports different communication protocol such as : ... ... @@ -192,7 +192,7 @@ 192 192 193 193 194 194 195 -=== 2.2. 3Insert SIM card ===199 +=== 2.2.2 Insert SIM card === 196 196 197 197 ((( 198 198 Insert the NB-IoT Card get from your provider. ... ... @@ -203,19 +203,19 @@ 203 203 ))) 204 204 205 205 206 -[[image:16573 51240556-536.png]]210 +[[image:1657328884227-504.png]] 207 207 208 208 209 209 210 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===214 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 211 211 212 212 ((( 213 213 ((( 214 -User need to configure 95S31Bvia serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31Bsupport AT Commands, user can use a USB to TTL adapter to connect to95S31Band use AT Commands to configure it, as below.218 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. 215 215 ))) 216 216 ))) 217 217 218 -[[image: 1657351312545-300.png]]222 +[[image:image-20220709092052-2.png]] 219 219 220 220 **Connection:** 221 221 ... ... @@ -235,18 +235,18 @@ 235 235 * Flow Control: (% style="color:green" %)**None** 236 236 237 237 ((( 238 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.242 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 239 239 ))) 240 240 241 241 [[image:1657329814315-101.png]] 242 242 243 243 ((( 244 -(% style="color:red" %)Note: the valid AT Commands can be found at: 95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]248 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 245 245 ))) 246 246 247 247 248 248 249 -=== 2.2. 5Use CoAP protocol to uplink data ===253 +=== 2.2.4 Use CoAP protocol to uplink data === 250 250 251 251 (% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 252 252 ... ... @@ -266,12 +266,10 @@ 266 266 ))) 267 267 268 268 ((( 269 - 270 - 271 271 For parameter description, please refer to AT command set 272 272 ))) 273 273 274 -[[image:1657352 146020-183.png]]276 +[[image:1657330452568-615.png]] 275 275 276 276 277 277 ((( ... ... @@ -278,11 +278,11 @@ 278 278 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server. 279 279 ))) 280 280 281 -[[image:16573 52185396-303.png]]283 +[[image:1657330472797-498.png]] 282 282 283 283 284 284 285 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 286 286 287 287 288 288 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -289,16 +289,15 @@ 289 289 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 290 290 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 291 291 292 -[[image:16573 52391268-297.png]]294 +[[image:1657330501006-241.png]] 293 293 294 294 295 -[[image:16573 52403317-397.png]]297 +[[image:1657330533775-472.png]] 296 296 297 297 298 298 299 -=== 2.2. 7Use MQTT protocol to uplink data ===301 +=== 2.2.6 Use MQTT protocol to uplink data === 300 300 301 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 302 302 303 303 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 304 304 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -305,40 +305,35 @@ 305 305 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 306 306 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 307 307 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 308 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527309 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)309 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 310 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 310 310 311 -[[image:1657 352634421-276.png]]312 +[[image:1657249978444-674.png]] 312 312 313 313 314 -[[image:16573 52645687-385.png]]315 +[[image:1657330723006-866.png]] 315 315 316 -((( 317 -To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 318 -))) 319 319 320 - 321 321 ((( 322 -MQTT protocol has a much high -power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.319 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 323 323 ))) 324 324 325 325 326 326 327 -=== 2.2. 8Use TCP protocol to uplink data ===324 +=== 2.2.7 Use TCP protocol to uplink data === 328 328 329 -This feature is supported since firmware version v110 330 330 331 331 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 332 332 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 333 333 334 -[[image: 1657352898400-901.png]]330 +[[image:image-20220709093918-1.png]] 335 335 336 336 337 -[[image: 1657352914475-252.png]]333 +[[image:image-20220709093918-2.png]] 338 338 339 339 340 340 341 -=== 2.2. 9Change Update Interval ===337 +=== 2.2.8 Change Update Interval === 342 342 343 343 User can use below command to change the (% style="color:green" %)**uplink interval**. 344 344 ... ... @@ -345,69 +345,32 @@ 345 345 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 346 346 347 347 ((( 348 - 344 +(% style="color:red" %)**NOTE:** 349 349 ))) 350 350 347 +((( 348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 349 +))) 351 351 352 352 352 + 353 353 == 2.3 Uplink Payload == 354 354 355 +In this mode, uplink payload includes in total 14 bytes 355 355 356 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 357 357 358 - 359 -For example: 360 - 361 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 362 - 363 - 364 -The uplink payloads are composed in ASCII String. For example: 365 - 366 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 367 - 368 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 369 - 370 - 371 -(% style="color:red" %)**NOTE:** 372 - 373 -(% style="color:red" %) 374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 375 -1. By default, the device will send an uplink message every 1 hour. 376 - 377 - 378 - 379 - 380 -=== 2.3.1 Payload Analyze === 381 - 382 -N95S31B uplink payload includes in total 21 bytes 383 - 384 - 385 385 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 386 386 |=(% style="width: 60px;" %)((( 387 387 **Size(bytes)** 388 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 389 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 390 -Reserve/ Same as NBSN95 CFGMOD=1 361 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 362 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 391 391 392 -No function here. 393 -)))|(% style="width:77px" %)((( 394 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 395 - 396 -By SHT31 397 -)))|(% style="width:80px" %)((( 398 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 399 - 400 -By SHT31 401 -))) 402 - 403 403 ((( 404 -((( 405 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 365 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 406 406 ))) 407 -))) 408 408 409 409 410 -[[image:16573 54294009-643.png]]369 +[[image:1657331036973-987.png]] 411 411 412 412 ((( 413 413 The payload is ASCII string, representative same HEX:
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content