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,45 +15,48 @@ 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 -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*. 24 +((( 25 +The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data. 26 +\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 27 +\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 28 +\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 29 +\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 30 +\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 31 +))) 26 26 27 -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. 28 - 29 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 30 - 31 -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). 32 - 33 - 34 -~* make sure you have NB-IoT coverage locally. 35 - 36 36 37 37 ))) 38 38 39 -[[image:16573 48284168-431.png]]36 +[[image:1657327959271-447.png]] 40 40 41 41 42 42 43 43 == 1.2 Features == 44 44 42 + 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 -* Monitor Temperature & Humidity via SHT31 44 +* Ultra low power consumption 45 +* Distance Detection by Ultrasonic technology 46 +* Flat object range 280mm - 7500mm 47 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 48 +* Cable Length: 25cm 47 47 * AT Commands to change parameters 48 48 * Uplink on periodically 49 49 * Downlink to change configure 50 50 * IP66 Waterproof Enclosure 51 -* Ultra-Low Power consumption 52 -* AT Commands to change parameters 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 56 56 57 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -73,7 +73,6 @@ 73 73 74 74 (% style="color:#037691" %)**Battery:** 75 75 76 - 77 77 * Li/SOCI2 un-chargeable battery 78 78 * Capacity: 8500mAh 79 79 * Self Discharge: <1% / Year @ 25°C ... ... @@ -80,7 +80,13 @@ 80 80 * Max continuously current: 130mA 81 81 * Max boost current: 2A, 1 second 82 82 83 +(% style="color:#037691" %)**Power Consumption** 83 83 85 +* STOP Mode: 10uA @ 3.3v 86 +* Max transmit power: 350mA@3.3v 87 + 88 + 89 + 84 84 == 1.4 Applications == 85 85 86 86 * Smart Buildings & Home Automation ... ... @@ -96,50 +96,22 @@ 96 96 97 97 == 1.5 Pin Definitions == 98 98 99 -N95S31B use the mother board from NBSN95 which as below. 100 100 101 -[[image: image-20220709144723-1.png]]106 +[[image:1657328609906-564.png]] 102 102 103 103 104 -=== 1.5.1 Jumper JP2 === 105 105 106 - PoweronDevice when putthisjumper.110 += 2. Use NDDS75 to communicate with IoT Server = 107 107 108 - 109 - 110 -=== 1.5.2 BOOT MODE / SW1 === 111 - 112 -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. 113 - 114 -2) Flash: work mode, device starts to work and send out console output for further debug 115 - 116 - 117 - 118 -=== 1.5.3 Reset Button === 119 - 120 -Press to reboot the device. 121 - 122 - 123 - 124 -=== 1.5.4 LED === 125 - 126 -It will flash: 127 - 128 -1. When boot the device in flash mode 129 -1. Send an uplink packet 130 - 131 -= 2. Use N95S31B to communicate with IoT Server = 132 - 133 133 == 2.1 How it works == 134 134 135 - 136 136 ((( 137 -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.115 +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. 138 138 ))) 139 139 140 140 141 141 ((( 142 -The diagram below shows the working flow in default firmware of N 95S31B:120 +The diagram below shows the working flow in default firmware of NDDS75: 143 143 ))) 144 144 145 145 ((( ... ... @@ -146,7 +146,7 @@ 146 146 147 147 ))) 148 148 149 -[[image:16573 50248151-650.png]]127 +[[image:1657328659945-416.png]] 150 150 151 151 ((( 152 152 ... ... @@ -153,45 +153,30 @@ 153 153 ))) 154 154 155 155 156 -== 2.2 Configure the N 95S31B==134 +== 2.2 Configure the NDDS75 == 157 157 158 158 159 -=== 2.2.1 Power On N95S31B === 160 - 161 - 162 -[[image:image-20220709150546-2.png]] 163 - 164 - 165 165 === 2.2.1 Test Requirement === 166 166 139 +((( 140 +To use NDDS75 in your city, make sure meet below requirements: 141 +))) 167 167 168 -To use N95S31B in your city, make sure meet below requirements: 169 - 170 170 * Your local operator has already distributed a NB-IoT Network there. 171 -* The local NB-IoT network used the band that N 95S31Bsupports.144 +* The local NB-IoT network used the band that NSE01 supports. 172 172 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 173 173 174 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 175 - 176 -N95S31B supports different communication protocol such as : 177 - 178 178 ((( 179 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 180 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 181 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 182 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 183 - 184 -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. 185 - 186 - 148 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server 187 187 ))) 188 188 189 -[[image:1657350625843-586.png]] 190 190 152 +[[image:1657328756309-230.png]] 191 191 192 192 193 -=== 2.2.3 Insert SIM card === 194 194 156 +=== 2.2.2 Insert SIM card === 157 + 195 195 ((( 196 196 Insert the NB-IoT Card get from your provider. 197 197 ))) ... ... @@ -201,19 +201,19 @@ 201 201 ))) 202 202 203 203 204 -[[image:16573 51240556-536.png]]167 +[[image:1657328884227-504.png]] 205 205 206 206 207 207 208 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===171 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 209 209 210 210 ((( 211 211 ((( 212 -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.175 +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. 213 213 ))) 214 214 ))) 215 215 216 -[[image: 1657351312545-300.png]]179 +[[image:image-20220709092052-2.png]] 217 217 218 218 **Connection:** 219 219 ... ... @@ -233,54 +233,40 @@ 233 233 * Flow Control: (% style="color:green" %)**None** 234 234 235 235 ((( 236 -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.199 +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. 237 237 ))) 238 238 239 239 [[image:1657329814315-101.png]] 240 240 241 241 ((( 242 -(% 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/]]205 +(% 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/]] 243 243 ))) 244 244 245 245 246 246 247 -=== 2.2. 5Use CoAP protocol to uplink data ===210 +=== 2.2.4 Use CoAP protocol to uplink data === 248 248 249 249 (% 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/]] 250 250 251 251 252 -((( 253 253 **Use below commands:** 254 -))) 255 255 256 -* ((( 257 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 258 -))) 259 -* ((( 260 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 261 -))) 262 -* ((( 263 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 264 -))) 217 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 218 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 219 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 265 265 266 -((( 267 - 268 - 269 269 For parameter description, please refer to AT command set 270 -))) 271 271 272 -[[image:1657352 146020-183.png]]223 +[[image:1657330452568-615.png]] 273 273 274 274 275 -((( 276 276 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. 277 -))) 278 278 279 -[[image:16573 52185396-303.png]]228 +[[image:1657330472797-498.png]] 280 280 281 281 282 282 283 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===232 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 284 284 285 285 286 286 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -287,56 +287,50 @@ 287 287 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 288 288 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 289 289 290 -[[image:16573 52391268-297.png]]239 +[[image:1657330501006-241.png]] 291 291 292 292 293 -[[image:16573 52403317-397.png]]242 +[[image:1657330533775-472.png]] 294 294 295 295 296 296 297 -=== 2.2. 7Use MQTT protocol to uplink data ===246 +=== 2.2.6 Use MQTT protocol to uplink data === 298 298 299 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 300 300 301 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 302 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 303 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 304 -* (% style="color:blue" %)**AT+UNAME=UNAME 305 -* (% style="color:blue" %)**AT+PWD=PWD 306 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527307 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)249 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 250 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 251 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 252 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 253 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 254 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 255 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 308 308 309 -[[image:1657 352634421-276.png]]257 +[[image:1657249978444-674.png]] 310 310 311 311 312 -[[image:16573 52645687-385.png]]260 +[[image:1657330723006-866.png]] 313 313 314 -((( 315 -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. 316 -))) 317 317 318 - 319 319 ((( 320 -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.264 +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. 321 321 ))) 322 322 323 323 324 324 325 -=== 2.2. 8Use TCP protocol to uplink data ===269 +=== 2.2.7 Use TCP protocol to uplink data === 326 326 327 -This feature is supported since firmware version v110 328 328 329 329 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 330 330 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 331 331 332 -[[image: 1657352898400-901.png]]275 +[[image:image-20220709093918-1.png]] 333 333 334 334 335 -[[image: 1657352914475-252.png]]278 +[[image:image-20220709093918-2.png]] 336 336 337 337 338 338 339 -=== 2.2. 9Change Update Interval ===282 +=== 2.2.8 Change Update Interval === 340 340 341 341 User can use below command to change the (% style="color:green" %)**uplink interval**. 342 342 ... ... @@ -343,90 +343,69 @@ 343 343 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 344 344 345 345 ((( 346 - 289 +(% style="color:red" %)**NOTE:** 347 347 ))) 348 348 292 +((( 293 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 294 +))) 349 349 350 350 297 + 351 351 == 2.3 Uplink Payload == 352 352 300 +In this mode, uplink payload includes in total 14 bytes 353 353 354 -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. 355 355 303 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 304 +|=(% style="width: 80px;" %)((( 305 +**Size(bytes)** 306 +)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 307 +|(% 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"]] 356 356 357 -For example: 309 +((( 310 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 311 +))) 358 358 359 - (% 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. 360 360 314 +[[image:1657331036973-987.png]] 361 361 362 -The uplink payloads are composed in ASCII String. For example: 316 +((( 317 +The payload is ASCII string, representative same HEX: 318 +))) 363 363 364 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 320 +((( 321 +0x72403155615900640c6c19029200 where: 322 +))) 365 365 366 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 367 - 368 - 369 -(% style="color:red" %)**NOTE:** 370 - 371 -(% style="color:red" %) 372 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 373 -1. By default, the device will send an uplink message every 1 hour. 374 - 375 -=== 2.3.1 Payload Analyze === 376 - 377 -N95S31B uplink payload includes in total 21 bytes 378 - 379 - 380 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 381 -|=(% style="width: 60px;" %)((( 382 -**Size(bytes)** 383 -)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 384 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 385 -Reserve/ Same as NBSN95 CFGMOD=1 386 - 387 -No function here. 388 -)))|(% style="width:77px" %)((( 389 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 390 - 391 -By SHT31 392 -)))|(% style="width:80px" %)((( 393 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 394 - 395 -By SHT31 324 +* ((( 325 +Device ID: 0x724031556159 = 724031556159 396 396 ))) 327 +* ((( 328 +Version: 0x0064=100=1.0.0 329 +))) 397 397 398 -((( 399 -((( 400 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 331 +* ((( 332 +BAT: 0x0c6c = 3180 mV = 3.180V 401 401 ))) 334 +* ((( 335 +Signal: 0x19 = 25 402 402 ))) 337 +* ((( 338 +Distance: 0x0292= 658 mm 339 +))) 340 +* ((( 341 +Interrupt: 0x00 = 0 403 403 404 404 405 -[[image:1657354294009-643.png]] 406 406 407 - 408 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 409 - 410 -* Device ID: 0x724031607457 = 724031607457 411 -* Version: 0x006e=110=1.1.0 412 - 413 -* BAT: 0x0ccd = 3277 mV = 3.277V 414 -* Signal: 0x1b = 27 415 -* Model: 0x01 = 1 416 -* 0x00dc000ccc= reserve, ignore in N95S31B 417 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 418 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 419 - 420 -((( 421 421 422 422 ))) 423 423 424 -((( 425 - 426 -))) 348 +== 2.4 Payload Explanation and Sensor Interface == 427 427 428 428 429 -=== 2. 3.2351 +=== 2.4.1 Device ID === 430 430 431 431 ((( 432 432 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -450,25 +450,20 @@ 450 450 451 451 452 452 453 -=== 2. 3.3Version Info ===375 +=== 2.4.2 Version Info === 454 454 377 +((( 378 +Specify the software version: 0x64=100, means firmware version 1.00. 379 +))) 455 455 456 -These bytes include the hardware and software version. 457 - 458 -Higher byte: Specify hardware version: always 0x00 for N95S31B 459 - 460 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 461 - 462 - 463 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 464 - 465 465 ((( 466 - 382 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 467 467 ))) 468 468 469 469 470 -=== 2.3.4 Battery Info === 471 471 387 +=== 2.4.3 Battery Info === 388 + 472 472 ((( 473 473 Ex1: 0x0B45 = 2885mV 474 474 ))) ... ... @@ -479,7 +479,7 @@ 479 479 480 480 481 481 482 -=== 2. 3.5Signal Strength ===399 +=== 2.4.4 Signal Strength === 483 483 484 484 ((( 485 485 NB-IoT Network signal Strength. ... ... @@ -511,26 +511,83 @@ 511 511 512 512 513 513 514 -=== 2. 3.6Temperature& Humidity===431 +=== 2.4.5 Distance === 515 515 516 - The devicewill beabletogetthe SHT31 temperatureand humiditydatanow and upload to IoT Server.433 +Get the distance. Flat object range 280mm - 7500mm. 517 517 518 - [[image:image-20220709161741-3.png]]435 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 519 519 437 +((( 438 +((( 439 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 440 +))) 441 +))) 520 520 521 -Convert the read byte to decimal and divide it by ten. 443 +((( 444 + 445 +))) 522 522 447 +((( 448 + 449 +))) 523 523 524 - **Example:**451 +=== 2.4.6 Digital Interrupt === 525 525 526 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 453 +((( 454 +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. 455 +))) 527 527 528 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 457 +((( 458 +The command is: 459 +))) 529 529 461 +((( 462 +(% 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]])**.** 463 +))) 530 530 531 531 532 -== 2.4 Downlink Payload == 466 +((( 467 +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. 468 +))) 533 533 470 + 471 +((( 472 +Example: 473 +))) 474 + 475 +((( 476 +0x(00): Normal uplink packet. 477 +))) 478 + 479 +((( 480 +0x(01): Interrupt Uplink Packet. 481 +))) 482 + 483 + 484 + 485 +=== 2.4.7 +5V Output === 486 + 487 +((( 488 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 489 +))) 490 + 491 + 492 +((( 493 +The 5V output time can be controlled by AT Command. 494 +))) 495 + 496 +((( 497 +(% style="color:blue" %)**AT+5VT=1000** 498 +))) 499 + 500 +((( 501 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 502 +))) 503 + 504 + 505 + 506 +== 2.5 Downlink Payload == 507 + 534 534 By default, NDDS75 prints the downlink payload to console port. 535 535 536 536 [[image:image-20220709100028-1.png]] ... ... @@ -581,16 +581,47 @@ 581 581 582 582 583 583 584 -== 2. 5BatteryAnalysis==558 +== 2.6 LED Indicator == 585 585 586 -=== 2.5.1 Battery Type === 587 587 561 +The NDDS75 has an internal LED which is to show the status of different state. 588 588 563 + 564 +* 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) 565 +* Then the LED will be on for 1 second means device is boot normally. 566 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 567 +* For each uplink probe, LED will be on for 500ms. 568 + 589 589 ((( 590 - 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.570 + 591 591 ))) 592 592 573 + 574 + 575 +== 2.7 Firmware Change Log == 576 + 577 + 578 +Download URL & Firmware Change log 579 + 593 593 ((( 581 +[[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/]] 582 +))) 583 + 584 + 585 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 586 + 587 + 588 + 589 +== 2.8 Battery Analysis == 590 + 591 +=== 2.8.1 Battery Type === 592 + 593 + 594 +((( 595 +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. 596 +))) 597 + 598 +((( 594 594 The battery is designed to last for several years depends on the actually use environment and update interval. 595 595 ))) 596 596 ... ... @@ -608,35 +608,56 @@ 608 608 609 609 610 610 611 -=== 2. 5.2 Power consumption Analyze ===616 +=== 2.8.2 Power consumption Analyze === 612 612 613 613 ((( 614 - 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.619 +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. 615 615 ))) 616 616 622 + 617 617 ((( 618 - 624 +Instruction to use as below: 619 619 ))) 620 620 627 +((( 628 +(% 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/]] 629 +))) 621 621 622 -=== 2.5.3 Battery Note === 623 623 624 624 ((( 625 - 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.633 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 626 626 ))) 627 627 636 +* ((( 637 +Product Model 638 +))) 639 +* ((( 640 +Uplink Interval 641 +))) 642 +* ((( 643 +Working Mode 644 +))) 628 628 646 +((( 647 +And the Life expectation in difference case will be shown on the right. 648 +))) 629 629 630 - === 2.5.4 Replacethe battery ===650 +[[image:image-20220709110451-3.png]] 631 631 632 632 653 + 654 +=== 2.8.3 Battery Note === 655 + 633 633 ((( 634 - 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.657 +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. 635 635 ))) 636 636 637 637 661 + 662 +=== 2.8.4 Replace the battery === 663 + 638 638 ((( 639 -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).665 +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). 640 640 ))) 641 641 642 642 ... ... @@ -659,7 +659,7 @@ 659 659 660 660 == 4.1 Access AT Commands == 661 661 662 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]688 +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/]] 663 663 664 664 665 665 AT+<CMD>? : Help on <CMD> ... ... @@ -747,9 +747,7 @@ 747 747 ))) 748 748 749 749 ((( 750 - 751 - 752 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 776 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 753 753 ))) 754 754 755 755 ... ... @@ -781,7 +781,7 @@ 781 781 = 7. Order Info = 782 782 783 783 784 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**808 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 785 785 786 786 787 787 (% class="wikigeneratedid" %) ... ... @@ -796,7 +796,7 @@ 796 796 797 797 (% style="color:#037691" %)**Package Includes**: 798 798 799 -* N 95S31BNB-IoTTemperatureandHumiditySensor823 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 800 800 * External antenna x 1 801 801 ))) 802 802 ... ... @@ -805,10 +805,11 @@ 805 805 806 806 (% style="color:#037691" %)**Dimension and weight**: 807 807 832 + 808 808 * Device Size: 13.0 x 5 x 4.5 cm 809 809 * Device Weight: 150g 810 -* Package Size / pcs : 1 4.0x8x 5 cm811 -* Weight / pcs : 180g835 +* Package Size / pcs : 15 x 12x 5.5 cm 836 +* Weight / pcs : 220g 812 812 ))) 813 813 814 814 (((
- 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