Changes for page LHT65N-PIR Temperature/Humidity/PIR Motion Sensor User Manual
Last modified by Xiaoling on 2025/06/10 09:17
From version 4.1
edited by Edwin Chen
on 2023/04/09 00:18
on 2023/04/09 00:18
Change comment:
There is no comment for this version
To version 14.1
edited by Edwin Chen
on 2023/04/09 08:54
on 2023/04/09 08:54
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -76,6 +76,7 @@ 76 76 * (% class="mark" %)Resolution: 1 lx 77 77 * (% class="mark" %)Range: 0-65535 lx 78 78 * (% class="mark" %)Operating Range: -40 °C ~~ 85 °C 79 +* 79 79 80 80 = 2. Connect LHT65N-PIR to IoT Server = 81 81 ... ... @@ -110,7 +110,7 @@ 110 110 111 111 112 112 (% class="wikigeneratedid" %) 113 -[[image:image-202 21224101636-1.png||height="435" width="715"]]114 +[[image:image-20230409080812-1.png||height="487" width="785"]] 114 114 115 115 116 116 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: ... ... @@ -130,7 +130,7 @@ 130 130 Add APP EUI in the application. 131 131 132 132 133 -[[image:image-20220522232916-3.png||_mstalt="430495"]] 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"]] 134 134 135 135 136 136 [[image:image-20220522232932-4.png||_mstalt="430157"]] ... ... @@ -140,12 +140,9 @@ 140 140 141 141 142 142 143 -(% style="color:red" %)**Note: LHT65N- E5use same payload decoder as LHT65.**144 +(% style="color:red" %)**Note: LHT65N-PIR use same payload decoder as LHT65.** 144 144 145 145 146 -[[image:image-20220522233026-6.png||_mstalt="429403"]] 147 - 148 - 149 149 Input APP EUI, APP KEY and DEV EUI: 150 150 151 151 ... ... @@ -152,9 +152,9 @@ 152 152 [[image:image-20220522233118-7.png||_mstalt="430430"]] 153 153 154 154 155 -=== 2.3.2 Step 2: Activate LHT65N- E5by pressing the ACT button for more than 5 seconds. ===153 +=== 2.3.2 Step 2: Activate LHT65N-PIR by pressing the ACT button for more than 5 seconds. === 156 156 157 -Use ACT button to activate LHT65N- E5and 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.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. 158 158 [[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]] 159 159 160 160 ... ... @@ -196,20 +196,20 @@ 196 196 [[Ext value>>||anchor="H2.4.6Extvalue"]] 197 197 ))) 198 198 199 -* The First 6 bytes: has fix meanings for every LHT65N- E5.200 -* The 7th byte (EXT #): defines the external sensor model. It can be 0x0 5or 0x09for LHT65N-E5201 -* The 8^^th^^ ~~ 9^^th^^byte:Illuminance. Range:0-65535lx.202 -* The 10th ~~ 11thbyte:Reserve,always 0xFFFF197 +* 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. 203 203 204 204 === 2.4.1 Decoder in TTN V3 === 205 205 206 206 207 -When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N- E5decoder in TTNv3 for friendly reading.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. 208 208 209 -Below is the position to put the decoder and LHT65N- E5decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]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]] 210 210 211 211 212 -[[image:image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]] 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"]] 213 213 214 214 215 215 === 2.4.2 BAT-Battery Info === ... ... @@ -217,397 +217,108 @@ 217 217 218 218 These two bytes of BAT include the battery state and the actually voltage 219 219 220 -[[image:image-20220523152839-18.png||_mstalt="457613"]] 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"]] 221 221 222 222 223 -[[image:image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]] 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"]] 224 224 225 225 226 -Check the battery voltage for LHT65N- E5.224 +Check the battery voltage for LHT65N-PIR. 227 227 228 -* BAT status=(0 Xcba4>>14)&0xFF=11(B),very good226 +* BAT status=(0xcba4>>14)&0xFF=11(B),very good 229 229 * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV 230 230 231 231 === 2.4.3 Built-in Temperature === 232 232 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"]] 233 233 234 -[[image:image-20220522235639-2.png||_mstalt="431756" height="138" width="722"]] 235 - 236 236 * Temperature: 0x0ABB/100=27.47℃ 237 237 238 -[[image:image-20220522235639-3.png||_mstalt="432120"]] 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"]] 239 239 240 240 * Temperature: (0xF5C6-65536)/100=-26.18℃ 241 241 242 242 === 2.4.4 Built-in Humidity === 243 243 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"]] 244 244 245 -[[image:image-20220522235639-4.png||_mstalt="432484" height="138" width="722"]] 246 - 247 247 * Humidity: 0x025C/10=60.4% 248 248 249 249 === 2.4.5 Ext value === 250 250 251 -==== 2.4.5.1 Ext~=0x0 5, IlluminanceSensor ====247 +==== 2.4.5.1 Ext~=0x0A, PIR Sensor ==== 252 252 253 - 254 254 [[image:image-20221224161634-2.png||height="138" width="851"]] 255 255 256 256 257 - * Illumination=0x005E=94 lux252 +==== 2.4.5.2 Ext Value ==== 258 258 259 -The last2bytesofdataaremeaningless254 +There are 4 bytes in Ext Value field. 260 260 261 - [[image:image-20221224161725-3.png]]256 +Bit0 of byte 8th shows if this uplink is generate by PIR activity. 262 262 263 -* When the sensor is not connected or not connected properly, will show "NULL" 264 - 265 - The last 2 bytes of data are meaningless 266 - 267 - 268 - 269 -==== 2.4.5.2 Ext~=0x85, E5 sensor with Unix Timestamp ==== 270 - 271 - 272 -((( 273 -Timestamp mode is designed for LHT65N-E5 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: 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** 274 274 ))) 275 - 266 +|(% style="width:147px" %)((( 267 +**Value** 268 +)))|(% style="width:108px" %)((( 269 +Reserve 270 +)))|(% style="width:228px" %)((( 276 276 ((( 277 - 278 -))) 272 +0: Normal Uplink 279 279 280 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:535px" %) 281 -|=(% style="width: 88px;" %)((( 282 -**Size(bytes)** 283 -)))|=(% style="width: 93px;" %)((( 284 -**2** 285 -)))|=(% style="width: 94px;" %)((( 286 -**2** 287 -)))|=(% style="width: 117px;" %)((( 288 -**2** 289 -)))|=(% style="width: 54px;" %)((( 290 -**1** 291 -)))|=(% style="width: 79px;" %)((( 292 -**4** 274 +1: Uplink by activity detected 293 293 ))) 294 -|(% style="width:88px" %)((( 295 -**Value** 296 -)))|(% style="width:93px" %)((( 297 -[[External temperature>>||anchor="H4.2SetExternalSensorMode"]] 298 -)))|(% style="width:94px" %)((( 299 -[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]] 300 -)))|(% style="width:117px" %)((( 301 -BAT Status & 302 -Illumination 303 -)))|(% style="width:54px" %)((( 304 -Status & Ext 305 -)))|(% style="width:79px" %)((( 306 -[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]] 307 307 ))) 308 308 309 -* *Batterystatus & Built-inHumidity**278 +**Note**: Uplink by activity is disable by default. 310 310 311 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:461px" %) 312 -|=(% style="width: 67px;" %)Bit(bit)|=(% style="width: 256px;" %)[15:14]|=(% style="width: 132px;" %)[11:0] 313 -|(% style="width:67px" %)Value|(% style="width:256px" %)((( 314 -BAT Status 315 -00(b): Ultra Low ( BAT <= 2.50v) 316 -01(b): Low (2.50v <=BAT <= 2.55v) 317 -10(b): OK (2.55v <= BAT <=2.65v) 318 -11(b): Good (BAT >= 2.65v) 319 -)))|(% style="width:132px" %)((( 320 -Illumination 321 -))) 322 322 323 - ***Status&ExtByte**281 +The 9^^th^^ ~~ 11^^st^^ byte: Movement Detect Count. 324 324 325 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:500px" %) 326 -|=(% scope="row" style="width: 60px;" %)**Bits**|(% style="width:90px" %)**7**|(% style="width:100px" %)**6**|(% style="width:90px" %)**5**|(% style="width:100px" %)**4**|(% style="width:60px" %)**[3:0]** 327 -|=(% style="width: 96px;" %)**Status&Ext**|(% style="width:124px" %)None-ACK Flag|(% style="width:146px" %)Poll Message FLAG|(% style="width:109px" %)Sync time OK|(% style="width:143px" %)Unix Time Request|(% style="width:106px" %)Ext: 0b(1001) 283 +0x00 E5 09 : Total detect 58633 activity since end node start. 328 328 329 -* (% style="color:blue" %)**Poll Message Flag**:(%%) 1: This message is a poll message reply, 0: means this is a normal uplink. 330 -* (% style="color:blue" %)**Sync time OK**: (%%) 1: Set time ok,0: N/A. After time SYNC request is sent, LHT65N-E5 will set this bit to 0 until got the time stamp from the application server. 331 -* (% style="color:blue" %)**Unix Time Request**:(%%) 1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N-E5 will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this) 332 332 333 333 == 2.5 Show data on Datacake == 334 334 335 - 336 -((( 337 337 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: 338 -))) 339 339 340 -((( 341 - 342 -))) 343 - 344 -((( 345 345 (% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the LoRaWAN network. 346 -))) 347 347 348 -((( 349 349 (% 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. 350 -))) 351 351 352 - 353 - 354 -((( 355 355 Add Datacake: 356 -))) 357 357 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"]] 358 358 359 -[[image:image-20220523000825-7.png||_mstalt="429884" height="262" width="583"]] 360 360 361 361 362 - 363 363 Select default key as Access Key: 364 364 365 365 366 -[[image:image-20220523000825-8.png||_mstalt="430248" height="453" width="406"]] 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"]] 367 367 368 368 369 369 In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT65 device. 370 370 371 371 372 -[[image:image-20221224161935-5.png||height="523" width="409"]] 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"]] 373 373 374 374 375 -[[image:image-20221224161957-6.png||height="306" width="852"]] 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"]] 376 376 377 377 378 -== 2.6 Datalog Feature == 379 379 380 - 381 -((( 382 -Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LHT65N-E5 will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N-E5. 383 -))) 384 - 385 - 386 -=== 2.6.1 Ways to get datalog via LoRaWAN === 387 - 388 - 389 -There are two methods: 390 - 391 -(% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range. 392 - 393 - 394 -(% style="color:blue" %)**Method 2: **(%%)Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N-E5 will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N-E5 will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. 395 - 396 - 397 -(% style="color:red" %)**Note for method 2:** 398 - 399 -* a) LHT65N-E5 will do an ACK check for data records sending to make sure every data arrive server. 400 -* b) LHT65N-E5 will send data in **CONFIRMED Mode** when PNACKMD=1, but LHT65N-E5 won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if LHT65N-E5 gets a ACK, LHT65N-E5 will consider there is a network connection and resend all NONE-ACK Message. 401 - 402 -Below is the typical case for the auto-update datalog feature (Set PNACKMD=1) 403 - 404 - 405 -[[image:image-20220703111700-2.png||_mstalt="426244" height="381" width="1119"]] 406 - 407 - 408 -=== 2.6.2 Unix TimeStamp === 409 - 410 - 411 -LHT65N-E5 uses Unix TimeStamp format based on 412 - 413 - 414 -[[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]] 415 - 416 - 417 - 418 -User can get this time from link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] : 419 - 420 -Below is the converter example 421 - 422 -[[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]] 423 - 424 - 425 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25 426 - 427 - 428 -=== 2.6.3 Set Device Time === 429 - 430 - 431 -((( 432 -(% style="color:blue" %)**There are two ways to set device's time:** 433 -))) 434 - 435 -((( 436 -**1. Through LoRaWAN MAC Command (Default settings)** 437 -))) 438 - 439 -((( 440 -User need to set SYNCMOD=1 to enable sync time via MAC command. 441 -))) 442 - 443 -((( 444 -Once LHT65N-E5 Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LHT65N-E5. If LHT65N-E5 fails to get the time from the server, LHT65N-E5 will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days). 445 -))) 446 - 447 -((( 448 -(% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.** 449 -))) 450 - 451 - 452 -((( 453 -**2. Manually Set Time** 454 -))) 455 - 456 -((( 457 -User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server. 458 -))) 459 - 460 - 461 -=== 2.6.4 Poll sensor value === 462 - 463 - 464 -User can poll sensor value based on timestamps from the server. Below is the downlink command. 465 - 466 -[[image:image-20220523152302-15.png||_mstalt="451581"]] 467 - 468 - 469 -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. 470 - 471 -For example, downlink command (% _mstmutation="1" %)**31 5FC5F350 5FC6 0160 05**(%%) 472 - 473 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data 474 - 475 -Uplink Internal =5s,means LHT65N-E5 will send one packet every 5s. range 5~~255s. 476 - 477 - 478 -=== 2.6.5 Datalog Uplink payload === 479 - 480 - 481 -The Datalog poll reply uplink will use below payload format. 482 - 483 -**Retrieval data payload:** 484 - 485 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:480px" %) 486 -|=(% style="width: 60px;" %)((( 487 -**Size(bytes)** 488 -)))|=(% style="width: 90px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 70px;" %)**2**|=(% style="width: 100px;" %)**1**|=(% style="width: 70px;" %)**4** 489 -|(% style="width:97px" %)**Value**|(% style="width:123px" %)[[External sensor data>>||anchor="H2.4.6Extvalue"]]|(% style="width:108px" %)[[Built In Temperature>>||anchor="H2.4.3Built-inTemperature"]]|(% style="width:133px" %)[[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]]|(% style="width:159px" %)Poll message flag & Ext|(% style="width:80px" %)[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]] 490 - 491 -**Poll message flag & Ext:** 492 - 493 -[[image:image-20221006192726-1.png||_mstalt="430508" height="112" width="754"]] 494 - 495 -(% style="color:blue" %)**No ACK Message**(%%): 1: This message means this payload is fromn Uplink Message which doesn't get ACK from the server before ( for [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]] feature) 496 - 497 -(% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply. 498 - 499 -* Poll Message Flag is set to 1. 500 - 501 -* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands. 502 - 503 -For example, in US915 band, the max payload for different DR is: 504 - 505 -(% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data 506 - 507 -(% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) 508 - 509 -(% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data 510 - 511 -(% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data. 512 - 513 -If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0 514 - 515 - 516 -**Example:** 517 - 518 -If LHT65N-E5 has below data inside Flash: 519 - 520 -[[image:image-20220523144455-1.png||_mstalt="430040" height="335" width="735"]] 521 - 522 - 523 -If user sends below downlink command: (% style="background-color:yellow" %)3160065F9760066DA705 524 - 525 -Where : Start time: 60065F97 = time 21/1/19 04:27:03 526 - 527 - Stop time: 60066DA7= time 21/1/19 05:27:03 528 - 529 - 530 -**LHT65N-E5 will uplink this payload.** 531 - 532 -[[image:image-20220523001219-13.png||_mstalt="451204" height="421" style="text-align:left" width="727"]] 533 - 534 - 535 -__**7FFF089801464160065F97**__ **__7FFF__ __088E__ __014B__ __41__ __60066009__** 7FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E 536 - 537 -Where the first 11 bytes is for the first entry: 538 - 539 -7FFF089801464160065F97 540 - 541 -Ext sensor data=0x7FFF/100=327.67 542 - 543 -Temp=0x088E/100=22.00 544 - 545 -Hum=0x014B/10=32.6 546 - 547 -poll message flag & Ext=0x41,means reply data,Ext=1 548 - 549 -Unix time is 0x60066009=1611030423s=21/1/19 04:27:03 550 - 551 - 552 -== 2.7 Alarm Mode == 553 - 554 -((( 555 - 556 - 557 -when the device is in alarm mode, it checks the built-in sensor temperature for a short time. if the temperature exceeds the preconfigured range, it sends an uplink immediately. 558 -))) 559 - 560 -((( 561 -(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.** 562 - 563 - 564 -))) 565 - 566 -=== 2.7.1 ALARM MODE === 567 - 568 - 569 -(% class="box infomessage" %) 570 -((( 571 -((( 572 -**AT+WMOD=1**: Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor) 573 -))) 574 - 575 -((( 576 -**AT+CITEMP=1**: The interval between checking the alarm temperature. (In minutes) 577 -))) 578 - 579 -((( 580 -**AT+ARTEMP**: Gets or sets the alarm range of the internal temperature sensor 581 -))) 582 - 583 -((( 584 -(% _mstmutation="1" %)**AT+ARTEMP=? **(%%): Gets the alarm range of the internal temperature sensor(% style="display:none" %) 585 -))) 586 - 587 -((( 588 -**AT+ARTEMP=45,105**: Set the internal temperature sensor alarm range from 45 to 105. 589 -))) 590 -))) 591 - 592 -(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX** 593 - 594 -Total bytes: 8 bytes 595 - 596 -**Example:**AA0100010001003C 597 - 598 -WMOD=01 599 - 600 -CITEMP=0001 601 - 602 -TEMPlow=0001 603 - 604 -TEMPhigh=003C 605 - 606 - 607 607 == 2.8 LED Indicator == 608 608 609 609 610 -The LHT65 has a triple color LED which for easy showing different stage . 319 +The LHT65N-PIR has a triple color LED which for easy showing different stage . 611 611 612 612 While user press ACT button, the LED will work as per LED status with ACT button. 613 613 ... ... @@ -620,16 +620,18 @@ 620 620 621 621 == 2.9 installation == 622 622 332 +~1. Don't install LHT65N-PIR outdoor or place where will get wet 623 623 624 - [[image:image-20220516231650-1.png||_mstalt="428597"height="436"width="428"]]334 +2. Towards the PIR probe to the place where need to monitor activity. 625 625 626 626 337 + 627 627 = 3. Sensors and Accessories = 628 628 629 629 == 3.1 E2 Extension Cable == 630 630 631 631 632 -[[image:image-20220619092222-1.png||_mstalt="429533" height="182" width="188"]][[image:image-20220619092313-2.png||_mstalt="430222" height="182" width="173"]] 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"]] 633 633 634 634 635 635 **1m long breakout cable for LHT65N-E5. Features:** ... ... @@ -638,21 +638,15 @@ 638 638 Use for AT Command 639 639 ))) 640 640 * ((( 641 -Update firmware for LHT65N- E5352 +Update firmware for LHT65N-PIR 642 642 ))) 643 -* ((( 644 -Exposed All pins from the LHT65N Type-C connector. 645 645 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"]] 646 646 647 - 648 -))) 649 649 650 - [[image:image-20220619092421-3.png||_mstalt="430547"height="371"width="529"]]358 += 4. Configure LHT65N-PIR via AT command or LoRaWAN downlink = 651 651 652 652 653 -= 4. Configure LHT65N-E5 via AT command or LoRaWAN downlink = 654 - 655 - 656 656 ((( 657 657 Use can configure LHT65N-E5 via AT Command or LoRaWAN Downlink. 658 658 ))) ... ... @@ -761,168 +761,15 @@ 761 761 762 762 * There is no downlink command to set to Sleep mode. 763 763 764 -== 4.4 Set system time == 765 - 766 - 767 -Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]] 768 - 769 - 770 -(% style="color:#4f81bd" %)**AT Command:** 771 - 772 -[[image:image-20220523151253-8.png||_mstalt="430677"]] 773 - 774 - 775 -(% style="color:#4f81bd" %)**Downlink Command:** 776 - 777 -0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352 778 - 779 - 780 -== 4.5 Set Time Sync Mode == 781 - 782 - 783 -((( 784 -Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command. 785 -))) 786 - 787 -((( 788 -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. 789 - 790 790 791 -))) 792 792 793 - (%style="color:#4f81bd"%)**ATCommand:**471 += 5. Battery & Power Consumption = 794 794 795 - [[image:image-20220523151336-9.png||_mstalt="431717"]]473 +LHT65N-PIR use **CR17450** battery pack. See below link for detail information about the battery info and how to replace. 796 796 475 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 797 797 798 -(% style="color:#4f81bd" %)**Downlink Command:** 799 799 800 -0x28 01 ~/~/ Same As AT+SYNCMOD=1 801 -0x28 00 ~/~/ Same As AT+SYNCMOD=0 802 - 803 - 804 -== 4.6 Set Time Sync Interval == 805 - 806 - 807 -Feature: Define System time sync interval. SYNCTDC default value: 10 days. 808 - 809 - 810 -(% style="color:#4f81bd" %)**AT Command:** 811 - 812 -[[image:image-20220523151411-10.png||_mstalt="449696"]] 813 - 814 - 815 -(% style="color:#4f81bd" %)**Downlink Command:** 816 - 817 -**0x29 0A** ~/~/ Same as AT+SYNCTDC=0x0A 818 - 819 - 820 -== 4.7 Print data entries base on page. == 821 - 822 - 823 -Feature: Print the sector data from start page to stop page (max is 416 pages). 824 - 825 - 826 -(% style="color:#4f81bd" %)**AT Command: AT+PDTA** 827 - 828 -[[image:image-20220523151450-11.png||_mstalt="451035"]] 829 - 830 - 831 -(% style="color:#4f81bd" %)**Downlink Command:** 832 - 833 -No downlink commands for feature 834 - 835 - 836 -== 4.8 Print last few data entries. == 837 - 838 - 839 -Feature: Print the last few data entries 840 - 841 - 842 -(% style="color:#4f81bd" %)**AT Command: AT+PLDTA** 843 - 844 -[[image:image-20220523151524-12.png||_mstalt="452101"]] 845 - 846 - 847 -(% style="color:#4f81bd" %)**Downlink Command:** 848 - 849 -No downlink commands for feature 850 - 851 - 852 -== 4.9 Clear Flash Record == 853 - 854 - 855 -Feature: Clear flash storage for data log feature. 856 - 857 - 858 -(% style="color:#4f81bd" %)**AT Command: AT+CLRDTA** 859 - 860 -[[image:image-20220523151556-13.png||_mstalt="454129"]] 861 - 862 - 863 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3** 864 - 865 -* Example: 0xA301 ~/~/ Same as AT+CLRDTA 866 - 867 -== 4.10 Auto Send None-ACK messages == 868 - 869 - 870 -Feature: LHT65N-E5 will wait for ACK for each uplink, If LHT65N-E5 doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LHT65N-E5 keeps sending messages in normal periodically. Once LHT65N-E5 gets ACK from a server, it will consider the network is ok and start to send the not-arrive message. 871 - 872 - 873 -(% style="color:#4f81bd" %)**AT Command: AT+PNACKMD** 874 - 875 -The default factory setting is 0 876 - 877 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:367px" %) 878 -|=(% style="width: 158px;" %)**Command Example**|=(% style="width: 118px;" %)**Function**|=(% style="width: 87px;" %)**Response** 879 -|(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK 880 - 881 -(% style="color:#4f81bd" %)**Downlink Command: 0x34** 882 - 883 -* Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 884 - 885 -= 5. Battery & How to replace = 886 - 887 -== 5.1 Battery Type == 888 - 889 - 890 -((( 891 -LHT65N-E5 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. 892 -))) 893 - 894 -((( 895 -The discharge curve is not linear so can't simply use percentage to show the battery level. Below is the battery performance. 896 - 897 - 898 -[[image:image-20220515075034-1.png||_mstalt="428961" height="208" width="644"]] 899 -))) 900 - 901 -The minimum Working Voltage for the LHT65N-E5 is ~~ 2.5v. When battery is lower than 2.6v, it is time to change the battery. 902 - 903 - 904 -== 5.2 Replace Battery == 905 - 906 - 907 -LHT65N-E5 has two screws on the back, Unscrew them, and changing the battery inside is ok. The battery is a general CR17450 battery (3.0v). Any brand should be ok. 908 - 909 -[[image:image-20220515075440-2.png||_mstalt="429546" height="338" width="272"]][[image:image-20220515075625-3.png||_mstalt="431574" height="193" width="257"]] 910 - 911 - 912 -== 5.3 Battery Life Analyze == 913 - 914 - 915 -((( 916 -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: 917 -[[https:~~/~~/www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf]] 918 -))) 919 - 920 - 921 -((( 922 -A full detail test report for LHT65N-E5 on different frequency can be found at : [[https:~~/~~/www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0>>https://www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0]] 923 -))) 924 - 925 - 926 926 = 6. FAQ = 927 927 928 928 == 6.1 How to use AT Command? ==
- image-20230409080812-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +249.6 KB - Content