Last modified by Xiaoling on 2025/04/24 10:52
Show last authors
1 (% style="text-align:center" %)
2 [[image:1655774244188-589.png]]
3
4
5
6
7 (% _mstvisible="1" %)
8 (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
9
10 {{toc/}}
11
12
13
14
15
16
17
18
19 = 1.  Introduction =
20
21 == 1.1  What is LHT52 Temperature & Humidity Sensor ==
22
23
24 (((
25 The Dragino LHT52 Temperature & Humidity sensor is a Long Range LoRaWAN Sensor. It includes a (% style="color:blue" %)**built-in Temperature & Humidity sensor** (%%)and has a USB Type-C sensor connector to connect to external sensors such as external Temperature Sensor.
26 )))
27
28 (((
29 LHT52 (% style="color:blue" %)**senses environment temperature and humidity**(%%) and send these values via long-range wireless LoRaWAN protocol. It targets professional wireless sensor network applications such as food service, smart metering, smart cities, building automation, and so on.
30 )))
31
32 (((
33 LHT52 supports(% style="color:blue" %)** 2 x AAA batteries **(%%)and works for a long time up to several years. Use can replace the batteries easily after they are finished.
34 )))
35
36 (((
37 LHT52 is fully compatible with LoRaWAN v1.0.3 protocol, it can work with standard LoRaWAN gateway.
38 )))
39
40 (((
41 LHT52 supports(% style="color:blue" %)** Datalog feature** (%%)to make sure users won't miss sensor data. It records sensor value for every uplink. These values can be retrieved by LoRaWAN server via downlink command.
42 )))
43
44 (((
45 LHT52 supports(% style="color:blue" %)** temperature alarm feature**(%%). It can uplink alarm in a short interval while temperature exceeds preset limits.
46 )))
47
48 (((
49 *Battery life depends how often to send data, please see [[battery analyzer>>||anchor="H4.2A0PowerConsumptionAnalyze"]].
50 )))
51
52 [[image:1655774519494-861.png]]
53
54
55 == 1.2  Features ==
56
57
58 * Wall Attachable.
59 * LoRaWAN v1.0.3 Class A protocol.
60 * Built-in Temperature & Humidity sensor
61 * Optional External Probe
62 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
63 * AT Commands to change parameters
64 * Remote configure parameters via LoRaWAN Downlink
65 * Firmware upgradable via program port
66 * Support 2 x AAA LR03 batteries.
67 * Datalog feature
68 * IP Rating: IP52
69
70 == 1.3  Specification ==
71
72
73 **Built-in Temperature Sensor:**
74
75 * Resolution: 0.01 °C
76 * Accuracy Tolerance: Typ ±0.3 °C
77 * Long Term Drift: < 0.02 °C/yr
78 * Operating Range: -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
79
80 **Built-in Humidity Sensor:**
81
82 * Resolution: 0.1 %RH
83 * Accuracy Tolerance: Typ ±3 %RH
84 * Long Term Drift: < 0.25 RH/yr
85 * Operating Range: 0 ~~ 99.0 %RH(no Dew)
86
87 == 1.4  Power Consumption ==
88
89
90 LHT52 (without external sensor): Idle: 5uA, Transmit: max 110mA
91
92 LHT52 + External Temperature Probe (AS-01): Idle: 6uA, Transmit: max 110mA.
93
94
95 == 1.5  Storage & Operation Temperature ==
96
97
98 -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
99
100
101 == 1.6  Applications ==
102
103
104 * Smart Buildings & Home Automation
105 * Logistics and Supply Chain Management
106 * Smart Metering
107 * Smart Agriculture
108 * Smart Cities
109 * Smart Factory
110
111 = 2.  Operation Mode =
112
113 == 2.1  How it work? ==
114
115
116 Each LHT52 is shipped with a worldwide unique set of LoRaWAN OTAA keys. To use LHT52 in a LoRaWAN network, user needs to input the OTAA keys in LoRaWAN network server. After this, if LHT52 is under this LoRaWAN network coverage, LHT52 can join the LoRaWAN network and start to transmit sensor data. The default period for each uplink is** 20 minutes**.
117
118
119 == 2.2  How to Activate LHT52? ==
120
121
122 (% style="color:red" %)** 1.  Open enclosure from below position.**
123
124 [[image:image-20220621093835-1.png]]
125
126
127 (% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries.**
128
129 [[image:image-20220621093835-2.png]]
130
131
132 (% style="color:red" %)** 3.  Press the reset button to activate device.**
133
134 [[image:image-20220621093835-3.png]]
135
136
137 User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of LHT52.
138
139
140 == 2.3  Example to join LoRaWAN network ==
141
142
143 This section shows an example for how to join the [[TheThingsNetwork>>url:https://www.thethingsnetwork.org/]] LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are of similar procedure.
144
145
146 (% _mstvisible="1" class="wikigeneratedid" %)
147 [[image:1655775912928-657.png]]
148
149 Assume the DLOS8 is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. We need to add the LHT52 device in TTN V3 portal. 
150
151
152 (% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from LHT52.
153
154 Each LHT52 is shipped with a sticker with the default DEV EUI as below:
155
156 [[image:image-20230426083617-1.png||height="294" width="633"]]
157
158
159 You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
160
161 **Create the application.**
162
163 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SAC01L_LoRaWAN_Temperature%26Humidity_Sensor_User_Manual/WebHome/image-20250423093843-1.png?width=756&height=264&rev=1.1||alt="image-20250423093843-1.png"]]
164
165 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111305-2.png?width=1000&height=572&rev=1.1||alt="image-20240907111305-2.png"]]
166
167
168 **Add devices to the created Application.**
169
170 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111659-3.png?width=977&height=185&rev=1.1||alt="image-20240907111659-3.png"]]
171
172 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111820-5.png?width=975&height=377&rev=1.1||alt="image-20240907111820-5.png"]]
173
174
175 **Enter end device specifics manually.**
176
177 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112136-6.png?width=697&height=687&rev=1.1||alt="image-20240907112136-6.png"]]
178
179
180 **Add DevEUI and AppKey.**
181
182 **Customize a platform ID for the device.**
183
184 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112427-7.png?rev=1.1||alt="image-20240907112427-7.png"]]
185
186
187 (% style="color:blue" %)**Step 2**(%%):  Add decoder.
188
189 In TTN, user can add a custom payload so it shows friendly reading.
190
191 Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/LHT52>>https://github.com/dragino/dragino-end-node-decoder/tree/main/LHT52]]
192
193 Below is TTN screen shot:
194
195 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140556-1.png?width=1184&height=488&rev=1.1||alt="image-20241009140556-1.png" height="488" width="1184"]]
196
197 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140603-2.png?width=1168&height=562&rev=1.1||alt="image-20241009140603-2.png" height="562" width="1168"]]
198
199
200 (% style="color:blue" %)**Step 3**(%%):  Use ACT button to activate LHT52 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.
201
202 [[image:image-20220621095134-4.png]]
203
204
205 == 2.4  Uplink Payload ==
206
207
208 Uplink payloads include two types: Valid Sensor Value and other status / control command.
209
210 * Valid Sensor Value: Use FPORT=2
211 * Other control command: Use FPORT other than 2.
212
213 === 2.4.1  Uplink FPORT~=5, Device Status ===
214
215
216 Uplink the device configures with FPORT=5. Once LHT52 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours.
217
218 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:370px" %)
219 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bytes)(% style="display:none" %) (%%)**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2**
220 |(% style="width:99px" %)Value|(% style="width:62px" %)Sensor Model|(% style="width:80px" %)Firmware Version|(% style="width:82px" %)Frequency Band|(% style="width:85px" %)Sub-band|(% style="width:46px" %)BAT
221
222 [[image:image-20220621100550-5.png||height="368" width="1260"]](% style="display:none" %)
223
224 Example Payload (FPort=5):  [[image:image-20220621105116-11.png]]
225
226
227 (% style="color:#4472c4" %)**Sensor Model**(%%): For LHT52, this value is 0x09.
228
229 (% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
230
231 (% style="color:#4472c4" %)**Frequency Band**:
232
233 *0x01: EU868
234
235 *0x02: US915
236
237 *0x03: IN865
238
239 *0x04: AU915
240
241 *0x05: KZ865
242
243 *0x06: RU864
244
245 *0x07: AS923
246
247 *0x08: AS923-1
248
249 *0x09: AS923-2
250
251 *0x0a: AS923-3
252
253
254 (% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
255
256 (% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for LHT52.
257
258 (% style="color:#4472c4" %)**Ex1**(%%): 0x0B3A = 2874mV
259
260
261 Use can also get the Device Status uplink through the downlink command:
262
263 (% style="color:#4472c4" %)**Downlink:  **(%%)0x2301
264
265 [[image:image-20220621100550-6.png||height="440" width="1302"]]
266
267
268 === 2.4.2  Uplink FPORT~=2, Real time sensor value ===
269
270
271 LHT52 will send this uplink after Device Status uplink once join LoRaWAN network successfully. And it will periodically send this uplink. Default interval is 20 minutes and [[can be changed>>||anchor="H3.1A0DownlinkCommandSet"]].
272
273 Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
274
275 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:390px" %)
276 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
277 **Size(bytes)**
278 )))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
279 **2**
280 )))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
281 **2**
282 )))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)(((
283 **2**
284 )))|=(% style="width: 40px;background-color:#4F81BD;color:white" %)(((
285 **1**
286 )))|=(% style="width: 80px;background-color:#4F81BD;color:white" %)(((
287 **4**
288 )))
289 |(% style="width:97px" %)(((
290 Value
291 )))|(% style="width:39px" %)(((
292 [[Temperature>>||anchor="HTemperature26ExternalTemperature:"]]
293 )))|(% style="width:100px" %)(((
294 (((
295 [[Humidity>>||anchor="HHumidity:"]]
296 )))
297 )))|(% style="width:77px" %)(((
298 (((
299 [[External Temperature>>||anchor="HTemperature26ExternalTemperature:"]]
300 )))
301 )))|(% style="width:47px" %)(((
302 [[Ext>>||anchor="HExtension23" _msthash="1817486"]] #
303 )))|(% style="width:51px" %)(((
304 [[Unix TimeStamp>>||anchor="H2.6.1A0UnixTimeStamp"]]
305 )))
306
307 **Temperature:**
308
309 [[image:image-20220621101526-7.png]]
310
311 Example Payload (FPort=2):  (% style="background-color:yellow" %)**08 CD 02 20 7F FF 01 61 CD 4E DD**
312
313
314 ==== (% style="color:blue" %)**Temperature & External Temperature:**(%%) ====
315
316
317 * Example1:  0x08CD/100=22.53℃
318 * Example2:  (0xF5C6-65536)/100=-26.18℃
319
320 If payload is: F5C6 :  (F5C6 & 8000 == 1) , temp = (F5C6 - 65536)/100 =-26.18℃
321
322 （F5C6 & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
323
324
325 ==== (% style="color:blue" %)**Humidity:**(%%) ====
326
327
328 * Humidity:    0x0220/10=54.4%
329
330 ==== (% style="color:blue" %)**Extension #**(%%) ====
331
332
333 Bytes for External Sensor:
334
335 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:310px" %)
336 |=(% style="width: 105px;background-color:#4F81BD;color:white" %)**EXT # Value**|=(% style="width: 205px;background-color:#4F81BD;color:white" %)**External Sensor Probe**
337 |(% style="width:103px" %)0x01|(% style="width:203px" %)Sensor AS-01, Temperature
338
339 === 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
340
341
342 LHT52 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
343
344 [[image:image-20220621101659-8.png||height="482" width="1292"]](% style="display:none" %)
345
346
347 * Each data entry is 11 bytes, to save airtime and battery, LHT52 will send max bytes according to the current DR and Frequency bands.(% style="display:none" %)
348
349 For example, in US915 band, the max payload for different DR is:
350
351 1. **DR0**: max is 11 bytes so one entry of data
352 1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
353 1. **DR2**: total payload includes 11 entries of data
354 1. **DR3**: total payload includes 22 entries of data.
355
356 (% style="color:red" %)**Notice: LHT52 will save 178 set of history data, If device doesn't have any data in the polling time. Device will uplink 11 bytes of 0.**
357
358 See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
359
360
361 === 2.4.4  Uplink FPORT~=4, DS18B20 ID ===
362
363
364 User can get external DS18B20 ID through the downlink command.
365
366 Downlink:  0x2302
367
368 [[image:image-20220621101853-9.png||height="529" width="1366"]]
369
370 Example Payload (FPort=4):  (% style="color:#037691" %)**28 86 63 B2 00 00 00 9F**
371
372 The External DS18B20 ID is 0x28 86 63 B2 00 00 00 9F
373
374
375 === 2.4.5  Decoder in TTN V3 ===
376
377
378 In LoRaWAN protocol, the uplink payload is HEX format, user need to add a payload formatter/decoder in LoRaWAN Server to get human friendly string.
379
380 In TTN , add formatter as below:
381
382 [[image:image-20220621102026-10.png]]
383
384
385 (((
386 Please check the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
387 )))
388
389 (((
390
391 )))
392
393 == 2.5 Show data on Datacake ==
394
395
396 (((
397 Datacake IoT platform provides a human friendly interface to show the sensor data in charts, 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:
398 )))
399
400 (((
401
402 )))
403
404 (((
405 (% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
406 )))
407
408 (((
409 (% style="color:blue" %)**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.
410 )))
411
412 (((
413 ~1. Add Datacake:
414 )))
415
416 (((
417 2. Select default key as Access Key:
418 )))
419
420 (((
421 3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT52:
422 )))
423
424 (((
425 Please refer to the figure below
426 )))
427
428
429 [[image:image-20220621112422-1.png]]
430
431
432 Log in to DATACAKE, copy the API under the account
433
434 [[image:image-20220621112422-2.png]]
435
436
437 [[image:image-20220621112422-3.png]]
438
439
440
441 [[image:image-20220621112422-4.png||height="741" width="1237"]]
442
443
444 [[image:image-20220621112422-5.png||height="314" width="1226"]]
445
446
447 [[image:image-20220621112422-6.png]]
448
449
450 [[image:image-20220621112422-7.png]]
451
452 [[image:image-20220621112422-8.png]]
453
454
455 [[image:image-20220621112422-9.png||height="338" width="1211"]]
456
457
458 [[image:image-20220621112422-10.png||height="372" width="1215"]]
459
460
461
462 Copy and paste the [[TTN decoder>>https://www.dropbox.com/sh/6ighqpavkd33gqi/AACPu62g--x0gBADvHZs_xr6a?dl=0]] here and save
463
464 [[image:image-20220621112422-11.png||height="575" width="1215"]]
465
466
467 Visual widgets please read the DATACAKE documentation
468
469 [[image:image-20220622154805-1.png]]
470
471
472 == 2.6  Datalog Feature ==
473
474
475 (% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
476 When user want to retrieve sensor value, he can send a poll command from the IoT platform to ask sensor to send value in the required time slot.
477
478
479 === 2.6.1  Unix TimeStamp ===
480
481
482 Unix TimeStamp shows the sampling time of uplink payload. format base on
483
484 [[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
485
486 User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
487
488 For example: if the Unix Timestamp we got is hex 0x60137afd, we can convert it to Decimal: 1611889405. and then convert to the time: 2021 – Jan ~-~- 29 Friday 03:03:25 (GMT)
489
490
491 [[image:1655782409139-256.png]]
492
493
494 === 2.6.2  Poll sensor value ===
495
496
497 (((
498 User can poll sensor value based on timestamps from the server. Below is the downlink command.
499 )))
500
501 (((
502 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.
503 )))
504
505 (((
506 For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
507 )))
508
509 (((
510 Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
511 )))
512
513 (((
514 Uplink Internal =5s，means LHT52 will send one packet every 5s. range 5~~255s.
515 )))
516
517
518 === 2.6.3  Datalog Uplink payload ===
519
520
521 See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
522
523 (% style="display:none" %) (%%)
524
525 == 2.7  Alarm Mode ==
526
527
528 (((
529 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.
530 )))
531
532 (((
533 The alarm mode can be modified by AT command or downlink, Alarm mode is disabled by default.
534 )))
535
536 (((
537 If you need to enable the Alarm mode, please refer to the following
538 )))
539
540 (((
541 (% style="color:red" %)**Note: Alarm mode will increase the power consumption, we recommend extending the normal uplink time (20 minutes default) when enable this feature.**
542 )))
543
544 (((
545
546 )))
547
548 (((
549 (% style="color:blue" %)**AT Commands for Alarm mode:**
550 )))
551
552 (((
553 (% style="color:#037691" %)**AT+WMOD=1**(%%)**: ** Enable/Disable Alarm Mode. (0:Disable, 1: Enable),need to reset the node to take effect
554 )))
555
556 (((
557 (% style="color:#037691" %)**AT+CITEMP=1**(%%)**: ** The interval to check temperature for Alarm. (Unit: minute)
558 )))
559
560 (((
561 (% style="color:#037691" %)**AT+ARTEMP=-40,125**(%%)**:   ** Set the normal temperature range from -40°C to 125°C
562 )))
563
564 (((
565 Suppose you want to set the normal temperature from 15°C to 50°C, and turn on the alarm mode, and check the temperature every 2 minutes. Please refer to the following
566 )))
567
568 [[image:image-20220621114109-14.png]]
569
570 [[image:image-20220621114109-15.png]]
571
572
573 (((
574 Modification via downlink,Take TTN_V3 as an example((% style="color:red" %)downlink commands, please refer to the downlink command set for details(%%))
575 )))
576
577 (((
578 In order to ensure that the node is indeed modified by downlink, I reset the node to factory settings first.
579 )))
580
581 [[image:image-20220621114109-16.png]]
582
583
584 [[image:image-20220621114109-17.png||height="583" width="1274"]]
585
586 [[image:image-20220621114109-18.png]]
587
588
589 Or use a downlink directly: AA010002000F0032 ([[See command info>>||anchor="H3.1A0DownlinkCommandSet"]])
590
591 [[image:image-20220621114109-19.png||height="178" width="1292"]]
592
593
594 == 2.8 LED Indicator ==
595
596
597 (((
598 The LHT52 has a triple color LED which for easy showing different stage.
599 )))
600
601
602 (((
603 (% style="color:#037691" %)**In a normal working state**:
604 )))
605
606 * When the node is restarted, (% style="color:green" %)**GREEN, **(% style="color:red" %)**RED**(%%) and (% style="color:blue" %)**BLUE**(%%)** **are sequentially lit.
607
608 * During OTAA Join:
609 ** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.
610 ** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.
611
612 * After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.
613 ** (% style="color:blue" %)**BLUE LED**(%%) when external sensor is connected
614 ** (% style="color:green" %)**GREEN LED**(%%) when external sensor is not connected
615
616 * For each success downlink, the (% style="color:purple" %)**PURPLE LED**(%%) will blink once
617
618 (((
619 (% style="color:#037691" %)**In AT Command Mode:**
620 )))
621
622 (((
623 If user use console cable to send AT Command to LHT52, the (% style="color:red" %)**RED LED**(%%) will always on until:
624 )))
625
626 * Power off/on LHT52
627 * Press reset button of LHT52.
628 * Send an AT Command: AT+CLPM=1
629
630 (% style="display:none" %) (%%)
631
632
633 == 2.9 Button ==
634
635
636 Press the button LHT52 will reset and join network again.
637
638
639 = 3.  Configure LHT52 via AT command or LoRaWAN downlink =
640
641
642 Use can configure LHT52 via AT Command or LoRaWAN Downlink.
643
644 * AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
645
646 * LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
647
648 There are two kinds of commands to configure LHT52, they are:
649
650 * (% style="color:#4f81bd" %)**General Commands:**
651
652 These commands are to configure:
653
654 * General system settings like: uplink interval.
655
656 * LoRaWAN protocol & radio-related commands.
657
658 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]]
659
660
661 * (% style="color:#4f81bd" %)**Commands special design for LHT52**
662
663 These commands are only valid for LHT52, as below:
664
665
666 == 3.1  Downlink Command Set ==
667
668
669 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
670 |=(% style="width: 100px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 150px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 100px;background-color:#4F81BD;color:white" %)**Response**|=(% style="width: 150px;background-color:#4F81BD;color:white" %)**Downlink**
671 |(% style="width:161px" %)AT+TDC=?|(% style="width:138px" %)View current TDC time|(% style="width:243px" %)(((
672 1200000
673 OK
674 )))|(% style="width:1001px" %)Default 1200000(ms)
675 |(% style="width:161px" %)AT+TDC=300000|(% style="width:138px" %)Set TDC time|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
676 0X0100012C:
677 01: fixed command
678 00012C: 0X00012C=300(seconds)
679 )))
680 |(% style="width:161px" %)ATZ|(% style="width:138px" %)Reset node|(% style="width:243px" %) |(% style="width:1001px" %)0x04FF
681 |(% style="width:161px" %)AT+FDR|(% style="width:138px" %)Restore factory settings|(% style="width:243px" %) |(% style="width:1001px" %)0X04FE
682 |(% style="width:161px" %)AT+CFM=?|(% style="width:138px" %)View the current confirmation mode status|(% style="width:243px" %)(((
683 0
684 OK
685 )))|(% style="width:1001px" %)Default 0
686 |(% style="width:161px" %)AT+CFM=1|(% style="width:138px" %)Turn on confirmation mode|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
687 0x0500: close
688 0x0501: open
689 05: fixed command
690 )))
691 |(% style="width:161px" %)AT+CHE=?|(% style="width:138px" %)View the current sub-band select 0-7, the default is 0|(% style="width:243px" %)(((
692 0
693 OK
694 )))|(% style="width:1001px" %)Default 0
695 |(% style="width:161px" %)AT+CHE=2|(% style="width:138px" %)(((
696 Set subband to 2
697 (CN470,US915,AU915)
698 )))|(% style="width:243px" %)(((
699 Attention:Take effect after ATZ
700 OK
701 )))|(% style="width:1001px" %)(((
702 0X0702:
703 07: fixed command
704 02: Select subband 2
705 )))
706 |(% style="width:161px" %)AT+WMOD=?|(% style="width:138px" %)View the current alarm mode status|(% style="width:243px" %)(((
707 0
708 OK
709 )))|(% style="width:1001px" %)Default 0
710 |(% style="width:161px" %)AT+WMOD=1|(% style="width:138px" %)Turn on alarm mode|(% style="width:243px" %)(((
711 Attention:Take effect after ATZ
712 OK
713 )))|(% style="width:1001px" %)(((
714 0xA501: open
715 0XA500: close
716 A5: fixed command
717 )))
718 |(% style="width:161px" %)AT+CITEMP=?|(% style="width:138px" %)View the current temperature detection time interval|(% style="width:243px" %)(((
719 1
720 OK
721 )))|(% style="width:1001px" %)Default 1(min)
722 |(% style="width:161px" %)AT+CITEMP=2|(% style="width:138px" %)Set the temperature detection time interval to 2min|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
723 0XA70002
724 A7: fixed command
725 0002: 0X0002=2(min)
726 )))
727 |(% style="width:161px" %)AT+NJM=?|(% style="width:138px" %)Check the current network connection method|(% style="width:243px" %)(((
728 1
729 OK
730 )))|(% style="width:1001px" %)Default 1
731 |(% style="width:161px" %)AT+NJM=0|(% style="width:138px" %)Change the network connection method to ABP|(% style="width:243px" %)(((
732 Attention:Take effect after ATZ
733 OK
734 )))|(% style="width:1001px" %)(((
735 0X2000: ABP
736 0x2001: OTAA
737 20: fixed command
738 )))
739 |(% style="width:161px" %)AT+RPL=?|(% style="width:138px" %)View current RPL settings|(% style="width:243px" %)(((
740 0
741 OK
742 )))|(% style="width:1001px" %)Default 0
743 |(% style="width:161px" %)AT+RPL=1|(% style="width:138px" %)set RPL=1|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
744 0x2101:
745 21: fixed command
746 01: for details, check wiki
747 )))
748 |(% style="width:161px" %)AT+ADR=?|(% style="width:138px" %)View current ADR status|(% style="width:243px" %)(((
749 1
750 OK
751 )))|(% style="width:1001px" %)Default 0
752 |(% style="width:161px" %)AT+ADR=0|(% style="width:138px" %)Set the ADR state to off|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
753 0x2200: close
754 0x2201: open
755 22: fixed command
756 )))
757 |(% style="width:161px" %)AT+DR=?|(% style="width:138px" %)View the current DR settings|(% style="width:243px" %)OK|(% style="width:1001px" %)
758 |(% style="width:161px" %)AT+DR=1|(% style="width:138px" %)(((
759 set DR to 1
760 It takes effect only when ADR=0
761 )))|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
762 0X22000100:
763 00: ADR=0
764 01: DR=1
765 00: TXP=0
766 22: fixed command
767 )))
768 |(% style="width:161px" %)AT+TXP=?|(% style="width:138px" %)View the current TXP|(% style="width:243px" %)OK|(% style="width:1001px" %)
769 |(% style="width:161px" %)AT+TXP=0|(% style="width:138px" %)(((
770 set TXP to 0
771 It takes effect only when ADR=0
772 )))|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
773 0X22000100:
774 00: ADR=0
775 01: DR=1
776 00: TXP=0
777 22: fixed command
778 )))
779 |(% style="width:161px" %) |(% style="width:138px" %)Upload node configuration or DS18B20 ID|(% style="width:243px" %) |(% style="width:1001px" %)(((
780 0X2301:Upload node configuration
781 0x2302: Upload DS18B20 ID
782 23: fixed command
783 )))
784 |(% style="width:161px" %)AT+DWELL=?|(% style="width:138px" %)Check the high-rate upload settings|(% style="width:243px" %)(((
785 1
786 OK
787 )))|(% style="width:1001px" %)Default 1
788 |(% style="width:161px" %)AT+DWELL=1|(% style="width:138px" %)(((
789 Set high rate upload
790 (AS923,AU915)
791 )))|(% style="width:243px" %)(((
792 Attention:Take effect after ATZ
793 OK
794 )))|(% style="width:1001px" %)(((
795 0x2501: close
796 0x2500: open
797 25: fixed command
798 for details, check wiki
799 )))
800 |(% style="width:161px" %)AT+RJTDC=?|(% style="width:138px" %)View current RJTDC set time|(% style="width:243px" %)(((
801 20
802 OK
803 )))|(% style="width:1001px" %)Default 20(min)
804 |(% style="width:161px" %)AT+RJTDC=10|(% style="width:138px" %)Set RJTDC time interval|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
805 0X26000A:
806 26: fixed command
807 000A: 0X000A=10(min)
808 for details, check wiki
809 )))
810 |(% style="width:161px" %) |(% style="width:138px" %)Retrieve stored data for a specified period of time|(% style="width:243px" %) |(% style="width:1001px" %)(((
811 0X3161DE7C7061DE8A800A:
812 31: fixed command
813 61DE7C70:0X61DE7C70=2022/1/12 15:00:00
814 61DE8A80:0X61DE8A80=2022/1/12 16:00:00
815 0A: 0X0A=10(second)
816 View details 2.6.2
817 )))
818 |(% style="width:161px" %)AT+DDETECT=?|(% style="width:138px" %)View the current DDETECT setting status and time|(% style="width:243px" %)(((
819 0,1440
820 OK
821 )))|(% style="width:1001px" %)Default 0,1440(min)
822 |(% style="width:161px" %)AT+DDETECT=1,1440|(% style="width:138px" %)(((
823 Set DDETECT setting status and time
824 ((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
825 )))|(% style="width:243px" %)OK|(% style="width:1001px" %)(((
826 0X320005A0: close
827 0X320105A0: open
828 32: fixed command
829 05A0: 0X05A0=1440(min)
830 )))
831 |(% style="width:161px" %) |(% style="width:138px" %)(((
832 Downlink Modification Alarm Mode
833 (AT+WMOD,AT+CITEMP,AT+ARTEMP)
834 )))|(% style="width:243px" %) |(% style="width:1001px" %)(((
835 0XAA010002000F00032:
836 AA: fixed command
837 01: 0X01=1(AT+MOD)
838 0002: 0X0002=2(AT+CITEMP)
839 000F: 0X000F=15(AT+ARTEMP)
840 0032: 0X0032=50(AT+ARTEMP)
841 )))
842
843 == 3.2  Set Password ==
844
845
846 Feature: Set device password, max 9 digits.
847
848 (% style="color:#4f81bd" %)**AT Command: AT+PWORD**
849
850 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
851 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
852 |(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
853 123456
854 OK
855 )))
856 |(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
857
858 (% style="color:#4f81bd" %)**Downlink Command:**
859
860 No downlink command for this feature.
861
862
863 = 4.  Battery & How to replace =
864
865 == 4.1  Battery Type and replace ==
866
867
868 LHT52 uses 2 x AAA LR03(1.5v) batteries. If the batteries running low (shows 2.1v in the platform). User can buy generic AAA battery and replace it.
869
870
871 (% style="color:red" %)**Note: **
872
873 1.  The LHT52 doesn't have any screw, use can use nail to open it by the middle.
874
875 [[image:image-20220621143535-5.png]]
876
877
878 2.  Make sure the direction is correct when install the AAA batteries.
879
880 [[image:image-20220621143535-6.png]]
881
882
883 == 4.2  Power Consumption Analyze ==
884
885
886 Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
887
888 Instruction to use as below:
889
890 (% style="color:blue" %)**Step 1**(%%):  Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
891
892 [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
893
894
895 (% style="color:blue" %)**Step 2**(%%):  (% style="display:none" %) (%%)Open it and choose
896
897 * Product Model
898 * Uplink Interval
899 * Working Mode
900
901 And the Life expectation in difference case will be shown on the right.
902
903 [[image:image-20220621143643-7.png||height="429" width="1326"]]
904
905
906 = 5.  Sensors and Accessories =
907
908 == 5.1  Temperature Probe (AS-01) ==
909
910
911 External Temperature Probe base on DS18B20. (note: Default Package doesn't include AS-01)
912
913 [[image:image-20220621141939-4.png||height="315" width="279"]] [[image:image-20220621141546-2.png||height="308" width="205"]](% style="display:none" %)
914
915
916 **External Temperature Probe (AS-01):(% style="display:none" %) (%%)**
917
918 * Resolution: 0.0625 °C
919 * ±0.5°C accuracy from -10°C to +85°C
920 * ±2°C accuracy from -55°C to +125°C
921 * Operating Range: -55 °C ~~ 125 °C
922 * Cable Length: 2 meters
923
924 == 5.2  Program Converter (AS-02) ==
925
926
927 AS-02 is an optional accessory, it is USB Type-C converter. AS-02 provide below feature:
928
929 1. Access AT console of LHT52 when used with USB-TTL adapter. [[See this link>>||anchor="H6.1HowtouseATCommandtoconfigureLHT52"]].
930 1. Update firmware to LHT52 when used with DAP-Link adapter.  [[See this link>>doc:Main.Firmware Upgrade Instruction.WebHome||anchor="H2.3LHT52"]].
931
932 [[image:image-20220621141724-3.png]]
933
934
935 = 6. FAQ =
936
937 == 6.1 How to use AT Command to configure LHT52 ==
938
939
940 LHT52 supports AT Command set. User can use a USB to TTL adapter plus the Program Cable to connect to LHT52 for using AT command, as below.
941
942
943 [[image:image-20220621144150-8.png||height="537" width="724"]]
944
945
946 **Connection:**
947
948 * (% style="background-color:yellow" %)USB to TTL GND <~-~-> Program Converter GND pin
949 * (% style="background-color:yellow" %)USB to TTL RXD  <~-~-> Program Converter D+ pin
950 * (% style="background-color:yellow" %)USB to TTL TXD  <~-~-> Program Converter A11 pin
951
952 It is also possible to connect using DAPLink
953
954 [[image:image-20220621144235-9.png||height="485" width="729"]]
955
956 (((
957 **Connection:**
958 )))
959
960 * (((
961 (% style="background-color:yellow" %)USB to DAP-LINK GND <~-~-> Program Converter GND pin
962 )))
963 * (((
964 (% style="background-color:yellow" %)USB to DAP-LINK RXD  <~-~-> Program Converter D+ pin
965 )))
966 * (((
967 (% style="background-color:yellow" %)USB to DAP-LINK TXD  <~-~-> Program Converter A11 pin
968 )))
969
970 (((
971
972
973 In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**115200**(%%) to access to access serial console for LHT52. 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.
974 )))
975
976 (((
977 Input password and ATZ to activate LHT52,As shown below:
978 )))
979
980
981 [[image:image-20220621144235-10.png]]
982
983
984 == 6.2  AT Command and Downlink ==
985
986
987 (((
988 Sending ATZ will reboot the node
989 )))
990
991 (((
992 Sending AT+FDR will restore the node to factory settings
993 )))
994
995 (((
996 Get the node's AT command setting by sending AT+CFG
997 )))
998
999 (((
1000
1001 )))
1002
1003 (((
1004 **Example：**                                           
1005 )))
1006
1007 (((
1008 AT+VER=EU868 v1.0
1009 )))
1010
1011 (((
1012 AT+NJM=1          
1013 )))
1014
1015 (((
1016 AT+DEUI=25 32 12 45 65 26 12 35
1017 )))
1018
1019 (((
1020 AT+APPEUI=25 32 12 45 65 26 32 16
1021 )))
1022
1023 (((
1024 AT+APPKEY=25 32 12 45 65 26 32 16 89 48 85 65 45 87 89 55
1025 )))
1026
1027 (((
1028 AT+DADDR=00 00 00 00
1029 )))
1030
1031 (((
1032 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1033 )))
1034
1035 (((
1036 AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1037 )))
1038
1039 (((
1040 AT+NWKID=00 00 00 13
1041 )))
1042
1043 (((
1044 AT+ADR=1
1045 )))
1046
1047 (((
1048 AT+DR=5
1049 )))
1050
1051 (((
1052 AT+TXP=0
1053 )))
1054
1055 (((
1056 AT+CHS=0
1057 )))
1058
1059 (((
1060 AT+CLASS=A
1061 )))
1062
1063 (((
1064 AT+CFM=0
1065 )))
1066
1067 (((
1068 AT+JN1DL=5000
1069 )))
1070
1071 (((
1072 AT+JN2DL=6000
1073 )))
1074
1075 (((
1076 AT+RX1DL=5000
1077 )))
1078
1079 (((
1080 AT+RX2DL=6000
1081 )))
1082
1083 (((
1084 AT+RX1WTO=24
1085 )))
1086
1087 (((
1088 AT+RX2WTO=6
1089 )))
1090
1091 (((
1092 AT+RX2FQ=869525000
1093 )))
1094
1095 (((
1096 AT+RX2DR=0
1097 )))
1098
1099 (((
1100 AT+RPL=0
1101 )))
1102
1103 (((
1104 AT+FCU=6
1105 )))
1106
1107 (((
1108 AT+FCD=0
1109 )))
1110
1111 (((
1112 AT+CFS=0
1113 )))
1114
1115 (((
1116 AT+NJS=1
1117 )))
1118
1119 (((
1120 AT+DCS=0
1121 )))
1122
1123 (((
1124 AT+PNM=1
1125 )))
1126
1127 (((
1128 AT+PWORD=123456
1129 )))
1130
1131 (((
1132 AT+EXT=1
1133 )))
1134
1135 (((
1136 AT+TDC=120000
1137 )))
1138
1139 (((
1140 AT+TIMESTAMP=1640851037 2021 12 30 7 57 17
1141 )))
1142
1143 (((
1144 AT+RJTDC=20
1145 )))
1146
1147 (((
1148 AT+DDETECT=0,1440
1149 )))
1150
1151 (((
1152 AT+WMOD=0
1153 )))
1154
1155 (((
1156 AT+CITEMP=1
1157 )))
1158
1159 (((
1160 AT+ARTEMP=-40,125
1161 )))
1162
1163 (((
1164 Send AT+PDTA=? to get the stored 174 data
1165 )))
1166
1167
1168 (((
1169 **Example：**
1170 )))
1171
1172 [[image:image-20220621144804-11.png]]
1173
1174
1175 == 6.3  How to upgrade the firmware? ==
1176
1177
1178 LHT52 requires a program converter to upload images to LHT52, which is used to upload image to LHT52 for:
1179
1180 * Support new features
1181 * For bug fix
1182 * Change LoRaWAN bands.
1183
1184 (((
1185 User can check this link for the detail of operation of firmware upgrade: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction.WebHome||anchor="H2.3LHT52"]]
1186 )))
1187
1188
1189 == 6.4  How to change the LoRa Frequency Bands/Region? ==
1190
1191
1192 User can follow the introduction for [[how to upgrade image>>||anchor="H6.3A0Howtoupgradethefirmware3F"]]. When download the images, choose the required image file for download.
1193
1194
1195 == 6.5 Why i see different working temperature for the device? ==
1196
1197
1198 The working temperature range of device depends on the battery user choose.
1199
1200 * Normal AAA Battery can support -10 ~~ 50°C working range.
1201 * Special AAA battery can support -40 ~~ 60 °C working range. For example: [[Energizer L92>>https://data.energizer.com/pdfs/l92.pdf]]
1202
1203 == 6.6 How to enable LHT52's offline device re-join function? ==
1204
1205
1206 (% style="color:blue" %)**Before firmware v1.1(including v1.1):**
1207
1208 For LHT52, we turn off the offline re-join function by default, so customers need to manually configure to start offline detection.
1209
1210 (% style="color:#4f81bd" %)**AT Command: AT+DDETECT**
1211
1212 AT+DDETECT=<Flag>,<ACK_Timout> (Default Value: AT+DDETECT=0,1440)
1213
1214 * ACK_Timout: Unit: min
1215
1216 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:410px" %)
1217 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:168px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:87px" %)**Response**
1218 |(% style="width:155px" %)(((
1219 AT+DDETECT=1,1440
1220 value1
1221 )))|(% style="width:147px" %)Enable online detect|(% style="width:87px" %)(((
1222 1
1223 OK
1224 )))
1225 |(% style="width:155px" %)(((
1226 AT+DDETECT=1,?
1227 value2
1228 )))|(% style="width:147px" %)Online detection packet sending time|(% style="width:87px" %)OK
1229
1230 (% style="color:#4f81bd" %)**Downlink Command: 0x32**
1231
1232 Format: Command Code (0x32) followed by 3 bytes.
1233
1234 If the downlink payload=32 01 05A0, it means set end node to use confirm mode, while type code is 32.
1235
1236 * **Example 1:** Downlink Payload: 32 01 05A0  ~/~/ Set AT+DDETECT=1,1440
1237 ** 0x01** : Flag**
1238 ** **0x05A0 **: ACK_Timout : 1440minutes (24 hours)
1239
1240 * **Explain**: Enable Online Detect, if end node doesn't receive any downlink within **ACK_Timout**( 1440 minutes or 24 hours). means device doesn't get ACK from server within last 24 hours. Device will process rejoin, rejoin request interval is (% style="color:blue" %)**[[AT+RJTDC>>https://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.27A0Adjustnetworkrejoininginterval]]**(%%) period. For AU915/ US915, device will use the sub-band used for last join.
1241
1242 (% style="color:blue" %)**After firmware v1.1:**
1243
1244 After firmware v1.1, we enabled offline re-join function by default and changed the default ACK_Timout to 2880minutes (48 hours).
1245
1246 * **Default**: AT+DDETECT=1,2880
1247 * **Explain**: Enable Online Detect, if end node doesn't receive any downlink within **ACK_Timout**( 2880 minutes or 48 hours). means device doesn't get ACK from server within last 48 hours. Device will process rejoin, rejoin request interval is (% style="color:blue" %)**[[AT+RJTDC>>https://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.27A0Adjustnetworkrejoininginterval]]**(%%) period. For AU915/ US915, device will use the sub-band used for last join.
1248
1249 = 7. Order Info =
1250
1251 == 7.1  Main Device ==
1252
1253
1254 (((
1255 Part Number: (% style="color:#4472c4" %)**LHT65N-XX**
1256 )))
1257
1258 (((
1259 (% style="color:#4472c4" %)**XX **(%%): The default frequency band
1260 )))
1261
1262 * (% style="color:red" %)**AS923**(%%)**: **LoRaWAN AS923 band
1263 * (% style="color:red" %)**AU915**(%%)**: **LoRaWAN AU915 band
1264 * (% style="color:red" %)**EU433**(%%)**: **LoRaWAN EU433 band
1265 * (% style="color:red" %)**EU868**(%%)**:** LoRaWAN EU868 band
1266 * (% style="color:red" %)**KR920**(%%)**: **LoRaWAN KR920 band
1267 * (% style="color:red" %)**US915**(%%)**: **LoRaWAN US915 band
1268 * (% style="color:red" %)**IN865**(%%)**:  **LoRaWAN IN865 band
1269 * (% style="color:red" %)**CN470**(%%)**: **LoRaWAN CN470 band
1270
1271 == 7.2  Accessories ==
1272
1273
1274 (% style="color:red" %)**Note: below accessories are not include in the main device package, need to order separately.**
1275
1276 **Temperature Probe: (% style="color:red" %)AS-01(%%)**
1277
1278 **Program Converter: (% style="color:red" %)AS-02(%%)**
1279
1280
1281 = 8. Packing Info =
1282
1283
1284 **Package Includes**:
1285
1286 * LHT52 Temperature & Humidity Sensor x 1
1287
1288 = 9. Support =
1289
1290
1291 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1292 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
1293
1294 = 10.  Reference material =
1295
1296
1297 * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/ucgxio6zltajlxg/AACxr_XyH4Cy7gevG293k4zqa?dl=0]]
1298
1299 = 11. FCC Warning =
1300
1301
1302 This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1303
1304 (1) This device may not cause harmful interference;
1305
1306 (2) this device must accept any interference received,including interference that may cause undesired operation.
1307
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0