Skip to Content
Last modified by Xiaoling on 2023/07/18 10:12
From version 170.28
edited by Xiaoling
on 2022/06/22 11:17
Change comment: There is no comment for this version
To version 170.29
edited by Xiaoling
on 2022/06/22 11:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -59,7 +59,6 @@
59 59  * Datalog feature
60 60  
61 61  
62 -
63 63  == 1.3 Specification ==
64 64  
65 65  
... ... @@ -85,7 +85,6 @@
85 85  * Operating Range: -55 °C ~~ 125 °C
86 86  
87 87  
88 -
89 89  = 2. Connect LHT65N to IoT Server =
90 90  
91 91  == 2.1 How does LHT65N work? ==
... ... @@ -267,6 +267,10 @@
267 267  * The 7th byte (EXT #): defines the external sensor model.
268 268  * 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.)
269 269  
268 +
269 +
270 +
271 +
270 270  === 2.4.1 Decoder in TTN V3 ===
271 271  
272 272  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.
... ... @@ -297,6 +297,10 @@
297 297  * BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
298 298  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
299 299  
302 +
303 +
304 +
305 +
300 300  === 2.4.3 Built-in Temperature ===
301 301  
302 302  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
... ... @@ -307,6 +307,10 @@
307 307  
308 308  * Temperature:  (0xF5C6-65536)/100=-26.18℃
309 309  
316 +
317 +
318 +
319 +
310 310  === 2.4.4 Built-in Humidity ===
311 311  
312 312  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
... ... @@ -313,6 +313,10 @@
313 313  
314 314  * Humidity:    0x025C/10=60.4%
315 315  
326 +
327 +
328 +
329 +
316 316  === 2.4.5 Ext # ===
317 317  
318 318  Bytes for External Sensor:
... ... @@ -465,6 +465,10 @@
465 465  * 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.
466 466  * 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)
467 467  
482 +
483 +
484 +
485 +
468 468  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
469 469  
470 470  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
... ... @@ -539,6 +539,10 @@
539 539  1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
540 540  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.
541 541  
560 +
561 +
562 +
563 +
542 542  === 2.6.2 Unix TimeStamp ===
543 543  
544 544  
... ... @@ -561,20 +561,37 @@
561 561  
562 562  === 2.6.3 Set Device Time ===
563 563  
586 +(((
564 564  There are two ways to set device's time:
588 +)))
565 565  
590 +(((
566 566  **~1. Through LoRaWAN MAC Command (Default settings)**
592 +)))
567 567  
594 +(((
568 568  User need to set SYNCMOD=1 to enable sync time via MAC command.
596 +)))
569 569  
598 +(((
570 570  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).
600 +)))
571 571  
602 +(((
572 572  (% 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.
604 +)))
573 573  
606 +(((
607 +
608 +)))
574 574  
610 +(((
575 575  **2. Manually Set Time**
612 +)))
576 576  
614 +(((
577 577  User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
616 +)))
578 578  
579 579  
580 580