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

From version 175.1
edited by Bei Jinggeng
on 2022/06/23 11:40
Change comment: Uploaded new attachment "image-20220623113959-5.png", version {1}
To version 189.8
edited by Xiaoling
on 2022/08/08 16:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
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
... ... @@ -60,8 +60,6 @@
60 60  
61 61  
62 62  
63 -
64 -
65 65  == 1.3 Specification ==
66 66  
67 67  
... ... @@ -72,6 +72,8 @@
72 72  * Long Term Drift: < 0.02 °C/yr
73 73  * Operating Range: -40 ~~ 85 °C
74 74  
74 +
75 +
75 75  **Built-in Humidity Sensor:**
76 76  
77 77  * Resolution: 0.04 %RH
... ... @@ -79,6 +79,8 @@
79 79  * Long Term Drift: < 0.02 °C/yr
80 80  * Operating Range: 0 ~~ 96 %RH
81 81  
83 +
84 +
82 82  **External Temperature Sensor:**
83 83  
84 84  * Resolution: 0.0625 °C
... ... @@ -88,12 +88,11 @@
88 88  
89 89  
90 90  
91 -
92 -
93 93  = 2. Connect LHT65N to IoT Server =
94 94  
95 95  == 2.1 How does LHT65N work? ==
96 96  
98 +
97 97  (((
98 98  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.
99 99  )))
... ... @@ -103,8 +103,10 @@
103 103  )))
104 104  
105 105  
108 +
106 106  == 2.2 How to Activate LHT65N? ==
107 107  
111 +
108 108  (((
109 109  The LHT65N has two working modes:
110 110  )))
... ... @@ -129,6 +129,7 @@
129 129  
130 130  == 2.3 Example to join LoRaWAN network ==
131 131  
136 +
132 132  (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
133 133  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.
134 134  
... ... @@ -144,6 +144,7 @@
144 144  
145 145  === 2.3.1 Step 1: Create Device n TTN ===
146 146  
152 +
147 147  (((
148 148  Create a device in TTN V3 with the OTAA keys from LHT65N.
149 149  )))
... ... @@ -168,9 +168,10 @@
168 168  [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
169 169  
170 170  
171 -Note: LHT65N use same payload as LHT65.
172 172  
178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
173 173  
180 +
174 174  [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
175 175  
176 176  
... ... @@ -184,6 +184,7 @@
184 184  
185 185  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
186 186  
194 +
187 187  (((
188 188  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.
189 189  )))
... ... @@ -195,6 +195,7 @@
195 195  
196 196  == 2.4 Uplink Payload ==
197 197  
206 +
198 198  (((
199 199  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.
200 200  )))
... ... @@ -269,13 +269,13 @@
269 269  
270 270  * The First 6 bytes: has fix meanings for every LHT65N.
271 271  * The 7th byte (EXT #): defines the external sensor model.
272 -* 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.)
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.)
273 273  
274 274  
275 275  
276 -
277 277  === 2.4.1 Decoder in TTN V3 ===
278 278  
287 +
279 279  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.
280 280  
281 281  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -291,6 +291,7 @@
291 291  
292 292  === 2.4.2 BAT-Battery Info ===
293 293  
303 +
294 294  These two bytes of BAT include the battery state and the actually voltage
295 295  
296 296  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -306,9 +306,9 @@
306 306  
307 307  
308 308  
309 -
310 310  === 2.4.3 Built-in Temperature ===
311 311  
321 +
312 312  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
313 313  
314 314  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -319,9 +319,9 @@
319 319  
320 320  
321 321  
322 -
323 323  === 2.4.4 Built-in Humidity ===
324 324  
334 +
325 325  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
326 326  
327 327  * Humidity:    0x025C/10=60.4%
... ... @@ -328,9 +328,9 @@
328 328  
329 329  
330 330  
331 -
332 332  === 2.4.5 Ext # ===
333 333  
343 +
334 334  Bytes for External Sensor:
335 335  
336 336  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -362,6 +362,7 @@
362 362  
363 363  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
364 364  
375 +
365 365  (((
366 366  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:
367 367  )))
... ... @@ -475,17 +475,19 @@
475 475  
476 476  * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
477 477  
478 -[[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)
479 479  
480 -* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
481 -* 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.
482 -* 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)
483 483  
484 484  
485 485  
486 -
487 487  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
488 488  
501 +
489 489  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
490 490  
491 491  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -494,10 +494,46 @@
494 494  
495 495  AT+EXT=6,timeout  (% _msthash="506085" _msttexthash="8782189" _mstvisible="3" style="color:red" %)Time to power this sensor, from 0 ~~ 65535ms
496 496  
510 +For example:
497 497  
512 +AT+EXT=6,1000 will power this sensor for 1000ms before sampling the ADC value.
498 498  
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 +
499 499  == 2.5 Show data on Datacake ==
500 500  
549 +
501 501  (((
502 502  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:
503 503  )))
... ... @@ -545,6 +545,7 @@
545 545  
546 546  == 2.6 Datalog Feature ==
547 547  
597 +
548 548  (((
549 549  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.
550 550  )))
... ... @@ -553,12 +553,15 @@
553 553  
554 554  === 2.6.1 Ways to get datalog via LoRaWAN ===
555 555  
606 +
556 556  There are two methods:
557 557  
558 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
559 -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.
560 560  
612 +Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
561 561  
614 +[[image:image-20220703111700-2.png||height="381" width="1119"]]
562 562  
563 563  
564 564  === 2.6.2 Unix TimeStamp ===
... ... @@ -583,6 +583,7 @@
583 583  
584 584  === 2.6.3 Set Device Time ===
585 585  
639 +
586 586  (((
587 587  There are two ways to set device's time:
588 588  )))
... ... @@ -600,7 +600,7 @@
600 600  )))
601 601  
602 602  (((
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 doesnt support. If server doesnt 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.**
604 604  )))
605 605  
606 606  (((
... ... @@ -619,6 +619,7 @@
619 619  
620 620  === 2.6.4 Poll sensor value ===
621 621  
676 +
622 622  User can poll sensor value based on timestamps from the server. Below is the downlink command.
623 623  
624 624  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -636,6 +636,7 @@
636 636  
637 637  === 2.6.5 Datalog Uplink payload ===
638 638  
694 +
639 639  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
640 640  The Datalog poll reply uplink will use below payload format.
641 641  
... ... @@ -642,6 +642,9 @@
642 642  (% _mstvisible="1" %)
643 643  (((
644 644  (% _mstvisible="2" %)
701 +
702 +
703 +(% _mstvisible="2" %)
645 645  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
646 646  )))
647 647  
... ... @@ -769,6 +769,7 @@
769 769  )))
770 770  )))
771 771  
831 +
772 772  (% _mstvisible="1" %)
773 773  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
774 774  
... ... @@ -904,7 +904,7 @@
904 904  (% _mstvisible="1" %)
905 905  (((
906 906  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
907 - 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
908 908  )))
909 909  
910 910  (% _mstvisible="1" %)
... ... @@ -1001,8 +1001,21 @@
1001 1001  )))
1002 1002  )))
1003 1003  
1064 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
1004 1004  
1066 +Total bytes: 8 bytes
1005 1005  
1068 +**Example:**AA0100010001003C
1069 +
1070 +WMOD=01
1071 +
1072 +CITEMP=0001
1073 +
1074 +TEMPlow=0001
1075 +
1076 +TEMPhigh=003C
1077 +
1078 +
1006 1006  == 2.8 LED Indicator ==
1007 1007  
1008 1008  The LHT65 has a triple color LED which for easy showing different stage .
... ... @@ -1017,8 +1017,6 @@
1017 1017  * For each success downlink, the PURPLE LED will blink once
1018 1018  
1019 1019  
1020 -
1021 -
1022 1022  == 2.9 installation ==
1023 1023  
1024 1024  (% _mstvisible="1" %)
... ... @@ -1032,8 +1032,24 @@
1032 1032  
1033 1033  [[image:image-20220619092222-1.png||height="182" width="188"]][[image:image-20220619092313-2.png||height="182" width="173"]]
1034 1034  
1035 -1m long breakout cable for LHT65N
1106 +**1m long breakout cable for LHT65N. Features:**
1036 1036  
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 +
1037 1037  [[image:image-20220619092421-3.png||height="371" width="529"]]
1038 1038  
1039 1039  
... ... @@ -1054,8 +1054,6 @@
1054 1054  * Working voltage 2.35v ~~ 5v
1055 1055  
1056 1056  
1057 -
1058 -
1059 1059  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
1060 1060  
1061 1061  (((
... ... @@ -1122,8 +1122,6 @@
1122 1122  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1123 1123  
1124 1124  
1125 -
1126 -
1127 1127  == 4.2 Set External Sensor Mode ==
1128 1128  
1129 1129  Feature: Change External Sensor Mode.
... ... @@ -1146,8 +1146,6 @@
1146 1146  * 0xA20702003c: Same as AT+SETCNT=60
1147 1147  
1148 1148  
1149 -
1150 -
1151 1151  == 4.3 Enable/Disable uplink Temperature probe ID ==
1152 1152  
1153 1153  (((
... ... @@ -1176,8 +1176,6 @@
1176 1176  * **0xA801**     **~-~->** AT+PID=1
1177 1177  
1178 1178  
1179 -
1180 -
1181 1181  == 4.4 Set Password ==
1182 1182  
1183 1183  Feature: Set device password, max 9 digits
... ... @@ -1225,8 +1225,6 @@
1225 1225  * There is no downlink command to set to Sleep mode.
1226 1226  
1227 1227  
1228 -
1229 -
1230 1230  == 4.7 Set system time ==
1231 1231  
1232 1232  Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
... ... @@ -1324,8 +1324,6 @@
1324 1324  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1325 1325  
1326 1326  
1327 -
1328 -
1329 1329  == 4.13 Auto Send None-ACK messages ==
1330 1330  
1331 1331  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
... ... @@ -1345,8 +1345,6 @@
1345 1345  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1346 1346  
1347 1347  
1348 -
1349 -
1350 1350  = 5. Battery & How to replace =
1351 1351  
1352 1352  == 5.1 Battery Type ==
... ... @@ -1719,7 +1719,59 @@
1719 1719  Finally, unplug the DuPont cable on port4, and then use the DuPont cable to short circuit port3 and port1 to reset the device.
1720 1720  
1721 1721  
1795 +== 6.6 Using USB-TYPE-C to connect to the computer using the AT command ==
1722 1722  
1797 +[[image:image-20220623110706-1.png]]
1798 +
1799 +
1800 +[[image:image-20220623112117-4.png||height="459" width="343"]]
1801 +
1802 +(((
1803 +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.
1804 +)))
1805 +
1806 +
1807 +Input password and ATZ to activate LHT65N,As shown below:
1808 +
1809 +[[image:image-20220615154519-3.png||height="672" width="807"]]
1810 +
1811 +
1812 +== 6.7 How to use  USB-TYPE-C to connect PC to upgrade firmware? ==
1813 +
1814 +[[image:image-20220623110706-1.png]]
1815 +
1816 +(% style="color:blue" %)**Step1**(%%): Install TremoProgrammer  first.
1817 +
1818 +[[image:image-20220615170542-5.png]]
1819 +
1820 +
1821 +(% style="color:blue" %)**Step2**(%%):wiring method.(% style="display:none" %)
1822 +
1823 +(% _msthash="506146" _msttexthash="52173160" %)
1824 +First connect the four lines;
1825 +
1826 +(% _msthash="506146" _msttexthash="52173160" %)
1827 +[[image:image-20220623113959-5.png||height="528" width="397"]]
1828 +
1829 +(% _msthash="506146" _msttexthash="52173160" %)
1830 +Press and hold the start key to restart and enter  (% _mstvisible="1" %)bootlaod(%%) mode.
1831 +
1832 +(% style="color:blue" %)**Step3:**(%%)Select the device port to be connected, baud rate and bin file to be downloaded.
1833 +
1834 +[[image:image-20220615171334-6.png]]
1835 +
1836 +
1837 +Click the (% style="color:blue" %)**start**(%%) button to start the firmware upgrade.
1838 +
1839 +
1840 +When this interface appears, it indicates that the download has been completed.
1841 +
1842 +[[image:image-20220620160723-8.png]]
1843 +
1844 +
1845 +Finally,restart reset device again
1846 +
1847 +
1723 1723  = 7. Order Info =
1724 1724  
1725 1725  
... ... @@ -1748,8 +1748,6 @@
1748 1748  * (% style="color:red" %)**E3**(%%): External Temperature Probe
1749 1749  
1750 1750  
1751 -
1752 -
1753 1753  = 8. Packing Info =
1754 1754  
1755 1755  
... ... @@ -1764,15 +1764,11 @@
1764 1764  * Device Weight: 120.5g
1765 1765  
1766 1766  
1767 -
1768 -
1769 1769  = 9. Reference material =
1770 1770  
1771 1771  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1772 1772  
1773 1773  
1774 -
1775 -
1776 1776  = 10. FCC Warning =
1777 1777  
1778 1778  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