Last modified by Mengting Qiu on 2024/04/30 14:27
<
From version < 57.1 >
edited by Xiaoling
on 2022/05/23 12:00
To version < 49.1 >
edited by Edwin Chen
on 2022/05/23 00:12
>
Change comment: Uploaded new attachment "image-20220523001219-12.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,47 +1,27 @@
1 -(% style="text-align:center" %)
2 -[[image:image-20220523115324-1.jpeg||height="500" width="500"]]
3 -
4 -
5 -**LHT65N LoRaWAN Temperature & Humidity Sensor Manual**
6 -
7 -
8 -
9 -**Table of Contents：**
10 -
1 +{{box cssClass="floatinginfobox" title="**Contents**"}}
11 11  {{toc/}}
3 +{{/box}}
12 12  
5 += Overview =
13 13  
7 +[[image:LHT65N_10.png||alt="LHT65_Image" height="265" width="265"]]
14 14  
15 -= 1.Introduction =
16 16  
17 -== 1.1 What is LHT65N Temperature & Humidity Sensor ==
10 +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 -(((
20 -The Dragino LHT65N Temperature & Humidity sensor is a Long Range LoRaWAN Sensor. It includes a (% style="color:#4f81bd" %)**built-in Temperature & Humidity sensor**(%%) and has an external sensor connector to connect to an external (% style="color:#4f81bd" %)**Temperature Sensor**(%%)**.**
21 -)))
22 -
23 -(((
24 24  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.
25 -)))
26 26  
27 -(((
28 28  LHT65N has a built-in 2400mAh non-chargeable battery which can be used for up to 10 years*.
29 -)))
30 30  
31 -(((
32 32  LHT65N is full compatible with LoRaWAN v1.0.3 Class A protocol, it can work with a standard LoRaWAN gateway.
33 -)))
34 34  
35 -(((
36 -LHT65N supports (% style="color:#4f81bd" %)**Datalog Feature**(%%). It will record the data when there is no network coverage and users can retrieve the sensor value later to ensure no miss for every sensor reading.
37 -)))
18 +LHT65N supports (% class="mark" %)Datalog Feature(%%). It will record the data when there is no network coverage and users can retrieve the sensor value later to ensure no miss for every sensor reading.
38 38  
39 -(((
40 40  *The actual battery life depends on how often to send data, please see the battery analyzer chapter.
41 -)))
42 42  
43 -== 1.2 Features ==
44 44  
23 +== Features: ==
24 +
45 45  * Wall mountable
46 46  * LoRaWAN v1.0.3 Class A protocol
47 47  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
... ... @@ -54,91 +54,55 @@
54 54  * Tri-color LED to indicate working status
55 55  * Datalog feature
56 56  
57 -== 1.3 Specification ==
37 +== Specification: ==
58 58  
59 -(((
60 60  **Built-in Temperature Sensor:**
61 -)))
62 62  
63 -* (((
64 -Resolution: 0.01 °C
65 -)))
66 -* (((
67 -Accuracy Tolerance : Typ ±0.3 °C
68 -)))
69 -* (((
70 -Long Term Drift: < 0.02 °C/yr
71 -)))
72 -* (((
73 -Operating Range: -40 ~~ 85 °C
74 -)))
41 +* Resolution: 0.01 °C
42 +* Accuracy Tolerance : Typ ±0.3 °C
43 +* Long Term Drift: < 0.02 °C/yr
44 +* Operating Range: -40 ~~ 85 °C
75 75  
76 -(((
77 77  **Built-in Humidity Sensor:**
78 -)))
79 79  
80 -* (((
81 -Resolution: 0.04 %RH
82 -)))
83 -* (((
84 -Accuracy Tolerance : Typ ±3 %RH
85 -)))
86 -* (((
87 -Long Term Drift: < 0.02 °C/yr
88 -)))
89 -* (((
90 -Operating Range: 0 ~~ 96 %RH
91 -)))
48 +* Resolution: 0.04 %RH
49 +* Accuracy Tolerance : Typ ±3 %RH
50 +* Long Term Drift: < 0.02 °C/yr
51 +* Operating Range: 0 ~~ 96 %RH
92 92  
93 -(((
94 94  **External Temperature Sensor:**
95 -)))
96 96  
97 -* (((
98 -Resolution: 0.0625 °C
99 -)))
100 -* (((
101 -±0.5°C accuracy from -10°C to +85°C
102 -)))
103 -* (((
104 -±2°C accuracy from -55°C to +125°C
105 -)))
106 -* (((
107 -Operating Range: -55 °C ~~ 125 °C
108 -)))
55 +* Resolution: 0.0625 °C
56 +* ±0.5°C accuracy from -10°C to +85°C
57 +* ±2°C accuracy from -55°C to +125°C
58 +* Operating Range: -55 °C ~~ 125 °C
109 109  
110 -= 2. Connect LHT65N to IoT Server =
60 += Connect LHT65N to IoT Server =
111 111  
112 -== 2.1 How does LHT65N work? ==
62 +== How does LHT65N work? ==
113 113  
114 -(((
115 115  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.
116 -)))
117 117  
118 -(((
119 119  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.
120 -)))
121 121  
122 -== 2.2 How to Activate LHT65N? ==
123 123  
69 +== How to Activate LHT65N? ==
70 +
124 124  The LHT65N has two working modes:
125 125  
126 126  * **Deep Sleep Mode**: LHT65N doesn’t have any LoRaWAN activation. This mode is used for storage and shipping to save battery life.
127 127  * **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, LHT65 will be in STOP mode (IDLE mode), in STOP mode, LHT65N has the same power consumption as Deep Sleep mode. 
128 128  
129 -(((
130 130  The LHT65N is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
131 -)))
132 132  
133 133  [[image:image-20220515123819-1.png||height="379" width="317"]]
134 134  
135 -(% border="1" %)
136 136  |**Behavior on ACT**|**Function**|**Action**
137 137  |**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.
138 138  |**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.
139 139  |**Fast press ACT 5 times**|Deactivate Device|red led will solid on for 5 seconds. This means LHT65N is in Deep Sleep Mode.
140 140  
141 -== 2.3 Example to join LoRaWAN network ==
85 +== Example to join LoRaWAN network ==
142 142  
143 143  (% class="wikigeneratedid" %)
144 144  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.
... ... @@ -149,7 +149,7 @@
149 149  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:
150 150  
151 151  
152 -=== 2.3.1 Step 1: Create Device n TTN ===
96 +=== **Step 1**: Create Device n TTN ===
153 153  
154 154  Create a device in TTN V3 with the OTAA keys from LHT65N.
155 155  
... ... @@ -179,7 +179,7 @@
179 179  [[image:image-20220522233118-7.png]]
180 180  
181 181  
182 -=== 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
126 +=== Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
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  
... ... @@ -186,7 +186,7 @@
186 186  [[image:image-20220522233300-8.png]]
187 187  
188 188  
189 -== 2.4 Uplink Payload ==
133 +== Uplink Payload: ==
190 190  
191 191  The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and(% class="mark" %) every 20 minutes(%%) send one uplink by default.
192 192  
... ... @@ -193,7 +193,7 @@
193 193  After each uplink, the (% class="mark" %)BLUE LED(%%) will blink once.
194 194  
195 195  
196 -(% border="1" style="width:572px" %)
140 +(% style="width:572px" %)
197 197  |(% 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**
198 198  |(% style="width:106px" %)**Value**|(% style="width:71px" %)[[BAT>>path:#Battery]]|(% style="width:128px" %)(((
199 199  [[Built-In>>path:#SHT20_Temperature]]
... ... @@ -209,7 +209,7 @@
209 209  * The 7th byte (EXT #): defines the external sensor model.
210 210  * 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.)
211 211  
212 -=== 2.4.1 Decoder in TTN V3 ===
156 +=== Decoder in TTN V3 ===
213 213  
214 214  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.
215 215  
... ... @@ -220,7 +220,7 @@
220 220  [[image:image-20220522234118-10.png]]
221 221  
222 222  
223 -=== 2.4.2 BAT-Battery Info ===
167 +=== BAT-Battery Info ===
224 224  
225 225  These two bytes of BAT include the battery state and the actually voltage
226 226  
... ... @@ -245,7 +245,7 @@
245 245  * BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
246 246  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
247 247  
248 -=== 2.4.3 Built-in Temperature ===
192 +=== Built-in Temperature ===
249 249  
250 250  [[image:image-20220522235639-2.png]]
251 251  
... ... @@ -255,13 +255,13 @@
255 255  
256 256  * Temperature:  (0xF5C6-65536)/100=-26.18℃
257 257  
258 -=== 2.4.4 Built-in Humidity ===
202 +=== Built-in Humidity ===
259 259  
260 260  [[image:image-20220522235639-4.png]]
261 261  
262 262  * Humidity:    0x025C/10=60.4%
263 263  
264 -=== 2.4.5 Ext # ===
208 +=== Ext # ===
265 265  
266 266  Bytes for External Sensor:
267 267  
... ... @@ -270,16 +270,19 @@
270 270  |(% style="width:139px" %)0x01|(% style="width:484px" %)Sensor E3, Temperature Sensor
271 271  |(% style="width:139px" %)0x09|(% style="width:484px" %)Sensor E3, Temperature Sensor, Datalog Mod
272 272  
273 -=== 2.4.6 Ext value ===
217 +=== Ext value ===
274 274  
275 -==== 2.4.6.1 Ext~=1, E3 Temperature Sensor ====
219 +==== Ext~=1, E3 Temperature Sensor ====
276 276  
277 277  [[image:image-20220522235639-5.png]]
278 278  
223 +
279 279  * DS18B20 temp=0x0ADD/100=27.81℃
280 280  
281 281  The last 2 bytes of data are meaningless
282 282  
228 +
229 +
283 283  [[image:image-20220522235639-6.png]]
284 284  
285 285  * External temperature= (0xF54F-65536)/100=-27.37℃
... ... @@ -286,15 +286,16 @@
286 286  
287 287  The last 2 bytes of data are meaningless
288 288  
236 +
289 289  If the external sensor is 0x01, and there is no external temperature connected. The temperature will be set to 7FFF which is 327.67℃
290 290  
291 291  
292 -==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
240 +==== Ext~=9, E3 sensor with Unix Timestamp ====
293 293  
294 294  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:
295 295  
296 296  
297 -(% border="1" style="width:697px" %)
245 +(% style="width:697px" %)
298 298  |(% 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**
299 299  |(% style="width:96px" %)**Value**|(% style="width:164px" %)[[External temperature>>path:#DS18b20_value]]|(% style="width:104px" %)(((
300 300  [[Built-In>>path:#SHT20_Temperature]]
... ... @@ -312,9 +312,9 @@
312 312  [[Time Stamp>>path:#Unix_Time_Stamp]]
313 313  )))
314 314  
315 -* **Battery status & **[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Built-in Humidity**>>path:#SHT20_Humidity]]
263 +* **Battery status & **[[(% class="wikiinternallink" %)**Built-in Humidity**>>path:#SHT20_Humidity]]
316 316  
317 -(% border="1" style="width:587px" %)
265 +(% style="width:587px" %)
318 318  |Bit(bit)|(% style="width:280px" %)[15:14]|(% style="width:136px" %)[11:0]
319 319  |Value|(% style="width:280px" %)(((
320 320  BAT Status
... ... @@ -334,7 +334,7 @@
334 334  
335 335  * **Status & Ext Byte**
336 336  
337 -(% border="1" style="width:732px" %)
285 +(% style="width:732px" %)
338 338  |(% 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]**
339 339  |(% 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" %)(((
340 340  Ext:
... ... @@ -346,10 +346,12 @@
346 346  * 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.
347 347  * 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)
348 348  
349 -== 2.5 Show data on Datacake ==
350 350  
298 +== Show data on Datacake ==
299 +
351 351  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:
352 352  
302 +
353 353  **Step 1**: Be sure that your device is programmed and properly connected to the LoRaWAN network.
354 354  
355 355  **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.
... ... @@ -374,186 +374,9 @@
374 374  [[image:image-20220523000825-10.png||height="432" width="762"]]
375 375  
376 376  
377 -== 2.6 Datalog Feature ==
378 378  
379 -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.
328 +== LED Indicator ==
380 380  
381 -=== 2.6.1 Unix TimeStamp ===
382 -
383 -LHT65N uses Unix TimeStamp format based on
384 -
385 -[[image:image-20220523001219-11.png||height="97" width="627"]]
386 -
387 -
388 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
389 -
390 -Below is the converter example
391 -
392 -[[image:image-20220523001219-12.png||height="302" width="730"]]
393 -
394 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
395 -
396 -
397 -=== 2.6.2 Set Device Time ===
398 -
399 -There are two ways to set device’s time:
400 -
401 -**~1. Through LoRaWAN MAC Command (Default settings)**
402 -
403 -User need to set SYNCMOD=1 to enable sync time via MAC command.
404 -
405 -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).
406 -
407 -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.
408 -
409 -
410 -**2. Manually Set Time**
411 -
412 -User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
413 -
414 -
415 -=== 2.6.3 Poll sensor value ===
416 -
417 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
418 -
419 -
420 -(% border="1" style="width:454px" %)
421 -|(% style="width:69px" %)1byte|(% style="width:129px" %)4bytes|(% style="width:134px" %)4bytes|(% style="width:119px" %)1byte
422 -|(% style="width:69px" %)31|(% style="width:129px" %)Timestamp start|(% style="width:134px" %)Timestamp end|(% style="width:119px" %)Uplink Interval
423 -
424 -Timestamp start and Timestamp end use Unix TimeStamp format as mentioned above. Devices will reply with all data log during this time period, use the uplink interval.
425 -
426 -
427 -For example, downlink command 31 5FC5F350 5FC6 0160 05
428 -
429 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data
430 -
431 -Uplink Internal =5s，means LHT65N will send one packet every 5s. range 5~~255s.
432 -
433 -
434 -=== 2.6.4 Datalog Uplink payload ===
435 -
436 -The Datalog poll reply uplink will use below payload format.
437 -
438 -
439 -Retrieval data payload
440 -
441 -(% border="1" %)
442 -|**Size(bytes)**|**2**|**2**|**2**|**1**|**4**
443 -|**Value**|[[External sensor data>>path:#Extension_sensor_value]]|(((
444 -[[Built-In>>path:#SHT20_Temperature]]
445 -
446 -[[Temperature>>path:#SHT20_Temperature]]
447 -)))|(((
448 -[[Built-in>>path:#SHT20_Humidity]]
449 -
450 -[[Humidity>>path:#SHT20_Humidity]]
451 -)))|[[Poll message flag & Ext>>path:#Poll_EXT]]|(((
452 -[[Unix Time Stamp>>path:#Unix_Time_Stamp]]
453 -
454 -
455 -)))
456 -
457 -Poll message flag & Ext
458 -
459 -
460 -(% border="1" %)
461 -|**Bits**|**7**|**6**|**5**|**4**|**[3:0]**
462 -|**Status & Ext**|Not Defined|Poll Message Flag|Sync time OK|Unix Time Request|(((
463 -Ext:
464 -
465 -0b(1001)
466 -)))
467 -
468 -Poll Message Flag: 1: This message is a poll message reply.
469 -
470 -* Poll Message Flag is set to 1.
471 -* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
472 -
473 -For example, in US915 band, the max payload for different DR is:
474 -
475 -a)      DR0: max is 11 bytes so one entry of data
476 -
477 -b)      DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
478 -
479 -c)      DR2: total payload includes 11 entries of data
480 -
481 -d)      DR3: total payload includes 22 entries of data.
482 -
483 -If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0   
484 -
485 -
486 -**Example:**
487 -
488 -If LHT65N has below data inside Flash:
489 -
490 -Flash Addr   |Unix Time | Ext | BAT voltage|  Value                  
491 -
492 -80196E0 21/1/19 04:27:03 1 3145 sht_temp=22.00 sht_hum=32.6 ds_temp=327.67
493 -
494 -80196F0 21/1/19 04:28:57 1 3145 sht_temp=21.90 sht_hum=33.1 ds_temp=327.67
495 -
496 -8019700 21/1/19 04:30:30 1 3145 sht_temp=21.81 sht_hum=33.4 ds_temp=327.67
497 -
498 -8019710 21/1/19 04:40:30 1 3145 sht_temp=21.65 sht_hum=33.7 ds_temp=327.67
499 -
500 -8019720 21/1/19 04:50:30 1 3147 sht_temp=21.55 sht_hum=34.1 ds_temp=327.67
501 -
502 -8019730 21/1/19 05:00:30 1 3149 sht_temp=21.50 sht_hum=34.1 ds_temp=327.67
503 -
504 -8019740 21/1/19 05:10:30 1 3149 sht_temp=21.43 sht_hum=34.6 ds_temp=327.67
505 -
506 -8019750 21/1/19 05:20:30 1 3151 sht_temp=21.35 sht_hum=34.9 ds_temp=327.67
507 -
508 -
509 -If user sends below downlink command:
510 -
511 -3160065F9760066DA705
512 -
513 - Where : Start time: 60065F97 = time 21/1/19 04:27:03
514 -
515 - Stop time 60066DA7= time 21/1/19 05:27:03
516 -
517 -
518 -LHT65N will uplink this payload.
519 -
520 -[[image:image-20220523001219-13.png||height="421" width="727"]]
521 -
522 -7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
523 -
524 -Where the first 11 bytes is for the first entry:
525 -
526 -7FFF089801464160065F97
527 -
528 -Ext sensor data=0x7FFF/100=327.67
529 -
530 -Temp=0x0898/100=22.00
531 -
532 -Hum=0x0146/10=32.6
533 -
534 -poll message flag & Ext=0x41,means reply data,Ext=1
535 -
536 -Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
537 -
538 -
539 -== 2.7 Alarm Mode ==
540 -
541 -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.
542 -
543 -
544 -Note: Alarm mode will increase a little big the power consumption, we recommend extending the normal reading time when enabling this feature.
545 -
546 -
547 -AT Commands for Alarm mode:
548 -
549 -**AT+WMOD=1**: Enable/Disable Alarm Mode. (0:Disable, 1: Enable)
550 -
551 -**AT+CITEMP=1**: The interval to check the temperature for Alarm. (Unit: minute)
552 -
553 -
554 -
555 -== 2.8 LED Indicator ==
556 -
557 557  The LHT65N has a triple color LED which for easy shows different stage.
558 558  
559 559  While pressing ACT button, the LED will work as per LED status with ACT button.
... ... @@ -567,14 +567,17 @@
567 567  
568 568  ----
569 569  
570 -== 2.9 Installation ==
343 +== Installation ==
571 571  
572 -[[image:image-20220516231650-1.png||height="436" width="428"]]
345 +[[image:image-20220516231650-1.png||height="632" width="620"]]
573 573  
574 -= 3. Sensors & Accessories =
575 575  
576 -== 3.1 E3 Temperature Probe ==
577 577  
349 +
350 += Sensors & Accessories =
351 +
352 +== E3 Temperature Probe ==
353 +
578 578  [[image:image-20220515080154-4.png||height="182" width="161"]] [[image:image-20220515080330-5.png||height="201" width="195"]]
579 579  
580 580  
... ... @@ -586,350 +586,36 @@
586 586  * Operating Range: -40 ~~ 125 °C
587 587  * -55°C to 125°C
588 588  * Working voltage 2.35v ~~ 5v
365 +
589 589  
590 -= 4. Configure LHT65N via AT Command or LoRaWAN Downlink =
367 += Battery & How to replace =
591 591  
592 -Use can configure LHT65N via AT Command or LoRaWAN Downlink.
369 +== Battery Type ==
593 593  
594 -* AT Command Connection: See [[FAQ>>path:#AT_COMMAND]].
595 -* LoRaWAN Downlink instruction for different platforms:
596 -
597 -[[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]]
598 -
599 -There are two kinds of commands to configure LHT65N, they are:
600 -
601 -* **General Commands**.
602 -
603 -These commands are to configure:
604 -
605 -* General system settings like: uplink interval.
606 -* LoRaWAN protocol & radio-related commands.
607 -
608 -They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki:
609 -
610 -[[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_Downlink_Command>>url:http://wiki.dragino.com/index.php?title=End_Device_Downlink_Command]]
611 -
612 -* **Commands special design for LHT65N**
613 -
614 -These commands are only valid for LHT65N, as below:
615 -
616 -== 4.1 Set Transmit Interval Time ==
617 -
618 -Feature: Change LoRaWAN End Node Transmit Interval.
619 -
620 -**AT Command: AT+TDC**
621 -
622 -(% border="1" %)
623 -|**Command Example**|**Function**|**Response**
624 -|AT+TDC?|Show current transmit Interval|(((
625 -30000
626 -
627 -OK
628 -
629 -the interval is 30000ms = 30s
630 -)))
631 -|AT+TDC=60000|Set Transmit Interval|(((
632 -OK
633 -
634 -Set transmit interval to 60000ms = 60 seconds
635 -)))
636 -
637 -**Downlink Command: 0x01**
638 -
639 -Format: Command Code (0x01) followed by 3 bytes time value.
640 -
641 -If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
642 -
643 -* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
644 -* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
645 -
646 -== 4.2 Set External Sensor Mode ==
647 -
648 -Feature: Change External Sensor Mode.
649 -
650 -**AT Command: AT+EXT**
651 -
652 -(% border="1" %)
653 -|**Command Example**|**Function**|**Response**
654 -|AT+EXT?|Get current external sensor mode|(((
655 -1
656 -
657 -OK
658 -
659 -External Sensor mode =1
660 -)))
661 -|AT+EXT=1|(% colspan="2" %)Set external sensor mode to 1
662 -|AT+EXT=9|(% colspan="2" %)Set to external DS18B20 with timestamp
663 -
664 -**Downlink Command: 0xA2**
665 -
666 -Total bytes: 2 ~~ 5 bytes
667 -
668 -Example:
669 -
670 -* 0xA201: Set external sensor type to E1
671 -* 0xA209: Same as AT+EXT=9
672 -* 0xA20702003c,Same as AT+SETCNT=60
673 -
674 -== 4.3 Enable/Disable uplink Temperature probe ID ==
675 -
676 -Feature: If PID is enabled, device will send the temperature probe ID on:
677 -
678 -* First Packet after OTAA Join
679 -* Every 24 hours since the first packet.
680 -
681 -PID is default set to disable (0)
682 -
683 -
684 -**AT Command:**
685 -
686 -(% border="1" %)
687 -|**Command Example**|**Function**|**Response**
688 -|AT+PID=1|Enable PID uplink|OK
689 -
690 -**Downlink Command:**
691 -
692 -* 0xA800     à AT+PID=0
693 -* 0xA801     à AT+PID=1
694 -
695 -== 4.4 Set Password ==
696 -
697 -Feature: Set device password, max 9 digits
698 -
699 -**AT Command: AT+PWORD**
700 -
701 -(% border="1" %)
702 -|**Command Example**|**Function**|**Response**
703 -|AT+PWORD=?|Show password|(((
704 -123456
705 -
706 -
707 -OK
708 -)))
709 -|AT+PWORD=999999|Set password|OK
710 -
711 -**Downlink Command:**
712 -
713 -No downlink command for this feature.
714 -
715 -== 4.5 Quit AT Command ==
716 -
717 -Feature: Quit AT Command mode, so user needs to input password again before use AT Commands.
718 -
719 -**AT Command: AT+DISAT**
720 -
721 -(% border="1" %)
722 -|**Command Example**|**Function**|**Response**
723 -|AT+DISAT|Quit AT Commands mode|OK
724 -
725 -**Downlink Command:**
726 -
727 -No downlink command for this feature.
728 -
729 -
730 -== 4.6 Set to sleep mode ==
731 -
732 -Feature: Set device to sleep mode
733 -
734 -**AT Command: AT+SLEEP**
735 -
736 -(% border="1" %)
737 -| | |
738 -|**Command Example**|**Function**|**Response**
739 -|AT+SLEEP|Set to sleep mode|(((
740 -Clear all stored sensor data…
741 -
742 -OK
743 -)))
744 -
745 -**Downlink Command:**
746 -
747 -* There is no downlink command to set to Sleep mode.
748 -
749 -== 4.7 Set system time ==
750 -
751 -Feature: Set system time, unix format. [[See here for format detail.>>path:#TimeStamp]]
752 -
753 -**AT Command:**
754 -
755 -(% border="1" %)
756 -|**Command Example**|**Function**
757 -|AT+TIMESTAMP=1611104352|(((
758 -OK
759 -
760 -Set System time to 2021-01-20 00:59:12
761 -)))
762 -
763 -**Downlink Command:**
764 -
765 -0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
766 -
767 -== 4.8 Set Time Sync Mode ==
768 -
769 -Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
770 -
771 -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.
772 -
773 -
774 -**AT Command:**
775 -
776 -|**Command Example**|**Function**
777 -|AT+SYNCMOD=1|Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq)
778 -
779 -**Downlink Command:**
780 -
781 -0x28 01 ~/~/ Same As AT+SYNCMOD=1
782 -
783 -0x28 00 ~/~/ Same As AT+SYNCMOD=0
784 -
785 -== 4.9 Set Time Sync Interval ==
786 -
787 -Feature: Define System time sync interval. SYNCTDC default value: 10 days.
788 -
789 -**AT Command:**
790 -
791 -(% border="1" %)
792 -|**Command Example**|**Function**
793 -|AT+SYNCTDC=0x0A|Set SYNCTDC to 10 (0x0A), so the sync time is 10 days.
794 -
795 -**Downlink Command:**
796 -
797 -0x29 0A ~/~/ Same as AT+SYNCTDC=0x0A
798 -
799 -== 4.10 Print data entries base on page. ==
800 -
801 -Feature: Print the sector data from start page to stop page (max is 416 pages).
802 -
803 -**AT Command: AT+PDTA**
804 -
805 -(% border="1" %)
806 -|**Command Example**|**Response**
807 -|(((
808 -AT+PDTA=1,3
809 -
810 -
811 -
812 -Print page 1 to 3
813 -)))|(((
814 -8019500 19/6/26 16:48 1 2992 sht_temp=28.21 sht_hum=71.5 ds_temp=27.31
815 -
816 -8019510 19/6/26 16:53 1 2994 sht_temp=27.64 sht_hum=69.3 ds_temp=26.93
817 -
818 -8019520 19/6/26 16:58 1 2996 sht_temp=28.39 sht_hum=72.0 ds_temp=27.06
819 -
820 -8019530 19/6/26 17:03 1 2996 sht_temp=27.97 sht_hum=70.4 ds_temp=27.12
821 -
822 -8019540 19/6/26 17:08 1 2996 sht_temp=27.80 sht_hum=72.9 ds_temp=27.06
823 -
824 -8019550 19/6/26 17:13 1 2998 sht_temp=27.30 sht_hum=72.4 ds_temp=26.68
825 -
826 -8019560 19/6/26 17:22 1 2992 sht_temp=26.27 sht_hum=62.3 ds_temp=26.56
827 -
828 -8019570
829 -
830 -8019580
831 -
832 -8019590
833 -
834 -80195A0
835 -
836 -80195B0
837 -
838 -80195C0
839 -
840 -80195D0
841 -
842 -80195E0
843 -
844 -80195F0
845 -
846 -
847 -OK
848 -)))
849 -
850 -**Downlink Command:**
851 -
852 -No downlink commands for feature
853 -
854 -== 4.11 Print last few data entries. ==
855 -
856 -Feature: Print the last few data entries
857 -
858 -**AT Command: AT+PLDTA**
859 -
860 -(% border="1" %)
861 -|**Command Example**|**Response**
862 -|(((
863 -AT+PLDTA=5
864 -
865 -
866 -
867 -Print last 5 entries
868 -)))|(((
869 -Stop Tx and RTP events when read sensor data
870 -
871 -1 19/6/26 13:59 1 3005 sht_temp=27.09 sht_hum=79.5 ds_temp=26.75
872 -
873 -2 19/6/26 14:04 1 3007 sht_temp=26.65 sht_hum=74.8 ds_temp=26.43
874 -
875 -3 19/6/26 14:09 1 3007 sht_temp=26.91 sht_hum=77.9 ds_temp=26.56
876 -
877 -4 19/6/26 14:15 1 3007 sht_temp=26.93 sht_hum=76.7 ds_temp=26.75
878 -
879 -5 19/6/26 14:20 1 3007 sht_temp=26.78 sht_hum=76.6 ds_temp=26.43
880 -
881 -Start Tx and RTP events
882 -
883 -OK
884 -)))
885 -
886 -**Downlink Command:**
887 -
888 -No downlink commands for feature
889 -
890 -== 4.12 Clear Flash Record ==
891 -
892 -Feature: Clear flash storage for data log feature.
893 -
894 -**AT Command: AT+CLRDTA**
895 -
896 -(% border="1" %)
897 -|**Command Example**|**Function**|**Response**
898 -|AT+CLRDTA|Clear date record|(((
899 -Clear all stored sensor data…
900 -
901 -OK
902 -)))
903 -
904 -**Downlink Command: 0xA3**
905 -
906 -* Example: 0xA301 ~/~/Same as AT+CLRDTA
907 -
908 -= 5. Battery & How to replace =
909 -
910 -== 5.1 Battery Type ==
911 -
912 912  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.
913 913  
914 914  The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
915 915  [[image:image-20220515075034-1.png||height="208" width="644"]]
916 916  
376 +
917 917  The minimum Working Voltage for the LHT65N is ~~ 2.5v. When battery is lower than 2.6v, it is time to change the battery.
918 918  
919 919  
920 -== 5.2 Replace Battery ==
380 +== Replace Battery ==
921 921  
922 922  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.
923 923  
924 924  [[image:image-20220515075440-2.png||height="338" width="272"]][[image:image-20220515075625-3.png||height="193" width="257"]]
925 925  
926 -== 5.3 Battery Life Analyze ==
927 927  
387 +== Battery Life Analyze ==
388 +
928 928  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:
929 929  https:~/~/www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf
930 930  
931 -= 6. Order Info =
932 932  
393 += Order Info =
394 +
933 933  Part Number: (% class="mark" %)**LHT65N-XX**
934 934  
935 935  **XX**: The default frequency band
... ... @@ -947,7 +947,7 @@
947 947  
948 948  * **E3**: External Temperature Probe
949 949  
950 -= 7. Packing Info =
412 += Packing Info =
951 951  
952 952  **Package Includes**:
953 953  
... ... @@ -962,10 +962,10 @@
962 962  * Package Size / pcs : 14.5 x 8 x 5 cm
963 963  * Weight / pcs : 170g
964 964  
965 -= 8. FCC Warning =
427 += FCC Warning =
966 966  
967 967  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
968 968  
969 -(1) This device may not cause harmful interference；
431 +(1) This device may not cause harmful interference, and
970 970  
971 -(2) this device must accept any interference received, including interference that may cause undesired operation.
433 +(2) this device must accept any interference received, including interference that may cause undesired operation
image-20220523001219-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -35.6 KB
Content
image-20220523111447-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -910.1 KB
Content
image-20220523112300-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.5 KB
Content
image-20220523115324-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -910.1 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0