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, 0 added, 18 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 95S31BNB-IoTTemperature& HumiditySensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Content
-
... ... @@ -1,12 +1,10 @@ 1 1 (% style="text-align:center" %) 2 -[[image: 1657348034241-728.png||height="470" width="470"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 - 9 - 10 10 **Table of Contents:** 11 11 12 12 {{toc/}} ... ... @@ -15,60 +15,49 @@ 15 15 16 16 17 17 16 + 18 18 = 1. Introduction = 19 19 20 -== 1.1 What is N 95S31BNB-IoTSensorNode==19 +== 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 22 ((( 23 23 24 24 25 25 ((( 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*. 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. 27 27 ))) 28 28 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 -((( 42 42 43 43 ))) 44 44 45 -((( 46 -~* make sure you have NB-IoT coverage locally. 47 -))) 36 +[[image:1654503236291-817.png]] 48 48 49 - 50 -))) 51 51 52 -[[image:16573 48284168-431.png]]39 +[[image:1657327959271-447.png]] 53 53 54 54 55 55 56 56 == 1.2 Features == 57 57 45 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 -* Monitor Temperature & Humidity via SHT31 47 +* Ultra low power consumption 48 +* Distance Detection by Ultrasonic technology 49 +* Flat object range 280mm - 7500mm 50 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 51 +* Cable Length: 25cm 60 60 * AT Commands to change parameters 61 61 * Uplink on periodically 62 62 * Downlink to change configure 63 63 * IP66 Waterproof Enclosure 64 -* Ultra-Low Power consumption 65 -* AT Commands to change parameters 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 - 70 - 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,7 +87,6 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -96,7 +96,10 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 84 +(% style="color:#037691" %)**Power Consumption** 99 99 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 100 100 101 101 102 102 == 1.4 Applications == ... ... @@ -112,59 +112,25 @@ 112 112 113 113 114 114 103 + 115 115 == 1.5 Pin Definitions == 116 116 117 -N95S31B use the mother board from NBSN95 which as below. 118 118 119 -[[image: image-20220709144723-1.png]]107 +[[image:1657328609906-564.png]] 120 120 121 121 122 -=== 1.5.1 Jumper JP2 === 123 123 124 - PoweronDevice when putthisjumper.111 += 2. Use NDDS75 to communicate with IoT Server = 125 125 126 - 127 - 128 -=== 1.5.2 BOOT MODE / SW1 === 129 - 130 -((( 131 -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. 132 -))) 133 - 134 -((( 135 -2) Flash: work mode, device starts to work and send out console output for further debug 136 -))) 137 - 138 - 139 - 140 -=== 1.5.3 Reset Button === 141 - 142 -Press to reboot the device. 143 - 144 - 145 - 146 -=== 1.5.4 LED === 147 - 148 -It will flash: 149 - 150 -1. When boot the device in flash mode 151 -1. Send an uplink packet 152 - 153 - 154 - 155 - 156 -= 2. Use N95S31B to communicate with IoT Server = 157 - 158 158 == 2.1 How it works == 159 159 160 - 161 161 ((( 162 -The N 95S31Bis equipped with a NB-IoT module, the pre-loaded firmware in N95S31Bwill 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 +The NDDS75 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. 163 163 ))) 164 164 165 165 166 166 ((( 167 -The diagram below shows the working flow in default firmware of N 95S31B:121 +The diagram below shows the working flow in default firmware of NDDS75: 168 168 ))) 169 169 170 170 ((( ... ... @@ -171,7 +171,7 @@ 171 171 172 172 ))) 173 173 174 -[[image:16573 50248151-650.png]]128 +[[image:1657328659945-416.png]] 175 175 176 176 ((( 177 177 ... ... @@ -178,45 +178,30 @@ 178 178 ))) 179 179 180 180 181 -== 2.2 Configure the N 95S31B==135 +== 2.2 Configure the NDDS75 == 182 182 183 183 184 -=== 2.2.1 Power On N95S31B === 185 - 186 - 187 -[[image:image-20220709150546-2.png]] 188 - 189 - 190 190 === 2.2.1 Test Requirement === 191 191 140 +((( 141 +To use NDDS75 in your city, make sure meet below requirements: 142 +))) 192 192 193 -To use N95S31B in your city, make sure meet below requirements: 194 - 195 195 * Your local operator has already distributed a NB-IoT Network there. 196 -* The local NB-IoT network used the band that N 95S31Bsupports.145 +* The local NB-IoT network used the band that NSE01 supports. 197 197 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 198 198 199 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 200 - 201 -N95S31B supports different communication protocol such as : 202 - 203 203 ((( 204 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 205 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 206 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 207 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 208 - 209 -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. 210 - 211 - 149 +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 server 212 212 ))) 213 213 214 -[[image:1657350625843-586.png]] 215 215 153 +[[image:1657328756309-230.png]] 216 216 217 217 218 -=== 2.2.3 Insert SIM card === 219 219 157 +=== 2.2.2 Insert SIM card === 158 + 220 220 ((( 221 221 Insert the NB-IoT Card get from your provider. 222 222 ))) ... ... @@ -226,19 +226,19 @@ 226 226 ))) 227 227 228 228 229 -[[image:16573 51240556-536.png]]168 +[[image:1657328884227-504.png]] 230 230 231 231 232 232 233 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===172 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 234 234 235 235 ((( 236 236 ((( 237 -User need to configure 95S31Bvia serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31Bsupport AT Commands, user can use a USB to TTL adapter to connect to95S31Band use AT Commands to configure it, as below.176 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. 238 238 ))) 239 239 ))) 240 240 241 -[[image: 1657351312545-300.png]]180 +[[image:image-20220709092052-2.png]] 242 242 243 243 **Connection:** 244 244 ... ... @@ -258,110 +258,90 @@ 258 258 * Flow Control: (% style="color:green" %)**None** 259 259 260 260 ((( 261 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.200 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 262 262 ))) 263 263 264 264 [[image:1657329814315-101.png]] 265 265 266 266 ((( 267 -(% style="color:red" %)Note: the valid AT Commands can be found at: 95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]206 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 268 268 ))) 269 269 270 270 271 271 272 -=== 2.2. 5Use CoAP protocol to uplink data ===211 +=== 2.2.4 Use CoAP protocol to uplink data === 273 273 274 274 (% 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/]] 275 275 276 276 277 -((( 278 278 **Use below commands:** 279 -))) 280 280 281 -* ((( 282 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 283 -))) 284 -* ((( 285 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 286 -))) 287 -* ((( 288 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 289 -))) 218 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 219 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 220 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 290 290 291 -((( 292 - 293 - 294 294 For parameter description, please refer to AT command set 295 -))) 296 296 297 -[[image:1657352 146020-183.png]]224 +[[image:1657330452568-615.png]] 298 298 299 299 300 -((( 301 301 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. 302 -))) 303 303 304 -[[image:16573 52185396-303.png]]229 +[[image:1657330472797-498.png]] 305 305 306 306 307 307 308 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===233 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 309 309 310 310 311 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 236 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 312 312 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 313 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 238 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 314 314 315 -[[image:16573 52391268-297.png]]240 +[[image:1657330501006-241.png]] 316 316 317 317 318 -[[image:16573 52403317-397.png]]243 +[[image:1657330533775-472.png]] 319 319 320 320 321 321 322 -=== 2.2. 7Use MQTT protocol to uplink data ===247 +=== 2.2.6 Use MQTT protocol to uplink data === 323 323 324 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 325 325 326 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 327 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 328 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 329 -* (% style="color:blue" %)**AT+UNAME=UNAME 330 -* (% style="color:blue" %)**AT+PWD=PWD 331 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527332 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)250 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 251 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 252 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 253 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 254 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 255 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 256 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 333 333 334 -[[image:1657 352634421-276.png]]258 +[[image:1657249978444-674.png]] 335 335 336 336 337 -[[image:16573 52645687-385.png]]261 +[[image:1657330723006-866.png]] 338 338 339 -((( 340 -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. 341 -))) 342 342 343 - 344 344 ((( 345 -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.265 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 346 346 ))) 347 347 348 348 349 349 350 -=== 2.2. 8Use TCP protocol to uplink data ===270 +=== 2.2.7 Use TCP protocol to uplink data === 351 351 352 -This feature is supported since firmware version v110 353 353 354 354 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 355 355 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 356 356 357 -[[image: 1657352898400-901.png]]276 +[[image:image-20220709093918-1.png]] 358 358 359 359 360 -[[image: 1657352914475-252.png]]279 +[[image:image-20220709093918-2.png]] 361 361 362 362 363 363 364 -=== 2.2. 9Change Update Interval ===283 +=== 2.2.8 Change Update Interval === 365 365 366 366 User can use below command to change the (% style="color:green" %)**uplink interval**. 367 367 ... ... @@ -368,103 +368,69 @@ 368 368 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 369 369 370 370 ((( 371 - 290 +(% style="color:red" %)**NOTE:** 372 372 ))) 373 373 293 +((( 294 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 295 +))) 374 374 375 375 298 + 376 376 == 2.3 Uplink Payload == 377 377 301 +In this mode, uplink payload includes in total 14 bytes 378 378 379 -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. 380 380 304 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 305 +|=(% style="width: 80px;" %)((( 306 +**Size(bytes)** 307 +)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 308 +|(% 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.8A0DigitalInterrupt"]] 381 381 382 -For example: 310 +((( 311 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 312 +))) 383 383 384 - (% 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. 385 385 315 +[[image:1657331036973-987.png]] 386 386 387 -The uplink payloads are composed in ASCII String. For example: 388 - 389 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 390 - 391 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 392 - 393 - 394 -(% style="color:red" %)**NOTE:** 395 - 396 -(% style="color:red" %) 397 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 398 -1. By default, the device will send an uplink message every 1 hour. 399 - 400 - 401 -=== 2.3.1 Payload Analyze === 402 - 403 -N95S31B uplink payload includes in total 21 bytes 404 - 405 - 406 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 407 -|=(% style="width: 60px;" %)((( 408 -**Size(bytes)** 409 -)))|=(% 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** 410 -|(% 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" %)((( 411 411 ((( 412 - Reserve/Sameas NBSN95 CFGMOD=1318 +The payload is ASCII string, representative same HEX: 413 413 ))) 414 414 415 415 ((( 416 - No functionhere.322 +0x72403155615900640c6c19029200 where: 417 417 ))) 418 -)))|(% style="width:77px" %)((( 419 -((( 420 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 421 -))) 422 422 423 -((( 424 - BySHT31325 +* ((( 326 +Device ID: 0x724031556159 = 724031556159 425 425 ))) 426 -)))|(% style="width:80px" %)((( 427 -((( 428 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 328 +* ((( 329 +Version: 0x0064=100=1.0.0 429 429 ))) 430 430 431 -((( 432 -B y SHT31332 +* ((( 333 +BAT: 0x0c6c = 3180 mV = 3.180V 433 433 ))) 335 +* ((( 336 +Signal: 0x19 = 25 434 434 ))) 435 - 436 -((( 437 -((( 438 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 338 +* ((( 339 +Distance: 0x0292= 658 mm 439 439 ))) 440 -))) 341 +* ((( 342 +Interrupt: 0x00 = 0 441 441 442 442 443 -[[image:1657354294009-643.png]] 444 444 445 - 446 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 447 - 448 -* Device ID: 0x724031607457 = 724031607457 449 -* Version: 0x006e=110=1.1.0 450 - 451 -* BAT: 0x0ccd = 3277 mV = 3.277V 452 -* Signal: 0x1b = 27 453 -* Model: 0x01 = 1 454 -* 0x00dc000ccc= reserve, ignore in N95S31B 455 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 456 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 457 - 458 -((( 459 459 460 460 ))) 461 461 462 -((( 463 - 464 -))) 349 +== 2.4 Payload Explanation and Sensor Interface == 465 465 466 466 467 -=== 2. 3.2352 +=== 2.4.1 Device ID === 468 468 469 469 ((( 470 470 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -488,25 +488,24 @@ 488 488 489 489 490 490 491 -=== 2. 3.3Version Info ===376 +=== 2.4.2 Version Info === 492 492 378 +((( 379 +Specify the software version: 0x64=100, means firmware version 1.00. 380 +))) 493 493 494 -These bytes include the hardware and software version. 382 +((( 383 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 384 +))) 495 495 496 -Higher byte: Specify hardware version: always 0x00 for N95S31B 497 497 498 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 499 499 388 +=== 2.4.3 Battery Info === 500 500 501 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 502 - 503 503 ((( 504 - 391 +Check the battery voltage for LSE01. 505 505 ))) 506 506 507 - 508 -=== 2.3.4 Battery Info === 509 - 510 510 ((( 511 511 Ex1: 0x0B45 = 2885mV 512 512 ))) ... ... @@ -517,7 +517,7 @@ 517 517 518 518 519 519 520 -=== 2. 3.5Signal Strength ===404 +=== 2.4.4 Signal Strength === 521 521 522 522 ((( 523 523 NB-IoT Network signal Strength. ... ... @@ -549,26 +549,83 @@ 549 549 550 550 551 551 552 -=== 2. 3.6Temperature& Humidity===436 +=== 2.4.5 Distance === 553 553 554 - The devicewill beabletogetthe SHT31 temperatureand humiditydatanow and upload to IoT Server.438 +Get the distance. Flat object range 280mm - 7500mm. 555 555 556 - [[image:image-20220709161741-3.png]]440 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 557 557 442 +((( 443 +((( 444 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 445 +))) 446 +))) 558 558 559 -Convert the read byte to decimal and divide it by ten. 448 +((( 449 + 450 +))) 560 560 452 +((( 453 + 454 +))) 561 561 562 - **Example:**456 +=== 2.4.6 Digital Interrupt === 563 563 564 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 458 +((( 459 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 460 +))) 565 565 566 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 462 +((( 463 +The command is: 464 +))) 567 567 466 +((( 467 +(% 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]])**.** 468 +))) 568 568 569 569 570 -== 2.4 Downlink Payload == 471 +((( 472 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 473 +))) 571 571 475 + 476 +((( 477 +Example: 478 +))) 479 + 480 +((( 481 +0x(00): Normal uplink packet. 482 +))) 483 + 484 +((( 485 +0x(01): Interrupt Uplink Packet. 486 +))) 487 + 488 + 489 + 490 +=== 2.4.7 +5V Output === 491 + 492 +((( 493 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 494 +))) 495 + 496 + 497 +((( 498 +The 5V output time can be controlled by AT Command. 499 +))) 500 + 501 +((( 502 +(% style="color:blue" %)**AT+5VT=1000** 503 +))) 504 + 505 +((( 506 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 507 +))) 508 + 509 + 510 + 511 +== 2.5 Downlink Payload == 512 + 572 572 By default, NDDS75 prints the downlink payload to console port. 573 573 574 574 [[image:image-20220709100028-1.png]] ... ... @@ -619,16 +619,47 @@ 619 619 620 620 621 621 622 -== 2. 5BatteryAnalysis==563 +== 2.6 LED Indicator == 623 623 624 -=== 2.5.1 Battery Type === 625 625 566 +The NDDS75 has an internal LED which is to show the status of different state. 626 626 568 + 569 +* 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) 570 +* Then the LED will be on for 1 second means device is boot normally. 571 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 572 +* For each uplink probe, LED will be on for 500ms. 573 + 627 627 ((( 628 - TheN95S31B 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.575 + 629 629 ))) 630 630 578 + 579 + 580 +== 2.7 Firmware Change Log == 581 + 582 + 583 +Download URL & Firmware Change log 584 + 631 631 ((( 586 +[[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/]] 587 +))) 588 + 589 + 590 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 591 + 592 + 593 + 594 +== 2.8 Battery Analysis == 595 + 596 +=== 2.8.1 Battery Type === 597 + 598 + 599 +((( 600 +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. 601 +))) 602 + 603 +((( 632 632 The battery is designed to last for several years depends on the actually use environment and update interval. 633 633 ))) 634 634 ... ... @@ -646,35 +646,56 @@ 646 646 647 647 648 648 649 -=== 2. 5.2 Power consumption Analyze ===621 +=== 2.8.2 Power consumption Analyze === 650 650 651 651 ((( 652 - 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/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.624 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 653 653 ))) 654 654 627 + 655 655 ((( 656 - 629 +Instruction to use as below: 657 657 ))) 658 658 632 +((( 633 +(% 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/]] 634 +))) 659 659 660 -=== 2.5.3 Battery Note === 661 661 662 662 ((( 663 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.638 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 664 664 ))) 665 665 641 +* ((( 642 +Product Model 643 +))) 644 +* ((( 645 +Uplink Interval 646 +))) 647 +* ((( 648 +Working Mode 649 +))) 666 666 651 +((( 652 +And the Life expectation in difference case will be shown on the right. 653 +))) 667 667 668 - ===2.5.4 Replacethe battery ===655 +[[image:image-20220708141352-7.jpeg]] 669 669 670 670 658 + 659 +=== 2.8.3 Battery Note === 660 + 671 671 ((( 672 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.662 +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 transmit LoRa, then the battery life may be decreased. 673 673 ))) 674 674 675 675 666 + 667 +=== 2.8.4 Replace the battery === 668 + 676 676 ((( 677 -The default battery pack of N 95S31Bincludes 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).670 +The default battery pack of NDDS75 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 NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]693 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 701 701 702 702 703 703 AT+<CMD>? : Help on <CMD> ... ... @@ -785,9 +785,7 @@ 785 785 ))) 786 786 787 787 ((( 788 - 789 - 790 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 781 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 791 791 ))) 792 792 793 793 ... ... @@ -819,7 +819,7 @@ 819 819 = 7. Order Info = 820 820 821 821 822 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**813 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 823 823 824 824 825 825 (% class="wikigeneratedid" %) ... ... @@ -834,7 +834,7 @@ 834 834 835 835 (% style="color:#037691" %)**Package Includes**: 836 836 837 -* N 95S31BNB-IoTTemperatureandHumiditySensor828 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 838 838 * External antenna x 1 839 839 ))) 840 840 ... ... @@ -843,10 +843,11 @@ 843 843 844 844 (% style="color:#037691" %)**Dimension and weight**: 845 845 837 + 846 846 * Device Size: 13.0 x 5 x 4.5 cm 847 847 * Device Weight: 150g 848 -* Package Size / pcs : 1 4.0x8x 5 cm849 -* Weight / pcs : 180g840 +* Package Size / pcs : 15 x 12x 5.5 cm 841 +* Weight / pcs : 220g 850 850 ))) 851 851 852 852 (((
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content