Last modified by Xiaoling on 2025/04/24 10:00
<
From version < 10.1 >
edited by Edwin Chen
on 2023/04/09 08:27
To version < 4.1 >
edited by Edwin Chen
on 2023/04/09 00:18
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -76,7 +76,6 @@
76 76  * (% class="mark" %)Resolution: 1 lx
77 77  * (% class="mark" %)Range: 0-65535 lx
78 78  * (% class="mark" %)Operating Range: -40 °C ~~ 85 °C
79 -*
80 80  
81 81  = 2. Connect LHT65N-PIR to IoT Server =
82 82  
... ... @@ -111,7 +111,7 @@
111 111  
112 112  
113 113  (% class="wikigeneratedid" %)
114 -[[image:image-20230409080812-1.png||height="487" width="785"]]
113 +[[image:image-20221224101636-1.png||height="435" width="715"]]
115 115  
116 116  
117 117  Assume the LPS8v2 is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network||_mstvisible="2"]], So it provides network coverage for LHT65N-PIR. Next we need to add the LHT65N-PIR device in TTN V3:
... ... @@ -131,7 +131,7 @@
131 131  Add APP EUI in the application.
132 132  
133 133  
134 -[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522232916-3.png||_mstalt="430495"]]
133 +[[image:image-20220522232916-3.png||_mstalt="430495"]]
135 135  
136 136  
137 137  [[image:image-20220522232932-4.png||_mstalt="430157"]]
... ... @@ -141,9 +141,12 @@
141 141  
142 142  
143 143  
144 -(% style="color:red" %)**Note: LHT65N-PIR use same payload decoder as LHT65.**
143 +(% style="color:red" %)**Note: LHT65N-E5 use same payload decoder as LHT65.**
145 145  
146 146  
146 +[[image:image-20220522233026-6.png||_mstalt="429403"]]
147 +
148 +
147 147  Input APP EUI,  APP KEY and DEV EUI:
148 148  
149 149  
... ... @@ -150,9 +150,9 @@
150 150  [[image:image-20220522233118-7.png||_mstalt="430430"]]
151 151  
152 152  
153 -=== 2.3.2 Step 2: Activate LHT65N-PIR by pressing the ACT button for more than 5 seconds. ===
155 +=== 2.3.2 Step 2: Activate LHT65N-E5 by pressing the ACT button for more than 5 seconds. ===
154 154  
155 -Use ACT button to activate LHT65N-PIR 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.
157 +Use ACT button to activate LHT65N-E5 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.
156 156  [[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]]
157 157  
158 158  
... ... @@ -194,20 +194,20 @@
194 194  [[Ext value>>||anchor="H2.4.6Extvalue"]]
195 195  )))
196 196  
197 -* The First 6 bytes: has fix meanings for every LHT65N-PIR.
198 -* The 7th byte (EXT #): defines the external sensor model. It can be 0x0A for LHT65N-PIR
199 -* The 8^^th^^ byte: Alarm Bit (if this uplink is from periodically or movement)
200 -* The 9^^th^^ ~~ 11^^st^^  byte: Movement Detect Count.
199 +* The First 6 bytes: has fix meanings for every LHT65N-E5.
200 +* The 7th byte (EXT #): defines the external sensor model. It can be 0x05 or 0x09 for LHT65N-E5
201 +* The 8^^th^^ ~~ 9^^th^^ byte: Illuminance. Range: 0-65535 lx.
202 +* The 10th ~~ 11th byte: Reserve, always 0xFFFF
201 201  
202 202  === 2.4.1 Decoder in TTN V3 ===
203 203  
204 204  
205 -When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-PIR decoder in TTNv3 for friendly reading.
207 +When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-E5 decoder in TTNv3 for friendly reading.
206 206  
207 -Below is the position to put the decoder and LHT65N-PIR decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
209 +Below is the position to put the decoder and LHT65N-E5 decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
208 208  
209 209  
210 -[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]]
212 +[[image:image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]]
211 211  
212 212  
213 213  === 2.4.2 BAT-Battery Info ===
... ... @@ -215,37 +215,38 @@
215 215  
216 216  These two bytes of BAT include the battery state and the actually voltage
217 217  
218 -[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220523152839-18.png||_mstalt="457613"]]
220 +[[image:image-20220523152839-18.png||_mstalt="457613"]]
219 219  
220 220  
221 -[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]]
223 +[[image:image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]]
222 222  
223 223  
224 -Check the battery voltage for LHT65N-PIR.
226 +Check the battery voltage for LHT65N-E5.
225 225  
226 -* BAT status=(0xcba4>>14)&0xFF=11(B)，very good
228 +* BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
227 227  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
228 228  
229 229  === 2.4.3 Built-in Temperature ===
230 230  
231 231  
232 -[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-2.png||_mstalt="431756" height="138" width="722"]]
234 +[[image:image-20220522235639-2.png||_mstalt="431756" height="138" width="722"]]
233 233  
234 234  * Temperature:  0x0ABB/100=27.47℃
235 235  
236 -[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-3.png||_mstalt="432120"]]
238 +[[image:image-20220522235639-3.png||_mstalt="432120"]]
237 237  
238 238  * Temperature:  (0xF5C6-65536)/100=-26.18℃
239 239  
240 240  === 2.4.4 Built-in Humidity ===
241 241  
242 -[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-4.png||_mstalt="432484" height="138" width="722"]]
243 243  
245 +[[image:image-20220522235639-4.png||_mstalt="432484" height="138" width="722"]]
246 +
244 244  * Humidity:    0x025C/10=60.4%
245 245  
246 246  === 2.4.5 Ext value ===
247 247  
248 -==== 2.4.5.1 Ext~=0x0A, PIR Sensor ====
251 +==== 2.4.5.1 Ext~=0x05, Illuminance Sensor ====
249 249  
250 250  
251 251  [[image:image-20221224161634-2.png||height="138" width="851"]]
... ... @@ -262,16 +262,97 @@
262 262   The last 2 bytes of data are meaningless
263 263  
264 264  
268 +
269 +==== 2.4.5.2 Ext~=0x85, E5 sensor with Unix Timestamp ====
270 +
271 +
272 +(((
273 +Timestamp mode is designed for LHT65N-E5 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:
274 +)))
275 +
276 +(((
277 +
278 +)))
279 +
280 +(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:535px" %)
281 +|=(% style="width: 88px;" %)(((
282 +**Size(bytes)**
283 +)))|=(% style="width: 93px;" %)(((
284 +**2**
285 +)))|=(% style="width: 94px;" %)(((
286 +**2**
287 +)))|=(% style="width: 117px;" %)(((
288 +**2**
289 +)))|=(% style="width: 54px;" %)(((
290 +**1**
291 +)))|=(% style="width: 79px;" %)(((
292 +**4**
293 +)))
294 +|(% style="width:88px" %)(((
295 +**Value**
296 +)))|(% style="width:93px" %)(((
297 +[[External temperature>>||anchor="H4.2SetExternalSensorMode"]]
298 +)))|(% style="width:94px" %)(((
299 +[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]]
300 +)))|(% style="width:117px" %)(((
301 +BAT Status &
302 +Illumination
303 +)))|(% style="width:54px" %)(((
304 +Status & Ext
305 +)))|(% style="width:79px" %)(((
306 +[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]]
307 +)))
308 +
309 +* **Battery status & Built-in Humidity**
310 +
311 +(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:461px" %)
312 +|=(% style="width: 67px;" %)Bit(bit)|=(% style="width: 256px;" %)[15:14]|=(% style="width: 132px;" %)[11:0]
313 +|(% style="width:67px" %)Value|(% style="width:256px" %)(((
314 +BAT Status
315 +00(b): Ultra Low ( BAT <= 2.50v)
316 +01(b): Low  (2.50v <=BAT <= 2.55v)
317 +10(b): OK   (2.55v <= BAT <=2.65v)
318 +11(b): Good   (BAT >= 2.65v)
319 +)))|(% style="width:132px" %)(((
320 +Illumination
321 +)))
322 +
323 +* **Status & Ext Byte**
324 +
325 +(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:500px" %)
326 +|=(% scope="row" 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]**
327 +|=(% 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)
328 +
329 +* (% style="color:blue" %)**Poll Message Flag**:(%%)  1: This message is a poll message reply, 0: means this is a normal uplink.
330 +* (% style="color:blue" %)**Sync time OK**: (%%) 1: Set time ok，0: N/A. After time SYNC request is sent, LHT65N-E5 will set this bit to 0 until got the time stamp from the application server.
331 +* (% style="color:blue" %)**Unix Time Request**:(%%)  1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N-E5 will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this)
332 +
265 265  == 2.5 Show data on Datacake ==
266 266  
335 +
336 +(((
267 267  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:
338 +)))
268 268  
340 +(((
341 +
342 +)))
343 +
344 +(((
269 269  (% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the LoRaWAN network.
346 +)))
270 270  
348 +(((
271 271  (% 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.
350 +)))
272 272  
352 +
353 +
354 +(((
273 273  Add Datacake:
356 +)))
274 274  
358 +
275 275  [[image:image-20220523000825-7.png||_mstalt="429884" height="262" width="583"]]
276 276  
277 277  
... ... @@ -291,11 +291,239 @@
291 291  [[image:image-20221224161957-6.png||height="306" width="852"]]
292 292  
293 293  
378 +== 2.6 Datalog Feature ==
294 294  
380 +
381 +(((
382 +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-E5 will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N-E5.
383 +)))
384 +
385 +
386 +=== 2.6.1 Ways to get datalog via LoRaWAN ===
387 +
388 +
389 +There are two methods:
390 +
391 +(% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range.
392 +
393 +
394 +(% style="color:blue" %)**Method 2: **(%%)Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N-E5 will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N-E5 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.
395 +
396 +
397 +(% style="color:red" %)**Note for method 2:**
398 +
399 +* a) LHT65N-E5 will do an ACK check for data records sending to make sure every data arrive server.
400 +* b) LHT65N-E5 will send data in **CONFIRMED Mode** when PNACKMD=1, but LHT65N-E5 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-E5 gets a ACK, LHT65N-E5 will consider there is a network connection and resend all NONE-ACK Message.
401 +
402 +Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
403 +
404 +
405 +[[image:image-20220703111700-2.png||_mstalt="426244" height="381" width="1119"]]
406 +
407 +
408 +=== 2.6.2 Unix TimeStamp ===
409 +
410 +
411 +LHT65N-E5 uses Unix TimeStamp format based on
412 +
413 +
414 +[[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]]
415 +
416 +
417 +
418 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
419 +
420 +Below is the converter example
421 +
422 +[[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]]
423 +
424 +
425 +So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
426 +
427 +
428 +=== 2.6.3 Set Device Time ===
429 +
430 +
431 +(((
432 +(% style="color:blue" %)**There are two ways to set device's time:**
433 +)))
434 +
435 +(((
436 +**1.  Through LoRaWAN MAC Command (Default settings)**
437 +)))
438 +
439 +(((
440 +User need to set SYNCMOD=1 to enable sync time via MAC command.
441 +)))
442 +
443 +(((
444 +Once LHT65N-E5 Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LHT65N-E5. If LHT65N-E5 fails to get the time from the server, LHT65N-E5 will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
445 +)))
446 +
447 +(((
448 +(% 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.**
449 +)))
450 +
451 +
452 +(((
453 +**2. Manually Set Time**
454 +)))
455 +
456 +(((
457 +User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
458 +)))
459 +
460 +
461 +=== 2.6.4 Poll sensor value ===
462 +
463 +
464 +User can poll sensor value based on timestamps from the server. Below is the downlink command.
465 +
466 +[[image:image-20220523152302-15.png||_mstalt="451581"]]
467 +
468 +
469 +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.
470 +
471 +For example, downlink command (% _mstmutation="1" %)**31 5FC5F350 5FC6 0160 05**(%%)
472 +
473 +Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data
474 +
475 +Uplink Internal =5s，means LHT65N-E5 will send one packet every 5s. range 5~~255s.
476 +
477 +
478 +=== 2.6.5 Datalog Uplink payload ===
479 +
480 +
481 +The Datalog poll reply uplink will use below payload format.
482 +
483 +**Retrieval data payload:**
484 +
485 +(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:480px" %)
486 +|=(% style="width: 60px;" %)(((
487 +**Size(bytes)**
488 +)))|=(% style="width: 90px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 70px;" %)**2**|=(% style="width: 100px;" %)**1**|=(% style="width: 70px;" %)**4**
489 +|(% 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"]]
490 +
491 +**Poll message flag & Ext:**
492 +
493 +[[image:image-20221006192726-1.png||_mstalt="430508" height="112" width="754"]]
494 +
495 +(% 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)
496 +
497 +(% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply.
498 +
499 +* Poll Message Flag is set to 1.
500 +
501 +* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
502 +
503 +For example, in US915 band, the max payload for different DR is:
504 +
505 +(% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data
506 +
507 +(% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
508 +
509 +(% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data
510 +
511 +(% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data.
512 +
513 +If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0   
514 +
515 +
516 +**Example:**
517 +
518 +If LHT65N-E5 has below data inside Flash:
519 +
520 +[[image:image-20220523144455-1.png||_mstalt="430040" height="335" width="735"]]
521 +
522 +
523 +If user sends below downlink command: (% style="background-color:yellow" %)3160065F9760066DA705
524 +
525 +Where : Start time: 60065F97 = time 21/1/19 04:27:03
526 +
527 + Stop time: 60066DA7= time 21/1/19 05:27:03
528 +
529 +
530 +**LHT65N-E5 will uplink this payload.**
531 +
532 +[[image:image-20220523001219-13.png||_mstalt="451204" height="421" style="text-align:left" width="727"]]
533 +
534 +
535 +__**7FFF089801464160065F97**__ **__7FFF__ __088E__ __014B__ __41__ __60066009__** 7FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
536 +
537 +Where the first 11 bytes is for the first entry:
538 +
539 +7FFF089801464160065F97
540 +
541 +Ext sensor data=0x7FFF/100=327.67
542 +
543 +Temp=0x088E/100=22.00
544 +
545 +Hum=0x014B/10=32.6
546 +
547 +poll message flag & Ext=0x41,means reply data,Ext=1
548 +
549 +Unix time is 0x60066009=1611030423s=21/1/19 04:27:03
550 +
551 +
552 +== 2.7 Alarm Mode ==
553 +
554 +(((
555 +
556 +
557 +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.
558 +)))
559 +
560 +(((
561 +(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.**
562 +
563 +
564 +)))
565 +
566 +=== 2.7.1 ALARM MODE ===
567 +
568 +
569 +(% class="box infomessage" %)
570 +(((
571 +(((
572 +**AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor)
573 +)))
574 +
575 +(((
576 +**AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
577 +)))
578 +
579 +(((
580 +**AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
581 +)))
582 +
583 +(((
584 +(% _mstmutation="1" %)**AT+ARTEMP=？ **(%%):  Gets the alarm range of the internal temperature sensor(% style="display:none" %)
585 +)))
586 +
587 +(((
588 +**AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
589 +)))
590 +)))
591 +
592 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
593 +
594 +Total bytes: 8 bytes
595 +
596 +**Example:**AA0100010001003C
597 +
598 +WMOD=01
599 +
600 +CITEMP=0001
601 +
602 +TEMPlow=0001
603 +
604 +TEMPhigh=003C
605 +
606 +
295 295  == 2.8 LED Indicator ==
296 296  
297 297  
298 -The LHT65N-PIR has a triple color LED which for easy showing different stage .
610 +The LHT65 has a triple color LED which for easy showing different stage .
299 299  
300 300  While user press ACT button, the LED will work as per LED status with ACT button.
301 301  
... ... @@ -326,13 +326,19 @@
326 326  Use for AT Command
327 327  )))
328 328  * (((
329 -Update firmware for LHT65N-PIR
641 +Update firmware for LHT65N-E5
330 330  )))
643 +* (((
644 +Exposed All pins from the LHT65N Type-C connector.
331 331  
646 +
647 +
648 +)))
649 +
332 332  [[image:image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]]
333 333  
334 334  
335 -= 4. Configure LHT65N-PIR via AT command or LoRaWAN downlink =
653 += 4. Configure LHT65N-E5 via AT command or LoRaWAN downlink =
336 336  
337 337  
338 338  (((
... ... @@ -443,6 +443,127 @@
443 443  
444 444  * There is no downlink command to set to Sleep mode.
445 445  
764 +== 4.4 Set system time ==
765 +
766 +
767 +Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
768 +
769 +
770 +(% style="color:#4f81bd" %)**AT Command:**
771 +
772 +[[image:image-20220523151253-8.png||_mstalt="430677"]]
773 +
774 +
775 +(% style="color:#4f81bd" %)**Downlink Command:**
776 +
777 +0x306007806000  ~/~/  Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
778 +
779 +
780 +== 4.5 Set Time Sync Mode ==
781 +
782 +
783 +(((
784 +Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
785 +)))
786 +
787 +(((
788 +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.
789 +
790 +
791 +)))
792 +
793 +(% style="color:#4f81bd" %)**AT Command:**
794 +
795 +[[image:image-20220523151336-9.png||_mstalt="431717"]]
796 +
797 +
798 +(% style="color:#4f81bd" %)**Downlink Command:**
799 +
800 +0x28 01  ~/~/  Same As AT+SYNCMOD=1
801 +0x28 00  ~/~/  Same As AT+SYNCMOD=0
802 +
803 +
804 +== 4.6 Set Time Sync Interval ==
805 +
806 +
807 +Feature: Define System time sync interval. SYNCTDC default value: 10 days.
808 +
809 +
810 +(% style="color:#4f81bd" %)**AT Command:**
811 +
812 +[[image:image-20220523151411-10.png||_mstalt="449696"]]
813 +
814 +
815 +(% style="color:#4f81bd" %)**Downlink Command:**
816 +
817 +**0x29 0A**  ~/~/ Same as AT+SYNCTDC=0x0A
818 +
819 +
820 +== 4.7 Print data entries base on page. ==
821 +
822 +
823 +Feature: Print the sector data from start page to stop page (max is 416 pages).
824 +
825 +
826 +(% style="color:#4f81bd" %)**AT Command: AT+PDTA**
827 +
828 +[[image:image-20220523151450-11.png||_mstalt="451035"]]
829 +
830 +
831 +(% style="color:#4f81bd" %)**Downlink Command:**
832 +
833 +No downlink commands for feature
834 +
835 +
836 +== 4.8 Print last few data entries. ==
837 +
838 +
839 +Feature: Print the last few data entries
840 +
841 +
842 +(% style="color:#4f81bd" %)**AT Command: AT+PLDTA**
843 +
844 +[[image:image-20220523151524-12.png||_mstalt="452101"]]
845 +
846 +
847 +(% style="color:#4f81bd" %)**Downlink Command:**
848 +
849 +No downlink commands for feature
850 +
851 +
852 +== 4.9 Clear Flash Record ==
853 +
854 +
855 +Feature: Clear flash storage for data log feature.
856 +
857 +
858 +(% style="color:#4f81bd" %)**AT Command: AT+CLRDTA**
859 +
860 +[[image:image-20220523151556-13.png||_mstalt="454129"]]
861 +
862 +
863 +(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
864 +
865 +* Example: 0xA301  ~/~/  Same as AT+CLRDTA
866 +
867 +== 4.10 Auto Send None-ACK messages ==
868 +
869 +
870 +Feature: LHT65N-E5 will wait for ACK for each uplink, If LHT65N-E5 doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LHT65N-E5 keeps sending messages in normal periodically. Once LHT65N-E5 gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
871 +
872 +
873 +(% style="color:#4f81bd" %)**AT Command: AT+PNACKMD**
874 +
875 +The default factory setting is 0
876 +
877 +(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:367px" %)
878 +|=(% style="width: 158px;" %)**Command Example**|=(% style="width: 118px;" %)**Function**|=(% style="width: 87px;" %)**Response**
879 +|(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK
880 +
881 +(% style="color:#4f81bd" %)**Downlink Command: 0x34**
882 +
883 +* Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
884 +
446 446  = 5. Battery & How to replace =
447 447  
448 448  == 5.1 Battery Type ==
image-20230409080812-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -249.6 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0