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, 19 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-20220709110451-3.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,54 +15,46 @@ 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 ... ... @@ -85,7 +85,6 @@ 85 85 86 86 (% style="color:#037691" %)**Battery:** 87 87 88 - 89 89 * Li/SOCI2 un-chargeable battery 90 90 * Capacity: 8500mAh 91 91 * Self Discharge: <1% / Year @ 25°C ... ... @@ -92,6 +92,12 @@ 92 92 * Max continuously current: 130mA 93 93 * Max boost current: 2A, 1 second 94 94 84 +(% style="color:#037691" %)**Power Consumption** 85 + 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 88 + 89 + 95 95 == 1.4 Applications == 96 96 97 97 * Smart Buildings & Home Automation ... ... @@ -105,52 +105,25 @@ 105 105 106 106 107 107 103 + 108 108 == 1.5 Pin Definitions == 109 109 110 -N95S31B use the mother board from NBSN95 which as below. 111 111 112 -[[image: image-20220709144723-1.png]]107 +[[image:1657328609906-564.png]] 113 113 114 114 115 -=== 1.5.1 Jumper JP2 === 116 116 117 - PoweronDevice when putthisjumper.111 += 2. Use NDDS75 to communicate with IoT Server = 118 118 119 - 120 - 121 -=== 1.5.2 BOOT MODE / SW1 === 122 - 123 -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. 124 - 125 -2) Flash: work mode, device starts to work and send out console output for further debug 126 - 127 - 128 - 129 -=== 1.5.3 Reset Button === 130 - 131 -Press to reboot the device. 132 - 133 - 134 - 135 -=== 1.5.4 LED === 136 - 137 -It will flash: 138 - 139 -1. When boot the device in flash mode 140 -1. Send an uplink packet 141 - 142 -= 2. Use N95S31B to communicate with IoT Server = 143 - 144 144 == 2.1 How it works == 145 145 146 - 147 147 ((( 148 -The N 95S31Bis equipped with a NB-IoT module, the pre-loaded firmware in N95S31Bwill get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B.116 +The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75. 149 149 ))) 150 150 151 151 152 152 ((( 153 -The diagram below shows the working flow in default firmware of N 95S31B:121 +The diagram below shows the working flow in default firmware of NDDS75: 154 154 ))) 155 155 156 156 ((( ... ... @@ -157,7 +157,7 @@ 157 157 158 158 ))) 159 159 160 -[[image:16573 50248151-650.png]]128 +[[image:1657328659945-416.png]] 161 161 162 162 ((( 163 163 ... ... @@ -164,45 +164,30 @@ 164 164 ))) 165 165 166 166 167 -== 2.2 Configure the N 95S31B==135 +== 2.2 Configure the NDDS75 == 168 168 169 169 170 -=== 2.2.1 Power On N95S31B === 171 - 172 - 173 -[[image:image-20220709150546-2.png]] 174 - 175 - 176 176 === 2.2.1 Test Requirement === 177 177 140 +((( 141 +To use NDDS75 in your city, make sure meet below requirements: 142 +))) 178 178 179 -To use N95S31B in your city, make sure meet below requirements: 180 - 181 181 * Your local operator has already distributed a NB-IoT Network there. 182 -* The local NB-IoT network used the band that N 95S31Bsupports.145 +* The local NB-IoT network used the band that NSE01 supports. 183 183 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 184 184 185 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 186 - 187 -N95S31B supports different communication protocol such as : 188 - 189 189 ((( 190 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 191 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 192 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 193 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 194 - 195 -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. 196 - 197 - 149 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server 198 198 ))) 199 199 200 -[[image:1657350625843-586.png]] 201 201 153 +[[image:1657328756309-230.png]] 202 202 203 203 204 -=== 2.2.3 Insert SIM card === 205 205 157 +=== 2.2.2 Insert SIM card === 158 + 206 206 ((( 207 207 Insert the NB-IoT Card get from your provider. 208 208 ))) ... ... @@ -212,19 +212,19 @@ 212 212 ))) 213 213 214 214 215 -[[image:16573 51240556-536.png]]168 +[[image:1657328884227-504.png]] 216 216 217 217 218 218 219 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===172 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 220 220 221 221 ((( 222 222 ((( 223 -User need to configure 95S31Bvia serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31Bsupport AT Commands, user can use a USB to TTL adapter to connect to95S31Band use AT Commands to configure it, as below.176 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. 224 224 ))) 225 225 ))) 226 226 227 -[[image: 1657351312545-300.png]]180 +[[image:image-20220709092052-2.png]] 228 228 229 229 **Connection:** 230 230 ... ... @@ -244,110 +244,90 @@ 244 244 * Flow Control: (% style="color:green" %)**None** 245 245 246 246 ((( 247 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.200 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 248 248 ))) 249 249 250 250 [[image:1657329814315-101.png]] 251 251 252 252 ((( 253 -(% style="color:red" %)Note: the valid AT Commands can be found at: 95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]206 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 254 254 ))) 255 255 256 256 257 257 258 -=== 2.2. 5Use CoAP protocol to uplink data ===211 +=== 2.2.4 Use CoAP protocol to uplink data === 259 259 260 260 (% 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/]] 261 261 262 262 263 -((( 264 264 **Use below commands:** 265 -))) 266 266 267 -* ((( 268 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 269 -))) 270 -* ((( 271 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 272 -))) 273 -* ((( 274 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 275 -))) 218 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 219 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 220 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 276 276 277 -((( 278 - 279 - 280 280 For parameter description, please refer to AT command set 281 -))) 282 282 283 -[[image:1657352 146020-183.png]]224 +[[image:1657330452568-615.png]] 284 284 285 285 286 -((( 287 287 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. 288 -))) 289 289 290 -[[image:16573 52185396-303.png]]229 +[[image:1657330472797-498.png]] 291 291 292 292 293 293 294 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===233 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 295 295 296 296 297 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 236 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 298 298 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 299 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 238 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 300 300 301 -[[image:16573 52391268-297.png]]240 +[[image:1657330501006-241.png]] 302 302 303 303 304 -[[image:16573 52403317-397.png]]243 +[[image:1657330533775-472.png]] 305 305 306 306 307 307 308 -=== 2.2. 7Use MQTT protocol to uplink data ===247 +=== 2.2.6 Use MQTT protocol to uplink data === 309 309 310 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 311 311 312 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 313 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 314 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 315 -* (% style="color:blue" %)**AT+UNAME=UNAME 316 -* (% style="color:blue" %)**AT+PWD=PWD 317 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527318 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)250 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 251 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 252 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 253 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 254 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 255 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 256 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 319 319 320 -[[image:1657 352634421-276.png]]258 +[[image:1657249978444-674.png]] 321 321 322 322 323 -[[image:16573 52645687-385.png]]261 +[[image:1657330723006-866.png]] 324 324 325 -((( 326 -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. 327 -))) 328 328 329 - 330 330 ((( 331 -MQTT protocol has a much high -power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.265 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 332 332 ))) 333 333 334 334 335 335 336 -=== 2.2. 8Use TCP protocol to uplink data ===270 +=== 2.2.7 Use TCP protocol to uplink data === 337 337 338 -This feature is supported since firmware version v110 339 339 340 340 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 341 341 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 342 342 343 -[[image: 1657352898400-901.png]]276 +[[image:image-20220709093918-1.png]] 344 344 345 345 346 -[[image: 1657352914475-252.png]]279 +[[image:image-20220709093918-2.png]] 347 347 348 348 349 349 350 -=== 2.2. 9Change Update Interval ===283 +=== 2.2.8 Change Update Interval === 351 351 352 352 User can use below command to change the (% style="color:green" %)**uplink interval**. 353 353 ... ... @@ -354,103 +354,69 @@ 354 354 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 355 355 356 356 ((( 357 - 290 +(% style="color:red" %)**NOTE:** 358 358 ))) 359 359 293 +((( 294 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 295 +))) 360 360 361 361 298 + 362 362 == 2.3 Uplink Payload == 363 363 301 +In this mode, uplink payload includes in total 14 bytes 364 364 365 -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. 366 366 304 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 305 +|=(% style="width: 80px;" %)((( 306 +**Size(bytes)** 307 +)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 308 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 367 367 368 -For example: 310 +((( 311 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 312 +))) 369 369 370 - (% 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. 371 371 315 +[[image:1657331036973-987.png]] 372 372 373 -The uplink payloads are composed in ASCII String. For example: 374 - 375 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 376 - 377 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 378 - 379 - 380 -(% style="color:red" %)**NOTE:** 381 - 382 -(% style="color:red" %) 383 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 384 -1. By default, the device will send an uplink message every 1 hour. 385 - 386 - 387 -=== 2.3.1 Payload Analyze === 388 - 389 -N95S31B uplink payload includes in total 21 bytes 390 - 391 - 392 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 393 -|=(% style="width: 60px;" %)((( 394 -**Size(bytes)** 395 -)))|=(% 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** 396 -|(% 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" %)((( 397 397 ((( 398 - Reserve/Sameas NBSN95 CFGMOD=1318 +The payload is ASCII string, representative same HEX: 399 399 ))) 400 400 401 401 ((( 402 - No functionhere.322 +0x72403155615900640c6c19029200 where: 403 403 ))) 404 -)))|(% style="width:77px" %)((( 405 -((( 406 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 407 -))) 408 408 409 -((( 410 - BySHT31325 +* ((( 326 +Device ID: 0x724031556159 = 724031556159 411 411 ))) 412 -)))|(% style="width:80px" %)((( 413 -((( 414 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 328 +* ((( 329 +Version: 0x0064=100=1.0.0 415 415 ))) 416 416 417 -((( 418 -B y SHT31332 +* ((( 333 +BAT: 0x0c6c = 3180 mV = 3.180V 419 419 ))) 335 +* ((( 336 +Signal: 0x19 = 25 420 420 ))) 421 - 422 -((( 423 -((( 424 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 338 +* ((( 339 +Distance: 0x0292= 658 mm 425 425 ))) 426 -))) 341 +* ((( 342 +Interrupt: 0x00 = 0 427 427 428 428 429 -[[image:1657354294009-643.png]] 430 430 431 - 432 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 433 - 434 -* Device ID: 0x724031607457 = 724031607457 435 -* Version: 0x006e=110=1.1.0 436 - 437 -* BAT: 0x0ccd = 3277 mV = 3.277V 438 -* Signal: 0x1b = 27 439 -* Model: 0x01 = 1 440 -* 0x00dc000ccc= reserve, ignore in N95S31B 441 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 442 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 443 - 444 -((( 445 445 446 446 ))) 447 447 448 -((( 449 - 450 -))) 349 +== 2.4 Payload Explanation and Sensor Interface == 451 451 452 452 453 -=== 2. 3.2352 +=== 2.4.1 Device ID === 454 454 455 455 ((( 456 456 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -474,25 +474,24 @@ 474 474 475 475 476 476 477 -=== 2. 3.3Version Info ===376 +=== 2.4.2 Version Info === 478 478 378 +((( 379 +Specify the software version: 0x64=100, means firmware version 1.00. 380 +))) 479 479 480 -These bytes include the hardware and software version. 382 +((( 383 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 384 +))) 481 481 482 -Higher byte: Specify hardware version: always 0x00 for N95S31B 483 483 484 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 485 485 388 +=== 2.4.3 Battery Info === 486 486 487 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 488 - 489 489 ((( 490 - 391 +Check the battery voltage for LSE01. 491 491 ))) 492 492 493 - 494 -=== 2.3.4 Battery Info === 495 - 496 496 ((( 497 497 Ex1: 0x0B45 = 2885mV 498 498 ))) ... ... @@ -503,7 +503,7 @@ 503 503 504 504 505 505 506 -=== 2. 3.5Signal Strength ===404 +=== 2.4.4 Signal Strength === 507 507 508 508 ((( 509 509 NB-IoT Network signal Strength. ... ... @@ -535,26 +535,83 @@ 535 535 536 536 537 537 538 -=== 2. 3.6Temperature& Humidity===436 +=== 2.4.5 Distance === 539 539 540 - The devicewill beabletogetthe SHT31 temperatureand humiditydatanow and upload to IoT Server.438 +Get the distance. Flat object range 280mm - 7500mm. 541 541 542 - [[image:image-20220709161741-3.png]]440 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 543 543 442 +((( 443 +((( 444 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 445 +))) 446 +))) 544 544 545 -Convert the read byte to decimal and divide it by ten. 448 +((( 449 + 450 +))) 546 546 452 +((( 453 + 454 +))) 547 547 548 - **Example:**456 +=== 2.4.6 Digital Interrupt === 549 549 550 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 458 +((( 459 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 460 +))) 551 551 552 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 462 +((( 463 +The command is: 464 +))) 553 553 466 +((( 467 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 468 +))) 554 554 555 555 556 -== 2.4 Downlink Payload == 471 +((( 472 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 473 +))) 557 557 475 + 476 +((( 477 +Example: 478 +))) 479 + 480 +((( 481 +0x(00): Normal uplink packet. 482 +))) 483 + 484 +((( 485 +0x(01): Interrupt Uplink Packet. 486 +))) 487 + 488 + 489 + 490 +=== 2.4.7 +5V Output === 491 + 492 +((( 493 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 494 +))) 495 + 496 + 497 +((( 498 +The 5V output time can be controlled by AT Command. 499 +))) 500 + 501 +((( 502 +(% style="color:blue" %)**AT+5VT=1000** 503 +))) 504 + 505 +((( 506 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 507 +))) 508 + 509 + 510 + 511 +== 2.5 Downlink Payload == 512 + 558 558 By default, NDDS75 prints the downlink payload to console port. 559 559 560 560 [[image:image-20220709100028-1.png]] ... ... @@ -605,16 +605,47 @@ 605 605 606 606 607 607 608 -== 2. 5BatteryAnalysis==563 +== 2.6 LED Indicator == 609 609 610 -=== 2.5.1 Battery Type === 611 611 566 +The NDDS75 has an internal LED which is to show the status of different state. 612 612 568 + 569 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 570 +* Then the LED will be on for 1 second means device is boot normally. 571 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 572 +* For each uplink probe, LED will be on for 500ms. 573 + 613 613 ((( 614 - TheN95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.575 + 615 615 ))) 616 616 578 + 579 + 580 +== 2.7 Firmware Change Log == 581 + 582 + 583 +Download URL & Firmware Change log 584 + 617 617 ((( 586 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 587 +))) 588 + 589 + 590 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 591 + 592 + 593 + 594 +== 2.8 Battery Analysis == 595 + 596 +=== 2.8.1 Battery Type === 597 + 598 + 599 +((( 600 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 601 +))) 602 + 603 +((( 618 618 The battery is designed to last for several years depends on the actually use environment and update interval. 619 619 ))) 620 620 ... ... @@ -632,35 +632,56 @@ 632 632 633 633 634 634 635 -=== 2. 5.2 Power consumption Analyze ===621 +=== 2.8.2 Power consumption Analyze === 636 636 637 637 ((( 638 - The file**DRAGINO_N95S31B-Power-Analyzer.pdf**from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.624 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 639 639 ))) 640 640 627 + 641 641 ((( 642 - 629 +Instruction to use as below: 643 643 ))) 644 644 632 +((( 633 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 634 +))) 645 645 646 -=== 2.5.3 Battery Note === 647 647 648 648 ((( 649 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.638 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 650 650 ))) 651 651 641 +* ((( 642 +Product Model 643 +))) 644 +* ((( 645 +Uplink Interval 646 +))) 647 +* ((( 648 +Working Mode 649 +))) 652 652 651 +((( 652 +And the Life expectation in difference case will be shown on the right. 653 +))) 653 653 654 - ===2.5.4 Replacethe battery ===655 +[[image:image-20220708141352-7.jpeg]] 655 655 656 656 658 + 659 +=== 2.8.3 Battery Note === 660 + 657 657 ((( 658 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.662 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased. 659 659 ))) 660 660 661 661 666 + 667 +=== 2.8.4 Replace the battery === 668 + 662 662 ((( 663 -The default battery pack of N 95S31Bincludes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).670 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 664 664 ))) 665 665 666 666 ... ... @@ -683,7 +683,7 @@ 683 683 684 684 == 4.1 Access AT Commands == 685 685 686 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]693 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 687 687 688 688 689 689 AT+<CMD>? : Help on <CMD> ... ... @@ -771,9 +771,7 @@ 771 771 ))) 772 772 773 773 ((( 774 - 775 - 776 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 781 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 777 777 ))) 778 778 779 779 ... ... @@ -805,7 +805,7 @@ 805 805 = 7. Order Info = 806 806 807 807 808 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**813 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 809 809 810 810 811 811 (% class="wikigeneratedid" %) ... ... @@ -820,7 +820,7 @@ 820 820 821 821 (% style="color:#037691" %)**Package Includes**: 822 822 823 -* N 95S31BNB-IoTTemperatureandHumiditySensor828 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 824 824 * External antenna x 1 825 825 ))) 826 826 ... ... @@ -829,10 +829,11 @@ 829 829 830 830 (% style="color:#037691" %)**Dimension and weight**: 831 831 837 + 832 832 * Device Size: 13.0 x 5 x 4.5 cm 833 833 * Device Weight: 150g 834 -* Package Size / pcs : 1 4.0x8x 5 cm835 -* Weight / pcs : 180g840 +* Package Size / pcs : 15 x 12x 5.5 cm 841 +* Weight / pcs : 220g 836 836 ))) 837 837 838 838 (((
- 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-20220709110451-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -611.5 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