Skip to Content
Last modified by Xiaoling on 2023/07/18 10:12
From version 170.28
edited by Xiaoling
on 2022/06/22 11:17
Change comment: There is no comment for this version
To version 189.8
edited by Xiaoling
on 2022/08/08 16:22
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="579" width="379"]]
2 +[[image:image-20220613162008-1.png||_mstalt="428142" height="510" width="334"]]
3 3  
4 4  
5 5  
... ... @@ -46,6 +46,7 @@
46 46  
47 47  == 1.2 Features ==
48 48  
49 +
49 49  * Wall mountable
50 50  * LoRaWAN v1.0.3 Class A protocol
51 51  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
... ... @@ -70,6 +70,8 @@
70 70  * Long Term Drift: < 0.02 °C/yr
71 71  * Operating Range: -40 ~~ 85 °C
72 72  
74 +
75 +
73 73  **Built-in Humidity Sensor:**
74 74  
75 75  * Resolution: 0.04 %RH
... ... @@ -77,6 +77,8 @@
77 77  * Long Term Drift: < 0.02 °C/yr
78 78  * Operating Range: 0 ~~ 96 %RH
79 79  
83 +
84 +
80 80  **External Temperature Sensor:**
81 81  
82 82  * Resolution: 0.0625 °C
... ... @@ -90,6 +90,7 @@
90 90  
91 91  == 2.1 How does LHT65N work? ==
92 92  
98 +
93 93  (((
94 94  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.
95 95  )))
... ... @@ -99,8 +99,10 @@
99 99  )))
100 100  
101 101  
108 +
102 102  == 2.2 How to Activate LHT65N? ==
103 103  
111 +
104 104  (((
105 105  The LHT65N has two working modes:
106 106  )))
... ... @@ -125,6 +125,7 @@
125 125  
126 126  == 2.3 Example to join LoRaWAN network ==
127 127  
136 +
128 128  (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
129 129  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.
130 130  
... ... @@ -140,6 +140,7 @@
140 140  
141 141  === 2.3.1 Step 1: Create Device n TTN ===
142 142  
152 +
143 143  (((
144 144  Create a device in TTN V3 with the OTAA keys from LHT65N.
145 145  )))
... ... @@ -164,9 +164,10 @@
164 164  [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
165 165  
166 166  
167 -Note: LHT65N use same payload as LHT65.
168 168  
178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
169 169  
180 +
170 170  [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
171 171  
172 172  
... ... @@ -180,6 +180,7 @@
180 180  
181 181  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
182 182  
194 +
183 183  (((
184 184  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.
185 185  )))
... ... @@ -191,6 +191,7 @@
191 191  
192 192  == 2.4 Uplink Payload ==
193 193  
206 +
194 194  (((
195 195  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.
196 196  )))
... ... @@ -265,10 +265,13 @@
265 265  
266 266  * The First 6 bytes: has fix meanings for every LHT65N.
267 267  * The 7th byte (EXT #): defines the external sensor model.
268 -* 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.)
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.)
269 269  
283 +
284 +
270 270  === 2.4.1 Decoder in TTN V3 ===
271 271  
287 +
272 272  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.
273 273  
274 274  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -284,6 +284,7 @@
284 284  
285 285  === 2.4.2 BAT-Battery Info ===
286 286  
303 +
287 287  These two bytes of BAT include the battery state and the actually voltage
288 288  
289 289  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -297,8 +297,11 @@
297 297  * BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
298 298  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
299 299  
317 +
318 +
300 300  === 2.4.3 Built-in Temperature ===
301 301  
321 +
302 302  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
303 303  
304 304  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -307,14 +307,20 @@
307 307  
308 308  * Temperature:  (0xF5C6-65536)/100=-26.18℃
309 309  
330 +
331 +
310 310  === 2.4.4 Built-in Humidity ===
311 311  
334 +
312 312  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
313 313  
314 314  * Humidity:    0x025C/10=60.4%
315 315  
339 +
340 +
316 316  === 2.4.5 Ext # ===
317 317  
343 +
318 318  Bytes for External Sensor:
319 319  
320 320  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -346,6 +346,7 @@
346 346  
347 347  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
348 348  
375 +
349 349  (((
350 350  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:
351 351  )))
... ... @@ -459,14 +459,19 @@
459 459  
460 460  * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
461 461  
462 -[[image:image-20220523152434-16.png||_mstalt="453921" _mstvisible="3"]]
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)
463 463  
464 -* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
465 -* 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.
466 -* 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)
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)
467 467  
497 +
498 +
468 468  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
469 469  
501 +
470 470  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
471 471  
472 472  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -475,10 +475,46 @@
475 475  
476 476  AT+EXT=6,timeout  (% _msthash="506085" _msttexthash="8782189" _mstvisible="3" style="color:red" %)Time to power this sensor, from 0 ~~ 65535ms
477 477  
510 +For example:
478 478  
512 +AT+EXT=6,1000 will power this sensor for 1000ms before sampling the ADC value.
479 479  
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 +
480 480  == 2.5 Show data on Datacake ==
481 481  
549 +
482 482  (((
483 483  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:
484 484  )))
... ... @@ -526,6 +526,7 @@
526 526  
527 527  == 2.6 Datalog Feature ==
528 528  
597 +
529 529  (((
530 530  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.
531 531  )))
... ... @@ -534,11 +534,17 @@
534 534  
535 535  === 2.6.1 Ways to get datalog via LoRaWAN ===
536 536  
606 +
537 537  There are two methods:
538 538  
539 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
540 -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.
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.
541 541  
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 +
542 542  === 2.6.2 Unix TimeStamp ===
543 543  
544 544  
... ... @@ -561,25 +561,44 @@
561 561  
562 562  === 2.6.3 Set Device Time ===
563 563  
639 +
640 +(((
564 564  There are two ways to set device's time:
642 +)))
565 565  
644 +(((
566 566  **~1. Through LoRaWAN MAC Command (Default settings)**
646 +)))
567 567  
648 +(((
568 568  User need to set SYNCMOD=1 to enable sync time via MAC command.
650 +)))
569 569  
652 +(((
570 570  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 +)))
571 571  
572 -(% 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.
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 +)))
573 573  
660 +(((
661 +
662 +)))
574 574  
664 +(((
575 575  **2. Manually Set Time**
666 +)))
576 576  
668 +(((
577 577  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 +)))
578 578  
579 579  
580 580  
581 581  === 2.6.4 Poll sensor value ===
582 582  
676 +
583 583  User can poll sensor value based on timestamps from the server. Below is the downlink command.
584 584  
585 585  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -597,6 +597,7 @@
597 597  
598 598  === 2.6.5 Datalog Uplink payload ===
599 599  
694 +
600 600  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
601 601  The Datalog poll reply uplink will use below payload format.
602 602  
... ... @@ -603,6 +603,9 @@
603 603  (% _mstvisible="1" %)
604 604  (((
605 605  (% _mstvisible="2" %)
701 +
702 +
703 +(% _mstvisible="2" %)
606 606  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
607 607  )))
608 608  
... ... @@ -730,6 +730,7 @@
730 730  )))
731 731  )))
732 732  
831 +
733 733  (% _mstvisible="1" %)
734 734  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
735 735  
... ... @@ -741,9 +741,11 @@
741 741  (% _mstvisible="2" %)
742 742  (((
743 743  (% _msthash="736723" _msttexthash="2005003" _mstvisible="3" %)
843 +(((
744 744  Poll Message Flag: 1: This message is a poll message reply.
745 745  )))
746 746  )))
847 +)))
747 747  
748 748  (% _mstvisible="1" %)
749 749  * (% _mstvisible="3" %)
... ... @@ -751,17 +751,21 @@
751 751  (% _mstvisible="4" %)
752 752  (((
753 753  (% _msthash="1197157" _msttexthash="561548" _mstvisible="5" %)
855 +(((
754 754  Poll Message Flag is set to 1.
755 755  )))
756 756  )))
859 +)))
757 757  * (% _mstvisible="3" %)
758 758  (((
759 759  (% _mstvisible="4" %)
760 760  (((
761 761  (% _msthash="1197158" _msttexthash="9284964" _mstvisible="5" %)
865 +(((
762 762  Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
763 763  )))
764 764  )))
869 +)))
765 765  
766 766  (% _mstvisible="1" %)
767 767  (((
... ... @@ -768,12 +768,16 @@
768 768  (% _mstvisible="2" %)
769 769  (((
770 770  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
876 +(((
771 771  
878 +)))
772 772  
773 773  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
881 +(((
774 774  For example, in US915 band, the max payload for different DR is:
775 775  )))
776 776  )))
885 +)))
777 777  
778 778  (% _mstvisible="1" %)
779 779  (((
... ... @@ -780,9 +780,11 @@
780 780  (% _mstvisible="2" %)
781 781  (((
782 782  (% _msthash="736725" _msttexthash="1065532" _mstvisible="3" %)
892 +(((
783 783  a) DR0: max is 11 bytes so one entry of data
784 784  )))
785 785  )))
896 +)))
786 786  
787 787  (% _mstvisible="1" %)
788 788  (((
... ... @@ -789,9 +789,11 @@
789 789  (% _mstvisible="2" %)
790 790  (((
791 791  (% _msthash="736726" _msttexthash="3265665" _mstvisible="3" %)
903 +(((
792 792  b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
793 793  )))
794 794  )))
907 +)))
795 795  
796 796  (% _mstvisible="1" %)
797 797  (((
... ... @@ -798,9 +798,11 @@
798 798  (% _mstvisible="2" %)
799 799  (((
800 800  (% _msthash="736727" _msttexthash="1454115" _mstvisible="3" style="text-align: left;" %)
914 +(((
801 801  c) DR2: total payload includes 11 entries of data
802 802  )))
803 803  )))
918 +)))
804 804  
805 805  (% _mstvisible="1" %)
806 806  (((
... ... @@ -807,9 +807,11 @@
807 807  (% _mstvisible="2" %)
808 808  (((
809 809  (% _msthash="736728" _msttexthash="1483924" _mstvisible="3" style="text-align: left;" %)
925 +(((
810 810  d) DR3: total payload includes 22 entries of data.
811 811  )))
812 812  )))
929 +)))
813 813  
814 814  (% _mstvisible="1" %)
815 815  (((
... ... @@ -816,9 +816,11 @@
816 816  (% _mstvisible="2" %)
817 817  (((
818 818  (% _msthash="736729" _msttexthash="5848349" _mstvisible="3" style="text-align: left;" %)
936 +(((
819 819  If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0   
820 820  )))
821 821  )))
940 +)))
822 822  
823 823  
824 824  (% _mstvisible="1" style="text-align: left;" %)
... ... @@ -845,7 +845,7 @@
845 845  (% _mstvisible="1" %)
846 846  (((
847 847  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
848 - Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03
967 + Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03
849 849  )))
850 850  
851 851  (% _mstvisible="1" %)
... ... @@ -864,55 +864,99 @@
864 864  [[image:image-20220523001219-13.png||_mstalt="451204" _mstvisible="3" height="421" style="text-align:left" width="727"]]
865 865  
866 866  (% _msthash="315271" _msttexthash="12012546" _mstvisible="1" style="text-align: left;" %)
986 +(((
867 867  7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
988 +)))
868 868  
869 869  (% _msthash="315237" _msttexthash="1385839" %)
991 +(((
870 870  Where the first 11 bytes is for the first entry:
993 +)))
871 871  
872 872  (% _msthash="315238" _msttexthash="274846" %)
996 +(((
873 873  7FFF089801464160065F97
998 +)))
874 874  
875 875  (% _msthash="315239" _msttexthash="617435" %)
1001 +(((
876 876  Ext sensor data=0x7FFF/100=327.67
1003 +)))
877 877  
878 878  (% _msthash="315240" _msttexthash="270543" %)
1006 +(((
879 879  Temp=0x0898/100=22.00
1008 +)))
880 880  
881 881  (% _msthash="315241" _msttexthash="211783" %)
1011 +(((
882 882  Hum=0x0146/10=32.6
1013 +)))
883 883  
884 884  (% _msthash="315242" _msttexthash="1569776" %)
1016 +(((
885 885  poll message flag & Ext=0x41,means reply data,Ext=1
1018 +)))
886 886  
887 887  (% _msthash="315243" _msttexthash="1120509" %)
1021 +(((
888 888  Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
1023 +)))
889 889  
890 890  
891 891  
892 892  == 2.7 Alarm Mode ==
893 893  
1029 +(((
894 894  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 +)))
895 895  
1033 +(((
896 896  (% 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 +)))
897 897  
1037 +(((
898 898  **AT COMMAND FOR ALARM MODE:**
1039 +)))
899 899  
900 900  (% _mstvisible="1" class="box infomessage" %)
901 901  (((
1043 +(((
902 902  **AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled)
1045 +)))
903 903  
1047 +(((
904 904  **AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
1049 +)))
905 905  
1051 +(((
906 906  **AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
1053 +)))
907 907  
1055 +(((
908 908  **AT+ARTEMP=？ **:  Gets the alarm range of the internal temperature sensor(% _mstvisible="3" style="display:none" %)
1057 +)))
909 909  
1059 +(((
910 910  **AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
911 911  )))
1062 +)))
912 912  
1064 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
913 913  
1066 +Total bytes: 8 bytes
914 914  
1068 +**Example:**AA0100010001003C
915 915  
1070 +WMOD=01
1071 +
1072 +CITEMP=0001
1073 +
1074 +TEMPlow=0001
1075 +
1076 +TEMPhigh=003C
1077 +
1078 +
916 916  == 2.8 LED Indicator ==
917 917  
918 918  The LHT65 has a triple color LED which for easy showing different stage .
... ... @@ -922,10 +922,11 @@
922 922  In a normal working state:
923 923  
924 924  * For each uplink, the BLUE LED or RED LED will blink once.
925 - BLUE LED when external sensor is connected.
1088 +BLUE LED when external sensor is connected.
926 926  * RED LED when external sensor is not connected
927 927  * For each success downlink, the PURPLE LED will blink once
928 928  
1092 +
929 929  == 2.9 installation ==
930 930  
931 931  (% _mstvisible="1" %)
... ... @@ -939,8 +939,24 @@
939 939  
940 940  [[image:image-20220619092222-1.png||height="182" width="188"]][[image:image-20220619092313-2.png||height="182" width="173"]]
941 941  
942 -1m long breakout cable for LHT65N
1106 +**1m long breakout cable for LHT65N. Features:**
943 943  
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 +
944 944  [[image:image-20220619092421-3.png||height="371" width="529"]]
945 945  
946 946  
... ... @@ -960,28 +960,51 @@
960 960  * Operating Range: -40 ~~ 125 °C
961 961  * Working voltage 2.35v ~~ 5v
962 962  
1143 +
963 963  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
964 964  
1146 +(((
965 965  Use can configure LHT65N via AT Command or LoRaWAN Downlink.
1148 +)))
966 966  
967 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
1150 +* (((
1151 +AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
1152 +)))
968 968  
969 -* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
1154 +* (((
1155 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
1156 +)))
970 970  
1158 +(((
971 971  There are two kinds of commands to configure LHT65N, they are:
1160 +)))
972 972  
973 -* (% style="color:#4f81bd" %)**General Commands**.
1162 +* (((
1163 +(% style="color:#4f81bd" %)**General Commands**.
1164 +)))
974 974  
1166 +(((
975 975  These commands are to configure:
1168 +)))
976 976  
977 -1. General system settings like: uplink interval.
978 -1. LoRaWAN protocol & radio-related commands.
1170 +1. (((
1171 +General system settings like: uplink interval.
1172 +)))
1173 +1. (((
1174 +LoRaWAN protocol & radio-related commands.
1175 +)))
979 979  
1177 +(((
980 980  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 +)))
981 981  
982 -* (% style="color:#4f81bd" %)**Commands special design for LHT65N**
1181 +* (((
1182 +(% style="color:#4f81bd" %)**Commands special design for LHT65N**
1183 +)))
983 983  
1185 +(((
984 984  These commands are only valid for LHT65N, as below:
1187 +)))
985 985  
986 986  
987 987  == 4.1 Set Transmit Interval Time ==
... ... @@ -1003,6 +1003,7 @@
1003 1003  
1004 1004  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1005 1005  
1209 +
1006 1006  == 4.2 Set External Sensor Mode ==
1007 1007  
1008 1008  Feature: Change External Sensor Mode.
... ... @@ -1024,6 +1024,7 @@
1024 1024  
1025 1025  * 0xA20702003c: Same as AT+SETCNT=60
1026 1026  
1231 +
1027 1027  == 4.3 Enable/Disable uplink Temperature probe ID ==
1028 1028  
1029 1029  (((
... ... @@ -1051,6 +1051,7 @@
1051 1051  * **0xA800**  **~-~->** AT+PID=0
1052 1052  * **0xA801**     **~-~->** AT+PID=1
1053 1053  
1259 +
1054 1054  == 4.4 Set Password ==
1055 1055  
1056 1056  Feature: Set device password, max 9 digits
... ... @@ -1097,6 +1097,7 @@
1097 1097  
1098 1098  * There is no downlink command to set to Sleep mode.
1099 1099  
1306 +
1100 1100  == 4.7 Set system time ==
1101 1101  
1102 1102  Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
... ... @@ -1193,6 +1193,7 @@
1193 1193  
1194 1194  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1195 1195  
1403 +
1196 1196  == 4.13 Auto Send None-ACK messages ==
1197 1197  
1198 1198  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
... ... @@ -1211,6 +1211,7 @@
1211 1211  
1212 1212  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1213 1213  
1422 +
1214 1214  = 5. Battery & How to replace =
1215 1215  
1216 1216  == 5.1 Battery Type ==
... ... @@ -1270,16 +1270,11 @@
1270 1270  
1271 1271  (% _msthash="506061" _msttexthash="170755" %)**Connection:**
1272 1272  
1273 -(% _msthash="506062" _msttexthash="1187732" %)
1274 -**✓ (% style="background-color:yellow" %)USB to TTL GND <~-~->GND(%%)**
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-**
1275 1275  
1276 -(% _msthash="506063" _msttexthash="1158313" %)**✓  **(% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+**
1277 -
1278 -(% _msthash="506064" _msttexthash="1175629" %)**✓  **(% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11**
1279 -
1280 -(% _msthash="506065" _msttexthash="1164696" %)**✓  **(% style="background-color:yellow" %)**USB to TTL 3.3V <~-~-> D-**
1281 -
1282 -
1283 1283  (((
1284 1284  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.
1285 1285  )))
... ... @@ -1588,7 +1588,59 @@
1588 1588  Finally, unplug the DuPont cable on port4, and then use the DuPont cable to short circuit port3 and port1 to reset the device.
1589 1589  
1590 1590  
1795 +== 6.6 Using USB-TYPE-C to connect to the computer using the AT command ==
1591 1591  
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 +
1592 1592  = 7. Order Info =
1593 1593  
1594 1594  
... ... @@ -1616,6 +1616,7 @@
1616 1616  
1617 1617  * (% style="color:red" %)**E3**(%%): External Temperature Probe
1618 1618  
1875 +
1619 1619  = 8. Packing Info =
1620 1620  
1621 1621  
... ... @@ -1629,10 +1629,12 @@
1629 1629  * Device Size:  10 x 10 x 3.5 cm
1630 1630  * Device Weight: 120.5g
1631 1631  
1889 +
1632 1632  = 9. Reference material =
1633 1633  
1634 1634  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1635 1635  
1894 +
1636 1636  = 10. FCC Warning =
1637 1637  
1638 1638  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
image-20220623110706-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +689.7 KB
Content
image-20220623110723-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +501.5 KB
Content
image-20220623111949-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 MB
Content
image-20220623112117-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +513.9 KB
Content
image-20220623113959-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +834.2 KB
Content
image-20220628150112-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +220.3 KB
Content
image-20220628150542-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +45.6 KB
Content
image-20220628150648-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +8.3 KB
Content
image-20220628150714-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +7.1 KB
Content
image-20220628151005-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +7.3 KB
Content
image-20220628151056-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +8.2 KB
Content
image-20220628151143-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +7.2 KB
Content
image-20220703111533-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +694.5 KB
Content
image-20220703111700-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +369.4 KB
Content