Skip to Content
Last modified by Xiaoling on 2023/07/18 10:12
From version 170.27
edited by Xiaoling
on 2022/06/22 11:17
Change comment: There is no comment for this version
To version 170.31
edited by Xiaoling
on 2022/06/22 11:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -84,7 +84,6 @@
84 84  * Operating Range: -55 °C ~~ 125 °C
85 85  
86 86  
87 -
88 88  = 2. Connect LHT65N to IoT Server =
89 89  
90 90  == 2.1 How does LHT65N work? ==
... ... @@ -266,6 +266,10 @@
266 266  * The 7th byte (EXT #): defines the external sensor model.
267 267  * The 8(% _msthash="734578" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) ~~ 11(% _msthash="734579" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) byte: the value for external sensor value. The definition is based on external sensor type. (If EXT=0, there won’t be these four bytes.)
268 268  
268 +
269 +
270 +
271 +
269 269  === 2.4.1 Decoder in TTN V3 ===
270 270  
271 271  When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N decoder in TTNv3 for friendly reading.
... ... @@ -296,6 +296,10 @@
296 296  * BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
297 297  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
298 298  
302 +
303 +
304 +
305 +
299 299  === 2.4.3 Built-in Temperature ===
300 300  
301 301  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
... ... @@ -306,6 +306,10 @@
306 306  
307 307  * Temperature:  (0xF5C6-65536)/100=-26.18℃
308 308  
316 +
317 +
318 +
319 +
309 309  === 2.4.4 Built-in Humidity ===
310 310  
311 311  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
... ... @@ -312,6 +312,10 @@
312 312  
313 313  * Humidity:    0x025C/10=60.4%
314 314  
326 +
327 +
328 +
329 +
315 315  === 2.4.5 Ext # ===
316 316  
317 317  Bytes for External Sensor:
... ... @@ -464,6 +464,10 @@
464 464  * Sync time OK:  1: Set time ok，0: N/A. After time SYNC request is sent, LHT65N will set this bit to 0 until got the time stamp from the application server.
465 465  * Unix Time Request:  1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this)
466 466  
482 +
483 +
484 +
485 +
467 467  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
468 468  
469 469  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
... ... @@ -538,6 +538,10 @@
538 538  1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
539 539  1. Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N will store the sensor data, and it will send all messages after network recover.
540 540  
560 +
561 +
562 +
563 +
541 541  === 2.6.2 Unix TimeStamp ===
542 542  
543 543  
... ... @@ -560,20 +560,37 @@
560 560  
561 561  === 2.6.3 Set Device Time ===
562 562  
586 +(((
563 563  There are two ways to set device's time:
588 +)))
564 564  
590 +(((
565 565  **~1. Through LoRaWAN MAC Command (Default settings)**
592 +)))
566 566  
594 +(((
567 567  User need to set SYNCMOD=1 to enable sync time via MAC command.
596 +)))
568 568  
598 +(((
569 569  Once LHT65N Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LHT65N. If LHT65N fails to get the time from the server, LHT65N will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
600 +)))
570 570  
602 +(((
571 571  (% style="color:red" %)Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn’t support. If server doesn’t support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.
604 +)))
572 572  
606 +(((
607 +
608 +)))
573 573  
610 +(((
574 574  **2. Manually Set Time**
612 +)))
575 575  
614 +(((
576 576  User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
616 +)))
577 577  
578 578  
579 579  
... ... @@ -740,9 +740,11 @@
740 740  (% _mstvisible="2" %)
741 741  (((
742 742  (% _msthash="736723" _msttexthash="2005003" _mstvisible="3" %)
783 +(((
743 743  Poll Message Flag: 1: This message is a poll message reply.
744 744  )))
745 745  )))
787 +)))
746 746  
747 747  (% _mstvisible="1" %)
748 748  * (% _mstvisible="3" %)
... ... @@ -750,17 +750,21 @@
750 750  (% _mstvisible="4" %)
751 751  (((
752 752  (% _msthash="1197157" _msttexthash="561548" _mstvisible="5" %)
795 +(((
753 753  Poll Message Flag is set to 1.
754 754  )))
755 755  )))
799 +)))
756 756  * (% _mstvisible="3" %)
757 757  (((
758 758  (% _mstvisible="4" %)
759 759  (((
760 760  (% _msthash="1197158" _msttexthash="9284964" _mstvisible="5" %)
805 +(((
761 761  Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
762 762  )))
763 763  )))
809 +)))
764 764  
765 765  (% _mstvisible="1" %)
766 766  (((
... ... @@ -767,12 +767,16 @@
767 767  (% _mstvisible="2" %)
768 768  (((
769 769  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
816 +(((
770 770  
818 +)))
771 771  
772 772  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
821 +(((
773 773  For example, in US915 band, the max payload for different DR is:
774 774  )))
775 775  )))
825 +)))
776 776  
777 777  (% _mstvisible="1" %)
778 778  (((
... ... @@ -779,9 +779,11 @@
779 779  (% _mstvisible="2" %)
780 780  (((
781 781  (% _msthash="736725" _msttexthash="1065532" _mstvisible="3" %)
832 +(((
782 782  a) DR0: max is 11 bytes so one entry of data
783 783  )))
784 784  )))
836 +)))
785 785  
786 786  (% _mstvisible="1" %)
787 787  (((
... ... @@ -788,9 +788,11 @@
788 788  (% _mstvisible="2" %)
789 789  (((
790 790  (% _msthash="736726" _msttexthash="3265665" _mstvisible="3" %)
843 +(((
791 791  b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
792 792  )))
793 793  )))
847 +)))
794 794  
795 795  (% _mstvisible="1" %)
796 796  (((
... ... @@ -797,9 +797,11 @@
797 797  (% _mstvisible="2" %)
798 798  (((
799 799  (% _msthash="736727" _msttexthash="1454115" _mstvisible="3" style="text-align: left;" %)
854 +(((
800 800  c) DR2: total payload includes 11 entries of data
801 801  )))
802 802  )))
858 +)))
803 803  
804 804  (% _mstvisible="1" %)
805 805  (((
... ... @@ -806,9 +806,11 @@
806 806  (% _mstvisible="2" %)
807 807  (((
808 808  (% _msthash="736728" _msttexthash="1483924" _mstvisible="3" style="text-align: left;" %)
865 +(((
809 809  d) DR3: total payload includes 22 entries of data.
810 810  )))
811 811  )))
869 +)))
812 812  
813 813  (% _mstvisible="1" %)
814 814  (((
... ... @@ -815,9 +815,11 @@
815 815  (% _mstvisible="2" %)
816 816  (((
817 817  (% _msthash="736729" _msttexthash="5848349" _mstvisible="3" style="text-align: left;" %)
876 +(((
818 818  If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0   
819 819  )))
820 820  )))
880 +)))
821 821  
822 822  
823 823  (% _mstvisible="1" style="text-align: left;" %)
... ... @@ -863,51 +863,83 @@
863 863  [[image:image-20220523001219-13.png||_mstalt="451204" _mstvisible="3" height="421" style="text-align:left" width="727"]]
864 864  
865 865  (% _msthash="315271" _msttexthash="12012546" _mstvisible="1" style="text-align: left;" %)
926 +(((
866 866  7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
928 +)))
867 867  
868 868  (% _msthash="315237" _msttexthash="1385839" %)
931 +(((
869 869  Where the first 11 bytes is for the first entry:
933 +)))
870 870  
871 871  (% _msthash="315238" _msttexthash="274846" %)
936 +(((
872 872  7FFF089801464160065F97
938 +)))
873 873  
874 874  (% _msthash="315239" _msttexthash="617435" %)
941 +(((
875 875  Ext sensor data=0x7FFF/100=327.67
943 +)))
876 876  
877 877  (% _msthash="315240" _msttexthash="270543" %)
946 +(((
878 878  Temp=0x0898/100=22.00
948 +)))
879 879  
880 880  (% _msthash="315241" _msttexthash="211783" %)
951 +(((
881 881  Hum=0x0146/10=32.6
953 +)))
882 882  
883 883  (% _msthash="315242" _msttexthash="1569776" %)
956 +(((
884 884  poll message flag & Ext=0x41,means reply data,Ext=1
958 +)))
885 885  
886 886  (% _msthash="315243" _msttexthash="1120509" %)
961 +(((
887 887  Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
963 +)))
888 888  
889 889  
890 890  
891 891  == 2.7 Alarm Mode ==
892 892  
969 +(((
893 893  when the device is in alarm mode, it checks the built-in sensor temperature for a short time. if the temperature exceeds the preconfigured range, it sends an uplink immediately.
971 +)))
894 894  
973 +(((
895 895  (% style="color:red" %)Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.
975 +)))
896 896  
977 +(((
897 897  **AT COMMAND FOR ALARM MODE:**
979 +)))
898 898  
899 899  (% _mstvisible="1" class="box infomessage" %)
900 900  (((
983 +(((
901 901  **AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled)
985 +)))
902 902  
987 +(((
903 903  **AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
989 +)))
904 904  
991 +(((
905 905  **AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
993 +)))
906 906  
995 +(((
907 907  **AT+ARTEMP=？ **:  Gets the alarm range of the internal temperature sensor(% _mstvisible="3" style="display:none" %)
997 +)))
908 908  
999 +(((
909 909  **AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
910 910  )))
1002 +)))
911 911  
912 912  
913 913