Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 71.1
edited by Edwin Chen
on 2022/10/09 23:47
on 2022/10/09 23:47
Change comment:
There is no comment for this version
To version 57.1
edited by Edwin Chen
on 2022/10/08 17:11
on 2022/10/08 17:11
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 8 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,3 +1,5 @@ 1 +== == 2 + 1 1 (% style="text-align:center" %) 2 2 [[image:1664505654417-133.png]] 3 3 ... ... @@ -97,7 +97,6 @@ 97 97 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 98 98 * Tracking: max: 38mA 99 99 100 - 101 101 == 1.3 Features == 102 102 103 103 ... ... @@ -116,7 +116,6 @@ 116 116 * Tri-color LED, Alarm button 117 117 * Datalog 118 118 119 - 120 120 == 1.4 Applications == 121 121 122 122 ... ... @@ -123,7 +123,6 @@ 123 123 * Logistics and Supply Chain Management 124 124 * Human tracking 125 125 126 - 127 127 = 2.1 Use TrackerD = 128 128 129 129 ... ... @@ -186,10 +186,8 @@ 186 186 (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. 187 187 188 188 188 +== 2.3 Positioning Mode(SMOD) == 189 189 190 -== 2.3 Positioning Mode(SMOD) == 191 - 192 - 193 193 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 194 194 195 195 * (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. ... ... @@ -199,23 +199,18 @@ 199 199 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 200 200 201 201 199 +== 2.3 Uplink Payload == 202 202 203 -== 2.4 Uplink Payload == 204 204 202 +=== 2.3.1 Uplink FPORT~=5, Device Status === 205 205 206 - === 2.4.1Uplink FPORT~=5, Device Status===204 +Uplink the device configures with FPORT=5. Once LHT52 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours. 207 207 206 +|=**Size (bytes)**|=**1**|=**2**|=**1**|=**1**|=**2** 207 +|**Value**|Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT 208 208 209 - Uplink the device configures with FPORT=5. Once LGT92 Joined the network, it will uplink thismessageto the server. After first uplink, LHT52will uplink Device Status every12hours.209 +[[image:image-20221006181357-2.png]] 210 210 211 - 212 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 213 -|=(% scope="row" style="width: 108px;" %)**Size(bytes)**|=(% style="width: 82px;" %)**1**|=(% style="width: 83px;" %)**2**|=(% style="width: 94px;" %)**1**|=(% style="width: 84px;" %)**1**|=(% style="width: 44px;" %)2|=(% style="width: 63px;" %)**2**|=(% style="width: 60px;" %)1 214 -|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status 215 - 216 -[[image:1665301570342-765.png]] 217 - 218 - 219 219 Example Payload (FPort=5): [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]] 220 220 221 221 **Sensor Model**: For TrackerD, this value is 0x13. ... ... @@ -253,26 +253,25 @@ 253 253 Use can also get the Device Status uplink through the downlink command: 254 254 255 255 248 +=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning === 256 256 257 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 258 258 251 +The default uplink payload includes totally 11 bytes. (User can use AT+SMOD=1,0 to enable uploading on-board Temperature and humidity value, and total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. ) 259 259 260 -User can use **AT+SMOD=1,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band. 261 261 262 - 263 263 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 264 264 |=(% scope="row" style="width: 50px;" %)((( 265 265 **Size(bytes)** 266 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width: 73px" %)1|(% style="width:40px" %)(((267 -2 257 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)((( 258 +2(optional) 268 268 )))|(% style="width:87px" %)((( 269 -2 260 +2(optional) 270 270 ))) 271 271 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 272 272 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 273 -)))|(% style="width: 73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]264 +)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 274 274 275 -[[image:1665 301636888-168.png]]266 +[[image:1664501958445-288.png]] 276 276 277 277 278 278 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -281,15 +281,11 @@ 281 281 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 282 282 |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 283 283 284 -==== ==== 285 - 286 -==== ==== 287 - 288 288 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 289 289 290 290 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 291 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit 292 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 278 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits 279 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 293 293 294 294 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 295 295 ... ... @@ -299,19 +299,19 @@ 299 299 * Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 300 300 * Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 301 301 302 - 303 303 (% style="color:red" %)**Important note:** 304 304 305 305 1. When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF. 306 306 307 -2. Inthis mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:293 +2. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 308 308 309 309 310 310 [[image:1664502116362-706.png]] 311 311 312 312 313 -3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 314 314 300 +4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 301 + 315 315 [[image:1664502166010-515.png]] 316 316 317 317 ... ... @@ -321,13 +321,12 @@ 321 321 Example: 0x4B & 0x40 >> 6 = 0x01 322 322 323 323 324 - 325 325 ==== (% style="color:blue" %)**BAT:**(%%) ==== 326 326 327 327 Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 328 328 329 329 ((( 330 -The battery info shows the battery voltage,User can usethebelow mapping to indicate the battery in percentage: \316 +The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \ 331 331 ))) 332 332 333 333 * > 4.0v : 80% ~~ 100% ... ... @@ -336,7 +336,6 @@ 336 336 * 3.40v ~~ 3.69v: 20% ~~ 40% 337 337 * < 3.39v: 0~~20% 338 338 339 - 340 340 ==== (% style="color:blue" %)**LON:**(%%) ==== 341 341 342 342 Enable/Disable LED activity for uplink ... ... @@ -361,51 +361,15 @@ 361 361 362 362 363 363 364 -=== 2. 4.33,RealtimeGNSS Positioning(Default Mode)===349 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 365 365 366 366 367 -The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity) 368 368 353 +=== 2.3.4 BLE positioning Payload(Fport2) === 369 369 370 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 371 -|=(% scope="row" style="width: 50px;" %)((( 372 -**Size(bytes)** 373 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1 374 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 375 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 376 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 377 377 378 -(% class="wikigeneratedid" %) 379 -[[image:1665301687277-443.png]] 356 +Different MODE has different payload: (% style="color:blue" %)**MODE=2** 380 380 381 - 382 - 383 -=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 384 - 385 - 386 -Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD 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. 387 - 388 - 389 -(% style="color:red" %)**Note for this mode:** 390 - 391 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 392 -* 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. 393 - 394 -The payload is 15 bytes, as below. 395 - 396 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 397 -|=(% scope="row" %)((( 398 -**Size(bytes)** 399 -)))|4|4|2|1|1|1|1|1 400 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 401 - 402 -[[image:image-20221009160309-2.png]] 403 - 404 - 405 - 406 -=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 407 - 408 - 409 409 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 410 410 |=(% scope="row" style="width: 60px;" %)((( 411 411 **Size(bytes)** ... ... @@ -433,11 +433,9 @@ 433 433 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 434 434 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 435 435 385 +=== 2.3.5 Add Payload format in TTN V3 === 436 436 437 437 438 -=== 2.4.6 Add Payload format in TTN V3 === 439 - 440 - 441 441 In TTN V3, use can add a custom payload so it shows friendly. 442 442 443 443 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** ... ... @@ -455,7 +455,7 @@ 455 455 456 456 457 457 458 -== 2. 5Integrate with Datacake ==405 +== 2.4 Integrate with Datacake == 459 459 460 460 461 461 ((( ... ... @@ -471,7 +471,7 @@ 471 471 472 472 473 473 474 -== 2. 6Integrate with Tago ==421 +== 2.5 Integrate with Tago == 475 475 476 476 477 477 ((( ... ... @@ -487,24 +487,12 @@ 487 487 488 488 489 489 490 -== 2. 7Datalog Feature ==437 +== 2.6 Datalog Feature == 491 491 492 492 493 - total273entries,bydefaultdisable440 +== 2.6 Alarm Mode == 494 494 495 495 496 -Example use case. 497 - 498 -[[image:image-20221009234703-2.png]] 499 - 500 - 501 -[[image:image-20221009234629-1.png||height="441" width="652"]] 502 - 503 - 504 - 505 -== 2.8 Alarm Mode == 506 - 507 - 508 508 ((( 509 509 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 510 510 ))) ... ... @@ -528,16 +528,15 @@ 528 528 529 529 530 530 531 -== 2. 9Transport Mode ==466 +== 2.7 Transport Mode == 532 532 533 533 534 534 In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes. 535 535 536 536 472 +== 2.8 LED Status == 537 537 538 -== 2.10 LED Status == 539 539 540 - 541 541 (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 542 542 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 543 543 |(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A ... ... @@ -552,11 +552,9 @@ 552 552 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 553 553 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 554 554 489 +== 2.9 Button Function == 555 555 556 556 557 -== 2.11 Button Function == 558 - 559 - 560 560 (% style="color:blue" %)**RESET button:** 561 561 562 562 [[image:1664502835802-546.png]] ... ... @@ -575,11 +575,9 @@ 575 575 |(% 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 576 576 |(% 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. 577 577 510 +== 2.10 USB Port Function == 578 578 579 579 580 -== 2.12 USB Port Function == 581 - 582 - 583 583 The USB interface of TrackerD has below functions: 584 584 585 585 * Power on the device ... ... @@ -587,8 +587,6 @@ 587 587 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 588 588 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 589 589 590 - 591 - 592 592 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 593 593 594 594 ... ... @@ -710,16 +710,16 @@ 710 710 711 711 712 712 713 -=== 3.2.6 Disable/Enable TransportMode ===641 +=== 3.2.6 Disable/Enable movement detect (Debug Only) === 714 714 715 715 716 -User scan use this feature to enable/disableTransportMode.644 +User can use this feature to check and set thread hole of movement detect 717 717 718 718 * (% style="color:blue" %)**AT Command:** 719 719 720 720 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 721 721 722 -Example: AT+ INTWK =1 **~-~-> ** Enable TransportMode.650 +Example: AT+ INTWK =1 **~-~-> ** Enable detect movement. 723 723 724 724 725 725 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** ... ... @@ -736,25 +736,9 @@ 736 736 737 737 * (% style="color:blue" %)**AT Command:** 738 738 739 -(% style="color:#037691" %)**AT+SMOD= aa,bb**667 +(% style="color:#037691" %)**AT+SMOD=xx. ** 740 740 741 -(% style="color:#037691" %)** aa:** 742 742 743 -* (% style="color:#037691" %)**1: GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 744 -* (% style="color:#037691" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 745 -* (% style="color:#037691" %)**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 746 - 747 -(% style="color:#037691" %)**bb:** 748 - 749 -(% style="color:#037691" %)** if aa = 1: ** 750 - 751 -* (% style="color:#037691" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 752 -* (% style="color:#037691" %)**1 :**(%%) GPS +BAT State 753 - 754 -(% style="color:#037691" %)** if aa = 2: ** 755 - 756 -* (% style="color:#037691" %)**3 : **(%%)(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 757 - 758 758 **Example:** 759 759 760 760 AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum ... ... @@ -761,7 +761,7 @@ 761 761 762 762 AT+ SMOD =1,1 **~-~->** GPS +BAT State 763 763 764 - AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 676 + AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 765 765 766 766 767 767 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** ... ... @@ -792,7 +792,7 @@ 792 792 793 793 794 794 795 -=== 3. 2.9 Set PDOP value for GPS fix accuracy ===707 +=== 3.3.9 Set PDOP value for GPS fix accuracy === 796 796 797 797 798 798 PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server. ... ... @@ -915,7 +915,6 @@ 915 915 [[image:1664503635019-941.png]] 916 916 917 917 918 - 919 919 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 920 920 921 921 [[image:1664503715811-892.png]] ... ... @@ -980,8 +980,6 @@ 980 980 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 981 981 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 982 982 983 - 984 - 985 985 = 8. Order Info = 986 986 987 987 ... ... @@ -997,8 +997,6 @@ 997 997 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 998 998 * (% style="color:red" %)**US915**(%%): Default frequency band US915 999 999 1000 - 1001 - 1002 1002 = 9. Packing Info = 1003 1003 1004 1004 ... ... @@ -1012,7 +1012,6 @@ 1012 1012 * Device Size: 85 x 48 x 15 cm 1013 1013 * Weight: 50g 1014 1014 1015 - 1016 1016 = 10. Support = 1017 1017 1018 1018 ... ... @@ -1019,7 +1019,6 @@ 1019 1019 * 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. 1020 1020 * 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]]. 1021 1021 1022 - 1023 1023 = 11. Reference = 1024 1024 1025 1025
- 1665301570342-765.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1665301636888-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.6 KB - Content
- 1665301687277-443.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- 1665301786397-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- image-20221009160220-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.4 KB - Content
- image-20221009160309-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.2 KB - Content
- image-20221009234629-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -222.9 KB - Content
- image-20221009234703-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -136.4 KB - Content