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,43 +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 -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 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. 27 -\\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. 28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 29 -\\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) 30 -\\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. 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*. 31 31 ))) 32 32 29 +((( 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. 31 +))) 32 + 33 +((( 34 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 36 + 37 +((( 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). 39 +))) 40 + 41 +((( 33 33 34 34 ))) 35 35 36 -[[image:1657327959271-447.png]] 45 +((( 46 +~* make sure you have NB-IoT coverage locally. 47 +))) 37 37 49 + 50 +))) 38 38 52 +[[image:1657348284168-431.png]] 39 39 40 -== 1.2 Features == 41 41 42 42 56 +== 1.2 Features == 57 + 43 43 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 44 -* Ultra low power consumption 45 -* Distance Detection by Ultrasonic technology 46 -* Flat object range 280mm - 7500mm 47 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 48 -* Cable Length: 25cm 59 +* Monitor Temperature & Humidity via SHT31 49 49 * AT Commands to change parameters 50 50 * Uplink on periodically 51 51 * Downlink to change configure 52 52 * IP66 Waterproof Enclosure 64 +* Ultra-Low Power consumption 65 +* AT Commands to change parameters 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 ... ... @@ -80,13 +80,8 @@ 80 80 * Max continuously current: 130mA 81 81 * Max boost current: 2A, 1 second 82 82 83 -(% style="color:#037691" %)**Power Consumption** 84 84 85 -* STOP Mode: 10uA @ 3.3v 86 -* Max transmit power: 350mA@3.3v 87 87 88 - 89 - 90 90 == 1.4 Applications == 91 91 92 92 * Smart Buildings & Home Automation ... ... @@ -102,22 +102,56 @@ 102 102 103 103 == 1.5 Pin Definitions == 104 104 113 +N95S31B use the mother board from NBSN95 which as below. 105 105 106 -[[image: 1657328609906-564.png]]115 +[[image:image-20220709144723-1.png]] 107 107 108 108 118 +=== 1.5.1 Jumper JP2 === 109 109 110 - = 2. UseNDDS75 tocommunicate withIoTServer =120 +Power on Device when put this jumper. 111 111 122 + 123 + 124 +=== 1.5.2 BOOT MODE / SW1 === 125 + 126 +((( 127 +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. 128 +))) 129 + 130 +((( 131 +2) Flash: work mode, device starts to work and send out console output for further debug 132 +))) 133 + 134 + 135 + 136 +=== 1.5.3 Reset Button === 137 + 138 +Press to reboot the device. 139 + 140 + 141 + 142 +=== 1.5.4 LED === 143 + 144 +It will flash: 145 + 146 +1. When boot the device in flash mode 147 +1. Send an uplink packet 148 + 149 + 150 + 151 += 2. Use N95S31B to communicate with IoT Server = 152 + 112 112 == 2.1 How it works == 113 113 155 + 114 114 ((( 115 -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.157 +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. 116 116 ))) 117 117 118 118 119 119 ((( 120 -The diagram below shows the working flow in default firmware of N DDS75:162 +The diagram below shows the working flow in default firmware of N95S31B: 121 121 ))) 122 122 123 123 ((( ... ... @@ -124,7 +124,7 @@ 124 124 125 125 ))) 126 126 127 -[[image:1657328 659945-416.png]]169 +[[image:1657350248151-650.png]] 128 128 129 129 ((( 130 130 ... ... @@ -131,30 +131,67 @@ 131 131 ))) 132 132 133 133 134 -== 2.2 Configure the N DDS75 ==176 +== 2.2 Configure the N95S31B == 135 135 136 136 179 +=== 2.2.1 Power On N95S31B === 180 + 181 + 182 +[[image:image-20220709150546-2.png]] 183 + 184 + 137 137 === 2.2.1 Test Requirement === 138 138 187 + 139 139 ((( 140 -To use N DDS75 in your city, make sure meet below requirements:189 +To use N95S31B in your city, make sure meet below requirements: 141 141 ))) 142 142 143 -* Your local operator has already distributed a NB-IoT Network there. 144 -* The local NB-IoT network used the band that NSE01 supports. 145 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 192 +* ((( 193 +Your local operator has already distributed a NB-IoT Network there. 194 +))) 195 +* ((( 196 +The local NB-IoT network used the band that N95S31B supports. 197 +))) 198 +* ((( 199 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 200 +))) 146 146 147 147 ((( 148 -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 server203 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 149 149 ))) 150 150 206 +((( 207 +N95S31B supports different communication protocol such as : 208 +))) 151 151 152 -[[image:1657328756309-230.png]] 210 +((( 211 +* ((( 212 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 213 +))) 214 +* ((( 215 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 216 +))) 217 +* ((( 218 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 219 +))) 220 +* ((( 221 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 222 +))) 153 153 224 +((( 225 +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. 226 +))) 154 154 228 + 229 +))) 155 155 156 - ===2.2.2 Insert SIM card ===231 +[[image:1657350625843-586.png]] 157 157 233 + 234 + 235 +=== 2.2.3 Insert SIM card === 236 + 158 158 ((( 159 159 Insert the NB-IoT Card get from your provider. 160 160 ))) ... ... @@ -164,19 +164,19 @@ 164 164 ))) 165 165 166 166 167 -[[image:165732 8884227-504.png]]246 +[[image:1657351240556-536.png]] 168 168 169 169 170 170 171 -=== 2.2. 3DDS75 to configure it ===250 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 172 172 173 173 ((( 174 174 ((( 175 -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.254 +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. 176 176 ))) 177 177 ))) 178 178 179 -[[image: image-20220709092052-2.png]]258 +[[image:1657351312545-300.png]] 180 180 181 181 **Connection:** 182 182 ... ... @@ -196,18 +196,18 @@ 196 196 * Flow Control: (% style="color:green" %)**None** 197 197 198 198 ((( 199 -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.278 +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. 200 200 ))) 201 201 202 202 [[image:1657329814315-101.png]] 203 203 204 204 ((( 205 -(% 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/]]284 +(% 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/]] 206 206 ))) 207 207 208 208 209 209 210 -=== 2.2. 4289 +=== 2.2.5 Use CoAP protocol to uplink data === 211 211 212 212 (% 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/]] 213 213 ... ... @@ -227,10 +227,12 @@ 227 227 ))) 228 228 229 229 ((( 309 + 310 + 230 230 For parameter description, please refer to AT command set 231 231 ))) 232 232 233 -[[image:16573 30452568-615.png]]314 +[[image:1657352146020-183.png]] 234 234 235 235 236 236 ((( ... ... @@ -237,11 +237,11 @@ 237 237 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. 238 238 ))) 239 239 240 -[[image:16573 30472797-498.png]]321 +[[image:1657352185396-303.png]] 241 241 242 242 243 243 244 -=== 2.2. 5325 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 245 245 246 246 247 247 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -248,50 +248,56 @@ 248 248 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 249 249 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 250 250 251 -[[image:16573 30501006-241.png]]332 +[[image:1657352391268-297.png]] 252 252 253 253 254 -[[image:16573 30533775-472.png]]335 +[[image:1657352403317-397.png]] 255 255 256 256 257 257 258 -=== 2.2. 6339 +=== 2.2.7 Use MQTT protocol to uplink data === 259 259 341 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 260 260 261 261 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 262 262 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 263 263 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 264 -* (% style="color:blue" %)**AT+UNAME=UNAME 265 -* (% style="color:blue" %)**AT+PWD=PWD 266 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT267 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT346 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 347 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 348 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 349 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 268 268 269 -[[image:165724 9978444-674.png]]351 +[[image:1657352634421-276.png]] 270 270 271 271 272 -[[image:16573 30723006-866.png]]354 +[[image:1657352645687-385.png]] 273 273 356 +((( 357 +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. 358 +))) 274 274 360 + 275 275 ((( 276 -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.362 +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. 277 277 ))) 278 278 279 279 280 280 281 -=== 2.2. 7367 +=== 2.2.8 Use TCP protocol to uplink data === 282 282 369 +This feature is supported since firmware version v110 283 283 284 284 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 285 285 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 286 286 287 -[[image: image-20220709093918-1.png]]374 +[[image:1657352898400-901.png]] 288 288 289 289 290 -[[image: image-20220709093918-2.png]]377 +[[image:1657352914475-252.png]] 291 291 292 292 293 293 294 -=== 2.2. 8381 +=== 2.2.9 Change Update Interval === 295 295 296 296 User can use below command to change the (% style="color:green" %)**uplink interval**. 297 297 ... ... @@ -298,162 +298,157 @@ 298 298 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 299 299 300 300 ((( 301 - (%style="color:red" %)**NOTE:**388 + 302 302 ))) 303 303 304 -((( 305 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 306 -))) 307 307 308 308 309 - 310 310 == 2.3 Uplink Payload == 311 311 312 -In this mode, uplink payload includes in total 14 bytes 313 313 396 +((( 397 +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. 398 +))) 314 314 315 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 316 -|=(% style="width: 60px;" %)((( 317 -**Size(bytes)** 318 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 60px;" %)**1** 319 -|(% 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"]] 320 320 321 321 ((( 322 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.402 +For example: 323 323 ))) 324 324 405 +((( 406 + (% 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. 407 +))) 325 325 326 -[[image:1657331036973-987.png]] 327 327 328 328 ((( 329 -The payload is ASCIIstring,representative sameHEX:411 +The uplink payloads are composed in ASCII String. For example: 330 330 ))) 331 331 332 332 ((( 333 -0 x72403155615900640c6c19029200where:415 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 334 334 ))) 335 335 336 - *(((337 - DeviceID:0x724031556159=724031556159418 +((( 419 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 338 338 ))) 339 -* ((( 340 -Version: 0x0064=100=1.0.0 421 + 422 + 423 +((( 424 +(% style="color:red" %)**NOTE:** 341 341 ))) 342 342 343 -* ((( 344 -BAT: 0x0c6c = 3180 mV = 3.180V 427 +(% style="color:red" %) 428 +1. ((( 429 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 345 345 ))) 346 - *(((347 - Signal:0x19=25431 +1. ((( 432 +By default, the device will send an uplink message every 1 hour. 348 348 ))) 349 -* ((( 350 -Distance: 0x0292= 658 mm 351 -))) 352 -* ((( 353 -Interrupt: 0x00 = 0 354 354 355 355 356 356 357 - 358 -))) 437 +=== 2.3.1 Payload Analyze === 359 359 360 - ==2.4PayloadExplanationandSensorInterface==439 +N95S31B uplink payload includes in total 21 bytes 361 361 362 362 363 -=== 2.4.1 Device ID === 364 - 442 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 443 +|=(% style="width: 60px;" %)((( 444 +**Size(bytes)** 445 +)))|=(% 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** 446 +|(% 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" %)((( 365 365 ((( 366 - By default, theDeviceID equal to thelast6bytes of IMEI.448 +Reserve/ Same as NBSN95 CFGMOD=1 367 367 ))) 368 368 369 369 ((( 370 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID452 +No function here. 371 371 ))) 372 - 454 +)))|(% style="width:77px" %)((( 373 373 ((( 374 - **Example:**456 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 375 375 ))) 376 376 377 377 ((( 378 - AT+DEUI=A84041F15612460 +By SHT31 379 379 ))) 380 - 462 +)))|(% style="width:80px" %)((( 381 381 ((( 382 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.464 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 383 383 ))) 384 384 385 - 386 - 387 -=== 2.4.2 Version Info === 388 - 389 389 ((( 390 - Specifythe software version: 0x64=100, means firmware version 1.00.468 +By SHT31 391 391 ))) 470 +))) 392 392 393 393 ((( 394 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 473 +((( 474 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 395 395 ))) 476 +))) 396 396 397 397 479 +[[image:1657354294009-643.png]] 398 398 399 -=== 2.4.3 Battery Info === 400 400 401 -((( 402 -Ex1: 0x0B45 = 2885mV 403 -))) 482 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 404 404 405 -((( 406 -Ex2: 0x0B49 = 2889mV 407 -))) 484 +* Device ID: 0x724031607457 = 724031607457 485 +* Version: 0x006e=110=1.1.0 408 408 487 +* BAT: 0x0ccd = 3277 mV = 3.277V 488 +* Signal: 0x1b = 27 489 +* Model: 0x01 = 1 490 +* 0x00dc000ccc= reserve, ignore in N95S31B 491 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 492 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 409 409 410 - 411 -=== 2.4.4 Signal Strength === 412 - 413 413 ((( 414 - NB-IoTNetwork signal Strength.495 + 415 415 ))) 416 416 417 417 ((( 418 - **Ex1:0x1d = 29**499 + 419 419 ))) 420 420 502 + 503 +=== 2.3.2 Device ID === 504 + 421 421 ((( 422 - (% style="color:blue"%)**0**(%%)-113dBmorless506 +By default, the Device ID equal to the last 6 bytes of IMEI. 423 423 ))) 424 424 425 425 ((( 426 -(% style="color:blue" %)** 1**(%%)-111dBm510 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 427 427 ))) 428 428 429 429 ((( 430 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm514 +**Example:** 431 431 ))) 432 432 433 433 ((( 434 - (% style="color:blue" %)**31** (%%) -51dBm or greater518 +AT+DEUI=A84041F15612 435 435 ))) 436 436 437 437 ((( 438 - (%style="color:blue"%)**99**(%%)Notknownor notdetectable522 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 439 439 ))) 440 440 441 441 442 442 443 -=== 2. 4.5Distance===527 +=== 2.3.3 Version Info === 444 444 445 -Get the distance. Flat object range 280mm - 7500mm. 529 +((( 530 +These bytes include the hardware and software version. 531 +))) 446 446 447 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 448 - 449 449 ((( 450 -((( 451 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 534 +Higher byte: Specify hardware version: always 0x00 for N95S31B 452 452 ))) 453 -))) 454 454 455 455 ((( 456 - 538 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 457 457 ))) 458 458 459 459 ((( ... ... @@ -460,63 +460,79 @@ 460 460 461 461 ))) 462 462 463 -=== 2.4.6 Digital Interrupt === 464 - 465 465 ((( 466 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.546 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 467 467 ))) 468 468 469 469 ((( 470 - Thecommand is:550 + 471 471 ))) 472 472 553 + 554 +=== 2.3.4 Battery Info === 555 + 473 473 ((( 474 - (% 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]])**.**557 +Ex1: 0x0B45 = 2885mV 475 475 ))) 476 476 477 - 478 478 ((( 479 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.561 +Ex2: 0x0B49 = 2889mV 480 480 ))) 481 481 482 482 565 + 566 +=== 2.3.5 Signal Strength === 567 + 483 483 ((( 484 - Example:569 +NB-IoT Network signal Strength. 485 485 ))) 486 486 487 487 ((( 488 - 0x(00):Normaluplinkpacket.573 +**Ex1: 0x1d = 29** 489 489 ))) 490 490 491 491 ((( 492 - 0x(01):InterruptUplinkPacket.577 +(% style="color:blue" %)**0**(%%) -113dBm or less 493 493 ))) 494 494 495 - 496 - 497 -=== 2.4.7 +5V Output === 498 - 499 499 ((( 500 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.581 +(% style="color:blue" %)**1**(%%) -111dBm 501 501 ))) 502 502 503 - 504 504 ((( 505 - The5V output timean be controlledbyAT Command.585 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 506 506 ))) 507 507 508 508 ((( 509 -(% style="color:blue" %)** AT+5VT=1000**589 +(% style="color:blue" %)**31** (%%) -51dBm or greater 510 510 ))) 511 511 512 512 ((( 513 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.593 +(% style="color:blue" %)**99** (%%) Not known or not detectable 514 514 ))) 515 515 516 516 517 517 518 -== 2. 5Downlink Payload ==598 +=== 2.3.6 Temperature & Humidity === 519 519 600 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 601 + 602 +[[image:image-20220709161741-3.png]] 603 + 604 + 605 +Convert the read byte to decimal and divide it by ten. 606 + 607 + 608 +**Example:** 609 + 610 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 611 + 612 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 613 + 614 + 615 + 616 +== 2.4 Downlink Payload == 617 + 520 520 By default, NDDS75 prints the downlink payload to console port. 521 521 522 522 [[image:image-20220709100028-1.png]] ... ... @@ -567,47 +567,16 @@ 567 567 568 568 569 569 570 -== 2. 6LED Indicator ==668 +== 2.5 Battery Analysis == 571 571 670 +=== 2.5.1 Battery Type === 572 572 573 -The NDDS75 has an internal LED which is to show the status of different state. 574 574 575 - 576 -* 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) 577 -* Then the LED will be on for 1 second means device is boot normally. 578 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 579 -* For each uplink probe, LED will be on for 500ms. 580 - 581 581 ((( 582 - 674 +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. 583 583 ))) 584 584 585 - 586 - 587 -== 2.7 Firmware Change Log == 588 - 589 - 590 -Download URL & Firmware Change log 591 - 592 592 ((( 593 -[[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/]] 594 -))) 595 - 596 - 597 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 598 - 599 - 600 - 601 -== 2.8 Battery Analysis == 602 - 603 -=== 2.8.1 Battery Type === 604 - 605 - 606 -((( 607 -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. 608 -))) 609 - 610 -((( 611 611 The battery is designed to last for several years depends on the actually use environment and update interval. 612 612 ))) 613 613 ... ... @@ -625,56 +625,35 @@ 625 625 626 626 627 627 628 -=== 2. 8.2 Power consumption Analyze ===695 +=== 2.5.2 Power consumption Analyze === 629 629 630 630 ((( 631 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.698 +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. 632 632 ))) 633 633 634 - 635 635 ((( 636 - Instructionto use as below:702 + 637 637 ))) 638 638 639 -((( 640 -(% 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/]] 641 -))) 642 642 706 +=== 2.5.3 Battery Note === 643 643 644 644 ((( 645 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose709 +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. 646 646 ))) 647 647 648 -* ((( 649 -Product Model 650 -))) 651 -* ((( 652 -Uplink Interval 653 -))) 654 -* ((( 655 -Working Mode 656 -))) 657 657 658 -((( 659 -And the Life expectation in difference case will be shown on the right. 660 -))) 661 661 662 - [[image:image-20220709110451-3.png]]714 +=== 2.5.4 Replace the battery === 663 663 664 664 665 - 666 -=== 2.8.3 Battery Note === 667 - 668 668 ((( 669 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.718 +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. 670 670 ))) 671 671 672 672 673 - 674 -=== 2.8.4 Replace the battery === 675 - 676 676 ((( 677 -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).723 +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). 678 678 ))) 679 679 680 680 ... ... @@ -697,7 +697,7 @@ 697 697 698 698 == 4.1 Access AT Commands == 699 699 700 -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/]]746 +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/]] 701 701 702 702 703 703 AT+<CMD>? : Help on <CMD> ... ... @@ -785,8 +785,12 @@ 785 785 ))) 786 786 787 787 ((( 788 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 834 + 835 + 836 +((( 837 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 789 789 ))) 839 +))) 790 790 791 791 792 792 ... ... @@ -817,7 +817,7 @@ 817 817 = 7. Order Info = 818 818 819 819 820 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**870 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 821 821 822 822 823 823 (% class="wikigeneratedid" %) ... ... @@ -832,7 +832,7 @@ 832 832 833 833 (% style="color:#037691" %)**Package Includes**: 834 834 835 -* NS E01DistanceDetectSensorNode x 1885 +* N95S31B NB-IoT Temperature and Humidity Sensor 836 836 * External antenna x 1 837 837 ))) 838 838 ... ... @@ -841,11 +841,10 @@ 841 841 842 842 (% style="color:#037691" %)**Dimension and weight**: 843 843 844 - 845 845 * Device Size: 13.0 x 5 x 4.5 cm 846 846 * Device Weight: 150g 847 -* Package Size / pcs : 1 5x12x 5.5cm848 -* Weight / pcs : 220g896 +* Package Size / pcs : 14.0 x 8x 5 cm 897 +* Weight / pcs : 180g 849 849 ))) 850 850 851 851 (((
- 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