Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
Uploaded new attachment "1657330501006-241.png", version {1}
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 31 removed)
- 1657330533775-472.png
- 1657330723006-866.png
- 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-20220709093918-1.png
- image-20220709093918-2.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
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N 95S31BNB-IoTTemperature& HumiditySensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - 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,16 +58,20 @@ 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 58 + 59 + 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -85,6 +85,7 @@ 85 85 * - B20 @H-FDD: 800MHz 86 86 * - B28 @H-FDD: 700MHz 87 87 77 + 88 88 (% style="color:#037691" %)**Battery:** 89 89 90 90 * Li/SOCI2 un-chargeable battery ... ... @@ -93,9 +93,17 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 96 -== 1.4 Applications == 97 97 87 +(% style="color:#037691" %)**Power Consumption** 98 98 89 +* STOP Mode: 10uA @ 3.3v 90 +* Max transmit power: 350mA@3.3v 91 + 92 + 93 + 94 + 95 +== 1.4 Applications == 96 + 99 99 * Smart Buildings & Home Automation 100 100 * Logistics and Supply Chain Management 101 101 * Smart Metering ... ... @@ -108,65 +108,25 @@ 108 108 109 109 110 110 109 +== 1.5 Pin Definitions == 111 111 112 -== 1.5 Pin Definitions & Switch == 113 113 112 +[[image:1657328609906-564.png]] 114 114 115 -N95S31B use the mother board from NBSN95 which as below. 116 116 117 117 118 -[[image:image-20220709144723-1.png]] 119 119 117 += 2. Use NDDS75 to communicate with IoT Server = 120 120 121 - 122 -=== 1.5.1 Jumper JP2 === 123 - 124 - 125 -Power on Device when put this jumper. 126 - 127 - 128 - 129 -=== 1.5.2 BOOT MODE / SW1 === 130 - 131 - 132 -((( 133 -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. 134 -))) 135 - 136 -((( 137 -2) Flash: work mode, device starts to work and send out console output for further debug 138 -))) 139 - 140 - 141 - 142 -=== 1.5.3 Reset Button === 143 - 144 - 145 -Press to reboot the device. 146 - 147 - 148 - 149 -=== 1.5.4 LED === 150 - 151 - 152 -It will flash: 153 - 154 -1. When boot the device in flash mode 155 -1. Send an uplink packet 156 - 157 -= 2. Use N95S31B to communicate with IoT Server = 158 - 159 - 160 160 == 2.1 How it works == 161 161 162 - 163 163 ((( 164 -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.122 +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. 165 165 ))) 166 166 167 167 168 168 ((( 169 -The diagram below shows the working flow in default firmware of N 95S31B:127 +The diagram below shows the working flow in default firmware of NDDS75: 170 170 ))) 171 171 172 172 ((( ... ... @@ -173,7 +173,7 @@ 173 173 174 174 ))) 175 175 176 -[[image:1657 520100595-569.png]]134 +[[image:1657328659945-416.png]] 177 177 178 178 ((( 179 179 ... ... @@ -180,69 +180,30 @@ 180 180 ))) 181 181 182 182 183 -== 2.2 Configure the N 95S31B==141 +== 2.2 Configure the NDDS75 == 184 184 185 185 186 -=== 2.2.1 Power On N95S31B === 187 - 188 - 189 -[[image:image-20220709150546-2.png]] 190 - 191 - 192 - 193 193 === 2.2.1 Test Requirement === 194 194 195 - 196 196 ((( 197 -To use N 95S31Bin your city, make sure meet below requirements:147 +To use NDDS75 in your city, make sure meet below requirements: 198 198 ))) 199 199 200 -* ((( 201 -Your local operator has already distributed a NB-IoT Network there. 202 -))) 203 -* ((( 204 -The local NB-IoT network used the band that N95S31B supports. 205 -))) 206 -* ((( 207 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 208 -))) 150 +* Your local operator has already distributed a NB-IoT Network there. 151 +* The local NB-IoT network used the band that NSE01 supports. 152 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 209 209 210 210 ((( 211 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 155 +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 212 212 ))) 213 213 214 -((( 215 -N95S31B supports different communication protocol such as : 216 -))) 217 217 218 -((( 219 -* ((( 220 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 221 -))) 222 -* ((( 223 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 224 -))) 225 -* ((( 226 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 227 -))) 228 -* ((( 229 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 230 -))) 159 +[[image:1657328756309-230.png]] 231 231 232 -((( 233 -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. 234 -))) 235 235 236 - 237 -))) 238 238 239 - [[image:1657350625843-586.png]]163 +=== 2.2.2 Insert SIM card === 240 240 241 - 242 - 243 -=== 2.2.3 Insert SIM card === 244 - 245 - 246 246 ((( 247 247 Insert the NB-IoT Card get from your provider. 248 248 ))) ... ... @@ -252,24 +252,20 @@ 252 252 ))) 253 253 254 254 255 -[[image:16573 51240556-536.png]]174 +[[image:1657328884227-504.png]] 256 256 257 257 258 258 259 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===178 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 260 260 261 - 262 262 ((( 263 263 ((( 264 -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. 265 - 266 - 182 +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. 267 267 ))) 268 268 ))) 269 269 270 -[[image: 1657351312545-300.png]]186 +[[image:image-20220709092052-2.png]] 271 271 272 - 273 273 **Connection:** 274 274 275 275 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -288,359 +288,286 @@ 288 288 * Flow Control: (% style="color:green" %)**None** 289 289 290 290 ((( 291 -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.206 +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. 292 292 ))) 293 293 294 294 [[image:1657329814315-101.png]] 295 295 296 - 297 297 ((( 298 -(% 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]]**212 +(% 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/]] 299 299 ))) 300 300 301 301 302 302 303 -=== 2.2. 5Use CoAP protocol to uplink data ===217 +=== 2.2.4 Use CoAP protocol to uplink data === 304 304 219 +(% 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/]] 305 305 306 -(% 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/]]** 307 307 308 - 309 -((( 310 310 **Use below commands:** 311 -))) 312 312 313 -* ((( 314 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 315 -))) 316 -* ((( 317 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 318 -))) 319 -* ((( 320 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 321 -))) 224 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 225 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 226 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 322 322 323 -((( 324 - 325 - 326 326 For parameter description, please refer to AT command set 327 -))) 328 328 329 -[[image:1657 352146020-183.png]]230 +[[image:1657249793983-486.png]] 330 330 331 331 332 -((( 333 -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. 334 -))) 233 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server. 335 335 336 -[[image:1657 352185396-303.png]]235 +[[image:1657249831934-534.png]] 337 337 338 338 339 339 340 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===239 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 341 341 241 +This feature is supported since firmware version v1.0.1 342 342 343 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 243 + 244 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 344 344 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 345 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 246 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 346 346 347 -[[image:1657 352391268-297.png]]248 +[[image:1657249864775-321.png]] 348 348 349 349 350 -[[image:1657 352403317-397.png]]251 +[[image:1657249930215-289.png]] 351 351 352 352 353 353 354 -=== 2.2. 7Use MQTT protocol to uplink data ===255 +=== 2.2.6 Use MQTT protocol to uplink data === 355 355 257 +This feature is supported since firmware version v110 356 356 357 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 358 358 359 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 360 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 361 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 362 -* (% style="color:blue" %)**AT+UNAME=UNAME 363 -* (% style="color:blue" %)**AT+PWD=PWD 364 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527365 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527**(%%)260 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 261 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 262 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 263 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 264 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 265 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 266 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 366 366 367 -[[image:1657 352634421-276.png]]268 +[[image:1657249978444-674.png]] 368 368 369 369 370 -[[image:1657 352645687-385.png]]271 +[[image:1657249990869-686.png]] 371 371 372 372 373 373 ((( 374 -To savebatterylife,N95S31Bwillestablishasubscriptionbeforeeachuplinkandclose thesubscription3 secondsafteruplinksuccessful. Any downlink commandsfromserver will onlyarriveduringthesubscriptionperiod.275 +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. 375 375 ))) 376 376 377 377 378 -((( 379 -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. 380 -))) 381 381 280 +=== 2.2.7 Use TCP protocol to uplink data === 382 382 383 - 384 -=== 2.2.8 Use TCP protocol to uplink data === 385 - 386 - 387 387 This feature is supported since firmware version v110 388 388 284 + 389 389 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 390 390 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 391 391 392 -[[image:1657 352898400-901.png]]288 +[[image:1657250217799-140.png]] 393 393 394 394 395 -[[image:1657 352914475-252.png]]291 +[[image:1657250255956-604.png]] 396 396 397 397 398 398 399 -=== 2.2. 9Change Update Interval ===295 +=== 2.2.8 Change Update Interval === 400 400 401 - 402 402 User can use below command to change the (% style="color:green" %)**uplink interval**. 403 403 404 404 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 405 405 406 406 ((( 407 - 302 +(% style="color:red" %)**NOTE:** 408 408 ))) 409 409 410 410 ((( 411 -(% style="color:red" %) **NOTE:Sincefirmware version is v1.2:**306 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 412 412 ))) 413 413 414 -((( 415 -(% 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).** 416 -))) 417 417 418 418 419 - 420 420 == 2.3 Uplink Payload == 421 421 313 +In this mode, uplink payload includes in total 18 bytes 422 422 315 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 316 +|=(% style="width: 60px;" %)((( 317 +**Size(bytes)** 318 +)))|=(% 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** 319 +|(% 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"]] 320 + 423 423 ((( 424 - N95S31B has differentworking modesforthe connections of different typesofsensors. This section describesthesemodes.Usercanuse theAT Command (% style="color:blue"%)**AT+MOD**(%%)toset NBSN95to different workingmodes.322 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 425 425 ))) 426 426 427 427 326 +[[image:image-20220708111918-4.png]] 327 + 328 + 329 +The payload is ASCII string, representative same HEX: 330 + 331 +0x72403155615900640c7817075e0a8c02f900 where: 332 + 333 +* Device ID: 0x 724031556159 = 724031556159 334 +* Version: 0x0064=100=1.0.0 335 + 336 +* BAT: 0x0c78 = 3192 mV = 3.192V 337 +* Singal: 0x17 = 23 338 +* Soil Moisture: 0x075e= 1886 = 18.86 % 339 +* Soil Temperature:0x0a8c =2700=27 °C 340 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 341 +* Interrupt: 0x00 = 0 342 + 343 +== 2.4 Payload Explanation and Sensor Interface == 344 + 345 + 346 +=== 2.4.1 Device ID === 347 + 428 428 ((( 429 - Forexample:349 +By default, the Device ID equal to the last 6 bytes of IMEI. 430 430 ))) 431 431 432 432 ((( 433 - (% style="color:blue" %)**AT+ CFGMOD=2**~/~/willsetthe N95S31B towork in MOD=2 distancemode whichtargetto measure distancevia UltrasonicSensor.353 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 434 434 ))) 435 435 436 - 437 437 ((( 438 - The uplink payloads are composed in ASCII String. For example:357 +**Example:** 439 439 ))) 440 440 441 441 ((( 442 -0 a cd 00 ed 0a cc 00 00 ef 02 d21d (total24 ASCII Chars) . Representative the actually payload:361 +AT+DEUI=A84041F15612 443 443 ))) 444 444 445 445 ((( 446 - 0x0acd00ed0acc0000ef02d21dTotal12 bytes365 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 447 447 ))) 448 448 449 449 369 + 370 +=== 2.4.2 Version Info === 371 + 450 450 ((( 451 - (%style="color:red"%)**NOTE:**373 +Specify the software version: 0x64=100, means firmware version 1.00. 452 452 ))) 453 453 454 -(% style="color:red" %) 455 -1. ((( 456 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 376 +((( 377 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 457 457 ))) 458 -1. ((( 459 -**By default, the device will send an uplink message every 1 hour.** 460 460 461 461 462 462 463 - 382 +=== 2.4.3 Battery Info === 383 + 384 +((( 385 +Check the battery voltage for LSE01. 464 464 ))) 465 465 466 -=== 2.3.1 Payload Analyze === 388 +((( 389 +Ex1: 0x0B45 = 2885mV 390 +))) 467 467 392 +((( 393 +Ex2: 0x0B49 = 2889mV 394 +))) 468 468 469 -==== 2.3.1.1 Before Firmware v1.2 ==== 470 470 471 471 472 - N95S31Buplink payloadincludes inotal21 bytes398 +=== 2.4.4 Signal Strength === 473 473 474 - 475 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %) 476 -|=(% style="width: 60px;" %)((( 477 -**Size(bytes)** 478 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2** 479 -|(% 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:174px" %)((( 480 480 ((( 481 - Reserve/Sameas NBSN95 CFGMOD=1401 +NB-IoT Network signal Strength. 482 482 ))) 483 483 484 484 ((( 485 - Nofunctionhere.405 +**Ex1: 0x1d = 29** 486 486 ))) 487 - )))|(% style="width:106px" %)(((407 + 488 488 ((( 489 - [[Temperature>>||anchor="H2.3.6A0Temperature26Humidity"]]409 +(% style="color:blue" %)**0**(%%) -113dBm or less 490 490 ))) 491 491 492 492 ((( 493 - BySHT31413 +(% style="color:blue" %)**1**(%%) -111dBm 494 494 ))) 495 - )))|(% style="width:85px" %)(((415 + 496 496 ((( 497 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]417 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 498 498 ))) 499 499 500 500 ((( 501 - BySHT31421 +(% style="color:blue" %)**31** (%%) -51dBm or greater 502 502 ))) 503 -))) 504 504 505 505 ((( 506 - 507 - 508 -((( 509 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 425 +(% style="color:blue" %)**99** (%%) Not known or not detectable 510 510 ))) 511 -))) 512 512 513 513 514 -[[image:1657354294009-643.png]] 515 515 430 +=== 2.4.5 Soil Moisture === 516 516 517 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 432 +((( 433 +((( 434 +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. 435 +))) 436 +))) 518 518 519 -* Device ID: 0x724031607457 = 724031607457 438 +((( 439 +((( 440 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 441 +))) 442 +))) 520 520 521 -* Version: 0x006e=110=1.1.0 522 - 523 -* BAT: 0x0ccd = 3277 mV = 3.277V 524 - 525 -* Signal: 0x1b = 27 526 - 527 -* Model: 0x01 = 1 528 - 529 -* 0x00dc000ccc= reserve, ignore in N95S31B 530 - 531 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 532 - 533 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 534 - 535 535 ((( 536 536 446 +))) 537 537 538 - 539 - 448 +((( 449 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 540 540 ))) 541 541 542 -==== 2.3.1.2 Since Firmware v1.2 ==== 543 543 544 544 545 - Inthismode, uplink payloadincludes 91 bytes in total by default.454 +=== 2.4.6 Soil Temperature === 546 546 547 -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. 548 - 549 - 550 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %) 551 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4** 552 -|(% 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 ..... 553 - 554 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 555 - 556 - 557 -[[image:image-20220908154949-1.png]] 558 - 559 - 560 -The payload is ASCII string, representative same HEX: 561 - 562 -0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where: 563 - 564 -* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782 565 - 566 -* (% style="color:blue" %)Version: 0x000c=120=1.2 567 - 568 -* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V 569 - 570 -* (% style="color:red" %)Singal: 0x0c = 12 571 - 572 -* (% style="color:blue" %)Mod: 0x01 = 1 573 - 574 -* TemDS18B20: 0x0000= 0 = 0 575 - 576 -* (% style="color:green" %)Interrupt: 0x00= 0 577 - 578 -* (% style="color:green" %)adc: 0x0030= 48 579 - 580 -* SHTTEM: 0x0114= 276 = 27.6 581 - 582 -* SHTHUM:0x0231 =561=56.1% 583 - 584 -* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 585 - 586 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 587 - 588 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 589 - 590 -=== 2.3.2 Device ID === 591 - 592 - 593 593 ((( 594 - Bydefault,theDeviceID equal to thelast6bytes ofIMEI.457 +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 595 595 ))) 596 596 597 597 ((( 598 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 599 - 600 - 461 +**Example**: 601 601 ))) 602 602 603 603 ((( 604 - (%style="color:blue"%)**Example:**465 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 605 605 ))) 606 606 607 607 ((( 608 - AT+DEUI=A84041F15612469 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 609 609 ))) 610 610 611 -((( 612 -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. 613 613 614 - 615 -))) 616 616 617 - (% style="color:red"%)**NOTE:When the firmwareversionsv1.2 and laterfirmware:**474 +=== 2.4.7 Soil Conductivity (EC) === 618 618 619 - 620 -By default, the Device ID equal to the last 15 bits of IMEI. 621 - 622 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 623 - 624 - 625 -**(% style="color:blue" %)Example:(%%)** 626 - 627 -AT+DEUI=868411056754138 628 - 629 - 630 - 631 -=== 2.3.3 Version Info === 632 - 633 - 634 634 ((( 635 - These bytes include thehardware andsoftwareversion.477 +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). 636 636 ))) 637 637 638 638 ((( 639 - Higherbyte: Specifyhardwareversion: always 0x00forN95S31B481 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 640 640 ))) 641 641 642 642 ((( 643 - Lowerbyte:Specifythesoftwareversion:0x6E=110, means firmwareversion110485 +Generally, the EC value of irrigation water is less than 800uS / cm. 644 644 ))) 645 645 646 646 ((( ... ... @@ -648,87 +648,71 @@ 648 648 ))) 649 649 650 650 ((( 651 - Forexample: 0x00 6E: this device is N95S31B with firmware version 110.493 + 652 652 ))) 653 653 496 +=== 2.4.8 Digital Interrupt === 497 + 654 654 ((( 655 - 499 +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. 656 656 ))) 657 657 658 - 659 -=== 2.3.4 Battery Info === 660 - 661 - 662 662 ((( 663 - Ex1:0x0B45 = 2885mV503 +The command is: 664 664 ))) 665 665 666 666 ((( 667 - Ex2:0x0B49=2889mV507 +(% 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]])**.** 668 668 ))) 669 669 670 670 511 +((( 512 +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. 513 +))) 671 671 672 -=== 2.3.5 Signal Strength === 673 673 674 - 675 675 ((( 676 - NB-IoT Network signalStrength.517 +Example: 677 677 ))) 678 678 679 679 ((( 680 - **Ex1:0x1d=29**521 +0x(00): Normal uplink packet. 681 681 ))) 682 682 683 683 ((( 684 -( %style="color:blue"%)**0**(%%) -113dBm orless525 +0x(01): Interrupt Uplink Packet. 685 685 ))) 686 686 528 + 529 + 530 +=== 2.4.9 +5V Output === 531 + 687 687 ((( 688 - (%style="color:blue"%)**1**(%%)-111dBm533 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 689 689 ))) 690 690 536 + 691 691 ((( 692 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm538 +The 5V output time can be controlled by AT Command. 693 693 ))) 694 694 695 695 ((( 696 -(% style="color:blue" %)** 31**(%%) -51dBm or greater542 +(% style="color:blue" %)**AT+5VT=1000** 697 697 ))) 698 698 699 699 ((( 700 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable546 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 701 701 ))) 702 702 703 703 704 704 705 -== =2.3.6Temperature & Humidity ===551 +== 2.5 Downlink Payload == 706 706 553 +By default, NSE01 prints the downlink payload to console port. 707 707 708 - The devicewill beable toget the SHT31temperature and humidity data now and upload to IoT Server.555 +[[image:image-20220708133731-5.png]] 709 709 710 -[[image:image-20220709161741-3.png]] 711 711 712 - 713 -Convert the read byte to decimal and divide it by ten. 714 - 715 - 716 -**Example:** 717 - 718 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 719 - 720 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 721 - 722 - 723 - 724 -== 2.4 Downlink Payload == 725 - 726 - 727 -By default, N95S31B prints the downlink payload to console port. 728 - 729 -[[image:image-20220709100028-1.png]] 730 - 731 - 732 732 ((( 733 733 (% style="color:blue" %)**Examples:** 734 734 ))) ... ... @@ -762,7 +762,7 @@ 762 762 ))) 763 763 764 764 ((( 765 -If payload = 0x04FF, it will reset the 95S31B591 +If payload = 0x04FF, it will reset the NSE01 766 766 ))) 767 767 768 768 ... ... @@ -774,82 +774,78 @@ 774 774 775 775 776 776 777 -== 2. 5HumidityandTemperaturealarm function==603 +== 2.6 LED Indicator == 778 778 605 +((( 606 +The NSE01 has an internal LED which is to show the status of different state. 779 779 780 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 781 781 609 +* 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) 610 +* Then the LED will be on for 1 second means device is boot normally. 611 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 612 +* For each uplink probe, LED will be on for 500ms. 613 +))) 782 782 783 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 784 784 785 785 786 -² When min=0, and max≠0, Alarm higher than max 787 787 788 - ²Whenmin≠0,and max=0, Alarmlower thanmin618 +== 2.7 Installation in Soil == 789 789 790 - ² When min≠0and max≠0, Alarmhigherthanmaxorlowerthan min620 +__**Measurement the soil surface**__ 791 791 622 +((( 623 +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]] 624 +))) 792 792 793 - (% style="color:blue" %)**Example:**626 +[[image:1657259653666-883.png]] 794 794 795 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 796 796 629 +((( 630 + 797 797 798 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 632 +((( 633 +Dig a hole with diameter > 20CM. 634 +))) 799 799 800 -² When min=0, and max≠0, Alarm higher than max 636 +((( 637 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 638 +))) 639 +))) 801 801 802 - ² When min≠0, andmax=0, Alarm lower thanmin641 +[[image:1654506665940-119.png]] 803 803 804 -² When min≠0 and max≠0, Alarm higher than max or lower than min 643 +((( 644 + 645 +))) 805 805 806 806 807 - **~(%style="color:blue"%)Example:(%%)**648 +== 2.8 Firmware Change Log == 808 808 809 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 810 810 651 +Download URL & Firmware Change log 811 811 653 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 812 812 813 -== 2.6 Set the number of data to be uploaded and the recording time == 814 814 656 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 815 815 816 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 817 817 818 -* (% 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) 819 -* (% 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. 820 820 821 - Thediagram below explainstheelationshipbetweenTR, NOUD,and TDC more clearly**:**660 +== 2.9 Battery Analysis == 822 822 823 - [[image:image-20221009000513-1.png||height="732"width="1018"]]662 +=== 2.9.1 Battery Type === 824 824 825 825 826 - 827 -== 2.7 Read or Clear cached data == 828 - 829 - 830 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 831 - 832 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 833 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 834 - 835 -[[image:image-20220908163102-2.png]] 836 - 837 - 838 - 839 -== 2.8 Battery Analysis == 840 - 841 - 842 -=== 2.8.1 Battery Type === 843 - 844 - 845 845 ((( 846 -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.666 +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. 847 847 ))) 848 848 669 + 849 849 ((( 850 850 The battery is designed to last for several years depends on the actually use environment and update interval. 851 851 ))) 852 852 674 + 853 853 ((( 854 854 The battery related documents as below: 855 855 ))) ... ... @@ -859,42 +859,61 @@ 859 859 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 860 860 861 861 ((( 862 -[[image:image-2022070 9101450-2.png]]684 +[[image:image-20220708140453-6.png]] 863 863 ))) 864 864 865 865 866 866 867 -=== 2. 8.2 Power consumption Analyze ===689 +=== 2.9.2 Power consumption Analyze === 868 868 691 +((( 692 +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. 693 +))) 869 869 695 + 870 870 ((( 871 - 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.697 +Instruction to use as below: 872 872 ))) 873 873 874 874 ((( 875 - 701 +(% 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/]] 876 876 ))) 877 877 878 878 879 -=== 2.8.3 Battery Note === 705 +((( 706 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 707 +))) 880 880 709 +* ((( 710 +Product Model 711 +))) 712 +* ((( 713 +Uplink Interval 714 +))) 715 +* ((( 716 +Working Mode 717 +))) 881 881 882 882 ((( 883 - 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.720 +And the Life expectation in difference case will be shown on the right. 884 884 ))) 885 885 723 +[[image:image-20220708141352-7.jpeg]] 886 886 887 887 888 -=== 2.8.4 Replace the battery === 889 889 727 +=== 2.9.3 Battery Note === 890 890 891 891 ((( 892 - 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.730 +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. 893 893 ))) 894 894 895 895 734 + 735 +=== 2.9.4 Replace the battery === 736 + 896 896 ((( 897 -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).738 +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). 898 898 ))) 899 899 900 900 ... ... @@ -901,7 +901,6 @@ 901 901 902 902 = 3. Access NB-IoT Module = 903 903 904 - 905 905 ((( 906 906 Users can directly access the AT command set of the NB-IoT module. 907 907 ))) ... ... @@ -908,23 +908,19 @@ 908 908 909 909 ((( 910 910 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/]] 911 - 912 - 913 913 ))) 914 914 915 -[[image:1657 333200519-600.png]]753 +[[image:1657261278785-153.png]] 916 916 917 917 918 918 919 919 = 4. Using the AT Commands = 920 920 921 - 922 922 == 4.1 Access AT Commands == 923 923 761 +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/]] 924 924 925 -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]] 926 926 927 - 928 928 AT+<CMD>? : Help on <CMD> 929 929 930 930 AT+<CMD> : Run <CMD> ... ... @@ -964,24 +964,7 @@ 964 964 965 965 AT+SERVADDR : Server Address 966 966 967 -AT+TR : Get or Set record time 968 968 969 -AT+APN : Get or set the APN 970 - 971 -AT+FBAND : Get or Set whether to automatically modify the frequency band 972 - 973 -AT+DNSCFG : Get or Set DNS Server 974 - 975 -AT+GETSENSORVALUE : Returns the current sensor measurement 976 - 977 -AT+NOUD : Get or Set the number of data to be uploaded 978 - 979 -AT+CDP : Read or Clear cached data 980 - 981 -AT+SHTEMP: Get or Set alarm of temp 982 - 983 -AT+SHHUM: Get or Set alarm of moisture 984 - 985 985 (% style="color:#037691" %)**COAP Management** 986 986 987 987 AT+URI : Resource parameters ... ... @@ -1015,7 +1015,6 @@ 1015 1015 1016 1016 = 5. FAQ = 1017 1017 1018 - 1019 1019 == 5.1 How to Upgrade Firmware == 1020 1020 1021 1021 ... ... @@ -1028,18 +1028,20 @@ 1028 1028 ))) 1029 1029 1030 1030 ((( 1031 - 849 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 850 +))) 1032 1032 852 + 853 + 854 +== 5.2 Can I calibrate NSE01 to different soil types? == 855 + 1033 1033 ((( 1034 - (%style="color:red"%)**Notice,N95S31BandLSN50v2share thesamemotherboard.Theyuse thesameconnectionand method toupdate.**857 +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]]. 1035 1035 ))) 1036 -))) 1037 1037 1038 1038 1039 - 1040 1040 = 6. Trouble Shooting = 1041 1041 1042 - 1043 1043 == 6.1 Connection problem when uploading firmware == 1044 1044 1045 1045 ... ... @@ -1055,7 +1055,6 @@ 1055 1055 1056 1056 == 6.2 AT Command input doesn't work == 1057 1057 1058 - 1059 1059 ((( 1060 1060 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. 1061 1061 ... ... @@ -1066,7 +1066,7 @@ 1066 1066 = 7. Order Info = 1067 1067 1068 1068 1069 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**888 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 1070 1070 1071 1071 1072 1072 (% class="wikigeneratedid" %) ... ... @@ -1081,7 +1081,7 @@ 1081 1081 1082 1082 (% style="color:#037691" %)**Package Includes**: 1083 1083 1084 -* N 95S31BNB-IoTTemperatureandHumiditySensor903 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 1085 1085 * External antenna x 1 1086 1086 ))) 1087 1087 ... ... @@ -1090,10 +1090,8 @@ 1090 1090 1091 1091 (% style="color:#037691" %)**Dimension and weight**: 1092 1092 1093 -* Device Size: 13.0 x 5 x 4.5 cm 1094 -* Device Weight: 150g 1095 -* Package Size / pcs : 14.0 x 8x 5 cm 1096 -* Weight / pcs : 180g 912 +* Size: 195 x 125 x 55 mm 913 +* Weight: 420g 1097 1097 ))) 1098 1098 1099 1099 ((( ... ... @@ -1105,8 +1105,5 @@ 1105 1105 1106 1106 = 9. Support = 1107 1107 1108 - 1109 1109 * 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. 1110 1110 * 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]] 1111 - 1112 -
- 1657330533775-472.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.9 KB - Content
- 1657330723006-866.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.1 KB - Content
- 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-20220709093918-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.2 KB - Content
- image-20220709093918-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -61.9 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