Changes for page LDDS45 - LoRaWAN Distance Detection Sensor User Manual
Last modified by Mengting Qiu on 2025/02/26 15:04
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -67,6 +67,7 @@ 67 67 68 68 69 69 70 + 70 70 = 1. Introduction = 71 71 72 72 == 1.1 What is LoRaWAN Soil pH Sensor == ... ... @@ -113,6 +113,7 @@ 113 113 * 8500mAh Battery for long term use 114 114 115 115 117 + 116 116 == 1.3 Probe Specification == 117 117 118 118 ... ... @@ -134,11 +134,13 @@ 134 134 * Length: 3.5 meters 135 135 136 136 139 + 137 137 == 1.4 Applications == 138 138 139 139 * Smart Agriculture 140 140 141 141 145 + 142 142 == 1.5 Pin mapping and power on == 143 143 144 144 [[image:1654592472094-134.png]] ... ... @@ -217,9 +217,7 @@ 217 217 [[image:image-20220607170442-2.png]] 218 218 219 219 220 -((( 221 221 (% style="color:blue" %)**Step 3**(%%)**:** The LSPH01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel. 222 -))) 223 223 224 224 [[image:1654592697690-910.png]] 225 225 ... ... @@ -227,17 +227,11 @@ 227 227 228 228 == 2.3 Uplink Payload == 229 229 230 -((( 231 231 LSPH01 will uplink payload via LoRaWAN with below payload format: 232 -))) 233 233 234 -((( 235 235 Uplink payload includes in total 11 bytes. 236 -))) 237 237 238 -((( 239 239 Normal uplink payload: 240 -))) 241 241 242 242 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 243 243 |((( ... ... @@ -321,17 +321,13 @@ 321 321 322 322 === 2.3.6 Message Type === 323 323 324 -((( 325 325 For a normal uplink payload, the message type is always 0x01. 326 -))) 327 327 328 -((( 329 329 Valid Message Type: 330 -))) 331 331 332 332 333 333 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 334 -| =**Message Type Code**|=**Description**|=**Payload**326 +|**Message Type Code**|**Description**|**Payload** 335 335 |0x01|Normal Uplink|[[Normal Uplink Payload>>path:#H2.3200BUplinkPayload]] 336 336 |0x02|Reply configures info|[[Configure Info Payload>>path:#H3.4GetFirmwareVersionInfo]] 337 337 |0x03|Reply Calibration Info|[[Calibration Payload>>path:#H2.7Calibration]] ... ... @@ -338,6 +338,7 @@ 338 338 339 339 340 340 333 + 341 341 === 2.3.7 Decode payload in The Things Network === 342 342 343 343 While using TTN network, you can add the payload format to decode the payload. ... ... @@ -363,21 +363,12 @@ 363 363 364 364 == 2.5 Show Data in DataCake IoT Server == 365 365 366 -((( 367 367 [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps: 368 -))) 369 369 370 -((( 371 - 372 -))) 373 373 374 -((( 375 375 (% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.** 376 -))) 377 377 378 -((( 379 379 (% style="color:blue" %)**Step 2**(%%)**: To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:** 380 -))) 381 381 382 382 383 383 [[image:1654592790040-760.png]] ... ... @@ -400,13 +400,9 @@ 400 400 [[image:1654592856403-259.png]] 401 401 402 402 403 -((( 404 404 (% style="color:blue" %)**Step 5**(%%)**: add payload decode** 405 -))) 406 406 407 -((( 408 408 Download Datacake decoder from: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]] 409 -))) 410 410 411 411 412 412 [[image:1654592878525-845.png]] ... ... @@ -429,10 +429,8 @@ 429 429 === 2.6.1 Before measurement === 430 430 431 431 ((( 432 -((( 433 433 If the LSPH01 has more than 7 days not use or just clean the pH probe. User should put the probe inside pure water for more than 24 hours for activation. If no put in water, user need to put inside soil for more than 24 hours to ensure the measurement accuracy. 434 434 ))) 435 -))) 436 436 437 437 438 438 ... ... @@ -439,45 +439,24 @@ 439 439 === 2.6.2 Measurement === 440 440 441 441 442 -((( 443 443 (% style="color:#4f81bd" %)**Measurement the soil surface:** 444 -))) 445 445 446 -((( 447 447 [[image:1654592946732-634.png]] 448 -))) 449 449 450 -((( 451 451 Choose the proper measuring position. Split the surface soil according to the measured deep. 452 -))) 453 453 454 -((( 455 455 Put pure water, or rainwater to make the soil of measurement point to moist mud. Remove rocks or hard things. 456 -))) 457 457 458 -((( 459 459 Slowly insert the probe to the measure point. Don’t use large force which will break the probe. Make sure not shake when inserting. 460 -))) 461 461 462 -((( 463 463 Put soil over the probe after insert. And start to measure. 464 -))) 465 465 466 -((( 467 - 468 -))) 469 469 470 -((( 471 471 (% style="color:#4f81bd" %)**Measurement inside soil:** 472 -))) 473 473 474 -((( 475 475 Dig a hole with diameter > 20CM. 476 -))) 477 477 478 -((( 479 479 Insert the probe inside, method like measure the surface. 480 -))) 481 481 482 482 483 483 ... ... @@ -507,13 +507,9 @@ 507 507 508 508 == 2.7 Calibration == 509 509 510 -((( 511 511 User can do calibration for the probe. It is limited to use below pH buffer solution to calibrate: 4.00, 6.86, 9.18. When calibration, user need to clean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode might need max 24 hours to be stable). 512 -))) 513 513 514 -((( 515 515 After stable, user can use below command to calibrate. 516 -))) 517 517 518 518 [[image:image-20220607171149-4.png]] 519 519 ... ... @@ -520,7 +520,7 @@ 520 520 521 521 (% style="color:#037691" %)**Calibration Payload** 522 522 523 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green;width:510px" %)476 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 524 524 |((( 525 525 **Size** 526 526 ... ... @@ -550,6 +550,7 @@ 550 550 551 551 552 552 506 + 553 553 == 2.8 Frequency Plans == 554 554 555 555 ((( ... ... @@ -559,61 +559,32 @@ 559 559 560 560 === 2.8.1 EU863-870 (EU868) === 561 561 562 -((( 563 563 (% style="color:blue" %)**Uplink:** 564 -))) 565 565 566 -((( 567 567 868.1 - SF7BW125 to SF12BW125 568 -))) 569 569 570 -((( 571 571 868.3 - SF7BW125 to SF12BW125 and SF7BW250 572 -))) 573 573 574 -((( 575 575 868.5 - SF7BW125 to SF12BW125 576 -))) 577 577 578 -((( 579 579 867.1 - SF7BW125 to SF12BW125 580 -))) 581 581 582 -((( 583 583 867.3 - SF7BW125 to SF12BW125 584 -))) 585 585 586 -((( 587 587 867.5 - SF7BW125 to SF12BW125 588 -))) 589 589 590 -((( 591 591 867.7 - SF7BW125 to SF12BW125 592 -))) 593 593 594 -((( 595 595 867.9 - SF7BW125 to SF12BW125 596 -))) 597 597 598 -((( 599 599 868.8 - FSK 600 -))) 601 601 602 -((( 603 - 604 -))) 605 605 606 -((( 607 607 (% style="color:blue" %)**Downlink:** 608 -))) 609 609 610 -((( 611 611 Uplink channels 1-9 (RX1) 612 -))) 613 613 614 -((( 615 615 869.525 - SF9BW125 (RX2 downlink only) 616 -))) 617 617 618 618 619 619 ... ... @@ -635,93 +635,48 @@ 635 635 * Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) 636 636 637 637 638 - 639 - 640 640 === 2.8.3 CN470-510 (CN470) === 641 641 642 -((( 643 643 Used in China, Default use CHE=1 644 -))) 645 645 646 -((( 647 647 (% style="color:blue" %)**Uplink:** 648 -))) 649 649 650 -((( 651 651 486.3 - SF7BW125 to SF12BW125 652 -))) 653 653 654 -((( 655 655 486.5 - SF7BW125 to SF12BW125 656 -))) 657 657 658 -((( 659 659 486.7 - SF7BW125 to SF12BW125 660 -))) 661 661 662 -((( 663 663 486.9 - SF7BW125 to SF12BW125 664 -))) 665 665 666 -((( 667 667 487.1 - SF7BW125 to SF12BW125 668 -))) 669 669 670 -((( 671 671 487.3 - SF7BW125 to SF12BW125 672 -))) 673 673 674 -((( 675 675 487.5 - SF7BW125 to SF12BW125 676 -))) 677 677 678 -((( 679 679 487.7 - SF7BW125 to SF12BW125 680 -))) 681 681 682 -((( 683 - 684 -))) 685 685 686 -((( 687 687 (% style="color:blue" %)**Downlink:** 688 -))) 689 689 690 -((( 691 691 506.7 - SF7BW125 to SF12BW125 692 -))) 693 693 694 -((( 695 695 506.9 - SF7BW125 to SF12BW125 696 -))) 697 697 698 -((( 699 699 507.1 - SF7BW125 to SF12BW125 700 -))) 701 701 702 -((( 703 703 507.3 - SF7BW125 to SF12BW125 704 -))) 705 705 706 -((( 707 707 507.5 - SF7BW125 to SF12BW125 708 -))) 709 709 710 -((( 711 711 507.7 - SF7BW125 to SF12BW125 712 -))) 713 713 714 -((( 715 715 507.9 - SF7BW125 to SF12BW125 716 -))) 717 717 718 -((( 719 719 508.1 - SF7BW125 to SF12BW125 720 -))) 721 721 722 -((( 723 723 505.3 - SF12BW125 (RX2 downlink only) 724 -))) 725 725 726 726 727 727 ... ... @@ -747,111 +747,56 @@ 747 747 * Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) 748 748 749 749 630 + 750 750 === 2.8.5 AS920-923 & AS923-925 (AS923) === 751 751 752 -((( 753 753 (% style="color:blue" %)**Default Uplink channel:** 754 -))) 755 755 756 -((( 757 757 923.2 - SF7BW125 to SF10BW125 758 -))) 759 759 760 -((( 761 761 923.4 - SF7BW125 to SF10BW125 762 -))) 763 763 764 -((( 765 - 766 -))) 767 767 768 -((( 769 769 (% style="color:blue" %)**Additional Uplink Channel**: 770 -))) 771 771 772 -((( 773 773 (OTAA mode, channel added by JoinAccept message) 774 -))) 775 775 776 -((( 777 - 778 -))) 779 779 780 -((( 781 781 (% style="color:blue" %)**AS920~~AS923 for Japan, Malaysia, Singapore**: 782 -))) 783 783 784 -((( 785 785 922.2 - SF7BW125 to SF10BW125 786 -))) 787 787 788 -((( 789 789 922.4 - SF7BW125 to SF10BW125 790 -))) 791 791 792 -((( 793 793 922.6 - SF7BW125 to SF10BW125 794 -))) 795 795 796 -((( 797 797 922.8 - SF7BW125 to SF10BW125 798 -))) 799 799 800 -((( 801 801 923.0 - SF7BW125 to SF10BW125 802 -))) 803 803 804 -((( 805 805 922.0 - SF7BW125 to SF10BW125 806 -))) 807 807 808 -((( 809 - 810 -))) 811 811 812 -((( 813 813 (% style="color:blue" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**: 814 -))) 815 815 816 -((( 817 817 923.6 - SF7BW125 to SF10BW125 818 -))) 819 819 820 -((( 821 821 923.8 - SF7BW125 to SF10BW125 822 -))) 823 823 824 -((( 825 825 924.0 - SF7BW125 to SF10BW125 826 -))) 827 827 828 -((( 829 829 924.2 - SF7BW125 to SF10BW125 830 -))) 831 831 832 -((( 833 833 924.4 - SF7BW125 to SF10BW125 834 -))) 835 835 836 -((( 837 837 924.6 - SF7BW125 to SF10BW125 838 -))) 839 839 840 -((( 841 - 842 -))) 843 843 844 -((( 845 845 (% style="color:blue" %)**Downlink:** 846 -))) 847 847 848 -((( 849 849 Uplink channels 1-8 (RX1) 850 -))) 851 851 852 -((( 853 853 923.2 - SF10BW125 (RX2) 854 -))) 855 855 856 856 857 857 ... ... @@ -918,6 +918,7 @@ 918 918 * Blink once when device transmit a packet. 919 919 920 920 746 + 921 921 == 2.10 Firmware Change Log == 922 922 923 923 ... ... @@ -976,6 +976,7 @@ 976 976 977 977 978 978 805 + 979 979 == 3.2 Set Interrupt Mode == 980 980 981 981 Feature, Set Interrupt mode for GPIO_EXIT. ... ... @@ -994,6 +994,7 @@ 994 994 * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode 995 995 * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger 996 996 824 + 997 997 == 3.3 Calibrate Sensor == 998 998 999 999 Detail See [[Calibration Guide>>path:#H2.7Calibration]] for the user of 0x13 and 0x14 downlink commands ... ... @@ -1011,6 +1011,7 @@ 1011 1011 * Reply to the confirmation package: 26 01 1012 1012 * Reply to non-confirmed packet: 26 00 1013 1013 842 + 1014 1014 Device will send an uplink after got this downlink command. With below payload: 1015 1015 1016 1016 Configures info payload: ... ... @@ -1233,6 +1233,7 @@ 1233 1233 * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 1234 1234 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 1235 1235 1065 + 1236 1236 = 9. Packing Info = 1237 1237 1238 1238 ... ... @@ -1247,6 +1247,7 @@ 1247 1247 * Package Size / pcs : cm 1248 1248 * Weight / pcs : g 1249 1249 1080 + 1250 1250 = 10. Support = 1251 1251 1252 1252 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.