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, 19 removed)
- 1665301570342-765.png
- 1665301636888-168.png
- 1665301687277-443.png
- 1665301786397-168.png
- 1667288597595-714.png
- image-20221006181316-1.png
- image-20221006181357-2.png
- image-20221009160220-1.png
- image-20221009160309-2.png
- image-20221009234629-1.png
- image-20221009234703-2.png
- image-20221024105643-1.png
- image-20221024105643-2.png
- image-20221102140621-1.png
- image-20221102140638-2.png
- image-20221102140704-3.png
- image-20221102140712-4.png
- image-20221102140748-5.png
- image-20221102140801-6.png
Details
- Page properties
-
- Content
-
... ... @@ -61,11 +61,13 @@ 61 61 * EEPROM: 520 KB 62 62 * Clock Speed: 32Mhz 63 63 64 + 64 64 (% style="color:blue" %)**Common DC Characteristics:** 65 65 66 66 * Supply Voltage: 5V via USB port or Internal li-on battery 67 67 * Operating Temperature: -40 ~~ 60°C 68 68 70 + 69 69 (% style="color:blue" %)**LoRa Spec:** 70 70 71 71 * Frequency Range, ... ... @@ -87,10 +87,12 @@ 87 87 * Packet engine up to 256 bytes with CRC. 88 88 * LoRaWAN 1.0.3 Specification 89 89 92 + 90 90 (% style="color:blue" %)**Battery:** 91 91 92 92 * 1000mA Li-on Battery power (for model TrackerD) 93 93 97 + 94 94 (% style="color:blue" %)**Power Consumption** 95 95 96 96 * Sleeping Mode: 200uA ... ... @@ -189,132 +189,42 @@ 189 189 (% 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. 190 190 191 191 196 +(% style="color:blue" %)**Positioning Mode(SMOD):** 192 192 193 -== 2.3 Positioning Mode(SMOD) == 198 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get GPS location info. 199 +* (% style="color:#037691" %)**BLE ONLY: **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking. 200 +* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. 194 194 202 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 195 195 196 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 197 197 198 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 199 -* (% 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. 200 -* (% 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. 201 201 202 - Userscanswitchmodes by [[changingSMOD>>||anchor="H3.2.7SetPositioningMode"]].206 +== 2.3 Uplink Payload == 203 203 204 204 209 +=== 2.3.1 Uplink FPORT~=5, Device Status === 205 205 206 -== 2.4 Uplink Payload == 207 207 208 208 209 -=== 2. 4.1Uplink FPORT~=5,Device Status ===213 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning === 210 210 211 211 212 - Uplink the deviceconfigureswithFPORT=5.OnceTrackerDJoinedthenetwork, itwilluplinkthismessage totheserver.Afterthe firstuplink,TrackerDwilluplink DeviceStatusevery12hours.216 +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. ) 213 213 214 -Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 215 215 216 - 217 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 218 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1 219 -|=(% 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 220 - 221 -[[image:1665301570342-765.png]] 222 - 223 - 224 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 225 - 226 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13 227 - 228 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version 229 - 230 -(% style="color:#037691" %)**Frequency Band**: 231 - 232 -*0x01: EU868 233 - 234 -*0x02: US915 235 - 236 -*0x03: IN865 237 - 238 -*0x04: AU915 239 - 240 -*0x05: KZ865 241 - 242 -*0x06: RU864 243 - 244 -*0x07: AS923 245 - 246 -*0x08: AS923-1 247 - 248 -*0x09: AS923-2 249 - 250 -*0x0a: AS923-3 251 - 252 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 253 - 254 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 255 - 256 - 257 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 258 - 259 -Use can also get the Device Status uplink through the downlink command: 260 - 261 - 262 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 263 - 264 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 265 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 266 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 267 - 268 -(% style="color:blue" %)** SMOD:** 269 - 270 -(% style="color:red" %)** 1 :** (%%) GPS ONLY 271 - 272 -(% style="color:red" %)** 2 :** (%%) BLE ONLY 273 - 274 -(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 275 - 276 - 277 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 278 - 279 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 280 - 281 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 282 - 283 - 284 -(% style="color:blue" %)** BLE_Settings:** 285 - 286 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 287 - 288 -(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 289 - 290 - 291 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 292 - 293 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 294 -|=(% 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 295 -|=(% 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"]] 296 - 297 - 298 - 299 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 300 - 301 - 302 -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, 303 - 304 - 305 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 306 -|=(% scope="row" style="width: 60px;" %)((( 219 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 220 +|=(% scope="row" style="width: 50px;" %)((( 307 307 **Size(bytes)** 308 -)))|(% style="width: 50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((309 -2 310 -)))|(% style="width: 30px" %)(((311 -2 222 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)((( 223 +2(optional) 224 +)))|(% style="width:87px" %)((( 225 +2(optional) 312 312 ))) 313 313 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 314 314 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 315 -)))|(% style="width: 73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]229 +)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 316 316 317 -[[image:1665 301636888-168.png]]231 +[[image:1664501958445-288.png]] 318 318 319 319 320 320 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -325,9 +325,9 @@ 325 325 326 326 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 327 327 328 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width: 120px" %)329 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width: 30px" %)2bits|(% style="width:30px" %)1bit330 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 242 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 243 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits 244 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 331 331 332 332 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 333 333 ... ... @@ -337,18 +337,23 @@ 337 337 * Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 338 338 * Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 339 339 254 + 255 + 340 340 (% style="color:red" %)**Important note:** 341 341 342 342 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. 343 343 344 -2. In thismode, the total payloadwill be15 bytes, whileUS915/AU915DR0 acceptsonly 11 bytes payload.Inthiscase, the payloadon server willbeignore andshows as below:260 +2. In firmware version v1.5, Roll & Pitch is disabled by default. 345 345 262 +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: 346 346 264 + 347 347 [[image:1664502116362-706.png]] 348 348 349 349 350 -3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 351 351 269 +4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 270 + 352 352 [[image:1664502166010-515.png]] 353 353 354 354 ... ... @@ -355,15 +355,15 @@ 355 355 356 356 ==== (% style="color:blue" %)**Alarm:**(%%) ==== 357 357 358 - **Example:**0x4B & 0x40 >> 6 = 0x01277 +Example: 0x4B & 0x40 >> 6 = 0x01 359 359 360 360 361 361 ==== (% style="color:blue" %)**BAT:**(%%) ==== 362 362 363 - **Example:**0x4B45& 0x3FFF ⇒ 2885(mV).282 +Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 364 364 365 365 ((( 366 -The battery info shows the battery voltage,User can usethebelow mapping to indicate the battery in percentage: \285 +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: \ 367 367 ))) 368 368 369 369 * > 4.0v : 80% ~~ 100% ... ... @@ -374,33 +374,17 @@ 374 374 375 375 376 376 377 -==== (% style="color:blue" %)**MOD:**(%%) ==== 378 - 379 -**Example: ** (0x60>>6) & 0x3f =1 380 - 381 -**Set the format of GPS data uplink link:** 382 - 383 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 384 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 385 - 386 - 387 -**Set the format of BLE data uplink link:** 388 - 389 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 390 - 391 - 392 392 ==== (% style="color:blue" %)**LON:**(%%) ==== 393 393 394 -**Example:** (0x60>>5) & 0x01=1. 395 395 396 396 Enable/Disable LED activity for uplink 397 397 398 398 ((( 399 - (% style="color:#037691" %)**0x00:**(%%)Disable LED indicator.302 +0x00: Disable LED indicator. 400 400 ))) 401 401 402 402 ((( 403 - (% style="color:#037691" %)**0x01:**(%%)Enable LED indicator (Default Value)306 +0x01: Enable LED indicator (Default Value) 404 404 ))) 405 405 406 406 ... ... @@ -415,57 +415,15 @@ 415 415 416 416 417 417 418 -=== 2. 4.33,RealtimeGNSS Positioning(Default Mode)===321 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 419 419 420 420 421 -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) 422 422 325 +=== 2.3.4 BLE positioning Payload(Fport2) === 423 423 424 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 425 -|=(% scope="row" style="width: 60px;" %)((( 426 -**Size(bytes)** 427 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 428 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 429 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 430 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 431 431 432 -(% class="wikigeneratedid" %) 433 -[[image:1665301687277-443.png]] 328 +Different MODE has different payload: (% style="color:blue" %)**MODE=2** 434 434 435 - 436 - 437 -=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 438 - 439 - 440 -Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-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. 441 - 442 - 443 -(% style="color:red" %)**Note for this mode:** 444 - 445 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 446 -* 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. 447 -* 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 448 - 449 -The payload is 15 bytes, as below. 450 - 451 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 452 -|=(% scope="row" %)((( 453 -**Size(bytes)** 454 -)))|4|4|2|1|1|1|1|1 455 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 456 - 457 -[[image:image-20221009160309-2.png]] 458 - 459 - 460 - 461 -=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 462 - 463 - 464 -TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink. 465 - 466 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 467 - 468 - 469 469 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 470 470 |=(% scope="row" style="width: 60px;" %)((( 471 471 **Size(bytes)** ... ... @@ -485,7 +485,7 @@ 485 485 [[image:1664502425687-834.png]] 486 486 487 487 488 -* (% style="color:#037691" %)**BAT: ** (%%) 349 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 489 489 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 490 490 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 491 491 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. ... ... @@ -495,35 +495,11 @@ 495 495 496 496 497 497 498 -=== 2. 4.6UplinkFPORT~=8,WiFiPositioningwith StrongestWiFiSSID===359 +=== 2.3.5 Add Payload format in TTN V3 === 499 499 500 500 501 - TrackerD supports WiFi scansforindoorpositioning. Usercanset[[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]]to **BLEpure** or **GPS/BLE hybrid**soTrackerD will scan WiFi and findthestrongestWiFi info anduplink.362 +In TTN V3, use can add a custom payload so it shows friendly. 502 502 503 - 504 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 505 -|=(% scope="row" style="width: 60px;" %)((( 506 -**Size(bytes)** 507 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 508 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 509 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 510 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 511 - 512 -(% class="wikigeneratedid" %) 513 -[[image:1667288597595-714.png||height="212" width="1151"]] 514 - 515 - 516 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 517 -* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 518 -* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 519 - 520 - 521 - 522 -=== 2.4.7 Add Payload format in TTN V3 === 523 - 524 - 525 -In TTN V3, user can add a custom payload so it shows friendly. 526 - 527 527 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 528 528 529 529 ... ... @@ -530,9 +530,8 @@ 530 530 [[image:1664502649601-895.png]] 531 531 532 532 533 -Add the decoder from this link: 370 +Add the decoder from this link: 534 534 535 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 536 536 537 537 Save the change the uplink message will be parsed. As below: 538 538 ... ... @@ -540,49 +540,41 @@ 540 540 541 541 542 542 543 -== 2. 5Integrate with Datacake ==379 +== 2.4 Integrate with Datacake == 544 544 545 545 382 +((( 546 546 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. 384 +))) 547 547 386 +((( 548 548 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]] 388 +))) 549 549 390 + 550 550 [[image:1664502695771-538.png]] 551 551 552 552 553 553 554 -== 2. 6Integrate with Tago ==395 +== 2.5 Integrate with Tago == 555 555 556 556 557 -After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot. 398 +((( 399 +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. 400 +))) 558 558 402 +((( 559 559 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]] 404 +))) 560 560 561 561 562 - 563 563 [[image:1664502715371-321.png]] 564 564 565 565 566 566 567 -== 2. 7DatalogFeature ==411 +== 2.6 Alarm Mode == 568 568 569 569 570 -total 273 entries,by default, 571 - 572 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 573 - 574 -Example use case. 575 - 576 -[[image:image-20221009234703-2.png||height="328" width="899"]] 577 - 578 - 579 -[[image:image-20221009234629-1.png||height="390" width="577"]] 580 - 581 - 582 - 583 -== 2.8 Alarm Mode == 584 - 585 - 586 586 ((( 587 587 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 588 588 ))) ... ... @@ -589,7 +589,7 @@ 589 589 590 590 591 591 ((( 592 -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 salert mode.420 +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. 593 593 ))) 594 594 595 595 ... ... @@ -597,7 +597,7 @@ 597 597 Two ways to exit alarm mode: 598 598 ))) 599 599 600 -* Server send sa downlink command to exit.428 +* Server send a downlink command to exit. 601 601 * User fast press the RED button 10 times. 602 602 603 603 ((( ... ... @@ -606,16 +606,13 @@ 606 606 607 607 608 608 609 -== 2. 9Transport Mode ==437 +== 2.7 Sports Mode == 610 610 611 611 612 -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. 613 613 441 +== 2.8 LED Status == 614 614 615 615 616 -== 2.10 LED Status == 617 - 618 - 619 619 (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 620 620 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 621 621 |(% 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 ... ... @@ -632,7 +632,7 @@ 632 632 633 633 634 634 635 -== 2. 11Button Function ==460 +== 2.9 Button Function == 636 636 637 637 638 638 (% style="color:blue" %)**RESET button:** ... ... @@ -647,8 +647,8 @@ 647 647 [[image:1664502854406-763.png]] 648 648 649 649 650 -(% border="1" style="background-color:#ffffcc; color:green; width:5 10px" %)651 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 20 5px;" %)**Action**|=(% style="width: 205px;" %)**Description**475 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 476 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description** 652 652 |(% 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"]] 653 653 |(% 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 654 654 |(% 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. ... ... @@ -655,7 +655,7 @@ 655 655 656 656 657 657 658 -== 2.1 2USB Port Function ==483 +== 2.10 USB Port Function == 659 659 660 660 661 661 The USB interface of TrackerD has below functions: ... ... @@ -691,9 +691,11 @@ 691 691 [[image:1664503022490-662.png]] 692 692 693 693 519 + 694 694 [[image:1664503035713-500.png]] 695 695 696 696 523 + 697 697 [[image:1664503047675-651.png]] 698 698 699 699 ... ... @@ -737,16 +737,16 @@ 737 737 738 738 739 739 740 -=== 3.2.3 Set Transport Mode Packet transmission interval ===567 +=== 3.2.3 Set Sports Mode Packet transmission interval === 741 741 742 742 743 -Set TransportModepacket transmit interval570 +Set sports packet transmit interval 744 744 745 745 * (% style="color:blue" %)**AT Command:** 746 746 747 747 (% style="color:#037691" %)**AT+MTDC=xx. ** 748 748 749 -Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds inTransport mode, Default Value: 300000576 +Example: AT+MTDC=300000 **~-~-> ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 750 750 751 751 752 752 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** ... ... @@ -786,16 +786,16 @@ 786 786 787 787 788 788 789 -=== 3.2.6 Disable/Enable TransportMode ===616 +=== 3.2.6 Disable/Enable movement detect (Debug Only) === 790 790 791 791 792 -User scan use this feature to enable/disableTransportMode.619 +User can use this feature to check and set thread hole of movement detect 793 793 794 794 * (% style="color:blue" %)**AT Command:** 795 795 796 796 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 797 797 798 -Example: AT+ INTWK =1 **~-~-> ** Enable TransportMode.625 +Example: AT+ INTWK =1 **~-~-> ** Enable detect movement. 799 799 800 800 801 801 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** ... ... @@ -807,40 +807,35 @@ 807 807 === 3.2.7 Set Positioning Mode === 808 808 809 809 810 -SMOD define how TrackerD scan and uplink dat a:637 +SMOD define the how TrackerD scan and uplink date. 811 811 639 +GPS室外定位模式: 设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 812 812 813 - *(%style="color:blue" %)**AT Command:**641 +BLE室内定位模式: 设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 814 814 815 - (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**643 +GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 816 816 817 - (%style="color:#037691" %)** aa:**645 +运动模式: 设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 818 818 819 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 820 -* (% 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. 821 -* (% 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. 822 822 823 -(% style="color:#037691" %)**bb:** 824 824 825 -* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 826 -* (% style="color:red" %)**1 :**(%%) GPS +BAT State 649 +* (% style="color:blue" %)**AT Command:** 827 827 828 -(% style="color:#037691" %)** cc:**651 +(% style="color:#037691" %)**AT+SMOD=xx. ** 829 829 830 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 831 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 832 832 833 - (%style="color:blue" %)**Example:**654 + **Example:** 834 834 835 - AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 836 - AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 837 - AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 838 - AT+ SMOD =2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 656 + AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum 839 839 658 + AT+ SMOD =1,1 **~-~->** GPS +BAT State 840 840 660 + AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 661 + 662 + 841 841 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 842 842 843 -(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+ SMOD =1,0,0665 +(% style="color:#037691" %)**0xA5 01 00** (%%) ~/~/ Same as AT+ SMOD =1,0 844 844 845 845 846 846 ... ... @@ -857,7 +857,7 @@ 857 857 858 858 (% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 859 859 860 - **Example:**AT+FTIME=150682 +Example: AT+FTIME=150 861 861 862 862 863 863 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** ... ... @@ -866,7 +866,7 @@ 866 866 867 867 868 868 869 -=== 3. 2.9 Set PDOP value for GPS fix accuracy ===691 +=== 3.3.9 Set PDOP value for GPS fix accuracy === 870 870 871 871 872 872 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. ... ... @@ -894,7 +894,7 @@ 894 894 895 895 * (% style="color:blue" %)**AT Command:** 896 896 897 -(% style="color:#037691" %)**AT+CFM=xx** 719 +(% style="color:#037691" %)**AT+CFM=xx. ** 898 898 899 899 900 900 **~ Example:** ... ... @@ -910,79 +910,6 @@ 910 910 911 911 912 912 913 -=== 3.2.10 Auto Send None-ACK messages === 914 - 915 - 916 -TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message. 917 - 918 - 919 -* (% style="color:blue" %)**AT Command: AT+PNACKMD** 920 - 921 -The default factory setting is 0. 922 - 923 - 924 -**Command Example Function Response:** 925 - 926 -(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 927 - 928 - 929 -* (% style="color:blue" %)**Downlink Command: 0x34** 930 - 931 -Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 932 - 933 - 934 - 935 -=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 936 - 937 - 938 -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. 939 - 940 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 941 - 942 -(% style="color:blue" %)**AT Command:** 943 - 944 - (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 945 - 946 - (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 947 - 948 - 949 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)** 950 - 951 -Example: 0xA5010203040506 ~/~/ Set BLEMASK to 123456 952 - 953 - 954 -=== 3.2.12 Set WiFIMASK to filter WiFi SSID === 955 - 956 - 957 -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. 958 - 959 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 960 - 961 -(% style="color:blue" %)**AT Command:** 962 - 963 - (% style="color:#037691" %)**AT+ WiFiMASK =123456** (%%) ~/~/ Set WiFiMASK = 123456 964 - 965 - (% style="color:#037691" %)**AT+ WiFiMASK =0** (%%) ~/~/ disable WiFiMASK 966 - 967 - 968 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)** 969 - 970 -Example: 0xA5010203040506 ~/~/ Set WiFiMASK to 123456 971 - 972 - 973 -=== 3.2.13 Disable/Enable Information printing === 974 - 975 - 976 -Users can use this feature to enable/disable Information printing. 977 - 978 -(% style="color:blue" %)**AT Command:** 979 - 980 - 981 -(% style="color:#037691" %)**AT+ SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 982 - 983 -Example: AT+ SHOWID =1 ~-~-> Enable Information printing. 984 - 985 - 986 986 = 4. Setting for Different Scenarios = 987 987 988 988 ... ... @@ -1023,10 +1023,9 @@ 1023 1023 [[image:1664503574618-659.png]] 1024 1024 1025 1025 1026 - 1027 1027 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 1028 1028 1029 -[[https:~~/~~/ github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]777 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1030 1030 1031 1031 1032 1032 Users need to use below files: ... ... @@ -1063,24 +1063,12 @@ 1063 1063 [[image:1664503635019-941.png]] 1064 1064 1065 1065 1066 - 1067 1067 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1068 1068 1069 1069 [[image:1664503715811-892.png]] 1070 1070 1071 1071 1072 -(% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2. 1073 1073 1074 -[[image:image-20221024105643-1.png]] 1075 - 1076 -**~ Figure1** 1077 - 1078 - 1079 -[[image:image-20221024105643-2.png]] 1080 - 1081 - **Figure2** 1082 - 1083 - 1084 1084 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 1085 1085 1086 1086 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: ... ... @@ -1140,54 +1140,8 @@ 1140 1140 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1141 1141 1142 1142 1143 -== 7.3 Notes on using different serial port tools for TrackerD == 1144 1144 1145 1145 1146 -=== **Serial port utility** === 1147 - 1148 - 1149 -Serial port utility requires you to automatically add data streams. 1150 - 1151 -Need to adjust the data stream to RTS/CTS on physical restart. 1152 - 1153 - 1154 -(% class="wikigeneratedid" %) 1155 -[[image:image-20221102140621-1.png]] 1156 - 1157 - 1158 -When using AT commands, the data flow needs to be adjusted to XON/XOFF 1159 - 1160 - 1161 -[[image:image-20221102140638-2.png]] 1162 - 1163 - 1164 - 1165 -=== **SecureCRT** === 1166 - 1167 - 1168 -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. 1169 - 1170 - 1171 -[[image:image-20221102140704-3.png]] 1172 - 1173 - 1174 -[[image:image-20221102140712-4.png]] 1175 - 1176 - 1177 - 1178 -=== **PUTTY** === 1179 - 1180 - 1181 -[[image:image-20221102140748-5.png]] 1182 - 1183 - 1184 -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. 1185 - 1186 - 1187 -[[image:image-20221102140801-6.png]] 1188 - 1189 - 1190 - 1191 1191 = 8. Order Info = 1192 1192 1193 1193 ... ... @@ -1215,7 +1215,7 @@ 1215 1215 1216 1216 (% style="color:#037691" %)**Dimensions and Weight**: 1217 1217 1218 -* Device Size: 85 x 48 x 15 m m908 +* Device Size: 85 x 48 x 15 cm 1219 1219 * Weight: 50g 1220 1220 1221 1221 ... ... @@ -1234,3 +1234,5 @@ 1234 1234 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1235 1235 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1236 1236 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 927 + 928 +
- 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
- 1667288597595-714.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.9 KB - Content
- image-20221006181316-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -17.7 KB - Content
- image-20221006181357-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.0 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
- image-20221024105643-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -11.3 KB - Content
- image-20221024105643-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.5 KB - Content
- image-20221102140621-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.1 KB - Content
- image-20221102140638-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.8 KB - Content
- image-20221102140704-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -15.5 KB - Content
- image-20221102140712-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -73.2 KB - Content
- image-20221102140748-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.0 KB - Content
- image-20221102140801-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -21.0 KB - Content