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, 28 removed)
- 1657331036973-987.png
- 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
- 1657520100595-569.png
- image-20220709100028-1.png
- image-20220709101450-2.png
- image-20220709110451-3.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
- image-20220908154949-1.png
- image-20220908163102-2.png
- image-20221009001045-1.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,56 +1,41 @@ 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 18 +== 1.1 What is NDDS75 Distance Detection Sensor == 20 20 21 -== 1.1 What is N95S31B NB-IoT Sensor Node == 22 - 23 23 ((( 24 24 25 25 26 26 ((( 27 -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. 28 28 ))) 29 29 30 -((( 31 -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. 32 -))) 33 - 34 -((( 35 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 -))) 37 - 38 -((( 39 -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). 40 -))) 41 - 42 -((( 43 43 44 44 ))) 45 45 46 -((( 47 -~* make sure you have NB-IoT coverage locally. 48 -))) 35 +[[image:1654503236291-817.png]] 49 49 50 - 51 -))) 52 52 53 -[[image:16573 48284168-431.png]]38 +[[image:1657327959271-447.png]] 54 54 55 55 56 56 ... ... @@ -58,13 +58,15 @@ 58 58 59 59 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 -* 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 62 62 * AT Commands to change parameters 63 63 * Uplink on periodically 64 64 * Downlink to change configure 65 65 * IP66 Waterproof Enclosure 66 -* Ultra-Low Power consumption 67 -* AT Commands to change parameters 68 68 * Micro SIM card slot for NB-IoT SIM 69 69 * 8500mAh Battery for long term use 70 70 ... ... @@ -94,10 +94,15 @@ 94 94 * Max continuously current: 130mA 95 95 * Max boost current: 2A, 1 second 96 96 84 +(% style="color:#037691" %)**Power Consumption** 97 97 98 -== 1.4 Applications == 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: 350mA@3.3v 99 99 100 100 90 + 91 +== 1.4 Applications == 92 + 101 101 * Smart Buildings & Home Automation 102 102 * Logistics and Supply Chain Management 103 103 * Smart Metering ... ... @@ -110,67 +110,24 @@ 110 110 111 111 112 112 113 -== 1.5 Pin Definitions & Switch==105 +== 1.5 Pin Definitions == 114 114 115 115 116 - N95S31B use themother board from NBSN95which as below.108 +[[image:1657328609906-564.png]] 117 117 118 118 119 -[[image:image-20220709144723-1.png]] 120 120 112 += 2. Use NDDS75 to communicate with IoT Server = 121 121 122 - 123 -=== 1.5.1 Jumper JP2 === 124 - 125 - 126 -Power on Device when put this jumper. 127 - 128 - 129 - 130 -=== 1.5.2 BOOT MODE / SW1 === 131 - 132 - 133 -((( 134 -**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. 135 -))) 136 - 137 -((( 138 -**2) Flash:** work mode, device starts to work and send out console output for further debug 139 -))) 140 - 141 - 142 - 143 -=== 1.5.3 Reset Button === 144 - 145 - 146 -Press to reboot the device. 147 - 148 - 149 - 150 -=== 1.5.4 LED === 151 - 152 - 153 -It will flash: 154 - 155 -1. When boot the device in flash mode 156 - 157 -2. Send an uplink packet 158 - 159 - 160 - 161 -= 2. Use N95S31B to communicate with IoT Server = 162 - 163 - 164 164 == 2.1 How it works == 165 165 166 - 167 167 ((( 168 -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. 169 169 ))) 170 170 171 171 172 172 ((( 173 -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: 174 174 ))) 175 175 176 176 ((( ... ... @@ -177,7 +177,7 @@ 177 177 178 178 ))) 179 179 180 -[[image:1657 520100595-569.png]]129 +[[image:1657328659945-416.png]] 181 181 182 182 ((( 183 183 ... ... @@ -184,69 +184,30 @@ 184 184 ))) 185 185 186 186 187 -== 2.2 Configure the N 95S31B==136 +== 2.2 Configure the NDDS75 == 188 188 189 189 190 -=== 2.2.1 Power On N95S31B === 191 - 192 - 193 -[[image:image-20220709150546-2.png]] 194 - 195 - 196 - 197 197 === 2.2.1 Test Requirement === 198 198 199 - 200 200 ((( 201 -To use N 95S31Bin your city, make sure meet below requirements:142 +To use NDDS75 in your city, make sure meet below requirements: 202 202 ))) 203 203 204 -* ((( 205 -Your local operator has already distributed a NB-IoT Network there. 206 -))) 207 -* ((( 208 -The local NB-IoT network used the band that N95S31B supports. 209 -))) 210 -* ((( 211 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 212 -))) 145 +* Your local operator has already distributed a NB-IoT Network there. 146 +* The local NB-IoT network used the band that NSE01 supports. 147 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 213 213 214 214 ((( 215 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 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 216 216 ))) 217 217 218 -((( 219 -N95S31B supports different communication protocol such as : 220 -))) 221 221 222 -((( 223 -* ((( 224 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 225 -))) 226 -* ((( 227 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 228 -))) 229 -* ((( 230 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 231 -))) 232 -* ((( 233 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 234 -))) 154 +[[image:1657328756309-230.png]] 235 235 236 -((( 237 -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. 238 -))) 239 239 240 - 241 -))) 242 242 243 - [[image:1657350625843-586.png]]158 +=== 2.2.2 Insert SIM card === 244 244 245 - 246 - 247 -=== 2.2.3 Insert SIM card === 248 - 249 - 250 250 ((( 251 251 Insert the NB-IoT Card get from your provider. 252 252 ))) ... ... @@ -256,33 +256,29 @@ 256 256 ))) 257 257 258 258 259 -[[image:16573 51240556-536.png]]169 +[[image:1657328884227-504.png]] 260 260 261 261 262 262 263 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 264 264 265 - 266 266 ((( 267 267 ((( 268 -User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 269 - 270 - 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. 271 271 ))) 272 272 ))) 273 273 274 -[[image: 1657351312545-300.png]]181 +[[image:image-20220709092052-2.png]] 275 275 183 +**Connection:** 276 276 277 - **(% style="color:blue" %)Connection:**185 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 278 278 279 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**187 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 280 280 281 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**189 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 282 282 283 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 284 284 285 - 286 286 In the PC, use below serial tool settings: 287 287 288 288 * Baud: (% style="color:green" %)**9600** ... ... @@ -292,116 +292,95 @@ 292 292 * Flow Control: (% style="color:green" %)**None** 293 293 294 294 ((( 295 -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. 296 296 ))) 297 297 298 298 [[image:1657329814315-101.png]] 299 299 300 - 301 301 ((( 302 -(% style="color:red" %) **Note: the valid AT Commands can be found at:**(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**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/]] 303 303 ))) 304 304 305 305 306 306 307 -=== 2.2. 5Use CoAP protocol to uplink data ===212 +=== 2.2.4 Use CoAP protocol to uplink data === 308 308 214 +(% 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/]] 309 309 310 -(% 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/]]** 311 311 312 - 313 -((( 314 314 **Use below commands:** 315 -))) 316 316 317 -* ((( 318 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 319 -))) 320 -* ((( 321 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 322 -))) 323 -* ((( 324 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 325 -))) 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 326 326 327 -((( 328 - 329 - 330 330 For parameter description, please refer to AT command set 331 -))) 332 332 333 -[[image:1657352 146020-183.png]]225 +[[image:1657330452568-615.png]] 334 334 335 335 336 -((( 337 337 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. 338 -))) 339 339 340 -[[image:16573 52185396-303.png]]230 +[[image:1657330472797-498.png]] 341 341 342 342 343 343 344 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 345 345 346 346 347 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 237 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 348 348 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 349 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 239 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 350 350 351 -[[image:1657352391268-297.png]] 352 352 242 +[[image:1657330501006-241.png]] 353 353 354 -[[image:1657352403317-397.png]] 355 355 245 +[[image:1657330533775-472.png]] 356 356 357 357 358 -=== 2.2.7 Use MQTT protocol to uplink data === 359 359 249 +=== 2.2.6 Use MQTT protocol to uplink data === 360 360 361 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 362 362 363 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 364 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 365 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 366 -* (% style="color:blue" %)**AT+UNAME=UNAME 367 -* (% style="color:blue" %)**AT+PWD=PWD 368 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527369 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)252 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 253 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 254 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 255 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 256 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 257 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 258 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 370 370 371 -[[image:1657 352634421-276.png]]260 +[[image:1657249978444-674.png]] 372 372 373 373 374 -[[image:16573 52645687-385.png]]263 +[[image:1657330723006-866.png]] 375 375 376 376 377 377 ((( 378 -To savebatterylife,N95S31Bwillestablishasubscriptionbeforeeachuplinkandclose thesubscription3 secondsafteruplinksuccessful. Any downlink commandsfromserver will onlyarriveduringthesubscriptionperiod.267 +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. 379 379 ))) 380 380 381 381 382 -((( 383 -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. 384 -))) 385 385 272 +=== 2.2.7 Use TCP protocol to uplink data === 386 386 387 387 388 -=== 2.2.8 Use TCP protocol to uplink data === 275 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 276 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 389 389 390 390 391 - This features supported since firmwareversion v110279 +[[image:image-20220709093918-1.png]] 392 392 393 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 394 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 395 395 396 -[[image: 1657352898400-901.png]]282 +[[image:image-20220709093918-2.png]] 397 397 398 398 399 -[[image:1657352914475-252.png]] 400 400 401 401 402 402 403 -=== 2.2.9 Change Update Interval === 404 404 289 +=== 2.2.8 Change Update Interval === 405 405 406 406 User can use below command to change the (% style="color:green" %)**uplink interval**. 407 407 ... ... @@ -408,250 +408,190 @@ 408 408 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 409 409 410 410 ((( 411 - 296 +(% style="color:red" %)**NOTE:** 412 412 ))) 413 413 414 414 ((( 415 -(% style="color:red" %) **NOTE:Sincefirmware version is v1.2:**300 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 416 416 ))) 417 417 418 -((( 419 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 420 -))) 421 421 422 422 423 - 424 424 == 2.3 Uplink Payload == 425 425 307 +In this mode, uplink payload includes in total 18 bytes 426 426 309 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 310 +|=(% style="width: 60px;" %)((( 311 +**Size(bytes)** 312 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1** 313 +|(% 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" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 314 + 427 427 ((( 428 - N95S31B has differentworking modesforthe connections of different typesofsensors. This section describesthesemodes.Usercanuse theAT Command (% style="color:blue"%)**AT+MOD**(%%)toset NBSN95to different workingmodes.316 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 429 429 ))) 430 430 431 431 320 +[[image:image-20220708111918-4.png]] 321 + 322 + 323 +The payload is ASCII string, representative same HEX: 324 + 325 +0x72403155615900640c7817075e0a8c02f900 where: 326 + 327 +* Device ID: 0x 724031556159 = 724031556159 328 +* Version: 0x0064=100=1.0.0 329 + 330 +* BAT: 0x0c78 = 3192 mV = 3.192V 331 +* Singal: 0x17 = 23 332 +* Soil Moisture: 0x075e= 1886 = 18.86 % 333 +* Soil Temperature:0x0a8c =2700=27 °C 334 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 335 +* Interrupt: 0x00 = 0 336 + 337 +== 2.4 Payload Explanation and Sensor Interface == 338 + 339 + 340 +=== 2.4.1 Device ID === 341 + 432 432 ((( 433 - Forexample:343 +By default, the Device ID equal to the last 6 bytes of IMEI. 434 434 ))) 435 435 436 436 ((( 437 - (% style="color:blue" %)**AT+ CFGMOD=2**~/~/willsetthe N95S31B towork in MOD=2 distancemode whichtargetto measure distancevia UltrasonicSensor.347 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 438 438 ))) 439 439 440 - 441 441 ((( 442 - The uplink payloads are composed in ASCII String. For example:351 +**Example:** 443 443 ))) 444 444 445 445 ((( 446 -0 a cd 00 ed 0a cc 00 00 ef 02 d21d (total24 ASCII Chars) . Representative the actually payload:355 +AT+DEUI=A84041F15612 447 447 ))) 448 448 449 449 ((( 450 - 0x0acd00ed0acc0000ef02d21dTotal12 bytes359 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 451 451 ))) 452 452 453 453 363 + 364 +=== 2.4.2 Version Info === 365 + 454 454 ((( 455 - (%style="color:red"%)**NOTE:**367 +Specify the software version: 0x64=100, means firmware version 1.00. 456 456 ))) 457 457 458 -(% style="color:red" %) 459 -1. ((( 460 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 370 +((( 371 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 461 461 ))) 462 -1. ((( 463 -**By default, the device will send an uplink message every 1 hour.** 464 464 465 465 466 466 467 - 376 +=== 2.4.3 Battery Info === 377 + 378 +((( 379 +Check the battery voltage for LSE01. 468 468 ))) 469 469 470 -=== 2.3.1 Payload Analyze === 382 +((( 383 +Ex1: 0x0B45 = 2885mV 384 +))) 471 471 386 +((( 387 +Ex2: 0x0B49 = 2889mV 388 +))) 472 472 473 -==== 2.3.1.1 Before Firmware v1.2 ==== 474 474 475 475 476 - N95S31Buplink payloadincludes inotal21 bytes392 +=== 2.4.4 Signal Strength === 477 477 478 - 479 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 480 -|=(% style="width: 50px;" %)((( 481 -**Size(bytes)** 482 -)))|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2** 483 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)((( 484 484 ((( 485 - Reserve/Sameas NBSN95 CFGMOD=1395 +NB-IoT Network signal Strength. 486 486 ))) 487 487 488 488 ((( 489 - Nofunctionhere.399 +**Ex1: 0x1d = 29** 490 490 ))) 491 - )))|(% style="width:102px" %)(((401 + 492 492 ((( 493 - [[Temperature>>||anchor="H2.3.6A0Temperature26Humidity"]]403 +(% style="color:blue" %)**0**(%%) -113dBm or less 494 494 ))) 495 495 496 496 ((( 497 - BySHT31407 +(% style="color:blue" %)**1**(%%) -111dBm 498 498 ))) 499 - )))|(% style="width:81px" %)(((409 + 500 500 ((( 501 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]411 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 502 502 ))) 503 503 504 504 ((( 505 - BySHT31415 +(% style="color:blue" %)**31** (%%) -51dBm or greater 506 506 ))) 507 -))) 508 508 509 509 ((( 510 - 511 - 512 -((( 513 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 419 +(% style="color:blue" %)**99** (%%) Not known or not detectable 514 514 ))) 515 -))) 516 516 517 517 518 -[[image:1657354294009-643.png]] 519 519 424 +=== 2.4.5 Soil Moisture === 520 520 521 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 426 +((( 427 +((( 428 +Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil. 429 +))) 430 +))) 522 522 523 -**where:** 432 +((( 433 +((( 434 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 435 +))) 436 +))) 524 524 525 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 526 - 527 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 528 - 529 -* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 530 - 531 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 532 - 533 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 534 - 535 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 536 - 537 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 538 - 539 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 540 - 541 541 ((( 542 542 440 +))) 543 543 544 - 545 - 442 +((( 443 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 546 546 ))) 547 547 548 -==== 2.3.1.2 Since Firmware v1.2 ==== 549 549 550 550 551 - Inthismode, uplink payloadincludes 91 bytes in total by default.448 +=== 2.4.6 Soil Temperature === 552 552 553 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 554 - 555 - 556 -(% border="2" style="background-color:#ffffcc; color:green; width:520px" %) 557 -|(% style="width:50px" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**2**|(% style="width:50px" %)**1**|(% style="width:30px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:50px" %)**4** 558 -|(% style="width:95px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 559 - 560 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 561 - 562 - 563 -[[image:image-20220908154949-1.png]] 564 - 565 - 566 -The payload is ASCII string, representative same HEX: 567 - 568 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ ** 569 - 570 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 571 - 572 -**where:** 573 - 574 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 575 - 576 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 577 - 578 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 579 - 580 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 581 - 582 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 583 - 584 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 585 - 586 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 587 - 588 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 589 - 590 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 591 - 592 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 593 - 594 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 595 - 596 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 597 - 598 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 599 - 600 - 601 -=== 2.3.2 Device ID === 602 - 603 - 604 604 ((( 605 - Bydefault,theDeviceID equal to thelast6bytes ofIMEI.451 +Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is 606 606 ))) 607 607 608 608 ((( 609 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 610 - 611 - 455 +**Example**: 612 612 ))) 613 613 614 614 ((( 615 - (%style="color:blue"%)**Example:**459 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 616 616 ))) 617 617 618 618 ((( 619 - AT+DEUI=A84041F15612463 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 620 620 ))) 621 621 622 -((( 623 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID. 624 624 625 - 626 -))) 627 627 628 - (% style="color:red"%)**NOTE:When the firmwareversionsv1.2 and laterfirmware:**468 +=== 2.4.7 Soil Conductivity (EC) === 629 629 630 - 631 -By default, the Device ID equal to the last 15 bits of IMEI. 632 - 633 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 634 - 635 - 636 -(% style="color:blue" %)**Example:** 637 - 638 -AT+DEUI=868411056754138 639 - 640 - 641 - 642 -=== 2.3.3 Version Info === 643 - 644 - 645 645 ((( 646 - These bytes include thehardware andsoftwareversion.471 +Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000). 647 647 ))) 648 648 649 649 ((( 650 - Higherbyte: Specifyhardwareversion: always 0x00forN95S31B475 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 651 651 ))) 652 652 653 653 ((( 654 - Lowerbyte:Specifythesoftwareversion:0x6E=110, means firmwareversion110479 +Generally, the EC value of irrigation water is less than 800uS / cm. 655 655 ))) 656 656 657 657 ((( ... ... @@ -659,87 +659,71 @@ 659 659 ))) 660 660 661 661 ((( 662 - Forexample: 0x00 6E: this device is N95S31B with firmware version 110.487 + 663 663 ))) 664 664 490 +=== 2.4.8 Digital Interrupt === 491 + 665 665 ((( 666 - 493 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server. 667 667 ))) 668 668 669 - 670 -=== 2.3.4 Battery Info === 671 - 672 - 673 673 ((( 674 - Ex1:0x0B45 = 2885mV497 +The command is: 675 675 ))) 676 676 677 677 ((( 678 - Ex2:0x0B49=2889mV501 +(% 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]])**.** 679 679 ))) 680 680 681 681 505 +((( 506 +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. 507 +))) 682 682 683 -=== 2.3.5 Signal Strength === 684 684 685 - 686 686 ((( 687 - NB-IoT Network signalStrength.511 +Example: 688 688 ))) 689 689 690 690 ((( 691 - **Ex1:0x1d=29**515 +0x(00): Normal uplink packet. 692 692 ))) 693 693 694 694 ((( 695 -( %style="color:blue"%)**0**(%%) -113dBm orless519 +0x(01): Interrupt Uplink Packet. 696 696 ))) 697 697 522 + 523 + 524 +=== 2.4.9 +5V Output === 525 + 698 698 ((( 699 - (%style="color:blue"%)**1**(%%)-111dBm527 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 700 700 ))) 701 701 530 + 702 702 ((( 703 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm532 +The 5V output time can be controlled by AT Command. 704 704 ))) 705 705 706 706 ((( 707 -(% style="color:blue" %)** 31**(%%) -51dBm or greater536 +(% style="color:blue" %)**AT+5VT=1000** 708 708 ))) 709 709 710 710 ((( 711 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable540 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 712 712 ))) 713 713 714 714 715 715 716 -== =2.3.6Temperature & Humidity ===545 +== 2.5 Downlink Payload == 717 717 547 +By default, NSE01 prints the downlink payload to console port. 718 718 719 - The devicewill beable toget the SHT31temperature and humidity data now and upload to IoT Server.549 +[[image:image-20220708133731-5.png]] 720 720 721 -[[image:image-20220709161741-3.png]] 722 722 723 - 724 -Convert the read byte to decimal and divide it by ten. 725 - 726 - 727 -**Example:** 728 - 729 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 730 - 731 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 732 - 733 - 734 - 735 -== 2.4 Downlink Payload == 736 - 737 - 738 -By default, N95S31B prints the downlink payload to console port. 739 - 740 -[[image:image-20220709100028-1.png]] 741 - 742 - 743 743 ((( 744 744 (% style="color:blue" %)**Examples:** 745 745 ))) ... ... @@ -773,7 +773,7 @@ 773 773 ))) 774 774 775 775 ((( 776 -If payload = 0x04FF, it will reset the 95S31B585 +If payload = 0x04FF, it will reset the NSE01 777 777 ))) 778 778 779 779 ... ... @@ -785,82 +785,78 @@ 785 785 786 786 787 787 788 -== 2. 5HumidityandTemperaturealarm function==597 +== 2.6 LED Indicator == 789 789 599 +((( 600 +The NSE01 has an internal LED which is to show the status of different state. 790 790 791 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 792 792 603 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 604 +* Then the LED will be on for 1 second means device is boot normally. 605 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 606 +* For each uplink probe, LED will be on for 500ms. 607 +))) 793 793 794 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 795 795 796 796 797 -² When min=0, and max≠0, Alarm higher than max 798 798 799 - ²Whenmin≠0,and max=0, Alarmlower thanmin612 +== 2.7 Installation in Soil == 800 800 801 - ² When min≠0and max≠0, Alarmhigherthanmaxorlowerthan min614 +__**Measurement the soil surface**__ 802 802 616 +((( 617 +Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]] 618 +))) 803 803 804 - (% style="color:blue" %)**Example:**620 +[[image:1657259653666-883.png]] 805 805 806 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 807 807 623 +((( 624 + 808 808 809 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 626 +((( 627 +Dig a hole with diameter > 20CM. 628 +))) 810 810 811 -² When min=0, and max≠0, Alarm higher than max 630 +((( 631 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 632 +))) 633 +))) 812 812 813 - ² When min≠0, andmax=0, Alarm lower thanmin635 +[[image:1654506665940-119.png]] 814 814 815 -² When min≠0 and max≠0, Alarm higher than max or lower than min 637 +((( 638 + 639 +))) 816 816 817 817 818 - **~(%style="color:blue"%)Example:(%%)**642 +== 2.8 Firmware Change Log == 819 819 820 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 821 821 645 +Download URL & Firmware Change log 822 822 647 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 823 823 824 -== 2.6 Set the number of data to be uploaded and the recording time == 825 825 650 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 826 826 827 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 828 828 829 -* (% style="color:#037691" %)**AT+TR=900** (%%)~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 830 -* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 831 831 832 - Thediagram below explainstheelationshipbetweenTR, NOUD,and TDC more clearly**:**654 +== 2.9 Battery Analysis == 833 833 834 - [[image:image-20221009001045-1.png||height="726"width="1009"]]656 +=== 2.9.1 Battery Type === 835 835 836 836 837 - 838 -== 2.7 Read or Clear cached data == 839 - 840 - 841 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 842 - 843 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 844 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 845 - 846 -[[image:image-20220908163102-2.png]] 847 - 848 - 849 - 850 -== 2.8 Battery Analysis == 851 - 852 - 853 -=== 2.8.1 Battery Type === 854 - 855 - 856 856 ((( 857 -The N 95S31Bbattery 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.660 +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. 858 858 ))) 859 859 663 + 860 860 ((( 861 861 The battery is designed to last for several years depends on the actually use environment and update interval. 862 862 ))) 863 863 668 + 864 864 ((( 865 865 The battery related documents as below: 866 866 ))) ... ... @@ -870,42 +870,61 @@ 870 870 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 871 871 872 872 ((( 873 -[[image:image-2022070 9101450-2.png]]678 +[[image:image-20220708140453-6.png]] 874 874 ))) 875 875 876 876 877 877 878 -=== 2. 8.2 Power consumption Analyze ===683 +=== 2.9.2 Power consumption Analyze === 879 879 685 +((( 686 +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. 687 +))) 880 880 689 + 881 881 ((( 882 - The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement toanalyzethe powerconsumption in different case.User can useit for design guideline for their project.691 +Instruction to use as below: 883 883 ))) 884 884 885 885 ((( 886 - 695 +(% 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/]] 887 887 ))) 888 888 889 889 890 -=== 2.8.3 Battery Note === 699 +((( 700 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 701 +))) 891 891 703 +* ((( 704 +Product Model 705 +))) 706 +* ((( 707 +Uplink Interval 708 +))) 709 +* ((( 710 +Working Mode 711 +))) 892 892 893 893 ((( 894 - The Li-SICO batteryis designed for smallcurrent/ long periodapplication.Itisnotgoodto use a high current, short period transmit method. The recommendedminimum period for useof thisbatteryis5 minutes. If you use a shorterperiod time to uplinkdata, thenthe battery life may be decreased.714 +And the Life expectation in difference case will be shown on the right. 895 895 ))) 896 896 717 +[[image:image-20220708141352-7.jpeg]] 897 897 898 898 899 -=== 2.8.4 Replace the battery === 900 900 721 +=== 2.9.3 Battery Note === 901 901 902 902 ((( 903 - 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.724 +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. 904 904 ))) 905 905 906 906 728 + 729 +=== 2.9.4 Replace the battery === 730 + 907 907 ((( 908 -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).732 +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). 909 909 ))) 910 910 911 911 ... ... @@ -912,7 +912,6 @@ 912 912 913 913 = 3. Access NB-IoT Module = 914 914 915 - 916 916 ((( 917 917 Users can directly access the AT command set of the NB-IoT module. 918 918 ))) ... ... @@ -919,23 +919,19 @@ 919 919 920 920 ((( 921 921 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/]] 922 - 923 - 924 924 ))) 925 925 926 -[[image:1657 333200519-600.png]]747 +[[image:1657261278785-153.png]] 927 927 928 928 929 929 930 930 = 4. Using the AT Commands = 931 931 932 - 933 933 == 4.1 Access AT Commands == 934 934 755 +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/]] 935 935 936 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 937 937 938 - 939 939 AT+<CMD>? : Help on <CMD> 940 940 941 941 AT+<CMD> : Run <CMD> ... ... @@ -975,24 +975,7 @@ 975 975 976 976 AT+SERVADDR : Server Address 977 977 978 -AT+TR : Get or Set record time 979 979 980 -AT+APN : Get or set the APN 981 - 982 -AT+FBAND : Get or Set whether to automatically modify the frequency band 983 - 984 -AT+DNSCFG : Get or Set DNS Server 985 - 986 -AT+GETSENSORVALUE : Returns the current sensor measurement 987 - 988 -AT+NOUD : Get or Set the number of data to be uploaded 989 - 990 -AT+CDP : Read or Clear cached data 991 - 992 -AT+SHTEMP: Get or Set alarm of temp 993 - 994 -AT+SHHUM: Get or Set alarm of moisture 995 - 996 996 (% style="color:#037691" %)**COAP Management** 997 997 998 998 AT+URI : Resource parameters ... ... @@ -1026,7 +1026,6 @@ 1026 1026 1027 1027 = 5. FAQ = 1028 1028 1029 - 1030 1030 == 5.1 How to Upgrade Firmware == 1031 1031 1032 1032 ... ... @@ -1039,18 +1039,20 @@ 1039 1039 ))) 1040 1040 1041 1041 ((( 1042 - 843 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 844 +))) 1043 1043 846 + 847 + 848 +== 5.2 Can I calibrate NSE01 to different soil types? == 849 + 1044 1044 ((( 1045 - (%style="color:red"%)**Notice,N95S31BandLSN50v2share thesamemotherboard.Theyuse thesameconnectionand method toupdate.**851 +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]]. 1046 1046 ))) 1047 -))) 1048 1048 1049 1049 1050 - 1051 1051 = 6. Trouble Shooting = 1052 1052 1053 - 1054 1054 == 6.1 Connection problem when uploading firmware == 1055 1055 1056 1056 ... ... @@ -1066,7 +1066,6 @@ 1066 1066 1067 1067 == 6.2 AT Command input doesn't work == 1068 1068 1069 - 1070 1070 ((( 1071 1071 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 1072 1072 ... ... @@ -1077,7 +1077,7 @@ 1077 1077 = 7. Order Info = 1078 1078 1079 1079 1080 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**882 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 1081 1081 1082 1082 1083 1083 (% class="wikigeneratedid" %) ... ... @@ -1092,7 +1092,7 @@ 1092 1092 1093 1093 (% style="color:#037691" %)**Package Includes**: 1094 1094 1095 -* N 95S31BNB-IoTTemperatureandHumiditySensor897 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 1096 1096 * External antenna x 1 1097 1097 ))) 1098 1098 ... ... @@ -1101,10 +1101,8 @@ 1101 1101 1102 1102 (% style="color:#037691" %)**Dimension and weight**: 1103 1103 1104 -* Device Size: 13.0 x 5 x 4.5 cm 1105 -* Device Weight: 150g 1106 -* Package Size / pcs : 14.0 x 8x 5 cm 1107 -* Weight / pcs : 180g 906 +* Size: 195 x 125 x 55 mm 907 +* Weight: 420g 1108 1108 ))) 1109 1109 1110 1110 ((( ... ... @@ -1116,6 +1116,5 @@ 1116 1116 1117 1117 = 9. Support = 1118 1118 1119 - 1120 1120 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1121 1121 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
- 1657331036973-987.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -83.8 KB - Content
- 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
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709100028-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.8 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
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.7 KB - Content
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content