Changes for page LHT52 - LoRaWAN Temperature & Humidity Sensor User Manual

Last modified by Mengting Qiu on 2024/04/30 14:27

From version < 50.1 >

edited by Edwin Chen
on 2022/05/23 00:12

To version < 55.2 >

edited by Xiaoling
on 2022/05/23 11:28

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 2 added, 0 removed)
- image-20220523111447-1.jpeg
- image-20220523112300-2.png

Details

Page properties

Author

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

Content

@@ -1,12 +1,17 @@
++(% style="text-align:center" %)
++[[image:image-20220523111447-1.jpeg||height="448" width="448"]]
++
  {{box cssClass="floatinginfobox" title="**Contents**"}}
  {{toc/}}
  {{/box}}
--= Overview =
++{{toc/}}
--[[image:LHT65N_10.png||alt="LHT65_Image" height="265" width="265"]]
++= 1.Introduction =
++== 1.1 What is LHT65N Temperature & Humidity Sensor ==
++
  The Dragino LHT65N Temperature & Humidity sensor is a Long Range LoRaWAN Sensor. It includes a(% class="mark" %) **built-in Temperature & Humidity sensor**(%%) and has an external sensor connector to connect to an external (% class="mark" %)**Temperature Sensor**(%%)**.**
  The LHT65N allows users to send data and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, building automation, and so on.
@@ -19,9 +19,8 @@
  *The actual battery life depends on how often to send data, please see the battery analyzer chapter.
++== 1.2 Features ==
--== Features: ==
--
  * Wall mountable
  * LoRaWAN v1.0.3 Class A protocol
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
@@ -34,7 +34,7 @@
  * Tri-color LED to indicate working status
  * Datalog feature
--== Specification: ==
++== 1.3 Specification ==
  **Built-in Temperature Sensor:**
@@ -57,9 +57,9 @@
  * ±2°C accuracy from -55°C to +125°C
  * Operating Range: -55 °C ~~ 125 °C
--= Connect LHT65N to IoT Server =
++= 2. Connect LHT65N to IoT Server =
--== How does LHT65N work? ==
++== 2.1 How does LHT65N work? ==
  LHT65N is configured as LoRaWAN OTAA Class A mode by default. Each LHT65N is shipped with a worldwide unique set of OTAA keys. To use LHT65N in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N.
@@ -66,7 +66,7 @@
  If LHT65N is under the coverage of this LoRaWAN network. LHT65N can join the LoRaWAN network automatically. After successfully joining, LHT65N will start to measure environment temperature and humidity, and start to transmit sensor data to the LoRaWAN server. The default period for each uplink is 20 minutes.
--== How to Activate LHT65N? ==
++== 2.2 How to Activate LHT65N? ==
  The LHT65N has two working modes:
@@ -77,12 +77,13 @@
  [[image:image-20220515123819-1.png||height="379" width="317"]]
++(% border="1" %)
  |**Behavior on ACT**|**Function**|**Action**
  |**Pressing ACT between 1s < time < 3s**|Test uplink status|If LHT65N is already Joined to the LoRaWAN network, LHT65N will send an uplink packet, if LHT65N has an external sensor connected, blue led will blink once. If LHT65N has no external sensor, red led will blink once.
  |**Pressing ACT for more than 3s**|Active Device|green led will fast blink 5 times, LHT65N will enter working mode and start to JOIN LoRaWAN network. green led will solid turn on for 5 seconds after join in network.
  |**Fast press ACT 5 times**|Deactivate Device|red led will solid on for 5 seconds. This means LHT65N is in Deep Sleep Mode.
--== Example to join LoRaWAN network ==
++== 2.3 Example to join LoRaWAN network ==
  (% class="wikigeneratedid" %)
  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.
@@ -93,7 +93,7 @@
  Assume the LPS8N is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network]], So it provides network coverage for LHT65N. Next we need to add the LHT65N device in TTN V3:
--=== **Step 1**: Create Device n TTN ===
++=== **2.3.1 Step 1**: Create Device n TTN ===
  Create a device in TTN V3 with the OTAA keys from LHT65N.
@@ -123,7 +123,7 @@
  [[image:image-20220522233118-7.png]]
--=== Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
++=== 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
  Use ACT button to activate LHT65N and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
@@ -260,7 +260,7 @@
  [[Time Stamp>>path:#Unix_Time_Stamp]]
  )))
--* **Battery status & **[[(% class="wikiinternallink" %)**Built-in Humidity**>>path:#SHT20_Humidity]]
++* **Battery status & **[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Built-in Humidity**>>path:#SHT20_Humidity]]
  (% style="width:587px" %)
  |Bit(bit)|(% style="width:280px" %)[15:14]|(% style="width:136px" %)[11:0]
@@ -294,7 +294,6 @@
  * Sync time OK: 1: Set time ok，0: N/A. After time SYNC request is sent, LHT65N will set this bit to 0 until got the time stamp from the application server.
  * Unix Time Request:1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this)
--
  == Show data on Datacake ==
  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:
@@ -324,7 +324,182 @@
  [[image:image-20220523000825-10.png||height="432" width="762"]]
++== Datalog Feature ==
++This feature is always enabled. When user wants to retrieve the sensor value, he can send a poll command from the IoT platform to ask LHT65N to send the value in the required time slot.
++
++=== Unix TimeStamp ===
++
++LHT65N uses Unix TimeStamp format based on
++
++[[image:image-20220523001219-11.png||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||height="353" width="853"]]
++
++So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
++
++
++=== Set Device Time ===
++
++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 Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LHT65N. If LHT65N fails to get the time from the server, LHT65N will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
++
++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.
++
++
++=== Poll sensor value ===
++
++User can poll sensor value based on timestamps from the server. Below is the downlink command.
++
++
++(% style="width:454px" %)
++|(% style="width:69px" %)1byte|(% style="width:129px" %)4bytes|(% style="width:134px" %)4bytes|(% style="width:119px" %)1byte
++|(% style="width:69px" %)31|(% style="width:129px" %)Timestamp start|(% style="width:134px" %)Timestamp end|(% style="width:119px" %)Uplink Interval
++
++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 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 will send one packet every 5s. range 5~~255s.
++
++
++=== Datalog Uplink payload ===
++
++The Datalog poll reply uplink will use below payload format.
++
++
++Retrieval data payload
++
++|**Size(bytes)**|**2**|**2**|**2**|**1**|**4**
++|**Value**|[[External sensor data>>path:#Extension_sensor_value]]|(((
++[[Built-In>>path:#SHT20_Temperature]]
++
++[[Temperature>>path:#SHT20_Temperature]]
++)))|(((
++[[Built-in>>path:#SHT20_Humidity]]
++
++[[Humidity>>path:#SHT20_Humidity]]
++)))|[[Poll message flag & Ext>>path:#Poll_EXT]]|(((
++[[Unix Time Stamp>>path:#Unix_Time_Stamp]]
++
++
++)))
++
++Poll message flag & Ext
++
++
++|**Bits**|**7**|**6**|**5**|**4**|**[3:0]**
++|**Status & Ext**|Not Defined|Poll Message Flag|Sync time OK|Unix Time Request|(((
++Ext:
++
++0b(1001)
++)))
++
++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:
++
++a)      DR0: max is 11 bytes so one entry of data
++
++b)      DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
++
++c)      DR2: total payload includes 11 entries of data
++
++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 has below data inside Flash:
++
++Flash Addr   |Unix Time | Ext | BAT voltage|      Value
++
++80196E0 21/1/19 04:27:03 1 3145 sht_temp=22.00 sht_hum=32.6 ds_temp=327.67
++
++80196F0 21/1/19 04:28:57 1 3145 sht_temp=21.90 sht_hum=33.1 ds_temp=327.67
++
++8019700 21/1/19 04:30:30 1 3145 sht_temp=21.81 sht_hum=33.4 ds_temp=327.67
++
++8019710 21/1/19 04:40:30 1 3145 sht_temp=21.65 sht_hum=33.7 ds_temp=327.67
++
++8019720 21/1/19 04:50:30 1 3147 sht_temp=21.55 sht_hum=34.1 ds_temp=327.67
++
++8019730 21/1/19 05:00:30 1 3149 sht_temp=21.50 sht_hum=34.1 ds_temp=327.67
++
++8019740 21/1/19 05:10:30 1 3149 sht_temp=21.43 sht_hum=34.6 ds_temp=327.67
++
++8019750 21/1/19 05:20:30 1 3151 sht_temp=21.35 sht_hum=34.9 ds_temp=327.67
++
++
++If user sends below downlink command:
++
++3160065F9760066DA705
++
++   Where : Start time: 60065F97 = time 21/1/19 04:27:03
++
++          Stop time 60066DA7= time 21/1/19 05:27:03
++
++
++LHT65N will uplink this payload.
++
++[[image:image-20220523001219-13.png]]
++
++7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
++
++Where the first 11 bytes is for the first entry:
++
++7FFF089801464160065F97
++
++Ext sensor data=0x7FFF/100=327.67
++
++Temp=0x0898/100=22.00
++
++Hum=0x0146/10=32.6
++
++poll message flag & Ext=0x41,means reply data,Ext=1
++
++Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
++
++
++== Alarm Mode ==
++
++Alarm mode feature is added since firmware v1.5. When device is in Alarm mode, it will check the built-in sensor temperature in a short interval. If the temperature exceeds the pre-configure range, it will send an uplink immediately.
++
++
++Note: Alarm mode will increase a little big the power consumption, we recommend extending the normal reading time when enabling this feature.
++
++
++AT Commands for Alarm mode:
++
++**AT+WMOD=1**: Enable/Disable Alarm Mode. (0:Disable, 1: Enable)
++
++**AT+CITEMP=1**: The interval to check the temperature for Alarm. (Unit: minute)
++
++
++
  == LED Indicator ==
  The LHT65N has a triple color LED which for easy shows different stage.
@@ -342,7 +342,7 @@
  == Installation ==
--[[image:image-20220516231650-1.png||height="632" width="620"]]
++[[image:image-20220516231650-1.png||height="436" width="428"]]
@@ -362,8 +362,328 @@
  * Operating Range: -40 ~~ 125 °C
  * -55°C to 125°C
  * Working voltage 2.35v ~~ 5v
--
++= Configure LHT65N via AT Command or LoRaWAN Downlink =
++
++Use can configure LHT65N via AT Command or LoRaWAN Downlink.
++
++* AT Command Connection: See [[FAQ>>path:#AT_COMMAND]].
++* LoRaWAN Downlink instruction for different platforms:
++
++[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#Use_Note_for_Server>>url:http://wiki.dragino.com/index.php?title=Main_Page#Use_Note_for_Server]]
++
++
++There are two kinds of commands to configure LHT65N, they are:
++
++* **General Commands**.
++
++These commands are to configure:
++
++* General system settings like: uplink interval.
++* LoRaWAN protocol & radio-related commands.
++
++They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki:
++
++[[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_Downlink_Command>>url:http://wiki.dragino.com/index.php?title=End_Device_Downlink_Command]]
++
++
++
++* **Commands special design for LHT65N**
++
++These commands are only valid for LHT65N, as below:
++
++
++== Set Transmit Interval Time ==
++
++Feature: Change LoRaWAN End Node Transmit Interval.
++
++**AT Command: AT+TDC**
++
++|**Command Example**|**Function**|**Response**
++|AT+TDC?|Show current transmit Interval|(((
++30000
++
++OK
++
++the interval is 30000ms = 30s
++)))
++|AT+TDC=60000|Set Transmit Interval|(((
++OK
++
++Set transmit interval to 60000ms = 60 seconds
++)))
++
++**Downlink Command: 0x01**
++
++Format: Command Code (0x01) followed by 3 bytes time value.
++
++If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
++
++* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
++* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
++
++== Set External Sensor Mode ==
++
++Feature: Change External Sensor Mode.
++
++**AT Command: AT+EXT**
++
++|**Command Example**|**Function**|**Response**
++|AT+EXT?|Get current external sensor mode|(((
++1
++
++OK
++
++External Sensor mode =1
++)))
++|AT+EXT=1|(% colspan="2" %)Set external sensor mode to 1
++|AT+EXT=9|(% colspan="2" %)Set to external DS18B20 with timestamp
++
++**Downlink Command: 0xA2**
++
++Total bytes: 2 ~~ 5 bytes
++
++Example:
++
++* 0xA201: Set external sensor type to E1
++* 0xA209: Same as AT+EXT=9
++* 0xA20702003c,Same as AT+SETCNT=60
++
++== Enable/Disable uplink Temperature probe ID ==
++
++Feature: If PID is enabled, device will send the temperature probe ID on:
++
++* First Packet after OTAA Join
++* Every 24 hours since the first packet.
++
++PID is default set to disable (0)
++
++
++**AT Command:**
++
++|**Command Example**|**Function**|**Response**
++|AT+PID=1|Enable PID uplink|OK
++
++**Downlink Command:**
++
++* 0xA800     à AT+PID=0
++* 0xA801     à AT+PID=1
++
++== Set Password ==
++
++Feature: Set device password, max 9 digits
++
++**AT Command: AT+PWORD**
++
++|**Command Example**|**Function**|**Response**
++|AT+PWORD=?|Show password|(((
++123456
++
++
++OK
++)))
++|AT+PWORD=999999|Set password|OK
++
++**Downlink Command:**
++
++No downlink command for this feature.
++
++
++== Quit AT Command ==
++
++Feature: Quit AT Command mode, so user needs to input password again before use AT Commands.
++
++**AT Command: AT+DISAT**
++
++|**Command Example**|**Function**|**Response**
++|AT+DISAT|Quit AT Commands mode|OK
++
++**Downlink Command:**
++
++No downlink command for this feature.
++
++
++== Set to sleep mode ==
++
++Feature: Set device to sleep mode
++
++**AT Command: AT+SLEEP**
++
++| | |
++|**Command Example**|**Function**|**Response**
++|AT+SLEEP|Set to sleep mode|(((
++Clear all stored sensor data…
++
++OK
++)))
++
++**Downlink Command:**
++
++* There is no downlink command to set to Sleep mode.
++
++== Set system time ==
++
++Feature: Set system time, unix format. [[See here for format detail.>>path:#TimeStamp]]
++
++**AT Command:**
++
++|**Command Example**|**Function**
++|AT+TIMESTAMP=1611104352|(((
++OK
++
++Set System time to 2021-01-20 00:59:12
++)))
++
++**Downlink Command:**
++
++0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
++
++
++== 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.
++
++
++**AT Command:**
++
++|**Command Example**|**Function**
++|AT+SYNCMOD=1|Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq)
++
++**Downlink Command:**
++
++0x28 01 ~/~/ Same As AT+SYNCMOD=1
++
++0x28 00 ~/~/ Same As AT+SYNCMOD=0
++
++
++== Set Time Sync Interval ==
++
++Feature: Define System time sync interval. SYNCTDC default value: 10 days.
++
++**AT Command:**
++
++|**Command Example**|**Function**
++|AT+SYNCTDC=0x0A|Set SYNCTDC to 10 (0x0A), so the sync time is 10 days.
++
++**Downlink Command:**
++
++0x29 0A ~/~/ Same as AT+SYNCTDC=0x0A
++
++
++== Print data entries base on page. ==
++
++Feature: Print the sector data from start page to stop page (max is 416 pages).
++
++**AT Command: AT+PDTA**
++
++|**Command Example**|**Response**
++|(((
++AT+PDTA=1,3
++
++
++
++Print page 1 to 3
++)))|(((
++8019500 19/6/26 16:48 1 2992 sht_temp=28.21 sht_hum=71.5 ds_temp=27.31
++
++8019510 19/6/26 16:53 1 2994 sht_temp=27.64 sht_hum=69.3 ds_temp=26.93
++
++8019520 19/6/26 16:58 1 2996 sht_temp=28.39 sht_hum=72.0 ds_temp=27.06
++
++8019530 19/6/26 17:03 1 2996 sht_temp=27.97 sht_hum=70.4 ds_temp=27.12
++
++8019540 19/6/26 17:08 1 2996 sht_temp=27.80 sht_hum=72.9 ds_temp=27.06
++
++8019550 19/6/26 17:13 1 2998 sht_temp=27.30 sht_hum=72.4 ds_temp=26.68
++
++8019560 19/6/26 17:22 1 2992 sht_temp=26.27 sht_hum=62.3 ds_temp=26.56
++
++8019570
++
++8019580
++
++8019590
++
++80195A0
++
++80195B0
++
++80195C0
++
++80195D0
++
++80195E0
++
++80195F0
++
++
++OK
++)))
++
++**Downlink Command:**
++
++No downlink commands for feature
++
++
++
++== Print last few data entries. ==
++
++Feature: Print the last few data entries
++
++**AT Command: AT+PLDTA**
++
++|**Command Example**|**Response**
++|(((
++AT+PLDTA=5
++
++
++
++Print last 5 entries
++)))|(((
++Stop Tx and RTP events when read sensor data
++
++1 19/6/26 13:59 1 3005 sht_temp=27.09 sht_hum=79.5 ds_temp=26.75
++
++2 19/6/26 14:04 1 3007 sht_temp=26.65 sht_hum=74.8 ds_temp=26.43
++
++3 19/6/26 14:09 1 3007 sht_temp=26.91 sht_hum=77.9 ds_temp=26.56
++
++4 19/6/26 14:15 1 3007 sht_temp=26.93 sht_hum=76.7 ds_temp=26.75
++
++5 19/6/26 14:20 1 3007 sht_temp=26.78 sht_hum=76.6 ds_temp=26.43
++
++Start Tx and RTP events
++
++OK
++)))
++
++**Downlink Command:**
++
++No downlink commands for feature
++
++
++
++== Clear Flash Record ==
++
++Feature: Clear flash storage for data log feature.
++
++**AT Command: AT+CLRDTA**
++
++|**Command Example**|**Function**|**Response**
++|AT+CLRDTA|Clear date record|(((
++Clear all stored sensor data…
++
++OK
++)))
++
++**Downlink Command: 0xA3**
++
++* Example: 0xA301   ~/~/Same as AT+CLRDTA
++
++
  = Battery & How to replace =
  == Battery Type ==

image-20220523111447-1.jpeg

Author

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

Size

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

Content

image-20220523112300-2.png

Author

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

Size

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

Content

Changes for page LHT52 - LoRaWAN Temperature & Humidity Sensor User Manual

Summary

Details

Applications

Navigation