Last modified by Xiaoling on 2023/07/18 10:12

From version 170.25
edited by Xiaoling
on 2022/06/22 11:16
Change comment: There is no comment for this version
To version 189.11
edited by Xiaoling
on 2022/08/08 16:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220613162008-1.png||_mstalt="428142" height="579" 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
... ... @@ -58,9 +58,6 @@
58 58  * Tri-color LED to indicate working status
59 59  * Datalog feature
60 60  
61 -
62 -
63 -
64 64  == 1.3 Specification ==
65 65  
66 66  
... ... @@ -89,19 +89,34 @@
89 89  
90 90  == 2.1 How does LHT65N work? ==
91 91  
90 +
91 +(((
92 92  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.
93 +)))
93 93  
95 +(((
94 94  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.
97 +)))
95 95  
96 96  
100 +
97 97  == 2.2 How to Activate LHT65N? ==
98 98  
103 +
104 +(((
99 99  The LHT65N has two working modes:
106 +)))
100 100  
101 -* (% 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.
102 -* (% 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. 
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 +)))
103 103  
115 +(((
104 104  The LHT65N is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
117 +)))
105 105  
106 106  
107 107  [[image:image-20220515123819-1.png||_mstalt="430742" _mstvisible="3" height="379" width="317"]]
... ... @@ -112,6 +112,7 @@
112 112  
113 113  == 2.3 Example to join LoRaWAN network ==
114 114  
128 +
115 115  (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
116 116  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.
117 117  
... ... @@ -127,6 +127,7 @@
127 127  
128 128  === 2.3.1 Step 1: Create Device n TTN ===
129 129  
144 +
130 130  (((
131 131  Create a device in TTN V3 with the OTAA keys from LHT65N.
132 132  )))
... ... @@ -151,9 +151,10 @@
151 151  [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
152 152  
153 153  
154 -Note: LHT65N use same payload as LHT65.
155 155  
170 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
156 156  
172 +
157 157  [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
158 158  
159 159  
... ... @@ -167,6 +167,7 @@
167 167  
168 168  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
169 169  
186 +
170 170  (((
171 171  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.
172 172  )))
... ... @@ -178,6 +178,7 @@
178 178  
179 179  == 2.4 Uplink Payload ==
180 180  
198 +
181 181  (((
182 182  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.
183 183  )))
... ... @@ -252,12 +252,11 @@
252 252  
253 253  * The First 6 bytes: has fix meanings for every LHT65N.
254 254  * The 7th byte (EXT #): defines the external sensor model.
255 -* 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 wont be these four bytes.)
273 +* 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.)
256 256  
257 -
258 -
259 259  === 2.4.1 Decoder in TTN V3 ===
260 260  
277 +
261 261  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.
262 262  
263 263  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -273,6 +273,7 @@
273 273  
274 274  === 2.4.2 BAT-Battery Info ===
275 275  
293 +
276 276  These two bytes of BAT include the battery state and the actually voltage
277 277  
278 278  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -286,9 +286,9 @@
286 286  * BAT status=(0Xcba4>>14)&0xFF=11(B),very good
287 287  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
288 288  
289 -
290 290  === 2.4.3 Built-in Temperature ===
291 291  
309 +
292 292  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
293 293  
294 294  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -299,6 +299,7 @@
299 299  
300 300  === 2.4.4 Built-in Humidity ===
301 301  
320 +
302 302  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
303 303  
304 304  * Humidity:    0x025C/10=60.4%
... ... @@ -305,6 +305,7 @@
305 305  
306 306  === 2.4.5 Ext # ===
307 307  
327 +
308 308  Bytes for External Sensor:
309 309  
310 310  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -336,6 +336,7 @@
336 336  
337 337  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
338 338  
359 +
339 339  (((
340 340  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:
341 341  )))
... ... @@ -449,15 +449,17 @@
449 449  
450 450  * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
451 451  
452 -[[image:image-20220523152434-16.png||_mstalt="453921" _mstvisible="3"]]
473 +(% border="1" cellspacing="8" style="background-color:#ffffcc; color:green; width:520px" %)
474 +|(% 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]**
475 +|(% 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)
453 453  
454 -* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
455 -* 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.
456 -* 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 +* (% style="color:blue" %)**Poll Message Flag**:(%%)  1: This message is a poll message reply, 0: means this is a normal uplink.
478 +* (% 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.
479 +* (% 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)
457 457  
458 -
459 459  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
460 460  
483 +
461 461  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
462 462  
463 463  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -466,10 +466,46 @@
466 466  
467 467  AT+EXT=6,timeout  (% _msthash="506085" _msttexthash="8782189" _mstvisible="3" style="color:red" %)Time to power this sensor, from 0 ~~ 65535ms
468 468  
492 +For example:
469 469  
494 +AT+EXT=6,1000 will power this sensor for 1000ms before sampling the ADC value.
470 470  
496 +
497 +Or use **downlink command A2** to set the same.
498 +
499 +The measuring range of the node is only about 0.1V to 1.1V The voltage resolution is about 0.24mv.
500 +
501 +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.
502 +
503 +[[image:image-20220628150112-1.png||height="241" width="285"]]
504 +
505 +
506 +When ADC_IN1 pin is connected to GND or suspended, ADC value is 0
507 +
508 +[[image:image-20220628150714-4.png]]
509 +
510 +
511 +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.
512 +
513 +1) The minimum range is about 0.1V. Each chip has internal calibration, so this value is close to 0.1V
514 +
515 +[[image:image-20220628151005-5.png]]
516 +
517 +
518 +2) The maximum range is about 1.1V. Each chip has internal calibration, so this value is close to 1.1v
519 +
520 +[[image:image-20220628151056-6.png]]
521 +
522 +
523 +3) Within range
524 +
525 +[[image:image-20220628151143-7.png]]
526 +
527 +
528 +
471 471  == 2.5 Show data on Datacake ==
472 472  
531 +
473 473  (((
474 474  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:
475 475  )))
... ... @@ -517,6 +517,7 @@
517 517  
518 518  == 2.6 Datalog Feature ==
519 519  
579 +
520 520  (((
521 521  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.
522 522  )))
... ... @@ -525,13 +525,17 @@
525 525  
526 526  === 2.6.1 Ways to get datalog via LoRaWAN ===
527 527  
588 +
528 528  There are two methods:
529 529  
530 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
531 -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.
591 +1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range.
592 +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.
532 532  
594 +Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
533 533  
596 +[[image:image-20220703111700-2.png||height="381" width="1119"]]
534 534  
598 +
535 535  === 2.6.2 Unix TimeStamp ===
536 536  
537 537  
... ... @@ -554,25 +554,44 @@
554 554  
555 555  === 2.6.3 Set Device Time ===
556 556  
621 +
622 +(((
557 557  There are two ways to set device's time:
624 +)))
558 558  
626 +(((
559 559  **~1. Through LoRaWAN MAC Command (Default settings)**
628 +)))
560 560  
630 +(((
561 561  User need to set SYNCMOD=1 to enable sync time via MAC command.
632 +)))
562 562  
634 +(((
563 563  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).
636 +)))
564 564  
565 -(% 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.
638 +(((
639 +(% 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.**
640 +)))
566 566  
642 +(((
643 +
644 +)))
567 567  
646 +(((
568 568  **2. Manually Set Time**
648 +)))
569 569  
650 +(((
570 570  User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
652 +)))
571 571  
572 572  
573 573  
574 574  === 2.6.4 Poll sensor value ===
575 575  
658 +
576 576  User can poll sensor value based on timestamps from the server. Below is the downlink command.
577 577  
578 578  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -590,6 +590,7 @@
590 590  
591 591  === 2.6.5 Datalog Uplink payload ===
592 592  
676 +
593 593  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
594 594  The Datalog poll reply uplink will use below payload format.
595 595  
... ... @@ -596,6 +596,9 @@
596 596  (% _mstvisible="1" %)
597 597  (((
598 598  (% _mstvisible="2" %)
683 +
684 +
685 +(% _mstvisible="2" %)
599 599  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
600 600  )))
601 601  
... ... @@ -734,9 +734,11 @@
734 734  (% _mstvisible="2" %)
735 735  (((
736 736  (% _msthash="736723" _msttexthash="2005003" _mstvisible="3" %)
824 +(((
737 737  Poll Message Flag: 1: This message is a poll message reply.
738 738  )))
739 739  )))
828 +)))
740 740  
741 741  (% _mstvisible="1" %)
742 742  * (% _mstvisible="3" %)
... ... @@ -744,17 +744,21 @@
744 744  (% _mstvisible="4" %)
745 745  (((
746 746  (% _msthash="1197157" _msttexthash="561548" _mstvisible="5" %)
836 +(((
747 747  Poll Message Flag is set to 1.
748 748  )))
749 749  )))
840 +)))
750 750  * (% _mstvisible="3" %)
751 751  (((
752 752  (% _mstvisible="4" %)
753 753  (((
754 754  (% _msthash="1197158" _msttexthash="9284964" _mstvisible="5" %)
846 +(((
755 755  Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
756 756  )))
757 757  )))
850 +)))
758 758  
759 759  (% _mstvisible="1" %)
760 760  (((
... ... @@ -761,12 +761,16 @@
761 761  (% _mstvisible="2" %)
762 762  (((
763 763  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
857 +(((
764 764  
859 +)))
765 765  
766 766  (% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
862 +(((
767 767  For example, in US915 band, the max payload for different DR is:
768 768  )))
769 769  )))
866 +)))
770 770  
771 771  (% _mstvisible="1" %)
772 772  (((
... ... @@ -773,9 +773,11 @@
773 773  (% _mstvisible="2" %)
774 774  (((
775 775  (% _msthash="736725" _msttexthash="1065532" _mstvisible="3" %)
873 +(((
776 776  a) DR0: max is 11 bytes so one entry of data
777 777  )))
778 778  )))
877 +)))
779 779  
780 780  (% _mstvisible="1" %)
781 781  (((
... ... @@ -782,9 +782,11 @@
782 782  (% _mstvisible="2" %)
783 783  (((
784 784  (% _msthash="736726" _msttexthash="3265665" _mstvisible="3" %)
884 +(((
785 785  b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
786 786  )))
787 787  )))
888 +)))
788 788  
789 789  (% _mstvisible="1" %)
790 790  (((
... ... @@ -791,9 +791,11 @@
791 791  (% _mstvisible="2" %)
792 792  (((
793 793  (% _msthash="736727" _msttexthash="1454115" _mstvisible="3" style="text-align: left;" %)
895 +(((
794 794  c) DR2: total payload includes 11 entries of data
795 795  )))
796 796  )))
899 +)))
797 797  
798 798  (% _mstvisible="1" %)
799 799  (((
... ... @@ -800,9 +800,11 @@
800 800  (% _mstvisible="2" %)
801 801  (((
802 802  (% _msthash="736728" _msttexthash="1483924" _mstvisible="3" style="text-align: left;" %)
906 +(((
803 803  d) DR3: total payload includes 22 entries of data.
804 804  )))
805 805  )))
910 +)))
806 806  
807 807  (% _mstvisible="1" %)
808 808  (((
... ... @@ -809,9 +809,11 @@
809 809  (% _mstvisible="2" %)
810 810  (((
811 811  (% _msthash="736729" _msttexthash="5848349" _mstvisible="3" style="text-align: left;" %)
917 +(((
812 812  If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0   
813 813  )))
814 814  )))
921 +)))
815 815  
816 816  
817 817  (% _mstvisible="1" style="text-align: left;" %)
... ... @@ -838,7 +838,7 @@
838 838  (% _mstvisible="1" %)
839 839  (((
840 840  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
841 - Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03
948 + Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03
842 842  )))
843 843  
844 844  (% _mstvisible="1" %)
... ... @@ -857,57 +857,106 @@
857 857  [[image:image-20220523001219-13.png||_mstalt="451204" _mstvisible="3" height="421" style="text-align:left" width="727"]]
858 858  
859 859  (% _msthash="315271" _msttexthash="12012546" _mstvisible="1" style="text-align: left;" %)
967 +(((
860 860  7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
969 +)))
861 861  
862 862  (% _msthash="315237" _msttexthash="1385839" %)
972 +(((
863 863  Where the first 11 bytes is for the first entry:
974 +)))
864 864  
865 865  (% _msthash="315238" _msttexthash="274846" %)
977 +(((
866 866  7FFF089801464160065F97
979 +)))
867 867  
868 868  (% _msthash="315239" _msttexthash="617435" %)
982 +(((
869 869  Ext sensor data=0x7FFF/100=327.67
984 +)))
870 870  
871 871  (% _msthash="315240" _msttexthash="270543" %)
987 +(((
872 872  Temp=0x0898/100=22.00
989 +)))
873 873  
874 874  (% _msthash="315241" _msttexthash="211783" %)
992 +(((
875 875  Hum=0x0146/10=32.6
994 +)))
876 876  
877 877  (% _msthash="315242" _msttexthash="1569776" %)
997 +(((
878 878  poll message flag & Ext=0x41,means reply data,Ext=1
999 +)))
879 879  
880 880  (% _msthash="315243" _msttexthash="1120509" %)
1002 +(((
881 881  Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
1004 +)))
882 882  
883 883  
884 884  
885 885  == 2.7 Alarm Mode ==
886 886  
1010 +
1011 +(((
887 887  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.
1013 +)))
888 888  
889 -(% style="color:red" %)Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.
1015 +(((
1016 +(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.**
890 890  
1018 +
1019 +)))
1020 +
1021 +(((
891 891  **AT COMMAND FOR ALARM MODE:**
1023 +)))
892 892  
893 893  (% _mstvisible="1" class="box infomessage" %)
894 894  (((
1027 +(((
895 895  **AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled)
1029 +)))
896 896  
1031 +(((
897 897  **AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
1033 +)))
898 898  
1035 +(((
899 899  **AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
1037 +)))
900 900  
1039 +(((
901 901  **AT+ARTEMP=? **:  Gets the alarm range of the internal temperature sensor(% _mstvisible="3" style="display:none" %)
1041 +)))
902 902  
1043 +(((
903 903  **AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
904 904  )))
1046 +)))
905 905  
1048 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
906 906  
1050 +Total bytes: 8 bytes
907 907  
1052 +**Example:**AA0100010001003C
908 908  
1054 +WMOD=01
1055 +
1056 +CITEMP=0001
1057 +
1058 +TEMPlow=0001
1059 +
1060 +TEMPhigh=003C
1061 +
1062 +
1063 +
909 909  == 2.8 LED Indicator ==
910 910  
1066 +
911 911  The LHT65 has a triple color LED which for easy showing different stage .
912 912  
913 913  While user press ACT button, the LED will work as per LED status with ACT button.
... ... @@ -915,14 +915,13 @@
915 915  In a normal working state:
916 916  
917 917  * For each uplink, the BLUE LED or RED LED will blink once.
918 - BLUE LED when external sensor is connected.
1074 +BLUE LED when external sensor is connected.
919 919  * RED LED when external sensor is not connected
920 920  * For each success downlink, the PURPLE LED will blink once
921 921  
922 -
923 -
924 924  == 2.9 installation ==
925 925  
1080 +
926 926  (% _mstvisible="1" %)
927 927  [[image:image-20220516231650-1.png||_mstalt="428597" _mstvisible="3" height="436" width="428"]]
928 928  
... ... @@ -932,10 +932,31 @@
932 932  
933 933  == 3.1 E2 Extension Cable ==
934 934  
1090 +
935 935  [[image:image-20220619092222-1.png||height="182" width="188"]][[image:image-20220619092313-2.png||height="182" width="173"]]
936 936  
937 -1m long breakout cable for LHT65N
938 938  
1094 +**1m long breakout cable for LHT65N. Features:**
1095 +
1096 +* (((
1097 +Use for AT Command, works for both LHT52/LHT65N
1098 +)))
1099 +* (((
1100 +Update firmware for LHT65N, works for both LHT52/LHT65N
1101 +)))
1102 +* (((
1103 +Supports ADC mode to monitor external ADC
1104 +)))
1105 +* (((
1106 +Supports Interrupt mode
1107 +)))
1108 +* (((
1109 +Exposed All pins from the LHT65N Type-C connector.
1110 +
1111 +
1112 +
1113 +)))
1114 +
939 939  [[image:image-20220619092421-3.png||height="371" width="529"]]
940 940  
941 941  
... ... @@ -955,36 +955,60 @@
955 955  * Operating Range: -40 ~~ 125 °C
956 956  * Working voltage 2.35v ~~ 5v
957 957  
958 -
959 -
960 960  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
961 961  
1136 +
1137 +(((
962 962  Use can configure LHT65N via AT Command or LoRaWAN Downlink.
1139 +)))
963 963  
964 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
1141 +* (((
1142 +AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
1143 +)))
965 965  
966 -* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
1145 +* (((
1146 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
1147 +)))
967 967  
1149 +(((
968 968  There are two kinds of commands to configure LHT65N, they are:
1151 +)))
969 969  
970 -* (% style="color:#4f81bd" %)**General Commands**.
1153 +* (((
1154 +(% style="color:#4f81bd" %)**General Commands**.
1155 +)))
971 971  
1157 +(((
972 972  These commands are to configure:
1159 +)))
973 973  
974 -1. General system settings like: uplink interval.
975 -1. LoRaWAN protocol & radio-related commands.
1161 +1. (((
1162 +General system settings like: uplink interval.
1163 +)))
1164 +1. (((
1165 +LoRaWAN protocol & radio-related commands.
1166 +)))
976 976  
1168 +(((
977 977  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]]
1170 +)))
978 978  
979 -* (% style="color:#4f81bd" %)**Commands special design for LHT65N**
1172 +* (((
1173 +(% style="color:#4f81bd" %)**Commands special design for LHT65N**
1174 +)))
980 980  
1176 +(((
981 981  These commands are only valid for LHT65N, as below:
1178 +)))
982 982  
983 983  
1181 +
984 984  == 4.1 Set Transmit Interval Time ==
985 985  
1184 +
986 986  Feature: Change LoRaWAN End Node Transmit Interval.
987 987  
1187 +
988 988  (% style="color:#4f81bd" %)**AT Command: AT+TDC**
989 989  
990 990  [[image:image-20220523150701-2.png||_mstalt="427453" _mstvisible="3"]]
... ... @@ -1002,8 +1002,10 @@
1002 1002  
1003 1003  == 4.2 Set External Sensor Mode ==
1004 1004  
1205 +
1005 1005  Feature: Change External Sensor Mode.
1006 1006  
1208 +
1007 1007  (% style="color:#4f81bd" %)**AT Command: AT+EXT**
1008 1008  
1009 1009  [[image:image-20220523150759-3.png||_mstalt="432146" _mstvisible="3"]]
... ... @@ -1021,9 +1021,9 @@
1021 1021  
1022 1022  * 0xA20702003c: Same as AT+SETCNT=60
1023 1023  
1024 -
1025 1025  == 4.3 Enable/Disable uplink Temperature probe ID ==
1026 1026  
1228 +
1027 1027  (((
1028 1028  Feature: If PID is enabled, device will send the temperature probe ID on:
1029 1029  )))
... ... @@ -1037,6 +1037,8 @@
1037 1037  
1038 1038  (((
1039 1039  PID is default set to disable (0)
1242 +
1243 +
1040 1040  )))
1041 1041  
1042 1042  (% style="color:#4f81bd" %)**AT Command:**
... ... @@ -1049,11 +1049,12 @@
1049 1049  * **0xA800**  **~-~->** AT+PID=0
1050 1050  * **0xA801**     **~-~->** AT+PID=1
1051 1051  
1052 -
1053 1053  == 4.4 Set Password ==
1054 1054  
1258 +
1055 1055  Feature: Set device password, max 9 digits
1056 1056  
1261 +
1057 1057  (% style="color:#4f81bd" %)**AT Command: AT+PWORD**
1058 1058  
1059 1059  [[image:image-20220523151052-5.png||_mstalt="428623" _mstvisible="3"]]
... ... @@ -1067,8 +1067,10 @@
1067 1067  
1068 1068  == 4.5 Quit AT Command ==
1069 1069  
1275 +
1070 1070  Feature: Quit AT Command mode, so user needs to input password again before use AT Commands.
1071 1071  
1278 +
1072 1072  (% style="color:#4f81bd" %)**AT Command: AT+DISAT**
1073 1073  
1074 1074  [[image:image-20220523151132-6.png||_mstalt="428649" _mstvisible="3"]]
... ... @@ -1082,6 +1082,7 @@
1082 1082  
1083 1083  == 4.6 Set to sleep mode ==
1084 1084  
1292 +
1085 1085  Feature: Set device to sleep mode
1086 1086  
1087 1087  * **AT+Sleep=0**  : Normal working mode, device will sleep and use lower power when there is no LoRa message
... ... @@ -1096,12 +1096,12 @@
1096 1096  
1097 1097  * There is no downlink command to set to Sleep mode.
1098 1098  
1099 -
1100 -
1101 1101  == 4.7 Set system time ==
1102 1102  
1309 +
1103 1103  Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
1104 1104  
1312 +
1105 1105  (% _msthash="315253" _msttexthash="137488" style="color:#4f81bd" %)**AT Command:**
1106 1106  
1107 1107  [[image:image-20220523151253-8.png||_mstalt="430677" _mstvisible="3"]]
... ... @@ -1115,6 +1115,7 @@
1115 1115  
1116 1116  == 4.8 Set Time Sync Mode ==
1117 1117  
1326 +
1118 1118  (((
1119 1119  Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
1120 1120  )))
... ... @@ -1121,6 +1121,8 @@
1121 1121  
1122 1122  (((
1123 1123  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.
1333 +
1334 +
1124 1124  )))
1125 1125  
1126 1126  (% _msthash="506058" _msttexthash="137488" style="color:#4f81bd" %)**AT Command:**
... ... @@ -1137,8 +1137,10 @@
1137 1137  
1138 1138  == 4.9 Set Time Sync Interval ==
1139 1139  
1351 +
1140 1140  Feature: Define System time sync interval. SYNCTDC default value: 10 days.
1141 1141  
1354 +
1142 1142  (% _msthash="315256" _msttexthash="137488" style="color:#4f81bd" %)**AT Command:**
1143 1143  
1144 1144  [[image:image-20220523151411-10.png||_mstalt="449696" _mstvisible="3"]]
... ... @@ -1152,8 +1152,10 @@
1152 1152  
1153 1153  == 4.10 Print data entries base on page. ==
1154 1154  
1368 +
1155 1155  Feature: Print the sector data from start page to stop page (max is 416 pages).
1156 1156  
1371 +
1157 1157  (% _msthash="315258" _msttexthash="264953" style="color:#4f81bd" %)**AT Command: AT+PDTA**
1158 1158  
1159 1159  [[image:image-20220523151450-11.png||_mstalt="451035" _mstvisible="3"]]
... ... @@ -1167,8 +1167,10 @@
1167 1167  
1168 1168  == 4.11 Print last few data entries. ==
1169 1169  
1385 +
1170 1170  Feature: Print the last few data entries
1171 1171  
1388 +
1172 1172  (% _msthash="315260" _msttexthash="288522" style="color:#4f81bd" %)**AT Command: AT+PLDTA**
1173 1173  
1174 1174  [[image:image-20220523151524-12.png||_mstalt="452101" _mstvisible="3"]]
... ... @@ -1182,6 +1182,7 @@
1182 1182  
1183 1183  == 4.12 Clear Flash Record ==
1184 1184  
1402 +
1185 1185  Feature: Clear flash storage for data log feature.
1186 1186  
1187 1187  
... ... @@ -1194,13 +1194,13 @@
1194 1194  
1195 1195  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1196 1196  
1197 -
1198 -
1199 1199  == 4.13 Auto Send None-ACK messages ==
1200 1200  
1417 +
1201 1201  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
1202 1202  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.
1203 1203  
1421 +
1204 1204  (% style="color:#4f81bd" %)**AT Command: AT+PNACKMD**
1205 1205  
1206 1206  (% _msthash="315396" _msttexthash="734682" _mstvisible="1" %)
... ... @@ -1214,11 +1214,11 @@
1214 1214  
1215 1215  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1216 1216  
1217 -
1218 1218  = 5. Battery & How to replace =
1219 1219  
1220 1220  == 5.1 Battery Type ==
1221 1221  
1439 +
1222 1222  (((
1223 1223  (((
1224 1224  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.
... ... @@ -1239,8 +1239,10 @@
1239 1239  The minimum Working Voltage for the LHT65N is ~~ 2.5v. When battery is lower than 2.6v, it is time to change the battery.
1240 1240  
1241 1241  
1460 +
1242 1242  == 5.2 Replace Battery ==
1243 1243  
1463 +
1244 1244  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.
1245 1245  
1246 1246  [[image:image-20220515075440-2.png||_mstalt="429546" _mstvisible="3" height="338" width="272"]][[image:image-20220515075625-3.png||_mstalt="431574" _mstvisible="3" height="193" width="257"]]
... ... @@ -1248,6 +1248,7 @@
1248 1248  
1249 1249  == 5.3 Battery Life Analyze ==
1250 1250  
1471 +
1251 1251  (((
1252 1252  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:
1253 1253  [[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]]
... ... @@ -1265,8 +1265,10 @@
1265 1265  
1266 1266  = 6. FAQ =
1267 1267  
1489 +
1268 1268  == 6.1 How to use AT Command? ==
1269 1269  
1492 +
1270 1270  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.
1271 1271  
1272 1272  [[image:image-20220530085651-1.png||_mstalt="429949"]]
... ... @@ -1274,16 +1274,11 @@
1274 1274  
1275 1275  (% _msthash="506061" _msttexthash="170755" %)**Connection:**
1276 1276  
1277 -(% _msthash="506062" _msttexthash="1187732" %)
1278 -**✓ (% style="background-color:yellow" %)USB to TTL GND <~-~->GND(%%)**
1500 +* (% style="background-color:yellow" %)**USB to TTL GND <~-~->GND**
1501 +* (% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+**
1502 +* (% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11**
1503 +* (% style="background-color:yellow" %)**USB to TTL 3.3V <~-~-> D-**
1279 1279  
1280 -(% _msthash="506063" _msttexthash="1158313" %)**✓  **(% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+**
1281 -
1282 -(% _msthash="506064" _msttexthash="1175629" %)**✓  **(% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11**
1283 -
1284 -(% _msthash="506065" _msttexthash="1164696" %)**✓  **(% style="background-color:yellow" %)**USB to TTL 3.3V <~-~-> D-**
1285 -
1286 -
1287 1287  (((
1288 1288  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.
1289 1289  )))
... ... @@ -1490,40 +1490,43 @@
1490 1490  AT+PID:  Get or set the PID
1491 1491  
1492 1492  
1711 +
1493 1493  == 6.2 Where to use AT commands and Downlink commands ==
1494 1494  
1495 -(% _msthash="506131" _msttexthash="14585714" %)
1496 -AT commands:
1497 1497  
1715 +**AT commands:**
1716 +
1498 1498  [[image:image-20220620153708-1.png||height="603" width="723"]]
1499 1499  
1500 -(% _msthash="506132" _msttexthash="337922" %)
1501 -Downlink commands:
1502 1502  
1720 +**Downlink commands:**
1503 1503  
1504 -(% _msthash="506133" _msttexthash="33046" %)
1505 -**TTN:**
1506 1506  
1723 +
1724 +(% style="color:blue" %)**TTN:**
1725 +
1507 1507  [[image:image-20220615092124-2.png||_mstalt="429221" height="649" width="688"]]
1508 1508  
1509 1509  
1510 -(% _msthash="506134" _msttexthash="11113791" %)
1511 -**Helium:**
1512 1512  
1730 +(% style="color:blue" %)**Helium:**
1731 +
1513 1513  [[image:image-20220615092551-3.png||_mstalt="430794" height="423" width="835"]]
1514 1514  
1515 1515  
1516 -(% _msthash="506135" _msttexthash="4159844" %)
1517 -**Chirpstack:The downlink window will not be displayed until the network is accessed**
1518 1518  
1736 +(% style="color:blue" %)**Chirpstack: The downlink window will not be displayed until the network is accessed**
1737 +
1738 +
1519 1519  [[image:image-20220615094850-6.png||_mstalt="433082"]]
1520 1520  
1741 +
1521 1521  [[image:image-20220615094904-7.png||_mstalt="433485" height="281" width="911"]]
1522 1522  
1523 1523  
1524 -(% _msthash="506136" _msttexthash="39286" %)
1525 -**Aws:**
1526 1526  
1746 +(% style="color:blue" %)**Aws:**
1747 +
1527 1527  [[image:image-20220615092939-4.png||_mstalt="434460" height="448" width="894"]]
1528 1528  
1529 1529  
... ... @@ -1530,6 +1530,7 @@
1530 1530  
1531 1531  == 6.3 How to change the uplink interval? ==
1532 1532  
1754 +
1533 1533  [[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/||_msthash="506137" _msttexthash="5712018"]]
1534 1534  
1535 1535  
... ... @@ -1536,6 +1536,7 @@
1536 1536  
1537 1537  == 6.4 How to use TTL-USB to connect a PC to input AT commands? ==
1538 1538  
1761 +
1539 1539  [[image:image-20220615153355-1.png]]
1540 1540  
1541 1541  [[image:1655802313617-381.png]]
... ... @@ -1593,6 +1593,66 @@
1593 1593  
1594 1594  
1595 1595  
1819 +== 6.6 Using USB-TYPE-C to connect to the computer using the AT command ==
1820 +
1821 +
1822 +[[image:image-20220623110706-1.png]]
1823 +
1824 +
1825 +[[image:image-20220623112117-4.png||height="459" width="343"]]
1826 +
1827 +
1828 +(((
1829 +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.
1830 +)))
1831 +
1832 +
1833 +Input password and ATZ to activate LHT65N,As shown below:
1834 +
1835 +[[image:image-20220615154519-3.png||height="672" width="807"]]
1836 +
1837 +
1838 +
1839 +== 6.7 How to use  USB-TYPE-C to connect PC to upgrade firmware? ==
1840 +
1841 +
1842 +[[image:image-20220623110706-1.png]]
1843 +
1844 +
1845 +(% style="color:blue" %)**Step1**(%%): Install TremoProgrammer  first.
1846 +
1847 +[[image:image-20220615170542-5.png]]
1848 +
1849 +
1850 +(% style="color:blue" %)**Step2**(%%):wiring method.(% style="display:none" %)
1851 +
1852 +(% _msthash="506146" _msttexthash="52173160" %)
1853 +First connect the four lines;
1854 +
1855 +(% _msthash="506146" _msttexthash="52173160" %)
1856 +[[image:image-20220623113959-5.png||height="528" width="397"]]
1857 +
1858 +(% _msthash="506146" _msttexthash="52173160" %)
1859 +Press and hold the start key to restart and enter  (% _mstvisible="1" %)bootlaod(%%) mode.
1860 +
1861 +
1862 +(% style="color:blue" %)**Step3:**(%%)Select the device port to be connected, baud rate and bin file to be downloaded.
1863 +
1864 +[[image:image-20220615171334-6.png]]
1865 +
1866 +
1867 +Click the (% style="color:blue" %)**start**(%%) button to start the firmware upgrade.
1868 +
1869 +
1870 +When this interface appears, it indicates that the download has been completed.
1871 +
1872 +[[image:image-20220620160723-8.png]]
1873 +
1874 +
1875 +Finally,restart reset device again
1876 +
1877 +
1878 +
1596 1596  = 7. Order Info =
1597 1597  
1598 1598  
... ... @@ -1622,6 +1622,7 @@
1622 1622  
1623 1623  
1624 1624  
1908 +
1625 1625  = 8. Packing Info =
1626 1626  
1627 1627  
... ... @@ -1636,12 +1636,19 @@
1636 1636  * Device Weight: 120.5g
1637 1637  
1638 1638  
1923 +
1924 +
1639 1639  = 9. Reference material =
1640 1640  
1927 +
1641 1641  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1642 1642  
1930 +
1931 +
1932 +
1643 1643  = 10. FCC Warning =
1644 1644  
1935 +
1645 1645  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1646 1646  
1647 1647  (1) This device may not cause harmful interference;
image-20220623110706-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +689.7 KB
Content
image-20220623110723-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +501.5 KB
Content
image-20220623111949-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 MB
Content
image-20220623112117-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +513.9 KB
Content
image-20220623113959-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +834.2 KB
Content
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