Changes for page LHT65N -- Manual do sensor de temperatura e umidade LoRaWAN
Last modified by Xiaoling on 2023/07/18 10:12
From version 176.1
edited by Bei Jinggeng
on 2022/06/23 11:43
on 2022/06/23 11:43
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 9 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 (% style="text-align:center" %) 2 -[[image:image-20220613162008-1.png||_mstalt="428142" height="5 79" width="379"]]2 +[[image:image-20220613162008-1.png||_mstalt="428142" height="510" width="334"]] 3 3 4 4 5 5 ... ... @@ -46,6 +46,7 @@ 46 46 47 47 == 1.2 Features == 48 48 49 + 49 49 * Wall mountable 50 50 * LoRaWAN v1.0.3 Class A protocol 51 51 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915 ... ... @@ -60,7 +60,6 @@ 60 60 61 61 62 62 63 - 64 64 == 1.3 Specification == 65 65 66 66 ... ... @@ -71,6 +71,8 @@ 71 71 * Long Term Drift: < 0.02 °C/yr 72 72 * Operating Range: -40 ~~ 85 °C 73 73 74 + 75 + 74 74 **Built-in Humidity Sensor:** 75 75 76 76 * Resolution: 0.04 %RH ... ... @@ -78,6 +78,8 @@ 78 78 * Long Term Drift: < 0.02 °C/yr 79 79 * Operating Range: 0 ~~ 96 %RH 80 80 83 + 84 + 81 81 **External Temperature Sensor:** 82 82 83 83 * Resolution: 0.0625 °C ... ... @@ -87,11 +87,11 @@ 87 87 88 88 89 89 90 - 91 91 = 2. Connect LHT65N to IoT Server = 92 92 93 93 == 2.1 How does LHT65N work? == 94 94 98 + 95 95 ((( 96 96 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. 97 97 ))) ... ... @@ -101,8 +101,10 @@ 101 101 ))) 102 102 103 103 108 + 104 104 == 2.2 How to Activate LHT65N? == 105 105 111 + 106 106 ((( 107 107 The LHT65N has two working modes: 108 108 ))) ... ... @@ -127,6 +127,7 @@ 127 127 128 128 == 2.3 Example to join LoRaWAN network == 129 129 136 + 130 130 (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %) 131 131 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. 132 132 ... ... @@ -142,6 +142,7 @@ 142 142 143 143 === 2.3.1 Step 1: Create Device n TTN === 144 144 152 + 145 145 ((( 146 146 Create a device in TTN V3 with the OTAA keys from LHT65N. 147 147 ))) ... ... @@ -166,9 +166,10 @@ 166 166 [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]] 167 167 168 168 169 -Note: LHT65N use same payload as LHT65. 170 170 178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.** 171 171 180 + 172 172 [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]] 173 173 174 174 ... ... @@ -182,6 +182,7 @@ 182 182 183 183 === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. === 184 184 194 + 185 185 ((( 186 186 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. 187 187 ))) ... ... @@ -193,6 +193,7 @@ 193 193 194 194 == 2.4 Uplink Payload == 195 195 206 + 196 196 ((( 197 197 The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% _mstvisible="3" style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default. 198 198 ))) ... ... @@ -267,12 +267,13 @@ 267 267 268 268 * The First 6 bytes: has fix meanings for every LHT65N. 269 269 * The 7th byte (EXT #): defines the external sensor model. 270 -* The 8(% _msthash="734578" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) ~~ 11(% _msthash="734579" _msttexthash="21372" _mstvisible="4" %)^^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.)281 +* The 8(% _msthash="734578" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) ~~ 11(% _msthash="734579" _msttexthash="21372" _mstvisible="4" %)^^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.) 271 271 272 272 273 273 274 274 === 2.4.1 Decoder in TTN V3 === 275 275 287 + 276 276 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. 277 277 278 278 Below is the position to put the decoder and LHT65N decoder can be download from here: ... ... @@ -288,6 +288,7 @@ 288 288 289 289 === 2.4.2 BAT-Battery Info === 290 290 303 + 291 291 These two bytes of BAT include the battery state and the actually voltage 292 292 293 293 [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]] ... ... @@ -305,6 +305,7 @@ 305 305 306 306 === 2.4.3 Built-in Temperature === 307 307 321 + 308 308 [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]] 309 309 310 310 * Temperature: 0x0ABB/100=27.47℃ ... ... @@ -317,6 +317,7 @@ 317 317 318 318 === 2.4.4 Built-in Humidity === 319 319 334 + 320 320 [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]] 321 321 322 322 * Humidity: 0x025C/10=60.4% ... ... @@ -325,6 +325,7 @@ 325 325 326 326 === 2.4.5 Ext # === 327 327 343 + 328 328 Bytes for External Sensor: 329 329 330 330 [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]] ... ... @@ -356,6 +356,7 @@ 356 356 357 357 ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ==== 358 358 375 + 359 359 ((( 360 360 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: 361 361 ))) ... ... @@ -469,16 +469,19 @@ 469 469 470 470 * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte** 471 471 472 -[[image:image-20220523152434-16.png||_mstalt="453921" _mstvisible="3"]] 489 +(% border="1" cellspacing="8" style="background-color:#ffffcc; color:green; width:520px" %) 490 +|(% style="width:60px" %)**Bits**|(% style="width:90px" %)**7**|(% style="width:100px" %)**6**|(% style="width:90px" %)**5**|(% style="width:100px" %)**4**|(% style="width:60px" %)**[3:0]** 491 +|(% 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) 473 473 474 -* Poll Message Flag: 1: This message is a poll message reply, 0: means this is a normal uplink. 475 -* Sync time OK: 476 -* 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) 493 +* (% style="color:blue" %)**Poll Message Flag**:(%%) 1: This message is a poll message reply, 0: means this is a normal uplink. 494 +* (% 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. 495 +* (% 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) 477 477 478 478 479 479 480 480 ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ==== 481 481 501 + 482 482 In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can 483 483 484 484 be used to power the external ADC sensor; user can control the power on time for this ... ... @@ -487,10 +487,46 @@ 487 487 488 488 AT+EXT=6,timeout (% _msthash="506085" _msttexthash="8782189" _mstvisible="3" style="color:red" %)Time to power this sensor, from 0 ~~ 65535ms 489 489 510 +For example: 490 490 512 +AT+EXT=6,1000 will power this sensor for 1000ms before sampling the ADC value. 491 491 514 + 515 +Or use **downlink command A2** to set the same. 516 + 517 +The measuring range of the node is only about 0.1V to 1.1V The voltage resolution is about 0.24mv. 518 + 519 +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. 520 + 521 +[[image:image-20220628150112-1.png||height="241" width="285"]] 522 + 523 + 524 +When ADC_IN1 pin is connected to GND or suspended, ADC value is 0 525 + 526 +[[image:image-20220628150714-4.png]] 527 + 528 + 529 +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. 530 + 531 +1) The minimum range is about 0.1V. Each chip has internal calibration, so this value is close to 0.1V 532 + 533 +[[image:image-20220628151005-5.png]] 534 + 535 + 536 +2) The maximum range is about 1.1V. Each chip has internal calibration, so this value is close to 1.1v 537 + 538 +[[image:image-20220628151056-6.png]] 539 + 540 + 541 +3) Within range 542 + 543 +[[image:image-20220628151143-7.png]] 544 + 545 + 546 + 492 492 == 2.5 Show data on Datacake == 493 493 549 + 494 494 ((( 495 495 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: 496 496 ))) ... ... @@ -538,6 +538,7 @@ 538 538 539 539 == 2.6 Datalog Feature == 540 540 597 + 541 541 ((( 542 542 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. 543 543 ))) ... ... @@ -546,13 +546,17 @@ 546 546 547 547 === 2.6.1 Ways to get datalog via LoRaWAN === 548 548 606 + 549 549 There are two methods: 550 550 551 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range. 552 -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. 609 +1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range. 610 +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 the network recovery. 553 553 612 +Below is the typical case for the auto-update datalog feature (Set PNACKMD=1) 554 554 614 +[[image:image-20220703111700-2.png||height="381" width="1119"]] 555 555 616 + 556 556 === 2.6.2 Unix TimeStamp === 557 557 558 558 ... ... @@ -575,6 +575,7 @@ 575 575 576 576 === 2.6.3 Set Device Time === 577 577 639 + 578 578 ((( 579 579 There are two ways to set device's time: 580 580 ))) ... ... @@ -592,7 +592,7 @@ 592 592 ))) 593 593 594 594 ((( 595 -(% 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.657 +(% 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.** 596 596 ))) 597 597 598 598 ((( ... ... @@ -611,6 +611,7 @@ 611 611 612 612 === 2.6.4 Poll sensor value === 613 613 676 + 614 614 User can poll sensor value based on timestamps from the server. Below is the downlink command. 615 615 616 616 [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]] ... ... @@ -628,6 +628,7 @@ 628 628 629 629 === 2.6.5 Datalog Uplink payload === 630 630 694 + 631 631 (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %) 632 632 The Datalog poll reply uplink will use below payload format. 633 633 ... ... @@ -634,6 +634,9 @@ 634 634 (% _mstvisible="1" %) 635 635 ((( 636 636 (% _mstvisible="2" %) 701 + 702 + 703 +(% _mstvisible="2" %) 637 637 (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload** 638 638 ))) 639 639 ... ... @@ -761,6 +761,7 @@ 761 761 ))) 762 762 ))) 763 763 831 + 764 764 (% _mstvisible="1" %) 765 765 (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext** 766 766 ... ... @@ -896,7 +896,7 @@ 896 896 (% _mstvisible="1" %) 897 897 ((( 898 898 (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %) 899 - Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03 967 + Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03 900 900 ))) 901 901 902 902 (% _mstvisible="1" %) ... ... @@ -993,8 +993,21 @@ 993 993 ))) 994 994 ))) 995 995 1064 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX** 996 996 1066 +Total bytes: 8 bytes 997 997 1068 +**Example:**AA0100010001003C 1069 + 1070 +WMOD=01 1071 + 1072 +CITEMP=0001 1073 + 1074 +TEMPlow=0001 1075 + 1076 +TEMPhigh=003C 1077 + 1078 + 998 998 == 2.8 LED Indicator == 999 999 1000 1000 The LHT65 has a triple color LED which for easy showing different stage . ... ... @@ -1009,7 +1009,6 @@ 1009 1009 * For each success downlink, the PURPLE LED will blink once 1010 1010 1011 1011 1012 - 1013 1013 == 2.9 installation == 1014 1014 1015 1015 (% _mstvisible="1" %) ... ... @@ -1023,8 +1023,24 @@ 1023 1023 1024 1024 [[image:image-20220619092222-1.png||height="182" width="188"]][[image:image-20220619092313-2.png||height="182" width="173"]] 1025 1025 1026 -1m long breakout cable for LHT65N 1106 +**1m long breakout cable for LHT65N. Features:** 1027 1027 1108 +* ((( 1109 +Use for AT Command, works for both LHT52/LHT65N 1110 +))) 1111 +* ((( 1112 +Update firmware for LHT65N, works for both LHT52/LHT65N 1113 +))) 1114 +* ((( 1115 +Supports ADC mode to monitor external ADC 1116 +))) 1117 +* ((( 1118 +Supports Interrupt mode 1119 +))) 1120 +* ((( 1121 +Exposed All pins from the LHT65N Type-C connector. 1122 +))) 1123 + 1028 1028 [[image:image-20220619092421-3.png||height="371" width="529"]] 1029 1029 1030 1030 ... ... @@ -1045,7 +1045,6 @@ 1045 1045 * Working voltage 2.35v ~~ 5v 1046 1046 1047 1047 1048 - 1049 1049 = 4. Configure LHT65N via AT command or LoRaWAN downlink = 1050 1050 1051 1051 ((( ... ... @@ -1112,7 +1112,6 @@ 1112 1112 * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 1113 1113 1114 1114 1115 - 1116 1116 == 4.2 Set External Sensor Mode == 1117 1117 1118 1118 Feature: Change External Sensor Mode. ... ... @@ -1135,7 +1135,6 @@ 1135 1135 * 0xA20702003c: Same as AT+SETCNT=60 1136 1136 1137 1137 1138 - 1139 1139 == 4.3 Enable/Disable uplink Temperature probe ID == 1140 1140 1141 1141 ((( ... ... @@ -1164,7 +1164,6 @@ 1164 1164 * **0xA801** **~-~->** AT+PID=1 1165 1165 1166 1166 1167 - 1168 1168 == 4.4 Set Password == 1169 1169 1170 1170 Feature: Set device password, max 9 digits ... ... @@ -1212,7 +1212,6 @@ 1212 1212 * There is no downlink command to set to Sleep mode. 1213 1213 1214 1214 1215 - 1216 1216 == 4.7 Set system time == 1217 1217 1218 1218 Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]] ... ... @@ -1310,7 +1310,6 @@ 1310 1310 * Example: 0xA301 ~/~/Same as AT+CLRDTA 1311 1311 1312 1312 1313 - 1314 1314 == 4.13 Auto Send None-ACK messages == 1315 1315 1316 1316 (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %) ... ... @@ -1330,7 +1330,6 @@ 1330 1330 * Example: 0x3401 ~/~/Same as AT+PNACKMD=1 1331 1331 1332 1332 1333 - 1334 1334 = 5. Battery & How to replace = 1335 1335 1336 1336 == 5.1 Battery Type == ... ... @@ -1720,7 +1720,7 @@ 1720 1720 [[image:image-20220615154519-3.png||height="672" width="807"]] 1721 1721 1722 1722 1723 -== 6. 6How to use USB-TYPE-C to connect PC to upgrade firmware? ==1812 +== 6.7 How to use USB-TYPE-C to connect PC to upgrade firmware? == 1724 1724 1725 1725 [[image:image-20220623110706-1.png]] 1726 1726 ... ... @@ -1784,7 +1784,6 @@ 1784 1784 * (% style="color:red" %)**E3**(%%): External Temperature Probe 1785 1785 1786 1786 1787 - 1788 1788 = 8. Packing Info = 1789 1789 1790 1790 ... ... @@ -1799,13 +1799,11 @@ 1799 1799 * Device Weight: 120.5g 1800 1800 1801 1801 1802 - 1803 1803 = 9. Reference material = 1804 1804 1805 1805 * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]] 1806 1806 1807 1807 1808 - 1809 1809 = 10. FCC Warning = 1810 1810 1811 1811 This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
- image-20220628150112-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +220.3 KB - Content
- image-20220628150542-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +45.6 KB - Content
- image-20220628150648-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +8.3 KB - Content
- image-20220628150714-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +7.1 KB - Content
- image-20220628151005-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +7.3 KB - Content
- image-20220628151056-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +8.2 KB - Content
- image-20220628151143-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +7.2 KB - Content
- image-20220703111533-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +694.5 KB - Content
- image-20220703111700-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +369.4 KB - Content