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