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, 17 added, 0 removed)
- 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
-
- 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,44 +13,41 @@ 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 -The NDDS75 can beappliedoscenariossuch ashorizontaldistancemeasurement,liquidlevelmeasurement,parkingmanagementsystem, objectproximity andpresencedetection,intelligenttrashcanmanagementsystem,robotobstacleavoidance,automaticcontrol,sewer,bottomwaterlevel monitoring, etc. It detectsthe distancebetweenthemeasuredobjectandthesensor, and uploads the valueviawirelesstoIoTServervia NB-IoTNetwork.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 31 ))) 32 32 33 33 ((( 34 -N arrowBand-Internetof Things(NB-IoT) is a standards-basedlow power widearea (LPWA) technology developedtoenable a wide rangeof new IoTdevicesandservices.NB-IoTsignificantlyimproves the powerconsumption ofuserdevices,systemcapacityandspectrumefficiency,especiallyindeep coverage.34 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 35 ))) 36 36 37 37 ((( 38 -N DDS75 supports different uplink methodsinclude(% style="color:blue" %)**TCP,MQTT, UDPand CoAP**fordifferent 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). 39 39 ))) 40 40 41 41 ((( 42 - NDDS75is 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 + 43 43 ))) 44 44 45 45 ((( 46 - TouseNDDS75, userneedstocheckif there isNB-IoT coverageinlocalarea and with the bands NDDS75 supports. If thelocal 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. 47 47 ))) 48 -))) 49 49 50 50 51 51 ))) 52 52 53 -[[image:165732 7959271-447.png]]52 +[[image:1657348284168-431.png]] 54 54 55 55 56 56 ... ... @@ -57,15 +57,13 @@ 57 57 == 1.2 Features == 58 58 59 59 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 60 -* Ultra low power consumption 61 -* Distance Detection by Ultrasonic technology 62 -* Flat object range 280mm - 7500mm 63 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 64 -* Cable Length: 25cm 59 +* Monitor Temperature & Humidity via SHT31 65 65 * AT Commands to change parameters 66 66 * Uplink on periodically 67 67 * Downlink to change configure 68 68 * IP66 Waterproof Enclosure 64 +* Ultra-Low Power consumption 65 +* AT Commands to change parameters 69 69 * Micro SIM card slot for NB-IoT SIM 70 70 * 8500mAh Battery for long term use 71 71 ... ... @@ -96,13 +96,8 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 99 -(% style="color:#037691" %)**Power Consumption** 100 100 101 -* STOP Mode: 10uA @ 3.3v 102 -* Max transmit power: 350mA@3.3v 103 103 104 - 105 - 106 106 == 1.4 Applications == 107 107 108 108 * Smart Buildings & Home Automation ... ... @@ -118,22 +118,56 @@ 118 118 119 119 == 1.5 Pin Definitions == 120 120 113 +N95S31B use the mother board from NBSN95 which as below. 121 121 122 -[[image: 1657328609906-564.png]]115 +[[image:image-20220709144723-1.png]] 123 123 124 124 118 +=== 1.5.1 Jumper JP2 === 125 125 126 - = 2. UseNDDS75 tocommunicate withIoTServer =120 +Power on Device when put this jumper. 127 127 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 + 128 128 == 2.1 How it works == 129 129 155 + 130 130 ((( 131 -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. 132 132 ))) 133 133 134 134 135 135 ((( 136 -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: 137 137 ))) 138 138 139 139 ((( ... ... @@ -140,7 +140,7 @@ 140 140 141 141 ))) 142 142 143 -[[image:1657328 659945-416.png]]169 +[[image:1657350248151-650.png]] 144 144 145 145 ((( 146 146 ... ... @@ -147,30 +147,67 @@ 147 147 ))) 148 148 149 149 150 -== 2.2 Configure the N DDS75 ==176 +== 2.2 Configure the N95S31B == 151 151 152 152 179 +=== 2.2.1 Power On N95S31B === 180 + 181 + 182 +[[image:image-20220709150546-2.png]] 183 + 184 + 153 153 === 2.2.1 Test Requirement === 154 154 187 + 155 155 ((( 156 -To use N DDS75 in your city, make sure meet below requirements:189 +To use N95S31B in your city, make sure meet below requirements: 157 157 ))) 158 158 159 -* Your local operator has already distributed a NB-IoT Network there. 160 -* The local NB-IoT network used the band that NSE01 supports. 161 -* 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 +))) 162 162 163 163 ((( 164 -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. 165 165 ))) 166 166 206 +((( 207 +N95S31B supports different communication protocol such as : 208 +))) 167 167 168 -[[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 +))) 169 169 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 +))) 170 170 228 + 229 +))) 171 171 172 - ===2.2.2 Insert SIM card ===231 +[[image:1657350625843-586.png]] 173 173 233 + 234 + 235 +=== 2.2.3 Insert SIM card === 236 + 174 174 ((( 175 175 Insert the NB-IoT Card get from your provider. 176 176 ))) ... ... @@ -180,19 +180,19 @@ 180 180 ))) 181 181 182 182 183 -[[image:165732 8884227-504.png]]246 +[[image:1657351240556-536.png]] 184 184 185 185 186 186 187 -=== 2.2. 3DDS75 to configure it ===250 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 188 188 189 189 ((( 190 190 ((( 191 -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. 192 192 ))) 193 193 ))) 194 194 195 -[[image: image-20220709092052-2.png]]258 +[[image:1657351312545-300.png]] 196 196 197 197 **Connection:** 198 198 ... ... @@ -212,18 +212,18 @@ 212 212 * Flow Control: (% style="color:green" %)**None** 213 213 214 214 ((( 215 -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. 216 216 ))) 217 217 218 218 [[image:1657329814315-101.png]] 219 219 220 220 ((( 221 -(% 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/]] 222 222 ))) 223 223 224 224 225 225 226 -=== 2.2. 4289 +=== 2.2.5 Use CoAP protocol to uplink data === 227 227 228 228 (% 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/]] 229 229 ... ... @@ -243,10 +243,12 @@ 243 243 ))) 244 244 245 245 ((( 309 + 310 + 246 246 For parameter description, please refer to AT command set 247 247 ))) 248 248 249 -[[image:16573 30452568-615.png]]314 +[[image:1657352146020-183.png]] 250 250 251 251 252 252 ((( ... ... @@ -253,11 +253,11 @@ 253 253 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. 254 254 ))) 255 255 256 -[[image:16573 30472797-498.png]]321 +[[image:1657352185396-303.png]] 257 257 258 258 259 259 260 -=== 2.2. 5325 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 261 261 262 262 263 263 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -264,15 +264,16 @@ 264 264 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 265 265 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 266 266 267 -[[image:16573 30501006-241.png]]332 +[[image:1657352391268-297.png]] 268 268 269 269 270 -[[image:16573 30533775-472.png]]335 +[[image:1657352403317-397.png]] 271 271 272 272 273 273 274 -=== 2.2. 6339 +=== 2.2.7 Use MQTT protocol to uplink data === 275 275 341 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 276 276 277 277 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 278 278 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -279,35 +279,40 @@ 279 279 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 280 280 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 281 281 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 282 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT283 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT348 +* (% 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 284 284 285 -[[image:165724 9978444-674.png]]351 +[[image:1657352634421-276.png]] 286 286 287 287 288 -[[image:16573 30723006-866.png]]354 +[[image:1657352645687-385.png]] 289 289 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 +))) 290 290 360 + 291 291 ((( 292 -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. 293 293 ))) 294 294 295 295 296 296 297 -=== 2.2. 7367 +=== 2.2.8 Use TCP protocol to uplink data === 298 298 369 +This feature is supported since firmware version v110 299 299 300 300 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 301 301 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 302 302 303 -[[image: image-20220709093918-1.png]]374 +[[image:1657352898400-901.png]] 304 304 305 305 306 -[[image: image-20220709093918-2.png]]377 +[[image:1657352914475-252.png]] 307 307 308 308 309 309 310 -=== 2.2. 8381 +=== 2.2.9 Change Update Interval === 311 311 312 312 User can use below command to change the (% style="color:green" %)**uplink interval**. 313 313 ... ... @@ -314,164 +314,158 @@ 314 314 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 315 315 316 316 ((( 317 - (%style="color:red" %)**NOTE:**388 + 318 318 ))) 319 319 320 -((( 321 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 322 -))) 323 323 324 324 325 - 326 326 == 2.3 Uplink Payload == 327 327 328 -In this mode, uplink payload includes in total 14 bytes 329 329 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 +))) 330 330 331 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 332 -|=(% style="width: 60px;" %)((( 333 -**Size(bytes)** 334 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 335 -|(% 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"]] 336 336 337 337 ((( 338 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.402 +For example: 339 339 ))) 340 340 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 +))) 341 341 342 -[[image:1657331036973-987.png]] 343 343 344 344 ((( 345 -The payload is ASCIIstring,representative sameHEX:411 +The uplink payloads are composed in ASCII String. For example: 346 346 ))) 347 347 348 348 ((( 349 -0 x72403155615900640c6c19029200where:415 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 350 350 ))) 351 351 352 - *(((353 - DeviceID:0x724031556159=724031556159418 +((( 419 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 354 354 ))) 355 -* ((( 356 -Version: 0x0064=100=1.0.0 421 + 422 + 423 +((( 424 +(% style="color:red" %)**NOTE:** 357 357 ))) 358 358 359 -* ((( 360 -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"]]. 361 361 ))) 362 - *(((363 - Signal:0x19=25431 +1. ((( 432 +By default, the device will send an uplink message every 1 hour. 364 364 ))) 365 -* ((( 366 -Distance: 0x0292= 658 mm 367 -))) 368 -* ((( 369 -Interrupt: 0x00 = 0 370 370 371 371 372 372 373 - 374 -))) 437 +=== 2.3.1 Payload Analyze === 375 375 376 - ==2.4PayloadExplanationandSensorInterface==439 +N95S31B uplink payload includes in total 21 bytes 377 377 378 378 379 -=== 2.4.1 Device ID === 380 - 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" %)((( 381 381 ((( 382 - By default, theDeviceID equal to thelast6bytes of IMEI.448 +Reserve/ Same as NBSN95 CFGMOD=1 383 383 ))) 384 384 385 385 ((( 386 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID452 +No function here. 387 387 ))) 388 - 454 +)))|(% style="width:77px" %)((( 389 389 ((( 390 - **Example:**456 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 391 391 ))) 392 392 393 393 ((( 394 - AT+DEUI=A84041F15612460 +By SHT31 395 395 ))) 396 - 462 +)))|(% style="width:80px" %)((( 397 397 ((( 398 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.464 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 399 399 ))) 400 400 401 - 402 - 403 -=== 2.4.2 Version Info === 404 - 405 405 ((( 406 - Specifythe software version: 0x64=100, means firmware version 1.00.468 +By SHT31 407 407 ))) 470 +))) 408 408 409 409 ((( 410 -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. 411 411 ))) 476 +))) 412 412 413 413 479 +[[image:1657354294009-643.png]] 414 414 415 -=== 2.4.3 Battery Info === 416 416 417 -((( 418 -Ex1: 0x0B45 = 2885mV 419 -))) 482 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 420 420 421 -((( 422 -Ex2: 0x0B49 = 2889mV 423 -))) 484 +* Device ID: 0x724031607457 = 724031607457 485 +* Version: 0x006e=110=1.1.0 424 424 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 425 425 426 - 427 -=== 2.4.4 Signal Strength === 428 - 429 429 ((( 430 - NB-IoTNetwork signal Strength.495 + 431 431 ))) 432 432 433 433 ((( 434 - **Ex1:0x1d = 29**499 + 435 435 ))) 436 436 502 + 503 +=== 2.3.2 Device ID === 504 + 437 437 ((( 438 - (% style="color:blue"%)**0**(%%)-113dBmorless506 +By default, the Device ID equal to the last 6 bytes of IMEI. 439 439 ))) 440 440 441 441 ((( 442 -(% style="color:blue" %)** 1**(%%)-111dBm510 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 443 443 ))) 444 444 445 445 ((( 446 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm514 +**Example:** 447 447 ))) 448 448 449 449 ((( 450 - (% style="color:blue" %)**31** (%%) -51dBm or greater518 +AT+DEUI=A84041F15612 451 451 ))) 452 452 453 453 ((( 454 - (%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. 455 455 ))) 456 456 457 457 458 458 459 -=== 2. 4.5Distance===527 +=== 2.3.3 Version Info === 460 460 461 -Get the distance. Flat object range 280mm - 7500mm. 462 462 463 463 ((( 464 - Forexample,if the datayou getfrom theregisteris **__0x0B 0x05__**, the distancebetweenthesensorand the measuredobject is531 +These bytes include the hardware and software version. 465 465 ))) 466 466 467 467 ((( 468 -((( 469 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 535 +Higher byte: Specify hardware version: always 0x00 for N95S31B 470 470 ))) 471 -))) 472 472 473 473 ((( 474 - 539 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 475 475 ))) 476 476 477 477 ((( ... ... @@ -478,63 +478,79 @@ 478 478 479 479 ))) 480 480 481 -=== 2.4.6 Digital Interrupt === 482 - 483 483 ((( 484 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.547 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 485 485 ))) 486 486 487 487 ((( 488 - Thecommand is:551 + 489 489 ))) 490 490 554 + 555 +=== 2.3.4 Battery Info === 556 + 491 491 ((( 492 - (% 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]])**.**558 +Ex1: 0x0B45 = 2885mV 493 493 ))) 494 494 495 - 496 496 ((( 497 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.562 +Ex2: 0x0B49 = 2889mV 498 498 ))) 499 499 500 500 566 + 567 +=== 2.3.5 Signal Strength === 568 + 501 501 ((( 502 - Example:570 +NB-IoT Network signal Strength. 503 503 ))) 504 504 505 505 ((( 506 - 0x(00):Normaluplinkpacket.574 +**Ex1: 0x1d = 29** 507 507 ))) 508 508 509 509 ((( 510 - 0x(01):InterruptUplinkPacket.578 +(% style="color:blue" %)**0**(%%) -113dBm or less 511 511 ))) 512 512 513 - 514 - 515 -=== 2.4.7 +5V Output === 516 - 517 517 ((( 518 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.582 +(% style="color:blue" %)**1**(%%) -111dBm 519 519 ))) 520 520 521 - 522 522 ((( 523 - The5V output timean be controlledbyAT Command.586 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 524 524 ))) 525 525 526 526 ((( 527 -(% style="color:blue" %)** AT+5VT=1000**590 +(% style="color:blue" %)**31** (%%) -51dBm or greater 528 528 ))) 529 529 530 530 ((( 531 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.594 +(% style="color:blue" %)**99** (%%) Not known or not detectable 532 532 ))) 533 533 534 534 535 535 536 -== 2. 5Downlink Payload ==599 +=== 2.3.6 Temperature & Humidity === 537 537 601 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 602 + 603 +[[image:image-20220709161741-3.png]] 604 + 605 + 606 +Convert the read byte to decimal and divide it by ten. 607 + 608 + 609 +**Example:** 610 + 611 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 612 + 613 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 614 + 615 + 616 + 617 +== 2.4 Downlink Payload == 618 + 538 538 By default, NDDS75 prints the downlink payload to console port. 539 539 540 540 [[image:image-20220709100028-1.png]] ... ... @@ -585,51 +585,16 @@ 585 585 586 586 587 587 588 -== 2. 6LED Indicator ==669 +== 2.5 Battery Analysis == 589 589 671 +=== 2.5.1 Battery Type === 590 590 591 -The NDDS75 has an internal LED which is to show the status of different state. 592 592 593 - 594 -* 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) 595 -* Then the LED will be on for 1 second means device is boot normally. 596 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 597 -* For each uplink probe, LED will be on for 500ms. 598 - 599 599 ((( 600 - 675 +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. 601 601 ))) 602 602 603 - 604 - 605 -== 2.7 Firmware Change Log == 606 - 607 - 608 608 ((( 609 -Download URL & Firmware Change log 610 -))) 611 - 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 -((( 618 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 619 -))) 620 - 621 - 622 - 623 -== 2.8 Battery Analysis == 624 - 625 -=== 2.8.1 Battery Type === 626 - 627 - 628 -((( 629 -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. 630 -))) 631 - 632 -((( 633 633 The battery is designed to last for several years depends on the actually use environment and update interval. 634 634 ))) 635 635 ... ... @@ -647,56 +647,35 @@ 647 647 648 648 649 649 650 -=== 2. 8.2 Power consumption Analyze ===696 +=== 2.5.2 Power consumption Analyze === 651 651 652 652 ((( 653 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.699 +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. 654 654 ))) 655 655 656 - 657 657 ((( 658 - Instructionto use as below:703 + 659 659 ))) 660 660 661 -((( 662 -(% 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/]] 663 -))) 664 664 707 +=== 2.5.3 Battery Note === 665 665 666 666 ((( 667 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose710 +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. 668 668 ))) 669 669 670 -* ((( 671 -Product Model 672 -))) 673 -* ((( 674 -Uplink Interval 675 -))) 676 -* ((( 677 -Working Mode 678 -))) 679 679 680 -((( 681 -And the Life expectation in difference case will be shown on the right. 682 -))) 683 683 684 - [[image:image-20220709110451-3.png]]715 +=== 2.5.4 Replace the battery === 685 685 686 686 687 - 688 -=== 2.8.3 Battery Note === 689 - 690 690 ((( 691 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.719 +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. 692 692 ))) 693 693 694 694 695 - 696 -=== 2.8.4 Replace the battery === 697 - 698 698 ((( 699 -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).724 +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). 700 700 ))) 701 701 702 702 ... ... @@ -719,7 +719,7 @@ 719 719 720 720 == 4.1 Access AT Commands == 721 721 722 -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/]]747 +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/]] 723 723 724 724 725 725 AT+<CMD>? : Help on <CMD> ... ... @@ -807,8 +807,12 @@ 807 807 ))) 808 808 809 809 ((( 810 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 835 + 836 + 837 +((( 838 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 811 811 ))) 840 +))) 812 812 813 813 814 814 ... ... @@ -839,7 +839,7 @@ 839 839 = 7. Order Info = 840 840 841 841 842 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**871 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 843 843 844 844 845 845 (% class="wikigeneratedid" %) ... ... @@ -854,7 +854,7 @@ 854 854 855 855 (% style="color:#037691" %)**Package Includes**: 856 856 857 -* NS E01DistanceDetectSensorNode x 1886 +* N95S31B NB-IoT Temperature and Humidity Sensor 858 858 * External antenna x 1 859 859 ))) 860 860 ... ... @@ -863,11 +863,10 @@ 863 863 864 864 (% style="color:#037691" %)**Dimension and weight**: 865 865 866 - 867 867 * Device Size: 13.0 x 5 x 4.5 cm 868 868 * Device Weight: 150g 869 -* Package Size / pcs : 1 5x12x 5.5cm870 -* Weight / pcs : 220g897 +* Package Size / pcs : 14.0 x 8x 5 cm 898 +* Weight / pcs : 180g 871 871 ))) 872 872 873 873 (((
- 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