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)
Details
- Page properties
-
- Content
-
... ... @@ -13,21 +13,16 @@ 13 13 == 1.1 What is NLMS01 Leaf Moisture Sensor == 14 14 15 15 16 -((( 17 17 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. 18 18 19 19 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. 20 20 21 21 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. 22 22 23 -NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 24 24 25 -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). 26 - 27 -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. 28 -))) 29 - 30 - 31 31 [[image:image-20220907171221-2.png]] 32 32 33 33 ... ... @@ -34,6 +34,7 @@ 34 34 [[image:image-20220907171221-3.png]] 35 35 36 36 32 + 37 37 == 1.2 Features == 38 38 39 39 ... ... @@ -67,12 +67,12 @@ 67 67 68 68 (% style="color:#037691" %)**NB-IoT Spec:** 69 69 70 -* B1 @H-FDD: 2100MHz 71 -* B3 @H-FDD: 1800MHz 72 -* B8 @H-FDD: 900MHz 73 -* B5 @H-FDD: 850MHz 74 -* B20 @H-FDD: 800MHz 75 -* B28 @H-FDD: 700MHz 66 +* - B1 @H-FDD: 2100MHz 67 +* - B3 @H-FDD: 1800MHz 68 +* - B8 @H-FDD: 900MHz 69 +* - B5 @H-FDD: 850MHz 70 +* - B20 @H-FDD: 800MHz 71 +* - B28 @H-FDD: 700MHz 76 76 77 77 78 78 ... ... @@ -111,8 +111,10 @@ 111 111 112 112 **~ ** 113 113 110 + 114 114 = 2. Use NLMS01 to communicate with IoT Server = 115 115 113 + 116 116 == 2.1 How it works == 117 117 118 118 ... ... @@ -124,8 +124,10 @@ 124 124 [[image:image-20220907171221-5.png]] 125 125 126 126 125 + 127 127 == 2.2 Configure the NLMS01 == 128 128 128 + 129 129 === 2.2.1 Test Requirement === 130 130 131 131 ... ... @@ -141,6 +141,7 @@ 141 141 [[image:image-20220907171221-6.png]] 142 142 143 143 144 + 144 144 === 2.2.2 Insert SIM card === 145 145 146 146 ... ... @@ -152,6 +152,7 @@ 152 152 [[image:image-20220907171221-7.png]] 153 153 154 154 156 + 155 155 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 156 156 157 157 ... ... @@ -183,6 +183,7 @@ 183 183 (% 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]] 184 184 185 185 188 + 186 186 === 2.2.4 Use CoAP protocol to uplink data === 187 187 188 188 ... ... @@ -205,6 +205,7 @@ 205 205 [[image:image-20220907171221-10.png]] 206 206 207 207 211 + 208 208 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 209 209 210 210 ... ... @@ -221,6 +221,7 @@ 221 221 222 222 223 223 228 + 224 224 === 2.2.6 Use MQTT protocol to uplink data === 225 225 226 226 ... ... @@ -245,6 +245,7 @@ 245 245 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. 246 246 247 247 253 + 248 248 === 2.2.7 Use TCP protocol to uplink data === 249 249 250 250 ... ... @@ -272,6 +272,7 @@ 272 272 (% 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).** 273 273 274 274 281 + 275 275 == 2.3 Uplink Payload == 276 276 277 277 ... ... @@ -280,9 +280,9 @@ 280 280 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. 281 281 282 282 283 -(% border="1" style="background-color:#ffffcc; color:green; width: 520px" %)284 -| =(% scope="row" style="width:50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:60px" %)**1**|(% style="width:20px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:50px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**4**285 -| =(% style="width:;" %)**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 .....290 +(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 291 +|(% 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 292 +|(% 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 ..... 286 286 287 287 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 288 288 ... ... @@ -300,7 +300,7 @@ 300 300 301 301 * (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 302 302 303 -* (% style="color:#037691" %)**BAT:** 310 +* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 304 304 305 305 * (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 306 306 ... ... @@ -312,7 +312,7 @@ 312 312 313 313 * (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C 314 314 315 -* (% style="color:#037691" %)**Time stamp :** 322 +* (% style="color:#037691" %)**Time stamp :** (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 316 316 317 317 * (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp : **(%%)010b0226631550fb 318 318 ... ... @@ -322,6 +322,7 @@ 322 322 323 323 == 2.4 Payload Explanation and Sensor Interface == 324 324 332 + 325 325 === 2.4.1 Device ID === 326 326 327 327 ... ... @@ -337,6 +337,7 @@ 337 337 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 338 338 339 339 348 + 340 340 === 2.4.2 Version Info === 341 341 342 342 ... ... @@ -345,6 +345,7 @@ 345 345 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 346 346 347 347 357 + 348 348 === 2.4.3 Battery Info === 349 349 350 350 ... ... @@ -355,6 +355,7 @@ 355 355 Ex2: 0x0B49 = 2889mV 356 356 357 357 368 + 358 358 === 2.4.4 Signal Strength === 359 359 360 360 ... ... @@ -374,6 +374,7 @@ 374 374 **99** Not known or not detectable 375 375 376 376 388 + 377 377 === 2.4.5 Leaf moisture === 378 378 379 379 ... ... @@ -384,6 +384,7 @@ 384 384 (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 385 385 386 386 399 + 387 387 === 2.4.6 Leaf Temperature === 388 388 389 389 ... ... @@ -396,6 +396,7 @@ 396 396 If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 397 397 398 398 412 + 399 399 === 2.4.7 Timestamp === 400 400 401 401 ... ... @@ -404,6 +404,7 @@ 404 404 Convert Unix timestamp to time 2022-9-5 9:40:11. 405 405 406 406 421 + 407 407 === 2.4.8 Digital Interrupt === 408 408 409 409 ... ... @@ -422,6 +422,7 @@ 422 422 0x(01): Interrupt Uplink Packet. 423 423 424 424 440 + 425 425 === 2.4.9 +5V Output === 426 426 427 427 ... ... @@ -434,6 +434,7 @@ 434 434 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 435 435 436 436 453 + 437 437 == 2.5 Downlink Payload == 438 438 439 439 ... ... @@ -466,6 +466,7 @@ 466 466 Downlink Payload: 06000003, Set AT+INTMOD=3 467 467 468 468 486 + 469 469 == 2.6 LED Indicator == 470 470 471 471 ... ... @@ -476,8 +476,6 @@ 476 476 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 477 477 * For each uplink probe, LED will be on for 500ms. 478 478 479 - 480 - 481 481 == 2.7 Installation == 482 482 483 483 ... ... @@ -487,6 +487,7 @@ 487 487 [[image:image-20220907171221-19.png]] 488 488 489 489 506 + 490 490 == 2.8 Moisture and Temperature alarm function == 491 491 492 492 ... ... @@ -519,6 +519,7 @@ 519 519 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 520 520 521 521 539 + 522 522 == 2.9 Set the number of data to be uploaded and the recording time == 523 523 524 524 ... ... @@ -543,6 +543,7 @@ 543 543 [[image:image-20220907171221-20.png]] 544 544 545 545 564 + 546 546 == 2.11 Firmware Change Log == 547 547 548 548 ... ... @@ -551,14 +551,61 @@ 551 551 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 552 552 553 553 554 -== 2.12 Battery & Power Consumption == 555 555 574 +== 2.12 Battery Analysis == 556 556 557 -NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 558 558 559 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].577 +=== 2.12.1 Battery Type === 560 560 561 561 580 +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. 581 + 582 +The battery is designed to last for several years depends on the actually use environment and update interval. 583 + 584 +The battery related documents as below: 585 + 586 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 587 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 588 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 589 + 590 +[[image:image-20220907171221-21.png]] 591 + 592 + 593 + 594 +=== 2.12.2 Power consumption Analyze === 595 + 596 + 597 +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. 598 + 599 +Instruction to use as below: 600 + 601 +(% 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/]] 602 + 603 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 604 + 605 +* Product Model 606 +* Uplink Interval 607 +* Working Mode 608 + 609 +And the Life expectation in difference case will be shown on the right. 610 + 611 +[[image:image-20220907171221-22.jpeg]] 612 + 613 + 614 +=== 2.12.3 Battery Note === 615 + 616 + 617 +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. 618 + 619 + 620 + 621 +=== 2.12.4 Replace the battery === 622 + 623 + 624 +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). 625 + 626 + 627 + 562 562 = 3. Access NB-IoT Module = 563 563 564 564 ... ... @@ -570,8 +570,10 @@ 570 570 [[image:image-20220907171221-23.png]] 571 571 572 572 639 + 573 573 = 4. Using the AT Commands = 574 574 642 + 575 575 == 4.1 Access AT Commands == 576 576 577 577 ... ... @@ -659,8 +659,10 @@ 659 659 AT+PWORD : Serial Access Password 660 660 661 661 730 + 662 662 = 5. FAQ = 663 663 733 + 664 664 == 5.1 How to Upgrade Firmware == 665 665 666 666 ... ... @@ -672,8 +672,10 @@ 672 672 (% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 673 673 674 674 745 + 675 675 = 6. Trouble Shooting = 676 676 748 + 677 677 == 6.1 Connection problem when uploading firmware == 678 678 679 679 ... ... @@ -680,6 +680,7 @@ 680 680 **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]] 681 681 682 682 755 + 683 683 == 6.2 AT Command input doesn't work == 684 684 685 685 ... ... @@ -686,6 +686,7 @@ 686 686 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. 687 687 688 688 762 + 689 689 = 7. Order Info = 690 690 691 691 ... ... @@ -692,6 +692,7 @@ 692 692 Part Number**:** NLMS01 693 693 694 694 769 + 695 695 = 8. Packing Info = 696 696 697 697