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,6 +9,7 @@ 9 9 10 10 = 1. Introduction = 11 11 12 + 12 12 == 1.1 What is NLMS01 Leaf Moisture Sensor == 13 13 14 14 ... ... @@ -33,6 +33,7 @@ 33 33 [[image:image-20220907171221-3.png]] 34 34 35 35 37 + 36 36 == 1.2 Features == 37 37 38 38 ... ... @@ -66,14 +66,15 @@ 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 71 +* - B1 @H-FDD: 2100MHz 72 +* - B3 @H-FDD: 1800MHz 73 +* - B8 @H-FDD: 900MHz 74 +* - B5 @H-FDD: 850MHz 75 +* - B20 @H-FDD: 800MHz 76 +* - B28 @H-FDD: 700MHz 75 75 76 76 79 + 77 77 == 1.4 Probe Specification == 78 78 79 79 ... ... @@ -94,6 +94,7 @@ 94 94 * Length: 3.5 meters 95 95 96 96 100 + 97 97 == 1.5 Applications == 98 98 99 99 ... ... @@ -100,6 +100,7 @@ 100 100 * Smart Agriculture 101 101 102 102 107 + 103 103 == 1.6 Pin mapping and power on == 104 104 105 105 ... ... @@ -107,8 +107,10 @@ 107 107 108 108 **~ ** 109 109 115 + 110 110 = 2. Use NLMS01 to communicate with IoT Server = 111 111 118 + 112 112 == 2.1 How it works == 113 113 114 114 ... ... @@ -120,8 +120,10 @@ 120 120 [[image:image-20220907171221-5.png]] 121 121 122 122 130 + 123 123 == 2.2 Configure the NLMS01 == 124 124 133 + 125 125 === 2.2.1 Test Requirement === 126 126 127 127 ... ... @@ -137,6 +137,7 @@ 137 137 [[image:image-20220907171221-6.png]] 138 138 139 139 149 + 140 140 === 2.2.2 Insert SIM card === 141 141 142 142 ... ... @@ -148,6 +148,7 @@ 148 148 [[image:image-20220907171221-7.png]] 149 149 150 150 161 + 151 151 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 152 152 153 153 ... ... @@ -179,6 +179,7 @@ 179 179 (% 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]] 180 180 181 181 193 + 182 182 === 2.2.4 Use CoAP protocol to uplink data === 183 183 184 184 ... ... @@ -201,6 +201,7 @@ 201 201 [[image:image-20220907171221-10.png]] 202 202 203 203 216 + 204 204 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 205 205 206 206 ... ... @@ -217,6 +217,7 @@ 217 217 218 218 219 219 233 + 220 220 === 2.2.6 Use MQTT protocol to uplink data === 221 221 222 222 ... ... @@ -241,6 +241,7 @@ 241 241 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. 242 242 243 243 258 + 244 244 === 2.2.7 Use TCP protocol to uplink data === 245 245 246 246 ... ... @@ -268,6 +268,7 @@ 268 268 (% 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).** 269 269 270 270 286 + 271 271 == 2.3 Uplink Payload == 272 272 273 273 ... ... @@ -276,9 +276,9 @@ 276 276 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. 277 277 278 278 279 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:520px" %)280 -|(% style="width:50px; background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**4**281 -|(% 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:520px" %) 296 +|=(% 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** 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 ..... 282 282 283 283 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 284 284 ... ... @@ -316,6 +316,7 @@ 316 316 317 317 == 2.4 Payload Explanation and Sensor Interface == 318 318 335 + 319 319 === 2.4.1 Device ID === 320 320 321 321 ... ... @@ -331,6 +331,7 @@ 331 331 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 332 332 333 333 351 + 334 334 === 2.4.2 Version Info === 335 335 336 336 ... ... @@ -339,6 +339,7 @@ 339 339 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 340 340 341 341 360 + 342 342 === 2.4.3 Battery Info === 343 343 344 344 ... ... @@ -349,6 +349,7 @@ 349 349 Ex2: 0x0B49 = 2889mV 350 350 351 351 371 + 352 352 === 2.4.4 Signal Strength === 353 353 354 354 ... ... @@ -368,6 +368,7 @@ 368 368 **99** Not known or not detectable 369 369 370 370 391 + 371 371 === 2.4.5 Leaf moisture === 372 372 373 373 ... ... @@ -378,6 +378,7 @@ 378 378 (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 379 379 380 380 402 + 381 381 === 2.4.6 Leaf Temperature === 382 382 383 383 ... ... @@ -390,6 +390,7 @@ 390 390 If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 391 391 392 392 415 + 393 393 === 2.4.7 Timestamp === 394 394 395 395 ... ... @@ -398,6 +398,7 @@ 398 398 Convert Unix timestamp to time 2022-9-5 9:40:11. 399 399 400 400 424 + 401 401 === 2.4.8 Digital Interrupt === 402 402 403 403 ... ... @@ -416,6 +416,7 @@ 416 416 0x(01): Interrupt Uplink Packet. 417 417 418 418 443 + 419 419 === 2.4.9 +5V Output === 420 420 421 421 ... ... @@ -428,6 +428,7 @@ 428 428 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 429 429 430 430 456 + 431 431 == 2.5 Downlink Payload == 432 432 433 433 ... ... @@ -460,6 +460,7 @@ 460 460 Downlink Payload: 06000003, Set AT+INTMOD=3 461 461 462 462 489 + 463 463 == 2.6 LED Indicator == 464 464 465 465 ... ... @@ -479,6 +479,7 @@ 479 479 [[image:image-20220907171221-19.png]] 480 480 481 481 509 + 482 482 == 2.8 Moisture and Temperature alarm function == 483 483 484 484 ... ... @@ -511,6 +511,7 @@ 511 511 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 512 512 513 513 542 + 514 514 == 2.9 Set the number of data to be uploaded and the recording time == 515 515 516 516 ... ... @@ -535,6 +535,7 @@ 535 535 [[image:image-20220907171221-20.png]] 536 536 537 537 567 + 538 538 == 2.11 Firmware Change Log == 539 539 540 540 ... ... @@ -543,14 +543,61 @@ 543 543 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 544 544 545 545 546 -== 2.12 Battery & Power Consumption == 547 547 577 +== 2.12 Battery Analysis == 548 548 549 -NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 550 550 551 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].580 +=== 2.12.1 Battery Type === 552 552 553 553 583 +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. 584 + 585 +The battery is designed to last for several years depends on the actually use environment and update interval. 586 + 587 +The battery related documents as below: 588 + 589 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 590 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 591 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 592 + 593 +[[image:image-20220907171221-21.png]] 594 + 595 + 596 + 597 +=== 2.12.2 Power consumption Analyze === 598 + 599 + 600 +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. 601 + 602 +Instruction to use as below: 603 + 604 +(% 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/]] 605 + 606 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 607 + 608 +* Product Model 609 +* Uplink Interval 610 +* Working Mode 611 + 612 +And the Life expectation in difference case will be shown on the right. 613 + 614 +[[image:image-20220907171221-22.jpeg]] 615 + 616 + 617 +=== 2.12.3 Battery Note === 618 + 619 + 620 +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. 621 + 622 + 623 + 624 +=== 2.12.4 Replace the battery === 625 + 626 + 627 +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). 628 + 629 + 630 + 554 554 = 3. Access NB-IoT Module = 555 555 556 556 ... ... @@ -562,8 +562,10 @@ 562 562 [[image:image-20220907171221-23.png]] 563 563 564 564 642 + 565 565 = 4. Using the AT Commands = 566 566 645 + 567 567 == 4.1 Access AT Commands == 568 568 569 569 ... ... @@ -651,8 +651,10 @@ 651 651 AT+PWORD : Serial Access Password 652 652 653 653 733 + 654 654 = 5. FAQ = 655 655 736 + 656 656 == 5.1 How to Upgrade Firmware == 657 657 658 658 ... ... @@ -664,8 +664,10 @@ 664 664 (% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 665 665 666 666 748 + 667 667 = 6. Trouble Shooting = 668 668 751 + 669 669 == 6.1 Connection problem when uploading firmware == 670 670 671 671 ... ... @@ -672,6 +672,7 @@ 672 672 **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]] 673 673 674 674 758 + 675 675 == 6.2 AT Command input doesn't work == 676 676 677 677 ... ... @@ -678,12 +678,7 @@ 678 678 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. 679 679 680 680 681 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 682 682 683 - 684 -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]]//**. 685 - 686 - 687 687 = 7. Order Info = 688 688 689 689 ... ... @@ -690,6 +690,7 @@ 690 690 Part Number**:** NLMS01 691 691 692 692 772 + 693 693 = 8. Packing Info = 694 694 695 695 ... ... @@ -704,6 +704,8 @@ 704 704 * Package Size / pcs : cm 705 705 * Weight / pcs : g 706 706 787 + 788 + 707 707 = 9. Support = 708 708 709 709