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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 18 added, 0 removed)
- 1657348034241-728.png
- 1657348284168-431.png
- 1657350248151-650.png
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- 1657352914475-252.png
- 1657354294009-643.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N DDS75 NB-IoTDistanceDetect Sensor User Manual1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual - Content
-
... ... @@ -1,10 +1,12 @@ 1 1 (% style="text-align:center" %) 2 -[[image: image-20220709085040-1.png||height="542" width="524"]]2 +[[image:1657348034241-728.png||height="470" width="470"]] 3 3 4 4 5 5 6 6 7 7 8 + 9 + 8 8 **Table of Contents:** 9 9 10 10 {{toc/}} ... ... @@ -13,65 +13,54 @@ 13 13 14 14 15 15 16 - 17 17 = 1. Introduction = 18 18 19 -== 1.1 What is N DDS75Distance DetectionSensor ==20 +== 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 24 24 ((( 25 -((( 26 -The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data. 26 +The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 27 27 ))) 28 28 29 29 ((( 30 - 31 -The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 30 +The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 32 32 ))) 33 33 34 34 ((( 35 - 36 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 34 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 37 37 ))) 38 38 39 39 ((( 40 - 41 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 38 +N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 42 42 ))) 43 43 44 44 ((( 45 - 46 -NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 42 + 47 47 ))) 48 48 49 49 ((( 50 - 51 -To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 46 +~* make sure you have NB-IoT coverage locally. 52 52 ))) 53 -))) 54 54 55 55 56 56 ))) 57 57 58 -[[image:165732 7959271-447.png]]52 +[[image:1657348284168-431.png]] 59 59 60 60 61 61 62 62 == 1.2 Features == 63 63 64 - 65 65 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 66 -* Ultra low power consumption 67 -* Distance Detection by Ultrasonic technology 68 -* Flat object range 280mm - 7500mm 69 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 70 -* Cable Length: 25cm 59 +* Monitor Temperature & Humidity via SHT31 71 71 * AT Commands to change parameters 72 72 * Uplink on periodically 73 73 * Downlink to change configure 74 74 * IP66 Waterproof Enclosure 64 +* Ultra-Low Power consumption 65 +* AT Commands to change parameters 75 75 * Micro SIM card slot for NB-IoT SIM 76 76 * 8500mAh Battery for long term use 77 77 ... ... @@ -101,12 +101,7 @@ 101 101 * Max continuously current: 130mA 102 102 * Max boost current: 2A, 1 second 103 103 104 -(% style="color:#037691" %)**Power Consumption** 105 105 106 -* STOP Mode: 10uA @ 3.3v 107 -* Max transmit power: 350mA@3.3v 108 - 109 - 110 110 == 1.4 Applications == 111 111 112 112 * Smart Buildings & Home Automation ... ... @@ -120,24 +120,57 @@ 120 120 121 121 122 122 123 -== 1.5 Pin Definitions == 109 +== 1.5 Pin Definitions & Switch == 124 124 111 +N95S31B use the mother board from NBSN95 which as below. 125 125 126 -[[image: 1657328609906-564.png]]113 +[[image:image-20220709144723-1.png]] 127 127 128 128 116 +=== 1.5.1 Jumper JP2 === 129 129 130 - = 2. UseNDDS75 tocommunicate withIoTServer =118 +Power on Device when put this jumper. 131 131 120 + 121 + 122 +=== 1.5.2 BOOT MODE / SW1 === 123 + 124 +((( 125 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 126 +))) 127 + 128 +((( 129 +2) Flash: work mode, device starts to work and send out console output for further debug 130 +))) 131 + 132 + 133 + 134 +=== 1.5.3 Reset Button === 135 + 136 +Press to reboot the device. 137 + 138 + 139 + 140 +=== 1.5.4 LED === 141 + 142 +It will flash: 143 + 144 +1. When boot the device in flash mode 145 +1. Send an uplink packet 146 + 147 + 148 += 2. Use N95S31B to communicate with IoT Server = 149 + 132 132 == 2.1 How it works == 133 133 152 + 134 134 ((( 135 -The N DDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.154 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B. 136 136 ))) 137 137 138 138 139 139 ((( 140 -The diagram below shows the working flow in default firmware of N DDS75:159 +The diagram below shows the working flow in default firmware of N95S31B: 141 141 ))) 142 142 143 143 ((( ... ... @@ -144,7 +144,7 @@ 144 144 145 145 ))) 146 146 147 -[[image:1657328 659945-416.png]]166 +[[image:1657350248151-650.png]] 148 148 149 149 ((( 150 150 ... ... @@ -151,30 +151,67 @@ 151 151 ))) 152 152 153 153 154 -== 2.2 Configure the N DDS75 ==173 +== 2.2 Configure the N95S31B == 155 155 156 156 176 +=== 2.2.1 Power On N95S31B === 177 + 178 + 179 +[[image:image-20220709150546-2.png]] 180 + 181 + 157 157 === 2.2.1 Test Requirement === 158 158 184 + 159 159 ((( 160 -To use N DDS75 in your city, make sure meet below requirements:186 +To use N95S31B in your city, make sure meet below requirements: 161 161 ))) 162 162 163 -* Your local operator has already distributed a NB-IoT Network there. 164 -* The local NB-IoT network used the band that NSE01 supports. 165 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 189 +* ((( 190 +Your local operator has already distributed a NB-IoT Network there. 191 +))) 192 +* ((( 193 +The local NB-IoT network used the band that N95S31B supports. 194 +))) 195 +* ((( 196 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 197 +))) 166 166 167 167 ((( 168 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server200 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 169 169 ))) 170 170 203 +((( 204 +N95S31B supports different communication protocol such as : 205 +))) 171 171 172 -[[image:1657328756309-230.png]] 207 +((( 208 +* ((( 209 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 210 +))) 211 +* ((( 212 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 213 +))) 214 +* ((( 215 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 216 +))) 217 +* ((( 218 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 219 +))) 173 173 221 +((( 222 +We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server. 223 +))) 174 174 225 + 226 +))) 175 175 176 - ===2.2.2 Insert SIM card ===228 +[[image:1657350625843-586.png]] 177 177 230 + 231 + 232 +=== 2.2.3 Insert SIM card === 233 + 178 178 ((( 179 179 Insert the NB-IoT Card get from your provider. 180 180 ))) ... ... @@ -184,19 +184,19 @@ 184 184 ))) 185 185 186 186 187 -[[image:165732 8884227-504.png]]243 +[[image:1657351240556-536.png]] 188 188 189 189 190 190 191 -=== 2.2. 3DDS75 to configure it ===247 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 192 192 193 193 ((( 194 194 ((( 195 -User need to configure DDS75 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 toDDS75 and use AT Commands to configure it, as below.251 +User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 196 196 ))) 197 197 ))) 198 198 199 -[[image: image-20220709092052-2.png]]255 +[[image:1657351312545-300.png]] 200 200 201 201 **Connection:** 202 202 ... ... @@ -216,18 +216,18 @@ 216 216 * Flow Control: (% style="color:green" %)**None** 217 217 218 218 ((( 219 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N DDS75.DDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.275 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 220 220 ))) 221 221 222 222 [[image:1657329814315-101.png]] 223 223 224 224 ((( 225 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]281 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 226 226 ))) 227 227 228 228 229 229 230 -=== 2.2. 4286 +=== 2.2.5 Use CoAP protocol to uplink data === 231 231 232 232 (% 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/]] 233 233 ... ... @@ -247,10 +247,12 @@ 247 247 ))) 248 248 249 249 ((( 306 + 307 + 250 250 For parameter description, please refer to AT command set 251 251 ))) 252 252 253 -[[image:16573 30452568-615.png]]311 +[[image:1657352146020-183.png]] 254 254 255 255 256 256 ((( ... ... @@ -257,11 +257,11 @@ 257 257 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. 258 258 ))) 259 259 260 -[[image:16573 30472797-498.png]]318 +[[image:1657352185396-303.png]] 261 261 262 262 263 263 264 -=== 2.2. 5322 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 265 265 266 266 267 267 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -268,15 +268,16 @@ 268 268 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 269 269 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 270 270 271 -[[image:16573 30501006-241.png]]329 +[[image:1657352391268-297.png]] 272 272 273 273 274 -[[image:16573 30533775-472.png]]332 +[[image:1657352403317-397.png]] 275 275 276 276 277 277 278 -=== 2.2. 6336 +=== 2.2.7 Use MQTT protocol to uplink data === 279 279 338 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 280 280 281 281 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 282 282 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -283,35 +283,40 @@ 283 283 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 284 284 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 285 285 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 286 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT287 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT345 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 346 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 288 288 289 -[[image:165724 9978444-674.png]]348 +[[image:1657352634421-276.png]] 290 290 291 291 292 -[[image:16573 30723006-866.png]]351 +[[image:1657352645687-385.png]] 293 293 353 +((( 354 +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. 355 +))) 294 294 357 + 295 295 ((( 296 -MQTT protocol has a much high erpower consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.359 +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. 297 297 ))) 298 298 299 299 300 300 301 -=== 2.2. 7364 +=== 2.2.8 Use TCP protocol to uplink data === 302 302 366 +This feature is supported since firmware version v110 303 303 304 304 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 305 305 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 306 306 307 -[[image: image-20220709093918-1.png]]371 +[[image:1657352898400-901.png]] 308 308 309 309 310 -[[image: image-20220709093918-2.png]]374 +[[image:1657352914475-252.png]] 311 311 312 312 313 313 314 -=== 2.2. 8378 +=== 2.2.9 Change Update Interval === 315 315 316 316 User can use below command to change the (% style="color:green" %)**uplink interval**. 317 317 ... ... @@ -318,162 +318,156 @@ 318 318 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 319 319 320 320 ((( 321 - (%style="color:red" %)**NOTE:**385 + 322 322 ))) 323 323 324 -((( 325 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 326 -))) 327 327 328 328 329 - 330 330 == 2.3 Uplink Payload == 331 331 332 -In this mode, uplink payload includes in total 14 bytes 333 333 393 +((( 394 +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. 395 +))) 334 334 335 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 336 -|=(% style="width: 60px;" %)((( 337 -**Size(bytes)** 338 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 339 -|(% 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"]] 340 340 341 341 ((( 342 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.399 +For example: 343 343 ))) 344 344 402 +((( 403 + (% 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. 404 +))) 345 345 346 -[[image:1657331036973-987.png]] 347 347 348 348 ((( 349 -The payload is ASCIIstring,representative sameHEX:408 +The uplink payloads are composed in ASCII String. For example: 350 350 ))) 351 351 352 352 ((( 353 -0 x72403155615900640c6c19029200where:412 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 354 354 ))) 355 355 356 - *(((357 - DeviceID:0x724031556159=724031556159415 +((( 416 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 358 358 ))) 359 -* ((( 360 -Version: 0x0064=100=1.0.0 418 + 419 + 420 +((( 421 +(% style="color:red" %)**NOTE:** 361 361 ))) 362 362 363 -* ((( 364 -BAT: 0x0c6c = 3180 mV = 3.180V 424 +(% style="color:red" %) 425 +1. ((( 426 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 365 365 ))) 366 - *(((367 - Signal:0x19=25428 +1. ((( 429 +By default, the device will send an uplink message every 1 hour. 368 368 ))) 369 -* ((( 370 -Distance: 0x0292= 658 mm 371 -))) 372 -* ((( 373 -Interrupt: 0x00 = 0 374 374 375 375 433 +=== 2.3.1 Payload Analyze === 376 376 377 - 378 -))) 435 +N95S31B uplink payload includes in total 21 bytes 379 379 380 -== 2.4 Payload Explanation and Sensor Interface == 381 381 382 - 383 -=== 2.4.1 Device ID === 384 - 438 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 439 +|=(% style="width: 60px;" %)((( 440 +**Size(bytes)** 441 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 442 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 385 385 ((( 386 - By default, theDeviceID equal to thelast6bytes of IMEI.444 +Reserve/ Same as NBSN95 CFGMOD=1 387 387 ))) 388 388 389 389 ((( 390 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID448 +No function here. 391 391 ))) 392 - 450 +)))|(% style="width:77px" %)((( 393 393 ((( 394 - **Example:**452 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 395 395 ))) 396 396 397 397 ((( 398 - AT+DEUI=A84041F15612456 +By SHT31 399 399 ))) 400 - 458 +)))|(% style="width:80px" %)((( 401 401 ((( 402 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.460 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 403 403 ))) 404 404 405 - 406 - 407 -=== 2.4.2 Version Info === 408 - 409 409 ((( 410 - Specifythe software version: 0x64=100, means firmware version 1.00.464 +By SHT31 411 411 ))) 466 +))) 412 412 413 413 ((( 414 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 469 +((( 470 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 415 415 ))) 472 +))) 416 416 417 417 475 +[[image:1657354294009-643.png]] 418 418 419 -=== 2.4.3 Battery Info === 420 420 421 -((( 422 -Ex1: 0x0B45 = 2885mV 423 -))) 478 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 424 424 425 -((( 426 -Ex2: 0x0B49 = 2889mV 427 -))) 480 +* Device ID: 0x724031607457 = 724031607457 481 +* Version: 0x006e=110=1.1.0 428 428 483 +* BAT: 0x0ccd = 3277 mV = 3.277V 484 +* Signal: 0x1b = 27 485 +* Model: 0x01 = 1 486 +* 0x00dc000ccc= reserve, ignore in N95S31B 487 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 488 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 429 429 430 - 431 -=== 2.4.4 Signal Strength === 432 - 433 433 ((( 434 - NB-IoTNetwork signal Strength.491 + 435 435 ))) 436 436 437 437 ((( 438 - **Ex1:0x1d = 29**495 + 439 439 ))) 440 440 498 + 499 +=== 2.3.2 Device ID === 500 + 441 441 ((( 442 - (% style="color:blue"%)**0**(%%)-113dBmorless502 +By default, the Device ID equal to the last 6 bytes of IMEI. 443 443 ))) 444 444 445 445 ((( 446 -(% style="color:blue" %)** 1**(%%)-111dBm506 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 447 447 ))) 448 448 449 449 ((( 450 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm510 +**Example:** 451 451 ))) 452 452 453 453 ((( 454 - (% style="color:blue" %)**31** (%%) -51dBm or greater514 +AT+DEUI=A84041F15612 455 455 ))) 456 456 457 457 ((( 458 - (%style="color:blue"%)**99**(%%)Notknownor notdetectable518 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 459 459 ))) 460 460 461 461 462 462 463 -=== 2. 4.5Distance===523 +=== 2.3.3 Version Info === 464 464 465 -Get the distance. Flat object range 280mm - 7500mm. 525 +((( 526 +These bytes include the hardware and software version. 527 +))) 466 466 467 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 468 - 469 469 ((( 470 -((( 471 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 530 +Higher byte: Specify hardware version: always 0x00 for N95S31B 472 472 ))) 473 -))) 474 474 475 475 ((( 476 - 534 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 477 477 ))) 478 478 479 479 ((( ... ... @@ -480,63 +480,79 @@ 480 480 481 481 ))) 482 482 483 -=== 2.4.6 Digital Interrupt === 484 - 485 485 ((( 486 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.542 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 487 487 ))) 488 488 489 489 ((( 490 - Thecommand is:546 + 491 491 ))) 492 492 549 + 550 +=== 2.3.4 Battery Info === 551 + 493 493 ((( 494 - (% style="color:blue"%)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**553 +Ex1: 0x0B45 = 2885mV 495 495 ))) 496 496 497 - 498 498 ((( 499 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.557 +Ex2: 0x0B49 = 2889mV 500 500 ))) 501 501 502 502 561 + 562 +=== 2.3.5 Signal Strength === 563 + 503 503 ((( 504 - Example:565 +NB-IoT Network signal Strength. 505 505 ))) 506 506 507 507 ((( 508 - 0x(00):Normaluplinkpacket.569 +**Ex1: 0x1d = 29** 509 509 ))) 510 510 511 511 ((( 512 - 0x(01):InterruptUplinkPacket.573 +(% style="color:blue" %)**0**(%%) -113dBm or less 513 513 ))) 514 514 515 - 516 - 517 -=== 2.4.7 +5V Output === 518 - 519 519 ((( 520 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.577 +(% style="color:blue" %)**1**(%%) -111dBm 521 521 ))) 522 522 523 - 524 524 ((( 525 - The5V output timean be controlledbyAT Command.581 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 526 526 ))) 527 527 528 528 ((( 529 -(% style="color:blue" %)** AT+5VT=1000**585 +(% style="color:blue" %)**31** (%%) -51dBm or greater 530 530 ))) 531 531 532 532 ((( 533 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.589 +(% style="color:blue" %)**99** (%%) Not known or not detectable 534 534 ))) 535 535 536 536 537 537 538 -== 2. 5Downlink Payload ==594 +=== 2.3.6 Temperature & Humidity === 539 539 596 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 597 + 598 +[[image:image-20220709161741-3.png]] 599 + 600 + 601 +Convert the read byte to decimal and divide it by ten. 602 + 603 + 604 +**Example:** 605 + 606 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 607 + 608 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 609 + 610 + 611 + 612 +== 2.4 Downlink Payload == 613 + 540 540 By default, NDDS75 prints the downlink payload to console port. 541 541 542 542 [[image:image-20220709100028-1.png]] ... ... @@ -587,47 +587,16 @@ 587 587 588 588 589 589 590 -== 2. 6LED Indicator ==664 +== 2.5 Battery Analysis == 591 591 666 +=== 2.5.1 Battery Type === 592 592 593 -The NDDS75 has an internal LED which is to show the status of different state. 594 594 595 - 596 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 597 -* Then the LED will be on for 1 second means device is boot normally. 598 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 599 -* For each uplink probe, LED will be on for 500ms. 600 - 601 601 ((( 602 - 670 +The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 603 603 ))) 604 604 605 - 606 - 607 -== 2.7 Firmware Change Log == 608 - 609 - 610 -Download URL & Firmware Change log 611 - 612 612 ((( 613 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 614 -))) 615 - 616 - 617 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 618 - 619 - 620 - 621 -== 2.8 Battery Analysis == 622 - 623 -=== 2.8.1 Battery Type === 624 - 625 - 626 -((( 627 -The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 628 -))) 629 - 630 -((( 631 631 The battery is designed to last for several years depends on the actually use environment and update interval. 632 632 ))) 633 633 ... ... @@ -645,56 +645,35 @@ 645 645 646 646 647 647 648 -=== 2. 8.2 Power consumption Analyze ===691 +=== 2.5.2 Power consumption Analyze === 649 649 650 650 ((( 651 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.694 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 652 652 ))) 653 653 654 - 655 655 ((( 656 - Instructionto use as below:698 + 657 657 ))) 658 658 659 -((( 660 -(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 661 -))) 662 662 702 +=== 2.5.3 Battery Note === 663 663 664 664 ((( 665 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose705 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased. 666 666 ))) 667 667 668 -* ((( 669 -Product Model 670 -))) 671 -* ((( 672 -Uplink Interval 673 -))) 674 -* ((( 675 -Working Mode 676 -))) 677 677 678 -((( 679 -And the Life expectation in difference case will be shown on the right. 680 -))) 681 681 682 - [[image:image-20220709110451-3.png]]710 +=== 2.5.4 Replace the battery === 683 683 684 684 685 - 686 -=== 2.8.3 Battery Note === 687 - 688 688 ((( 689 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.714 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 690 690 ))) 691 691 692 692 693 - 694 -=== 2.8.4 Replace the battery === 695 - 696 696 ((( 697 -The default battery pack of N DDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).719 +The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 698 698 ))) 699 699 700 700 ... ... @@ -717,7 +717,7 @@ 717 717 718 718 == 4.1 Access AT Commands == 719 719 720 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]742 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 721 721 722 722 723 723 AT+<CMD>? : Help on <CMD> ... ... @@ -805,8 +805,12 @@ 805 805 ))) 806 806 807 807 ((( 808 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 830 + 831 + 832 +((( 833 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 809 809 ))) 835 +))) 810 810 811 811 812 812 ... ... @@ -837,7 +837,7 @@ 837 837 = 7. Order Info = 838 838 839 839 840 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**866 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 841 841 842 842 843 843 (% class="wikigeneratedid" %) ... ... @@ -852,7 +852,7 @@ 852 852 853 853 (% style="color:#037691" %)**Package Includes**: 854 854 855 -* NS E01DistanceDetectSensorNode x 1881 +* N95S31B NB-IoT Temperature and Humidity Sensor 856 856 * External antenna x 1 857 857 ))) 858 858 ... ... @@ -861,11 +861,10 @@ 861 861 862 862 (% style="color:#037691" %)**Dimension and weight**: 863 863 864 - 865 865 * Device Size: 13.0 x 5 x 4.5 cm 866 866 * Device Weight: 150g 867 -* Package Size / pcs : 1 5x12x 5.5cm868 -* Weight / pcs : 220g892 +* Package Size / pcs : 14.0 x 8x 5 cm 893 +* Weight / pcs : 180g 869 869 ))) 870 870 871 871 (((
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content