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