Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 84.12
edited by Xiaoling
on 2022/10/26 08:56
on 2022/10/26 08:56
Change comment:
There is no comment for this version
To version 106.1
edited by Bei Jinggeng
on 2022/11/07 09:15
on 2022/11/07 09:15
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 7 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Bei - Content
-
... ... @@ -97,6 +97,7 @@ 97 97 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 98 98 * Tracking: max: 38mA 99 99 100 + 100 100 == 1.3 Features == 101 101 102 102 ... ... @@ -115,6 +115,7 @@ 115 115 * Tri-color LED, Alarm button 116 116 * Datalog 117 117 119 + 118 118 == 1.4 Applications == 119 119 120 120 ... ... @@ -121,9 +121,10 @@ 121 121 * Logistics and Supply Chain Management 122 122 * Human tracking 123 123 124 -= 2.1 Use TrackerD = 125 125 127 += 2. Use TrackerD = 126 126 129 + 127 127 == 2.1 How it works? == 128 128 129 129 ... ... @@ -189,9 +189,9 @@ 189 189 190 190 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 191 191 192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%) only get and uplink GPS location info.193 -* (% style="color:#037691" %)**BLE ONLY: 194 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 195 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 196 +* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking. 197 +* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 195 195 196 196 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 197 197 ... ... @@ -279,7 +279,9 @@ 279 279 280 280 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 281 281 285 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 282 282 287 + 283 283 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 284 284 285 285 (% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) ... ... @@ -286,6 +286,7 @@ 286 286 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit 287 287 |=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 288 288 294 + 289 289 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 290 290 291 291 ... ... @@ -292,12 +292,12 @@ 292 292 Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, 293 293 294 294 295 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:2 40px" %)296 -|=(% scope="row" style="width: 50px;" %)(((301 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 302 +|=(% scope="row" style="width: 60px;" %)((( 297 297 **Size(bytes)** 298 -)))|(% style="width: 30px" %)4|(% style="width:40px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1|(% style="width:20px" %)(((304 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 299 299 2 300 -)))|(% style="width: 20px" %)(((306 +)))|(% style="width:30px" %)((( 301 301 2 302 302 ))) 303 303 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( ... ... @@ -362,6 +362,7 @@ 362 362 * 3.40v ~~ 3.69v: 20% ~~ 40% 363 363 * < 3.39v: 0~~20% 364 364 371 + 365 365 ==== (% style="color:blue" %)**MOD:**(%%) ==== 366 366 367 367 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -392,7 +392,6 @@ 392 392 ))) 393 393 394 394 395 - 396 396 ==== (% style="color:blue" %)**Hum:**(%%) ==== 397 397 398 398 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree ... ... @@ -410,10 +410,10 @@ 410 410 The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity) 411 411 412 412 413 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width: 480px" %)414 -|=(% scope="row" style="width: 50px;" %)(((419 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 420 +|=(% scope="row" style="width: 60px;" %)((( 415 415 **Size(bytes)** 416 -)))|(% style="width:60px" %)4|(% style="width: 70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1422 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 417 417 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 418 418 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 419 419 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] ... ... @@ -432,12 +432,12 @@ 432 432 (% style="color:red" %)**Note for this mode:** 433 433 434 434 * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 435 -* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%)when PNACKMD=1, but TrackerD 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 TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.441 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD 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 TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages. 436 436 * c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL 437 437 438 438 The payload is 15 bytes, as below. 439 439 440 -(% border="1.5" style="background-color:#ffffcc; color:green; width:5 20px" %)446 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 441 441 |=(% scope="row" %)((( 442 442 **Size(bytes)** 443 443 )))|4|4|2|1|1|1|1|1 ... ... @@ -482,11 +482,35 @@ 482 482 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 483 483 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 484 484 485 -=== 2.4.6 Add Payload format in TTN V3 === 486 486 492 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 487 487 488 -In TTN V3, use can add a custom payload so it shows friendly. 489 489 495 +TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink. 496 + 497 + 498 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 499 +|=(% scope="row" style="width: 60px;" %)((( 500 +**Size(bytes)** 501 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 502 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 503 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 504 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 505 + 506 +(% class="wikigeneratedid" %) 507 +[[image:1667288597595-714.png||height="212" width="1151"]] 508 + 509 + 510 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 511 +* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 512 +* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 513 + 514 + 515 +=== 2.4.7 Add Payload format in TTN V3 === 516 + 517 + 518 +In TTN V3, user can add a custom payload so it shows friendly. 519 + 490 490 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 491 491 492 492 ... ... @@ -593,6 +593,7 @@ 593 593 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 594 594 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 595 595 626 + 596 596 == 2.11 Button Function == 597 597 598 598 ... ... @@ -608,12 +608,13 @@ 608 608 [[image:1664502854406-763.png]] 609 609 610 610 611 -(% border="1 .5" style="background-color:#ffffcc; color:green; width:520px" %)612 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 2 10px;" %)**Action**|=(% style="width: 210px;" %)**Description**642 +(% border="1" style="background-color:#ffffcc; color:green; width:510px" %) 643 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 613 613 |(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>>||anchor="H2.6AlarmMode"]] 614 614 |(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the (% style="color:red" %)**RED** (%%)button 10 times|(% style="width:265px" %)Exit Alarm Mode 615 615 |(% style="width:135px" %)Enter Deep Sleep Mode|(% style="width:220px" %)Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|(% style="width:265px" %)This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy. 616 616 648 + 617 617 == 2.12 USB Port Function == 618 618 619 619 ... ... @@ -624,6 +624,7 @@ 624 624 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 625 625 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 626 626 659 + 627 627 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 628 628 629 629 ... ... @@ -773,9 +773,9 @@ 773 773 774 774 (% style="color:#037691" %)** aa:** 775 775 776 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%) only get and uplink GPS location info.777 -* (% style="color:red" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 778 -* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 809 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 810 +* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking. 811 +* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 779 779 780 780 (% style="color:#037691" %)**bb:** 781 781 ... ... @@ -785,6 +785,7 @@ 785 785 (% style="color:#037691" %)**cc: ** 786 786 787 787 * (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 821 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 788 788 789 789 (% style="color:blue" %)**Example:** 790 790 ... ... @@ -791,6 +791,7 @@ 791 791 AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 792 792 AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 793 793 AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 828 + AT+ SMOD =2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 794 794 795 795 796 796 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** ... ... @@ -861,7 +861,7 @@ 861 861 862 862 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 863 863 864 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD=1899 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ CFM =1 865 865 866 866 867 867 ... ... @@ -890,7 +890,7 @@ 890 890 === 3.2.11 Set BLEMASK to filter BLE iBeacon === 891 891 892 892 893 -BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.928 +BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID. 894 894 895 895 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 896 896 ... ... @@ -900,13 +900,57 @@ 900 900 901 901 (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 902 902 938 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 903 903 904 - (% style="color:blue"%)**DownlinkPayload: (Prefix:0xA5)**940 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 905 905 906 -Example: 0xA5010203040506 ~/~/ Set BLEMASK to 123456 907 907 908 908 944 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 909 909 946 + 947 +WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456. It will ignore all other WiFi which doesn’t contact 123456 in the SSID. 948 + 949 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 950 + 951 +(% style="color:blue" %)**AT Command:** 952 + 953 + (% style="color:#037691" %)**AT+WiFiMASK =123456** (%%) ~/~/ Set WiFiMASK = 123456 954 + 955 + (% style="color:#037691" %)**AT+WiFiMASK =0** (%%) ~/~/ disable WiFiMASK 956 + 957 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 958 + 959 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 960 + 961 + 962 + 963 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 964 + 965 + 966 +Users can use this feature to enable/disable Information printing. 967 + 968 +(% style="color:blue" %)**AT Command:** 969 + 970 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 971 +\\Example: AT+SHOWID =1 ~-~-> Enable Information printing. 972 + 973 + 974 + 975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 976 + 977 + 978 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 979 + 980 +(% style="color:blue" %)**AT Command:** 981 + 982 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode, 983 + 984 +(% style="color:blue" %)**Downlink Payload:0X24**(%%) 985 +Example: 0x24 01 ~/~/ Same as AT+CHE= = 1 986 + 987 + 988 + 910 910 = 4. Setting for Different Scenarios = 911 911 912 912 ... ... @@ -1063,6 +1063,61 @@ 1063 1063 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1064 1064 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1065 1065 1145 + 1146 +== 7.3 Notes on using different serial port tools for TrackerD == 1147 + 1148 + 1149 +=== **Serial port utility** === 1150 + 1151 + 1152 +Serial port utility requires you to automatically add data streams. 1153 + 1154 +Need to adjust the data stream to RTS/CTS on physical restart. 1155 + 1156 + 1157 +(% class="wikigeneratedid" %) 1158 +[[image:image-20221102140621-1.png]] 1159 + 1160 + 1161 +When using AT commands, the data flow needs to be adjusted to XON/XOFF 1162 + 1163 + 1164 +[[image:image-20221102140638-2.png]] 1165 + 1166 + 1167 + 1168 +=== **SecureCRT** === 1169 + 1170 + 1171 +The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view. 1172 + 1173 + 1174 +[[image:image-20221102140704-3.png]] 1175 + 1176 + 1177 +[[image:image-20221102140712-4.png]] 1178 + 1179 + 1180 + 1181 +=== **PUTTY** === 1182 + 1183 + 1184 +[[image:image-20221102140748-5.png]] 1185 + 1186 + 1187 +Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty. 1188 + 1189 + 1190 +[[image:image-20221102140801-6.png]] 1191 + 1192 + 1193 +== 7.4 TrackerD trouble shooting == 1194 + 1195 + 1196 +V1.4.0: When the motion mode is turned on, the TDC needs to be greater than MTDC, otherwise TDC time will be confused 1197 + 1198 + 1199 + 1066 1066 = 8. Order Info = 1067 1067 1068 1068 ... ... @@ -1078,6 +1078,7 @@ 1078 1078 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1079 1079 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1080 1080 1215 + 1081 1081 = 9. Packing Info = 1082 1082 1083 1083 ... ... @@ -1088,9 +1088,10 @@ 1088 1088 1089 1089 (% style="color:#037691" %)**Dimensions and Weight**: 1090 1090 1091 -* Device Size: 85 x 48 x 15 cm1226 +* Device Size: 85 x 48 x 15 mm 1092 1092 * Weight: 50g 1093 1093 1229 + 1094 1094 = 10. Support = 1095 1095 1096 1096 ... ... @@ -1097,6 +1097,7 @@ 1097 1097 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1098 1098 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. 1099 1099 1236 + 1100 1100 = 11. Reference = 1101 1101 1102 1102 ... ... @@ -1104,4 +1104,5 @@ 1104 1104 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1105 1105 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1106 1106 1244 + 1107 1107
- 1667288597595-714.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.9 KB - Content
- image-20221102140621-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.1 KB - Content
- image-20221102140638-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.8 KB - Content
- image-20221102140704-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.5 KB - Content
- image-20221102140712-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +73.2 KB - Content
- image-20221102140748-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +56.0 KB - Content
- image-20221102140801-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +21.0 KB - Content