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, 22 removed)
- 1657332990863-496.png
- 1657333200519-600.png
- 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-20220709101450-2.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,74 +1,61 @@ 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 -{{toc/}} 13 13 14 14 15 15 16 16 17 17 15 + 18 18 = 1. Introduction = 19 19 20 -== 1.1 What is N 95S31BNB-IoTSensorNode==18 +== 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*. 24 +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. 25 +\\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. 26 +\\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. 27 +\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 28 +\\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) 29 +\\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 -))) 35 +[[image:1654503236291-817.png]] 48 48 49 - 50 -))) 51 51 52 -[[image:16573 48284168-431.png]]38 +[[image:1657327959271-447.png]] 53 53 54 54 55 55 56 56 == 1.2 Features == 57 57 44 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 -* Monitor Temperature & Humidity via SHT31 46 +* Ultra low power consumption 47 +* Distance Detection by Ultrasonic technology 48 +* Flat object range 280mm - 7500mm 49 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 50 +* Cable Length: 25cm 60 60 * AT Commands to change parameters 61 61 * Uplink on periodically 62 62 * Downlink to change configure 63 63 * IP66 Waterproof Enclosure 64 -* Ultra-Low Power consumption 65 -* AT Commands to change parameters 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 69 70 - 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,7 +87,6 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -96,9 +96,13 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 84 +(% style="color:#037691" %)**Power Consumption** 99 99 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 100 100 101 101 90 + 102 102 == 1.4 Applications == 103 103 104 104 * Smart Buildings & Home Automation ... ... @@ -112,52 +112,25 @@ 112 112 113 113 114 114 104 + 115 115 == 1.5 Pin Definitions == 116 116 117 -N95S31B use the mother board from NBSN95 which as below. 118 118 119 -[[image: image-20220709144723-1.png]]108 +[[image:1657328609906-564.png]] 120 120 121 121 122 -=== 1.5.1 Jumper JP2 === 123 123 124 - PoweronDevice when putthisjumper.112 += 2. Use NDDS75 to communicate with IoT Server = 125 125 126 - 127 - 128 -=== 1.5.2 BOOT MODE / SW1 === 129 - 130 -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. 131 - 132 -2) Flash: work mode, device starts to work and send out console output for further debug 133 - 134 - 135 - 136 -=== 1.5.3 Reset Button === 137 - 138 -Press to reboot the device. 139 - 140 - 141 - 142 -=== 1.5.4 LED === 143 - 144 -It will flash: 145 - 146 -1. When boot the device in flash mode 147 -1. Send an uplink packet 148 - 149 -= 2. Use N95S31B to communicate with IoT Server = 150 - 151 151 == 2.1 How it works == 152 152 153 - 154 154 ((( 155 -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.117 +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. 156 156 ))) 157 157 158 158 159 159 ((( 160 -The diagram below shows the working flow in default firmware of N 95S31B:122 +The diagram below shows the working flow in default firmware of NDDS75: 161 161 ))) 162 162 163 163 ((( ... ... @@ -164,7 +164,7 @@ 164 164 165 165 ))) 166 166 167 -[[image:16573 50248151-650.png]]129 +[[image:1657328659945-416.png]] 168 168 169 169 ((( 170 170 ... ... @@ -171,45 +171,30 @@ 171 171 ))) 172 172 173 173 174 -== 2.2 Configure the N 95S31B==136 +== 2.2 Configure the NDDS75 == 175 175 176 176 177 -=== 2.2.1 Power On N95S31B === 178 - 179 - 180 -[[image:image-20220709150546-2.png]] 181 - 182 - 183 183 === 2.2.1 Test Requirement === 184 184 141 +((( 142 +To use NDDS75 in your city, make sure meet below requirements: 143 +))) 185 185 186 -To use N95S31B in your city, make sure meet below requirements: 187 - 188 188 * Your local operator has already distributed a NB-IoT Network there. 189 -* The local NB-IoT network used the band that N 95S31Bsupports.146 +* The local NB-IoT network used the band that NSE01 supports. 190 190 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 191 191 192 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 193 - 194 -N95S31B supports different communication protocol such as : 195 - 196 196 ((( 197 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 198 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 199 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 200 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 201 - 202 -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. 203 - 204 - 150 +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 205 205 ))) 206 206 207 -[[image:1657350625843-586.png]] 208 208 154 +[[image:1657328756309-230.png]] 209 209 210 210 211 -=== 2.2.3 Insert SIM card === 212 212 158 +=== 2.2.2 Insert SIM card === 159 + 213 213 ((( 214 214 Insert the NB-IoT Card get from your provider. 215 215 ))) ... ... @@ -219,19 +219,19 @@ 219 219 ))) 220 220 221 221 222 -[[image:16573 51240556-536.png]]169 +[[image:1657328884227-504.png]] 223 223 224 224 225 225 226 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 227 227 228 228 ((( 229 229 ((( 230 -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.177 +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. 231 231 ))) 232 232 ))) 233 233 234 -[[image: 1657351312545-300.png]]181 +[[image:image-20220709092052-2.png]] 235 235 236 236 **Connection:** 237 237 ... ... @@ -251,110 +251,90 @@ 251 251 * Flow Control: (% style="color:green" %)**None** 252 252 253 253 ((( 254 -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.201 +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. 255 255 ))) 256 256 257 257 [[image:1657329814315-101.png]] 258 258 259 259 ((( 260 -(% 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/]]207 +(% 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/]] 261 261 ))) 262 262 263 263 264 264 265 -=== 2.2. 5Use CoAP protocol to uplink data ===212 +=== 2.2.4 Use CoAP protocol to uplink data === 266 266 267 267 (% 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/]] 268 268 269 269 270 -((( 271 271 **Use below commands:** 272 -))) 273 273 274 -* ((( 275 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 276 -))) 277 -* ((( 278 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 279 -))) 280 -* ((( 281 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 282 -))) 219 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 220 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 221 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 283 283 284 -((( 285 - 286 - 287 287 For parameter description, please refer to AT command set 288 -))) 289 289 290 -[[image:1657352 146020-183.png]]225 +[[image:1657330452568-615.png]] 291 291 292 292 293 -((( 294 294 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. 295 -))) 296 296 297 -[[image:16573 52185396-303.png]]230 +[[image:1657330472797-498.png]] 298 298 299 299 300 300 301 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 302 302 303 303 304 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 237 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 305 305 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 306 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 239 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 307 307 308 -[[image:16573 52391268-297.png]]241 +[[image:1657330501006-241.png]] 309 309 310 310 311 -[[image:16573 52403317-397.png]]244 +[[image:1657330533775-472.png]] 312 312 313 313 314 314 315 -=== 2.2. 7Use MQTT protocol to uplink data ===248 +=== 2.2.6 Use MQTT protocol to uplink data === 316 316 317 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 318 318 319 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 320 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 321 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 322 -* (% style="color:blue" %)**AT+UNAME=UNAME 323 -* (% style="color:blue" %)**AT+PWD=PWD 324 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527325 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)251 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 252 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 253 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 254 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 255 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 256 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 257 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 326 326 327 -[[image:1657 352634421-276.png]]259 +[[image:1657249978444-674.png]] 328 328 329 329 330 -[[image:16573 52645687-385.png]]262 +[[image:1657330723006-866.png]] 331 331 332 -((( 333 -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. 334 -))) 335 335 336 - 337 337 ((( 338 -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.266 +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. 339 339 ))) 340 340 341 341 342 342 343 -=== 2.2. 8Use TCP protocol to uplink data ===271 +=== 2.2.7 Use TCP protocol to uplink data === 344 344 345 -This feature is supported since firmware version v110 346 346 347 347 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 348 348 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 349 349 350 -[[image: 1657352898400-901.png]]277 +[[image:image-20220709093918-1.png]] 351 351 352 352 353 -[[image: 1657352914475-252.png]]280 +[[image:image-20220709093918-2.png]] 354 354 355 355 356 356 357 -=== 2.2. 9Change Update Interval ===284 +=== 2.2.8 Change Update Interval === 358 358 359 359 User can use below command to change the (% style="color:green" %)**uplink interval**. 360 360 ... ... @@ -361,207 +361,226 @@ 361 361 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 362 362 363 363 ((( 364 - 291 +(% style="color:red" %)**NOTE:** 365 365 ))) 366 366 294 +((( 295 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 296 +))) 367 367 368 368 299 + 369 369 == 2.3 Uplink Payload == 370 370 302 +In this mode, uplink payload includes in total 14 bytes 371 371 372 -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. 373 373 305 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 306 +|=(% style="width: 60px;" %)((( 307 +**Size(bytes)** 308 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1** 309 +|(% 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:108px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 374 374 375 -For example: 311 +((( 312 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 313 +))) 376 376 377 - (% 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. 378 378 316 +[[image:1657331036973-987.png]] 379 379 380 -The uplink payloads are composed in ASCII String. For example: 318 +((( 319 +The payload is ASCII string, representative same HEX: 320 +))) 381 381 382 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 322 +((( 323 +0x72403155615900640c6c19029200 where: 324 +))) 383 383 384 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 326 +* ((( 327 +Device ID: 0x724031556159 = 724031556159 328 +))) 329 +* ((( 330 +Version: 0x0064=100=1.0.0 331 +))) 385 385 333 +* ((( 334 +BAT: 0x0c6c = 3180 mV = 3.180V 335 +))) 336 +* ((( 337 +Signal: 0x19 = 25 338 +))) 339 +* ((( 340 +Distance: 0x0292= 658 mm 341 +))) 342 +* ((( 343 +Interrupt: 0x00 = 0 344 +))) 386 386 387 -(% style="color:red" %)**NOTE:** 388 388 389 -(% style="color:red" %) 390 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 391 -1. By default, the device will send an uplink message every 1 hour. 347 +== 2.4 Payload Explanation and Sensor Interface == 392 392 393 393 394 -=== 2. 3.1Payload Analyze ===350 +=== 2.4.1 Device ID === 395 395 396 -N95S31B uplink payload includes in total 21 bytes 397 - 398 - 399 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 400 -|=(% style="width: 60px;" %)((( 401 -**Size(bytes)** 402 -)))|=(% 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** 403 -|(% 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" %)((( 404 404 ((( 405 - Reserve/Same asNBSN95CFGMOD=1353 +By default, the Device ID equal to the last 6 bytes of IMEI. 406 406 ))) 407 407 408 408 ((( 409 - Nofunctionhere.357 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 410 410 ))) 411 - )))|(% style="width:77px" %)(((359 + 412 412 ((( 413 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]361 +**Example:** 414 414 ))) 415 415 416 416 ((( 417 - By SHT31365 +AT+DEUI=A84041F15612 418 418 ))) 419 - )))|(% style="width:80px" %)(((367 + 420 420 ((( 421 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]369 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 422 422 ))) 423 423 372 + 373 + 374 +=== 2.4.2 Version Info === 375 + 424 424 ((( 425 - BySHT31377 +Specify the software version: 0x64=100, means firmware version 1.00. 426 426 ))) 427 -))) 428 428 429 429 ((( 430 -((( 431 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 381 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 432 432 ))) 433 -))) 434 434 435 435 436 -[[image:1657354294009-643.png]] 437 437 386 +=== 2.4.3 Battery Info === 438 438 439 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 388 +((( 389 +Check the battery voltage for LSE01. 390 +))) 440 440 441 -* Device ID: 0x724031607457 = 724031607457 442 -* Version: 0x006e=110=1.1.0 443 - 444 -* BAT: 0x0ccd = 3277 mV = 3.277V 445 -* Signal: 0x1b = 27 446 -* Model: 0x01 = 1 447 -* 0x00dc000ccc= reserve, ignore in N95S31B 448 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 449 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 450 - 451 451 ((( 452 - 393 +Ex1: 0x0B45 = 2885mV 453 453 ))) 454 454 455 455 ((( 456 - 397 +Ex2: 0x0B49 = 2889mV 457 457 ))) 458 458 459 459 460 -=== 2.3.2 Device ID === 461 461 402 +=== 2.4.4 Signal Strength === 403 + 462 462 ((( 463 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.405 +NB-IoT Network signal Strength. 464 464 ))) 465 465 466 466 ((( 467 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID409 +**Ex1: 0x1d = 29** 468 468 ))) 469 469 470 470 ((( 471 - **Example:**413 +(% style="color:blue" %)**0**(%%) -113dBm or less 472 472 ))) 473 473 474 474 ((( 475 - AT+DEUI=A84041F15612417 +(% style="color:blue" %)**1**(%%) -111dBm 476 476 ))) 477 477 478 478 ((( 479 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.421 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 480 480 ))) 481 481 424 +((( 425 +(% style="color:blue" %)**31** (%%) -51dBm or greater 426 +))) 482 482 428 +((( 429 +(% style="color:blue" %)**99** (%%) Not known or not detectable 430 +))) 483 483 484 -=== 2.3.3 Version Info === 485 485 486 486 487 - Thesebytesincludethe hardware and softwareversion.434 +=== 2.4.5 Soil Moisture === 488 488 489 - Higherbyte:Specifyhardwareversion: always0x00forN95S31B436 +Get the distance. Flat object range 280mm - 7500mm. 490 490 491 - Lowerbyte: Specifythesoftwareversion:0x6E=110,meansfirmwareversion110438 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 492 492 493 - 494 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 495 - 496 496 ((( 497 - 441 +((( 442 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 498 498 ))) 444 +))) 499 499 500 - 501 -=== 2.3.4 Battery Info === 502 - 503 503 ((( 504 - Ex1:0x0B45 = 2885mV447 + 505 505 ))) 506 506 507 507 ((( 508 - Ex2:0x0B49 = 2889mV451 + 509 509 ))) 510 510 454 +=== 2.4.6 Digital Interrupt === 511 511 512 - 513 -=== 2.3.5 Signal Strength === 514 - 515 515 ((( 516 - NB-IoTNetworksignalStrength.457 +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. 517 517 ))) 518 518 519 519 ((( 520 - **Ex1:0x1d= 29**461 +The command is: 521 521 ))) 522 522 523 523 ((( 524 -(% style="color:blue" %)** 0**(%%)-113dBmor less465 +(% 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]])**.** 525 525 ))) 526 526 468 + 527 527 ((( 528 - (%style="color:blue"%)**1**(%%)-111dBm470 +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. 529 529 ))) 530 530 473 + 531 531 ((( 532 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm475 +Example: 533 533 ))) 534 534 535 535 ((( 536 -( %style="color:blue"%)**31** (%%) -51dBm or greater479 +0x(00): Normal uplink packet. 537 537 ))) 538 538 539 539 ((( 540 -( %style="color:blue" %)**99** (%%) Notknownor not detectable483 +0x(01): Interrupt Uplink Packet. 541 541 ))) 542 542 543 543 544 544 545 -=== 2. 3.6Temperature& Humidity===488 +=== 2.4.7 +5V Output === 546 546 547 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 490 +((( 491 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 492 +))) 548 548 549 -[[image:image-20220709161741-3.png]] 550 550 495 +((( 496 +The 5V output time can be controlled by AT Command. 497 +))) 551 551 552 -Convert the read byte to decimal and divide it by ten. 499 +((( 500 +(% style="color:blue" %)**AT+5VT=1000** 501 +))) 553 553 503 +((( 504 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 505 +))) 554 554 555 -**Example:** 556 556 557 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 558 558 559 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%509 +== 2.5 Downlink Payload == 560 560 561 - 562 - 563 -== 2.4 Downlink Payload == 564 - 565 565 By default, NDDS75 prints the downlink payload to console port. 566 566 567 567 [[image:image-20220709100028-1.png]] ... ... @@ -612,19 +612,52 @@ 612 612 613 613 614 614 615 -== 2. 5BatteryAnalysis==561 +== 2.6 LED Indicator == 616 616 617 -=== 2.5.1 Battery Type === 618 618 564 +The NDDS75 has an internal LED which is to show the status of different state. 619 619 566 + 567 +* 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) 568 +* Then the LED will be on for 1 second means device is boot normally. 569 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 570 +* For each uplink probe, LED will be on for 500ms. 571 + 620 620 ((( 621 - 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.573 + 622 622 ))) 623 623 576 + 577 + 578 +== 2.7 Firmware Change Log == 579 + 580 + 581 +Download URL & Firmware Change log 582 + 624 624 ((( 584 +[[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/]] 585 +))) 586 + 587 + 588 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 589 + 590 + 591 + 592 +== 2.9 Battery Analysis == 593 + 594 +=== 2.9.1 Battery Type === 595 + 596 + 597 +((( 598 +The NSE01 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. 599 +))) 600 + 601 + 602 +((( 625 625 The battery is designed to last for several years depends on the actually use environment and update interval. 626 626 ))) 627 627 606 + 628 628 ((( 629 629 The battery related documents as below: 630 630 ))) ... ... @@ -634,40 +634,61 @@ 634 634 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 635 635 636 636 ((( 637 -[[image:image-2022070 9101450-2.png]]616 +[[image:image-20220708140453-6.png]] 638 638 ))) 639 639 640 640 641 641 642 -=== 2. 5.2 Power consumption Analyze ===621 +=== 2.9.2 Power consumption Analyze === 643 643 644 644 ((( 645 - 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. 646 646 ))) 647 647 627 + 648 648 ((( 649 - 629 +Instruction to use as below: 650 650 ))) 651 651 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 +))) 652 652 653 -=== 2.5.3 Battery Note === 654 654 655 655 ((( 656 - 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 657 657 ))) 658 658 641 +* ((( 642 +Product Model 643 +))) 644 +* ((( 645 +Uplink Interval 646 +))) 647 +* ((( 648 +Working Mode 649 +))) 659 659 651 +((( 652 +And the Life expectation in difference case will be shown on the right. 653 +))) 660 660 661 - ===2.5.4 Replacethe battery ===655 +[[image:image-20220708141352-7.jpeg]] 662 662 663 663 658 + 659 +=== 2.9.3 Battery Note === 660 + 664 664 ((( 665 - 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. 666 666 ))) 667 667 668 668 666 + 667 +=== 2.9.4 Replace the battery === 668 + 669 669 ((( 670 -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 NSE01 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). 671 671 ))) 672 672 673 673 ... ... @@ -682,7 +682,7 @@ 682 682 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 683 683 ))) 684 684 685 -[[image:1657 333200519-600.png]]685 +[[image:1657261278785-153.png]] 686 686 687 687 688 688 ... ... @@ -690,7 +690,7 @@ 690 690 691 691 == 4.1 Access AT Commands == 692 692 693 -See NBSN95 AT Command inthis link for detail:s:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]693 +See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 694 694 695 695 696 696 AT+<CMD>? : Help on <CMD> ... ... @@ -778,13 +778,18 @@ 778 778 ))) 779 779 780 780 ((( 781 - 782 - 783 -(% 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, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 784 784 ))) 785 785 786 786 787 787 786 +== 5.2 Can I calibrate NSE01 to different soil types? == 787 + 788 +((( 789 +NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]]. 790 +))) 791 + 792 + 788 788 = 6. Trouble Shooting = 789 789 790 790 == 6.1 Connection problem when uploading firmware == ... ... @@ -812,7 +812,7 @@ 812 812 = 7. Order Info = 813 813 814 814 815 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**820 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 816 816 817 817 818 818 (% class="wikigeneratedid" %) ... ... @@ -827,7 +827,7 @@ 827 827 828 828 (% style="color:#037691" %)**Package Includes**: 829 829 830 -* N 95S31BNB-IoTTemperatureandHumiditySensor835 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 831 831 * External antenna x 1 832 832 ))) 833 833 ... ... @@ -836,10 +836,8 @@ 836 836 837 837 (% style="color:#037691" %)**Dimension and weight**: 838 838 839 -* Device Size: 13.0 x 5 x 4.5 cm 840 -* Device Weight: 150g 841 -* Package Size / pcs : 14.0 x 8x 5 cm 842 -* Weight / pcs : 180g 844 +* Size: 195 x 125 x 55 mm 845 +* Weight: 420g 843 843 ))) 844 844 845 845 (((
- 1657332990863-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.2 KB - Content
- 1657333200519-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 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-20220709101450-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.5 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