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,51 @@ 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 69 70 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,9 +96,13 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 86 +(% style="color:#037691" %)**Power Consumption** 99 99 88 +* STOP Mode: 10uA @ 3.3v 89 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 100 100 101 101 92 + 102 102 == 1.4 Applications == 103 103 104 104 * Smart Buildings & Home Automation ... ... @@ -112,56 +112,25 @@ 112 112 113 113 114 114 106 + 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]]110 +[[image:1657328609906-564.png]] 120 120 121 121 122 -=== 1.5.1 Jumper JP2 === 123 123 124 - PoweronDevice when putthisjumper.114 += 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 -= 2. Use N95S31B to communicate with IoT Server = 154 - 155 155 == 2.1 How it works == 156 156 157 - 158 158 ((( 159 -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.119 +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. 160 160 ))) 161 161 162 162 163 163 ((( 164 -The diagram below shows the working flow in default firmware of N 95S31B:124 +The diagram below shows the working flow in default firmware of NDDS75: 165 165 ))) 166 166 167 167 ((( ... ... @@ -168,7 +168,7 @@ 168 168 169 169 ))) 170 170 171 -[[image:16573 50248151-650.png]]131 +[[image:1657328659945-416.png]] 172 172 173 173 ((( 174 174 ... ... @@ -175,45 +175,30 @@ 175 175 ))) 176 176 177 177 178 -== 2.2 Configure the N 95S31B==138 +== 2.2 Configure the NDDS75 == 179 179 180 180 181 -=== 2.2.1 Power On N95S31B === 182 - 183 - 184 -[[image:image-20220709150546-2.png]] 185 - 186 - 187 187 === 2.2.1 Test Requirement === 188 188 143 +((( 144 +To use NDDS75 in your city, make sure meet below requirements: 145 +))) 189 189 190 -To use N95S31B in your city, make sure meet below requirements: 191 - 192 192 * Your local operator has already distributed a NB-IoT Network there. 193 -* The local NB-IoT network used the band that N 95S31Bsupports.148 +* The local NB-IoT network used the band that NSE01 supports. 194 194 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 195 195 196 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 197 - 198 -N95S31B supports different communication protocol such as : 199 - 200 200 ((( 201 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 202 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 203 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 204 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 205 - 206 -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. 207 - 208 - 152 +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 209 209 ))) 210 210 211 -[[image:1657350625843-586.png]] 212 212 156 +[[image:1657328756309-230.png]] 213 213 214 214 215 -=== 2.2.3 Insert SIM card === 216 216 160 +=== 2.2.2 Insert SIM card === 161 + 217 217 ((( 218 218 Insert the NB-IoT Card get from your provider. 219 219 ))) ... ... @@ -223,19 +223,19 @@ 223 223 ))) 224 224 225 225 226 -[[image:16573 51240556-536.png]]171 +[[image:1657328884227-504.png]] 227 227 228 228 229 229 230 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===175 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 231 231 232 232 ((( 233 233 ((( 234 -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.179 +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. 235 235 ))) 236 236 ))) 237 237 238 -[[image: 1657351312545-300.png]]183 +[[image:image-20220709092052-2.png]] 239 239 240 240 **Connection:** 241 241 ... ... @@ -255,110 +255,90 @@ 255 255 * Flow Control: (% style="color:green" %)**None** 256 256 257 257 ((( 258 -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.203 +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. 259 259 ))) 260 260 261 261 [[image:1657329814315-101.png]] 262 262 263 263 ((( 264 -(% 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/]]209 +(% 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/]] 265 265 ))) 266 266 267 267 268 268 269 -=== 2.2. 5Use CoAP protocol to uplink data ===214 +=== 2.2.4 Use CoAP protocol to uplink data === 270 270 271 271 (% 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/]] 272 272 273 273 274 -((( 275 275 **Use below commands:** 276 -))) 277 277 278 -* ((( 279 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 280 -))) 281 -* ((( 282 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 283 -))) 284 -* ((( 285 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 286 -))) 221 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 222 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 223 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 287 287 288 -((( 289 - 290 - 291 291 For parameter description, please refer to AT command set 292 -))) 293 293 294 -[[image:1657352 146020-183.png]]227 +[[image:1657330452568-615.png]] 295 295 296 296 297 -((( 298 298 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. 299 -))) 300 300 301 -[[image:16573 52185396-303.png]]232 +[[image:1657330472797-498.png]] 302 302 303 303 304 304 305 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===236 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 306 306 307 307 308 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 239 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 309 309 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 310 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 241 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 311 311 312 -[[image:16573 52391268-297.png]]243 +[[image:1657330501006-241.png]] 313 313 314 314 315 -[[image:16573 52403317-397.png]]246 +[[image:1657330533775-472.png]] 316 316 317 317 318 318 319 -=== 2.2. 7Use MQTT protocol to uplink data ===250 +=== 2.2.6 Use MQTT protocol to uplink data === 320 320 321 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 322 322 323 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 324 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 325 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 326 -* (% style="color:blue" %)**AT+UNAME=UNAME 327 -* (% style="color:blue" %)**AT+PWD=PWD 328 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527329 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)253 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 254 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 255 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 256 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 257 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 258 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 259 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 330 330 331 -[[image:1657 352634421-276.png]]261 +[[image:1657249978444-674.png]] 332 332 333 333 334 -[[image:16573 52645687-385.png]]264 +[[image:1657330723006-866.png]] 335 335 336 -((( 337 -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. 338 -))) 339 339 340 - 341 341 ((( 342 -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.268 +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. 343 343 ))) 344 344 345 345 346 346 347 -=== 2.2. 8Use TCP protocol to uplink data ===273 +=== 2.2.7 Use TCP protocol to uplink data === 348 348 349 -This feature is supported since firmware version v110 350 350 351 351 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 352 352 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 353 353 354 -[[image: 1657352898400-901.png]]279 +[[image:image-20220709093918-1.png]] 355 355 356 356 357 -[[image: 1657352914475-252.png]]282 +[[image:image-20220709093918-2.png]] 358 358 359 359 360 360 361 -=== 2.2. 9Change Update Interval ===286 +=== 2.2.8 Change Update Interval === 362 362 363 363 User can use below command to change the (% style="color:green" %)**uplink interval**. 364 364 ... ... @@ -365,103 +365,69 @@ 365 365 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 366 366 367 367 ((( 368 - 293 +(% style="color:red" %)**NOTE:** 369 369 ))) 370 370 296 +((( 297 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 298 +))) 371 371 372 372 301 + 373 373 == 2.3 Uplink Payload == 374 374 304 +In this mode, uplink payload includes in total 14 bytes 375 375 376 -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. 377 377 307 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 308 +|=(% style="width: 80px;" %)((( 309 +**Size(bytes)** 310 +)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 311 +|(% 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"]] 378 378 379 -For example: 313 +((( 314 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 315 +))) 380 380 381 - (% 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. 382 382 318 +[[image:1657331036973-987.png]] 383 383 384 -The uplink payloads are composed in ASCII String. For example: 385 - 386 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 387 - 388 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 389 - 390 - 391 -(% style="color:red" %)**NOTE:** 392 - 393 -(% style="color:red" %) 394 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 395 -1. By default, the device will send an uplink message every 1 hour. 396 - 397 - 398 -=== 2.3.1 Payload Analyze === 399 - 400 -N95S31B uplink payload includes in total 21 bytes 401 - 402 - 403 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 404 -|=(% style="width: 60px;" %)((( 405 -**Size(bytes)** 406 -)))|=(% 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** 407 -|(% 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" %)((( 408 408 ((( 409 - Reserve/Sameas NBSN95 CFGMOD=1321 +The payload is ASCII string, representative same HEX: 410 410 ))) 411 411 412 412 ((( 413 - No functionhere.325 +0x72403155615900640c6c19029200 where: 414 414 ))) 415 -)))|(% style="width:77px" %)((( 416 -((( 417 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 418 -))) 419 419 420 -((( 421 - BySHT31328 +* ((( 329 +Device ID: 0x724031556159 = 724031556159 422 422 ))) 423 -)))|(% style="width:80px" %)((( 424 -((( 425 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 331 +* ((( 332 +Version: 0x0064=100=1.0.0 426 426 ))) 427 427 428 -((( 429 -B y SHT31335 +* ((( 336 +BAT: 0x0c6c = 3180 mV = 3.180V 430 430 ))) 338 +* ((( 339 +Signal: 0x19 = 25 431 431 ))) 432 - 433 -((( 434 -((( 435 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 341 +* ((( 342 +Distance: 0x0292= 658 mm 436 436 ))) 437 -))) 344 +* ((( 345 +Interrupt: 0x00 = 0 438 438 439 439 440 -[[image:1657354294009-643.png]] 441 441 442 - 443 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 444 - 445 -* Device ID: 0x724031607457 = 724031607457 446 -* Version: 0x006e=110=1.1.0 447 - 448 -* BAT: 0x0ccd = 3277 mV = 3.277V 449 -* Signal: 0x1b = 27 450 -* Model: 0x01 = 1 451 -* 0x00dc000ccc= reserve, ignore in N95S31B 452 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 453 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 454 - 455 -((( 456 456 457 457 ))) 458 458 459 -((( 460 - 461 -))) 352 +== 2.4 Payload Explanation and Sensor Interface == 462 462 463 463 464 -=== 2. 3.2355 +=== 2.4.1 Device ID === 465 465 466 466 ((( 467 467 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -485,25 +485,24 @@ 485 485 486 486 487 487 488 -=== 2. 3.3Version Info ===379 +=== 2.4.2 Version Info === 489 489 381 +((( 382 +Specify the software version: 0x64=100, means firmware version 1.00. 383 +))) 490 490 491 -These bytes include the hardware and software version. 385 +((( 386 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 387 +))) 492 492 493 -Higher byte: Specify hardware version: always 0x00 for N95S31B 494 494 495 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 496 496 391 +=== 2.4.3 Battery Info === 497 497 498 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 499 - 500 500 ((( 501 - 394 +Check the battery voltage for LSE01. 502 502 ))) 503 503 504 - 505 -=== 2.3.4 Battery Info === 506 - 507 507 ((( 508 508 Ex1: 0x0B45 = 2885mV 509 509 ))) ... ... @@ -514,7 +514,7 @@ 514 514 515 515 516 516 517 -=== 2. 3.5Signal Strength ===407 +=== 2.4.4 Signal Strength === 518 518 519 519 ((( 520 520 NB-IoT Network signal Strength. ... ... @@ -546,26 +546,83 @@ 546 546 547 547 548 548 549 -=== 2. 3.6Temperature& Humidity===439 +=== 2.4.5 Distance === 550 550 551 - The devicewill beabletogetthe SHT31 temperatureand humiditydatanow and upload to IoT Server.441 +Get the distance. Flat object range 280mm - 7500mm. 552 552 553 - [[image:image-20220709161741-3.png]]443 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 554 554 445 +((( 446 +((( 447 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 448 +))) 449 +))) 555 555 556 -Convert the read byte to decimal and divide it by ten. 451 +((( 452 + 453 +))) 557 557 455 +((( 456 + 457 +))) 558 558 559 - **Example:**459 +=== 2.4.6 Digital Interrupt === 560 560 561 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 461 +((( 462 +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. 463 +))) 562 562 563 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 465 +((( 466 +The command is: 467 +))) 564 564 469 +((( 470 +(% 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]])**.** 471 +))) 565 565 566 566 567 -== 2.4 Downlink Payload == 474 +((( 475 +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. 476 +))) 568 568 478 + 479 +((( 480 +Example: 481 +))) 482 + 483 +((( 484 +0x(00): Normal uplink packet. 485 +))) 486 + 487 +((( 488 +0x(01): Interrupt Uplink Packet. 489 +))) 490 + 491 + 492 + 493 +=== 2.4.7 +5V Output === 494 + 495 +((( 496 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 497 +))) 498 + 499 + 500 +((( 501 +The 5V output time can be controlled by AT Command. 502 +))) 503 + 504 +((( 505 +(% style="color:blue" %)**AT+5VT=1000** 506 +))) 507 + 508 +((( 509 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 510 +))) 511 + 512 + 513 + 514 +== 2.5 Downlink Payload == 515 + 569 569 By default, NDDS75 prints the downlink payload to console port. 570 570 571 571 [[image:image-20220709100028-1.png]] ... ... @@ -616,16 +616,47 @@ 616 616 617 617 618 618 619 -== 2. 5BatteryAnalysis==566 +== 2.6 LED Indicator == 620 620 621 -=== 2.5.1 Battery Type === 622 622 569 +The NDDS75 has an internal LED which is to show the status of different state. 623 623 571 + 572 +* 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) 573 +* Then the LED will be on for 1 second means device is boot normally. 574 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 575 +* For each uplink probe, LED will be on for 500ms. 576 + 624 624 ((( 625 - 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.578 + 626 626 ))) 627 627 581 + 582 + 583 +== 2.7 Firmware Change Log == 584 + 585 + 586 +Download URL & Firmware Change log 587 + 628 628 ((( 589 +[[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/]] 590 +))) 591 + 592 + 593 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 594 + 595 + 596 + 597 +== 2.8 Battery Analysis == 598 + 599 +=== 2.8.1 Battery Type === 600 + 601 + 602 +((( 603 +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. 604 +))) 605 + 606 +((( 629 629 The battery is designed to last for several years depends on the actually use environment and update interval. 630 630 ))) 631 631 ... ... @@ -643,35 +643,56 @@ 643 643 644 644 645 645 646 -=== 2. 5.2 Power consumption Analyze ===624 +=== 2.8.2 Power consumption Analyze === 647 647 648 648 ((( 649 - 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.627 +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. 650 650 ))) 651 651 630 + 652 652 ((( 653 - 632 +Instruction to use as below: 654 654 ))) 655 655 635 +((( 636 +(% 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/]] 637 +))) 656 656 657 -=== 2.5.3 Battery Note === 658 658 659 659 ((( 660 - 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.641 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 661 661 ))) 662 662 644 +* ((( 645 +Product Model 646 +))) 647 +* ((( 648 +Uplink Interval 649 +))) 650 +* ((( 651 +Working Mode 652 +))) 663 663 654 +((( 655 +And the Life expectation in difference case will be shown on the right. 656 +))) 664 664 665 - === 2.5.4 Replacethe battery ===658 +[[image:image-20220709110451-3.png]] 666 666 667 667 661 + 662 +=== 2.8.3 Battery Note === 663 + 668 668 ((( 669 - 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.665 +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. 670 670 ))) 671 671 672 672 669 + 670 +=== 2.8.4 Replace the battery === 671 + 673 673 ((( 674 -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).673 +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). 675 675 ))) 676 676 677 677 ... ... @@ -694,7 +694,7 @@ 694 694 695 695 == 4.1 Access AT Commands == 696 696 697 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]696 +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/]] 698 698 699 699 700 700 AT+<CMD>? : Help on <CMD> ... ... @@ -782,9 +782,7 @@ 782 782 ))) 783 783 784 784 ((( 785 - 786 - 787 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 784 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 788 788 ))) 789 789 790 790 ... ... @@ -816,7 +816,7 @@ 816 816 = 7. Order Info = 817 817 818 818 819 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**816 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 820 820 821 821 822 822 (% class="wikigeneratedid" %) ... ... @@ -831,7 +831,7 @@ 831 831 832 832 (% style="color:#037691" %)**Package Includes**: 833 833 834 -* N 95S31BNB-IoTTemperatureandHumiditySensor831 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 835 835 * External antenna x 1 836 836 ))) 837 837 ... ... @@ -840,10 +840,11 @@ 840 840 841 841 (% style="color:#037691" %)**Dimension and weight**: 842 842 840 + 843 843 * Device Size: 13.0 x 5 x 4.5 cm 844 844 * Device Weight: 150g 845 -* Package Size / pcs : 1 4.0x8x 5 cm846 -* Weight / pcs : 180g843 +* Package Size / pcs : 15 x 12x 5.5 cm 844 +* Weight / pcs : 220g 847 847 ))) 848 848 849 849 (((
- 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