PIR Motion Sensor User Manual

Last modified by Xiaoling on 2025/04/24 10:00

From version < 9.1 >

edited by Edwin Chen
on 2023/04/09 08:24

To version < 4.1 >

edited by Edwin Chen
on 2023/04/09 00:18

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- image-20230409080812-1.png

Details

Page properties

Content

@@ -76,7 +76,6 @@
  * (% class="mark" %)Resolution: 1 lx
  * (% class="mark" %)Range: 0-65535 lx
  * (% class="mark" %)Operating Range: -40 °C ~~ 85 °C
--*
  = 2. Connect LHT65N-PIR to IoT Server =
@@ -111,7 +111,7 @@
  (% class="wikigeneratedid" %)
--[[image:image-20230409080812-1.png||height="487" width="785"]]
++[[image:image-20221224101636-1.png||height="435" width="715"]]
  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:
@@ -131,7 +131,7 @@
  Add APP EUI in the application.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522232916-3.png||_mstalt="430495"]]
++[[image:image-20220522232916-3.png||_mstalt="430495"]]
  [[image:image-20220522232932-4.png||_mstalt="430157"]]
@@ -141,9 +141,12 @@
--(% style="color:red" %)**Note: LHT65N-PIR use same payload decoder as LHT65.**
++(% style="color:red" %)**Note: LHT65N-E5 use same payload decoder as LHT65.**
++[[image:image-20220522233026-6.png||_mstalt="429403"]]
++
++
  Input APP EUI,  APP KEY and DEV EUI:
@@ -150,9 +150,9 @@
  [[image:image-20220522233118-7.png||_mstalt="430430"]]
--=== 2.3.2 Step 2: Activate LHT65N-PIR by pressing the ACT button for more than 5 seconds. ===
++=== 2.3.2 Step 2: Activate LHT65N-E5 by pressing the ACT button for more than 5 seconds. ===
--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.
++Use ACT button to activate LHT65N-E5 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.
  [[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]]
@@ -194,20 +194,20 @@
  [[Ext value>>||anchor="H2.4.6Extvalue"]]
  )))
--* The First 6 bytes: has fix meanings for every LHT65N-PIR.
--* The 7th byte (EXT #): defines the external sensor model. It can be 0x0A for LHT65N-PIR
--* The 8^^th^^ byte: Alarm Bit (if this uplink is from periodically or movement)
--* The 9^^th^^ ~~ 11^^st^^  byte: Movement Detect Count.
++* The First 6 bytes: has fix meanings for every LHT65N-E5.
++* The 7th byte (EXT #): defines the external sensor model. It can be 0x05 or 0x09 for LHT65N-E5
++* The 8^^th^^ ~~ 9^^th^^ byte: Illuminance. Range: 0-65535 lx.
++* The 10th ~~ 11th byte: Reserve, always 0xFFFF
  === 2.4.1 Decoder in TTN V3 ===
--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.
++When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-E5 decoder in TTNv3 for friendly reading.
--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]]
++Below is the position to put the decoder and LHT65N-E5 decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
--[[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"]]
++[[image:image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]]
  === 2.4.2 BAT-Battery Info ===
@@ -221,9 +221,9 @@
  [[image:image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]]
--Check the battery voltage for LHT65N-PIR.
++Check the battery voltage for LHT65N-E5.
--* BAT status=(0xcba4>>14)&0xFF=11(B)，very good
++* BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
  === 2.4.3 Built-in Temperature ===
@@ -263,6 +263,71 @@
            The last 2 bytes of data are meaningless
++
++==== 2.4.5.2 Ext~=0x85, E5 sensor with Unix Timestamp ====
++
++
++(((
++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:
++)))
++
++(((
++
++)))
++
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:535px" %)
++|=(% style="width: 88px;" %)(((
++**Size(bytes)**
++)))|=(% style="width: 93px;" %)(((
++**2**
++)))|=(% style="width: 94px;" %)(((
++**2**
++)))|=(% style="width: 117px;" %)(((
++**2**
++)))|=(% style="width: 54px;" %)(((
++**1**
++)))|=(% style="width: 79px;" %)(((
++**4**
++)))
++|(% style="width:88px" %)(((
++**Value**
++)))|(% style="width:93px" %)(((
++[[External temperature>>||anchor="H4.2SetExternalSensorMode"]]
++)))|(% style="width:94px" %)(((
++[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]]
++)))|(% style="width:117px" %)(((
++BAT Status &
++Illumination
++)))|(% style="width:54px" %)(((
++Status & Ext
++)))|(% style="width:79px" %)(((
++[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]]
++)))
++
++* **Battery status & Built-in Humidity**
++
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:461px" %)
++|=(% style="width: 67px;" %)Bit(bit)|=(% style="width: 256px;" %)[15:14]|=(% style="width: 132px;" %)[11:0]
++|(% style="width:67px" %)Value|(% style="width:256px" %)(((
++BAT Status
++00(b): Ultra Low ( BAT <= 2.50v)
++01(b): Low  (2.50v <=BAT <= 2.55v)
++10(b): OK   (2.55v <= BAT <=2.65v)
++11(b): Good   (BAT >= 2.65v)
++)))|(% style="width:132px" %)(((
++Illumination
++)))
++
++* **Status & Ext Byte**
++
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:500px" %)
++|=(% 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]**
++|=(% 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)
++
++* (% style="color:blue" %)**Poll Message Flag**:(%%)    1: This message is a poll message reply, 0: means this is a normal uplink.
++* (% 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.
++* (% 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)
++
  == 2.5 Show data on Datacake ==
@@ -308,11 +308,239 @@
  [[image:image-20221224161957-6.png||height="306" width="852"]]
++== 2.6 Datalog Feature ==
++
++(((
++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.
++)))
++
++
++=== 2.6.1 Ways to get datalog via LoRaWAN ===
++
++
++There are two methods:
++
++(% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range.
++
++
++(% 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.
++
++
++(% style="color:red" %)**Note for method 2:**
++
++* a) LHT65N-E5 will do an ACK check for data records sending to make sure every data arrive server.
++* 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.
++
++Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
++
++
++[[image:image-20220703111700-2.png||_mstalt="426244" height="381" width="1119"]]
++
++
++=== 2.6.2 Unix TimeStamp ===
++
++
++LHT65N-E5 uses Unix TimeStamp format based on
++
++
++[[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]]
++
++
++
++User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
++
++Below is the converter example
++
++[[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]]
++
++
++So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
++
++
++=== 2.6.3 Set Device Time ===
++
++
++(((
++(% style="color:blue" %)**There are two ways to set device's time:**
++)))
++
++(((
++**1.  Through LoRaWAN MAC Command (Default settings)**
++)))
++
++(((
++User need to set SYNCMOD=1 to enable sync time via MAC command.
++)))
++
++(((
++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).
++)))
++
++(((
++(% 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.**
++)))
++
++
++(((
++**2. Manually Set Time**
++)))
++
++(((
++User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
++)))
++
++
++=== 2.6.4 Poll sensor value ===
++
++
++User can poll sensor value based on timestamps from the server. Below is the downlink command.
++
++[[image:image-20220523152302-15.png||_mstalt="451581"]]
++
++
++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.
++
++For example, downlink command (% _mstmutation="1" %)**31 5FC5F350 5FC6 0160 05**(%%)
++
++Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data
++
++Uplink Internal =5s，means LHT65N-E5 will send one packet every 5s. range 5~~255s.
++
++
++=== 2.6.5 Datalog Uplink payload ===
++
++
++The Datalog poll reply uplink will use below payload format.
++
++**Retrieval data payload:**
++
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:480px" %)
++|=(% style="width: 60px;" %)(((
++**Size(bytes)**
++)))|=(% style="width: 90px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 70px;" %)**2**|=(% style="width: 100px;" %)**1**|=(% style="width: 70px;" %)**4**
++|(% 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"]]
++
++**Poll message flag & Ext:**
++
++[[image:image-20221006192726-1.png||_mstalt="430508" height="112" width="754"]]
++
++(% 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)
++
++(% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply.
++
++* Poll Message Flag is set to 1.
++
++* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
++
++For example, in US915 band, the max payload for different DR is:
++
++(% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data
++
++(% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
++
++(% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data
++
++(% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data.
++
++If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0
++
++
++**Example:**
++
++If LHT65N-E5 has below data inside Flash:
++
++[[image:image-20220523144455-1.png||_mstalt="430040" height="335" width="735"]]
++
++
++If user sends below downlink command:  (% style="background-color:yellow" %)3160065F9760066DA705
++
++Where : Start time: 60065F97 = time 21/1/19 04:27:03
++
++             Stop time: 60066DA7= time 21/1/19 05:27:03
++
++
++**LHT65N-E5 will uplink this payload.**
++
++[[image:image-20220523001219-13.png||_mstalt="451204" height="421" style="text-align:left" width="727"]]
++
++
++__**7FFF089801464160065F97**__ **__7FFF__ __088E__ __014B__ __41__ __60066009__** 7FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
++
++Where the first 11 bytes is for the first entry:
++
++7FFF089801464160065F97
++
++Ext sensor data=0x7FFF/100=327.67
++
++Temp=0x088E/100=22.00
++
++Hum=0x014B/10=32.6
++
++poll message flag & Ext=0x41,means reply data,Ext=1
++
++Unix time is 0x60066009=1611030423s=21/1/19 04:27:03
++
++
++== 2.7 Alarm Mode ==
++
++(((
++
++
++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.
++)))
++
++(((
++(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.**
++
++
++)))
++
++=== 2.7.1 ALARM MODE ===
++
++
++(% class="box infomessage" %)
++(((
++(((
++**AT+WMOD=1**:              Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor)
++)))
++
++(((
++**AT+CITEMP=1**:             The interval between checking the alarm temperature. (In minutes)
++)))
++
++(((
++**AT+ARTEMP**:                 Gets or sets the alarm range of the internal temperature sensor
++)))
++
++(((
++(% _mstmutation="1" %)**AT+ARTEMP=？ **(%%):          Gets the alarm range of the internal temperature sensor(% style="display:none" %)
++)))
++
++(((
++**AT+ARTEMP=45,105**:   Set the internal temperature sensor alarm range from 45 to 105.
++)))
++)))
++
++(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
++
++Total bytes: 8 bytes
++
++**Example:**AA0100010001003C
++
++WMOD=01
++
++CITEMP=0001
++
++TEMPlow=0001
++
++TEMPhigh=003C
++
++
  == 2.8 LED Indicator ==
--The LHT65N-PIR has a triple color LED which for easy showing different stage .
++The LHT65 has a triple color LED which for easy showing different stage .
  While user press ACT button, the LED will work as per LED status with ACT button.
@@ -343,13 +343,19 @@
  Use for AT Command
  )))
  * (((
--Update firmware for LHT65N-PIR
++Update firmware for LHT65N-E5
  )))
++* (((
++Exposed All pins from the LHT65N Type-C connector.
++
++
++)))
++
  [[image:image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]]
--= 4. Configure LHT65N-PIR via AT command or LoRaWAN downlink =
++= 4. Configure LHT65N-E5 via AT command or LoRaWAN downlink =
  (((
@@ -460,6 +460,127 @@
  * There is no downlink command to set to Sleep mode.
++== 4.4 Set system time ==
++
++
++Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
++
++
++(% style="color:#4f81bd" %)**AT Command:**
++
++[[image:image-20220523151253-8.png||_mstalt="430677"]]
++
++
++(% style="color:#4f81bd" %)**Downlink Command:**
++
++0x306007806000        ~/~/  Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
++
++
++== 4.5 Set Time Sync Mode ==
++
++
++(((
++Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
++)))
++
++(((
++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.
++
++
++)))
++
++(% style="color:#4f81bd" %)**AT Command:**
++
++[[image:image-20220523151336-9.png||_mstalt="431717"]]
++
++
++(% style="color:#4f81bd" %)**Downlink Command:**
++
++0x28 01             ~/~/  Same As AT+SYNCMOD=1
++0x28 00             ~/~/  Same As AT+SYNCMOD=0
++
++
++== 4.6 Set Time Sync Interval ==
++
++
++Feature: Define System time sync interval. SYNCTDC default value: 10 days.
++
++
++(% style="color:#4f81bd" %)**AT Command:**
++
++[[image:image-20220523151411-10.png||_mstalt="449696"]]
++
++
++(% style="color:#4f81bd" %)**Downlink Command:**
++
++**0x29 0A**       ~/~/ Same as AT+SYNCTDC=0x0A
++
++
++== 4.7 Print data entries base on page. ==
++
++
++Feature: Print the sector data from start page to stop page (max is 416 pages).
++
++
++(% style="color:#4f81bd" %)**AT Command: AT+PDTA**
++
++[[image:image-20220523151450-11.png||_mstalt="451035"]]
++
++
++(% style="color:#4f81bd" %)**Downlink Command:**
++
++No downlink commands for feature
++
++
++== 4.8 Print last few data entries. ==
++
++
++Feature: Print the last few data entries
++
++
++(% style="color:#4f81bd" %)**AT Command: AT+PLDTA**
++
++[[image:image-20220523151524-12.png||_mstalt="452101"]]
++
++
++(% style="color:#4f81bd" %)**Downlink Command:**
++
++No downlink commands for feature
++
++
++== 4.9 Clear Flash Record ==
++
++
++Feature: Clear flash storage for data log feature.
++
++
++(% style="color:#4f81bd" %)**AT Command: AT+CLRDTA**
++
++[[image:image-20220523151556-13.png||_mstalt="454129"]]
++
++
++(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
++
++* Example: 0xA301        ~/~/  Same as AT+CLRDTA
++
++== 4.10 Auto Send None-ACK messages ==
++
++
++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.
++
++
++(% style="color:#4f81bd" %)**AT Command: AT+PNACKMD**
++
++The default factory setting is 0
++
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:367px" %)
++|=(% style="width: 158px;" %)**Command Example**|=(% style="width: 118px;" %)**Function**|=(% style="width: 87px;" %)**Response**
++|(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK
++
++(% style="color:#4f81bd" %)**Downlink Command: 0x34**
++
++* Example: 0x3401       ~/~/  Same as AT+PNACKMD=1
++
  = 5. Battery & How to replace =
  == 5.1 Battery Type ==

image-20230409080812-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-249.6 KB

Content

Changes for page LHT65N-PIR Temperature/Humidity/PIR Motion Sensor User Manual

Summary

Details

Applications

Navigation