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, 1 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 : ... ... @@ -305,8 +305,8 @@ 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=f9527 309 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 310 310 311 311 [[image:1657352634421-276.png]] 312 312 ... ... @@ -352,62 +352,21 @@ 352 352 353 353 == 2.3 Uplink Payload == 354 354 359 +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 365 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 366 +|(% 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. 369 +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]]373 +[[image:1657331036973-987.png]] 411 411 412 412 ((( 413 413 The payload is ASCII string, representative same HEX:
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content