<
From version < 55.4 >
edited by Xiaoling
on 2022/05/23 11:51
To version < 55.1 >
edited by Xiaoling
on 2022/05/23 11:22
>
Change comment: Uploaded new attachment "image-20220523112300-2.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,19 +4,18 @@
1 -(% style="text-align:center" %)
2 -[[image:image-20220523111447-1.jpeg||height="448" width="448"]]
3 -
4 4  {{box cssClass="floatinginfobox" title="**Contents**"}}
5 5  {{toc/}}
6 6  {{/box}}
7 7  
8 -{{toc/}}
5 +(% class="wikigeneratedid" %)
6 += =
9 9  
10 -
11 -
8 +(% class="wikigeneratedid" %)
12 12  = 1.Introduction =
13 13  
14 -== 1.1 What is LHT65N Temperature & Humidity Sensor ==
11 +== 1.1 Overview ==
15 15  
13 +[[image:LHT65N_10.png||alt="LHT65_Image" height="265" width="265"]]
16 16  
15 +
17 17  The Dragino LHT65N Temperature & Humidity sensor is a Long Range LoRaWAN Sensor. It includes a(% class="mark" %) **built-in Temperature & Humidity sensor**(%%) and has an external sensor connector to connect to an external (% class="mark" %)**Temperature Sensor**(%%)**.**
18 18  
19 19  The LHT65N allows users to send data and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, building automation, and so on.
... ... @@ -26,8 +26,9 @@
26 26  
27 27  *The actual battery life depends on how often to send data, please see the battery analyzer chapter.
28 28  
29 -== 1.2 Features ==
30 30  
29 +== Features: ==
30 +
31 31  * Wall mountable
32 32  * LoRaWAN v1.0.3 Class A protocol
33 33  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
... ... @@ -40,7 +40,7 @@
40 40  * Tri-color LED to indicate working status
41 41  * Datalog feature
42 42  
43 -== 1.3 Specification ==
43 +== Specification: ==
44 44  
45 45  **Built-in Temperature Sensor:**
46 46  
... ... @@ -63,9 +63,9 @@
63 63  * ±2°C accuracy from -55°C to +125°C
64 64  * Operating Range: -55 °C ~~ 125 °C
65 65  
66 -= 2. Connect LHT65N to IoT Server =
66 += Connect LHT65N to IoT Server =
67 67  
68 -== 2.1 How does LHT65N work? ==
68 +== How does LHT65N work? ==
69 69  
70 70  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.
71 71  
... ... @@ -72,7 +72,7 @@
72 72  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.
73 73  
74 74  
75 -== 2.2 How to Activate LHT65N? ==
75 +== How to Activate LHT65N? ==
76 76  
77 77  The LHT65N has two working modes:
78 78  
... ... @@ -83,13 +83,12 @@
83 83  
84 84  [[image:image-20220515123819-1.png||height="379" width="317"]]
85 85  
86 -(% border="1" %)
87 87  |**Behavior on ACT**|**Function**|**Action**
88 88  |**Pressing ACT between 1s < time < 3s**|Test uplink status|If LHT65N is already Joined to the LoRaWAN network, LHT65N will send an uplink packet, if LHT65N has an external sensor connected, blue led will blink once. If LHT65N has no external sensor, red led will blink once.
89 89  |**Pressing ACT for more than 3s**|Active Device|green led will fast blink 5 times, LHT65N will enter working mode and start to JOIN LoRaWAN network. green led will solid turn on for 5 seconds after join in network.
90 90  |**Fast press ACT 5 times**|Deactivate Device|red led will solid on for 5 seconds. This means LHT65N is in Deep Sleep Mode.
91 91  
92 -== 2.3 Example to join LoRaWAN network ==
91 +== Example to join LoRaWAN network ==
93 93  
94 94  (% class="wikigeneratedid" %)
95 95  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.
... ... @@ -100,7 +100,7 @@
100 100  Assume the LPS8N is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network]], So it provides network coverage for LHT65N. Next we need to add the LHT65N device in TTN V3:
101 101  
102 102  
103 -=== 2.3.1 Step 1: Create Device n TTN ===
102 +=== **Step 1**: Create Device n TTN ===
104 104  
105 105  Create a device in TTN V3 with the OTAA keys from LHT65N.
106 106  
... ... @@ -130,7 +130,7 @@
130 130  [[image:image-20220522233118-7.png]]
131 131  
132 132  
133 -=== 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
132 +=== Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
134 134  
135 135  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.
136 136  
... ... @@ -137,7 +137,7 @@
137 137  [[image:image-20220522233300-8.png]]
138 138  
139 139  
140 -== 2.4 Uplink Payload ==
139 +== Uplink Payload: ==
141 141  
142 142  The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and(% class="mark" %) every 20 minutes(%%) send one uplink by default.
143 143  
... ... @@ -144,7 +144,7 @@
144 144  After each uplink, the (% class="mark" %)BLUE LED(%%) will blink once.
145 145  
146 146  
147 -(% border="1" style="width:572px" %)
146 +(% style="width:572px" %)
148 148  |(% style="width:106px" %)**Size(bytes)**|(% style="width:71px" %)**2**|(% style="width:128px" %)**2**|(% style="width:103px" %)**2**|(% style="width:72px" %)**1**|(% style="width:89px" %)**4**
149 149  |(% style="width:106px" %)**Value**|(% style="width:71px" %)[[BAT>>path:#Battery]]|(% style="width:128px" %)(((
150 150  [[Built-In>>path:#SHT20_Temperature]]
... ... @@ -160,7 +160,7 @@
160 160  * The 7th byte (EXT #): defines the external sensor model.
161 161  * The 8^^th^^ ~~ 11^^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.)
162 162  
163 -=== 2.4.1 Decoder in TTN V3 ===
162 +=== Decoder in TTN V3 ===
164 164  
165 165  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.
166 166  
... ... @@ -171,7 +171,7 @@
171 171  [[image:image-20220522234118-10.png]]
172 172  
173 173  
174 -=== 2.4.2 BAT-Battery Info ===
173 +=== BAT-Battery Info ===
175 175  
176 176  These two bytes of BAT include the battery state and the actually voltage
177 177  
... ... @@ -196,7 +196,7 @@
196 196  * BAT status=(0Xcba4>>14)&0xFF=11(B),very good
197 197  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
198 198  
199 -=== 2.4.3 Built-in Temperature ===
198 +=== Built-in Temperature ===
200 200  
201 201  [[image:image-20220522235639-2.png]]
202 202  
... ... @@ -206,13 +206,13 @@
206 206  
207 207  * Temperature:  (0xF5C6-65536)/100=-26.18℃
208 208  
209 -=== 2.4.4 Built-in Humidity ===
208 +=== Built-in Humidity ===
210 210  
211 211  [[image:image-20220522235639-4.png]]
212 212  
213 213  * Humidity:    0x025C/10=60.4%
214 214  
215 -=== 2.4.5 Ext # ===
214 +=== Ext # ===
216 216  
217 217  Bytes for External Sensor:
218 218  
... ... @@ -221,16 +221,19 @@
221 221  |(% style="width:139px" %)0x01|(% style="width:484px" %)Sensor E3, Temperature Sensor
222 222  |(% style="width:139px" %)0x09|(% style="width:484px" %)Sensor E3, Temperature Sensor, Datalog Mod
223 223  
224 -=== 2.4.6 Ext value ===
223 +=== Ext value ===
225 225  
226 -==== 2.4.6.1 Ext~=1, E3 Temperature Sensor ====
225 +==== Ext~=1, E3 Temperature Sensor ====
227 227  
228 228  [[image:image-20220522235639-5.png]]
229 229  
229 +
230 230  * DS18B20 temp=0x0ADD/100=27.81℃
231 231  
232 232  The last 2 bytes of data are meaningless
233 233  
234 +
235 +
234 234  [[image:image-20220522235639-6.png]]
235 235  
236 236  * External temperature= (0xF54F-65536)/100=-27.37℃
... ... @@ -237,15 +237,16 @@
237 237  
238 238  The last 2 bytes of data are meaningless
239 239  
242 +
240 240  If the external sensor is 0x01, and there is no external temperature connected. The temperature will be set to 7FFF which is 327.67℃
241 241  
242 242  
243 -==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
246 +==== Ext~=9, E3 sensor with Unix Timestamp ====
244 244  
245 245  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:
246 246  
247 247  
248 -(% border="1" style="width:697px" %)
251 +(% style="width:697px" %)
249 249  |(% style="width:96px" %)**Size(bytes)**|(% style="width:164px" %)**2**|(% style="width:104px" %)**2**|(% style="width:106px" %)**2**|(% style="width:108px" %)**1**|(% style="width:116px" %)**4**
250 250  |(% style="width:96px" %)**Value**|(% style="width:164px" %)[[External temperature>>path:#DS18b20_value]]|(% style="width:104px" %)(((
251 251  [[Built-In>>path:#SHT20_Temperature]]
... ... @@ -263,9 +263,9 @@
263 263  [[Time Stamp>>path:#Unix_Time_Stamp]]
264 264  )))
265 265  
266 -* **Battery status & **[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Built-in Humidity**>>path:#SHT20_Humidity]]
269 +* **Battery status & **[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Built-in Humidity**>>path:#SHT20_Humidity]]
267 267  
268 -(% border="1" style="width:587px" %)
271 +(% style="width:587px" %)
269 269  |Bit(bit)|(% style="width:280px" %)[15:14]|(% style="width:136px" %)[11:0]
270 270  |Value|(% style="width:280px" %)(((
271 271  BAT Status
... ... @@ -285,7 +285,7 @@
285 285  
286 286  * **Status & Ext Byte**
287 287  
288 -(% border="1" style="width:732px" %)
291 +(% style="width:732px" %)
289 289  |(% style="width:128px" %)**Bits**|(% style="width:102px" %)**7**|(% style="width:145px" %)**6**|(% style="width:117px" %)**5**|(% style="width:147px" %)**4**|(% style="width:90px" %)**[3:0]**
290 290  |(% style="width:128px" %)**Status & Ext**|(% style="width:102px" %)Not Defined|(% style="width:145px" %)Poll Message Flag|(% style="width:117px" %)Sync time OK|(% style="width:147px" %)Unix Time Request|(% style="width:90px" %)(((
291 291  Ext:
... ... @@ -297,10 +297,11 @@
297 297  * 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.
298 298  * 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)
299 299  
300 -== 2.5 Show data on Datacake ==
303 +== Show data on Datacake ==
301 301  
302 302  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:
303 303  
307 +
304 304  **Step 1**: Be sure that your device is programmed and properly connected to the LoRaWAN network.
305 305  
306 306  **Step 2**: Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations.
... ... @@ -325,11 +325,11 @@
325 325  [[image:image-20220523000825-10.png||height="432" width="762"]]
326 326  
327 327  
328 -== 2.6 Datalog Feature ==
332 +== Datalog Feature ==
329 329  
330 330  This feature is always enabled. When user wants to retrieve the sensor value, he can send a poll command from the IoT platform to ask LHT65N to send the value in the required time slot.
331 331  
332 -=== 2.6.1 Unix TimeStamp ===
336 +=== Unix TimeStamp ===
333 333  
334 334  LHT65N uses Unix TimeStamp format based on
335 335  
... ... @@ -340,12 +340,12 @@
340 340  
341 341  Below is the converter example
342 342  
343 -[[image:image-20220523001219-12.png||height="302" width="730"]]
347 +[[image:image-20220523001219-12.png||height="353" width="853"]]
344 344  
345 345  So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
346 346  
347 347  
348 -=== 2.6.2 Set Device Time ===
352 +=== Set Device Time ===
349 349  
350 350  There are two ways to set device’s time:
351 351  
... ... @@ -363,12 +363,12 @@
363 363  User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
364 364  
365 365  
366 -=== 2.6.3 Poll sensor value ===
370 +=== Poll sensor value ===
367 367  
368 368  User can poll sensor value based on timestamps from the server. Below is the downlink command.
369 369  
370 370  
371 -(% border="1" style="width:454px" %)
375 +(% style="width:454px" %)
372 372  |(% style="width:69px" %)1byte|(% style="width:129px" %)4bytes|(% style="width:134px" %)4bytes|(% style="width:119px" %)1byte
373 373  |(% style="width:69px" %)31|(% style="width:129px" %)Timestamp start|(% style="width:134px" %)Timestamp end|(% style="width:119px" %)Uplink Interval
374 374  
... ... @@ -382,7 +382,7 @@
382 382  Uplink Internal =5s,means LHT65N will send one packet every 5s. range 5~~255s.
383 383  
384 384  
385 -=== 2.6.4 Datalog Uplink payload ===
389 +=== Datalog Uplink payload ===
386 386  
387 387  The Datalog poll reply uplink will use below payload format.
388 388  
... ... @@ -389,7 +389,6 @@
389 389  
390 390  Retrieval data payload
391 391  
392 -(% border="1" %)
393 393  |**Size(bytes)**|**2**|**2**|**2**|**1**|**4**
394 394  |**Value**|[[External sensor data>>path:#Extension_sensor_value]]|(((
395 395  [[Built-In>>path:#SHT20_Temperature]]
... ... @@ -408,7 +408,6 @@
408 408  Poll message flag & Ext
409 409  
410 410  
411 -(% border="1" %)
412 412  |**Bits**|**7**|**6**|**5**|**4**|**[3:0]**
413 413  |**Status & Ext**|Not Defined|Poll Message Flag|Sync time OK|Unix Time Request|(((
414 414  Ext:
... ... @@ -468,7 +468,7 @@
468 468  
469 469  LHT65N will uplink this payload.
470 470  
471 -[[image:image-20220523001219-13.png||height="421" width="727"]]
473 +[[image:image-20220523001219-13.png]]
472 472  
473 473  7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
474 474  
... ... @@ -487,7 +487,7 @@
487 487  Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
488 488  
489 489  
490 -== 2.7 Alarm Mode ==
492 +== Alarm Mode ==
491 491  
492 492  Alarm mode feature is added since firmware v1.5. When device is in Alarm mode, it will check the built-in sensor temperature in a short interval. If the temperature exceeds the pre-configure range, it will send an uplink immediately.
493 493  
... ... @@ -503,7 +503,7 @@
503 503  
504 504  
505 505  
506 -== 2.8 LED Indicator ==
508 +== LED Indicator ==
507 507  
508 508  The LHT65N has a triple color LED which for easy shows different stage.
509 509  
... ... @@ -518,14 +518,17 @@
518 518  
519 519  ----
520 520  
521 -== 2.9 Installation ==
523 +== Installation ==
522 522  
523 523  [[image:image-20220516231650-1.png||height="436" width="428"]]
524 524  
525 -= 3. Sensors & Accessories =
526 526  
527 -== 3.1 E3 Temperature Probe ==
528 528  
529 +
530 += Sensors & Accessories =
531 +
532 +== E3 Temperature Probe ==
533 +
529 529  [[image:image-20220515080154-4.png||height="182" width="161"]] [[image:image-20220515080330-5.png||height="201" width="195"]]
530 530  
531 531  
... ... @@ -538,7 +538,7 @@
538 538  * -55°C to 125°C
539 539  * Working voltage 2.35v ~~ 5v
540 540  
541 -= 4. Configure LHT65N via AT Command or LoRaWAN Downlink =
546 += Configure LHT65N via AT Command or LoRaWAN Downlink =
542 542  
543 543  Use can configure LHT65N via AT Command or LoRaWAN Downlink.
544 544  
... ... @@ -547,6 +547,7 @@
547 547  
548 548  [[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#Use_Note_for_Server>>url:http://wiki.dragino.com/index.php?title=Main_Page#Use_Note_for_Server]]
549 549  
555 +
550 550  There are two kinds of commands to configure LHT65N, they are:
551 551  
552 552  * **General Commands**.
... ... @@ -560,17 +560,19 @@
560 560  
561 561  [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_Downlink_Command>>url:http://wiki.dragino.com/index.php?title=End_Device_Downlink_Command]]
562 562  
569 +
570 +
563 563  * **Commands special design for LHT65N**
564 564  
565 565  These commands are only valid for LHT65N, as below:
566 566  
567 -== 4.1 Set Transmit Interval Time ==
568 568  
576 +== Set Transmit Interval Time ==
577 +
569 569  Feature: Change LoRaWAN End Node Transmit Interval.
570 570  
571 571  **AT Command: AT+TDC**
572 572  
573 -(% border="1" %)
574 574  |**Command Example**|**Function**|**Response**
575 575  |AT+TDC?|Show current transmit Interval|(((
576 576  30000
... ... @@ -594,13 +594,12 @@
594 594  * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
595 595  * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
596 596  
597 -== 4.2 Set External Sensor Mode ==
605 +== Set External Sensor Mode ==
598 598  
599 599  Feature: Change External Sensor Mode.
600 600  
601 601  **AT Command: AT+EXT**
602 602  
603 -(% border="1" %)
604 604  |**Command Example**|**Function**|**Response**
605 605  |AT+EXT?|Get current external sensor mode|(((
606 606  1
... ... @@ -622,7 +622,7 @@
622 622  * 0xA209: Same as AT+EXT=9
623 623  * 0xA20702003c,Same as AT+SETCNT=60
624 624  
625 -== 4.3 Enable/Disable uplink Temperature probe ID ==
632 +== Enable/Disable uplink Temperature probe ID ==
626 626  
627 627  Feature: If PID is enabled, device will send the temperature probe ID on:
628 628  
... ... @@ -634,7 +634,6 @@
634 634  
635 635  **AT Command:**
636 636  
637 -(% border="1" %)
638 638  |**Command Example**|**Function**|**Response**
639 639  |AT+PID=1|Enable PID uplink|OK
640 640  
... ... @@ -643,13 +643,13 @@
643 643  * 0xA800     à AT+PID=0
644 644  * 0xA801     à AT+PID=1
645 645  
646 -== 4.4 Set Password ==
647 647  
653 +== Set Password ==
654 +
648 648  Feature: Set device password, max 9 digits
649 649  
650 650  **AT Command: AT+PWORD**
651 651  
652 -(% border="1" %)
653 653  |**Command Example**|**Function**|**Response**
654 654  |AT+PWORD=?|Show password|(((
655 655  123456
... ... @@ -663,13 +663,13 @@
663 663  
664 664  No downlink command for this feature.
665 665  
666 -== 4.5 Quit AT Command ==
667 667  
673 +== Quit AT Command ==
674 +
668 668  Feature: Quit AT Command mode, so user needs to input password again before use AT Commands.
669 669  
670 670  **AT Command: AT+DISAT**
671 671  
672 -(% border="1" %)
673 673  |**Command Example**|**Function**|**Response**
674 674  |AT+DISAT|Quit AT Commands mode|OK
675 675  
... ... @@ -678,13 +678,12 @@
678 678  No downlink command for this feature.
679 679  
680 680  
681 -== 4.6 Set to sleep mode ==
687 +== Set to sleep mode ==
682 682  
683 683  Feature: Set device to sleep mode
684 684  
685 685  **AT Command: AT+SLEEP**
686 686  
687 -(% border="1" %)
688 688  | | |
689 689  |**Command Example**|**Function**|**Response**
690 690  |AT+SLEEP|Set to sleep mode|(((
... ... @@ -697,13 +697,13 @@
697 697  
698 698  * There is no downlink command to set to Sleep mode.
699 699  
700 -== 4.7 Set system time ==
701 701  
706 +== Set system time ==
707 +
702 702  Feature: Set system time, unix format. [[See here for format detail.>>path:#TimeStamp]]
703 703  
704 704  **AT Command:**
705 705  
706 -(% border="1" %)
707 707  |**Command Example**|**Function**
708 708  |AT+TIMESTAMP=1611104352|(((
709 709  OK
... ... @@ -715,10 +715,12 @@
715 715  
716 716  0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
717 717  
718 -== 4.8 Set Time Sync Mode ==
719 719  
724 +== Set Time Sync Mode ==
725 +
720 720  Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
721 721  
728 +
722 722  SYNCMOD is set to 1 by default. If user want to set a different time from LoRaWAN server, user need to set this to 0.
723 723  
724 724  
... ... @@ -733,13 +733,13 @@
733 733  
734 734  0x28 00 ~/~/ Same As AT+SYNCMOD=0
735 735  
736 -== 4.9 Set Time Sync Interval ==
737 737  
744 +== Set Time Sync Interval ==
745 +
738 738  Feature: Define System time sync interval. SYNCTDC default value: 10 days.
739 739  
740 740  **AT Command:**
741 741  
742 -(% border="1" %)
743 743  |**Command Example**|**Function**
744 744  |AT+SYNCTDC=0x0A|Set SYNCTDC to 10 (0x0A), so the sync time is 10 days.
745 745  
... ... @@ -747,13 +747,13 @@
747 747  
748 748  0x29 0A ~/~/ Same as AT+SYNCTDC=0x0A
749 749  
750 -== 4.10 Print data entries base on page. ==
751 751  
758 +== Print data entries base on page. ==
759 +
752 752  Feature: Print the sector data from start page to stop page (max is 416 pages).
753 753  
754 754  **AT Command: AT+PDTA**
755 755  
756 -(% border="1" %)
757 757  |**Command Example**|**Response**
758 758  |(((
759 759  AT+PDTA=1,3
... ... @@ -802,13 +802,14 @@
802 802  
803 803  No downlink commands for feature
804 804  
805 -== 4.11 Print last few data entries. ==
806 806  
813 +
814 +== Print last few data entries. ==
815 +
807 807  Feature: Print the last few data entries
808 808  
809 809  **AT Command: AT+PLDTA**
810 810  
811 -(% border="1" %)
812 812  |**Command Example**|**Response**
813 813  |(((
814 814  AT+PLDTA=5
... ... @@ -838,13 +838,14 @@
838 838  
839 839  No downlink commands for feature
840 840  
841 -== 4.12 Clear Flash Record ==
842 842  
850 +
851 +== Clear Flash Record ==
852 +
843 843  Feature: Clear flash storage for data log feature.
844 844  
845 845  **AT Command: AT+CLRDTA**
846 846  
847 -(% border="1" %)
848 848  |**Command Example**|**Function**|**Response**
849 849  |AT+CLRDTA|Clear date record|(((
850 850  Clear all stored sensor data…
... ... @@ -856,31 +856,36 @@
856 856  
857 857  * Example: 0xA301 ~/~/Same as AT+CLRDTA
858 858  
859 -= 5. Battery & How to replace =
860 860  
861 -== 5.1 Battery Type ==
862 862  
870 += Battery & How to replace =
871 +
872 +== Battery Type ==
873 +
863 863  LHT65N is equipped with a 2400mAH Li-MnO2 (CR17505) battery . The battery is an un-rechargeable battery with low discharge rate targeting for up to 8~~10 years use. This type of battery is commonly used in IoT devices for long-term running, such as water meters.
864 864  
865 865  The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
866 866  [[image:image-20220515075034-1.png||height="208" width="644"]]
867 867  
879 +
868 868  The minimum Working Voltage for the LHT65N is ~~ 2.5v. When battery is lower than 2.6v, it is time to change the battery.
869 869  
870 870  
871 -== 5.2 Replace Battery ==
883 +== Replace Battery ==
872 872  
873 873  LHT65N has two screws on the back, Unscrew them, and changing the battery inside is ok. The battery is a general CR17450 battery. Any brand should be ok.
874 874  
875 875  [[image:image-20220515075440-2.png||height="338" width="272"]][[image:image-20220515075625-3.png||height="193" width="257"]]
876 876  
877 -== 5.3 Battery Life Analyze ==
878 878  
890 +== Battery Life Analyze ==
891 +
879 879  Dragino battery-powered products are all run in Low Power mode. User can check the guideline from this link to calculate the estimated battery life:
880 880  https:~/~/www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf
881 881  
882 -= 6. Order Info =
883 883  
896 += Order Info =
897 +
884 884  Part Number: (% class="mark" %)**LHT65N-XX**
885 885  
886 886  **XX**: The default frequency band
... ... @@ -898,7 +898,7 @@
898 898  
899 899  * **E3**: External Temperature Probe
900 900  
901 -= 7. Packing Info =
915 += Packing Info =
902 902  
903 903  **Package Includes**:
904 904  
... ... @@ -913,10 +913,10 @@
913 913  * Package Size / pcs : 14.5 x 8 x 5 cm
914 914  * Weight / pcs : 170g
915 915  
916 -= 8. FCC Warning =
930 += FCC Warning =
917 917  
918 918  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
919 919  
920 -(1) This device may not cause harmful interference
934 +(1) This device may not cause harmful interference, and
921 921  
922 -(2) this device must accept any interference received, including interference that may cause undesired operation.
936 +(2) this device must accept any interference received, including interference that may cause undesired operation
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0