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

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220613162008-1.png||_mstalt="428142" height="510" width="334"]]
2 +[[image:image-20220613162008-1.png||_mstalt="428142" height="579" width="379"]]
3 3  
4 4  
5 5  
... ... @@ -46,7 +46,6 @@
46 46  
47 47  == 1.2 Features ==
48 48  
49 -
50 50  * Wall mountable
51 51  * LoRaWAN v1.0.3 Class A protocol
52 52  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
... ... @@ -60,7 +60,6 @@
60 60  * Datalog feature
61 61  
62 62  
63 -
64 64  == 1.3 Specification ==
65 65  
66 66  
... ... @@ -71,8 +71,6 @@
71 71  * Long Term Drift: < 0.02 °C/yr
72 72  * Operating Range: -40 ~~ 85 °C
73 73  
74 -
75 -
76 76  **Built-in Humidity Sensor:**
77 77  
78 78  * Resolution: 0.04 %RH
... ... @@ -80,8 +80,6 @@
80 80  * Long Term Drift: < 0.02 °C/yr
81 81  * Operating Range: 0 ~~ 96 %RH
82 82  
83 -
84 -
85 85  **External Temperature Sensor:**
86 86  
87 87  * Resolution: 0.0625 °C
... ... @@ -95,7 +95,6 @@
95 95  
96 96  == 2.1 How does LHT65N work? ==
97 97  
98 -
99 99  (((
100 100  LHT65N is configured as LoRaWAN OTAA Class A mode by default. Each LHT65N is shipped with a worldwide unique set of OTAA keys. To use LHT65N in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N.
101 101  )))
... ... @@ -105,10 +105,8 @@
105 105  )))
106 106  
107 107  
108 -
109 109  == 2.2 How to Activate LHT65N? ==
110 110  
111 -
112 112  (((
113 113  The LHT65N has two working modes:
114 114  )))
... ... @@ -133,7 +133,6 @@
133 133  
134 134  == 2.3 Example to join LoRaWAN network ==
135 135  
136 -
137 137  (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
138 138  This section shows an example of how to join the TTN V3 LoRaWAN IoT server. Use with other LoRaWAN IoT servers is of a similar procedure.
139 139  
... ... @@ -149,7 +149,6 @@
149 149  
150 150  === 2.3.1 Step 1: Create Device n TTN ===
151 151  
152 -
153 153  (((
154 154  Create a device in TTN V3 with the OTAA keys from LHT65N.
155 155  )))
... ... @@ -174,10 +174,9 @@
174 174  [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
175 175  
176 176  
166 +Note: LHT65N use same payload as LHT65.
177 177  
178 -(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
179 179  
180 -
181 181  [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
182 182  
183 183  
... ... @@ -191,7 +191,6 @@
191 191  
192 192  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
193 193  
194 -
195 195  (((
196 196  Use ACT button to activate LHT65N and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
197 197  )))
... ... @@ -203,7 +203,6 @@
203 203  
204 204  == 2.4 Uplink Payload ==
205 205  
206 -
207 207  (((
208 208  The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% _mstvisible="3" style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default.
209 209  )))
... ... @@ -278,13 +278,10 @@
278 278  
279 279  * The First 6 bytes: has fix meanings for every LHT65N.
280 280  * The 7th byte (EXT #): defines the external sensor model.
281 -* 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.)
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.)
282 282  
283 -
284 -
285 285  === 2.4.1 Decoder in TTN V3 ===
286 286  
287 -
288 288  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.
289 289  
290 290  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -300,7 +300,6 @@
300 300  
301 301  === 2.4.2 BAT-Battery Info ===
302 302  
303 -
304 304  These two bytes of BAT include the battery state and the actually voltage
305 305  
306 306  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -314,11 +314,8 @@
314 314  * BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
315 315  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
316 316  
317 -
318 -
319 319  === 2.4.3 Built-in Temperature ===
320 320  
321 -
322 322  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
323 323  
324 324  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -327,20 +327,14 @@
327 327  
328 328  * Temperature:  (0xF5C6-65536)/100=-26.18℃
329 329  
330 -
331 -
332 332  === 2.4.4 Built-in Humidity ===
333 333  
334 -
335 335  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
336 336  
337 337  * Humidity:    0x025C/10=60.4%
338 338  
339 -
340 -
341 341  === 2.4.5 Ext # ===
342 342  
343 -
344 344  Bytes for External Sensor:
345 345  
346 346  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -372,7 +372,6 @@
372 372  
373 373  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
374 374  
375 -
376 376  (((
377 377  Timestamp mode is designed for LHT65N with E3 probe, it will send the uplink payload with Unix timestamp. With the limitation of 11 bytes (max distance of AU915/US915/AS923 band), the time stamp mode will be lack of BAT voltage field, instead, it shows the battery status. The payload is as below:
378 378  )))
... ... @@ -486,19 +486,14 @@
486 486  
487 487  * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
488 488  
489 -(% border="1" cellspacing="8" style="background-color:#ffffcc; color:green; width:520px" %)
490 -|(% style="width:60px" %)**Bits**|(% style="width:90px" %)**7**|(% style="width:100px" %)**6**|(% style="width:90px" %)**5**|(% style="width:100px" %)**4**|(% style="width:60px" %)**[3:0]**
491 -|(% style="width:96px" %)**Status&Ext**|(% style="width:124px" %)None-ACK Flag|(% style="width:146px" %)Poll Message FLAG|(% style="width:109px" %)Sync time OK|(% style="width:143px" %)Unix Time Request|(% style="width:106px" %)Ext: 0b(1001)
461 +[[image:image-20220523152434-16.png||_mstalt="453921" _mstvisible="3"]]
492 492  
493 -* (% style="color:blue" %)**Poll Message Flag**:(%%)  1: This message is a poll message reply, 0: means this is a normal uplink.
494 -* (% style="color:blue" %)**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.
495 -* (% style="color:blue" %)**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)
463 +* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
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 +* 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)
496 496  
497 -
498 -
499 499  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
500 500  
501 -
502 502  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
503 503  
504 504  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -507,46 +507,10 @@
507 507  
508 508  AT+EXT=6,timeout  (% _msthash="506085" _msttexthash="8782189" _mstvisible="3" style="color:red" %)Time to power this sensor, from 0 ~~ 65535ms
509 509  
510 -For example:
511 511  
512 -AT+EXT=6,1000 will power this sensor for 1000ms before sampling the ADC value.
513 513  
514 -
515 -Or use **downlink command A2** to set the same.
516 -
517 -The measuring range of the node is only about 0.1V to 1.1V The voltage resolution is about 0.24mv.
518 -
519 -When the measured output voltage of the sensor is not within the range of 0.1V and 1.1V, the output voltage terminal of the sensor shall be divided The example in the following figure is to reduce the output voltage of the sensor by three times If it is necessary to reduce more times, calculate according to the formula in the figure and connect the corresponding resistance in series.
520 -
521 -[[image:image-20220628150112-1.png||height="241" width="285"]]
522 -
523 -
524 -When ADC_IN1 pin is connected to GND or suspended, ADC value is 0
525 -
526 -[[image:image-20220628150714-4.png]]
527 -
528 -
529 -When the voltage collected by ADC_IN1 is less than the minimum range, the minimum range will be used as the output; Similarly, when the collected voltage is greater than the maximum range, the maximum range will be used as the output.
530 -
531 -1) The minimum range is about 0.1V. Each chip has internal calibration, so this value is close to 0.1V
532 -
533 -[[image:image-20220628151005-5.png]]
534 -
535 -
536 -2) The maximum range is about 1.1V. Each chip has internal calibration, so this value is close to 1.1v
537 -
538 -[[image:image-20220628151056-6.png]]
539 -
540 -
541 -3) Within range
542 -
543 -[[image:image-20220628151143-7.png]]
544 -
545 -
546 -
547 547  == 2.5 Show data on Datacake ==
548 548  
549 -
550 550  (((
551 551  Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
552 552  )))
... ... @@ -594,7 +594,6 @@
594 594  
595 595  == 2.6 Datalog Feature ==
596 596  
597 -
598 598  (((
599 599  Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LHT65N will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N.
600 600  )))
... ... @@ -603,17 +603,11 @@
603 603  
604 604  === 2.6.1 Ways to get datalog via LoRaWAN ===
605 605  
606 -
607 607  There are two methods:
608 608  
609 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range.
610 -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 the network recovery.
538 +1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
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.
611 611  
612 -Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
613 -
614 -[[image:image-20220703111700-2.png||height="381" width="1119"]]
615 -
616 -
617 617  === 2.6.2 Unix TimeStamp ===
618 618  
619 619  
... ... @@ -636,44 +636,25 @@
636 636  
637 637  === 2.6.3 Set Device Time ===
638 638  
639 -
640 -(((
641 641  There are two ways to set device's time:
642 -)))
643 643  
644 -(((
645 645  **~1. Through LoRaWAN MAC Command (Default settings)**
646 -)))
647 647  
648 -(((
649 649  User need to set SYNCMOD=1 to enable sync time via MAC command.
650 -)))
651 651  
652 -(((
653 653  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).
654 -)))
655 655  
656 -(((
657 -(% 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.**
658 -)))
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.
659 659  
660 -(((
661 -
662 -)))
663 663  
664 -(((
665 665  **2. Manually Set Time**
666 -)))
667 667  
668 -(((
669 669  User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
670 -)))
671 671  
672 672  
673 673  
674 674  === 2.6.4 Poll sensor value ===
675 675  
676 -
677 677  User can poll sensor value based on timestamps from the server. Below is the downlink command.
678 678  
679 679  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -691,7 +691,6 @@
691 691  
692 692  === 2.6.5 Datalog Uplink payload ===
693 693  
694 -
695 695  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
696 696  The Datalog poll reply uplink will use below payload format.
697 697  
... ... @@ -698,9 +698,6 @@
698 698  (% _mstvisible="1" %)
699 699  (((
700 700  (% _mstvisible="2" %)
701 -
702 -
703 -(% _mstvisible="2" %)
704 704  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
705 705  )))
706 706  
... ... @@ -828,7 +828,6 @@
828 828  )))
829 829  )))
830 830  
831 -
832 832  (% _mstvisible="1" %)
833 833  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
834 834  
... ... @@ -840,11 +840,9 @@
840 840  (% _mstvisible="2" %)
841 841  (((
842 842  (% _msthash="736723" _msttexthash="2005003" _mstvisible="3" %)
843 -(((
844 844  Poll Message Flag: 1: This message is a poll message reply.
845 845  )))
846 846  )))
847 -)))
848 848  
849 849  (% _mstvisible="1" %)
850 850  * (% _mstvisible="3" %)
... ... @@ -852,21 +852,17 @@
852 852  (% _mstvisible="4" %)
853 853  (((
854 854  (% _msthash="1197157" _msttexthash="561548" _mstvisible="5" %)
855 -(((
856 856  Poll Message Flag is set to 1.
857 857  )))
858 858  )))
859 -)))
860 860  * (% _mstvisible="3" %)
861 861  (((
862 862  (% _mstvisible="4" %)
863 863  (((
864 864  (% _msthash="1197158" _msttexthash="9284964" _mstvisible="5" %)
865 -(((
866 866  Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
867 867  )))
868 868  )))
869 -)))
870 870  
871 871  (% _mstvisible="1" %)
872 872  (((
... ... @@ -873,16 +873,12 @@
873 873  (% _mstvisible="2" %)
874 874  (((
875 875  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
876 -(((
877 877  
878 -)))
879 879  
880 880  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
881 -(((
882 882  For example, in US915 band, the max payload for different DR is:
883 883  )))
884 884  )))
885 -)))
886 886  
887 887  (% _mstvisible="1" %)
888 888  (((
... ... @@ -889,11 +889,9 @@
889 889  (% _mstvisible="2" %)
890 890  (((
891 891  (% _msthash="736725" _msttexthash="1065532" _mstvisible="3" %)
892 -(((
893 893  a) DR0: max is 11 bytes so one entry of data
894 894  )))
895 895  )))
896 -)))
897 897  
898 898  (% _mstvisible="1" %)
899 899  (((
... ... @@ -900,11 +900,9 @@
900 900  (% _mstvisible="2" %)
901 901  (((
902 902  (% _msthash="736726" _msttexthash="3265665" _mstvisible="3" %)
903 -(((
904 904  b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
905 905  )))
906 906  )))
907 -)))
908 908  
909 909  (% _mstvisible="1" %)
910 910  (((
... ... @@ -911,11 +911,9 @@
911 911  (% _mstvisible="2" %)
912 912  (((
913 913  (% _msthash="736727" _msttexthash="1454115" _mstvisible="3" style="text-align: left;" %)
914 -(((
915 915  c) DR2: total payload includes 11 entries of data
916 916  )))
917 917  )))
918 -)))
919 919  
920 920  (% _mstvisible="1" %)
921 921  (((
... ... @@ -922,11 +922,9 @@
922 922  (% _mstvisible="2" %)
923 923  (((
924 924  (% _msthash="736728" _msttexthash="1483924" _mstvisible="3" style="text-align: left;" %)
925 -(((
926 926  d) DR3: total payload includes 22 entries of data.
927 927  )))
928 928  )))
929 -)))
930 930  
931 931  (% _mstvisible="1" %)
932 932  (((
... ... @@ -933,11 +933,9 @@
933 933  (% _mstvisible="2" %)
934 934  (((
935 935  (% _msthash="736729" _msttexthash="5848349" _mstvisible="3" style="text-align: left;" %)
936 -(((
937 937  If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0   
938 938  )))
939 939  )))
940 -)))
941 941  
942 942  
943 943  (% _mstvisible="1" style="text-align: left;" %)
... ... @@ -964,7 +964,7 @@
964 964  (% _mstvisible="1" %)
965 965  (((
966 966  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
967 - Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03
847 + Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03
968 968  )))
969 969  
970 970  (% _mstvisible="1" %)
... ... @@ -983,99 +983,55 @@
983 983  [[image:image-20220523001219-13.png||_mstalt="451204" _mstvisible="3" height="421" style="text-align:left" width="727"]]
984 984  
985 985  (% _msthash="315271" _msttexthash="12012546" _mstvisible="1" style="text-align: left;" %)
986 -(((
987 987  7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
988 -)))
989 989  
990 990  (% _msthash="315237" _msttexthash="1385839" %)
991 -(((
992 992  Where the first 11 bytes is for the first entry:
993 -)))
994 994  
995 995  (% _msthash="315238" _msttexthash="274846" %)
996 -(((
997 997  7FFF089801464160065F97
998 -)))
999 999  
1000 1000  (% _msthash="315239" _msttexthash="617435" %)
1001 -(((
1002 1002  Ext sensor data=0x7FFF/100=327.67
1003 -)))
1004 1004  
1005 1005  (% _msthash="315240" _msttexthash="270543" %)
1006 -(((
1007 1007  Temp=0x0898/100=22.00
1008 -)))
1009 1009  
1010 1010  (% _msthash="315241" _msttexthash="211783" %)
1011 -(((
1012 1012  Hum=0x0146/10=32.6
1013 -)))
1014 1014  
1015 1015  (% _msthash="315242" _msttexthash="1569776" %)
1016 -(((
1017 1017  poll message flag & Ext=0x41,means reply data,Ext=1
1018 -)))
1019 1019  
1020 1020  (% _msthash="315243" _msttexthash="1120509" %)
1021 -(((
1022 1022  Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
1023 -)))
1024 1024  
1025 1025  
1026 1026  
1027 1027  == 2.7 Alarm Mode ==
1028 1028  
1029 -(((
1030 1030  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.
1031 -)))
1032 1032  
1033 -(((
1034 1034  (% style="color:red" %)Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.
1035 -)))
1036 1036  
1037 -(((
1038 1038  **AT COMMAND FOR ALARM MODE:**
1039 -)))
1040 1040  
1041 1041  (% _mstvisible="1" class="box infomessage" %)
1042 1042  (((
1043 -(((
1044 1044  **AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled)
1045 -)))
1046 1046  
1047 -(((
1048 1048  **AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
1049 -)))
1050 1050  
1051 -(((
1052 1052  **AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
1053 -)))
1054 1054  
1055 -(((
1056 1056  **AT+ARTEMP=？ **:  Gets the alarm range of the internal temperature sensor(% _mstvisible="3" style="display:none" %)
1057 -)))
1058 1058  
1059 -(((
1060 1060  **AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
1061 1061  )))
1062 -)))
1063 1063  
1064 -(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
1065 1065  
1066 -Total bytes: 8 bytes
1067 1067  
1068 -**Example:**AA0100010001003C
1069 1069  
1070 -WMOD=01
1071 -
1072 -CITEMP=0001
1073 -
1074 -TEMPlow=0001
1075 -
1076 -TEMPhigh=003C
1077 -
1078 -
1079 1079  == 2.8 LED Indicator ==
1080 1080  
1081 1081  The LHT65 has a triple color LED which for easy showing different stage .
... ... @@ -1085,11 +1085,10 @@
1085 1085  In a normal working state:
1086 1086  
1087 1087  * For each uplink, the BLUE LED or RED LED will blink once.
1088 -BLUE LED when external sensor is connected.
924 + BLUE LED when external sensor is connected.
1089 1089  * RED LED when external sensor is not connected
1090 1090  * For each success downlink, the PURPLE LED will blink once
1091 1091  
1092 -
1093 1093  == 2.9 installation ==
1094 1094  
1095 1095  (% _mstvisible="1" %)
... ... @@ -1103,24 +1103,8 @@
1103 1103  
1104 1104  [[image:image-20220619092222-1.png||height="182" width="188"]][[image:image-20220619092313-2.png||height="182" width="173"]]
1105 1105  
1106 -**1m long breakout cable for LHT65N. Features:**
941 +1m long breakout cable for LHT65N
1107 1107  
1108 -* (((
1109 -Use for AT Command， works for both LHT52/LHT65N
1110 -)))
1111 -* (((
1112 -Update firmware for LHT65N, works for both LHT52/LHT65N
1113 -)))
1114 -* (((
1115 -Supports ADC mode to monitor external ADC
1116 -)))
1117 -* (((
1118 -Supports Interrupt mode
1119 -)))
1120 -* (((
1121 -Exposed All pins from the LHT65N Type-C connector.
1122 -)))
1123 -
1124 1124  [[image:image-20220619092421-3.png||height="371" width="529"]]
1125 1125  
1126 1126  
... ... @@ -1140,51 +1140,28 @@
1140 1140  * Operating Range: -40 ~~ 125 °C
1141 1141  * Working voltage 2.35v ~~ 5v
1142 1142  
1143 -
1144 1144  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
1145 1145  
1146 -(((
1147 1147  Use can configure LHT65N via AT Command or LoRaWAN Downlink.
1148 -)))
1149 1149  
1150 -* (((
1151 -AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
1152 -)))
966 +* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
1153 1153  
1154 -* (((
1155 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
1156 -)))
968 +* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
1157 1157  
1158 -(((
1159 1159  There are two kinds of commands to configure LHT65N, they are:
1160 -)))
1161 1161  
1162 -* (((
1163 -(% style="color:#4f81bd" %)**General Commands**.
1164 -)))
972 +* (% style="color:#4f81bd" %)**General Commands**.
1165 1165  
1166 -(((
1167 1167  These commands are to configure:
1168 -)))
1169 1169  
1170 -1. (((
1171 -General system settings like: uplink interval.
1172 -)))
1173 -1. (((
1174 -LoRaWAN protocol & radio-related commands.
1175 -)))
976 +1. General system settings like: uplink interval.
977 +1. LoRaWAN protocol & radio-related commands.
1176 1176  
1177 -(((
1178 1178  They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
1179 -)))
1180 1180  
1181 -* (((
1182 -(% style="color:#4f81bd" %)**Commands special design for LHT65N**
1183 -)))
981 +* (% style="color:#4f81bd" %)**Commands special design for LHT65N**
1184 1184  
1185 -(((
1186 1186  These commands are only valid for LHT65N, as below:
1187 -)))
1188 1188  
1189 1189  
1190 1190  == 4.1 Set Transmit Interval Time ==
... ... @@ -1206,7 +1206,6 @@
1206 1206  
1207 1207  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1208 1208  
1209 -
1210 1210  == 4.2 Set External Sensor Mode ==
1211 1211  
1212 1212  Feature: Change External Sensor Mode.
... ... @@ -1228,7 +1228,6 @@
1228 1228  
1229 1229  * 0xA20702003c: Same as AT+SETCNT=60
1230 1230  
1231 -
1232 1232  == 4.3 Enable/Disable uplink Temperature probe ID ==
1233 1233  
1234 1234  (((
... ... @@ -1256,7 +1256,6 @@
1256 1256  * **0xA800**  **~-~->** AT+PID=0
1257 1257  * **0xA801**     **~-~->** AT+PID=1
1258 1258  
1259 -
1260 1260  == 4.4 Set Password ==
1261 1261  
1262 1262  Feature: Set device password, max 9 digits
... ... @@ -1303,7 +1303,6 @@
1303 1303  
1304 1304  * There is no downlink command to set to Sleep mode.
1305 1305  
1306 -
1307 1307  == 4.7 Set system time ==
1308 1308  
1309 1309  Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
... ... @@ -1400,7 +1400,6 @@
1400 1400  
1401 1401  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1402 1402  
1403 -
1404 1404  == 4.13 Auto Send None-ACK messages ==
1405 1405  
1406 1406  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
... ... @@ -1419,7 +1419,6 @@
1419 1419  
1420 1420  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1421 1421  
1422 -
1423 1423  = 5. Battery & How to replace =
1424 1424  
1425 1425  == 5.1 Battery Type ==
... ... @@ -1479,11 +1479,16 @@
1479 1479  
1480 1480  (% _msthash="506061" _msttexthash="170755" %)**Connection:**
1481 1481  
1482 -* (% style="background-color:yellow" %)**USB to TTL GND <~-~->GND**
1483 -* (% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+**
1484 -* (% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11**
1485 -* (% style="background-color:yellow" %)**USB to TTL 3.3V <~-~-> D-**
1272 +(% _msthash="506062" _msttexthash="1187732" %)
1273 +**✓ (% style="background-color:yellow" %)USB to TTL GND <~-~->GND(%%)**
1486 1486  
1275 +(% _msthash="506063" _msttexthash="1158313" %)**✓  **(% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+**
1276 +
1277 +(% _msthash="506064" _msttexthash="1175629" %)**✓  **(% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11**
1278 +
1279 +(% _msthash="506065" _msttexthash="1164696" %)**✓  **(% style="background-color:yellow" %)**USB to TTL 3.3V <~-~-> D-**
1280 +
1281 +
1487 1487  (((
1488 1488  In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console for LHT65N. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**) (%%)to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout.
1489 1489  )))
... ... @@ -1792,59 +1792,7 @@
1792 1792  Finally, unplug the DuPont cable on port4, and then use the DuPont cable to short circuit port3 and port1 to reset the device.
1793 1793  
1794 1794  
1795 -== 6.6 Using USB-TYPE-C to connect to the computer using the AT command ==
1796 1796  
1797 -[[image:image-20220623110706-1.png]]
1798 -
1799 -
1800 -[[image:image-20220623112117-4.png||height="459" width="343"]]
1801 -
1802 -(((
1803 -In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600** (%%)to access to access serial console for LHT65N. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(% style="color:red" %))(%%) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout.
1804 -)))
1805 -
1806 -
1807 -Input password and ATZ to activate LHT65N,As shown below:
1808 -
1809 -[[image:image-20220615154519-3.png||height="672" width="807"]]
1810 -
1811 -
1812 -== 6.7 How to use  USB-TYPE-C to connect PC to upgrade firmware? ==
1813 -
1814 -[[image:image-20220623110706-1.png]]
1815 -
1816 -(% style="color:blue" %)**Step1**(%%): Install TremoProgrammer  first.
1817 -
1818 -[[image:image-20220615170542-5.png]]
1819 -
1820 -
1821 -(% style="color:blue" %)**Step2**(%%)：wiring method.(% style="display:none" %)
1822 -
1823 -(% _msthash="506146" _msttexthash="52173160" %)
1824 -First connect the four lines；
1825 -
1826 -(% _msthash="506146" _msttexthash="52173160" %)
1827 -[[image:image-20220623113959-5.png||height="528" width="397"]]
1828 -
1829 -(% _msthash="506146" _msttexthash="52173160" %)
1830 -Press and hold the start key to restart and enter  (% _mstvisible="1" %)bootlaod(%%) mode.
1831 -
1832 -(% style="color:blue" %)**Step3：**(%%)Select the device port to be connected, baud rate and bin file to be downloaded.
1833 -
1834 -[[image:image-20220615171334-6.png]]
1835 -
1836 -
1837 -Click the (% style="color:blue" %)**start**(%%) button to start the firmware upgrade.
1838 -
1839 -
1840 -When this interface appears, it indicates that the download has been completed.
1841 -
1842 -[[image:image-20220620160723-8.png]]
1843 -
1844 -
1845 -Finally,restart reset device again
1846 -
1847 -
1848 1848  = 7. Order Info =
1849 1849  
1850 1850  
... ... @@ -1872,7 +1872,6 @@
1872 1872  
1873 1873  * (% style="color:red" %)**E3**(%%): External Temperature Probe
1874 1874  
1875 -
1876 1876  = 8. Packing Info =
1877 1877  
1878 1878  
... ... @@ -1886,12 +1886,10 @@
1886 1886  * Device Size:  10 x 10 x 3.5 cm
1887 1887  * Device Weight: 120.5g
1888 1888  
1889 -
1890 1890  = 9. Reference material =
1891 1891  
1892 1892  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1893 1893  
1894 -
1895 1895  = 10. FCC Warning =
1896 1896  
1897 1897  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
image-20220623110706-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -689.7 KB
Content
image-20220623110723-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -501.5 KB
Content
image-20220623111949-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1.6 MB
Content
image-20220623112117-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -513.9 KB
Content
image-20220623113959-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -834.2 KB
Content
image-20220628150112-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -220.3 KB
Content
image-20220628150542-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20220628150648-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -8.3 KB
Content
image-20220628150714-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -7.1 KB
Content
image-20220628151005-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -7.3 KB
Content
image-20220628151056-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -8.2 KB
Content
image-20220628151143-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -7.2 KB
Content
image-20220703111533-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -694.5 KB
Content
image-20220703111700-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -369.4 KB
Content