<
From version < 37.2 >
edited by Xiaoling
on 2023/02/01 10:02
To version < 34.1 >
edited by Xiaoling
on 2023/02/01 09:44
>
Change comment: Uploaded new attachment "1675215848113-696.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -269,7 +269,7 @@
269 269  
270 270  **Parameter:  **aa: ASCII value of SDI-12 sensor address in downlink or HEX value in AT Command)
271 271  
272 -**Example :   **AT+ADDRI=0 ( Equal to downlink: 0x AA 00 30)
272 +**Example :  **AT+ADDRI=0 ( Equal to downlink: 0x AA 00 30)
273 273  
274 274  
275 275  The following is the display information on the serial port and the server.
... ... @@ -387,7 +387,7 @@
387 387  [[image:image-20230201092208-15.png||height="214" width="1140"]]
388 388  
389 389  
390 -=== 2.3.2 Advance SDI-12 Debug command ===
390 +=== ​​​​​​​2.3.2 Advance SDI-12 Debug command ===
391 391  
392 392  
393 393  This command can be used to debug all SDI-12 command.
... ... @@ -421,6 +421,7 @@
421 421  
422 422  ​​​​​​​[[image:image-20230201092355-17.png||height="426" width="1135"]]
423 423  
424 +
424 424  ​​​​​​​
425 425  
426 426  === 2.3.3 Convert ASCII to String ===
... ... @@ -442,6 +442,9 @@
442 442  
443 443  [[image:1675214856590-846.png]]
444 444  
446 +
447 +
448 +
445 445  ​​​​​​​
446 446  
447 447  === 2.3.4 Define periodically SDI-12 commands and uplink. ===
... ... @@ -480,7 +480,7 @@
480 480  
481 481  (% border="1" style="background-color:#f7faff; width:436px" %)
482 482  |(% style="width:433px" %)(((
483 -**AT+DATACUTx=a,b,c**
487 +AT+DATACUTx=a,b,c
484 484  
485 485  **a**:  length for the return of AT+COMMAND
486 486  
... ... @@ -489,14 +489,13 @@
489 489  **c**:  define the position for valid value. 
490 490  )))
491 491  
492 -For example, if return from AT+COMMAND1 is “013METER   TER12 112T12-00024895” , Below AT+DATACUT1 will get different result to combine payload:
496 +For example, if return from AT+COMMAND1 is “013METER   TER12 112T12-00024895” ,. Below AT+DATACUT1 will get different result to combine payload:
493 493  
494 494  
495 -(% border="1" cellspacing="4" style="background-color:#f7faff; width:510px" %)
496 -|(% style="width:170px" %)**AT+DATACUT1 value**|(% style="width:338px" %)**Final Result to combine Payload**
497 -|(% style="width:170px" %)34,1,1+2+3|(% style="width:338px" %)0D 00 01 30 31 33
498 -|(% style="width:170px" %)34,2,1~~8+12~~16|(% style="width:338px" %)0D 00 01 30 31 33 4D 45 54 45 52 54 45 52 31 32
499 -|(% style="width:170px" %)34,2,1~~34|(% style="width:338px" %)0D 00 01 30 31 33 4D 45 54 45 52 20 20 20 54 45 52 31 32 20 31 31 32 54 31 32 2D 30 30 30 32 34 38 39 35 0D 0A
499 +|AT+DATACUT1 value|Final Result to combine Payload
500 +|34,1,1+2+3|0D 00 01 30 31 33
501 +|34,2,1~~8+12~~16|0D 00 01 30 31 33 4D 45 54 45 52 54 45 52 31 32
502 +|34,2,1~~34|0D 00 01 30 31 33 4D 45 54 45 52 20 20 20 54 45 52 31 32 20 31 31 32 54 31 32 2D 30 30 30 32 34 38 39 35 0D 0A
500 500  
501 501  * ** Downlink Payload:**
502 502  
... ... @@ -510,17 +510,21 @@
510 510  
511 511  Where:
512 512  
513 -* **MM **: the AT+COMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
514 -* **NN **:  1: set the AT+DATACUT value ; 2: set the AT+DATACUT value.
515 -* **LL **:  The length of AT+COMMAND or AT+DATACUT command
516 -* **XX XX XX XX **: AT+COMMAND or AT+DATACUT command
517 -* **YY **:  If YY=0, RS485-LN will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command. 
516 +* MM: the AT+COMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
517 +* NN:  1: set the AT+DATACUT value ; 2: set the AT+DATACUT value.
518 +* LL:  The length of AT+COMMAND or AT+DATACUT command
519 +* XX XX XX XX: AT+COMMAND or AT+DATACUT command
520 +* YY:  If YY=0, RS485-LN will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command. 
518 518  
519 -**Example:**
522 +Example:
520 520  
521 -[[image:image-20230201094129-18.png]]
524 +**AF 03 01 07 30 4D 43 21 01 01 01 00**: Same as AT+COMMAND3=**0MC!**,** 1**,** 1**,** 1**
522 522  
526 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
523 523  
528 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
529 +
530 +
524 524  **Clear SDI12 Command**
525 525  
526 526  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
... ... @@ -540,22 +540,23 @@
540 540  
541 541  
542 542  
550 +
543 543  **command combination**
544 544  
545 545  Below shows a screen shot how the results combines together to a uplink payload.
546 546  
547 -[[image:1675215745275-920.png]]
555 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
548 548  
549 549  
550 -If user don't want to use DATACUT for some command, he simply want to uplink all returns. AT+ALLDATAMOD can be set to 1.
558 +If user dont want to use DATACUT for some command, he simply want to uplink all returns. AT+ALLDATAMOD can be set to 1.
551 551  
552 -**AT+ALLDATAMOD** will simply get all return and don't do CRC check as result for SDI-12 command. AT+DATACUTx command has higher priority, if AT+DATACUTx has been set, AT+ALLDATAMOD will be ignore for this SDI-12 command.
560 +**AT+ALLDATAMOD** will simply get all return and dont do CRC check as result for SDI-12 command. AT+DATACUTx command has higher priority, if AT+DATACUTx has been set, AT+ALLDATAMOD will be ignore for this SDI-12 command.
553 553  
554 554  
555 -**For example: ** as below photo, AT+ALLDATAMOD=1, but AT+DATACUT1 has been set, AT+DATACUT1 will be still effect the result.
563 +For example: as below photo, AT+ALLDATAMOD=1, but AT+DATACUT1 has been set, AT+DATACUT1 will be still effect the result.
556 556  
557 557  
558 -[[image:1675215782925-448.png]]
566 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
559 559  
560 560  
561 561  If AT+ALLDATAMOD=1, **FX,X** will be added in the payload, FX specify which command is used and X specify the length of return. for example in above screen, F1 05 means the return is from AT+COMMAND1 and the return is 5 bytes.
... ... @@ -564,7 +564,6 @@
564 564  
565 565  **Compose Uplink**
566 566  
567 -
568 568  **AT+DATAUP=0**
569 569  
570 570  Compose the uplink payload with value returns in sequence and send with A SIGNLE UPLINK.
... ... @@ -574,7 +574,7 @@
574 574  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
575 575  
576 576  
577 -[[image:1675215828102-844.png]]
584 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]]
578 578  
579 579  
580 580  **AT+DATAUP=1**
... ... @@ -583,7 +583,7 @@
583 583  
584 584  Final Payload is
585 585  
586 -__**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**__
593 +**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
587 587  
588 588  1. Battery Info (2 bytes): Battery voltage
589 589  1. PAYVER (1 byte): Defined by AT+PAYVER
... ... @@ -591,24 +591,26 @@
591 591  1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
592 592  1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
593 593  
594 -[[image:1675215848113-696.png]]
601 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
595 595  
596 596  
597 597  **Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
598 598  
599 -* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
600 -* For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
601 -* For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
602 -* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
606 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
603 603  
604 -**~ When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;**
608 + * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
605 605  
606 -**~ When AT+DATAUP=1 and AT+ADR=0, the maximum number of bytes of each payload is determined by the DR value.**
610 + * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
607 607  
612 + ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
608 608  
609 -== ​​​​​​​2.4 Uplink Payload ==
614 + *** When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;**
610 610  
616 +**~ When AT+DATAUP=1 and AT+ADR=0, the maximum number of bytes of each payload is determined by the DR value.**
611 611  
618 +1.
619 +11. Uplink Payload
620 +
612 612  Uplink payloads have two types:
613 613  
614 614  * Distance Value: Use FPORT=2
... ... @@ -617,23 +617,24 @@
617 617  The application server should parse the correct value based on FPORT settings.
618 618  
619 619  
620 -=== 2.4.1 Device Payload, FPORT~=5 ===
629 +1.
630 +11.
631 +111. Device Payload, FPORT=5
621 621  
622 -
623 623  Include device configure status. Once SDI-12-LB Joined the network, it will uplink this message to the server.
624 624  
635 +
625 625  Users can also use the downlink command(0x26 01) to ask SDI-12-LB to resend this uplink.
626 626  
627 -(% border="1" cellspacing="4" style="background-color:#f7faff; width:437px" %)
628 -|(% colspan="6" style="width:434px" %)**Device Status (FPORT=5)**
629 -|(% style="width:102px" %)**Size (bytes)**|(% style="width:67px" %)**1**|(% style="width:80px" %)**2**|(% style="width:89px" %)**1**|(% style="width:52px" %)**1**|(% style="width:44px" %)**2**
630 -|(% style="width:102px" %)**Value**|(% style="width:67px" %)Sensor Model|(% style="width:80px" %)Firmware Version|(% style="width:89px" %)Frequency Band|(% style="width:52px" %)Sub-band|(% style="width:44px" %)BAT
631 631  
639 +|(% colspan="6" %)**Device Status (FPORT=5)**
640 +|**Size (bytes)**|**1**|**2**|**1**|**1**|**2**
641 +|**Value**|Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT
642 +
632 632  Example parse in TTNv3
633 633  
634 -[[image:1675215946738-635.png]]
645 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]]
635 635  
636 -
637 637  **Sensor Model**: For SDI-12-LB, this value is 0x17
638 638  
639 639  **Firmware Version**: 0x0100, Means: v1.0.0 version
... ... @@ -687,9 +687,10 @@
687 687  Ex2: 0x0B49 = 2889mV
688 688  
689 689  
690 -=== 2.4.2 Uplink Payload, FPORT~=2 ===
700 +1.
701 +11.
702 +111. Uplink Payload, FPORT=2
691 691  
692 -
693 693  There are different cases for uplink. See below
694 694  
695 695  * SDI-12 Debug Command return: FPORT=100
... ... @@ -696,24 +696,30 @@
696 696  
697 697  * Periodically Uplink: FPORT=2
698 698  
699 -(% border="1" cellspacing="4" style="background-color:#f7faff; width:510px" %)
700 -|(% style="width:93px" %)(((
701 -**Size(bytes)**
702 -)))|(% style="width:83px" %)**2**|(% style="width:70px" %)**1**|(% style="width:234px" %)**Length depends on the return from the commands**
703 -|(% style="width:93px" %)**Value**|(% style="width:83px" %)(((
710 +|(((
711 +**Size**
712 +
713 +**(bytes)**
714 +)))|**2**|**1**|**Length depends on the return from the commands**
715 +|**Value**|(((
704 704  Battery(mV)
717 +
705 705  &
719 +
706 706  Interrupt_Flag
707 -)))|(% style="width:70px" %)[[PAYLOAD_VER>>path:#Probe_Model]]|(% style="width:234px" %)(((
708 -If the valid payload is too long and exceed the maximum support.
721 +)))|[[PAYLOAD_VER>>path:#Probe_Model]]|(((
722 +If the valid payload is too long and exceed the maximum support
723 +
709 709  Payload length in server,server will show payload not provided in the LoRaWAN server.
710 710  )))
711 711  
712 -[[image:1675216282284-923.png]]
727 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
713 713  
714 714  
715 -=== 2.4.3 Battery Info ===
716 716  
731 +1.
732 +11.
733 +111. Battery Info
717 717  
718 718  Check the battery voltage for SDI-12-LB.
719 719  
... ... @@ -722,37 +722,216 @@
722 722  Ex2: 0x0B49 = 2889mV
723 723  
724 724  
725 -=== 2.4.4 Interrupt Pin ===
742 +1.
743 +11.
744 +111. Interrupt Pin
726 726  
727 -
728 728  This data field shows if this packet is generated by **Interrupt Pin** or not. [[Click here>>path:#Int_mod]] for the hardware and software set up. Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]].
729 729  
730 -**Example:**
731 731  
749 +Example:
750 +
732 732  Ex1: 0x0B45:0x0B&0x80= 0x00    Normal uplink packet.
733 733  
734 734  Ex2: 0x8B49:0x8B&0x80= 0x80    Interrupt Uplink Packet.
735 735  
736 736  
737 -=== 2.4.5 Payload version ===
756 +1.
757 +11.
758 +111. Payload version
738 738  
739 739  
740 740  
741 -=== 2.4.6 ​Decode payload in The Things Network ===
742 742  
743 743  
764 +1.
765 +11.
766 +111. ​Decode payload in The Things Network
767 +
744 744  While using TTN network, you can add the payload format to decode the payload.
745 745  
746 -[[image:1675216779406-595.png]]
770 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]]
747 747  
748 748  
749 749  There is no fix payload decoder in LoRaWAN server because the SDI-12 sensors returns are different. User need to write the decoder themselves for their case.
750 750  
751 -SDI-12-LB TTN Payload Decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>url:https://github.com/dragino/dragino-end-node-decoder]]
752 752  
776 +下面的解码生成超链接放进去.
753 753  
778 +function Decoder(bytes, port) {
754 754  
755 -1.
780 + if(port==5)
781 +
782 + {
783 +
784 + var freq_band;
785 +
786 + var sub_band;
787 +
788 + var sensor;
789 +
790 +
791 + if(bytes[0]==0x17)
792 +
793 + sensor= "SDI12-LB";
794 +
795 +
796 + var firm_ver= (bytes[1]&0x0f)+'.'+(bytes[2]>>4&0x0f)+'.'+(bytes[2]&0x0f);
797 +
798 +
799 + if(bytes[3]==0x01)
800 +
801 + freq_band="EU868";
802 +
803 + else if(bytes[3]==0x02)
804 +
805 + freq_band="US915";
806 +
807 + else if(bytes[3]==0x03)
808 +
809 + freq_band="IN865";
810 +
811 + else if(bytes[3]==0x04)
812 +
813 + freq_band="AU915";
814 +
815 + else if(bytes[3]==0x05)
816 +
817 + freq_band="KZ865";
818 +
819 + else if(bytes[3]==0x06)
820 +
821 + freq_band="RU864";
822 +
823 + else if(bytes[3]==0x07)
824 +
825 + freq_band="AS923";
826 +
827 + else if(bytes[3]==0x08)
828 +
829 + freq_band="AS923_1";
830 +
831 + else if(bytes[3]==0x09)
832 +
833 + freq_band="AS923_2";
834 +
835 + else if(bytes[3]==0x0A)
836 +
837 + freq_band="AS923_3";
838 +
839 + else if(bytes[3]==0x0F)
840 +
841 + freq_band="AS923_4";
842 +
843 + else if(bytes[3]==0x0B)
844 +
845 + freq_band="CN470";
846 +
847 + else if(bytes[3]==0x0C)
848 +
849 + freq_band="EU433";
850 +
851 + else if(bytes[3]==0x0D)
852 +
853 + freq_band="KR920";
854 +
855 + else if(bytes[3]==0x0E)
856 +
857 + freq_band="MA869";
858 +
859 +
860 + if(bytes[4]==0xff)
861 +
862 + sub_band="NULL";
863 +
864 + else
865 +
866 + sub_band=bytes[4];
867 +
868 +
869 + var bat= (bytes[5]<<8 | bytes[6])/1000;
870 +
871 +
872 + return {
873 +
874 + SENSOR_MODEL:sensor,
875 +
876 + FIRMWARE_VERSION:firm_ver,
877 +
878 + FREQUENCY_BAND:freq_band,
879 +
880 + SUB_BAND:sub_band,
881 +
882 + BAT:bat,
883 +
884 + }
885 +
886 + }
887 +
888 + else if(port==100)
889 +
890 + {
891 +
892 + var datas_sum={};
893 +
894 + for(var j=0;j<bytes.length;j++)
895 +
896 + {
897 +
898 + var datas= String.fromCharCode(bytes[j]);
899 +
900 + if(j=='0')
901 +
902 + datas_sum.datas_sum=datas;
903 +
904 + else
905 +
906 + datas_sum.datas_sum+=datas;
907 +
908 + }
909 +
910 +
911 + return datas_sum;
912 +
913 + }
914 +
915 + else
916 +
917 + {
918 +
919 + var decode={};
920 +
921 + decode.EXTI_Trigger= (bytes[0] & 0x80)? "TRUE":"FALSE";  
922 +
923 + decode.BatV= ((bytes[0]<<8 | bytes[1])&0x7FFF)/1000;
924 +
925 + decode.Payver= bytes[2];
926 +
927 + for(var i=3;i<bytes.length;i++)
928 +
929 + {
930 +
931 + var data= String.fromCharCode(bytes[i]);
932 +
933 + if(i=='3')
934 +
935 + decode.data_sum=data;
936 +
937 + else
938 +
939 + decode.data_sum+=data;
940 +
941 + }
942 +
943 + return decode; 
944 +
945 + }
946 +
947 +
948 +}
949 +
950 +
951 +1.
756 756  11. Uplink Interval
757 757  
758 758  The SDI-12-LB by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link:
... ... @@ -761,7 +761,7 @@
761 761  
762 762  
763 763  
764 -1.
960 +1.
765 765  11. Frequency Plans
766 766  
767 767  The SDI12-LB uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
... ... @@ -771,7 +771,7 @@
771 771  
772 772  
773 773  
774 -1.
970 +1.
775 775  11. Firmware Change Log
776 776  
777 777  **Firmware download link:**
... ... @@ -810,7 +810,7 @@
810 810  
811 811  
812 812  
813 -1.
1009 +1.
814 814  11. Set Transmit Interval Time
815 815  
816 816  Feature: Change LoRaWAN End Node Transmit Interval.
... ... @@ -840,7 +840,7 @@
840 840  * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
841 841  * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
842 842  
843 -1.
1039 +1.
844 844  11. Set Interrupt Mode
845 845  
846 846  Feature, Set Interrupt mode for GPIO_EXIT.
... ... @@ -873,7 +873,7 @@
873 873  * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
874 874  * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
875 875  
876 -1.
1072 +1.
877 877  11. Set the output time
878 878  
879 879  Feature, Control the output 3V3 , 5V or 12V.
... ... @@ -954,7 +954,7 @@
954 954  * Example 5: Downlink Payload: 070301F4  -> AT+12VT=500
955 955  * Example 6: Downlink Payload: 07030000  -> AT+12VT=0
956 956  
957 -1.
1153 +1.
958 958  11. Set the all data mode
959 959  
960 960  Feature, Set the all data mode.
... ... @@ -977,7 +977,7 @@
977 977  * Example 1: Downlink Payload: AB 00 ~/~/ AT+ALLDATAMOD=0
978 978  * Example 2: Downlink Payload: AB 01 ~/~/ AT+ALLDATAMOD=1
979 979  
980 -1.
1176 +1.
981 981  11. Set the splicing payload for uplink
982 982  
983 983  Feature, splicing payload for uplink.
... ... @@ -1018,7 +1018,7 @@
1018 1018  This means that the interval is set to 0x000014=20S
1019 1019  
1020 1020  
1021 -1.
1217 +1.
1022 1022  11. Set the payload version
1023 1023  
1024 1024  Feature, Set the payload version.
... ... @@ -1057,7 +1057,7 @@
1057 1057  SDI-12-LB:  2.45v ~~ 3.6v
1058 1058  
1059 1059  
1060 -1.
1256 +1.
1061 1061  11. Replace Battery
1062 1062  
1063 1063  Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
... ... @@ -1066,7 +1066,7 @@
1066 1066  
1067 1067  
1068 1068  
1069 -1.
1265 +1.
1070 1070  11. Power Consumption Analyze
1071 1071  
1072 1072  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.
... ... @@ -1106,14 +1106,14 @@
1106 1106  
1107 1107  
1108 1108  1.
1109 -11.
1305 +11.
1110 1110  111. ​Battery Note
1111 1111  
1112 1112  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.
1113 1113  
1114 1114  
1115 -1.
1116 -11.
1311 +1.
1312 +11.
1117 1117  111. ​Replace the battery
1118 1118  
1119 1119  You can change the battery in the SDI-12-LB.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
... ... @@ -1134,7 +1134,7 @@
1134 1134  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]
1135 1135  
1136 1136  
1137 -1.
1333 +1.
1138 1138  11. AT Command Set
1139 1139  
1140 1140  1. OTA firmware update
... ... @@ -1167,6 +1167,7 @@
1167 1167  * Weight / pcs : g
1168 1168  
1169 1169  
1366 +
1170 1170  1. ​Support
1171 1171  
1172 1172  * 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.
1675215946738-635.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -38.4 KB
Content
1675216282284-923.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -47.0 KB
Content
1675216779406-595.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.2 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0