Skip to Content
Last modified by Xiaoling on 2023/07/18 10:12
From version 170.26
edited by Xiaoling
on 2022/06/22 11:16
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
... ... @@ -86,24 +86,38 @@
86 86  
87 87  
88 88  
89 -
90 90  = 2. Connect LHT65N to IoT Server =
91 91  
92 92  == 2.1 How does LHT65N work? ==
93 93  
98 +
99 +(((
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.
101 +)))
95 95  
103 +(((
96 96  If LHT65N is under the coverage of this LoRaWAN network. LHT65N can join the LoRaWAN network automatically. After successfully joining, LHT65N will start to measure environment temperature and humidity, and start to transmit sensor data to the LoRaWAN server. The default period for each uplink is 20 minutes.
105 +)))
97 97  
98 98  
108 +
99 99  == 2.2 How to Activate LHT65N? ==
100 100  
111 +
112 +(((
101 101  The LHT65N has two working modes:
114 +)))
102 102  
103 -* (% style="color:blue" %)**Deep Sleep Mode**(%%): LHT65N doesn’t have any LoRaWAN activation. This mode is used for storage and shipping to save battery life.
104 -* (% style="color:blue" %)**Working Mode**(%%):  In this mode, LHT65N works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65N will be in STOP mode (IDLE mode), in STOP mode, LHT65N has the same power consumption as Deep Sleep mode. 
116 +* (((
117 +(% style="color:blue" %)**Deep Sleep Mode**(%%): LHT65N doesn’t have any LoRaWAN activation. This mode is used for storage and shipping to save battery life.
118 +)))
119 +* (((
120 +(% style="color:blue" %)**Working Mode**(%%):  In this mode, LHT65N works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65N will be in STOP mode (IDLE mode), in STOP mode, LHT65N has the same power consumption as Deep Sleep mode. 
121 +)))
105 105  
123 +(((
106 106  The LHT65N is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
125 +)))
107 107  
108 108  
109 109  [[image:image-20220515123819-1.png||_mstalt="430742" _mstvisible="3" height="379" width="317"]]
... ... @@ -114,6 +114,7 @@
114 114  
115 115  == 2.3 Example to join LoRaWAN network ==
116 116  
136 +
117 117  (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
118 118  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.
119 119  
... ... @@ -129,6 +129,7 @@
129 129  
130 130  === 2.3.1 Step 1: Create Device n TTN ===
131 131  
152 +
132 132  (((
133 133  Create a device in TTN V3 with the OTAA keys from LHT65N.
134 134  )))
... ... @@ -153,9 +153,10 @@
153 153  [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
154 154  
155 155  
156 -Note: LHT65N use same payload as LHT65.
157 157  
178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
158 158  
180 +
159 159  [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
160 160  
161 161  
... ... @@ -169,6 +169,7 @@
169 169  
170 170  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
171 171  
194 +
172 172  (((
173 173  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.
174 174  )))
... ... @@ -180,6 +180,7 @@
180 180  
181 181  == 2.4 Uplink Payload ==
182 182  
206 +
183 183  (((
184 184  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.
185 185  )))
... ... @@ -254,11 +254,13 @@
254 254  
255 255  * The First 6 bytes: has fix meanings for every LHT65N.
256 256  * The 7th byte (EXT #): defines the external sensor model.
257 -* 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.)
258 258  
259 259  
284 +
260 260  === 2.4.1 Decoder in TTN V3 ===
261 261  
287 +
262 262  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.
263 263  
264 264  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -274,6 +274,7 @@
274 274  
275 275  === 2.4.2 BAT-Battery Info ===
276 276  
303 +
277 277  These two bytes of BAT include the battery state and the actually voltage
278 278  
279 279  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -287,8 +287,11 @@
287 287  * BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
288 288  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
289 289  
317 +
318 +
290 290  === 2.4.3 Built-in Temperature ===
291 291  
321 +
292 292  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
293 293  
294 294  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -297,14 +297,20 @@
297 297  
298 298  * Temperature:  (0xF5C6-65536)/100=-26.18℃
299 299  
330 +
331 +
300 300  === 2.4.4 Built-in Humidity ===
301 301  
334 +
302 302  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
303 303  
304 304  * Humidity:    0x025C/10=60.4%
305 305  
339 +
340 +
306 306  === 2.4.5 Ext # ===
307 307  
343 +
308 308  Bytes for External Sensor:
309 309  
310 310  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -336,6 +336,7 @@
336 336  
337 337  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
338 338  
375 +
339 339  (((
340 340  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:
341 341  )))
... ... @@ -449,14 +449,19 @@
449 449  
450 450  * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
451 451  
452 -[[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)
453 453  
454 -* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
455 -* 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.
456 -* 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)
457 457  
497 +
498 +
458 458  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
459 459  
501 +
460 460  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
461 461  
462 462  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -465,10 +465,46 @@
465 465  
466 466  AT+EXT=6,timeout  (% _msthash="506085" _msttexthash="8782189" _mstvisible="3" style="color:red" %)Time to power this sensor, from 0 ~~ 65535ms
467 467  
510 +For example:
468 468  
512 +AT+EXT=6,1000 will power this sensor for 1000ms before sampling the ADC value.
469 469  
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 +
470 470  == 2.5 Show data on Datacake ==
471 471  
549 +
472 472  (((
473 473  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:
474 474  )))
... ... @@ -516,6 +516,7 @@
516 516  
517 517  == 2.6 Datalog Feature ==
518 518  
597 +
519 519  (((
520 520  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.
521 521  )))
... ... @@ -524,12 +524,17 @@
524 524  
525 525  === 2.6.1 Ways to get datalog via LoRaWAN ===
526 526  
606 +
527 527  There are two methods:
528 528  
529 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
530 -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.
531 531  
612 +Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
532 532  
614 +[[image:image-20220703111700-2.png||height="381" width="1119"]]
615 +
616 +
533 533  === 2.6.2 Unix TimeStamp ===
534 534  
535 535  
... ... @@ -552,25 +552,44 @@
552 552  
553 553  === 2.6.3 Set Device Time ===
554 554  
639 +
640 +(((
555 555  There are two ways to set device's time:
642 +)))
556 556  
644 +(((
557 557  **~1. Through LoRaWAN MAC Command (Default settings)**
646 +)))
558 558  
648 +(((
559 559  User need to set SYNCMOD=1 to enable sync time via MAC command.
650 +)))
560 560  
652 +(((
561 561  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 +)))
562 562  
563 -(% 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 +)))
564 564  
660 +(((
661 +
662 +)))
565 565  
664 +(((
566 566  **2. Manually Set Time**
666 +)))
567 567  
668 +(((
568 568  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 +)))
569 569  
570 570  
571 571  
572 572  === 2.6.4 Poll sensor value ===
573 573  
676 +
574 574  User can poll sensor value based on timestamps from the server. Below is the downlink command.
575 575  
576 576  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -588,6 +588,7 @@
588 588  
589 589  === 2.6.5 Datalog Uplink payload ===
590 590  
694 +
591 591  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
592 592  The Datalog poll reply uplink will use below payload format.
593 593  
... ... @@ -594,6 +594,9 @@
594 594  (% _mstvisible="1" %)
595 595  (((
596 596  (% _mstvisible="2" %)
701 +
702 +
703 +(% _mstvisible="2" %)
597 597  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
598 598  )))
599 599  
... ... @@ -721,6 +721,7 @@
721 721  )))
722 722  )))
723 723  
831 +
724 724  (% _mstvisible="1" %)
725 725  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
726 726  
... ... @@ -732,9 +732,11 @@
732 732  (% _mstvisible="2" %)
733 733  (((
734 734  (% _msthash="736723" _msttexthash="2005003" _mstvisible="3" %)
843 +(((
735 735  Poll Message Flag: 1: This message is a poll message reply.
736 736  )))
737 737  )))
847 +)))
738 738  
739 739  (% _mstvisible="1" %)
740 740  * (% _mstvisible="3" %)
... ... @@ -742,17 +742,21 @@
742 742  (% _mstvisible="4" %)
743 743  (((
744 744  (% _msthash="1197157" _msttexthash="561548" _mstvisible="5" %)
855 +(((
745 745  Poll Message Flag is set to 1.
746 746  )))
747 747  )))
859 +)))
748 748  * (% _mstvisible="3" %)
749 749  (((
750 750  (% _mstvisible="4" %)
751 751  (((
752 752  (% _msthash="1197158" _msttexthash="9284964" _mstvisible="5" %)
865 +(((
753 753  Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
754 754  )))
755 755  )))
869 +)))
756 756  
757 757  (% _mstvisible="1" %)
758 758  (((
... ... @@ -759,12 +759,16 @@
759 759  (% _mstvisible="2" %)
760 760  (((
761 761  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
876 +(((
762 762  
878 +)))
763 763  
764 764  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
881 +(((
765 765  For example, in US915 band, the max payload for different DR is:
766 766  )))
767 767  )))
885 +)))
768 768  
769 769  (% _mstvisible="1" %)
770 770  (((
... ... @@ -771,9 +771,11 @@
771 771  (% _mstvisible="2" %)
772 772  (((
773 773  (% _msthash="736725" _msttexthash="1065532" _mstvisible="3" %)
892 +(((
774 774  a) DR0: max is 11 bytes so one entry of data
775 775  )))
776 776  )))
896 +)))
777 777  
778 778  (% _mstvisible="1" %)
779 779  (((
... ... @@ -780,9 +780,11 @@
780 780  (% _mstvisible="2" %)
781 781  (((
782 782  (% _msthash="736726" _msttexthash="3265665" _mstvisible="3" %)
903 +(((
783 783  b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
784 784  )))
785 785  )))
907 +)))
786 786  
787 787  (% _mstvisible="1" %)
788 788  (((
... ... @@ -789,9 +789,11 @@
789 789  (% _mstvisible="2" %)
790 790  (((
791 791  (% _msthash="736727" _msttexthash="1454115" _mstvisible="3" style="text-align: left;" %)
914 +(((
792 792  c) DR2: total payload includes 11 entries of data
793 793  )))
794 794  )))
918 +)))
795 795  
796 796  (% _mstvisible="1" %)
797 797  (((
... ... @@ -798,9 +798,11 @@
798 798  (% _mstvisible="2" %)
799 799  (((
800 800  (% _msthash="736728" _msttexthash="1483924" _mstvisible="3" style="text-align: left;" %)
925 +(((
801 801  d) DR3: total payload includes 22 entries of data.
802 802  )))
803 803  )))
929 +)))
804 804  
805 805  (% _mstvisible="1" %)
806 806  (((
... ... @@ -807,9 +807,11 @@
807 807  (% _mstvisible="2" %)
808 808  (((
809 809  (% _msthash="736729" _msttexthash="5848349" _mstvisible="3" style="text-align: left;" %)
936 +(((
810 810  If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0   
811 811  )))
812 812  )))
940 +)))
813 813  
814 814  
815 815  (% _mstvisible="1" style="text-align: left;" %)
... ... @@ -836,7 +836,7 @@
836 836  (% _mstvisible="1" %)
837 837  (((
838 838  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
839 - 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
840 840  )))
841 841  
842 842  (% _mstvisible="1" %)
... ... @@ -855,55 +855,99 @@
855 855  [[image:image-20220523001219-13.png||_mstalt="451204" _mstvisible="3" height="421" style="text-align:left" width="727"]]
856 856  
857 857  (% _msthash="315271" _msttexthash="12012546" _mstvisible="1" style="text-align: left;" %)
986 +(((
858 858  7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
988 +)))
859 859  
860 860  (% _msthash="315237" _msttexthash="1385839" %)
991 +(((
861 861  Where the first 11 bytes is for the first entry:
993 +)))
862 862  
863 863  (% _msthash="315238" _msttexthash="274846" %)
996 +(((
864 864  7FFF089801464160065F97
998 +)))
865 865  
866 866  (% _msthash="315239" _msttexthash="617435" %)
1001 +(((
867 867  Ext sensor data=0x7FFF/100=327.67
1003 +)))
868 868  
869 869  (% _msthash="315240" _msttexthash="270543" %)
1006 +(((
870 870  Temp=0x0898/100=22.00
1008 +)))
871 871  
872 872  (% _msthash="315241" _msttexthash="211783" %)
1011 +(((
873 873  Hum=0x0146/10=32.6
1013 +)))
874 874  
875 875  (% _msthash="315242" _msttexthash="1569776" %)
1016 +(((
876 876  poll message flag & Ext=0x41,means reply data,Ext=1
1018 +)))
877 877  
878 878  (% _msthash="315243" _msttexthash="1120509" %)
1021 +(((
879 879  Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
1023 +)))
880 880  
881 881  
882 882  
883 883  == 2.7 Alarm Mode ==
884 884  
1029 +(((
885 885  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 +)))
886 886  
1033 +(((
887 887  (% 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 +)))
888 888  
1037 +(((
889 889  **AT COMMAND FOR ALARM MODE:**
1039 +)))
890 890  
891 891  (% _mstvisible="1" class="box infomessage" %)
892 892  (((
1043 +(((
893 893  **AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled)
1045 +)))
894 894  
1047 +(((
895 895  **AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
1049 +)))
896 896  
1051 +(((
897 897  **AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
1053 +)))
898 898  
1055 +(((
899 899  **AT+ARTEMP=？ **:  Gets the alarm range of the internal temperature sensor(% _mstvisible="3" style="display:none" %)
1057 +)))
900 900  
1059 +(((
901 901  **AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
902 902  )))
1062 +)))
903 903  
1064 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
904 904  
1066 +Total bytes: 8 bytes
905 905  
1068 +**Example:**AA0100010001003C
906 906  
1070 +WMOD=01
1071 +
1072 +CITEMP=0001
1073 +
1074 +TEMPlow=0001
1075 +
1076 +TEMPhigh=003C
1077 +
1078 +
907 907  == 2.8 LED Indicator ==
908 908  
909 909  The LHT65 has a triple color LED which for easy showing different stage .
... ... @@ -913,7 +913,7 @@
913 913  In a normal working state:
914 914  
915 915  * For each uplink, the BLUE LED or RED LED will blink once.
916 - BLUE LED when external sensor is connected.
1088 +BLUE LED when external sensor is connected.
917 917  * RED LED when external sensor is not connected
918 918  * For each success downlink, the PURPLE LED will blink once
919 919  
... ... @@ -931,8 +931,24 @@
931 931  
932 932  [[image:image-20220619092222-1.png||height="182" width="188"]][[image:image-20220619092313-2.png||height="182" width="173"]]
933 933  
934 -1m long breakout cable for LHT65N
1106 +**1m long breakout cable for LHT65N. Features:**
935 935  
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 +
936 936  [[image:image-20220619092421-3.png||height="371" width="529"]]
937 937  
938 938  
... ... @@ -955,26 +955,48 @@
955 955  
956 956  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
957 957  
1146 +(((
958 958  Use can configure LHT65N via AT Command or LoRaWAN Downlink.
1148 +)))
959 959  
960 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
1150 +* (((
1151 +AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
1152 +)))
961 961  
962 -* 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 +)))
963 963  
1158 +(((
964 964  There are two kinds of commands to configure LHT65N, they are:
1160 +)))
965 965  
966 -* (% style="color:#4f81bd" %)**General Commands**.
1162 +* (((
1163 +(% style="color:#4f81bd" %)**General Commands**.
1164 +)))
967 967  
1166 +(((
968 968  These commands are to configure:
1168 +)))
969 969  
970 -1. General system settings like: uplink interval.
971 -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 +)))
972 972  
1177 +(((
973 973  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 +)))
974 974  
975 -* (% style="color:#4f81bd" %)**Commands special design for LHT65N**
1181 +* (((
1182 +(% style="color:#4f81bd" %)**Commands special design for LHT65N**
1183 +)))
976 976  
1185 +(((
977 977  These commands are only valid for LHT65N, as below:
1187 +)))
978 978  
979 979  
980 980  == 4.1 Set Transmit Interval Time ==
... ... @@ -996,6 +996,7 @@
996 996  
997 997  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
998 998  
1209 +
999 999  == 4.2 Set External Sensor Mode ==
1000 1000  
1001 1001  Feature: Change External Sensor Mode.
... ... @@ -1017,6 +1017,7 @@
1017 1017  
1018 1018  * 0xA20702003c: Same as AT+SETCNT=60
1019 1019  
1231 +
1020 1020  == 4.3 Enable/Disable uplink Temperature probe ID ==
1021 1021  
1022 1022  (((
... ... @@ -1044,6 +1044,7 @@
1044 1044  * **0xA800**  **~-~->** AT+PID=0
1045 1045  * **0xA801**     **~-~->** AT+PID=1
1046 1046  
1259 +
1047 1047  == 4.4 Set Password ==
1048 1048  
1049 1049  Feature: Set device password, max 9 digits
... ... @@ -1206,6 +1206,7 @@
1206 1206  
1207 1207  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1208 1208  
1422 +
1209 1209  = 5. Battery & How to replace =
1210 1210  
1211 1211  == 5.1 Battery Type ==
... ... @@ -1265,16 +1265,11 @@
1265 1265  
1266 1266  (% _msthash="506061" _msttexthash="170755" %)**Connection:**
1267 1267  
1268 -(% _msthash="506062" _msttexthash="1187732" %)
1269 -**✓ (% 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-**
1270 1270  
1271 -(% _msthash="506063" _msttexthash="1158313" %)**✓  **(% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+**
1272 -
1273 -(% _msthash="506064" _msttexthash="1175629" %)**✓  **(% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11**
1274 -
1275 -(% _msthash="506065" _msttexthash="1164696" %)**✓  **(% style="background-color:yellow" %)**USB to TTL 3.3V <~-~-> D-**
1276 -
1277 -
1278 1278  (((
1279 1279  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.
1280 1280  )))
... ... @@ -1583,7 +1583,59 @@
1583 1583  Finally, unplug the DuPont cable on port4, and then use the DuPont cable to short circuit port3 and port1 to reset the device.
1584 1584  
1585 1585  
1795 +== 6.6 Using USB-TYPE-C to connect to the computer using the AT command ==
1586 1586  
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 +
1587 1587  = 7. Order Info =
1588 1588  
1589 1589  
... ... @@ -1625,10 +1625,12 @@
1625 1625  * Device Size:  10 x 10 x 3.5 cm
1626 1626  * Device Weight: 120.5g
1627 1627  
1889 +
1628 1628  = 9. Reference material =
1629 1629  
1630 1630  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1631 1631  
1894 +
1632 1632  = 10. FCC Warning =
1633 1633  
1634 1634  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