Wiki source code of LHT65N LoRaWAN Temperature & Humidity Sensor Manual
Version 241.1 by Ellie Zhang on 2023/05/08 11:29
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% style="text-align:center" %) | ||
| 2 | [[image:image-20220613162008-1.png||_mstalt="428142" height="510" width="334"]] | ||
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | **Table of Contents：** | ||
| 9 | |||
| 10 | {{toc/}} | ||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | = 1. Introduction = | ||
| 17 | |||
| 18 | == 1.1 What is LHT65N Temperature & Humidity Sensor == | ||
| 19 | |||
| 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 | |||
| 46 | |||
| 47 | == 1.2 Features == | ||
| 48 | |||
| 49 | |||
| 50 | * LoRaWAN v1.0.3 Class A protocol | ||
| 51 | * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915 | ||
| 52 | * AT Commands to change parameters | ||
| 53 | * Remote configure parameters via LoRaWAN Downlink | ||
| 54 | * Firmware upgradeable via program port | ||
| 55 | * Built-in 2400mAh battery for up to 10 years of use. | ||
| 56 | * Built-in Temperature & Humidity sensor | ||
| 57 | * Optional External Sensors | ||
| 58 | * Tri-color LED to indicate working status | ||
| 59 | * Datalog feature (Max 3328 records) | ||
| 60 | |||
| 61 | |||
| 62 | == 1.3 Specification == | ||
| 63 | |||
| 64 | |||
| 65 | (% style="color:#037691" %)**Built-in Temperature Sensor:** | ||
| 66 | |||
| 67 | * Resolution: 0.01 °C | ||
| 68 | * Accuracy Tolerance : Typ ±0.3 °C | ||
| 69 | * Long Term Drift: < 0.02 °C/yr | ||
| 70 | * Operating Range: -40 ~~ 85 °C | ||
| 71 | |||
| 72 | (% style="color:#037691" %)**Built-in Humidity Sensor:** | ||
| 73 | |||
| 74 | * Resolution: 0.04 %RH | ||
| 75 | * Accuracy Tolerance : Typ ±3 %RH | ||
| 76 | * Long Term Drift: < 0.02 °C/yr | ||
| 77 | * Operating Range: 0 ~~ 96 %RH | ||
| 78 | |||
| 79 | (% style="color:#037691" %)**External Temperature Sensor:** | ||
| 80 | |||
| 81 | * Resolution: 0.0625 °C | ||
| 82 | * ±0.5°C accuracy from -10°C to +85°C | ||
| 83 | * ±2°C accuracy from -55°C to +125°C | ||
| 84 | * Operating Range: -55 °C ~~ 125 °C | ||
| 85 | |||
| 86 | |||
| 87 | = 2. Connect LHT65N to IoT Server = | ||
| 88 | |||
| 89 | == 2.1 How does LHT65N work? == | ||
| 90 | |||
| 91 | |||
| 92 | ((( | ||
| 93 | 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. | ||
| 94 | ))) | ||
| 95 | |||
| 96 | ((( | ||
| 97 | 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. | ||
| 98 | ))) | ||
| 99 | |||
| 100 | |||
| 101 | == 2.2 How to Activate LHT65N? == | ||
| 102 | |||
| 103 | |||
| 104 | ((( | ||
| 105 | The LHT65N has two working modes: | ||
| 106 | ))) | ||
| 107 | |||
| 108 | * ((( | ||
| 109 | (% style="color:blue" %)**Deep Sleep Mode**(%%): LHT65N doesn't have any LoRaWAN activation. This mode is used for storage and shipping to save battery life. | ||
| 110 | ))) | ||
| 111 | * ((( | ||
| 112 | (% style="color:blue" %)**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, LHT65N will be in STOP mode (IDLE mode), in STOP mode, LHT65N has the same power consumption as Deep Sleep mode. | ||
| 113 | ))) | ||
| 114 | |||
| 115 | ((( | ||
| 116 | The LHT65N is set in deep sleep mode by default; The ACT button on the front is to switch to different modes: | ||
| 117 | ))) | ||
| 118 | |||
| 119 | |||
| 120 | [[image:image-20220515123819-1.png||_mstalt="430742" height="379" width="317"]] | ||
| 121 | |||
| 122 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 123 | |=(% style="width: 167px;background-color:#D9E2F3;color:#0070C0" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 225px;background-color:#D9E2F3;color:#0070C0" %)**Action** | ||
| 124 | |(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT between 1s < time < 3s|(% style="background-color:#f2f2f2; width:117px" %)Test uplink status|(% style="background-color:#f2f2f2; width:225px" %)((( | ||
| 125 | If LHT65N is already Joined to rhe LoRaWAN network, LHT65N will send an uplink packet, if LHT65N has external sensor connected,(% style="color:blue" %)**Blue led** (%%)will blink once. If LHT65N has not external sensor, (% style="color:red" %)**Red led**(%%) will blink once. | ||
| 126 | ))) | ||
| 127 | |(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT for more than 3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)((( | ||
| 128 | (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will fast blink 5 times, LHT65N will enter working mode and start to JOIN LoRaWAN network. | ||
| 129 | (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after join in network. | ||
| 130 | ))) | ||
| 131 | |(% style="background-color:#f2f2f2; width:167px" %)Fast press ACT 5 times.|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device|(% style="background-color:#f2f2f2; width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means LHT65N is in Deep Sleep Mode. | ||
| 132 | |||
| 133 | |||
| 134 | == 2.3 Example to join LoRaWAN network == | ||
| 135 | |||
| 136 | |||
| 137 | (% class="wikigeneratedid" %) | ||
| 138 | 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. | ||
| 139 | |||
| 140 | |||
| 141 | (% class="wikigeneratedid" %) | ||
| 142 | [[image:image-20220522232442-1.png||_mstalt="427830" height="387" width="648"]] | ||
| 143 | |||
| 144 | |||
| 145 | ((( | ||
| 146 | Assume the LPS8N is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network||_mstvisible="2"]], So it provides network coverage for LHT65N. Next we need to add the LHT65N device in TTN V3: | ||
| 147 | ))) | ||
| 148 | |||
| 149 | |||
| 150 | === 2.3.1 Step 1: Create Device n TTN === | ||
| 151 | |||
| 152 | |||
| 153 | ((( | ||
| 154 | Create a device in TTN V3 with the OTAA keys from LHT65N. | ||
| 155 | ))) | ||
| 156 | |||
| 157 | ((( | ||
| 158 | Each LHT65N is shipped with a sticker with its device EUI, APP Key and APP EUI as below: | ||
| 159 | ))) | ||
| 160 | |||
| 161 | [[image:image-20230426083319-1.png]] | ||
| 162 | |||
| 163 | User can enter these keys in the LoRaWAN Server portal. Below is TTN V3 screenshot: | ||
| 164 | |||
| 165 | Add APP EUI in the application. | ||
| 166 | |||
| 167 | |||
| 168 | [[image:image-20220522232916-3.png||_mstalt="430495"]] | ||
| 169 | |||
| 170 | |||
| 171 | [[image:image-20220522232932-4.png||_mstalt="430157"]] | ||
| 172 | |||
| 173 | |||
| 174 | [[image:image-20220522232954-5.png||_mstalt="431847"]] | ||
| 175 | |||
| 176 | |||
| 177 | |||
| 178 | (% style="color:red" %)**Note: LHT65N use same payload as LHT65.** | ||
| 179 | |||
| 180 | |||
| 181 | [[image:image-20220522233026-6.png||_mstalt="429403"]] | ||
| 182 | |||
| 183 | |||
| 184 | Input APP EUI, APP KEY and DEV EUI: | ||
| 185 | |||
| 186 | |||
| 187 | [[image:image-20220522233118-7.png||_mstalt="430430"]] | ||
| 188 | |||
| 189 | |||
| 190 | === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. === | ||
| 191 | |||
| 192 | |||
| 193 | ((( | ||
| 194 | 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. | ||
| 195 | ))) | ||
| 196 | |||
| 197 | [[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]] | ||
| 198 | |||
| 199 | |||
| 200 | == 2.4 Uplink Payload ( Fport~=2) == | ||
| 201 | |||
| 202 | |||
| 203 | ((( | ||
| 204 | The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default. | ||
| 205 | ))) | ||
| 206 | |||
| 207 | ((( | ||
| 208 | After each uplink, the (% style="color:blue" %)**BLUE LED**(%%) will blink once. | ||
| 209 | ))) | ||
| 210 | |||
| 211 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:390px" %) | ||
| 212 | |=(% style="width: 60px;background-color:#D9E2F3" %)((( | ||
| 213 | **Size(bytes)** | ||
| 214 | )))|=(% style="width: 30px;background-color:#D9E2F3" %)((( | ||
| 215 | **2** | ||
| 216 | )))|=(% style="width: 100px;background-color:#D9E2F3" %)((( | ||
| 217 | **2** | ||
| 218 | )))|=(% style="width: 100px;background-color:#D9E2F3" %)((( | ||
| 219 | **2** | ||
| 220 | )))|=(% style="width: 50px;background-color:#D9E2F3" %)((( | ||
| 221 | **1** | ||
| 222 | )))|=(% style="width: 50px;background-color:#D9E2F3" %)((( | ||
| 223 | **4** | ||
| 224 | ))) | ||
| 225 | |(% style="width:97px" %)((( | ||
| 226 | **Value** | ||
| 227 | )))|(% style="width:39px" %)((( | ||
| 228 | [[BAT>>||anchor="H2.4.2BAT-BatteryInfo"]] | ||
| 229 | )))|(% style="width:100px" %)((( | ||
| 230 | ((( | ||
| 231 | [[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]] | ||
| 232 | ))) | ||
| 233 | )))|(% style="width:77px" %)((( | ||
| 234 | ((( | ||
| 235 | [[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 236 | ))) | ||
| 237 | )))|(% style="width:47px" %)((( | ||
| 238 | [[Ext>>||anchor="H2.4.5Ext23"]] # | ||
| 239 | )))|(% style="width:51px" %)((( | ||
| 240 | [[Ext value>>||anchor="H2.4.6Extvalue"]] | ||
| 241 | ))) | ||
| 242 | |||
| 243 | * The First 6 bytes: has fix meanings for every LHT65N. | ||
| 244 | |||
| 245 | * The 7th byte (EXT #): defines the external sensor model. | ||
| 246 | |||
| 247 | * 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.) | ||
| 248 | |||
| 249 | |||
| 250 | === 2.4.1 Decoder in TTN V3 === | ||
| 251 | |||
| 252 | |||
| 253 | 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. | ||
| 254 | |||
| 255 | Below is the position to put the decoder and LHT65N decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]] | ||
| 256 | |||
| 257 | |||
| 258 | [[image:image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]] | ||
| 259 | |||
| 260 | |||
| 261 | === 2.4.2 BAT-Battery Info === | ||
| 262 | |||
| 263 | |||
| 264 | These two bytes of BAT include the battery state and the actually voltage. | ||
| 265 | |||
| 266 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:477px" %) | ||
| 267 | |=(% style="width: 69px; background-color:#D9E2F3;color:#0070C0" %)((( | ||
| 268 | **Bit(bit)** | ||
| 269 | )))|=(% style="width: 253px;background-color:#D9E2F3;color:#0070C0" %)[15:14]|=(% style="width: 155px;background-color:#D9E2F3;color:#0070C0" %)[13:0] | ||
| 270 | |(% style="width:66px" %)((( | ||
| 271 | **Value** | ||
| 272 | )))|(% style="width:250px" %)((( | ||
| 273 | BAT Status | ||
| 274 | 00(b): Ultra Low ( BAT <= 2.50v) | ||
| 275 | 01(b): Low (2.50v <=BAT <= 2.55v) | ||
| 276 | 10(b): OK (2.55v <= BAT <=2.65v) | ||
| 277 | 11(b): Good (BAT >= 2.65v) | ||
| 278 | )))|(% style="width:152px" %)Actually BAT voltage | ||
| 279 | |||
| 280 | **(b)stands for binary** | ||
| 281 | |||
| 282 | |||
| 283 | [[image:image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]] | ||
| 284 | |||
| 285 | |||
| 286 | Check the battery voltage for LHT65N. | ||
| 287 | |||
| 288 | * BAT status=(0Xcba4>>14)&0xFF=11 (BIN) ，very good | ||
| 289 | |||
| 290 | * Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV | ||
| 291 | |||
| 292 | |||
| 293 | === 2.4.3 Built-in Temperature === | ||
| 294 | |||
| 295 | |||
| 296 | [[image:image-20220522235639-2.png||_mstalt="431756" height="138" width="722"]] | ||
| 297 | |||
| 298 | * Temperature: 0x0ABB/100=27.47℃ | ||
| 299 | |||
| 300 | [[image:image-20220522235639-3.png||_mstalt="432120"]] | ||
| 301 | |||
| 302 | * Temperature: (0xF5C6-65536)/100=-26.18℃ | ||
| 303 | |||
| 304 | |||
| 305 | === 2.4.4 Built-in Humidity === | ||
| 306 | |||
| 307 | |||
| 308 | [[image:image-20220522235639-4.png||_mstalt="432484" height="138" width="722"]] | ||
| 309 | |||
| 310 | * Humidity: 0x025C/10=60.4% | ||
| 311 | |||
| 312 | |||
| 313 | === 2.4.5 Ext # === | ||
| 314 | |||
| 315 | |||
| 316 | Bytes for External Sensor: | ||
| 317 | |||
| 318 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:425px" %) | ||
| 319 | |=(% style="width: 102px; background-color:#D9E2F3;color:#0070C0" %)**EXT # Value**|=(% style="width: 323px;background-color:#D9E2F3;color:#0070C0" %)**External Sensor Type** | ||
| 320 | |(% style="width:102px" %)0x01|(% style="width:319px" %)Sensor E3, Temperature Sensor | ||
| 321 | |(% style="width:102px" %)0x09|(% style="width:319px" %)Sensor E3, Temperature Sensor, Datalog Mod | ||
| 322 | |||
| 323 | |||
| 324 | === 2.4.6 Ext value === | ||
| 325 | |||
| 326 | ==== 2.4.6.1 Ext~=1, E3 Temperature Sensor ==== | ||
| 327 | |||
| 328 | |||
| 329 | [[image:image-20220522235639-5.png||_mstalt="432848"]] | ||
| 330 | |||
| 331 | |||
| 332 | * DS18B20 temp=0x0ADD/100=27.81℃ | ||
| 333 | |||
| 334 | The last 2 bytes of data are meaningless | ||
| 335 | |||
| 336 | |||
| 337 | |||
| 338 | [[image:image-20220522235639-6.png||_mstalt="433212"]] | ||
| 339 | |||
| 340 | |||
| 341 | * External temperature= (0xF54F-65536)/100=-27.37℃ | ||
| 342 | |||
| 343 | F54F : (F54F & 8000 == 1) , temp = (F54F - 65536)/100 = 27.37℃ | ||
| 344 | |||
| 345 | （0105 & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative） | ||
| 346 | |||
| 347 | The last 2 bytes of data are meaningless | ||
| 348 | |||
| 349 | If the external sensor is 0x01, and there is no external temperature connected. The temperature will be set to 7FFF which is 327.67℃ | ||
| 350 | |||
| 351 | |||
| 352 | |||
| 353 | ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ==== | ||
| 354 | |||
| 355 | |||
| 356 | ((( | ||
| 357 | 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: | ||
| 358 | ))) | ||
| 359 | |||
| 360 | |||
| 361 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:480px" %) | ||
| 362 | |=(% style="width: 50px;background-color:#D9E2F3" %)((( | ||
| 363 | **Size(bytes)** | ||
| 364 | )))|=(% style="width: 70px;background-color:#D9E2F3" %)((( | ||
| 365 | **2** | ||
| 366 | )))|=(% style="width: 120px;background-color:#D9E2F3" %)((( | ||
| 367 | **2** | ||
| 368 | )))|=(% style="width: 120px;background-color:#D9E2F3" %)((( | ||
| 369 | **2** | ||
| 370 | )))|=(% style="width: 50px;background-color:#D9E2F3" %)((( | ||
| 371 | **1** | ||
| 372 | )))|=(% style="width: 70px;background-color:#D9E2F3" %)((( | ||
| 373 | **4** | ||
| 374 | ))) | ||
| 375 | |(% style="width:110px" %)((( | ||
| 376 | **Value** | ||
| 377 | )))|(% style="width:71px" %)((( | ||
| 378 | External temperature | ||
| 379 | )))|(% style="width:99px" %)((( | ||
| 380 | [[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]] | ||
| 381 | )))|(% style="width:132px" %)((( | ||
| 382 | BAT Status & [[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 383 | )))|(% style="width:54px" %)((( | ||
| 384 | Status & Ext | ||
| 385 | )))|(% style="width:64px" %)((( | ||
| 386 | [[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]] | ||
| 387 | ))) | ||
| 388 | |||
| 389 | * **Battery status & Built-in Humidity** | ||
| 390 | |||
| 391 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:461px" %) | ||
| 392 | |=(% style="width: 69px;background-color:#D9E2F3;color:#0070C0" %)Bit(bit)|=(% style="width: 258px;background-color:#D9E2F3;color:#0070C0" %)[15:14]|=(% style="width: 134px;background-color:#D9E2F3;color:#0070C0" %)[11:0] | ||
| 393 | |(% style="width:67px" %)**Value**|(% style="width:256px" %)((( | ||
| 394 | BAT Status | ||
| 395 | 00(b): Ultra Low ( BAT <= 2.50v) | ||
| 396 | 01(b): Low (2.50v <=BAT <= 2.55v) | ||
| 397 | 10(b): OK (2.55v <= BAT <=2.65v) | ||
| 398 | 11(b): Good (BAT >= 2.65v) | ||
| 399 | )))|(% style="width:132px" %)((( | ||
| 400 | [[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]] | ||
| 401 | ))) | ||
| 402 | |||
| 403 | * **Status & Ext Byte** | ||
| 404 | |||
| 405 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) | ||
| 406 | |=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Bits**|(% style="background-color:#d9e2f3; color:#0070c0; width:90px" %)**7**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**6**|(% style="background-color:#d9e2f3; color:#0070c0; width:90px" %)**5**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**[3:0]** | ||
| 407 | |=(% 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) | ||
| 408 | |||
| 409 | * (% style="color:blue" %)**Poll Message Flag**:(%%) 1: This message is a poll message reply, 0: means this is a normal uplink. | ||
| 410 | * (% style="color:blue" %)**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. | ||
| 411 | * (% style="color:blue" %)**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) | ||
| 412 | |||
| 413 | |||
| 414 | ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ==== | ||
| 415 | |||
| 416 | |||
| 417 | In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can | ||
| 418 | |||
| 419 | be used to power the external ADC sensor; user can control the power on time for this | ||
| 420 | |||
| 421 | (% style="color:blue" %)**sensor by setting:** | ||
| 422 | |||
| 423 | **AT+EXT=6,timeout** (% style="color:red" %)**Time to power this sensor, from 0 ~~ 65535ms** | ||
| 424 | |||
| 425 | **For example:** | ||
| 426 | |||
| 427 | AT+EXT=6,1000 will power this sensor for 1000ms before sampling the ADC value. | ||
| 428 | |||
| 429 | |||
| 430 | Or use **downlink command A2** to set the same. | ||
| 431 | |||
| 432 | The measuring range of the node is only about 0.1V to 1.1V The voltage resolution is about 0.24mv. | ||
| 433 | |||
| 434 | When the measured output voltage of the sensor is not within the range of 0.1V and 1.1V, the output voltage terminal of the sensor shall be divided The example in the following figure is to reduce the output voltage of the sensor by three times If it is necessary to reduce more times, calculate according to the formula in the figure and connect the corresponding resistance in series. | ||
| 435 | |||
| 436 | [[image:image-20220628150112-1.png||_mstalt="427414" height="241" width="285"]] | ||
| 437 | |||
| 438 | |||
| 439 | When ADC_IN1 pin is connected to GND or suspended, ADC value is 0 | ||
| 440 | |||
| 441 | [[image:image-20220628150714-4.png||_mstalt="431054"]] | ||
| 442 | |||
| 443 | |||
| 444 | When the voltage collected by ADC_IN1 is less than the minimum range, the minimum range will be used as the output; Similarly, when the collected voltage is greater than the maximum range, the maximum range will be used as the output. | ||
| 445 | |||
| 446 | |||
| 447 | 1) The minimum range is about 0.1V. Each chip has internal calibration, so this value is close to 0.1V | ||
| 448 | |||
| 449 | [[image:image-20220628151005-5.png||_mstalt="429546"]] | ||
| 450 | |||
| 451 | |||
| 452 | 2) The maximum range is about 1.1V. Each chip has internal calibration, so this value is close to 1.1v | ||
| 453 | |||
| 454 | [[image:image-20220628151056-6.png||_mstalt="431873"]] | ||
| 455 | |||
| 456 | |||
| 457 | 3) Within range | ||
| 458 | |||
| 459 | [[image:image-20220628151143-7.png||_mstalt="431210"]] | ||
| 460 | |||
| 461 | |||
| 462 | |||
| 463 | ==== 2.4.6.4 Ext~=2 TMP117 Sensor （Since Firmware v1.3） ==== | ||
| 464 | |||
| 465 | |||
| 466 | [[image:image-20220927095645-1.png||_mstalt="433771" height="534" width="460"]] | ||
| 467 | |||
| 468 | |||
| 469 | (% style="color:blue" %)**Ext=2,Temperature Sensor(TMP117)：** | ||
| 470 | |||
| 471 | [[image:image-20220906102307-7.png||_mstalt="430443"]] | ||
| 472 | |||
| 473 | |||
| 474 | (% style="color:blue" %)**Interrupt Mode and Counting Mode:** | ||
| 475 | |||
| 476 | The external cable NE2 can be use for MOD4 and MOD8 | ||
| 477 | |||
| 478 | |||
| 479 | |||
| 480 | ==== 2.4.6.5 Ext~=4 Interrupt Mode （Since Firmware v1.3） ==== | ||
| 481 | |||
| 482 | |||
| 483 | (% style="color:red" %)**Note: In this mode, 3.3v output will be always ON. LHT65N will send an uplink when there is a trigger.** | ||
| 484 | |||
| 485 | |||
| 486 | (% style="color:blue" %)**Interrupt Mode can be used to connect to external interrupt sensors such as:** | ||
| 487 | |||
| 488 | (% style="color:#037691" %)**Case 1: Door Sensor.** (%%)3.3v Out for such sensor is just to detect Open/Close. | ||
| 489 | |||
| 490 | In Open State, the power consumption is the same as if there is no probe | ||
| 491 | |||
| 492 | In Close state, the power consumption will be 3uA higher than normal. | ||
| 493 | |||
| 494 | [[image:image-20220906100852-1.png||_mstalt="429156" height="205" width="377"]] | ||
| 495 | |||
| 496 | |||
| 497 | Ext=4,Interrupt Sensor： | ||
| 498 | |||
| 499 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:504px" %) | ||
| 500 | |(% style="width:101px" %)((( | ||
| 501 | **AT+EXT=4,1** | ||
| 502 | )))|(% style="width:395px" %)((( | ||
| 503 | **Sent uplink packet in both rising and falling interrupt** | ||
| 504 | ))) | ||
| 505 | |(% style="width:101px" %)((( | ||
| 506 | **AT+EXT=4,2** | ||
| 507 | )))|(% style="width:395px" %)((( | ||
| 508 | **Sent uplink packet only in falling interrupt** | ||
| 509 | ))) | ||
| 510 | |(% style="width:101px" %)((( | ||
| 511 | **AT+EXT=4,3** | ||
| 512 | )))|(% style="width:395px" %)((( | ||
| 513 | **Sent uplink packet only in rising interrupt** | ||
| 514 | ))) | ||
| 515 | |||
| 516 | Trigger by falling edge: | ||
| 517 | |||
| 518 | [[image:image-20220906101145-2.png||_mstalt="428324"]] | ||
| 519 | |||
| 520 | |||
| 521 | Trigger by raising edge： | ||
| 522 | |||
| 523 | [[image:image-20220906101145-3.png||_mstalt="428688"]] | ||
| 524 | |||
| 525 | |||
| 526 | |||
| 527 | ==== 2.4.6.6 Ext~=8 Counting Mode（Since Firmware v1.3） ==== | ||
| 528 | |||
| 529 | |||
| 530 | (% style="color:red" %)**Note: In this mode, 3.3v output will be always ON. LHT65N will count for every interrupt and uplink periodically.** | ||
| 531 | |||
| 532 | |||
| 533 | (% style="color:blue" %)**Case 1**(%%): Low power consumption Flow Sensor, such flow sensor has pulse output and the power consumption in uA level and can be powered by LHT65N. | ||
| 534 | |||
| 535 | [[image:image-20220906101320-4.png||_mstalt="427336" height="366" width="698"]] | ||
| 536 | |||
| 537 | |||
| 538 | (% style="color:blue" %)**Case 2**(%%): Normal Flow Sensor: Such flow sensor has higher power consumption and is not suitable to be powered by LHT65N. It is powered by external power and output <3.3v pulse | ||
| 539 | |||
| 540 | [[image:image-20220906101320-5.png||_mstalt="427700" height="353" width="696"]] | ||
| 541 | |||
| 542 | |||
| 543 | Ext=8, Counting Sensor ( 4 bytes)： | ||
| 544 | |||
| 545 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:330px" %) | ||
| 546 | |(% style="width:131px" %)((( | ||
| 547 | **AT+EXT=8,0** | ||
| 548 | )))|(% style="width:195px" %)((( | ||
| 549 | **Count at falling interrupt** | ||
| 550 | ))) | ||
| 551 | |(% style="width:131px" %)((( | ||
| 552 | **AT+EXT=8,1** | ||
| 553 | )))|(% style="width:195px" %)((( | ||
| 554 | **Count at rising interrupt** | ||
| 555 | ))) | ||
| 556 | |(% style="width:131px" %)((( | ||
| 557 | **AT+SETCNT=60** | ||
| 558 | )))|(% style="width:195px" %)((( | ||
| 559 | **Sent current count to 60** | ||
| 560 | ))) | ||
| 561 | |||
| 562 | [[image:image-20220906101320-6.png||_mstalt="428064"]] | ||
| 563 | |||
| 564 | |||
| 565 | (% style="color:blue" %)**A2 downlink Command：** | ||
| 566 | |||
| 567 | A2 02: Same as AT+EXT=2 (AT+EXT= second byte) | ||
| 568 | |||
| 569 | A2 06 01 F4: Same as AT+EXT=6,500 (AT+EXT= second byte, third and fourth bytes) | ||
| 570 | |||
| 571 | A2 04 02: Same as AT+EXT=4,2 (AT+EXT= second byte, third byte) | ||
| 572 | |||
| 573 | A2 08 01 00: Same as AT+EXT=8,0 (AT+EXT= second byte, fourth byte) | ||
| 574 | |||
| 575 | A2 08 02 00 00 00 3C: Same as AT+ SETCNT=60 (AT+ SETCNT = 4th byte and 5th byte and 6th byte and 7th byte) | ||
| 576 | |||
| 577 | |||
| 578 | == 2.5 Show data on Datacake == | ||
| 579 | |||
| 580 | |||
| 581 | ((( | ||
| 582 | 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: | ||
| 583 | ))) | ||
| 584 | |||
| 585 | |||
| 586 | ((( | ||
| 587 | (% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the LoRaWAN network. | ||
| 588 | ))) | ||
| 589 | |||
| 590 | ((( | ||
| 591 | (% 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. | ||
| 592 | ))) | ||
| 593 | |||
| 594 | |||
| 595 | ((( | ||
| 596 | Add Datacake: | ||
| 597 | ))) | ||
| 598 | |||
| 599 | |||
| 600 | [[image:image-20220523000825-7.png||_mstalt="429884" height="262" width="583"]] | ||
| 601 | |||
| 602 | |||
| 603 | |||
| 604 | Select default key as Access Key: | ||
| 605 | |||
| 606 | |||
| 607 | [[image:image-20220523000825-8.png||_mstalt="430248" height="453" width="406"]] | ||
| 608 | |||
| 609 | |||
| 610 | In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT65 device. | ||
| 611 | |||
| 612 | |||
| 613 | [[image:image-20220523000825-9.png||_mstalt="430612" height="366" width="392"]] | ||
| 614 | |||
| 615 | |||
| 616 | [[image:image-20220523000825-10.png||_mstalt="450619" height="413" width="728"]] | ||
| 617 | |||
| 618 | |||
| 619 | == 2.6 Datalog Feature == | ||
| 620 | |||
| 621 | |||
| 622 | ((( | ||
| 623 | 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. | ||
| 624 | ))) | ||
| 625 | |||
| 626 | |||
| 627 | === 2.6.1 Ways to get datalog via LoRaWAN === | ||
| 628 | |||
| 629 | |||
| 630 | There are two methods: | ||
| 631 | |||
| 632 | (% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range. | ||
| 633 | |||
| 634 | |||
| 635 | (% style="color:blue" %)**Method 2: **(%%)Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N 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. | ||
| 636 | |||
| 637 | |||
| 638 | (% style="color:red" %)**Note for method 2:** | ||
| 639 | |||
| 640 | * a) LHT65N will do an ACK check for data records sending to make sure every data arrive server. | ||
| 641 | * b) LHT65N will send data in **CONFIRMED Mode** when PNACKMD=1, but LHT65N 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 gets a ACK, LHT65N will consider there is a network connection and resend all NONE-ACK Message. | ||
| 642 | |||
| 643 | Below is the typical case for the auto-update datalog feature (Set PNACKMD=1) | ||
| 644 | |||
| 645 | |||
| 646 | [[image:image-20220703111700-2.png||_mstalt="426244" height="381" width="1119"]] | ||
| 647 | |||
| 648 | |||
| 649 | === 2.6.2 Unix TimeStamp === | ||
| 650 | |||
| 651 | |||
| 652 | LHT65N uses Unix TimeStamp format based on | ||
| 653 | |||
| 654 | |||
| 655 | [[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]] | ||
| 656 | |||
| 657 | |||
| 658 | |||
| 659 | User can get this time from link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] : | ||
| 660 | |||
| 661 | Below is the converter example | ||
| 662 | |||
| 663 | [[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]] | ||
| 664 | |||
| 665 | |||
| 666 | So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25 | ||
| 667 | |||
| 668 | |||
| 669 | === 2.6.3 Set Device Time === | ||
| 670 | |||
| 671 | |||
| 672 | ((( | ||
| 673 | (% style="color:blue" %)**There are two ways to set device's time:** | ||
| 674 | ))) | ||
| 675 | |||
| 676 | ((( | ||
| 677 | **1. Through LoRaWAN MAC Command (Default settings)** | ||
| 678 | ))) | ||
| 679 | |||
| 680 | ((( | ||
| 681 | User need to set SYNCMOD=1 to enable sync time via MAC command. | ||
| 682 | ))) | ||
| 683 | |||
| 684 | ((( | ||
| 685 | 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). | ||
| 686 | ))) | ||
| 687 | |||
| 688 | ((( | ||
| 689 | (% 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.** | ||
| 690 | ))) | ||
| 691 | |||
| 692 | |||
| 693 | ((( | ||
| 694 | **2. Manually Set Time** | ||
| 695 | ))) | ||
| 696 | |||
| 697 | ((( | ||
| 698 | User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server. | ||
| 699 | ))) | ||
| 700 | |||
| 701 | |||
| 702 | === 2.6.4 Poll sensor value === | ||
| 703 | |||
| 704 | |||
| 705 | User can poll sensor value based on timestamps from the server. Below is the downlink command. | ||
| 706 | |||
| 707 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:428px" %) | ||
| 708 | |(% style="width:58px" %)1byte|(% style="width:128px" %)4bytes|(% style="width:123px" %)4bytes|(% style="width:116px" %)1byte | ||
| 709 | |(% style="width:58px" %)31|(% style="width:128px" %)Timestamp start|(% style="width:123px" %)Timestamp end|(% style="width:116px" %)Uplink Interval | ||
| 710 | |||
| 711 | 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. | ||
| 712 | |||
| 713 | For example, downlink command (% _mstmutation="1" %)**31 5FC5F350 5FC6 0160 05**(%%) | ||
| 714 | |||
| 715 | Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data | ||
| 716 | |||
| 717 | Uplink Internal =5s，means LHT65N will send one packet every 5s. range 5~~255s. | ||
| 718 | |||
| 719 | |||
| 720 | === 2.6.5 Datalog Uplink payload === | ||
| 721 | |||
| 722 | |||
| 723 | The Datalog poll reply uplink will use below payload format. | ||
| 724 | |||
| 725 | **Retrieval data payload:** | ||
| 726 | |||
| 727 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:480px" %) | ||
| 728 | |=(% style="width: 60px;background-color:#D9E2F3" %)((( | ||
| 729 | **Size(bytes)** | ||
| 730 | )))|=(% style="width: 90px;background-color:#D9E2F3" %)**2**|=(% style="width: 90px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 100px;background-color:#D9E2F3" %)**1**|=(% style="width: 70px;background-color:#D9E2F3" %)**4** | ||
| 731 | |(% 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"]] | ||
| 732 | |||
| 733 | **Poll message flag & Ext:** | ||
| 734 | |||
| 735 | [[image:image-20221006192726-1.png||_mstalt="430508" height="112" width="754"]] | ||
| 736 | |||
| 737 | (% 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) | ||
| 738 | |||
| 739 | (% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply. | ||
| 740 | |||
| 741 | * Poll Message Flag is set to 1. | ||
| 742 | |||
| 743 | * Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands. | ||
| 744 | |||
| 745 | For example, in US915 band, the max payload for different DR is: | ||
| 746 | |||
| 747 | (% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data | ||
| 748 | |||
| 749 | (% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) | ||
| 750 | |||
| 751 | (% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data | ||
| 752 | |||
| 753 | (% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data. | ||
| 754 | |||
| 755 | If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0 | ||
| 756 | |||
| 757 | |||
| 758 | **Example:** | ||
| 759 | |||
| 760 | If LHT65N has below data inside Flash: | ||
| 761 | |||
| 762 | [[image:image-20230426171833-4.png]] | ||
| 763 | |||
| 764 | |||
| 765 | If user sends below downlink command: (% style="background-color:yellow" %)3160065F9760066DA705 | ||
| 766 | |||
| 767 | Where : Start time: 60065F97 = time 21/1/19 04:27:03 | ||
| 768 | |||
| 769 | Stop time: 60066DA7= time 21/1/19 05:27:03 | ||
| 770 | |||
| 771 | |||
| 772 | **LHT65N will uplink this payload.** | ||
| 773 | |||
| 774 | [[image:image-20220523001219-13.png||_mstalt="451204" height="421" style="text-align:left" width="727"]] | ||
| 775 | |||
| 776 | |||
| 777 | __**7FFF089801464160065F97**__ **__7FFF__ __088E__ __014B__ __41__ __60066009__** 7FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E | ||
| 778 | |||
| 779 | Where the first 11 bytes is for the first entry: | ||
| 780 | |||
| 781 | 7FFF089801464160065F97 | ||
| 782 | |||
| 783 | Ext sensor data=0x7FFF/100=327.67 | ||
| 784 | |||
| 785 | Temp=0x088E/100=22.00 | ||
| 786 | |||
| 787 | Hum=0x014B/10=32.6 | ||
| 788 | |||
| 789 | poll message flag & Ext=0x41,means reply data,Ext=1 | ||
| 790 | |||
| 791 | Unix time is 0x60066009=1611030423s=21/1/19 04:27:03 | ||
| 792 | |||
| 793 | |||
| 794 | == 2.7 Alarm Mode & Feature "Multi sampling, one uplink" == | ||
| 795 | |||
| 796 | |||
| 797 | ((( | ||
| 798 | 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. | ||
| 799 | ))) | ||
| 800 | |||
| 801 | ((( | ||
| 802 | (% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.** | ||
| 803 | |||
| 804 | |||
| 805 | === 2.7.1 ALARM MODE ( Since v1.3.1 firmware) === | ||
| 806 | |||
| 807 | |||
| 808 | **Internal GXHT30 temperature alarm（Acquisition time: fixed at one minute）** | ||
| 809 | |||
| 810 | ((( | ||
| 811 | (% class="box infomessage" %) | ||
| 812 | ((( | ||
| 813 | **AT+WMOD=3**: Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor) | ||
| 814 | |||
| 815 | **AT+CITEMP=1**: The interval between checking the alarm temperature. (In minutes) | ||
| 816 | |||
| 817 | **AT+ARTEMP**: Gets or sets the alarm range of the internal temperature sensor | ||
| 818 | |||
| 819 | (% _mstmutation="1" %)**AT+ARTEMP=？ **(%%): Gets the alarm range of the internal temperature sensor(% style="display:none" %) | ||
| 820 | |||
| 821 | **AT+ARTEMP=45,105**: Set the internal temperature sensor alarm range from 45 to 105. | ||
| 822 | |||
| 823 | **AT+LEDALARM=1** : Enable LED visual Alarm. | ||
| 824 | ))) | ||
| 825 | ))) | ||
| 826 | |||
| 827 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 828 | |||
| 829 | AT+WMOD=1: A501 , AT+WMOD=0 : A600 | ||
| 830 | |||
| 831 | AT+CITEMP=1 : A60001 | ||
| 832 | |||
| 833 | AT+ARTEMP=1,60 : A70001003C | ||
| 834 | |||
| 835 | AT+ARTEMP=-16,60 : A7FFF0003C | ||
| 836 | |||
| 837 | AT+LEDALARM=1 : 3601 | ||
| 838 | |||
| 839 | |||
| 840 | (% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX** | ||
| 841 | |||
| 842 | Total bytes: 8 bytes | ||
| 843 | |||
| 844 | **Example: **AA0100010001003C | ||
| 845 | |||
| 846 | WMOD=01 | ||
| 847 | |||
| 848 | CITEMP=0001 | ||
| 849 | |||
| 850 | TEMPlow=0001 | ||
| 851 | |||
| 852 | TEMPhigh=003C | ||
| 853 | |||
| 854 | |||
| 855 | **DS18B20 and TMP117 Threshold Alarm** | ||
| 856 | |||
| 857 | **~ AT+WMOD=1,60,-10,20** | ||
| 858 | |||
| 859 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 860 | |||
| 861 | **Example: **A5013CFC180014 | ||
| 862 | |||
| 863 | MOD=01 | ||
| 864 | |||
| 865 | CITEMP=3C(S) | ||
| 866 | |||
| 867 | TEMPlow=FC18 | ||
| 868 | |||
| 869 | TEMPhigh=0014 | ||
| 870 | |||
| 871 | |||
| 872 | **Fluctuation alarm for DS18B20 and TMP117（Acquisition time: minimum 1s）** | ||
| 873 | |||
| 874 | **AT+WMOD=2,60,5** | ||
| 875 | |||
| 876 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 877 | |||
| 878 | **Example: **A5023C05 | ||
| 879 | |||
| 880 | MOD=02 | ||
| 881 | |||
| 882 | CITEMP=3C(S) | ||
| 883 | |||
| 884 | temperature fluctuation=05 | ||
| 885 | |||
| 886 | |||
| 887 | **Sampling multiple times and uplink together** | ||
| 888 | |||
| 889 | **AT+WMOD=3,1,60,20,-16,32,1** | ||
| 890 | |||
| 891 | Explain: | ||
| 892 | |||
| 893 | * (% style="color:#037691" %)**parameter1:**(%%)Set Working Mode to **Mode 3** | ||
| 894 | * (% style="color:#037691" %)**parameter2:**(%%) Set the temperature sampling mode to** 1**(1:DS18B20;2:TMP117;3:** **Internal GXHT30). | ||
| 895 | * (% style="color:#037691" %)**parameter3:**(%%)Sampling Interval is **60**s. | ||
| 896 | * (% style="color:#037691" %)**parameter4:**(%%)When there is **20** sampling dats, Device will send these data via one uplink. (max value is 60, means max 60 sampling in one uplink) | ||
| 897 | * (% style="color:#037691" %)**parameter5 & parameter6:**(%%)Temperature alarm range is **-16** to **32**°C, | ||
| 898 | * (% style="color:#037691" %)**parameter7:**(%%) 1 to enable temperature alarm, **0** to disable the temperature alarm. If alarm is enabled, a data will be sent immediately if temperate exceeds the Alarm range. | ||
| 899 | |||
| 900 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 901 | |||
| 902 | **Example: **A50301003C14FFF0002001 | ||
| 903 | |||
| 904 | MOD=03 | ||
| 905 | |||
| 906 | TEMP=DS18B20 | ||
| 907 | |||
| 908 | CITEMP=003C(S) | ||
| 909 | |||
| 910 | Total number of acquisitions=14 | ||
| 911 | |||
| 912 | TEMPlow=FFF0 | ||
| 913 | |||
| 914 | TEMPhigh=0020 | ||
| 915 | |||
| 916 | ARTEMP=01 | ||
| 917 | |||
| 918 | **Uplink payload( Fport=3)** | ||
| 919 | |||
| 920 | **Example: CBEA**01**0992**//0A41//**09C4** | ||
| 921 | |||
| 922 | BatV=CBEA | ||
| 923 | |||
| 924 | TEMP=DS18B20 | ||
| 925 | |||
| 926 | Temp1=0992 ~/~/ 24.50℃ | ||
| 927 | |||
| 928 | Temp2=0A41 ~/~/ 26.25℃ | ||
| 929 | |||
| 930 | Temp3=09C4 ~/~/ 25.00℃ | ||
| 931 | |||
| 932 | (% style="color:red" %)**Note: This uplink will automatically select the appropriate DR according to the data length** | ||
| 933 | |||
| 934 | (% style="color:red" %)** In this mode, the temperature resolution of ds18b20 is 0.25℃ to save power consumption** | ||
| 935 | ))) | ||
| 936 | |||
| 937 | |||
| 938 | === 2.7.2 ALARM MODE ( Before v1.3.1 firmware) === | ||
| 939 | |||
| 940 | |||
| 941 | (% class="box infomessage" %) | ||
| 942 | ((( | ||
| 943 | ((( | ||
| 944 | **AT+WMOD=1**: Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor) | ||
| 945 | ))) | ||
| 946 | |||
| 947 | ((( | ||
| 948 | **AT+CITEMP=1**: The interval between checking the alarm temperature. (In minutes) | ||
| 949 | ))) | ||
| 950 | |||
| 951 | ((( | ||
| 952 | **AT+ARTEMP**: Gets or sets the alarm range of the internal temperature sensor | ||
| 953 | ))) | ||
| 954 | |||
| 955 | ((( | ||
| 956 | (% _mstmutation="1" %)**AT+ARTEMP=？ **(%%): Gets the alarm range of the internal temperature sensor(% style="display:none" %) | ||
| 957 | ))) | ||
| 958 | |||
| 959 | ((( | ||
| 960 | **AT+ARTEMP=45,105**: Set the internal temperature sensor alarm range from 45 to 105. | ||
| 961 | ))) | ||
| 962 | ))) | ||
| 963 | |||
| 964 | (% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX** | ||
| 965 | |||
| 966 | Total bytes: 8 bytes | ||
| 967 | |||
| 968 | **Example:**AA0100010001003C | ||
| 969 | |||
| 970 | WMOD=01 | ||
| 971 | |||
| 972 | CITEMP=0001 | ||
| 973 | |||
| 974 | TEMPlow=0001 | ||
| 975 | |||
| 976 | TEMPhigh=003C | ||
| 977 | |||
| 978 | |||
| 979 | == 2.8 LED Indicator == | ||
| 980 | |||
| 981 | |||
| 982 | The LHT65 has a triple color LED which for easy showing different stage . | ||
| 983 | |||
| 984 | While user press ACT button, the LED will work as per LED status with ACT button. | ||
| 985 | |||
| 986 | In a normal working state: | ||
| 987 | |||
| 988 | * For each uplink, the BLUE LED or RED LED will blink once. | ||
| 989 | BLUE LED when external sensor is connected. | ||
| 990 | * RED LED when external sensor is not connected | ||
| 991 | * For each success downlink, the PURPLE LED will blink once | ||
| 992 | |||
| 993 | == 2.9 installation == | ||
| 994 | |||
| 995 | |||
| 996 | [[image:image-20220516231650-1.png||_mstalt="428597" height="436" width="428"]] | ||
| 997 | |||
| 998 | |||
| 999 | = 3. Sensors and Accessories = | ||
| 1000 | |||
| 1001 | == 3.1 E2 Extension Cable == | ||
| 1002 | |||
| 1003 | |||
| 1004 | [[image:image-20220619092222-1.png||_mstalt="429533" height="182" width="188"]][[image:image-20220619092313-2.png||_mstalt="430222" height="182" width="173"]] | ||
| 1005 | |||
| 1006 | |||
| 1007 | **1m long breakout cable for LHT65N. Features:** | ||
| 1008 | |||
| 1009 | * ((( | ||
| 1010 | Use for AT Command， works for both LHT52/LHT65N | ||
| 1011 | ))) | ||
| 1012 | * ((( | ||
| 1013 | Update firmware for LHT65N, works for both LHT52/LHT65N | ||
| 1014 | ))) | ||
| 1015 | * ((( | ||
| 1016 | Supports ADC mode to monitor external ADC | ||
| 1017 | ))) | ||
| 1018 | * ((( | ||
| 1019 | Supports Interrupt mode | ||
| 1020 | ))) | ||
| 1021 | * ((( | ||
| 1022 | Exposed All pins from the LHT65N Type-C connector. | ||
| 1023 | |||
| 1024 | |||
| 1025 | |||
| 1026 | ))) | ||
| 1027 | |||
| 1028 | [[image:image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]] | ||
| 1029 | |||
| 1030 | |||
| 1031 | == 3.2 E3 Temperature Probe == | ||
| 1032 | |||
| 1033 | |||
| 1034 | [[image:image-20220515080154-4.png||_mstalt="434681" alt="photo-20220515080154-4.png" height="182" width="161"]] [[image:image-20220515080330-5.png||_mstalt="428792" height="201" width="195"]] | ||
| 1035 | |||
| 1036 | |||
| 1037 | Temperature sensor with 2 meters cable long | ||
| 1038 | |||
| 1039 | * Resolution: 0.0625 °C | ||
| 1040 | * ±0.5°C accuracy from -10°C to +85°C | ||
| 1041 | * ±2°C accuracy from -55°C to +125°C | ||
| 1042 | * Operating Range: -40 ~~ 125 °C | ||
| 1043 | * Working voltage 2.35v ~~ 5v | ||
| 1044 | |||
| 1045 | |||
| 1046 | == 3.2 E31F Temperature Probe == | ||
| 1047 | |||
| 1048 | |||
| 1049 | [[image:65N-E31F-1.jpg||height="161" width="162"]] [[image:65N-E31F.jpg||height="192" width="194"]] | ||
| 1050 | |||
| 1051 | |||
| 1052 | Temperature sensor with 1 meters cable long | ||
| 1053 | |||
| 1054 | * Resolution: 0.01 °C | ||
| 1055 | * Accuracy Tolerance : Typical ±0.3 °C | ||
| 1056 | * Long Term Drift: < 0.02 °C/yr | ||
| 1057 | * Operating Range: -40 ~~ 125 °C | ||
| 1058 | * Working voltage 2.35v ~~ 5v | ||
| 1059 | |||
| 1060 | |||
| 1061 | = 4. Configure LHT65N via AT command or LoRaWAN downlink = | ||
| 1062 | |||
| 1063 | |||
| 1064 | ((( | ||
| 1065 | Use can configure LHT65N via AT Command or LoRaWAN Downlink. | ||
| 1066 | ))) | ||
| 1067 | |||
| 1068 | * ((( | ||
| 1069 | AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]]. | ||
| 1070 | ))) | ||
| 1071 | |||
| 1072 | * ((( | ||
| 1073 | LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] | ||
| 1074 | ))) | ||
| 1075 | |||
| 1076 | ((( | ||
| 1077 | There are two kinds of commands to configure LHT65N, they are: | ||
| 1078 | ))) | ||
| 1079 | |||
| 1080 | * ((( | ||
| 1081 | (% style="color:#4f81bd" %)**General Commands**. | ||
| 1082 | ))) | ||
| 1083 | |||
| 1084 | ((( | ||
| 1085 | These commands are to configure: | ||
| 1086 | ))) | ||
| 1087 | |||
| 1088 | 1. ((( | ||
| 1089 | General system settings like: uplink interval. | ||
| 1090 | ))) | ||
| 1091 | 1. ((( | ||
| 1092 | LoRaWAN protocol & radio-related commands. | ||
| 1093 | ))) | ||
| 1094 | |||
| 1095 | ((( | ||
| 1096 | They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] | ||
| 1097 | ))) | ||
| 1098 | |||
| 1099 | * ((( | ||
| 1100 | (% style="color:#4f81bd" %)**Commands special design for LHT65N** | ||
| 1101 | ))) | ||
| 1102 | |||
| 1103 | ((( | ||
| 1104 | These commands are only valid for LHT65N, as below: | ||
| 1105 | ))) | ||
| 1106 | |||
| 1107 | |||
| 1108 | == 4.1 Set Transmit Interval Time == | ||
| 1109 | |||
| 1110 | |||
| 1111 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
| 1112 | |||
| 1113 | |||
| 1114 | (% style="color:#4f81bd" %)**AT Command: AT+TDC** | ||
| 1115 | |||
| 1116 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:501px" %) | ||
| 1117 | |(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:166px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:180px" %)**Response** | ||
| 1118 | |(% style="width:155px" %)AT+TDC=?|(% style="width:162px" %)Show current transmit Interval|(% style="width:177px" %)30000 OK the interval is 30000ms = 30s | ||
| 1119 | |(% style="width:155px" %)AT+TDC=60000|(% style="width:162px" %)Set Transmit Interval|(% style="width:177px" %)OK Set transmit interval to 60000ms = 60 seconds | ||
| 1120 | |||
| 1121 | (% style="color:#4f81bd" %)**Downlink Command: 0x01** | ||
| 1122 | |||
| 1123 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
| 1124 | |||
| 1125 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
| 1126 | |||
| 1127 | * **Example 1**: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
| 1128 | |||
| 1129 | * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
| 1130 | |||
| 1131 | |||
| 1132 | == 4.2 Set External Sensor Mode == | ||
| 1133 | |||
| 1134 | |||
| 1135 | Feature: Change External Sensor Mode. | ||
| 1136 | |||
| 1137 | |||
| 1138 | (% style="color:#4f81bd" %)**AT Command: AT+EXT** | ||
| 1139 | |||
| 1140 | |||
| 1141 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:468px" %) | ||
| 1142 | |(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:153px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:160px" %)**Response** | ||
| 1143 | |(% style="width:155px" %)AT+EXT=?|(% style="width:151px" %)Get current external sensor mode|(% style="width:158px" %)1 OK External Sensor mode =1 | ||
| 1144 | |(% style="width:155px" %)AT+EXT=1|(% colspan="2" rowspan="1" style="width:309px" %)Set external sensor mode to 1 | ||
| 1145 | |(% style="width:155px" %)AT+EXT=9|(% colspan="2" rowspan="1" style="width:309px" %)Set to external DS18B20 with timestamp | ||
| 1146 | |||
| 1147 | (% style="color:#4f81bd" %)**Downlink Command: 0xA2** | ||
| 1148 | |||
| 1149 | Total bytes: 2 ~~ 5 bytes | ||
| 1150 | |||
| 1151 | **Example:** | ||
| 1152 | |||
| 1153 | * 0xA201: Set external sensor type to E1 | ||
| 1154 | |||
| 1155 | * 0xA209: Same as AT+EXT=9 | ||
| 1156 | |||
| 1157 | * 0xA20702003c: Same as AT+SETCNT=60 | ||
| 1158 | |||
| 1159 | |||
| 1160 | == 4.3 Enable/Disable uplink Temperature probe ID == | ||
| 1161 | |||
| 1162 | |||
| 1163 | ((( | ||
| 1164 | Feature: If PID is enabled, device will send the temperature probe ID on: | ||
| 1165 | ))) | ||
| 1166 | |||
| 1167 | * ((( | ||
| 1168 | First Packet after OTAA Join | ||
| 1169 | ))) | ||
| 1170 | * ((( | ||
| 1171 | Every 24 hours since the first packet. | ||
| 1172 | ))) | ||
| 1173 | |||
| 1174 | ((( | ||
| 1175 | PID is default set to disable (0) | ||
| 1176 | |||
| 1177 | |||
| 1178 | ))) | ||
| 1179 | |||
| 1180 | (% style="color:#4f81bd" %)**AT Command:** | ||
| 1181 | |||
| 1182 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:381px" %) | ||
| 1183 | |(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:138px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:88px" %)**Response** | ||
| 1184 | |(% style="width:155px" %)AT+PID=1|(% style="width:136px" %)Enable PID uplink|(% style="width:86px" %)OK | ||
| 1185 | |||
| 1186 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1187 | |||
| 1188 | * **0xA800** **~-~->** AT+PID=0 | ||
| 1189 | * **0xA801** **~-~->** AT+PID=1 | ||
| 1190 | |||
| 1191 | |||
| 1192 | == 4.4 Set Password == | ||
| 1193 | |||
| 1194 | |||
| 1195 | Feature: Set device password, max 9 digits | ||
| 1196 | |||
| 1197 | (% style="color:#4f81bd" %)**AT Command: AT+PWORD** | ||
| 1198 | |||
| 1199 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:372px" %) | ||
| 1200 | |(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:128px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:89px" %)**Response** | ||
| 1201 | |(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)((( | ||
| 1202 | 123456 | ||
| 1203 | |||
| 1204 | OK | ||
| 1205 | ))) | ||
| 1206 | |(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK | ||
| 1207 | |||
| 1208 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1209 | |||
| 1210 | No downlink command for this feature. | ||
| 1211 | |||
| 1212 | |||
| 1213 | == 4.5 Quit AT Command == | ||
| 1214 | |||
| 1215 | |||
| 1216 | Feature: Quit AT Command mode, so user needs to input password again before use AT Commands. | ||
| 1217 | |||
| 1218 | (% style="color:#4f81bd" %)**AT Command: AT+DISAT** | ||
| 1219 | |||
| 1220 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:433px" %) | ||
| 1221 | |(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:191px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:86px" %)**Response** | ||
| 1222 | |(% style="width:155px" %)AT+DISAT|(% style="width:191px" %)Quit AT Commands mode|(% style="width:86px" %)OK | ||
| 1223 | |||
| 1224 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1225 | |||
| 1226 | No downlink command for this feature. | ||
| 1227 | |||
| 1228 | |||
| 1229 | == 4.6 Set to sleep mode == | ||
| 1230 | |||
| 1231 | |||
| 1232 | Feature: Set device to sleep mode | ||
| 1233 | |||
| 1234 | * **AT+Sleep=0** : Normal working mode, device will sleep and use lower power when there is no LoRa message | ||
| 1235 | * **AT+Sleep=1** : Device is in deep sleep mode, no LoRa activation happen, used for storage or shipping. | ||
| 1236 | |||
| 1237 | (% style="color:#4f81bd" %)**AT Command: AT+SLEEP** | ||
| 1238 | |||
| 1239 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:513px" %) | ||
| 1240 | |(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:140px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:218px" %)**Response** | ||
| 1241 | |(% style="width:155px" %)AT+SLEEP|(% style="width:139px" %)Set to sleep mode|(% style="width:213px" %)((( | ||
| 1242 | Clear all stored sensor data… | ||
| 1243 | |||
| 1244 | OK | ||
| 1245 | ))) | ||
| 1246 | |||
| 1247 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1248 | |||
| 1249 | * There is no downlink command to set to Sleep mode. | ||
| 1250 | |||
| 1251 | |||
| 1252 | == 4.7 Set system time == | ||
| 1253 | |||
| 1254 | |||
| 1255 | Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]] | ||
| 1256 | |||
| 1257 | (% style="color:#4f81bd" %)**AT Command:** | ||
| 1258 | |||
| 1259 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:506px" %) | ||
| 1260 | |(% style="background-color:#d9e2f3; color:#0070c0; width:188px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:318px" %)**Function** | ||
| 1261 | |(% style="width:154px" %)AT+TIMESTAMP=1611104352|(% style="width:285px" %)((( | ||
| 1262 | OK | ||
| 1263 | |||
| 1264 | Set System time to 2021-01-20 00:59:12 | ||
| 1265 | ))) | ||
| 1266 | |||
| 1267 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1268 | |||
| 1269 | 0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352 | ||
| 1270 | |||
| 1271 | |||
| 1272 | == 4.8 Set Time Sync Mode == | ||
| 1273 | |||
| 1274 | |||
| 1275 | ((( | ||
| 1276 | Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command. | ||
| 1277 | ))) | ||
| 1278 | |||
| 1279 | ((( | ||
| 1280 | 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. | ||
| 1281 | ))) | ||
| 1282 | |||
| 1283 | (% style="color:#4f81bd" %)**AT Command:** | ||
| 1284 | |||
| 1285 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:475px" %) | ||
| 1286 | |(% style="background-color:#d9e2f3; color:#0070c0; width:156px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:315px" %)**Function** | ||
| 1287 | |(% style="width:156px" %)AT+SYNCMOD=1|(% style="width:315px" %)Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq) | ||
| 1288 | |||
| 1289 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1290 | |||
| 1291 | 0x28 01 ~/~/ Same As AT+SYNCMOD=1 | ||
| 1292 | 0x28 00 ~/~/ Same As AT+SYNCMOD=0 | ||
| 1293 | |||
| 1294 | |||
| 1295 | == 4.9 Set Time Sync Interval == | ||
| 1296 | |||
| 1297 | |||
| 1298 | Feature: Define System time sync interval. SYNCTDC default value: 10 days. | ||
| 1299 | |||
| 1300 | (% style="color:#4f81bd" %)**AT Command:** | ||
| 1301 | |||
| 1302 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:472px" %) | ||
| 1303 | |(% style="background-color:#d9e2f3; color:#0070c0; width:158px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:314px" %)**Function** | ||
| 1304 | |(% style="width:156px" %)AT+SYNCTDC=0x0A |(% style="width:311px" %)Set SYNCTDC to 10 (0x0A), so the sync time is 10 days. | ||
| 1305 | |||
| 1306 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1307 | |||
| 1308 | **0x29 0A** ~/~/ Same as AT+SYNCTDC=0x0A | ||
| 1309 | |||
| 1310 | |||
| 1311 | == 4.10 Print data entries base on page. == | ||
| 1312 | |||
| 1313 | |||
| 1314 | Feature: Print the sector data from start page to stop page (max is 416 pages). | ||
| 1315 | |||
| 1316 | (% style="color:#4f81bd" %)**AT Command: AT+PDTA** | ||
| 1317 | |||
| 1318 | [[image:image-20230426164330-2.png]] | ||
| 1319 | |||
| 1320 | |||
| 1321 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1322 | |||
| 1323 | No downlink commands for feature | ||
| 1324 | |||
| 1325 | |||
| 1326 | == 4.11 Print last few data entries. == | ||
| 1327 | |||
| 1328 | |||
| 1329 | Feature: Print the last few data entries | ||
| 1330 | |||
| 1331 | (% style="color:#4f81bd" %)**AT Command: AT+PLDTA** | ||
| 1332 | |||
| 1333 | [[image:image-20230426164932-3.png]] | ||
| 1334 | |||
| 1335 | |||
| 1336 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
| 1337 | |||
| 1338 | No downlink commands for feature | ||
| 1339 | |||
| 1340 | |||
| 1341 | == 4.12 Clear Flash Record == | ||
| 1342 | |||
| 1343 | |||
| 1344 | Feature: Clear flash storage for data log feature. | ||
| 1345 | |||
| 1346 | |||
| 1347 | (% style="color:#4f81bd" %)**AT Command: AT+CLRDTA** | ||
| 1348 | |||
| 1349 | |||
| 1350 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:503px" %) | ||
| 1351 | |(% style="background-color:#d9e2f3; color:#0070c0; width:157px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:137px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:209px" %)**Response** | ||
| 1352 | |(% style="width:155px" %)AT+CLRDTA |(% style="width:134px" %)Clear date record|(% style="width:209px" %)((( | ||
| 1353 | Clear all stored sensor data… | ||
| 1354 | |||
| 1355 | OK | ||
| 1356 | ))) | ||
| 1357 | |||
| 1358 | (% style="color:#4f81bd" %)**Downlink Command: 0xA3** | ||
| 1359 | |||
| 1360 | * Example: 0xA301 ~/~/ Same as AT+CLRDTA | ||
| 1361 | |||
| 1362 | |||
| 1363 | == 4.13 Auto Send None-ACK messages == | ||
| 1364 | |||
| 1365 | |||
| 1366 | 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. | ||
| 1367 | |||
| 1368 | (% style="color:#4f81bd" %)**AT Command: AT+PNACKMD** | ||
| 1369 | |||
| 1370 | The default factory setting is 0 | ||
| 1371 | |||
| 1372 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:367px" %) | ||
| 1373 | |=(% style="width: 158px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 120px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 87px;background-color:#D9E2F3;color:#0070C0" %)**Response** | ||
| 1374 | |(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK | ||
| 1375 | |||
| 1376 | (% style="color:#4f81bd" %)**Downlink Command: 0x34** | ||
| 1377 | |||
| 1378 | * Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 | ||
| 1379 | |||
| 1380 | |||
| 1381 | == 4.14 Modified WMOD command for external sensor TMP117 or DS18B20 temperature alarm（Since firmware 1.3.0） == | ||
| 1382 | |||
| 1383 | |||
| 1384 | Feature: Set internal and external temperature sensor alarms. | ||
| 1385 | |||
| 1386 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) | ||
| 1387 | |=(% style="width: 250px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 200px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**Response** | ||
| 1388 | |(% style="width:268px" %)AT+WMOD=parameter1,parameter2,parameter3,parameter4|(% style="width:255px" %)Set internal and external temperature sensor alarms|(% style="width:181px" %)OK | ||
| 1389 | |||
| 1390 | (% style="color:#037691" %)**AT+WMOD=parameter1,parameter2,parameter3,parameter4** | ||
| 1391 | |||
| 1392 | (% style="color:#037691" %)**Parameter 1**(%%): Alarm mode: | ||
| 1393 | |||
| 1394 | 0): Cancel | ||
| 1395 | |||
| 1396 | 1): Threshold alarm | ||
| 1397 | |||
| 1398 | 2): Fluctuation alarm | ||
| 1399 | |||
| 1400 | |||
| 1401 | (% style="color:#037691" %)** Parameter 2**(%%): Sampling time. Unit: seconds, up to 255 seconds. | ||
| 1402 | |||
| 1403 | (% style="color:red" %)**Note: When the collection time is less than 60 seconds and always exceeds the set alarm threshold, the sending interval will not be the collection time, but will be sent every 60 seconds.** | ||
| 1404 | |||
| 1405 | |||
| 1406 | (% style="color:#037691" %) **Parameter 3 and parameter 4:** | ||
| 1407 | |||
| 1408 | 1): If Alarm Mode is set to 1: Parameter 3 and parameter 4 are valid, as before, they represent low temperature and high temperature. | ||
| 1409 | |||
| 1410 | Such as AT+WMOD=1,60,45,105, it means high and low temperature alarm. | ||
| 1411 | |||
| 1412 | |||
| 1413 | 2): If Alarm Mode is set to 2: Parameter 3 is valid, which represents the difference between the currently collected temperature and the last uploaded temperature. | ||
| 1414 | |||
| 1415 | Such as AT+WMOD=2,10,2,it means that it is a fluctuation alarm. | ||
| 1416 | |||
| 1417 | If the difference between the current collected temperature and the last Uplin is ±2 degrees, the alarm will be issued. | ||
| 1418 | |||
| 1419 | |||
| 1420 | (% style="color:#4f81bd" %)**Downlink Command: 0xA5** | ||
| 1421 | |||
| 1422 | 0xA5 00 ~-~- AT+WMOD=0. | ||
| 1423 | |||
| 1424 | 0xA5 01 0A 11 94 29 04 ~-~- AT+WMOD=1,10,45,105 (AT+WMOD = second byte, third byte, fourth and fifth bytes divided by 100, sixth and seventh bytes divided by 100 ) | ||
| 1425 | |||
| 1426 | 0XA5 01 0A F9 C0 29 04 ~-~-AT+WMOD=1,10,-16,105(Need to convert -16 to -1600 for calculation，-1600(DEC)=FFFFFFFFFFFFF9C0(HEX) FFFFFFFFFFFFF9C0(HEX) +10000(HEX)=F9C0(HEX)) | ||
| 1427 | |||
| 1428 | 0xA5 02 0A 02 ~-~- AT+WMOD=2,10,2 (AT+WMOD = second byte, third byte, fourth byte) | ||
| 1429 | |||
| 1430 | 0xA5 FF ~-~- After the device receives it, upload the current alarm configuration (FPORT=8). Such as 01 0A 11 94 29 04 or 02 0A 02. | ||
| 1431 | |||
| 1432 | |||
| 1433 | = 5. Battery & How to replace = | ||
| 1434 | |||
| 1435 | == 5.1 Battery Type == | ||
| 1436 | |||
| 1437 | |||
| 1438 | ((( | ||
| 1439 | 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. | ||
| 1440 | ))) | ||
| 1441 | |||
| 1442 | ((( | ||
| 1443 | The discharge curve is not linear so can't simply use percentage to show the battery level. Below is the battery performance. | ||
| 1444 | |||
| 1445 | |||
| 1446 | [[image:image-20220515075034-1.png||_mstalt="428961" height="208" width="644"]] | ||
| 1447 | ))) | ||
| 1448 | |||
| 1449 | The minimum Working Voltage for the LHT65N is ~~ 2.5v. When battery is lower than 2.6v, it is time to change the battery. | ||
| 1450 | |||
| 1451 | |||
| 1452 | == 5.2 Replace Battery == | ||
| 1453 | |||
| 1454 | |||
| 1455 | 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. | ||
| 1456 | |||
| 1457 | [[image:image-20220515075440-2.png||_mstalt="429546" height="338" width="272"]][[image:image-20220515075625-3.png||_mstalt="431574" height="193" width="257"]] | ||
| 1458 | |||
| 1459 | |||
| 1460 | == 5.3 Battery Life Analyze == | ||
| 1461 | |||
| 1462 | |||
| 1463 | ((( | ||
| 1464 | 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: | ||
| 1465 | [[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]] | ||
| 1466 | ))) | ||
| 1467 | |||
| 1468 | |||
| 1469 | ((( | ||
| 1470 | A full detail test report for LHT65N 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]] | ||
| 1471 | ))) | ||
| 1472 | |||
| 1473 | |||
| 1474 | = 6. FAQ = | ||
| 1475 | |||
| 1476 | == 6.1 How to use AT Command? == | ||
| 1477 | |||
| 1478 | |||
| 1479 | LHT65N supports AT Command set.User can use a USB to TTL adapter plus the Program Cable to connect to LHT65 for using AT command, as below. | ||
| 1480 | |||
| 1481 | [[image:image-20220530085651-1.png||_mstalt="429949"]] | ||
| 1482 | |||
| 1483 | |||
| 1484 | **Connection:** | ||
| 1485 | |||
| 1486 | * (% style="background-color:yellow" %)**USB to TTL GND <~-~->GND** | ||
| 1487 | * (% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+** | ||
| 1488 | * (% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11** | ||
| 1489 | |||
| 1490 | ((( | ||
| 1491 | In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console for LHT65N. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**) (%%)to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout. | ||
| 1492 | ))) | ||
| 1493 | |||
| 1494 | |||
| 1495 | Input password and ATZ to activate LHT65N,As shown below: | ||
| 1496 | |||
| 1497 | [[image:image-20220530095701-4.png||_mstalt="430014"]] | ||
| 1498 | |||
| 1499 | |||
| 1500 | AT Command List is as below: | ||
| 1501 | |||
| 1502 | AT+<CMD>? : Help on <CMD> | ||
| 1503 | |||
| 1504 | AT+<CMD> : Run <CMD> | ||
| 1505 | |||
| 1506 | AT+<CMD>=<value> : Set the value | ||
| 1507 | |||
| 1508 | AT+<CMD>=? : Get the value | ||
| 1509 | |||
| 1510 | AT+DEBUG: Set more info output | ||
| 1511 | |||
| 1512 | ATZ: Trig a reset of the MCU | ||
| 1513 | |||
| 1514 | AT+FDR: Reset Parameters to Factory Default, Keys Reserve | ||
| 1515 | |||
| 1516 | AT+DEUI: Get or Set the Device EUI | ||
| 1517 | |||
| 1518 | AT+DADDR: Get or Set the Device Address | ||
| 1519 | |||
| 1520 | AT+APPKEY: Get or Set the Application Key | ||
| 1521 | |||
| 1522 | AT+NWKSKEY: Get or Set the Network Session Key | ||
| 1523 | |||
| 1524 | AT+APPSKEY: Get or Set the Application Session Key | ||
| 1525 | |||
| 1526 | AT+APPEUI: Get or Set the Application EUI | ||
| 1527 | |||
| 1528 | AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on) | ||
| 1529 | |||
| 1530 | AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec) | ||
| 1531 | |||
| 1532 | AT+DR: Get or Set the Data Rate. (0-7 corresponding to DR_X) | ||
| 1533 | |||
| 1534 | AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing | ||
| 1535 | |||
| 1536 | AT+PNM: Get or Set the public network mode. (0: off, 1: on) | ||
| 1537 | |||
| 1538 | AT+RX2FQ: Get or Set the Rx2 window frequency | ||
| 1539 | |||
| 1540 | AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X) | ||
| 1541 | |||
| 1542 | AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms | ||
| 1543 | |||
| 1544 | AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms | ||
| 1545 | |||
| 1546 | AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms | ||
| 1547 | |||
| 1548 | AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms | ||
| 1549 | |||
| 1550 | AT+NJM: Get or Set the Network Join Mode. (0: ABP, 1: OTAA) | ||
| 1551 | |||
| 1552 | AT+NWKID: Get or Set the Network ID | ||
| 1553 | |||
| 1554 | AT+FCU: Get or Set the Frame Counter Uplink | ||
| 1555 | |||
| 1556 | AT+FCD: Get or Set the Frame Counter Downlink | ||
| 1557 | |||
| 1558 | AT+CLASS: Get or Set the Device Class | ||
| 1559 | |||
| 1560 | AT+JOIN: Join network | ||
| 1561 | |||
| 1562 | AT+NJS: Get the join status | ||
| 1563 | |||
| 1564 | AT+SENDB: Send hexadecimal data along with the application port | ||
| 1565 | |||
| 1566 | AT+SEND: Send text data along with the application port | ||
| 1567 | |||
| 1568 | AT+RECVB: Print last received data in binary format (with hexadecimal values) | ||
| 1569 | |||
| 1570 | AT+RECV: Print last received data in raw format | ||
| 1571 | |||
| 1572 | AT+VER: Get current image version and Frequency Band | ||
| 1573 | |||
| 1574 | AT+CFM: Get or Set the confirmation mode (0-1) | ||
| 1575 | |||
| 1576 | AT+CFS: Get confirmation status of the last AT+SEND (0-1) | ||
| 1577 | |||
| 1578 | AT+SNR: Get the SNR of the last received packet | ||
| 1579 | |||
| 1580 | AT+RSSI: Get the RSSI of the last received packet | ||
| 1581 | |||
| 1582 | AT+TDC: Get or set the application data transmission interval in ms | ||
| 1583 | |||
| 1584 | AT+PORT: Get or set the application port | ||
| 1585 | |||
| 1586 | AT+DISAT: Disable AT commands | ||
| 1587 | |||
| 1588 | AT+PWORD: Set password, max 9 digits | ||
| 1589 | |||
| 1590 | AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode | ||
| 1591 | |||
| 1592 | AT+CHE: Get or Set eight channels mode,Only for US915,AU915,CN470 | ||
| 1593 | |||
| 1594 | AT+PDTA: Print the sector data from start page to stop page | ||
| 1595 | |||
| 1596 | AT+PLDTA: Print the last few sets of data | ||
| 1597 | |||
| 1598 | AT+CLRDTA: Clear the storage, record position back to 1st | ||
| 1599 | |||
| 1600 | AT+SLEEP: Set sleep mode | ||
| 1601 | |||
| 1602 | AT+EXT: Get or Set external sensor model | ||
| 1603 | |||
| 1604 | AT+BAT: Get the current battery voltage in mV | ||
| 1605 | |||
| 1606 | AT+CFG: Print all configurations | ||
| 1607 | |||
| 1608 | AT+WMOD: Get or Set Work Mode | ||
| 1609 | |||
| 1610 | AT+ARTEMP: Get or set the internal Temperature sensor alarm range | ||
| 1611 | |||
| 1612 | AT+CITEMP: Get or set the internal Temperature sensor collection interval in min | ||
| 1613 | |||
| 1614 | AT+SETCNT: Set the count at present | ||
| 1615 | |||
| 1616 | AT+RJTDC: Get or set the ReJoin data transmission interval in min | ||
| 1617 | |||
| 1618 | AT+RPL: Get or set response level | ||
| 1619 | |||
| 1620 | AT+TIMESTAMP: Get or Set UNIX timestamp in second | ||
| 1621 | |||
| 1622 | AT+LEAPSEC: Get or Set Leap Second | ||
| 1623 | |||
| 1624 | AT+SYNCMOD: Get or Set time synchronization method | ||
| 1625 | |||
| 1626 | AT+SYNCTDC: Get or set time synchronization interval in day | ||
| 1627 | |||
| 1628 | AT+PID: Get or set the PID | ||
| 1629 | |||
| 1630 | |||
| 1631 | == 6.2 Where to use AT commands and Downlink commands == | ||
| 1632 | |||
| 1633 | |||
| 1634 | **AT commands：** | ||
| 1635 | |||
| 1636 | [[image:image-20220620153708-1.png||_mstalt="429806" height="603" width="723"]] | ||
| 1637 | |||
| 1638 | |||
| 1639 | **Downlink commands:** | ||
| 1640 | |||
| 1641 | |||
| 1642 | (% style="color:blue" %)**TTN:** | ||
| 1643 | |||
| 1644 | [[image:image-20220615092124-2.png||_mstalt="429221" height="649" width="688"]] | ||
| 1645 | |||
| 1646 | |||
| 1647 | |||
| 1648 | (% style="color:blue" %)**Helium：** | ||
| 1649 | |||
| 1650 | [[image:image-20220615092551-3.png||_mstalt="430794" height="423" width="835"]] | ||
| 1651 | |||
| 1652 | |||
| 1653 | |||
| 1654 | (% style="color:blue" %)**Chirpstack: The downlink window will not be displayed until the network is accessed** | ||
| 1655 | |||
| 1656 | |||
| 1657 | [[image:image-20220615094850-6.png||_mstalt="433082"]] | ||
| 1658 | |||
| 1659 | |||
| 1660 | [[image:image-20220615094904-7.png||_mstalt="433485" height="281" width="911"]] | ||
| 1661 | |||
| 1662 | |||
| 1663 | |||
| 1664 | (% style="color:blue" %)**Aws:** | ||
| 1665 | |||
| 1666 | [[image:image-20220615092939-4.png||_mstalt="434460" height="448" width="894"]] | ||
| 1667 | |||
| 1668 | |||
| 1669 | == 6.3 How to change the uplink interval？ == | ||
| 1670 | |||
| 1671 | |||
| 1672 | Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]] | ||
| 1673 | |||
| 1674 | |||
| 1675 | == 6.4 How to use TTL-USB to connect a PC to input AT commands? == | ||
| 1676 | |||
| 1677 | |||
| 1678 | [[image:image-20220615153355-1.png||_mstalt="430222"]] | ||
| 1679 | |||
| 1680 | [[image:1655802313617-381.png||_mstalt="293917"]] | ||
| 1681 | |||
| 1682 | |||
| 1683 | ((( | ||
| 1684 | In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600** (%%)to access to access serial console for LHT65N. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(% style="color:red" %))(%%) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout. | ||
| 1685 | ))) | ||
| 1686 | |||
| 1687 | |||
| 1688 | Input password and ATZ to activate LHT65N,As shown below: | ||
| 1689 | |||
| 1690 | [[image:image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]] | ||
| 1691 | |||
| 1692 | |||
| 1693 | == 6.5 How to use TTL-USB to connect PC to upgrade firmware? == | ||
| 1694 | |||
| 1695 | |||
| 1696 | [[image:image-20220615153355-1.png||_mstalt="430222"]] | ||
| 1697 | |||
| 1698 | |||
| 1699 | (% style="color:blue" %)**Step1**(%%): Install [[TremoProgrammer>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AAAnJD_qGZ42bB52o4UmH9v9a/LHT65N%20Temperature%20%26%20Humidity%20Sensor/tool?dl=0&subfolder_nav_tracking=1]] first. | ||
| 1700 | |||
| 1701 | [[image:image-20220615170542-5.png||_mstalt="430638"]] | ||
| 1702 | |||
| 1703 | |||
| 1704 | |||
| 1705 | (% _mstmutation="1" style="color:blue" %)**Step2**(%%)：wiring method.(% style="display:none" %) | ||
| 1706 | |||
| 1707 | First connect the four lines；(% style="display:none" %) | ||
| 1708 | |||
| 1709 | [[image:image-20220621170938-1.png||_mstalt="431340" height="413" width="419"]]，(% style="display:none" %) | ||
| 1710 | |||
| 1711 | |||
| 1712 | Then use DuPont cable to short circuit port3 and port1, and then release them, so that the device enters bootlaod mode. | ||
| 1713 | |||
| 1714 | [[image:image-20220621170938-2.png||_mstalt="431704"]] | ||
| 1715 | |||
| 1716 | |||
| 1717 | |||
| 1718 | (% style="color:blue" %)**Step3：**(%%)Select the device port to be connected, baud rate and bin file to be downloaded. | ||
| 1719 | |||
| 1720 | [[image:image-20220615171334-6.png||_mstalt="431028"]] | ||
| 1721 | |||
| 1722 | |||
| 1723 | Click the (% style="color:blue" %)**start**(%%) button to start the firmware upgrade. | ||
| 1724 | |||
| 1725 | |||
| 1726 | When this interface appears, it indicates that the download has been completed. | ||
| 1727 | |||
| 1728 | [[image:image-20220620160723-8.png||_mstalt="430703"]] | ||
| 1729 | |||
| 1730 | |||
| 1731 | Finally, unplug the DuPont cable on port4, and then use the DuPont cable to short circuit port3 and port1 to reset the device. | ||
| 1732 | |||
| 1733 | |||
| 1734 | == 6.6 Using USB-TYPE-C to connect to the computer using the AT command == | ||
| 1735 | |||
| 1736 | |||
| 1737 | [[image:image-20220623110706-1.png||_mstalt="427869"]] | ||
| 1738 | |||
| 1739 | |||
| 1740 | **UART Port of LHT65N:** | ||
| 1741 | |||
| 1742 | * (% class="mark" %)**PB0: RXD** | ||
| 1743 | * (% class="mark" %)**PB1: TXD** | ||
| 1744 | * (% class="mark" %)**GND** | ||
| 1745 | |||
| 1746 | [[image:image-20220623112117-4.png||_mstalt="428350" height="459" width="343"]] | ||
| 1747 | |||
| 1748 | |||
| 1749 | ((( | ||
| 1750 | In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600** (%%)to access to access serial console for LHT65N. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(% style="color:red" %))(%%) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout. | ||
| 1751 | ))) | ||
| 1752 | |||
| 1753 | |||
| 1754 | Input password and ATZ to activate LHT65N,As shown below: | ||
| 1755 | |||
| 1756 | [[image:image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]] | ||
| 1757 | |||
| 1758 | |||
| 1759 | == 6.7 How to use USB-TYPE-C to connect PC to upgrade firmware? == | ||
| 1760 | |||
| 1761 | |||
| 1762 | [[image:image-20220623110706-1.png||_mstalt="427869"]] | ||
| 1763 | |||
| 1764 | |||
| 1765 | (% style="color:blue" %)**Step1**(%%): Install [[TremoProgrammer>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AAAnJD_qGZ42bB52o4UmH9v9a/LHT65N%20Temperature%20%26%20Humidity%20Sensor/tool?dl=0&subfolder_nav_tracking=1]] first. | ||
| 1766 | |||
| 1767 | [[image:image-20220615170542-5.png||_mstalt="430638"]] | ||
| 1768 | |||
| 1769 | |||
| 1770 | |||
| 1771 | (% _mstmutation="1" style="color:blue" %)**Step2**(%%)：wiring method.(% style="display:none" %) | ||
| 1772 | |||
| 1773 | First connect the four lines； | ||
| 1774 | |||
| 1775 | [[image:image-20220623113959-5.png||_mstalt="433485" height="528" width="397"]] | ||
| 1776 | |||
| 1777 | Connect A8 and GND with Dupont wire for a while and then separate，enter reset mode | ||
| 1778 | |||
| 1779 | |||
| 1780 | |||
| 1781 | (% style="color:blue" %)**Step3：**(%%)Select the device port to be connected, baud rate and bin file to be downloaded. | ||
| 1782 | |||
| 1783 | [[image:image-20220615171334-6.png||_mstalt="431028"]] | ||
| 1784 | |||
| 1785 | |||
| 1786 | Click the (% style="color:blue" %)**start**(%%) button to start the firmware upgrade. | ||
| 1787 | |||
| 1788 | |||
| 1789 | When this interface appears, it indicates that the download has been completed. | ||
| 1790 | |||
| 1791 | [[image:image-20220620160723-8.png||_mstalt="430703"]] | ||
| 1792 | |||
| 1793 | |||
| 1794 | Finally,Disconnect 3.3v，Connect A8 and GND with Dupont wire for a while and then separate，exit reset mode | ||
| 1795 | |||
| 1796 | |||
| 1797 | == 6.8 Why can't I see the datalog information == | ||
| 1798 | |||
| 1799 | |||
| 1800 | ~1. The time is not aligned, and the correct query command is not used. | ||
| 1801 | |||
| 1802 | 2. Decoder error, did not parse the datalog data, the data was filtered. | ||
| 1803 | |||
| 1804 | |||
| 1805 | = 7. Order Info = | ||
| 1806 | |||
| 1807 | |||
| 1808 | Part Number: (% style="color:#4f81bd" %)** LHT65N-XX-YY** | ||
| 1809 | |||
| 1810 | (% style="color:#4f81bd" %)**XX **(%%): The default frequency band | ||
| 1811 | |||
| 1812 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**AS923**(%%): LoRaWAN AS923 band | ||
| 1813 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**AU915**(%%): LoRaWAN AU915 band | ||
| 1814 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**EU433**(%%): LoRaWAN EU433 band | ||
| 1815 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**EU868**(%%): LoRaWAN EU868 band | ||
| 1816 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**KR920**(%%): LoRaWAN KR920 band | ||
| 1817 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**US915**(%%): LoRaWAN US915 band | ||
| 1818 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**IN865**(%%): LoRaWAN IN865 band | ||
| 1819 | * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**CN470**(%%): LoRaWAN CN470 band | ||
| 1820 | |||
| 1821 | (% style="color:#4f81bd" %)**YY**(%%): Sensor Accessories | ||
| 1822 | |||
| 1823 | * (% style="color:red" %)**E3**(%%): External Temperature Probe | ||
| 1824 | |||
| 1825 | |||
| 1826 | = 8. Packing Info = | ||
| 1827 | |||
| 1828 | |||
| 1829 | **Package Includes**: | ||
| 1830 | |||
| 1831 | * LHT65N Temperature & Humidity Sensor x 1 | ||
| 1832 | * Optional external sensor | ||
| 1833 | |||
| 1834 | **Dimension and weight**: | ||
| 1835 | |||
| 1836 | * Device Size: 10 x 10 x 3.5 mm | ||
| 1837 | * Device Weight: 120.5g | ||
| 1838 | |||
| 1839 | |||
| 1840 | = 9. Reference material = | ||
| 1841 | |||
| 1842 | |||
| 1843 | * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0]] | ||
| 1844 | |||
| 1845 | |||
| 1846 | = 10. FCC Warning = | ||
| 1847 | |||
| 1848 | |||
| 1849 | This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: | ||
| 1850 | |||
| 1851 | (1) This device may not cause harmful interference； | ||
| 1852 | |||
| 1853 | (2) this device must accept any interference received, including interference that may cause undesired operation. |