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
-
... ... @@ -9,23 +9,21 @@ 9 9 10 10 = 1. Introduction = 11 11 12 - 13 13 == 1.1 What is NLMS01 Leaf Moisture Sensor == 14 14 15 15 16 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 -))) 19 19 20 -((( 21 21 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. 22 -))) 23 23 24 -((( 25 25 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. 26 -\\NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 27 -\\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). 28 -\\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 + 22 +NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 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. 29 29 ))) 30 30 31 31 ... ... @@ -35,7 +35,6 @@ 35 35 [[image:image-20220907171221-3.png]] 36 36 37 37 38 - 39 39 == 1.2 Features == 40 40 41 41 ... ... @@ -69,12 +69,12 @@ 69 69 70 70 (% style="color:#037691" %)**NB-IoT Spec:** 71 71 72 -* -B1 @H-FDD: 2100MHz73 -* -B3 @H-FDD: 1800MHz74 -* -B8 @H-FDD: 900MHz75 -* -B5 @H-FDD: 850MHz76 -* -B20 @H-FDD: 800MHz77 -* -B28 @H-FDD: 700MHz69 +* 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 78 78 79 79 == 1.4 Probe Specification == 80 80 ... ... @@ -107,10 +107,8 @@ 107 107 108 108 **~ ** 109 109 110 - 111 111 = 2. Use NLMS01 to communicate with IoT Server = 112 112 113 - 114 114 == 2.1 How it works == 115 115 116 116 ... ... @@ -122,10 +122,8 @@ 122 122 [[image:image-20220907171221-5.png]] 123 123 124 124 125 - 126 126 == 2.2 Configure the NLMS01 == 127 127 128 - 129 129 === 2.2.1 Test Requirement === 130 130 131 131 ... ... @@ -141,7 +141,6 @@ 141 141 [[image:image-20220907171221-6.png]] 142 142 143 143 144 - 145 145 === 2.2.2 Insert SIM card === 146 146 147 147 ... ... @@ -153,7 +153,6 @@ 153 153 [[image:image-20220907171221-7.png]] 154 154 155 155 156 - 157 157 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 158 158 159 159 ... ... @@ -185,7 +185,6 @@ 185 185 (% 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]] 186 186 187 187 188 - 189 189 === 2.2.4 Use CoAP protocol to uplink data === 190 190 191 191 ... ... @@ -208,7 +208,6 @@ 208 208 [[image:image-20220907171221-10.png]] 209 209 210 210 211 - 212 212 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 213 213 214 214 ... ... @@ -225,7 +225,6 @@ 225 225 226 226 227 227 228 - 229 229 === 2.2.6 Use MQTT protocol to uplink data === 230 230 231 231 ... ... @@ -250,7 +250,6 @@ 250 250 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. 251 251 252 252 253 - 254 254 === 2.2.7 Use TCP protocol to uplink data === 255 255 256 256 ... ... @@ -278,7 +278,6 @@ 278 278 (% 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).** 279 279 280 280 281 - 282 282 == 2.3 Uplink Payload == 283 283 284 284 ... ... @@ -287,9 +287,9 @@ 287 287 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. 288 288 289 289 290 -(% border="1" style="background-color:#fff fcc;color:green;width:520px" %)291 -|(% style="width: 45px" %)**Size(bytes)**|(% style="width:45px" %)**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" %)4292 -|(% 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 .....276 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:520px" %) 277 +|(% 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** 278 +|(% 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 ..... 293 293 294 294 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 295 295 ... ... @@ -327,7 +327,6 @@ 327 327 328 328 == 2.4 Payload Explanation and Sensor Interface == 329 329 330 - 331 331 === 2.4.1 Device ID === 332 332 333 333 ... ... @@ -343,7 +343,6 @@ 343 343 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 344 344 345 345 346 - 347 347 === 2.4.2 Version Info === 348 348 349 349 ... ... @@ -352,7 +352,6 @@ 352 352 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 353 353 354 354 355 - 356 356 === 2.4.3 Battery Info === 357 357 358 358 ... ... @@ -363,7 +363,6 @@ 363 363 Ex2: 0x0B49 = 2889mV 364 364 365 365 366 - 367 367 === 2.4.4 Signal Strength === 368 368 369 369 ... ... @@ -383,7 +383,6 @@ 383 383 **99** Not known or not detectable 384 384 385 385 386 - 387 387 === 2.4.5 Leaf moisture === 388 388 389 389 ... ... @@ -394,7 +394,6 @@ 394 394 (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 395 395 396 396 397 - 398 398 === 2.4.6 Leaf Temperature === 399 399 400 400 ... ... @@ -407,7 +407,6 @@ 407 407 If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 408 408 409 409 410 - 411 411 === 2.4.7 Timestamp === 412 412 413 413 ... ... @@ -416,7 +416,6 @@ 416 416 Convert Unix timestamp to time 2022-9-5 9:40:11. 417 417 418 418 419 - 420 420 === 2.4.8 Digital Interrupt === 421 421 422 422 ... ... @@ -435,7 +435,6 @@ 435 435 0x(01): Interrupt Uplink Packet. 436 436 437 437 438 - 439 439 === 2.4.9 +5V Output === 440 440 441 441 ... ... @@ -448,14 +448,18 @@ 448 448 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 449 449 450 450 451 - 452 452 == 2.5 Downlink Payload == 453 453 454 454 455 455 By default, NLMS01 prints the downlink payload to console port. 456 456 457 -[[image:image-20220907171221-18.png]] 433 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:479.818px" %) 434 +|=(% 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)** 435 +|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4 436 +|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2 437 +|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4 458 458 439 + 459 459 460 460 (% style="color:blue" %)**Examples:** 461 461 ... ... @@ -481,7 +481,6 @@ 481 481 Downlink Payload: 06000003, Set AT+INTMOD=3 482 482 483 483 484 - 485 485 == 2.6 LED Indicator == 486 486 487 487 ... ... @@ -501,7 +501,6 @@ 501 501 [[image:image-20220907171221-19.png]] 502 502 503 503 504 - 505 505 == 2.8 Moisture and Temperature alarm function == 506 506 507 507 ... ... @@ -534,7 +534,6 @@ 534 534 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 535 535 536 536 537 - 538 538 == 2.9 Set the number of data to be uploaded and the recording time == 539 539 540 540 ... ... @@ -559,7 +559,6 @@ 559 559 [[image:image-20220907171221-20.png]] 560 560 561 561 562 - 563 563 == 2.11 Firmware Change Log == 564 564 565 565 ... ... @@ -568,61 +568,14 @@ 568 568 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 569 569 570 570 548 +== 2.12 Battery & Power Consumption == 571 571 572 -== 2.12 Battery Analysis == 573 573 551 +NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 574 574 575 - === 2.12.1 BatteryType===553 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 576 576 577 577 578 -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. 579 - 580 -The battery is designed to last for several years depends on the actually use environment and update interval. 581 - 582 -The battery related documents as below: 583 - 584 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 585 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 586 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 587 - 588 -[[image:image-20220907171221-21.png]] 589 - 590 - 591 - 592 -=== 2.12.2 Power consumption Analyze === 593 - 594 - 595 -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. 596 - 597 -Instruction to use as below: 598 - 599 -(% 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/]] 600 - 601 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 602 - 603 -* Product Model 604 -* Uplink Interval 605 -* Working Mode 606 - 607 -And the Life expectation in difference case will be shown on the right. 608 - 609 -[[image:image-20220907171221-22.jpeg]] 610 - 611 - 612 -=== 2.12.3 Battery Note === 613 - 614 - 615 -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. 616 - 617 - 618 - 619 -=== 2.12.4 Replace the battery === 620 - 621 - 622 -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). 623 - 624 - 625 - 626 626 = 3. Access NB-IoT Module = 627 627 628 628 ... ... @@ -634,10 +634,8 @@ 634 634 [[image:image-20220907171221-23.png]] 635 635 636 636 637 - 638 638 = 4. Using the AT Commands = 639 639 640 - 641 641 == 4.1 Access AT Commands == 642 642 643 643 ... ... @@ -725,10 +725,8 @@ 725 725 AT+PWORD : Serial Access Password 726 726 727 727 728 - 729 729 = 5. FAQ = 730 730 731 - 732 732 == 5.1 How to Upgrade Firmware == 733 733 734 734 ... ... @@ -740,10 +740,8 @@ 740 740 (% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 741 741 742 742 743 - 744 744 = 6. Trouble Shooting = 745 745 746 - 747 747 == 6.1 Connection problem when uploading firmware == 748 748 749 749 ... ... @@ -750,7 +750,6 @@ 750 750 **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]] 751 751 752 752 753 - 754 754 == 6.2 AT Command input doesn't work == 755 755 756 756 ... ... @@ -757,7 +757,12 @@ 757 757 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. 758 758 759 759 683 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 760 760 685 + 686 +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]]//**. 687 + 688 + 761 761 = 7. Order Info = 762 762 763 763 ... ... @@ -764,7 +764,6 @@ 764 764 Part Number**:** NLMS01 765 765 766 766 767 - 768 768 = 8. Packing Info = 769 769 770 770