Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 34 removed)
- 1664499635206-262.png
- 1664499921684-770.png
- 1664501652064-326.png
- 1664501677253-891.png
- 1664501711466-918.png
- 1664501721248-725.png
- 1664501734705-405.png
- 1664501784668-703.png
- 1664501958445-288.png
- 1664502116362-706.png
- 1664502166010-515.png
- 1664502425687-834.png
- 1664502649601-895.png
- 1664502676891-606.png
- 1664502695771-538.png
- 1664502715371-321.png
- 1664502835802-546.png
- 1664502854406-763.png
- 1664502999401-486.png
- 1664503022490-662.png
- 1664503035713-500.png
- 1664503047675-651.png
- 1664503563660-578.png
- 1664503574618-659.png
- 1664503593459-435.png
- 1664503611848-385.png
- 1664503635019-941.png
- 1664503715811-892.png
- 1664503752288-974.png
- 1664503794261-827.png
- 1664503808294-336.png
- 1664503824081-592.png
- 1664503831430-500.png
- 1664505654417-133.png
Details
- Page properties
-
- Content
-
... ... @@ -1,9 +7,3 @@ 1 -(% style="text-align:center" %) 2 -[[image:1664505654417-133.png]] 3 - 4 - 5 - 6 - 7 7 (% class="wikigeneratedid" %) 8 8 **Table of Contents:** 9 9 ... ... @@ -12,18 +12,19 @@ 12 12 13 13 14 14 9 + 15 15 = 1. Introduction = 16 16 12 +== 1.1 OverView == 17 17 18 -== 1.1 What is TrackerD == 19 19 20 - 21 21 ((( 22 22 TrackerD is an (% style="color:blue" %)**Open Source LoRaWAN Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**. 23 23 ))) 24 24 25 25 ((( 26 -In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario. 20 +There are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer in TrackerD. Make it useful for different kinds of applications. 21 +))) 27 27 28 28 ((( 29 29 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution. ... ... @@ -30,9 +30,8 @@ 30 30 ))) 31 31 32 32 ((( 33 -The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. zing current consumption. It targets professional tracking services.28 +The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates.It provides ultra-long range spread spectrum communication and high interference immunity whilst minimising current consumption. It targets professional tracking services. 34 34 ))) 35 -))) 36 36 37 37 ((( 38 38 TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network. ... ... @@ -40,841 +40,109 @@ 40 40 41 41 ))) 42 42 43 -[[image: 1664499921684-770.png]]37 +[[image:image-20220906111043-1.png]] 44 44 45 45 46 - (% style="color:red"%)**Note:LoRaWAN server can be a general LoRaWAN serverother than TTN.**40 +== 1.2 Features == 47 47 48 48 43 +* LoRaWAN v1.0.3 Class A protocol. 44 +* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864 45 +* Track position via GPS / BLE or WiFi 46 +* Temperature & Humidity 47 +* Motion detection 48 +* Built-in Buzzer 49 +* AT Commands to change parameters 50 +* Remote configure parameters via LoRa Downlink 51 +* Uplink on periodically 52 +* Datalog feature 53 +* Firmware upgradable via program port 54 +* Programable via Arduino IDE 55 +* 1000mAh li-on rechargeable battery 49 49 50 -== 1.2 Specifications == 51 51 52 52 53 - (% style="color:blue"%)**Micro Controller:**59 +== 1.3 Applications == 54 54 55 -* Espressif ESP32 PICO D4 56 -* MCU: ESP32 PICO D4 57 -* Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE 58 -* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps) 59 -* Integrated SPI flash : 4 MB 60 -* RAM: 448 KB 61 -* EEPROM: 520 KB 62 -* Clock Speed: 32Mhz 63 63 64 - 65 - 66 -(% style="color:blue" %)**Common DC Characteristics:** 67 - 68 -* Supply Voltage: 5V via USB port or Internal li-on battery 69 -* Operating Temperature: -40 ~~ 60°C 70 - 71 - 72 - 73 -(% style="color:blue" %)**LoRa Spec:** 74 - 75 -* Frequency Range, 76 -** Band 1 (HF): 862 ~~ 1020 Mhz 77 -* 168 dB maximum link budget. 78 -* +20 dBm - 100 mW constant RF output vs. 79 -* +14 dBm high efficiency PA. 80 -* Programmable bit rate up to 300 kbps. 81 -* High sensitivity: down to -148 dBm. 82 -* Bullet-proof front end: IIP3 = -12.5 dBm. 83 -* Excellent blocking immunity. 84 -* Low RX current of 10.3 mA, 200 nA register retention. 85 -* Fully integrated synthesizer with a resolution of 61 Hz. 86 -* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation. 87 -* Built-in bit synchronizer for clock recovery. 88 -* Preamble detection. 89 -* 127 dB Dynamic Range RSSI. 90 -* Automatic RF Sense and CAD with ultra-fast AFC. 91 -* Packet engine up to 256 bytes with CRC. 92 -* LoRaWAN 1.0.3 Specification 93 - 94 - 95 - 96 -(% style="color:blue" %)**Battery:** 97 - 98 -* 1000mA Li-on Battery power (for model TrackerD) 99 - 100 - 101 - 102 -(% style="color:blue" %)**Power Consumption** 103 - 104 -* Sleeping Mode: 200uA 105 -* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 106 -* Tracking: max: 38mA 107 - 108 - 109 - 110 - 111 -== 1.3 Features == 112 - 113 - 114 -* LoRaWAN 1.0.3 Class A 115 -* ESP32 PICO D4 116 -* SX1276/78 Wireless Chip 117 -** Arduino IDE Compatible 118 -* Open source hardware / software 119 -* Regular/ Real-time GPS,BLE,WIFI tracking 120 -* Built-in3 axis accelerometer (LIS3DH) 121 -* Humidity / temperature sensor : GXCAS Technology GXHT3X 122 -* Motion sensing capability 123 -* Power Monitoring 124 -* Charging circuit via USB port 125 -* 1000mA Li-on Battery power 126 -* Tri-color LED, Alarm button 127 -* Datalog 128 - 129 - 130 - 131 - 132 -== 1.4 Applications == 133 - 134 - 135 135 * Logistics and Supply Chain Management 136 136 * Human tracking 137 137 138 138 139 139 67 += 2. Use TrackerD in LoRaWAN network = 140 140 141 -= 2.1 Use TrackerD = 142 142 70 +== 2.1 LED == 143 143 144 -== 2.1 How it works? == 145 145 73 +== 2.2 Button == 146 146 147 -TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA. 148 148 76 += 3. Update Firmware = 149 149 150 150 151 -== 2.2Quick guideconnecttoLoRaWANserver==79 +== 3.1 Method 1: Update BIN file == 152 152 153 153 154 - Hereisan examplefor how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]].Below isthe networkstructure,weuse LPS8NasLoRaWANgatewayin thisexample.82 +(% style="color:blue" %)**Step1: **(%%)Connect TrackerD and PC via TypeC cable directly. 155 155 156 156 157 - [[image:1664501652064-326.png]]85 +(% style="color:blue" %)**Step2:**(%%) Install CH9102 driver in the PC. 158 158 159 - 160 - 161 -The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3: 162 - 163 - 164 -(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD. 165 - 166 -Each TrackerD is shipped with a sticker with the default device EUI as below: 167 - 168 - 169 -[[image:1664501677253-891.png]] 170 - 171 - 172 -Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: 173 - 174 - 175 -**__Add APP EUI in the application:__** 176 - 177 - 178 -[[image:1664501711466-918.png]] 179 - 180 - 181 - 182 -[[image:1664501721248-725.png]] 183 - 184 - 185 -[[image:1664501734705-405.png]] 186 - 187 - 188 - 189 -**__Add APP KEY and DEV EUI:__** 190 - 191 - 192 -[[image:1664501784668-703.png]] 193 - 194 - 195 - 196 - 197 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch. 198 - 199 - 200 -(% 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. 201 - 202 - 203 -(% style="color:blue" %)**Positioning Mode(SMOD):** 204 - 205 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get GPS location info. 206 -* (% style="color:#037691" %)**BLE ONLY: **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking. 207 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. 208 - 209 -User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 210 - 211 - 212 - 213 -== 2.3 Uplink Payload == 214 - 215 - 216 -=== 2.3.1 Uplink FPORT~=5, Device Status === 217 - 218 - 219 - 220 -=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning === 221 - 222 - 223 -The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. ) 224 - 225 - 226 -(% border="2" cellspacing="3" style="background-color:#ffffcc; color:green; width:520px" %) 227 -|=(% scope="row" style="width: 69px;" %)((( 228 -**Size** 229 - 230 -**(bytes)** 231 -)))|(% style="width:76px" %)4|(% style="width:87px" %)4|(% style="width:76px" %)2|(% style="width:52px" %)1|(% style="width:88px" %)((( 232 -2 233 - 234 -(optional ) 235 -)))|(% style="width:83px" %)((( 236 -2 237 - 238 -(optional) 239 -))) 240 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 241 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 242 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:83px" %)[[Tem>>||anchor="HTem:"]] 243 - 244 -[[image:1664501958445-288.png]] 245 - 246 - 247 -==== (% style="color:blue" %)Alarm & BAT:(%%) ==== 248 - 249 -(% border="2" style="background-color:#ffffcc; color:green; width:329px" %) 250 -|(% style="width:72px" %)**Size(bit)**|(% style="width:67px" %)1 bit|(% style="width:118px" %)1bit|(% style="width:63px" %)14 bits 251 -|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 252 - 253 -==== (% style="color:blue" %)FLAG:(%%) ==== 254 - 255 -(% border="2" style="background-color:#ffffcc; color:green; width:332px" %) 256 -|(% style="width:79px" %)**Size(bit)**|(% style="width:55px" %)2 bits|(% style="width:47px" %)1bit|(% style="width:140px" %)5 bits 257 -|(% style="width:79px" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H2.3.4BLEpositioningPayload28Fport229"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 258 - 259 -**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 260 - 261 - 262 -==== (% style="color:blue" %)Location info:(%%) ==== 263 - 264 -* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 265 -* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 266 - 267 -(% style="color:red" %)**Important note:** 268 - 269 -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. 270 - 271 -2. In firmware version v1.5, Roll & Pitch is disabled by default. 272 - 273 -3. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 274 - 275 - 276 -[[image:1664502116362-706.png]] 277 - 278 - 279 - 280 -4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 281 - 282 -[[image:1664502166010-515.png]] 283 - 284 - 285 - 286 -==== (% style="color:blue" %)Alarm:(%%) ==== 287 - 288 - 289 -Example: 0x4B & 0x40 >> 6 = 0x01 290 - 291 - 292 -==== (% style="color:blue" %)BAT:(%%) ==== 293 - 294 - 295 -Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 296 - 297 -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: \ 298 - 299 - 300 -* > 4.0v : 80% ~~ 100% 301 -* 3.85v ~~3.99v: 60% ~~ 80% 302 -* 3.70v ~~ 3.84v: 40% ~~ 60% 303 -* 3.40v ~~ 3.69v: 20% ~~ 40% 304 -* < 3.39v: 0~~20% 305 - 306 -==== (% style="color:blue" %)LON:(%%) ==== 307 - 308 - 309 -Enable/Disable LED activity for uplink 310 - 311 -0x00: Disable LED indicator. 312 - 313 -0x01: Enable LED indicator (Default Value) 314 - 315 - 316 -==== (% style="color:blue" %)Hum:(%%) ==== 317 - 318 -0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 319 - 320 - 321 -==== (% style="color:blue" %)Tem:(%%) ==== 322 - 323 -011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 324 - 325 - 326 - 327 - 328 -=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 329 - 330 - 331 - 332 -=== 2.3.4 BLE positioning Payload(Fport2) === 333 - 334 - 335 -Different MODE has different payload: 336 - 337 -**MODE=2** 338 - 339 -(% border="2" style="background-color:#ffffcc; color:green; width:491px" %) 340 -|(% style="width:70px" %)((( 341 -**Size** 342 - 343 -**(bytes)** 344 -)))|(% style="width:44px" %)16|(% style="width:61px" %)4|(% style="width:63px" %)4|(% style="width:71px" %)2|(% style="width:50px" %)4|(% style="width:47px" %)2|(% style="width:15px" %)1 345 -|(% style="width:70px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 346 -iBeacon MAJOR 347 -)))|(% style="width:63px" %)((( 348 -iBeacon MINOR 349 -)))|(% style="width:71px" %)((( 350 -iBeacon Measured Power 351 -)))|(% style="width:50px" %)((( 352 -iBeacon RSSI 353 -)))|(% style="width:47px" %)((( 354 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 355 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 356 - 357 -[[image:1664502425687-834.png]] 358 - 359 - 360 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 361 -* (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 362 -* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 363 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 364 -* (% style="color:#037691" %)**MINOR:** (%%)The MAJOR from the strongest iBeacon. 365 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 366 -* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 367 - 368 -=== 2.3.5 Add Payload format in TTN V3 === 369 - 370 - 371 -In TTN V3, use can add a custom payload so it shows friendly. 372 - 373 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 374 - 375 - 376 -[[image:1664502649601-895.png]] 377 - 378 - 379 -Add the decoder from this link: 380 - 381 - 382 -Save the change the uplink message will be parsed. As below: 383 - 384 -[[image:1664502676891-606.png]] 385 - 386 - 387 - 388 -== 2.4 Integrate with Datacake == 389 - 390 - 391 -After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot. 392 - 393 -Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]] 394 - 395 - 396 -[[image:1664502695771-538.png]] 397 - 398 - 399 - 400 -== 2.5 Integrate with Tago == 401 - 402 - 403 -After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot. 404 - 405 -Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]] 406 - 407 - 408 -[[image:1664502715371-321.png]] 409 - 410 - 411 - 412 -== 2.6 Alarm Mode == 413 - 414 - 415 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 416 - 417 - 418 -Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode. 419 - 420 - 421 -Two ways to exit alarm mode: 422 - 423 -* Server send a downlink command to exit. 424 -* User fast press the RED button 10 times. 425 - 426 -When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false. 427 - 428 - 429 - 430 -== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- == 431 - 432 - 433 - 434 -== 2.8 LED Status == 435 - 436 - 437 -(% border="2" style="background-color:#ffffcc; color:green; width:636px" %) 438 -|(% style="width:157px" %)**Event**|(% style="width:271px" %)**Action**|(% style="width:202px" %)**AT+LON to control on/off** 439 -|(% 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 440 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 441 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 442 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 443 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes 444 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 445 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 446 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes 447 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes 448 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 449 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 450 - 451 -== 2.9 Button Function == 452 - 453 - 454 -(% style="color:green" %)**RESET button:** 455 - 456 -[[image:1664502835802-546.png]] 457 - 458 -Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 459 - 460 - 461 -(% style="color:red" %)**RED button:** 462 - 463 -[[image:1664502854406-763.png]] 464 - 465 - 466 -(% border="2" style="background-color:#ffffcc; color:green; width:627px" %) 467 -|(% style="width:135px" %)**Function**|(% style="width:220px" %)**Action**|(% style="width:265px" %)**Description** 468 -|(% 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"]] 469 -|(% 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 470 -|(% 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. 471 - 472 - 473 - 474 -== 2.10 USB Port Function == 475 - 476 - 477 -The USB interface of TrackerD has below functions: 478 - 479 -* Power on the device 480 -* Recharge the battery 481 -* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 482 -* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 483 - 484 - 485 - 486 -= 3. Configure TrackerD via AT command or LoRaWAN downlink = 487 - 488 - 489 -User can configure TrackerD via AT Command or LoRaWAN Downlink. 490 - 491 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 492 - 493 - 494 - 495 -== 3.1 Access AT Command == 496 - 497 - 498 -TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below. 499 - 500 - 501 -[[image:1664502999401-486.png]] 502 - 503 - 504 -In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands: 505 - 506 - 507 -[[image:1664503022490-662.png]] 508 - 509 - 510 - 511 -[[image:1664503035713-500.png]] 512 - 513 - 514 - 515 -[[image:1664503047675-651.png]] 516 - 517 - 518 - 519 -== 3.2 Command Set == 520 - 521 - 522 -=== 3.2.1 Set Transmit Interval === 523 - 524 - 525 -Set device uplink interval. 526 - 527 -* (% style="color:blue" %)**AT Command:** 528 - 529 -(% style="color:#037691" %)**AT+TDC=xxx ** 530 - 531 -Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 532 - 533 - 534 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):** 535 - 536 -(% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 537 - 538 - 539 - 540 -=== 3.2.2 Set Alarm Packet transmission interval === 541 - 542 - 543 -Set alarm packet transmit interval 544 - 545 -* (% style="color:blue" %)**AT Command:** 546 - 547 -(% style="color:#037691" %)**AT+ATDC=xx. ** 548 - 549 -Example: AT+ATDC=60000 **~-~-> ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000 550 - 551 - 552 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):** 553 - 554 -(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 555 - 556 - 557 - 558 -=== 3.2.3 Set Sports Mode Packet transmission interval === 559 - 560 - 561 -Set sports packet transmit interval 562 - 563 -* (% style="color:blue" %)**AT Command:** 564 - 565 -(% style="color:#037691" %)**AT+MTDC=xx. ** 566 - 567 - Example: AT+MTDC=300000 **~-~-> ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 568 - 569 - 570 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 571 - 572 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ MTDC=3000000 573 - 574 - 575 - 576 -=== 3.2.4 Exit Alarm === 577 - 578 - 579 -Server send downlink command to exit Alarm mode 580 - 581 -* (% style="color:blue" %)**AT Command: No AT Command** 582 - 583 - 584 -* (% style="color:blue" %)**Downlink Payload (prefix 0x02):** 585 - 586 -(% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 587 - 588 - 589 - 590 -=== 3.2.5 Disable/Enable LED flash === 591 - 592 - 593 -Disable/Enable LED for position, downlink and uplink 594 - 595 -* (% style="color:blue" %)**AT Command:** 596 - 597 -(% style="color:#037691" %)**AT+LON=xx. (Disable (0), Enable (1), default:1)** 598 - 599 - Example: AT+LON=0 **~-~-> ** Disable LED for position, downlink and uplink. 600 - 601 - 602 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):** 603 - 604 -(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 605 - 606 - 607 - 608 -=== 3.2.6 Disable/Enable movement detect (Debug Only) === 609 - 610 - 611 -User can use this feature to check and set thread hole of movement detect 612 - 613 -* (% style="color:blue" %)**AT Command:** 614 - 615 -(% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 616 - 617 - Example: AT+ INTWK =1 **~-~-> ** Enable detect movement. 618 - 619 - 620 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 621 - 622 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+ INTWK =1 623 - 624 - 625 - 626 -=== 3.2.7 Set Positioning Mode === 627 - 628 - 629 -SMOD define the how TrackerD scan and uplink date. 630 - 631 -GPS室外定位模式: 设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 632 - 633 -BLE室内定位模式: 设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 634 - 635 -GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 636 - 637 -运动模式: 设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 638 - 639 - 640 - 641 -* (% style="color:blue" %)**AT Command:** 642 - 643 -(% style="color:#037691" %)**AT+SMOD=xx. ** 644 - 645 - 646 - **Example:** 647 - 648 - AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum 649 - 650 - AT+ SMOD =1,1 **~-~->** GPS +BAT State 651 - 652 - AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 653 - 654 - 655 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 656 - 657 -(% style="color:#037691" %)**0xA5 01 00** (%%) ~/~/ Same as AT+ SMOD =1,0 658 - 659 - 660 - 661 -=== 3.2.8 Set MAX GPS position time === 662 - 663 - 664 -Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude. 665 - 666 - 667 -If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink. 668 - 669 - 670 -* (% style="color:blue" %)**AT Command:** 671 - 672 -(% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 673 - 674 -Example: AT+FTIME=150 675 - 676 - 677 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** 678 - 679 -(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 680 - 681 - 682 - 683 -=== 3.3.9 Set PDOP value for GPS fix accuracy === 684 - 685 - 686 -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. 687 - 688 - 689 -A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 690 - 691 - 692 -* (% style="color:blue" %)**AT Command:** 693 - 694 -(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~-> ** Set PDOP to 2.5 695 - 696 - 697 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):** 698 - 699 -(% style="color:#037691" %)**0xAD 00 0A** (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1) 700 - 701 -(% style="color:#037691" %)**0xAD 00 19** (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5) 702 - 703 -(% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7) 704 - 705 - 706 - 707 -Disable/Enable the confirmation mode 708 - 709 -* (% style="color:blue" %)**AT Command:** 710 - 711 -(% style="color:#037691" %)**AT+CFM=xx. ** 712 - 713 - 714 -**~ Example:** 715 - 716 - AT+ CFM=0 **~-~-> ** Disable confirmation 717 - 718 - AT+ CFM=1 **~-~-> ** Enable confirmation 719 - 720 - 721 -* (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 722 - 723 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD =1 724 - 725 - 726 - 727 -= 4. Setting for Different Scenarios = 728 - 729 - 730 - 731 -= 5. Upload Firmware = 732 - 733 - 734 -== 5.1 Firmware Change Log == 735 - 736 - 737 -**[[See this link>>url:https://github.com/dragino/TrackerD]]** 738 - 739 - 740 - 741 -== 5.2 How to upgrade firmware == 742 - 743 - 744 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 745 - 746 - 747 -(% style="color:blue" %)**Step1: **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD. 748 - 749 - 750 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC. 751 - 752 752 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager. 753 753 754 754 755 -(% style="color:blue" %)**Step3:**(%%) : [[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]90 +(% style="color:blue" %)**Step3:**(%%) Download and Install Flash Tool from : 756 756 92 +[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]] 757 757 94 + 758 758 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 759 759 97 +[[image:image-20220712083115-1.png||height="238" width="1071"]] 760 760 761 -[[image:1664503563660-578.png]] 762 762 100 +[[image:image-20220712083115-2.png]] 763 763 764 -[[image:1664503574618-659.png]] 765 765 103 +(% style="color:blue" %)**Step5:** (%%) Select the bin file , com port and proper SPI configure. and click Start. 766 766 767 - (%style="color:blue"%)**Step5:** (%%) Selectthefirmware file (.bin format), comportandproper SPIconfigure. Clink Start.Bin file location:105 +Bin file can be downloaded from: [[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 768 768 769 -[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 770 770 108 +**Users need to use below files:** 771 771 772 -Users need to use below files: 110 +* boot_app0.bin @0e000 111 +* ESP_LORA-eeprom-class.bin @ 0x10000 773 773 774 - boot_app0.bin @0e000113 +[[image:image-20220712083115-3.png]] 775 775 776 -ESP_LORA-eeprom-class.bin @ 0x10000 777 777 116 +After upgrade finish, it will shows below: 778 778 779 -[[image:1 664503593459-435.png]]118 +[[image:image-20220712083115-4.png]] 780 780 781 781 782 782 783 - Afterupgradefinish,it will show finish as below:122 += 4. FAQ = 784 784 785 - [[image:1664503611848-385.png]]124 +== 4.1 Where can i find the source files for TrackerD? == 786 786 787 787 127 +Software & Hardware Source: [[https:~~/~~/github.com/dragino/TrackerD >>https://github.com/dragino/TrackerD]] 788 788 789 -= 6. Developer Guide = 790 790 791 791 792 -= =6.1Compile SourceCode==131 += 5. Order Info = 793 793 794 794 795 -=== 6.1.1 Set up ARDUINO compile environment === 796 - 797 - 798 -* Download the latest Arduino software (IDE) from the Arduino official website: [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]] 799 - 800 -Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]] 801 - 802 - 803 -[[image:1664503635019-941.png]] 804 - 805 - 806 -* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) find the esp32 information and install it. 807 - 808 -[[image:1664503715811-892.png]] 809 - 810 - 811 - 812 -* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]] 813 - 814 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 815 - 816 - 817 -[[image:1664503752288-974.png]] 818 - 819 - 820 - 821 -== 6.2 Source Code == 822 - 823 - 824 -* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 825 - 826 -[[image:1664503794261-827.png]] 827 - 828 - 829 - 830 -* (% style="color:blue" %)**Click to upload** 831 - 832 -[[image:1664503808294-336.png]] 833 - 834 - 835 - 836 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 837 - 838 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 839 - 840 - 841 - 842 -= 7. FAQ = 843 - 844 - 845 -== 7.1 How to change the LoRa Frequency Bands/Region? == 846 - 847 - 848 -User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 849 - 850 - 851 - 852 -== 7.2 What is the pin mapping for the USB program cable? == 853 - 854 - 855 -[[image:1664499635206-262.png]] 856 - 857 - 858 - 859 -(% border="2" style="background-color:#ffffcc; color:green; width:314px" %) 860 -|(% style="width:118px" %)**Pin**|(% style="width:67px" %)**Color**|(% style="width:123px" %)**USB Pin** 861 -|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC 862 -|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A) 863 -|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A) 864 -|(% style="width:118px" %)A1,B1,A12,B12|(% style="width:67px" %)Black|(% style="width:123px" %)GND 865 -|(% style="width:118px" %)A5|(% style="width:67px" %)Purple|(% style="width:123px" %)MTDC/GOIO13 866 -|(% style="width:118px" %)B5|(% style="width:67px" %)Blue|(% style="width:123px" %)MTDC/GPIO12 867 -|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 868 -|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 869 - 870 -= 8. Order Info = 871 - 872 - 873 873 Part Number: (% style="color:blue" %)**TrackerD-XXX** 874 874 875 875 (% style="color:blue" %)**XXX**(%%): The default frequency band 876 876 877 877 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 139 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470 878 878 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 879 879 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 880 880 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 ... ... @@ -882,28 +882,27 @@ 882 882 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 883 883 * (% style="color:red" %)**US915**(%%): Default frequency band US915 884 884 885 -= 9. Packing Info = 886 886 148 += 6. Packing Info = 887 887 150 + 888 888 **Package Includes**: 889 889 890 -* TrackerD LoRaWAN GPS/BLE Tracker x 1 891 -* USB recharge & program cable x 1 153 +* TrackerD x 1 154 +* Rechargeable cable x 1 155 +* Program Cable x 1 892 892 893 893 **Dimensions and Weight**: 894 894 895 -* Device Size: 85 x 48 x 15 cm896 -* Weight: 5 0g159 +* Device Size: 85 x 48 x 15 mm/pcs 160 +* Weight: 55g/pcs 897 897 898 -= 10. Support = 899 899 900 900 901 -* 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. 902 -* 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]] 164 += 7. Reference = 903 903 904 -= 11. Reference = 905 905 906 - 907 907 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 908 908 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 909 909 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 170 +
- 1664499635206-262.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.8 KB - Content
- 1664499921684-770.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.9 KB - Content
- 1664501652064-326.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.9 KB - Content
- 1664501677253-891.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -202.7 KB - Content
- 1664501711466-918.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -62.0 KB - Content
- 1664501721248-725.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.6 KB - Content
- 1664501734705-405.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.1 KB - Content
- 1664501784668-703.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -62.0 KB - Content
- 1664501958445-288.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.1 KB - Content
- 1664502116362-706.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.0 KB - Content
- 1664502166010-515.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -41.3 KB - Content
- 1664502425687-834.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.2 KB - Content
- 1664502649601-895.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -59.2 KB - Content
- 1664502676891-606.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.3 KB - Content
- 1664502695771-538.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -54.7 KB - Content
- 1664502715371-321.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -79.9 KB - Content
- 1664502835802-546.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -37.8 KB - Content
- 1664502854406-763.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.3 KB - Content
- 1664502999401-486.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -916.7 KB - Content
- 1664503022490-662.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -133.6 KB - Content
- 1664503035713-500.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -354.0 KB - Content
- 1664503047675-651.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -199.1 KB - Content
- 1664503563660-578.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.1 KB - Content
- 1664503574618-659.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -139.8 KB - Content
- 1664503593459-435.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -183.3 KB - Content
- 1664503611848-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -175.9 KB - Content
- 1664503635019-941.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -161.8 KB - Content
- 1664503715811-892.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.6 KB - Content
- 1664503752288-974.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -112.6 KB - Content
- 1664503794261-827.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.5 KB - Content
- 1664503808294-336.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -161.6 KB - Content
- 1664503824081-592.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -77.4 KB - Content
- 1664503831430-500.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -147.8 KB - Content
- 1664505654417-133.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.5 KB - Content