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

Summary

Details

Page properties
Content
... ... @@ -59,6 +59,7 @@
59 59  * Datalog feature
60 60  
61 61  
62 +
62 62  == 1.3 Specification ==
63 63  
64 64  
... ... @@ -84,6 +84,7 @@
84 84  * Operating Range: -55 °C ~~ 125 °C
85 85  
86 86  
88 +
87 87  = 2. Connect LHT65N to IoT Server =
88 88  
89 89  == 2.1 How does LHT65N work? ==
... ... @@ -265,10 +265,6 @@
265 265  * The 7th byte (EXT #): defines the external sensor model.
266 266  * 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.)
267 267  
268 -
269 -
270 -
271 -
272 272  === 2.4.1 Decoder in TTN V3 ===
273 273  
274 274  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.
... ... @@ -299,10 +299,6 @@
299 299  * BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
300 300  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
301 301  
302 -
303 -
304 -
305 -
306 306  === 2.4.3 Built-in Temperature ===
307 307  
308 308  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
... ... @@ -313,10 +313,6 @@
313 313  
314 314  * Temperature:  (0xF5C6-65536)/100=-26.18℃
315 315  
316 -
317 -
318 -
319 -
320 320  === 2.4.4 Built-in Humidity ===
321 321  
322 322  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
... ... @@ -323,10 +323,6 @@
323 323  
324 324  * Humidity:    0x025C/10=60.4%
325 325  
326 -
327 -
328 -
329 -
330 330  === 2.4.5 Ext # ===
331 331  
332 332  Bytes for External Sensor:
... ... @@ -479,10 +479,6 @@
479 479  * 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.
480 480  * 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)
481 481  
482 -
483 -
484 -
485 -
486 486  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
487 487  
488 488  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
... ... @@ -557,10 +557,6 @@
557 557  1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
558 558  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.
559 559  
560 -
561 -
562 -
563 -
564 564  === 2.6.2 Unix TimeStamp ===
565 565  
566 566  
... ... @@ -583,37 +583,20 @@
583 583  
584 584  === 2.6.3 Set Device Time ===
585 585  
586 -(((
587 587  There are two ways to set device's time:
588 -)))
589 589  
590 -(((
591 591  **~1. Through LoRaWAN MAC Command (Default settings)**
592 -)))
593 593  
594 -(((
595 595  User need to set SYNCMOD=1 to enable sync time via MAC command.
596 -)))
597 597  
598 -(((
599 599  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 -)))
601 601  
602 -(((
603 603  (% 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 -)))
605 605  
606 -(((
607 -
608 -)))
609 609  
610 -(((
611 611  **2. Manually Set Time**
612 -)))
613 613  
614 -(((
615 615  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 -)))
617 617  
618 618  
619 619