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,12 +66,12 @@ 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 76 77 77 ... ... @@ -110,8 +110,10 @@ 110 110 111 111 **~ ** 112 112 111 + 113 113 = 2. Use NLMS01 to communicate with IoT Server = 114 114 114 + 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 126 + 126 126 == 2.2 Configure the NLMS01 == 127 127 129 + 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 145 + 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 157 + 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 189 + 185 185 === 2.2.4 Use CoAP protocol to uplink data === 186 186 187 187 ... ... @@ -204,6 +204,7 @@ 204 204 [[image:image-20220907171221-10.png]] 205 205 206 206 212 + 207 207 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 208 208 209 209 ... ... @@ -220,6 +220,7 @@ 220 220 221 221 222 222 229 + 223 223 === 2.2.6 Use MQTT protocol to uplink data === 224 224 225 225 ... ... @@ -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 ... ... @@ -271,6 +271,7 @@ 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 282 + 274 274 == 2.3 Uplink Payload == 275 275 276 276 ... ... @@ -279,9 +279,9 @@ 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 ..... 291 +(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 292 +|(% 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 293 +|(% 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 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 ... ... @@ -295,32 +295,23 @@ 295 295 296 296 where: 297 297 298 -* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 307 +* Device ID: 0xf868411056754138 = f868411056754138 308 +* Version: 0x0064=100=1.0.0 309 +* BAT: 0x0c78 = 3192 mV = 3.192V 310 +* Singal: 0x17 = 23 311 +* Mod: 0x01 = 1 312 +* Interrupt: 0x00= 0 313 +* Leaf moisture: 0x0225= 549 = 54.9% 314 +* Leaf Temperature:0x010B =267=26.7 °C 315 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 316 +* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 317 +* 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 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 - 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 323 + 324 324 === 2.4.1 Device ID === 325 325 326 326 ... ... @@ -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 339 + 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 348 + 347 347 === 2.4.3 Battery Info === 348 348 349 349 ... ... @@ -354,6 +354,7 @@ 354 354 Ex2: 0x0B49 = 2889mV 355 355 356 356 359 + 357 357 === 2.4.4 Signal Strength === 358 358 359 359 ... ... @@ -373,6 +373,7 @@ 373 373 **99** Not known or not detectable 374 374 375 375 379 + 376 376 === 2.4.5 Leaf moisture === 377 377 378 378 ... ... @@ -383,6 +383,7 @@ 383 383 (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 384 384 385 385 390 + 386 386 === 2.4.6 Leaf Temperature === 387 387 388 388 ... ... @@ -395,6 +395,7 @@ 395 395 If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 396 396 397 397 403 + 398 398 === 2.4.7 Timestamp === 399 399 400 400 ... ... @@ -403,6 +403,7 @@ 403 403 Convert Unix timestamp to time 2022-9-5 9:40:11. 404 404 405 405 412 + 406 406 === 2.4.8 Digital Interrupt === 407 407 408 408 ... ... @@ -421,6 +421,7 @@ 421 421 0x(01): Interrupt Uplink Packet. 422 422 423 423 431 + 424 424 === 2.4.9 +5V Output === 425 425 426 426 ... ... @@ -433,18 +433,14 @@ 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 444 + 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 450 +[[image:image-20220907171221-18.png]] 446 446 447 - 448 448 449 449 (% style="color:blue" %)**Examples:** 450 450 ... ... @@ -470,6 +470,7 @@ 470 470 Downlink Payload: 06000003, Set AT+INTMOD=3 471 471 472 472 477 + 473 473 == 2.6 LED Indicator == 474 474 475 475 ... ... @@ -491,6 +491,7 @@ 491 491 [[image:image-20220907171221-19.png]] 492 492 493 493 499 + 494 494 == 2.8 Moisture and Temperature alarm function == 495 495 496 496 ... ... @@ -523,6 +523,7 @@ 523 523 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 524 524 525 525 532 + 526 526 == 2.9 Set the number of data to be uploaded and the recording time == 527 527 528 528 ... ... @@ -531,11 +531,8 @@ 531 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 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. 533 533 534 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 535 535 536 -[[image:image-20221009001002-1.png||height="706" width="982"]] 537 537 538 - 539 539 == 2.10 Read or Clear cached data == 540 540 541 541 ... ... @@ -547,6 +547,7 @@ 547 547 [[image:image-20220907171221-20.png]] 548 548 549 549 554 + 550 550 == 2.11 Firmware Change Log == 551 551 552 552 ... ... @@ -555,14 +555,61 @@ 555 555 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 556 556 557 557 558 -== 2.12 Battery & Power Consumption == 559 559 564 +== 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/]].567 +=== 2.12.1 Battery Type === 564 564 565 565 570 +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. 571 + 572 +The battery is designed to last for several years depends on the actually use environment and update interval. 573 + 574 +The battery related documents as below: 575 + 576 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 577 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 578 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 579 + 580 +[[image:image-20220907171221-21.png]] 581 + 582 + 583 + 584 +=== 2.12.2 Power consumption Analyze === 585 + 586 + 587 +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. 588 + 589 +Instruction to use as below: 590 + 591 +(% 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/]] 592 + 593 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 594 + 595 +* Product Model 596 +* Uplink Interval 597 +* Working Mode 598 + 599 +And the Life expectation in difference case will be shown on the right. 600 + 601 +[[image:image-20220907171221-22.jpeg]] 602 + 603 + 604 +=== 2.12.3 Battery Note === 605 + 606 + 607 +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. 608 + 609 + 610 + 611 +=== 2.12.4 Replace the battery === 612 + 613 + 614 +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). 615 + 616 + 617 + 566 566 = 3. Access NB-IoT Module = 567 567 568 568 ... ... @@ -574,8 +574,10 @@ 574 574 [[image:image-20220907171221-23.png]] 575 575 576 576 629 + 577 577 = 4. Using the AT Commands = 578 578 632 + 579 579 == 4.1 Access AT Commands == 580 580 581 581 ... ... @@ -635,36 +635,38 @@ 635 635 636 636 (% style="color:#037691" %)**COAP Management** 637 637 638 -AT+URI : 692 +AT+URI : Resource parameters 639 639 640 640 641 641 (% style="color:#037691" %)**UDP Management** 642 642 643 -AT+CFM : 697 +AT+CFM : Upload confirmation mode (only valid for UDP) 644 644 645 645 646 646 (% style="color:#037691" %)**MQTT Management** 647 647 648 -AT+CLIENT : 702 +AT+CLIENT : Get or Set MQTT client 649 649 650 -AT+UNAME : Get or Set MQTT Username 704 +AT+UNAME : Get or Set MQTT Username 651 651 652 -AT+PWD 706 +AT+PWD : Get or Set MQTT password 653 653 654 -AT+PUBTOPIC :Get or Set MQTT publish topic708 +AT+PUBTOPIC : Get or Set MQTT publish topic 655 655 656 -AT+SUBTOPIC :Get or Set MQTT subscription topic710 +AT+SUBTOPIC : Get or Set MQTT subscription topic 657 657 658 658 659 659 (% style="color:#037691" %)**Information** 660 660 661 -AT+FDR :Factory Data Reset715 +AT+FDR : Factory Data Reset 662 662 663 -AT+PWORD :Serial Access Password717 +AT+PWORD : Serial Access Password 664 664 665 665 720 + 666 666 = 5. FAQ = 667 667 723 + 668 668 == 5.1 How to Upgrade Firmware == 669 669 670 670 ... ... @@ -676,8 +676,10 @@ 676 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 735 + 679 679 = 6. Trouble Shooting = 680 680 738 + 681 681 == 6.1 Connection problem when uploading firmware == 682 682 683 683 ... ... @@ -684,6 +684,7 @@ 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 745 + 687 687 == 6.2 AT Command input doesn't work == 688 688 689 689 ... ... @@ -690,12 +690,7 @@ 690 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. 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,6 +702,7 @@ 702 702 Part Number**:** NLMS01 703 703 704 704 759 + 705 705 = 8. Packing Info = 706 706 707 707 ... ... @@ -717,7 +717,6 @@ 717 717 * Weight / pcs : g 718 718 719 719 720 - 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