Changes for page NLMS01-NB-IoT Leaf Moisture Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:54
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,24 +9,20 @@ 9 9 10 10 = 1. Introduction = 11 11 12 + 12 12 == 1.1 What is NLMS01 Leaf Moisture Sensor == 13 13 14 14 15 -((( 16 16 The Dragino NLMS01 is a (% style="color:blue" %)**NB-IOT Leaf Moisture Sensor**(%%) for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof. 17 17 18 18 NLMS01 detects leaf's(% style="color:blue" %)** moisture and temperature use FDR method**(%%), it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy. 19 19 20 20 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. 21 +\\NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 22 +\\NLMS01 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). 23 +\\To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from local operator and install NLMS01 to get NB-IoT network connection. 21 21 22 -NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 23 23 24 -NLMS01 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). 25 - 26 -To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from local operator and install NLMS01 to get NB-IoT network connection. 27 -))) 28 - 29 - 30 30 [[image:image-20220907171221-2.png]] 31 31 32 32 ... ... @@ -33,6 +33,7 @@ 33 33 [[image:image-20220907171221-3.png]] 34 34 35 35 32 + 36 36 == 1.2 Features == 37 37 38 38 ... ... @@ -53,6 +53,7 @@ 53 53 ((( 54 54 55 55 53 + 56 56 57 57 ))) 58 58 ... ... @@ -66,15 +66,13 @@ 66 66 67 67 (% style="color:#037691" %)**NB-IoT Spec:** 68 68 69 -* B1 @H-FDD: 2100MHz 70 -* B3 @H-FDD: 1800MHz 71 -* B8 @H-FDD: 900MHz 72 -* B5 @H-FDD: 850MHz 73 -* B20 @H-FDD: 800MHz 74 -* B28 @H-FDD: 700MHz 67 +* - B1 @H-FDD: 2100MHz 68 +* - B3 @H-FDD: 1800MHz 69 +* - B8 @H-FDD: 900MHz 70 +* - B5 @H-FDD: 850MHz 71 +* - B20 @H-FDD: 800MHz 72 +* - B28 @H-FDD: 700MHz 75 75 76 - 77 - 78 78 == 1.4 Probe Specification == 79 79 80 80 ... ... @@ -94,15 +94,11 @@ 94 94 * IP67 Protection 95 95 * Length: 3.5 meters 96 96 97 - 98 - 99 99 == 1.5 Applications == 100 100 101 101 102 102 * Smart Agriculture 103 103 104 - 105 - 106 106 == 1.6 Pin mapping and power on == 107 107 108 108 ... ... @@ -110,8 +110,10 @@ 110 110 111 111 **~ ** 112 112 105 + 113 113 = 2. Use NLMS01 to communicate with IoT Server = 114 114 108 + 115 115 == 2.1 How it works == 116 116 117 117 ... ... @@ -123,8 +123,10 @@ 123 123 [[image:image-20220907171221-5.png]] 124 124 125 125 120 + 126 126 == 2.2 Configure the NLMS01 == 127 127 123 + 128 128 === 2.2.1 Test Requirement === 129 129 130 130 ... ... @@ -140,6 +140,7 @@ 140 140 [[image:image-20220907171221-6.png]] 141 141 142 142 139 + 143 143 === 2.2.2 Insert SIM card === 144 144 145 145 ... ... @@ -151,6 +151,7 @@ 151 151 [[image:image-20220907171221-7.png]] 152 152 153 153 151 + 154 154 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 155 155 156 156 ... ... @@ -182,6 +182,7 @@ 182 182 (% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 183 183 184 184 183 + 185 185 === 2.2.4 Use CoAP protocol to uplink data === 186 186 187 187 ... ... @@ -194,6 +194,8 @@ 194 194 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 195 195 * (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 196 196 196 + 197 + 197 197 For parameter description, please refer to AT command set 198 198 199 199 [[image:image-20220907171221-9.png]] ... ... @@ -204,6 +204,7 @@ 204 204 [[image:image-20220907171221-10.png]] 205 205 206 206 208 + 207 207 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 208 208 209 209 ... ... @@ -210,9 +210,11 @@ 210 210 This feature is supported since firmware version v1.0.1 211 211 212 212 * (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 213 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 215 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 214 214 * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 215 215 218 + 219 + 216 216 [[image:image-20220907171221-11.png]] 217 217 218 218 ... ... @@ -220,6 +220,7 @@ 220 220 221 221 222 222 227 + 223 223 === 2.2.6 Use MQTT protocol to uplink data === 224 224 225 225 ... ... @@ -233,6 +233,8 @@ 233 233 * (% style="color:#037691" %)**AT+PUBTOPIC=PUB ** (%%) ~/~/ Set the sending topic of MQTT 234 234 * (% style="color:#037691" %)**AT+SUBTOPIC=SUB ** (%%) ~/~/ Set the subscription topic of MQTT 235 235 241 + 242 + 236 236 [[image:image-20220907171221-13.png]] 237 237 238 238 ... ... @@ -244,6 +244,7 @@ 244 244 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. 245 245 246 246 254 + 247 247 === 2.2.7 Use TCP protocol to uplink data === 248 248 249 249 ... ... @@ -252,6 +252,8 @@ 252 252 * (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 253 253 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port 254 254 263 + 264 + 255 255 [[image:image-20220907171221-15.png]] 256 256 257 257 ... ... @@ -268,9 +268,12 @@ 268 268 269 269 * (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 270 270 281 + 282 + 271 271 (% style="color:red" %)**NOTE: By default, the device will send an uplink message every 2 hour. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 272 272 273 273 286 + 274 274 == 2.3 Uplink Payload == 275 275 276 276 ... ... @@ -279,10 +279,11 @@ 279 279 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. 280 280 281 281 282 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:520px" %)283 -|(% style=" background-color:#d9e2f3; color:#0070c0;width:50px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0;width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:50px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0;width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:50px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:50px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0;width:50px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**4**284 -|(% style="width:96px" %)Value|(% style="width:82px" %)Device ID|(% style="width:42px" %)Ver|(% style="width:48px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:58px" %)MOD|(% style="width:82px" %)Interrupt|(% style="width:113px" %)Leaf moisture|(% style="width:134px" %)Leaf Temperature|(% style="width:100px" %)Time stamp|(% style="width:137px" %)Leaf Temperature|(% style="width:110px" %)Leaf moisture|(% style="width:122px" %)Time stamp ..... 295 +(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 296 +|(% style="width:96px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:42px" %)**2**|(% style="width:48px" %)**2**|(% style="width:124px" %)1|(% style="width:58px" %)1|(% style="width:82px" %)1|(% style="width:113px" %)2|(% style="width:134px" %)2|(% style="width:100px" %)4|(% style="width:137px" %)2|(% style="width:110px" %)2|(% style="width:122px" %)4 297 +|(% style="width:96px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:42px" %)Ver|(% style="width:48px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:58px" %)MOD|(% style="width:82px" %)Interrupt|(% style="width:113px" %)Leaf moisture|(% style="width:134px" %)Leaf Temperature|(% style="width:100px" %)Time stamp|(% style="width:137px" %)Leaf Temperature|(% style="width:110px" %)Leaf moisture|(% style="width:122px" %)Time stamp ..... 285 285 299 + 286 286 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 287 287 288 288 ... ... @@ -291,45 +291,36 @@ 291 291 292 292 The payload is ASCII string, representative same HEX: 293 293 294 - **0x__f868411056754138__(% style="color:blue" %)__0064__(% style="color:green" %)__0c78__(% style="color:#00b0f0" %)__17__(% style="color:#7030a0" %)__01__(% style="color:#d60093" %)__00__(% style="color:#a14d07" %)__0225__ (% style="color:#0020b0" %) __010b__ (% style="color:#420042" %)__6315537b__ (% style="color:#663300" %)//__010b0226631550fb__ __010e022663154d77__//(%%)**308 +0x(% style="color:red" %)f868411056754138(% style="color:blue" %)0064(% style="color:green" %)0c78(% style="color:red" %)17(% style="color:blue" %)01(% style="color:green" %)00(% style="color:blue" %)**0225010b6315537b**010b0226631550fb**010e022663154d77**01110225631549f1**011502246315466b**01190223631542e5**011d022163153f62**011e022163153bde**011e022163153859**(%%)** **where: 295 295 296 -where: 310 +* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 311 +* (% style="color:blue" %)Version: 0x0064=100=1.0.0 312 +* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V 313 +* (% style="color:red" %)Singal: 0x17 = 23 314 +* (% style="color:blue" %)Mod: 0x01 = 1 315 +* (% style="color:green" %)Interrupt: 0x00= 0 316 +* Leaf moisture: 0x0225= 549 = 54.9% 317 +* Leaf Temperature:0x010B =267=26.7 °C 318 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 319 +* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 320 +* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 297 297 298 -* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 299 299 300 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 301 301 302 -* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 303 303 304 -* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 305 305 306 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 307 - 308 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 309 - 310 -* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9% 311 - 312 -* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C 313 - 314 -* (% style="color:#037691" %)**Time stamp :** (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 315 - 316 -* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp : **(%%)010b0226631550fb 317 - 318 -* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 319 - 320 - 321 - 322 322 == 2.4 Payload Explanation and Sensor Interface == 323 323 328 + 324 324 === 2.4.1 Device ID === 325 325 326 326 327 327 By default, the Device ID equal to the last 15 bits of IMEI. 328 328 329 -User can use (% style="color:#037691" %)**AT+DEUI**(%%)to set Device ID334 +User can use **AT+DEUI** to set Device ID 330 330 331 331 332 - (% style="color:blue" %)**Example**:337 +**Example:** 333 333 334 334 AT+DEUI=868411056754138 335 335 ... ... @@ -336,6 +336,7 @@ 336 336 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 337 337 338 338 344 + 339 339 === 2.4.2 Version Info === 340 340 341 341 ... ... @@ -344,6 +344,7 @@ 344 344 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 345 345 346 346 353 + 347 347 === 2.4.3 Battery Info === 348 348 349 349 ... ... @@ -354,14 +354,14 @@ 354 354 Ex2: 0x0B49 = 2889mV 355 355 356 356 364 + 357 357 === 2.4.4 Signal Strength === 358 358 359 359 360 360 NB-IoT Network signal Strength. 361 361 370 +**Ex1: 0x1d = 29** 362 362 363 -(% style="color:blue" %)**Ex1: 0x1d = 29** 364 - 365 365 **0** -113dBm or less 366 366 367 367 **1** -111dBm ... ... @@ -373,28 +373,31 @@ 373 373 **99** Not known or not detectable 374 374 375 375 383 + 376 376 === 2.4.5 Leaf moisture === 377 377 378 378 379 -Get the moisture of the (% style="color:#037691" %)**Leaf**(%%). The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the Leaf.387 +Get the moisture of the **Leaf**. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the **Leaf**. 380 380 381 -For example, if the data you get from the register is (% style="color:#037691" %)**__0x05 0xDC__**(%%), the moisture content in the(% style="color:#037691" %)**Leaf**(%%)is389 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is 382 382 383 - (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**391 +**0229(H) = 549(D) /100 = 54.9.** 384 384 385 385 394 + 386 386 === 2.4.6 Leaf Temperature === 387 387 388 388 389 -Get the temperature in the Leaf. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the Leaf. For example, if the data you get from the register is (% style="color:#037691" %)**__0x09 0xEC__**(%%), the temperature content in the(% style="color:#037691" %)**Leaf **(%%)is398 +Get the temperature in the **Leaf**. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the **Leaf**. For example, if the data you get from the register is **__0x09 0xEC__**, the temperature content in the **Leaf **is 390 390 391 - (% style="color:blue" %)**Example**:400 +**Example**: 392 392 393 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C402 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 394 394 395 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C404 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 396 396 397 397 407 + 398 398 === 2.4.7 Timestamp === 399 399 400 400 ... ... @@ -406,11 +406,11 @@ 406 406 === 2.4.8 Digital Interrupt === 407 407 408 408 409 -Digital Interrupt refers to pin (% style="color:#037691" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server.419 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server. 410 410 411 411 The command is: 412 412 413 - (% style="color:blue" %)**AT+INTMOD=3 **(%%)~/~/423 +**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]])**.** 414 414 415 415 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. 416 416 ... ... @@ -421,6 +421,7 @@ 421 421 0x(01): Interrupt Uplink Packet. 422 422 423 423 434 + 424 424 === 2.4.9 +5V Output === 425 425 426 426 ... ... @@ -428,29 +428,24 @@ 428 428 429 429 The 5V output time can be controlled by AT Command. 430 430 431 - (% style="color:blue" %)**AT+5VT=1000**442 +**AT+5VT=1000** 432 432 433 433 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 434 434 435 435 447 + 436 436 == 2.5 Downlink Payload == 437 437 438 438 439 439 By default, NLMS01 prints the downlink payload to console port. 440 440 441 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:479.818px" %) 442 -|=(% style="width: 183px; background-color:#D9E2F3;color:#0070C0" %)**Downlink Control Type**|=(% style="width: 55px; background-color:#D9E2F3;color:#0070C0" %)FPort|=(% style="width: 93px; background-color:#D9E2F3;color:#0070C0" %)**Type Code**|=(% style="width: 146px; background-color: rgb(217, 226, 243); color: rgb(0, 112, 192);" %)**Downlink payload size(bytes)** 443 -|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4 444 -|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2 445 -|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4 453 +[[image:image-20220907171221-18.png]] 446 446 447 - 448 448 449 - (% style="color:blue" %)**Examples:**456 +**Examples:** 450 450 458 +* **Set TDC** 451 451 452 -* (% style="color:#037691" %)**Set TDC** 453 - 454 454 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 455 455 456 456 Payload: 01 00 00 1E TDC=30S ... ... @@ -457,19 +457,16 @@ 457 457 458 458 Payload: 01 00 00 3C TDC=60S 459 459 466 +* **Reset** 460 460 461 - 462 -* (% style="color:#037691" %)**Reset** 463 - 464 464 If payload = 0x04FF, it will reset the NLMS01 465 465 470 +* **INTMOD** 466 466 467 - 468 -* (% style="color:#037691" %)**INTMOD** 469 - 470 470 Downlink Payload: 06000003, Set AT+INTMOD=3 471 471 472 472 475 + 473 473 == 2.6 LED Indicator == 474 474 475 475 ... ... @@ -482,6 +482,7 @@ 482 482 483 483 484 484 488 + 485 485 == 2.7 Installation == 486 486 487 487 ... ... @@ -491,12 +491,13 @@ 491 491 [[image:image-20220907171221-19.png]] 492 492 493 493 498 + 494 494 == 2.8 Moisture and Temperature alarm function == 495 495 496 496 497 - (% style="color:blue" %)**➢ AT Command:**502 +**➢ AT Command:** 498 498 499 - (% style="color:#037691" %)**AT+ HUMALARM =min,max**504 +**AT+ HUMALARM =min,max** 500 500 501 501 ² When min=0, and max≠0, Alarm higher than max 502 502 ... ... @@ -505,7 +505,7 @@ 505 505 ² When min≠0 and max≠0, Alarm higher than max or lower than min 506 506 507 507 508 - (% style="color:blue" %)**Example:**513 +**Example:** 509 509 510 510 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 511 511 ... ... @@ -518,51 +518,100 @@ 518 518 ² When min≠0 and max≠0, Alarm higher than max or lower than min 519 519 520 520 521 - (% style="color:blue" %)**Example:**526 +**Example:** 522 522 523 523 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 524 524 525 525 531 + 526 526 == 2.9 Set the number of data to be uploaded and the recording time == 527 527 528 528 529 - (% style="color:blue" %)**➢ AT Command:**535 +**➢ AT Command:** 530 530 531 -* (% 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) 532 -* (% 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. 537 +**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) 533 533 534 - The di agram belowexplainsthe relationshipbetweenTR, NOUD,andTDCmore clearly**:**539 +**AT+NOUD=8** ~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 535 535 536 -[[image:image-20221009001002-1.png||height="706" width="982"]] 537 537 538 538 539 539 == 2.10 Read or Clear cached data == 540 540 541 541 542 - (% style="color:blue" %)**➢ AT Command:**546 +**➢ AT Command:** 543 543 544 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 545 -* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 548 +**AT+CDP** ~/~/ Read cached data 546 546 550 +**AT+CDP=0 ** ~/~/ Clear cached data 551 + 552 + 547 547 [[image:image-20220907171221-20.png]] 548 548 549 549 556 + 550 550 == 2.11 Firmware Change Log == 551 551 552 552 553 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/ qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]560 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 554 554 555 -Upgrade Instruction: [[Upgrade Firmware>> ||anchor="H5.1200BHowtoUpgradeFirmware"]]562 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 556 556 557 557 558 -== 2.12 Battery & Power Consumption == 559 559 566 +== 2.12 Battery Analysis == 560 560 561 -NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 562 562 563 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].569 +=== 2.12.1 Battery Type === 564 564 565 565 572 +The NLMS01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 573 + 574 +The battery is designed to last for several years depends on the actually use environment and update interval. 575 + 576 +The battery related documents as below: 577 + 578 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 579 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 580 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 581 + 582 +[[image:image-20220907171221-21.png]] 583 + 584 + 585 + 586 +=== 2.12.2 Power consumption Analyze === 587 + 588 + 589 +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. 590 + 591 +Instruction to use as below: 592 + 593 +**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/]] 594 + 595 +**Step 2: ** Open it and choose 596 + 597 +* Product Model 598 +* Uplink Interval 599 +* Working Mode 600 + 601 +And the Life expectation in difference case will be shown on the right. 602 + 603 +[[image:image-20220907171221-22.jpeg]] 604 + 605 + 606 +=== 2.12.3 Battery Note === 607 + 608 + 609 +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. 610 + 611 + 612 + 613 +=== 2.12.4 Replace the battery === 614 + 615 + 616 +The default battery pack of NLMS01 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). 617 + 618 + 619 + 566 566 = 3. Access NB-IoT Module = 567 567 568 568 ... ... @@ -574,97 +574,101 @@ 574 574 [[image:image-20220907171221-23.png]] 575 575 576 576 631 + 577 577 = 4. Using the AT Commands = 578 578 634 + 579 579 == 4.1 Access AT Commands == 580 580 581 581 582 582 See this link for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 583 583 584 -AT+<CMD>? : 640 +AT+<CMD>? : Help on <CMD> 585 585 586 -AT+<CMD> :Run <CMD>642 +AT+<CMD> : Run <CMD> 587 587 588 -AT+<CMD>=<value>: 644 +AT+<CMD>=<value> : Set the value 589 589 590 -AT+<CMD>=? :Get the value646 +AT+<CMD>=? : Get the value 591 591 592 592 593 - (% style="color:#037691" %)**General Commands**649 +**General Commands** 594 594 595 -AT :Attention651 +AT : Attention 596 596 597 -AT? :Short Help653 +AT? : Short Help 598 598 599 -ATZ :MCU Reset655 +ATZ : MCU Reset 600 600 601 -AT+TDC : 657 +AT+TDC : Application Data Transmission Interval 602 602 603 -AT+CFG : 659 +AT+CFG : Print all configurations 604 604 605 -AT+CFGMOD : 661 +AT+CFGMOD : Working mode selection 606 606 607 -AT+INTMOD : 663 +AT+INTMOD : Set the trigger interrupt mode 608 608 609 -AT+5VT :Set extend the time of 5V power665 +AT+5VT : Set extend the time of 5V power 610 610 611 -AT+PRO :Choose agreement667 +AT+PRO : Choose agreement 612 612 613 -AT+RXDL :Extend the sending and receiving time669 +AT+RXDL : Extend the sending and receiving time 614 614 615 -AT+SERVADDR :Server Address671 +AT+SERVADDR : Server Address 616 616 617 -AT+APN :Get or set the APN673 +AT+APN : Get or set the APN 618 618 619 -AT+FBAND :Get or Set whether to automatically modify the frequency band675 +AT+FBAND : Get or Set whether to automatically modify the frequency band 620 620 621 -AT+DNSCFG : Get or Set DNS Server 677 +AT+DNSCFG : Get or Set DNS Server 622 622 623 623 AT+GETSENSORVALUE : Returns the current sensor measurement 624 624 625 -AT+TR : 681 +AT+TR : Get or Set record time" 626 626 627 -AT+NOUD : 683 +AT+NOUD : Get or Set the number of data to be uploaded 628 628 629 -AT+CDP : 685 +AT+CDP : Read or Clear cached data 630 630 631 -AT+TEMPALARM : 687 +AT+TEMPALARM : Get or Set alarm of temp 632 632 633 -AT+HUMALARM : humidity689 +AT+HUMALARM : Get or Set alarm of PH 634 634 635 635 636 - (% style="color:#037691" %)**COAP Management**692 +**COAP Management** 637 637 638 -AT+URI : 694 +AT+URI : Resource parameters 639 639 640 640 641 - (% style="color:#037691" %)**UDP Management**697 +**UDP Management** 642 642 643 -AT+CFM : 699 +AT+CFM : Upload confirmation mode (only valid for UDP) 644 644 645 645 646 - (% style="color:#037691" %)**MQTT Management**702 +**MQTT Management** 647 647 648 -AT+CLIENT : 704 +AT+CLIENT : Get or Set MQTT client 649 649 650 -AT+UNAME : Get or Set MQTT Username 706 +AT+UNAME : Get or Set MQTT Username 651 651 652 -AT+PWD 708 +AT+PWD : Get or Set MQTT password 653 653 654 -AT+PUBTOPIC :Get or Set MQTT publish topic710 +AT+PUBTOPIC : Get or Set MQTT publish topic 655 655 656 -AT+SUBTOPIC :Get or Set MQTT subscription topic712 +AT+SUBTOPIC : Get or Set MQTT subscription topic 657 657 658 658 659 - (% style="color:#037691" %)**Information**715 +**Information** 660 660 661 -AT+FDR :Factory Data Reset717 +AT+FDR : Factory Data Reset 662 662 663 -AT+PWORD :Serial Access Password719 +AT+PWORD : Serial Access Password 664 664 665 665 722 + 666 666 = 5. FAQ = 667 667 725 + 668 668 == 5.1 How to Upgrade Firmware == 669 669 670 670 ... ... @@ -672,12 +672,13 @@ 672 672 673 673 Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]] 674 674 733 +**Notice, NLMS01** **and LLMS01** **share the same mother board. They use the same connection and method to update.** 675 675 676 -(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 677 677 678 678 679 679 = 6. Trouble Shooting = 680 680 739 + 681 681 == 6.1 Connection problem when uploading firmware == 682 682 683 683 ... ... @@ -684,18 +684,14 @@ 684 684 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 685 685 686 686 746 + 687 687 == 6.2 AT Command input doesn't work == 688 688 689 689 690 -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.750 +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 **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string. 691 691 692 692 693 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 694 694 695 - 696 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 697 - 698 - 699 699 = 7. Order Info = 700 700 701 701 ... ... @@ -702,14 +702,15 @@ 702 702 Part Number**:** NLMS01 703 703 704 704 760 + 705 705 = 8. Packing Info = 706 706 707 707 708 - (% style="color:#037691" %)**Package Includes:**764 +**Package Includes**: 709 709 710 710 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 711 711 712 - (% style="color:#037691" %)**Dimension and weight**:768 +**Dimension and weight**: 713 713 714 714 * Device Size: cm 715 715 * Device Weight: g ... ... @@ -718,6 +718,7 @@ 718 718 719 719 720 720 777 + 721 721 = 9. Support = 722 722 723 723
- image-20221009001002-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content