Wiki source code of LHT65-PIR Temperature/Humidity/PIR Sensor User Manual
Version 15.1 by Edwin Chen on 2023/04/09 09:02
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% style="text-align:center" %) | ||
2 | [[image:image-20221206143242-2.png||height="602" width="551"]] | ||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
9 | |||
10 | |||
11 | |||
12 | **Table of Contents:** | ||
13 | |||
14 | {{toc/}} | ||
15 | |||
16 | |||
17 | |||
18 | |||
19 | |||
20 | |||
21 | |||
22 | |||
23 | |||
24 | = 1. Introduction = | ||
25 | |||
26 | == 1.1 What is LHT65N-PIR Temperature,Humidity & PIR Sensor == | ||
27 | |||
28 | The Dragino (% style="color:blue" %)**LHT65N-PIR Temperature, Humidity & PIR sensor**(%%) is a Long Range LoRaWAN Sensor.It includes a (% style="color:blue" %)**built-in Temperature & Humidity sensor**(%%) and has an (% style="color:blue" %)**external PIR Probe**(%%)**.** LHT65N-PIR can detect environment Temperature & Humdity, it also detects (% style="color:blue" %)**People Activity**(%%) via PIR probe and them send these info to LoRaWAN IoT Server. | ||
29 | |||
30 | The LHT65N-PIR 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. | ||
31 | |||
32 | LHT65N-PIR has a (% style="color:blue" %)**built-in 2400mAh non-chargeable battery**(%%) which can be used for more than 5 years*. | ||
33 | |||
34 | LHT65N-PIR supports (% style="color:blue" %)**wireless configure & OTA update**(%%) which make user easy to use. | ||
35 | |||
36 | LHT65N-PIR is fully compatible with (% style="color:blue" %)**LoRaWAN v1.0.3 Class A protocol**(%%), it can work with a standard LoRaWAN gateway. | ||
37 | |||
38 | |||
39 | **~*~***The actual battery life depends on how often to send data, please see battery analyzer chapter. | ||
40 | |||
41 | |||
42 | == 1.2 Features == | ||
43 | |||
44 | * LoRaWAN v1.0.3 Class A protocol | ||
45 | * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915 | ||
46 | * AT Commands to change parameters | ||
47 | * Remote configure parameters via LoRaWAN Downlink | ||
48 | * Support wireless OTA update firmware | ||
49 | * Firmware upgradeable via program port | ||
50 | * Built-in 2400mAh battery for up to 5 years of use. | ||
51 | * Built-in Temperature & Humidity sensor | ||
52 | * External PIR Sensor | ||
53 | * Tri-color LED to indicate working status(% style="display:none" %) | ||
54 | |||
55 | == 1.3 Specification == | ||
56 | |||
57 | |||
58 | (% style="color:#037691" %)**Built-in Temperature Sensor:** | ||
59 | |||
60 | * Resolution: 0.01 °C | ||
61 | * Accuracy Tolerance : Typ ±0.3 °C | ||
62 | * Long Term Drift: < 0.02 °C/yr | ||
63 | * Operating Range: -40 ~~ 85 °C | ||
64 | |||
65 | (% style="color:#037691" %)**Built-in Humidity Sensor:** | ||
66 | |||
67 | * Resolution: 0.04 %RH | ||
68 | * Accuracy Tolerance : Typ ±3 %RH | ||
69 | * Long Term Drift: < 0.02 °C/yr | ||
70 | * Operating Range: 0 ~~ 96 %RH | ||
71 | |||
72 | (% class="mark" style="color:#037691" %)**External PIR Sensor:** | ||
73 | |||
74 | * (% class="mark" %)Base on BH1750 Illumination Sensor | ||
75 | * (% class="mark" %)Cable Length : 50cm | ||
76 | * (% class="mark" %)Resolution: 1 lx | ||
77 | * (% class="mark" %)Range: 0-65535 lx | ||
78 | * (% class="mark" %)Operating Range: -40 °C ~~ 85 °C | ||
79 | * | ||
80 | |||
81 | = 2. Connect LHT65N-PIR to IoT Server = | ||
82 | |||
83 | == 2.1 How does LHT65N-PIR work? == | ||
84 | |||
85 | LHT65N-PIR is configured as LoRaWAN OTAA Class A sensor by default. Each LHT65N-PIR is shipped with a worldwide unique set of OTAA keys. To use LHT65N-PIR in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N-PIR. | ||
86 | |||
87 | If LHT65N-PIR is within the coverage of this LoRaWAN network. LHT65N-PIR can join the LoRaWAN network automatically. After successfully joining, LHT65N-PIR will start to measure environment temperature, humidity & people activity, and start to transmit sensor data to the LoRaWAN server. The default period for each uplink is 20 minutes. | ||
88 | |||
89 | |||
90 | == 2.2 How to Activate LHT65N-PIR? == | ||
91 | |||
92 | The LHT65N-PIR has two working modes: | ||
93 | |||
94 | * (% style="color:blue" %)**Deep Sleep Mode**(%%): LHT65N-PIR doesn't have any LoRaWAN activation. This mode is used for storage and shipping to save battery life. | ||
95 | |||
96 | * (% style="color:blue" %)**Working Mode**(%%): In this mode, LHT65N-PIR works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65N-PIR will be in STOP mode (IDLE mode), in STOP mode, the PIR sensor is still working to detect people activity in low power consumption. | ||
97 | |||
98 | The LHT65N-PIR is set in deep sleep mode by default; The ACT button on the front is to switch to different modes: | ||
99 | |||
100 | |||
101 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220515123819-1.png?width=317&height=379&rev=1.1||alt="image-20220515123819-1.png" height="379" width="317"]] | ||
102 | |||
103 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220525110604-2.png?rev=1.1||alt="image-20220525110604-2.png"]] | ||
104 | |||
105 | |||
106 | == 2.3 Example to join LoRaWAN network == | ||
107 | |||
108 | |||
109 | (% class="wikigeneratedid" %) | ||
110 | 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. | ||
111 | |||
112 | |||
113 | (% class="wikigeneratedid" %) | ||
114 | [[image:image-20230409080812-1.png||height="487" width="785"]] | ||
115 | |||
116 | |||
117 | Assume the LPS8v2 is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network||_mstvisible="2"]], So it provides network coverage for LHT65N-PIR. Next we need to add the LHT65N-PIR device in TTN V3: | ||
118 | |||
119 | |||
120 | === 2.3.1 Step 1: Create Device n TTN === | ||
121 | |||
122 | |||
123 | Create a device in TTN V3 with the OTAA keys from LHT65N-PIR. | ||
124 | |||
125 | Each LHT65N-PIR is shipped with a sticker with its device EUI, APP Key and APP EUI as below: | ||
126 | |||
127 | [[image:image-20220617150003-1.jpeg||_mstalt="5426434"]] | ||
128 | |||
129 | User can enter these keys in the LoRaWAN Server portal. Below is TTN V3 screenshot: | ||
130 | |||
131 | Add APP EUI in the application. | ||
132 | |||
133 | |||
134 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522232916-3.png||_mstalt="430495"]] | ||
135 | |||
136 | |||
137 | [[image:image-20220522232932-4.png||_mstalt="430157"]] | ||
138 | |||
139 | |||
140 | [[image:image-20220522232954-5.png||_mstalt="431847"]] | ||
141 | |||
142 | |||
143 | |||
144 | (% style="color:red" %)**Note: LHT65N-PIR use same payload decoder as LHT65.** | ||
145 | |||
146 | |||
147 | Input APP EUI, APP KEY and DEV EUI: | ||
148 | |||
149 | |||
150 | [[image:image-20220522233118-7.png||_mstalt="430430"]] | ||
151 | |||
152 | |||
153 | === 2.3.2 Step 2: Activate LHT65N-PIR by pressing the ACT button for more than 5 seconds. === | ||
154 | |||
155 | Use ACT button to activate LHT65N-PIR 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. | ||
156 | [[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]] | ||
157 | |||
158 | |||
159 | == 2.4 Uplink Payload ( Fport~=2) == | ||
160 | |||
161 | The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default. | ||
162 | |||
163 | After each uplink, the (% style="color:blue" %)**BLUE LED**(%%) will blink once. | ||
164 | |||
165 | (% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:390px" %) | ||
166 | |=(% style="width: 60px;" %)((( | ||
167 | **Size(bytes)** | ||
168 | )))|=(% style="width: 30px;" %)((( | ||
169 | **2** | ||
170 | )))|=(% style="width: 100px;" %)((( | ||
171 | **2** | ||
172 | )))|=(% style="width: 100px;" %)((( | ||
173 | **2** | ||
174 | )))|=(% style="width: 50px;" %)((( | ||
175 | **1** | ||
176 | )))|=(% style="width: 50px;" %)((( | ||
177 | **4** | ||
178 | ))) | ||
179 | |(% style="width:97px" %)((( | ||
180 | **Value** | ||
181 | )))|(% style="width:39px" %)((( | ||
182 | [[BAT>>||anchor="H2.4.2BAT-BatteryInfo"]] | ||
183 | )))|(% style="width:100px" %)((( | ||
184 | ((( | ||
185 | [[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]] | ||
186 | ))) | ||
187 | )))|(% style="width:77px" %)((( | ||
188 | ((( | ||
189 | [[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]] | ||
190 | ))) | ||
191 | )))|(% style="width:47px" %)((( | ||
192 | [[Ext>>||anchor="H2.4.5Ext23"]] # | ||
193 | )))|(% style="width:51px" %)((( | ||
194 | [[Ext value>>||anchor="H2.4.6Extvalue"]] | ||
195 | ))) | ||
196 | |||
197 | * The First 6 bytes: has fix meanings for every LHT65N-PIR. | ||
198 | * The 7th byte (EXT #): defines the external sensor model. It can be 0x0A for LHT65N-PIR | ||
199 | * The 8^^th^^ byte: Alarm Bit (if this uplink is from periodically or movement) | ||
200 | * The 9^^th^^ ~~ 11^^st^^ byte: Movement Detect Count. | ||
201 | |||
202 | === 2.4.1 Decoder in TTN V3 === | ||
203 | |||
204 | |||
205 | When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-PIR decoder in TTNv3 for friendly reading. | ||
206 | |||
207 | Below is the position to put the decoder and LHT65N-PIR decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]] | ||
208 | |||
209 | |||
210 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]] | ||
211 | |||
212 | |||
213 | === 2.4.2 BAT-Battery Info === | ||
214 | |||
215 | |||
216 | These two bytes of BAT include the battery state and the actually voltage | ||
217 | |||
218 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220523152839-18.png||_mstalt="457613"]] | ||
219 | |||
220 | |||
221 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]] | ||
222 | |||
223 | |||
224 | Check the battery voltage for LHT65N-PIR. | ||
225 | |||
226 | * BAT status=(0xcba4>>14)&0xFF=11(B),very good | ||
227 | * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV | ||
228 | |||
229 | === 2.4.3 Built-in Temperature === | ||
230 | |||
231 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-2.png||_mstalt="431756" height="138" width="722"]] | ||
232 | |||
233 | * Temperature: 0x0ABB/100=27.47℃ | ||
234 | |||
235 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-3.png||_mstalt="432120"]] | ||
236 | |||
237 | * Temperature: (0xF5C6-65536)/100=-26.18℃ | ||
238 | |||
239 | === 2.4.4 Built-in Humidity === | ||
240 | |||
241 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-4.png||_mstalt="432484" height="138" width="722"]] | ||
242 | |||
243 | * Humidity: 0x025C/10=60.4% | ||
244 | |||
245 | === 2.4.5 Ext value === | ||
246 | |||
247 | ==== 2.4.5.1 Ext~=0x0A, PIR Sensor ==== | ||
248 | |||
249 | [[image:image-20221224161634-2.png||height="138" width="851"]] | ||
250 | |||
251 | |||
252 | ==== 2.4.5.2 Ext Value ==== | ||
253 | |||
254 | There are 4 bytes in Ext Value field. | ||
255 | |||
256 | Bit0 of byte 8th shows if this uplink is generate by PIR activity. | ||
257 | |||
258 | (% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:490px" %) | ||
259 | |=(% style="width: 147px;" %)((( | ||
260 | **The 8^^th^^ byte** | ||
261 | )))|=(% style="width: 108px;" %)((( | ||
262 | **Bit 1~~7** | ||
263 | )))|=(% style="width: 228px;" %)((( | ||
264 | **Bit 0** | ||
265 | ))) | ||
266 | |(% style="width:147px" %)((( | ||
267 | **Value** | ||
268 | )))|(% style="width:108px" %)((( | ||
269 | Reserve | ||
270 | )))|(% style="width:228px" %)((( | ||
271 | ((( | ||
272 | 0: Normal Uplink | ||
273 | |||
274 | 1: Uplink by activity detected | ||
275 | ))) | ||
276 | ))) | ||
277 | |||
278 | **Note**: Uplink by activity is disable by default. | ||
279 | |||
280 | |||
281 | The 9^^th^^ ~~ 11^^st^^ byte: Movement Detect Count. | ||
282 | |||
283 | 0x00 E5 09 : Total detect 58633 activity since end node start. | ||
284 | |||
285 | |||
286 | == 2.5 Show data on Datacake == | ||
287 | |||
288 | 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: | ||
289 | |||
290 | (% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the LoRaWAN network. | ||
291 | |||
292 | (% 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. | ||
293 | |||
294 | Add Datacake: | ||
295 | |||
296 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220523000825-7.png||_mstalt="429884" height="262" width="583"]] | ||
297 | |||
298 | |||
299 | |||
300 | Select default key as Access Key: | ||
301 | |||
302 | |||
303 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220523000825-8.png||_mstalt="430248" height="453" width="406"]] | ||
304 | |||
305 | |||
306 | In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT65 device. | ||
307 | |||
308 | |||
309 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20221224161935-5.png||height="523" width="409"]] | ||
310 | |||
311 | |||
312 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20221224161957-6.png||height="306" width="852"]] | ||
313 | |||
314 | |||
315 | |||
316 | == 2.8 LED Indicator == | ||
317 | |||
318 | |||
319 | The LHT65N-PIR has a triple color LED which for easy showing different stage . | ||
320 | |||
321 | While user press ACT button, the LED will work as per LED status with ACT button. | ||
322 | |||
323 | In a normal working state: | ||
324 | |||
325 | * For each uplink, the BLUE LED or RED LED will blink once. | ||
326 | BLUE LED when external sensor is connected. | ||
327 | * RED LED when external sensor is not connected | ||
328 | * For each success downlink, the PURPLE LED will blink once | ||
329 | |||
330 | == 2.9 installation == | ||
331 | |||
332 | ~1. Don't install LHT65N-PIR outdoor or place where will get wet | ||
333 | |||
334 | 2. Towards the PIR probe to the place where need to monitor activity. | ||
335 | |||
336 | |||
337 | |||
338 | = 3. Sensors and Accessories = | ||
339 | |||
340 | == 3.1 E2 Extension Cable == | ||
341 | |||
342 | |||
343 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220619092222-1.png||_mstalt="429533" height="182" width="188"]][[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220619092313-2.png||_mstalt="430222" height="182" width="173"]] | ||
344 | |||
345 | |||
346 | **1m long breakout cable for LHT65N-E5. Features:** | ||
347 | |||
348 | * ((( | ||
349 | Use for AT Command | ||
350 | ))) | ||
351 | * ((( | ||
352 | Update firmware for LHT65N-PIR | ||
353 | ))) | ||
354 | |||
355 | [[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]] | ||
356 | |||
357 | |||
358 | = 4. Configure LHT65N-PIR via AT command or LoRaWAN downlink = | ||
359 | |||
360 | |||
361 | ((( | ||
362 | Use can configure LHT65N-E5 via AT Command or LoRaWAN Downlink. | ||
363 | ))) | ||
364 | |||
365 | * ((( | ||
366 | AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]]. | ||
367 | ))) | ||
368 | |||
369 | * ((( | ||
370 | LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] | ||
371 | ))) | ||
372 | |||
373 | ((( | ||
374 | There are two kinds of commands to configure LHT65N-E5, they are: | ||
375 | ))) | ||
376 | |||
377 | * ((( | ||
378 | (% style="color:#4f81bd" %)**General Commands**. | ||
379 | ))) | ||
380 | |||
381 | ((( | ||
382 | These commands are to configure: | ||
383 | ))) | ||
384 | |||
385 | 1. ((( | ||
386 | General system settings like: uplink interval. | ||
387 | ))) | ||
388 | 1. ((( | ||
389 | LoRaWAN protocol & radio-related commands. | ||
390 | ))) | ||
391 | |||
392 | ((( | ||
393 | 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]] | ||
394 | ))) | ||
395 | |||
396 | * ((( | ||
397 | (% style="color:#4f81bd" %)**Commands special design for LHT65N-E5** | ||
398 | ))) | ||
399 | |||
400 | ((( | ||
401 | These commands are only valid for LHT65N-E5, as below: | ||
402 | ))) | ||
403 | |||
404 | |||
405 | == 4.1 Set Transmit Interval Time == | ||
406 | |||
407 | |||
408 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
409 | |||
410 | |||
411 | (% style="color:#4f81bd" %)**AT Command: AT+TDC** | ||
412 | |||
413 | [[image:image-20220523150701-2.png||_mstalt="427453"]] | ||
414 | |||
415 | |||
416 | (% style="color:#4f81bd" %)**Downlink Command: 0x01** | ||
417 | |||
418 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
419 | |||
420 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
421 | |||
422 | * **Example 1**: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
423 | |||
424 | * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
425 | |||
426 | == 4.2 Currently only supports E5 == | ||
427 | |||
428 | |||
429 | Feature: Set device password, max 9 digits | ||
430 | |||
431 | |||
432 | (% style="color:#4f81bd" %)**AT Command: AT+EXT** | ||
433 | |||
434 | (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) | ||
435 | |Command Example|Function|Response | ||
436 | |AT+EXT=?|Get or Set external sensor model|((( | ||
437 | 5 | ||
438 | |||
439 | OK | ||
440 | ))) | ||
441 | |AT+EXT=5|(% colspan="2" %)Set external sensor mode to 5 | ||
442 | |||
443 | (% style="color:#4f81bd" %)**Downlink Command:0xA2** | ||
444 | |||
445 | |||
446 | Total bytes: 2 bytes | ||
447 | |||
448 | **Example:** | ||
449 | |||
450 | * 0xA205: Set external sensor type to E5 | ||
451 | |||
452 | == 4.3 Set to sleep mode == | ||
453 | |||
454 | |||
455 | Feature: Set device to sleep mode | ||
456 | |||
457 | * **AT+Sleep=0** : Normal working mode, device will sleep and use lower power when there is no LoRa message | ||
458 | * **AT+Sleep=1** : Device is in deep sleep mode, no LoRa activation happen, used for storage or shipping. | ||
459 | |||
460 | (% style="color:#4f81bd" %)**AT Command: AT+SLEEP** | ||
461 | |||
462 | [[image:image-20220523151218-7.png||_mstalt="430703"]] | ||
463 | |||
464 | |||
465 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
466 | |||
467 | * There is no downlink command to set to Sleep mode. | ||
468 | |||
469 | |||
470 | = 5. Battery & Power Consumption = | ||
471 | |||
472 | LHT65N-PIR use **CR17450** battery pack. See below link for detail information about the battery info and how to replace. | ||
473 | |||
474 | [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
475 | |||
476 | |||
477 | = 6. OTA firmware update = | ||
478 | |||
479 | Please see this link for how to do OTA firmware update: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]] | ||
480 | |||
481 | |||
482 | = 6. FAQ = | ||
483 | |||
484 | == 6.1 How to use AT Command? == | ||
485 | |||
486 | |||
487 | LHT65N-E5 supports AT Command set.User can use a USB to TTL adapter plus the Program Cable to connect to LHT65 for using AT command, as below. | ||
488 | |||
489 | |||
490 | [[image:image-20220615153355-1.png||_mstalt="430222"]] | ||
491 | |||
492 | |||
493 | |||
494 | [[image:1655802313617-381.png||_mstalt="293917"]] | ||
495 | |||
496 | |||
497 | |||
498 | ((( | ||
499 | In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600** (%%)to access to access serial console for LHT65N-E5. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(% style="color:red" %))(%%) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout. | ||
500 | ))) | ||
501 | |||
502 | [[image:image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]] | ||
503 | |||
504 | AT Command List is as below: | ||
505 | |||
506 | AT+<CMD>? : Help on <CMD> | ||
507 | |||
508 | AT+<CMD> : Run <CMD> | ||
509 | |||
510 | AT+<CMD>=<value> : Set the value | ||
511 | |||
512 | AT+<CMD>=? : Get the value | ||
513 | |||
514 | AT+DEBUG: Set more info output | ||
515 | |||
516 | ATZ: Trig a reset of the MCU | ||
517 | |||
518 | AT+FDR: Reset Parameters to Factory Default, Keys Reserve | ||
519 | |||
520 | AT+DEUI: Get or Set the Device EUI | ||
521 | |||
522 | AT+DADDR: Get or Set the Device Address | ||
523 | |||
524 | AT+APPKEY: Get or Set the Application Key | ||
525 | |||
526 | AT+NWKSKEY: Get or Set the Network Session Key | ||
527 | |||
528 | AT+APPSKEY: Get or Set the Application Session Key | ||
529 | |||
530 | AT+APPEUI: Get or Set the Application EUI | ||
531 | |||
532 | AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on) | ||
533 | |||
534 | AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec) | ||
535 | |||
536 | AT+DR: Get or Set the Data Rate. (0-7 corresponding to DR_X) | ||
537 | |||
538 | AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing | ||
539 | |||
540 | AT+PNM: Get or Set the public network mode. (0: off, 1: on) | ||
541 | |||
542 | AT+RX2FQ: Get or Set the Rx2 window frequency | ||
543 | |||
544 | AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X) | ||
545 | |||
546 | AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms | ||
547 | |||
548 | AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms | ||
549 | |||
550 | AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms | ||
551 | |||
552 | AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms | ||
553 | |||
554 | AT+NJM: Get or Set the Network Join Mode. (0: ABP, 1: OTAA) | ||
555 | |||
556 | AT+NWKID: Get or Set the Network ID | ||
557 | |||
558 | AT+FCU: Get or Set the Frame Counter Uplink | ||
559 | |||
560 | AT+FCD: Get or Set the Frame Counter Downlink | ||
561 | |||
562 | AT+CLASS: Get or Set the Device Class | ||
563 | |||
564 | AT+JOIN: Join network | ||
565 | |||
566 | AT+NJS: Get the join status | ||
567 | |||
568 | AT+SENDB: Send hexadecimal data along with the application port | ||
569 | |||
570 | AT+SEND: Send text data along with the application port | ||
571 | |||
572 | AT+RECVB: Print last received data in binary format (with hexadecimal values) | ||
573 | |||
574 | AT+RECV: Print last received data in raw format | ||
575 | |||
576 | AT+VER: Get current image version and Frequency Band | ||
577 | |||
578 | AT+CFM: Get or Set the confirmation mode (0-1) | ||
579 | |||
580 | AT+CFS: Get confirmation status of the last AT+SEND (0-1) | ||
581 | |||
582 | AT+SNR: Get the SNR of the last received packet | ||
583 | |||
584 | AT+RSSI: Get the RSSI of the last received packet | ||
585 | |||
586 | AT+TDC: Get or set the application data transmission interval in ms | ||
587 | |||
588 | AT+PORT: Get or set the application port | ||
589 | |||
590 | AT+DISAT: Disable AT commands | ||
591 | |||
592 | AT+PWORD: Set password, max 9 digits | ||
593 | |||
594 | AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode | ||
595 | |||
596 | AT+CHE: Get or Set eight channels mode,Only for US915,AU915,CN470 | ||
597 | |||
598 | AT+PDTA: Print the sector data from start page to stop page | ||
599 | |||
600 | AT+PLDTA: Print the last few sets of data | ||
601 | |||
602 | AT+CLRDTA: Clear the storage, record position back to 1st | ||
603 | |||
604 | AT+SLEEP: Set sleep mode | ||
605 | |||
606 | AT+EXT: Get or Set external sensor model | ||
607 | |||
608 | AT+BAT: Get the current battery voltage in mV | ||
609 | |||
610 | AT+CFG: Print all configurations | ||
611 | |||
612 | AT+WMOD: Get or Set Work Mode | ||
613 | |||
614 | AT+ARTEMP: Get or set the internal Temperature sensor alarm range | ||
615 | |||
616 | AT+CITEMP: Get or set the internal Temperature sensor collection interval in min | ||
617 | |||
618 | AT+SETCNT: Set the count at present | ||
619 | |||
620 | AT+RJTDC: Get or set the ReJoin data transmission interval in min | ||
621 | |||
622 | AT+RPL: Get or set response level | ||
623 | |||
624 | AT+TIMESTAMP: Get or Set UNIX timestamp in second | ||
625 | |||
626 | AT+LEAPSEC: Get or Set Leap Second | ||
627 | |||
628 | AT+SYNCMOD: Get or Set time synchronization method | ||
629 | |||
630 | AT+SYNCTDC: Get or set time synchronization interval in day | ||
631 | |||
632 | AT+PID: Get or set the PID | ||
633 | |||
634 | |||
635 | == 6.2 Where to use AT commands and Downlink commands == | ||
636 | |||
637 | |||
638 | **AT commands:** | ||
639 | |||
640 | [[image:image-20220620153708-1.png||_mstalt="429806" height="603" width="723"]] | ||
641 | |||
642 | |||
643 | **Downlink commands:** | ||
644 | |||
645 | |||
646 | |||
647 | (% style="color:blue" %)**TTN:** | ||
648 | |||
649 | [[image:image-20220615092124-2.png||_mstalt="429221" height="649" width="688"]] | ||
650 | |||
651 | |||
652 | |||
653 | (% style="color:blue" %)**Helium:** | ||
654 | |||
655 | [[image:image-20220615092551-3.png||_mstalt="430794" height="423" width="835"]] | ||
656 | |||
657 | |||
658 | |||
659 | (% style="color:blue" %)**Chirpstack: The downlink window will not be displayed until the network is accessed** | ||
660 | |||
661 | |||
662 | [[image:image-20220615094850-6.png||_mstalt="433082"]] | ||
663 | |||
664 | |||
665 | [[image:image-20220615094904-7.png||_mstalt="433485" height="281" width="911"]] | ||
666 | |||
667 | |||
668 | |||
669 | (% style="color:blue" %)**Aws:** | ||
670 | |||
671 | [[image:image-20220615092939-4.png||_mstalt="434460" height="448" width="894"]] | ||
672 | |||
673 | |||
674 | == 6.3 How to change the uplink interval? == | ||
675 | |||
676 | |||
677 | Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]] | ||
678 | |||
679 | |||
680 | |||
681 | [[image:image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]] | ||
682 | |||
683 | |||
684 | == 6.4 How to use TTL-USB to connect PC to upgrade firmware? == | ||
685 | |||
686 | |||
687 | [[image:image-20220615153355-1.png||_mstalt="430222"]] | ||
688 | |||
689 | |||
690 | (% style="color:blue" %)**Step1**(%%): Install TremoProgrammer first. | ||
691 | |||
692 | [[image:image-20220615170542-5.png||_mstalt="430638"]] | ||
693 | |||
694 | |||
695 | |||
696 | (% _mstmutation="1" style="color:blue" %)**Step2**(%%):wiring method.(% style="display:none" %) | ||
697 | |||
698 | First connect the four lines;(% style="display:none" %) | ||
699 | |||
700 | [[image:image-20220621170938-1.png||_mstalt="431340" height="413" width="419"]],(% style="display:none" %) | ||
701 | |||
702 | |||
703 | Then use DuPont cable to short circuit port3 and port1, and then release them, so that the device enters bootlaod mode. | ||
704 | |||
705 | [[image:image-20220621170938-2.png||_mstalt="431704"]] | ||
706 | |||
707 | |||
708 | |||
709 | (% style="color:blue" %)**Step3:**(%%)Select the device port to be connected, baud rate and bin file to be downloaded. | ||
710 | |||
711 | [[image:image-20220615171334-6.png||_mstalt="431028"]] | ||
712 | |||
713 | |||
714 | Click the (% style="color:blue" %)**start**(%%) button to start the firmware upgrade. | ||
715 | |||
716 | |||
717 | When this interface appears, it indicates that the download has been completed. | ||
718 | |||
719 | [[image:image-20220620160723-8.png||_mstalt="430703"]] | ||
720 | |||
721 | |||
722 | Finally, unplug the DuPont cable on port4, and then use the DuPont cable to short circuit port3 and port1 to reset the device. | ||
723 | |||
724 | |||
725 | |||
726 | [[image:image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]] | ||
727 | |||
728 | |||
729 | = 7. Order Info = | ||
730 | |||
731 | |||
732 | Part Number: (% style="color:#4f81bd" %)** LHT65N-PIR-XX** | ||
733 | |||
734 | (% style="color:#4f81bd" %)**XX **(%%): The default frequency band | ||
735 | |||
736 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**AS923**(%%): LoRaWAN AS923 band | ||
737 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**AU915**(%%): LoRaWAN AU915 band | ||
738 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**EU433**(%%): LoRaWAN EU433 band | ||
739 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**EU868**(%%): LoRaWAN EU868 band | ||
740 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**KR920**(%%): LoRaWAN KR920 band | ||
741 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**US915**(%%): LoRaWAN US915 band | ||
742 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**IN865**(%%): LoRaWAN IN865 band | ||
743 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**CN470**(%%): LoRaWAN CN470 band | ||
744 | |||
745 | = 8. Packing Info = | ||
746 | |||
747 | |||
748 | **Package Includes**: | ||
749 | |||
750 | * LHT65N-PIR Temperature/Humidity/PIR Sensor x 1 | ||
751 | |||
752 | **Dimension and weight**: | ||
753 | |||
754 | * Device Size: 10 x 10 x 3.5 mm | ||
755 | * Device Weight: 120.5g | ||
756 | |||
757 | = 9. Reference material = | ||
758 | |||
759 | |||
760 | * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0]] | ||
761 | |||
762 | = 10. FCC Warning = | ||
763 | |||
764 | |||
765 | This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: | ||
766 | |||
767 | (1) This device may not cause harmful interference; | ||
768 | |||
769 | (2) this device must accept any interference received, including interference that may cause undesired operation. |