Wiki source code of LHT65N LoRaWAN Temperature & Humidity Sensor Manual
Version 102.1 by Edwin Chen on 2022/05/25 11:52
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% style="text-align:center" %) | ||
| 2 | [[image:image-20220523115324-1.jpeg||height="317" width="317"]] | ||
| 3 | |||
| 4 | |||
| 5 | **LHT65N LoRaWAN Temperature & Humidity Sensor Manual** | ||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | |||
| 10 | **Table of Contents：** | ||
| 11 | |||
| 12 | {{toc/}} | ||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | |||
| 17 | = 1. Introduction = | ||
| 18 | |||
| 19 | == 1.1 What is LHT65N Temperature & Humidity Sensor == | ||
| 20 | |||
| 21 | ((( | ||
| 22 | The Dragino LHT65N Temperature & Humidity sensor is a Long Range LoRaWAN Sensor. It includes a (% style="color:#4f81bd" %)**built-in Temperature & Humidity sensor**(%%) and has an external sensor connector to connect to an external (% style="color:#4f81bd" %)**Temperature Sensor**(%%)**.** | ||
| 23 | ))) | ||
| 24 | |||
| 25 | ((( | ||
| 26 | 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. | ||
| 27 | ))) | ||
| 28 | |||
| 29 | ((( | ||
| 30 | LHT65N has a built-in 2400mAh non-chargeable battery which can be used for up to 10 years*. | ||
| 31 | ))) | ||
| 32 | |||
| 33 | ((( | ||
| 34 | LHT65N is full compatible with LoRaWAN v1.0.3 Class A protocol, it can work with a standard LoRaWAN gateway. | ||
| 35 | ))) | ||
| 36 | |||
| 37 | ((( | ||
| 38 | LHT65N supports (% style="color:#4f81bd" %)**Datalog Feature**(%%). It will record the data when there is no network coverage and users can retrieve the sensor value later to ensure no miss for every sensor reading. | ||
| 39 | ))) | ||
| 40 | |||
| 41 | ((( | ||
| 42 | *The actual battery life depends on how often to send data, please see the battery analyzer chapter. | ||
| 43 | ))) | ||
| 44 | |||
| 45 | == 1.2 Features == | ||
| 46 | |||
| 47 | * Wall mountable | ||
| 48 | * LoRaWAN v1.0.3 Class A protocol | ||
| 49 | * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915 | ||
| 50 | * AT Commands to change parameters | ||
| 51 | * Remote configure parameters via LoRaWAN Downlink | ||
| 52 | * Firmware upgradeable via program port | ||
| 53 | * Built-in 2400mAh battery for up to 10 years of use. | ||
| 54 | * Built-in Temperature & Humidity sensor | ||
| 55 | * Optional External Sensors | ||
| 56 | * Tri-color LED to indicate working status | ||
| 57 | * Datalog feature | ||
| 58 | |||
| 59 | == 1.3 Specification == | ||
| 60 | |||
| 61 | ((( | ||
| 62 | **Built-in Temperature Sensor:** | ||
| 63 | ))) | ||
| 64 | |||
| 65 | * ((( | ||
| 66 | Resolution: 0.01 °C | ||
| 67 | ))) | ||
| 68 | * ((( | ||
| 69 | Accuracy Tolerance : Typ ±0.3 °C | ||
| 70 | ))) | ||
| 71 | * ((( | ||
| 72 | Long Term Drift: < 0.02 °C/yr | ||
| 73 | ))) | ||
| 74 | * ((( | ||
| 75 | Operating Range: -40 ~~ 85 °C | ||
| 76 | ))) | ||
| 77 | |||
| 78 | ((( | ||
| 79 | **Built-in Humidity Sensor:** | ||
| 80 | ))) | ||
| 81 | |||
| 82 | * ((( | ||
| 83 | Resolution: 0.04 %RH | ||
| 84 | ))) | ||
| 85 | * ((( | ||
| 86 | Accuracy Tolerance : Typ ±3 %RH | ||
| 87 | ))) | ||
| 88 | * ((( | ||
| 89 | Long Term Drift: < 0.02 °C/yr | ||
| 90 | ))) | ||
| 91 | * ((( | ||
| 92 | Operating Range: 0 ~~ 96 %RH | ||
| 93 | ))) | ||
| 94 | |||
| 95 | ((( | ||
| 96 | **External Temperature Sensor:** | ||
| 97 | ))) | ||
| 98 | |||
| 99 | * ((( | ||
| 100 | Resolution: 0.0625 °C | ||
| 101 | ))) | ||
| 102 | * ((( | ||
| 103 | ±0.5°C accuracy from -10°C to +85°C | ||
| 104 | ))) | ||
| 105 | * ((( | ||
| 106 | ±2°C accuracy from -55°C to +125°C | ||
| 107 | ))) | ||
| 108 | * ((( | ||
| 109 | Operating Range: -55 °C ~~ 125 °C | ||
| 110 | ))) | ||
| 111 | |||
| 112 | = 2. Connect LHT65N to IoT Server = | ||
| 113 | |||
| 114 | == 2.1 How does LHT65N work? == | ||
| 115 | |||
| 116 | ((( | ||
| 117 | 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. | ||
| 118 | ))) | ||
| 119 | |||
| 120 | ((( | ||
| 121 | 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. | ||
| 122 | ))) | ||
| 123 | |||
| 124 | == 2.2 How to Activate LHT65N? == | ||
| 125 | |||
| 126 | The LHT65N has two working modes: | ||
| 127 | |||
| 128 | * **Deep Sleep Mode**: LHT65N doesn’t have any LoRaWAN activation. This mode is used for storage and shipping to save battery life. | ||
| 129 | * **Working Mode**: In this mode, LHT65N works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65 will be in STOP mode (IDLE mode), in STOP mode, LHT65N has the same power consumption as Deep Sleep mode. | ||
| 130 | |||
| 131 | ((( | ||
| 132 | The LHT65N is set in deep sleep mode by default; The ACT button on the front is to switch to different modes: | ||
| 133 | ))) | ||
| 134 | |||
| 135 | [[image:image-20220515123819-1.png||height="379" width="317"]] | ||
| 136 | |||
| 137 | [[image:image-20220525110604-2.png]] | ||
| 138 | |||
| 139 | == 2.3 Example to join LoRaWAN network == | ||
| 140 | |||
| 141 | (% class="wikigeneratedid" %) | ||
| 142 | 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. | ||
| 143 | |||
| 144 | (% class="wikigeneratedid" %) | ||
| 145 | [[image:image-20220522232442-1.png||height="387" width="648"]] | ||
| 146 | |||
| 147 | 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: | ||
| 148 | |||
| 149 | |||
| 150 | === 2.3.1 Step 1: Create Device n TTN === | ||
| 151 | |||
| 152 | Create a device in TTN V3 with the OTAA keys from LHT65N. | ||
| 153 | |||
| 154 | Each LHT65N is shipped with a sticker with its device EUI, APP Key and APP EUI as below: | ||
| 155 | |||
| 156 | [[image:image-20220522232812-2.png||height="219" width="279"]] | ||
| 157 | |||
| 158 | User can enter these keys in the LoRaWAN Server portal. Below is TTN V3 screenshot: | ||
| 159 | |||
| 160 | Add APP EUI in the application. | ||
| 161 | |||
| 162 | [[image:image-20220522232916-3.png]] | ||
| 163 | |||
| 164 | [[image:image-20220522232932-4.png]] | ||
| 165 | |||
| 166 | [[image:image-20220522232954-5.png]] | ||
| 167 | |||
| 168 | Note: LHT65N use same payload as LHT65. | ||
| 169 | |||
| 170 | [[image:image-20220522233026-6.png]] | ||
| 171 | |||
| 172 | |||
| 173 | Input APP EUI, APP KEY and DEV EUI: | ||
| 174 | |||
| 175 | [[image:image-20220522233118-7.png]] | ||
| 176 | |||
| 177 | |||
| 178 | === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. === | ||
| 179 | |||
| 180 | 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. | ||
| 181 | |||
| 182 | [[image:image-20220522233300-8.png||height="219" width="722"]] | ||
| 183 | |||
| 184 | |||
| 185 | == 2.4 Uplink Payload == | ||
| 186 | |||
| 187 | The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default. | ||
| 188 | |||
| 189 | After each uplink, the (% style="color:blue" %)**BLUE LED**(%%) will blink once. | ||
| 190 | |||
| 191 | (% border="1" style="background-color:#ffffcc; color:green; width:426px" %) | ||
| 192 | |(% style="width:97px" %)((( | ||
| 193 | **Size(bytes)** | ||
| 194 | )))|(% style="width:39px" %)((( | ||
| 195 | **2** | ||
| 196 | )))|(% style="width:100px" %)((( | ||
| 197 | **2** | ||
| 198 | )))|(% style="width:77px" %)((( | ||
| 199 | **2** | ||
| 200 | )))|(% style="width:47px" %)((( | ||
| 201 | **1** | ||
| 202 | )))|(% style="width:51px" %)((( | ||
| 203 | **4** | ||
| 204 | ))) | ||
| 205 | |(% style="width:97px" %)((( | ||
| 206 | **Value** | ||
| 207 | )))|(% style="width:39px" %)((( | ||
| 208 | [[BAT>>||anchor="H2.4.2BAT-BatteryInfo"]] | ||
| 209 | )))|(% style="width:100px" %)((( | ||
| 210 | ((( | ||
| 211 | [[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]] | ||
| 212 | ))) | ||
| 213 | )))|(% style="width:77px" %)((( | ||
| 214 | ((( | ||
| 215 | [[Built-in>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 216 | ))) | ||
| 217 | |||
| 218 | ((( | ||
| 219 | [[Humidity>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 220 | ))) | ||
| 221 | )))|(% style="width:47px" %)((( | ||
| 222 | [[Ext>>||anchor="H2.4.5Ext23"]] # | ||
| 223 | )))|(% style="width:51px" %)((( | ||
| 224 | [[Ext value>>||anchor="H2.4.6Extvalue"]] | ||
| 225 | ))) | ||
| 226 | |||
| 227 | * The First 6 bytes: has fix meanings for every LHT65N. | ||
| 228 | * The 7th byte (EXT #): defines the external sensor model. | ||
| 229 | * The 8^^th^^ ~~ 11^^th^^ byte: the value for external sensor value. The definition is based on external sensor type. (If EXT=0, there won’t be these four bytes.) | ||
| 230 | |||
| 231 | === 2.4.1 Decoder in TTN V3 === | ||
| 232 | |||
| 233 | When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N decoder in TTNv3 for friendly reading. | ||
| 234 | |||
| 235 | Below is the position to put the decoder and LHT65N decoder can be download from here: | ||
| 236 | |||
| 237 | [[https:~~/~~/www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0 >>https://www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0]] | ||
| 238 | |||
| 239 | [[image:image-20220522234118-10.png||height="353" width="729"]] | ||
| 240 | |||
| 241 | === 2.4.2 BAT-Battery Info === | ||
| 242 | |||
| 243 | These two bytes of BAT include the battery state and the actually voltage | ||
| 244 | |||
| 245 | [[image:image-20220523152839-18.png]] | ||
| 246 | |||
| 247 | [[image:image-20220522235639-1.png||height="139" width="727"]] | ||
| 248 | |||
| 249 | Check the battery voltage for LHT65N. | ||
| 250 | |||
| 251 | * BAT status=(0Xcba4>>14)&0xFF=11(B)，very good | ||
| 252 | * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV | ||
| 253 | |||
| 254 | === 2.4.3 Built-in Temperature === | ||
| 255 | |||
| 256 | [[image:image-20220522235639-2.png||height="138" width="722"]] | ||
| 257 | |||
| 258 | * Temperature: 0x0ABB/100=27.47℃ | ||
| 259 | |||
| 260 | [[image:image-20220522235639-3.png]] | ||
| 261 | |||
| 262 | * Temperature: (0xF5C6-65536)/100=-26.18℃ | ||
| 263 | |||
| 264 | === 2.4.4 Built-in Humidity === | ||
| 265 | |||
| 266 | [[image:image-20220522235639-4.png||height="138" width="722"]] | ||
| 267 | |||
| 268 | * Humidity: 0x025C/10=60.4% | ||
| 269 | |||
| 270 | === 2.4.5 Ext # === | ||
| 271 | |||
| 272 | Bytes for External Sensor: | ||
| 273 | |||
| 274 | [[image:image-20220523152822-17.png]] | ||
| 275 | |||
| 276 | === 2.4.6 Ext value === | ||
| 277 | |||
| 278 | ==== 2.4.6.1 Ext~=1, E3 Temperature Sensor ==== | ||
| 279 | |||
| 280 | [[image:image-20220522235639-5.png]] | ||
| 281 | |||
| 282 | * DS18B20 temp=0x0ADD/100=27.81℃ | ||
| 283 | |||
| 284 | The last 2 bytes of data are meaningless | ||
| 285 | |||
| 286 | [[image:image-20220522235639-6.png]] | ||
| 287 | |||
| 288 | * External temperature= (0xF54F-65536)/100=-27.37℃ | ||
| 289 | |||
| 290 | ((( | ||
| 291 | The last 2 bytes of data are meaningless | ||
| 292 | ))) | ||
| 293 | |||
| 294 | ((( | ||
| 295 | If the external sensor is 0x01, and there is no external temperature connected. The temperature will be set to 7FFF which is 327.67℃ | ||
| 296 | ))) | ||
| 297 | |||
| 298 | |||
| 299 | ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ==== | ||
| 300 | |||
| 301 | Timestamp mode is designed for LHT65N 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: | ||
| 302 | |||
| 303 | (% border="1" style="background-color:#ffffcc; color:green; width:510px" %) | ||
| 304 | |(% style="width:96px" %)((( | ||
| 305 | **Size(bytes)** | ||
| 306 | )))|(% style="width:71px" %)((( | ||
| 307 | **2** | ||
| 308 | )))|(% style="width:99px" %)((( | ||
| 309 | **2** | ||
| 310 | )))|(% style="width:132px" %)((( | ||
| 311 | **2** | ||
| 312 | )))|(% style="width:54px" %)((( | ||
| 313 | **1** | ||
| 314 | )))|(% style="width:64px" %)((( | ||
| 315 | **4** | ||
| 316 | ))) | ||
| 317 | |(% style="width:96px" %)((( | ||
| 318 | **Value** | ||
| 319 | )))|(% style="width:71px" %)((( | ||
| 320 | [[External temperature>>||anchor="H4.2SetExternalSensorMode"]] | ||
| 321 | )))|(% style="width:99px" %)((( | ||
| 322 | ((( | ||
| 323 | [[Built-In>>||anchor="H2.4.3Built-inTemperature"]] | ||
| 324 | ))) | ||
| 325 | |||
| 326 | ((( | ||
| 327 | [[Temperature>>||anchor="H2.4.3Built-inTemperature"]] | ||
| 328 | ))) | ||
| 329 | )))|(% style="width:132px" %)((( | ||
| 330 | ((( | ||
| 331 | BAT Status & | ||
| 332 | ))) | ||
| 333 | |||
| 334 | ((( | ||
| 335 | [[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 336 | ))) | ||
| 337 | )))|(% style="width:54px" %)((( | ||
| 338 | Status & Ext | ||
| 339 | )))|(% style="width:64px" %)((( | ||
| 340 | ((( | ||
| 341 | [[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]] | ||
| 342 | ))) | ||
| 343 | ))) | ||
| 344 | |||
| 345 | * **Battery status & (% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)Built-in Humidity(%%)** | ||
| 346 | |||
| 347 | (% border="1" style="background-color:#ffffcc; color:green; width:469px" %) | ||
| 348 | |(% style="width:65px" %)Bit(bit)|(% style="width:267px" %)[15:14]|(% style="width:134px" %)[11:0] | ||
| 349 | |(% style="width:65px" %)Value|(% style="width:267px" %)((( | ||
| 350 | BAT Status | ||
| 351 | |||
| 352 | 00(b): Ultra Low ( BAT <= 2.50v) | ||
| 353 | |||
| 354 | 01(b): Low (2.50v <=BAT <= 2.55v) | ||
| 355 | |||
| 356 | 10(b): OK (2.55v <= BAT <=2.65v) | ||
| 357 | |||
| 358 | 11(b): Good (BAT >= 2.65v) | ||
| 359 | )))|(% style="width:134px" %)((( | ||
| 360 | [[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 361 | |||
| 362 | |||
| 363 | ))) | ||
| 364 | |||
| 365 | * **Status & Ext Byte** | ||
| 366 | |||
| 367 | [[image:image-20220523152434-16.png]] | ||
| 368 | |||
| 369 | * Poll Message Flag: 1: This message is a poll message reply, 0: means this is a normal uplink. | ||
| 370 | * 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. | ||
| 371 | * 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) | ||
| 372 | |||
| 373 | == 2.5 Show data on Datacake == | ||
| 374 | |||
| 375 | 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: | ||
| 376 | |||
| 377 | ((( | ||
| 378 | **Step 1**: Be sure that your device is programmed and properly connected to the LoRaWAN network. | ||
| 379 | ))) | ||
| 380 | |||
| 381 | ((( | ||
| 382 | **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. | ||
| 383 | ))) | ||
| 384 | |||
| 385 | ((( | ||
| 386 | Add Datacake: | ||
| 387 | ))) | ||
| 388 | |||
| 389 | [[image:image-20220523000825-7.png||height="262" width="583"]] | ||
| 390 | |||
| 391 | |||
| 392 | Select default key as Access Key: | ||
| 393 | |||
| 394 | [[image:image-20220523000825-8.png||height="453" width="406"]] | ||
| 395 | |||
| 396 | In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT65 device. | ||
| 397 | |||
| 398 | [[image:image-20220523000825-9.png||height="366" width="392"]] | ||
| 399 | |||
| 400 | [[image:image-20220523000825-10.png||height="413" width="728"]] | ||
| 401 | |||
| 402 | == 2.6 Datalog Feature == | ||
| 403 | |||
| 404 | 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 will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N. | ||
| 405 | |||
| 406 | === 2.6.1 Ways to get datalog via LoRaWAN === | ||
| 407 | |||
| 408 | There are two methods: | ||
| 409 | |||
| 410 | 1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range. | ||
| 411 | 1. Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N will store the sensor data, and it will send all messages after network recover. | ||
| 412 | |||
| 413 | === 2.6.2 Unix TimeStamp === | ||
| 414 | |||
| 415 | LHT65N uses Unix TimeStamp format based on | ||
| 416 | |||
| 417 | [[image:image-20220523001219-11.png||height="97" width="627"]] | ||
| 418 | |||
| 419 | |||
| 420 | ((( | ||
| 421 | User can get this time from link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] : | ||
| 422 | ))) | ||
| 423 | |||
| 424 | ((( | ||
| 425 | Below is the converter example | ||
| 426 | ))) | ||
| 427 | |||
| 428 | [[image:image-20220523001219-12.png||height="298" width="720"]] | ||
| 429 | |||
| 430 | So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25 | ||
| 431 | |||
| 432 | === 2.6.3 Set Device Time === | ||
| 433 | |||
| 434 | ((( | ||
| 435 | There are two ways to set device’s time: | ||
| 436 | ))) | ||
| 437 | |||
| 438 | ((( | ||
| 439 | **~1. Through LoRaWAN MAC Command (Default settings)** | ||
| 440 | ))) | ||
| 441 | |||
| 442 | ((( | ||
| 443 | User need to set SYNCMOD=1 to enable sync time via MAC command. | ||
| 444 | ))) | ||
| 445 | |||
| 446 | ((( | ||
| 447 | 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). | ||
| 448 | ))) | ||
| 449 | |||
| 450 | ((( | ||
| 451 | 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. | ||
| 452 | ))) | ||
| 453 | |||
| 454 | ((( | ||
| 455 | |||
| 456 | ))) | ||
| 457 | |||
| 458 | ((( | ||
| 459 | **2. Manually Set Time** | ||
| 460 | ))) | ||
| 461 | |||
| 462 | ((( | ||
| 463 | User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server. | ||
| 464 | ))) | ||
| 465 | |||
| 466 | === 2.6.4 Poll sensor value === | ||
| 467 | |||
| 468 | User can poll sensor value based on timestamps from the server. Below is the downlink command. | ||
| 469 | |||
| 470 | [[image:image-20220523152302-15.png]] | ||
| 471 | |||
| 472 | ((( | ||
| 473 | 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. | ||
| 474 | ))) | ||
| 475 | |||
| 476 | ((( | ||
| 477 | For example, downlink command (% style="display:none" %) (%%)**31 5FC5F350 5FC6 0160 05** | ||
| 478 | ))) | ||
| 479 | |||
| 480 | ((( | ||
| 481 | Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data | ||
| 482 | ))) | ||
| 483 | |||
| 484 | ((( | ||
| 485 | Uplink Internal =5s，means LHT65N will send one packet every 5s. range 5~~255s. | ||
| 486 | ))) | ||
| 487 | |||
| 488 | |||
| 489 | === 2.6.5 Datalog Uplink payload === | ||
| 490 | |||
| 491 | The Datalog poll reply uplink will use below payload format. | ||
| 492 | |||
| 493 | ((( | ||
| 494 | **Retrieval data payload** | ||
| 495 | ))) | ||
| 496 | |||
| 497 | (% border="1" style="background-color:#ffffcc; color:green; width:510px" %) | ||
| 498 | |(% style="width:93px" %)((( | ||
| 499 | ((( | ||
| 500 | **Size(bytes)** | ||
| 501 | ))) | ||
| 502 | )))|(% style="width:71px" %)((( | ||
| 503 | ((( | ||
| 504 | **2** | ||
| 505 | ))) | ||
| 506 | )))|(% style="width:102px" %)((( | ||
| 507 | ((( | ||
| 508 | **2** | ||
| 509 | ))) | ||
| 510 | )))|(% style="width:86px" %)((( | ||
| 511 | ((( | ||
| 512 | **2** | ||
| 513 | ))) | ||
| 514 | )))|(% style="width:86px" %)((( | ||
| 515 | ((( | ||
| 516 | **1** | ||
| 517 | ))) | ||
| 518 | )))|(% style="width:48px" %)((( | ||
| 519 | ((( | ||
| 520 | **4** | ||
| 521 | ))) | ||
| 522 | ))) | ||
| 523 | |(% style="width:93px" %)((( | ||
| 524 | ((( | ||
| 525 | **Value** | ||
| 526 | ))) | ||
| 527 | )))|(% style="width:71px" %)((( | ||
| 528 | ((( | ||
| 529 | [[External sensor data>>||anchor="H2.4.6Extvalue"]] | ||
| 530 | ))) | ||
| 531 | )))|(% style="width:102px" %)((( | ||
| 532 | ((( | ||
| 533 | ((( | ||
| 534 | [[Built In>>||anchor="H2.4.3Built-inTemperature"]] | ||
| 535 | ))) | ||
| 536 | ))) | ||
| 537 | |||
| 538 | ((( | ||
| 539 | ((( | ||
| 540 | [[Temperature>>||anchor="H2.4.3Built-inTemperature"]] | ||
| 541 | ))) | ||
| 542 | ))) | ||
| 543 | )))|(% style="width:86px" %)((( | ||
| 544 | ((( | ||
| 545 | ((( | ||
| 546 | [[Built-in>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 547 | ))) | ||
| 548 | ))) | ||
| 549 | |||
| 550 | ((( | ||
| 551 | ((( | ||
| 552 | [[Humidity>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 553 | ))) | ||
| 554 | ))) | ||
| 555 | )))|(% style="width:86px" %)((( | ||
| 556 | ((( | ||
| 557 | Poll message flag & Ext | ||
| 558 | ))) | ||
| 559 | )))|(% style="width:48px" %)((( | ||
| 560 | ((( | ||
| 561 | ((( | ||
| 562 | [[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]] | ||
| 563 | ))) | ||
| 564 | ))) | ||
| 565 | |||
| 566 | ((( | ||
| 567 | ((( | ||
| 568 | |||
| 569 | ))) | ||
| 570 | ))) | ||
| 571 | ))) | ||
| 572 | |||
| 573 | **Poll message flag & Ext** | ||
| 574 | |||
| 575 | [[image:image-20220523152208-14.png]] | ||
| 576 | |||
| 577 | ((( | ||
| 578 | ((( | ||
| 579 | Poll Message Flag: 1: This message is a poll message reply. | ||
| 580 | ))) | ||
| 581 | ))) | ||
| 582 | |||
| 583 | * ((( | ||
| 584 | ((( | ||
| 585 | Poll Message Flag is set to 1. | ||
| 586 | ))) | ||
| 587 | ))) | ||
| 588 | * ((( | ||
| 589 | ((( | ||
| 590 | Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands. | ||
| 591 | ))) | ||
| 592 | ))) | ||
| 593 | |||
| 594 | ((( | ||
| 595 | ((( | ||
| 596 | For example, in US915 band, the max payload for different DR is: | ||
| 597 | ))) | ||
| 598 | ))) | ||
| 599 | |||
| 600 | ((( | ||
| 601 | ((( | ||
| 602 | a) DR0: max is 11 bytes so one entry of data | ||
| 603 | ))) | ||
| 604 | ))) | ||
| 605 | |||
| 606 | ((( | ||
| 607 | ((( | ||
| 608 | b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) | ||
| 609 | ))) | ||
| 610 | ))) | ||
| 611 | |||
| 612 | ((( | ||
| 613 | ((( | ||
| 614 | c) DR2: total payload includes 11 entries of data | ||
| 615 | ))) | ||
| 616 | ))) | ||
| 617 | |||
| 618 | ((( | ||
| 619 | ((( | ||
| 620 | d) DR3: total payload includes 22 entries of data. | ||
| 621 | ))) | ||
| 622 | ))) | ||
| 623 | |||
| 624 | ((( | ||
| 625 | ((( | ||
| 626 | If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0 | ||
| 627 | ))) | ||
| 628 | ))) | ||
| 629 | |||
| 630 | |||
| 631 | **Example:** | ||
| 632 | |||
| 633 | If LHT65N has below data inside Flash: | ||
| 634 | |||
| 635 | [[image:image-20220523144455-1.png||height="335" width="735"]] | ||
| 636 | |||
| 637 | ((( | ||
| 638 | If user sends below downlink command: (% style="background-color:yellow" %)3160065F9760066DA705 | ||
| 639 | ))) | ||
| 640 | |||
| 641 | ((( | ||
| 642 | Where : Start time: 60065F97 = time 21/1/19 04:27:03 | ||
| 643 | ))) | ||
| 644 | |||
| 645 | ((( | ||
| 646 | Stop time 60066DA7= time 21/1/19 05:27:03 | ||
| 647 | ))) | ||
| 648 | |||
| 649 | ((( | ||
| 650 | |||
| 651 | ))) | ||
| 652 | |||
| 653 | ((( | ||
| 654 | LHT65N will uplink this payload. | ||
| 655 | ))) | ||
| 656 | |||
| 657 | [[image:image-20220523001219-13.png||height="421" width="727"]] | ||
| 658 | |||
| 659 | 7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E | ||
| 660 | |||
| 661 | Where the first 11 bytes is for the first entry: | ||
| 662 | |||
| 663 | 7FFF089801464160065F97 | ||
| 664 | |||
| 665 | Ext sensor data=0x7FFF/100=327.67 | ||
| 666 | |||
| 667 | Temp=0x0898/100=22.00 | ||
| 668 | |||
| 669 | Hum=0x0146/10=32.6 | ||
| 670 | |||
| 671 | poll message flag & Ext=0x41,means reply data,Ext=1 | ||
| 672 | |||
| 673 | Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03 | ||
| 674 | |||
| 675 | == 2.7 Alarm Mode == | ||
| 676 | |||
| 677 | 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. | ||
| 678 | |||
| 679 | ((( | ||
| 680 | (% style="color:red" %)Note: Alarm mode will increase a little big the power consumption, we recommend extending the normal reading time when enabling this feature. | ||
| 681 | ))) | ||
| 682 | |||
| 683 | **AT Commands for Alarm mode:** | ||
| 684 | |||
| 685 | (% class="box infomessage" %) | ||
| 686 | ((( | ||
| 687 | ((( | ||
| 688 | **AT+WMOD=1**: Enable/Disable Alarm Mode. (0:Disable, 1: Enable) | ||
| 689 | **AT+CITEMP=1**: The interval to check the temperature for Alarm. (Unit: minute) | ||
| 690 | ))) | ||
| 691 | ))) | ||
| 692 | |||
| 693 | == 2.8 LED Indicator == | ||
| 694 | |||
| 695 | ((( | ||
| 696 | The LHT65N has a triple color LED which for easy shows different stage. | ||
| 697 | ))) | ||
| 698 | |||
| 699 | ((( | ||
| 700 | While pressing ACT button, the LED will work as per LED status with ACT button. | ||
| 701 | ))) | ||
| 702 | |||
| 703 | ((( | ||
| 704 | In a normal working state: | ||
| 705 | ))) | ||
| 706 | |||
| 707 | * ((( | ||
| 708 | For each uplink, the BLUE LED or RED LED will blink once. | ||
| 709 | ))) | ||
| 710 | * ((( | ||
| 711 | BLUE LED when an external sensor is connected | ||
| 712 | ))) | ||
| 713 | * ((( | ||
| 714 | RED LED when an external sensor is not connected | ||
| 715 | ))) | ||
| 716 | * ((( | ||
| 717 | For each success downlink, the PURPLE LED will blink once | ||
| 718 | ))) | ||
| 719 | |||
| 720 | ---- | ||
| 721 | |||
| 722 | == 2.9 Installation == | ||
| 723 | |||
| 724 | [[image:image-20220516231650-1.png||height="436" width="428"]] | ||
| 725 | |||
| 726 | = 3. Sensors & Accessories = | ||
| 727 | |||
| 728 | == 3.1 E3 Temperature Probe == | ||
| 729 | |||
| 730 | [[image:image-20220515080154-4.png||height="182" width="161"]] [[image:image-20220515080330-5.png||height="201" width="195"]] | ||
| 731 | |||
| 732 | |||
| 733 | With Temperature sensor with 2 meters cable long | ||
| 734 | |||
| 735 | * Resolution: 0.0625 °C | ||
| 736 | * ±0.5°C accuracy from -10°C to +85°C | ||
| 737 | * ±2°C accuracy from -55°C to +125°C | ||
| 738 | * Operating Range: -40 ~~ 125 °C | ||
| 739 | * -55°C to 125°C | ||
| 740 | * Working voltage 2.35v ~~ 5v | ||
| 741 | |||
| 742 | = 4. Configure LHT65N via AT Command or LoRaWAN Downlink = | ||
| 743 | |||
| 744 | ((( | ||
| 745 | Use can configure LHT65N via AT Command or LoRaWAN Downlink. | ||
| 746 | ))) | ||
| 747 | |||
| 748 | * ((( | ||
| 749 | AT Command Connection: See [[FAQ>>path:#AT_COMMAND]]. | ||
| 750 | ))) | ||
| 751 | * ((( | ||
| 752 | LoRaWAN Downlink instruction for different platforms: | ||
| 753 | ))) | ||
| 754 | |||
| 755 | ((( | ||
| 756 | [[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]] | ||
| 757 | ))) | ||
| 758 | |||
| 759 | ((( | ||
| 760 | There are two kinds of commands to configure LHT65N, they are: | ||
| 761 | ))) | ||
| 762 | |||
| 763 | ((( | ||
| 764 | (% style="color:#4f81bd" %)* **General Commands**. | ||
| 765 | ))) | ||
| 766 | |||
| 767 | ((( | ||
| 768 | These commands are to configure: | ||
| 769 | ))) | ||
| 770 | |||
| 771 | * ((( | ||
| 772 | General system settings like: uplink interval. | ||
| 773 | ))) | ||
| 774 | * ((( | ||
| 775 | LoRaWAN protocol & radio-related commands. | ||
| 776 | ))) | ||
| 777 | |||
| 778 | ((( | ||
| 779 | They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: | ||
| 780 | ))) | ||
| 781 | |||
| 782 | ((( | ||
| 783 | [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_Downlink_Command>>url:http://wiki.dragino.com/index.php?title=End_Device_Downlink_Command]] | ||
| 784 | ))) | ||
| 785 | |||
| 786 | ((( | ||
| 787 | (% style="color:#4f81bd" %)* **Commands special design for LHT65N** | ||
| 788 | ))) | ||
| 789 | |||
| 790 | ((( | ||
| 791 | These commands are only valid for LHT65N, as below: | ||
| 792 | ))) | ||
| 793 | |||
| 794 | == 4.1 Set Transmit Interval Time == | ||
| 795 | |||
| 796 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
| 797 | |||
| 798 | **AT Command: AT+TDC** | ||
| 799 | |||
| 800 | [[image:image-20220523150701-2.png]] | ||
| 801 | |||
| 802 | ((( | ||
| 803 | **Downlink Command: 0x01** | ||
| 804 | ))) | ||
| 805 | |||
| 806 | ((( | ||
| 807 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
| 808 | ))) | ||
| 809 | |||
| 810 | ((( | ||
| 811 | If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
| 812 | ))) | ||
| 813 | |||
| 814 | * ((( | ||
| 815 | **Example 1**: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
| 816 | ))) | ||
| 817 | * ((( | ||
| 818 | **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
| 819 | ))) | ||
| 820 | |||
| 821 | == 4.2 Set External Sensor Mode == | ||
| 822 | |||
| 823 | Feature: Change External Sensor Mode. | ||
| 824 | |||
| 825 | **AT Command: AT+EXT** | ||
| 826 | |||
| 827 | [[image:image-20220523150759-3.png]] | ||
| 828 | |||
| 829 | ((( | ||
| 830 | **Downlink Command: 0xA2** | ||
| 831 | ))) | ||
| 832 | |||
| 833 | ((( | ||
| 834 | Total bytes: 2 ~~ 5 bytes | ||
| 835 | ))) | ||
| 836 | |||
| 837 | ((( | ||
| 838 | **Example:** | ||
| 839 | ))) | ||
| 840 | |||
| 841 | * ((( | ||
| 842 | 0xA201: Set external sensor type to E1 | ||
| 843 | ))) | ||
| 844 | * ((( | ||
| 845 | 0xA209: Same as AT+EXT=9 | ||
| 846 | ))) | ||
| 847 | * ((( | ||
| 848 | 0xA20702003c,Same as AT+SETCNT=60 | ||
| 849 | ))) | ||
| 850 | |||
| 851 | == 4.3 Enable/Disable uplink Temperature probe ID == | ||
| 852 | |||
| 853 | Feature: If PID is enabled, device will send the temperature probe ID on: | ||
| 854 | |||
| 855 | * First Packet after OTAA Join | ||
| 856 | * Every 24 hours since the first packet. | ||
| 857 | |||
| 858 | PID is default set to disable (0) | ||
| 859 | |||
| 860 | **AT Command:** | ||
| 861 | |||
| 862 | [[image:image-20220523150928-4.png]] | ||
| 863 | |||
| 864 | **Downlink Command:** | ||
| 865 | |||
| 866 | * 0xA800 **~-~->** AT+PID=0 | ||
| 867 | * 0xA801 **~-~->** AT+PID=1 | ||
| 868 | |||
| 869 | == 4.4 Set Password == | ||
| 870 | |||
| 871 | Feature: Set device password, max 9 digits | ||
| 872 | |||
| 873 | **AT Command: AT+PWORD** | ||
| 874 | |||
| 875 | [[image:image-20220523151052-5.png]] | ||
| 876 | |||
| 877 | ((( | ||
| 878 | **Downlink Command:** | ||
| 879 | ))) | ||
| 880 | |||
| 881 | ((( | ||
| 882 | No downlink command for this feature. | ||
| 883 | ))) | ||
| 884 | |||
| 885 | == 4.5 Quit AT Command == | ||
| 886 | |||
| 887 | Feature: Quit AT Command mode, so user needs to input password again before use AT Commands. | ||
| 888 | |||
| 889 | **AT Command: AT+DISAT** | ||
| 890 | |||
| 891 | [[image:image-20220523151132-6.png]] | ||
| 892 | |||
| 893 | **Downlink Command:** | ||
| 894 | |||
| 895 | No downlink command for this feature. | ||
| 896 | |||
| 897 | == 4.6 Set to sleep mode == | ||
| 898 | |||
| 899 | Feature: Set device to sleep mode | ||
| 900 | |||
| 901 | **AT Command: AT+SLEEP** | ||
| 902 | |||
| 903 | [[image:image-20220523151218-7.png]] | ||
| 904 | |||
| 905 | **Downlink Command:** | ||
| 906 | |||
| 907 | * There is no downlink command to set to Sleep mode. | ||
| 908 | |||
| 909 | == 4.7 Set system time == | ||
| 910 | |||
| 911 | Feature: Set system time, unix format. [[See here for format detail.>>path:#TimeStamp]] | ||
| 912 | |||
| 913 | **AT Command:** | ||
| 914 | |||
| 915 | [[image:image-20220523151253-8.png]] | ||
| 916 | |||
| 917 | **Downlink Command:** | ||
| 918 | |||
| 919 | 0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352 | ||
| 920 | |||
| 921 | == 4.8 Set Time Sync Mode == | ||
| 922 | |||
| 923 | ((( | ||
| 924 | Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command. | ||
| 925 | ))) | ||
| 926 | |||
| 927 | ((( | ||
| 928 | 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. | ||
| 929 | ))) | ||
| 930 | |||
| 931 | ((( | ||
| 932 | **AT Command:** | ||
| 933 | ))) | ||
| 934 | |||
| 935 | [[image:image-20220523151336-9.png]] | ||
| 936 | |||
| 937 | **Downlink Command:** | ||
| 938 | |||
| 939 | 0x28 01 ~/~/ Same As AT+SYNCMOD=1 | ||
| 940 | |||
| 941 | 0x28 00 ~/~/ Same As AT+SYNCMOD=0 | ||
| 942 | |||
| 943 | == 4.9 Set Time Sync Interval == | ||
| 944 | |||
| 945 | Feature: Define System time sync interval. SYNCTDC default value: 10 days. | ||
| 946 | |||
| 947 | **AT Command:** | ||
| 948 | |||
| 949 | [[image:image-20220523151411-10.png]] | ||
| 950 | |||
| 951 | **Downlink Command:** | ||
| 952 | |||
| 953 | 0x29 0A ~/~/ Same as AT+SYNCTDC=0x0A | ||
| 954 | |||
| 955 | == 4.10 Print data entries base on page. == | ||
| 956 | |||
| 957 | Feature: Print the sector data from start page to stop page (max is 416 pages). | ||
| 958 | |||
| 959 | **AT Command: AT+PDTA** | ||
| 960 | |||
| 961 | [[image:image-20220523151450-11.png]] | ||
| 962 | |||
| 963 | **Downlink Command:** | ||
| 964 | |||
| 965 | No downlink commands for feature | ||
| 966 | |||
| 967 | == 4.11 Print last few data entries. == | ||
| 968 | |||
| 969 | Feature: Print the last few data entries | ||
| 970 | |||
| 971 | **AT Command: AT+PLDTA** | ||
| 972 | |||
| 973 | [[image:image-20220523151524-12.png]] | ||
| 974 | |||
| 975 | **Downlink Command:** | ||
| 976 | |||
| 977 | No downlink commands for feature | ||
| 978 | |||
| 979 | == 4.12 Clear Flash Record == | ||
| 980 | |||
| 981 | Feature: Clear flash storage for data log feature. | ||
| 982 | |||
| 983 | **AT Command: AT+CLRDTA** | ||
| 984 | |||
| 985 | [[image:image-20220523151556-13.png]] | ||
| 986 | |||
| 987 | **Downlink Command: 0xA3** | ||
| 988 | |||
| 989 | * Example: 0xA301 ~/~/Same as AT+CLRDTA | ||
| 990 | |||
| 991 | == 4.13 Auto Send None-ACK messages == | ||
| 992 | |||
| 993 | Feature: LHT65N will wait for ACK for each uplink, If LHT65N doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LHT65N keeps sending messages in normal periodically. Once LHT65N gets ACK from a server, it will consider the network is ok and start to send the not-arrive message. | ||
| 994 | |||
| 995 | |||
| 996 | **AT Command: AT+PNACKMD** | ||
| 997 | |||
| 998 | The default factory setting is 0 | ||
| 999 | |||
| 1000 | (% border="1" style="background-color:#ffffcc; color:green; width:450px" %) | ||
| 1001 | |=(% style="width: 171px;" %)**Command Example**|=(% style="width: 219px;" %)**Function**|=(% style="width: 119px;" %)**Response** | ||
| 1002 | |(% style="width:171px" %)AT+PNACKMD=1|(% style="width:219px" %)Poll None-ACK message|(% style="width:119px" %)OK | ||
| 1003 | |||
| 1004 | **Downlink Command: 0x34** | ||
| 1005 | |||
| 1006 | * Example: 0x3401 ~/~/Same as AT+PNACKMD=1 | ||
| 1007 | |||
| 1008 | = 5. Battery & How to replace = | ||
| 1009 | |||
| 1010 | == 5.1 Battery Type == | ||
| 1011 | |||
| 1012 | LHT65N 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. | ||
| 1013 | |||
| 1014 | ((( | ||
| 1015 | The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance. | ||
| 1016 | [[image:image-20220515075034-1.png||height="208" width="644"]] | ||
| 1017 | ))) | ||
| 1018 | |||
| 1019 | ((( | ||
| 1020 | The minimum Working Voltage for the LHT65N is ~~ 2.5v. When battery is lower than 2.6v, it is time to change the battery. | ||
| 1021 | |||
| 1022 | ))) | ||
| 1023 | |||
| 1024 | == 5.2 Replace Battery == | ||
| 1025 | |||
| 1026 | LHT65N has two screws on the back, Unscrew them, and changing the battery inside is ok. The battery is a general CR17450 battery. Any brand should be ok. | ||
| 1027 | |||
| 1028 | [[image:image-20220515075440-2.png||height="338" width="272"]][[image:image-20220515075625-3.png||height="193" width="257"]] | ||
| 1029 | |||
| 1030 | == 5.3 Battery Life Analyze == | ||
| 1031 | |||
| 1032 | ((( | ||
| 1033 | 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: | ||
| 1034 | https:~/~/www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf | ||
| 1035 | ))) | ||
| 1036 | |||
| 1037 | = 6. Order Info = | ||
| 1038 | |||
| 1039 | ((( | ||
| 1040 | Part Number: (% style="color:#4f81bd" %)** LHT65N-XX-YY** | ||
| 1041 | ))) | ||
| 1042 | |||
| 1043 | ((( | ||
| 1044 | (% style="color:#4f81bd" %)**XX **(%%): The default frequency band | ||
| 1045 | ))) | ||
| 1046 | |||
| 1047 | * ((( | ||
| 1048 | (% style="color:#4f81bd" %)** AS923**(%%): LoRaWAN AS923 band | ||
| 1049 | ))) | ||
| 1050 | * ((( | ||
| 1051 | (% style="color:#4f81bd" %)** AU915**(%%): LoRaWAN AU915 band | ||
| 1052 | ))) | ||
| 1053 | * ((( | ||
| 1054 | (% style="color:#4f81bd" %)** EU433**(%%): LoRaWAN EU433 band | ||
| 1055 | ))) | ||
| 1056 | * ((( | ||
| 1057 | (% style="color:#4f81bd" %)** EU868**(%%): LoRaWAN EU868 band | ||
| 1058 | ))) | ||
| 1059 | * ((( | ||
| 1060 | (% style="color:#4f81bd" %)** KR920**(%%): LoRaWAN KR920 band | ||
| 1061 | ))) | ||
| 1062 | * ((( | ||
| 1063 | (% style="color:#4f81bd" %)** US915**(%%): LoRaWAN US915 band | ||
| 1064 | ))) | ||
| 1065 | * ((( | ||
| 1066 | (% style="color:#4f81bd" %)** IN865**(%%): LoRaWAN IN865 band | ||
| 1067 | ))) | ||
| 1068 | * ((( | ||
| 1069 | (% style="color:#4f81bd" %)** CN470**(%%): LoRaWAN CN470 band | ||
| 1070 | ))) | ||
| 1071 | |||
| 1072 | ((( | ||
| 1073 | (% style="color:#4f81bd" %)**YY**(%%): Sensor Accessories | ||
| 1074 | ))) | ||
| 1075 | |||
| 1076 | * ((( | ||
| 1077 | (% style="color:#4f81bd" %)**E3**(%%): External Temperature Probe | ||
| 1078 | ))) | ||
| 1079 | |||
| 1080 | = 7. Packing Info = | ||
| 1081 | |||
| 1082 | ((( | ||
| 1083 | **Package Includes**: | ||
| 1084 | ))) | ||
| 1085 | |||
| 1086 | * ((( | ||
| 1087 | LHT65N Temperature & Humidity Sensor x 1 | ||
| 1088 | ))) | ||
| 1089 | * ((( | ||
| 1090 | Program cable x 1 | ||
| 1091 | ))) | ||
| 1092 | * ((( | ||
| 1093 | Optional external sensor | ||
| 1094 | ))) | ||
| 1095 | |||
| 1096 | ((( | ||
| 1097 | **Dimension and weight**: | ||
| 1098 | ))) | ||
| 1099 | |||
| 1100 | * ((( | ||
| 1101 | Device Size: 13.5 x 7 x 3 cm | ||
| 1102 | ))) | ||
| 1103 | * ((( | ||
| 1104 | Device Weight: 105g | ||
| 1105 | ))) | ||
| 1106 | * ((( | ||
| 1107 | Package Size / pcs : 14.5 x 8 x 5 cm | ||
| 1108 | ))) | ||
| 1109 | * ((( | ||
| 1110 | Weight / pcs : 170g | ||
| 1111 | ))) | ||
| 1112 | |||
| 1113 | = 8. FCC Warning = | ||
| 1114 | |||
| 1115 | ((( | ||
| 1116 | This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: | ||
| 1117 | ))) | ||
| 1118 | |||
| 1119 | ((( | ||
| 1120 | (1) This device may not cause harmful interference； | ||
| 1121 | ))) | ||
| 1122 | |||
| 1123 | ((( | ||
| 1124 | (2) this device must accept any interference received, including interference that may cause undesired operation. | ||
| 1125 | ))) |