Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 143.2
edited by Xiaoling
on 2022/11/22 10:54
Change comment: There is no comment for this version
To version 84.12
edited by Xiaoling
on 2022/10/26 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,6 +14,7 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 +
17 17  == 1.1  What is TrackerD ==
18 18  
19 19  
... ... @@ -45,6 +45,7 @@
45 45  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
46 46  
47 47  
49 +
48 48  == 1.2 Specifications ==
49 49  
50 50  
... ... @@ -95,8 +95,6 @@
95 95  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
96 96  * Tracking: max: 38mA
97 97  
98 -
99 -
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,8 +115,6 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
118 -
119 -
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -123,10 +123,9 @@
123 123  * Logistics and Supply Chain Management
124 124  * Human tracking
125 125  
124 += 2.1 Use TrackerD =
126 126  
127 127  
128 -= 2.  Use TrackerD =
129 -
130 130  == 2.1 How it works? ==
131 131  
132 132  
... ... @@ -133,6 +133,7 @@
133 133  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.
134 134  
135 135  
133 +
136 136  == 2.2 Quick guide to connect to LoRaWAN server ==
137 137  
138 138  
... ... @@ -174,34 +174,34 @@
174 174  **__Add APP KEY and DEV EUI:__**
175 175  
176 176  
177 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
175 +[[image:1664501784668-703.png]]
178 178  
179 179  
180 180  
181 -(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
182 182  
183 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
180 +(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
184 184  
185 -[[image:1664502835802-546.png]]
186 186  
187 -
188 188  (% 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.
189 189  
190 190  
186 +
191 191  == 2.3  Positioning Mode(SMOD) ==
192 192  
193 193  
194 194  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
195 195  
196 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
197 -* (% 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.
198 -* (% 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.
192 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
193 +* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
194 +* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
199 199  
200 200  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
201 201  
202 202  
199 +
203 203  == 2.4  Uplink Payload ==
204 204  
202 +
205 205  === 2.4.1 Uplink FPORT~=5, Device Status ===
206 206  
207 207  
... ... @@ -281,9 +281,7 @@
281 281  
282 282  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
283 283  
284 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 285  
286 -
287 287  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
288 288  
289 289  (% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
... ... @@ -290,8 +290,6 @@
290 290  |=(% 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
291 291  |=(% 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"]]
292 292  
293 -
294 -
295 295  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
296 296  
297 297  
... ... @@ -298,12 +298,12 @@
298 298  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,
299 299  
300 300  
301 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
302 -|=(% scope="row" style="width: 60px;" %)(((
295 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:240px" %)
296 +|=(% scope="row" style="width: 50px;" %)(((
303 303  **Size(bytes)**
304 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
298 +)))|(% style="width:30px" %)4|(% style="width:40px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1|(% style="width:20px" %)(((
305 305  2
306 -)))|(% style="width:30px" %)(((
300 +)))|(% style="width:20px" %)(((
307 307  2
308 308  )))
309 309  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
... ... @@ -319,8 +319,6 @@
319 319  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
320 320  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
321 321  
322 -
323 -
324 324  ==== (% style="color:blue" %)**FLAG:**(%%) ====
325 325  
326 326  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -370,8 +370,6 @@
370 370  * 3.40v ~~ 3.69v:  20% ~~ 40%
371 371  * < 3.39v:  0~~20%
372 372  
373 -
374 -
375 375  ==== (% style="color:blue" %)**MOD:**(%%) ====
376 376  
377 377  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -402,6 +402,7 @@
402 402  )))
403 403  
404 404  
395 +
405 405  ==== (% style="color:blue" %)**Hum:**(%%) ====
406 406  
407 407  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -412,6 +412,7 @@
412 412  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
413 413  
414 414  
406 +
415 415  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
416 416  
417 417  
... ... @@ -418,10 +418,10 @@
418 418  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)
419 419  
420 420  
421 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
422 -|=(% scope="row" style="width: 60px;" %)(((
413 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
414 +|=(% scope="row" style="width: 50px;" %)(((
423 423  **Size(bytes)**
424 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
416 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
425 425  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
426 426  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
427 427  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
... ... @@ -430,6 +430,7 @@
430 430  [[image:1665301687277-443.png]]
431 431  
432 432  
425 +
433 433  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
434 434  
435 435  
... ... @@ -439,12 +439,12 @@
439 439  (% style="color:red" %)**Note for this mode:**
440 440  
441 441  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
442 -* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
435 +* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
443 443  * 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
444 444  
445 445  The payload is 15 bytes, as below.
446 446  
447 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
440 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
448 448  |=(% scope="row" %)(((
449 449  **Size(bytes)**
450 450  )))|4|4|2|1|1|1|1|1
... ... @@ -453,6 +453,7 @@
453 453  [[image:image-20221009160309-2.png]]
454 454  
455 455  
449 +
456 456  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
457 457  
458 458  
... ... @@ -484,41 +484,15 @@
484 484  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
485 485  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
486 486  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
487 -* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
481 +* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
488 488  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
489 489  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
490 490  
485 +=== 2.4.6  Add Payload format in TTN V3 ===
491 491  
492 492  
493 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
488 +In TTN V3, use can add a custom payload so it shows friendly.
494 494  
495 -
496 -TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
497 -
498 -
499 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
500 -|=(% scope="row" style="width: 60px;" %)(((
501 -**Size(bytes)**
502 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
503 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
504 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
505 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
506 -
507 -(% class="wikigeneratedid" %)
508 -[[image:1667288597595-714.png||height="212" width="1151"]]
509 -
510 -
511 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
512 -* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
513 -* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
514 -
515 -
516 -
517 -=== 2.4.7  Add Payload format in TTN V3 ===
518 -
519 -
520 -In TTN V3, user can add a custom payload so it shows friendly.
521 -
522 522  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
523 523  
524 524  
... ... @@ -525,7 +525,6 @@
525 525  [[image:1664502649601-895.png]]
526 526  
527 527  
528 -
529 529  Add the decoder from this link: 
530 530  
531 531  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -535,6 +535,7 @@
535 535  [[image:1664502676891-606.png]]
536 536  
537 537  
505 +
538 538  == 2.5 Integrate with Datacake ==
539 539  
540 540  
... ... @@ -542,10 +542,10 @@
542 542  
543 543  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]]
544 544  
545 -
546 546  [[image:1664502695771-538.png]]
547 547  
548 548  
516 +
549 549  == 2.6 Integrate with Tago ==
550 550  
551 551  
... ... @@ -554,9 +554,11 @@
554 554  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]]
555 555  
556 556  
525 +
557 557  [[image:1664502715371-321.png]]
558 558  
559 559  
529 +
560 560  == 2.7  Datalog Feature ==
561 561  
562 562  
... ... @@ -572,6 +572,7 @@
572 572  [[image:image-20221009234629-1.png||height="390" width="577"]]
573 573  
574 574  
545 +
575 575  == 2.8 Alarm Mode ==
576 576  
577 577  
... ... @@ -586,7 +586,7 @@
586 586  
587 587  
588 588  (((
589 -**Two ways to exit alarm mode:**
560 +Two ways to exit alarm mode:
590 590  )))
591 591  
592 592  * Server sends a downlink command to exit.
... ... @@ -597,6 +597,7 @@
597 597  )))
598 598  
599 599  
571 +
600 600  == 2.9 Transport Mode ==
601 601  
602 602  
... ... @@ -603,16 +603,17 @@
603 603  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.
604 604  
605 605  
578 +
606 606  == 2.10 LED Status ==
607 607  
608 608  
609 -(% border="1.5" style="background-color:#ffffcc; width:500px" %)
582 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
610 610  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
611 611  |(% 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
612 612  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
613 613  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
614 614  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
615 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
588 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
616 616  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
617 617  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
618 618  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -620,8 +620,6 @@
620 620  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
621 621  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
622 622  
623 -
624 -
625 625  == 2.11 Button Function ==
626 626  
627 627  
... ... @@ -637,14 +637,12 @@
637 637  [[image:1664502854406-763.png]]
638 638  
639 639  
640 -(% border="1" style="background-color:#ffffcc; width:510px" %)
641 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
642 -|(% 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.8AlarmMode"]]
611 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
612 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
613 +|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
643 643  |(% 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
644 644  |(% 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.
645 645  
646 -
647 -
648 648  == 2.12 USB Port Function ==
649 649  
650 650  
... ... @@ -655,8 +655,6 @@
655 655  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
656 656  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
657 657  
658 -
659 -
660 660  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
661 661  
662 662  
... ... @@ -665,6 +665,7 @@
665 665  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
666 666  
667 667  
635 +
668 668  == 3.1 Access AT Command ==
669 669  
670 670  
... ... @@ -689,6 +689,7 @@
689 689  
690 690  == 3.2 Command Set ==
691 691  
660 +
692 692  === 3.2.1 Set Transmit Interval ===
693 693  
694 694  
... ... @@ -706,6 +706,7 @@
706 706  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
707 707  
708 708  
678 +
709 709  === 3.2.2 Set Alarm Packet transmission interval ===
710 710  
711 711  
... ... @@ -723,6 +723,7 @@
723 723  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
724 724  
725 725  
696 +
726 726  === 3.2.3 Set Transport Mode Packet transmission interval ===
727 727  
728 728  
... ... @@ -737,9 +737,10 @@
737 737  
738 738  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
739 739  
740 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
711 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
741 741  
742 742  
714 +
743 743  === 3.2.4 Exit Alarm ===
744 744  
745 745  
... ... @@ -752,6 +752,7 @@
752 752  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
753 753  
754 754  
727 +
755 755  === 3.2.5 Disable/Enable LED flash ===
756 756  
757 757  
... ... @@ -769,6 +769,7 @@
769 769  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
770 770  
771 771  
745 +
772 772  === 3.2.6 Disable/Enable Transport Mode ===
773 773  
774 774  
... ... @@ -778,14 +778,15 @@
778 778  
779 779  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
780 780  
781 -Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
755 +Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
782 782  
783 783  
784 784  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
785 785  
786 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
760 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
787 787  
788 788  
763 +
789 789  === 3.2.7 Set Positioning Mode ===
790 790  
791 791  
... ... @@ -798,40 +798,32 @@
798 798  
799 799  (% style="color:#037691" %)** aa:**
800 800  
801 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
776 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
777 +* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
778 +* (% style="color:red" %)**3: GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
802 802  
803 -* (% 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.
804 -
805 -* (% 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.
806 -
807 807  (% style="color:#037691" %)**bb:**
808 808  
809 809  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
810 -
811 811  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
812 812  
813 813  (% style="color:#037691" %)**cc:   **
814 814  
815 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
816 -
817 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
787 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
818 818  
819 819  (% style="color:blue" %)**Example:**
820 820  
821 - AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
791 + AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
792 + AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
793 + AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
822 822  
823 - AT+SMOD=1,1,0 ~-~->  GPS +BAT State
824 824  
825 - AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
826 -
827 - AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
828 -
829 -
830 830  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
831 831  
832 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
798 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
833 833  
834 834  
801 +
835 835  === 3.2.8 Set MAX GPS position time ===
836 836  
837 837  
... ... @@ -838,7 +838,7 @@
838 838  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.
839 839  
840 840  
841 -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.
808 +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.
842 842  
843 843  
844 844  * (% style="color:blue" %)**AT Command:**
... ... @@ -853,6 +853,7 @@
853 853  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
854 854  
855 855  
823 +
856 856  === 3.2.9 Set PDOP value for GPS fix accuracy ===
857 857  
858 858  
... ... @@ -877,7 +877,7 @@
877 877  
878 878  
879 879  
880 -**Disable/Enable the confirmation mode**
848 +Disable/Enable the confirmation mode
881 881  
882 882  * (% style="color:blue" %)**AT Command:**
883 883  
... ... @@ -886,16 +886,17 @@
886 886  
887 887  **~ Example:**
888 888  
889 - AT+CFM=0    **~-~->   ** Disable confirmation
857 + AT+ CFM=0    **~-~->   ** Disable confirmation
890 890  
891 - AT+CFM=1    **~-~->  ** Enable confirmation
859 + AT+ CFM=1    **~-~->  ** Enable confirmation
892 892  
893 893  
894 894  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
895 895  
896 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
864 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
897 897  
898 898  
867 +
899 899  === 3.2.10  Auto Send None-ACK messages ===
900 900  
901 901  
... ... @@ -917,10 +917,11 @@
917 917  Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
918 918  
919 919  
889 +
920 920  === 3.2.11  Set BLEMASK to filter BLE iBeacon ===
921 921  
922 922  
923 -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.
893 +BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
924 924  
925 925  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
926 926  
... ... @@ -930,55 +930,13 @@
930 930  
931 931   (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
932 932  
933 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
934 934  
935 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
904 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
936 936  
906 +Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
937 937  
938 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
939 939  
940 940  
941 -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 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
942 -
943 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
944 -
945 -(% style="color:blue" %)**AT Command:**
946 -
947 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
948 -
949 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
950 -
951 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
952 -
953 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
954 -
955 -
956 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
957 -
958 -
959 -Users can use this feature to enable/disable Information printing.
960 -
961 -(% style="color:blue" %)**AT Command:**
962 -
963 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
964 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
965 -
966 -
967 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
968 -
969 -
970 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
971 -
972 -(% style="color:blue" %)**AT Command:**
973 -
974 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
975 -
976 -
977 -(% style="color:blue" %)**Downlink Payload:0X24**
978 -
979 -Example: 0x24 01 ~/~/ Same as AT+CHE=1
980 -
981 -
982 982  = 4. Setting for Different Scenarios =
983 983  
984 984  
... ... @@ -985,6 +985,7 @@
985 985  
986 986  = 5. Upload Firmware =
987 987  
916 +
988 988  == 5.1 Firmware Change Log ==
989 989  
990 990  
... ... @@ -991,6 +991,7 @@
991 991  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
992 992  
993 993  
923 +
994 994  == 5.2 How to upgrade firmware ==
995 995  
996 996  
... ... @@ -1023,27 +1023,29 @@
1023 1023  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1024 1024  
1025 1025  
1026 -**Users need to use below files:**
956 +Users need to use below files:
1027 1027  
1028 1028  boot_app0.bin @0e000
1029 1029  
1030 -US915.bin @ 0x10000(Select the bin file of the frequency band you need)
960 +ESP_LORA-eeprom-class.bin @ 0x10000
1031 1031  
1032 1032  
1033 -[[image:image-20221118105220-2.png]]
963 +[[image:1664503593459-435.png]]
1034 1034  
1035 1035  
1036 1036  
1037 1037  After upgrade finish, it will show finish as below:
1038 1038  
1039 -[[image:image-20221118105402-4.png]]
969 +[[image:1664503611848-385.png]]
1040 1040  
1041 1041  
1042 1042  
1043 1043  = 6. Developer Guide =
1044 1044  
975 +
1045 1045  == 6.1 Compile Source Code ==
1046 1046  
978 +
1047 1047  === 6.1.1 Set up ARDUINO compile environment ===
1048 1048  
1049 1049  
... ... @@ -1081,6 +1081,7 @@
1081 1081  [[image:1664503752288-974.png]]
1082 1082  
1083 1083  
1016 +
1084 1084  == 6.2 Source Code ==
1085 1085  
1086 1086  
... ... @@ -1101,8 +1101,10 @@
1101 1101  [[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1102 1102  
1103 1103  
1037 +
1104 1104  = 7.  FAQ =
1105 1105  
1040 +
1106 1106  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1107 1107  
1108 1108  
... ... @@ -1109,6 +1109,7 @@
1109 1109  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1110 1110  
1111 1111  
1047 +
1112 1112  == 7.2 What is the pin mapping for the USB program cable? ==
1113 1113  
1114 1114  
... ... @@ -1127,245 +1127,45 @@
1127 1127  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1128 1128  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1129 1129  
1066 += 8.  Order Info =
1130 1130  
1131 1131  
1132 -== 7.3 Notes on using different serial port tools for TrackerD ==
1133 -
1134 -=== 7.3.1  Serial port utility ===
1135 -
1136 -
1137 -Serial port utility requires you to automatically add data streams.
1138 -
1139 -Need to adjust the data stream to RTS/CTS on physical restart.
1140 -
1141 -(% class="wikigeneratedid" %)
1142 -[[image:image-20221102140621-1.png]]
1143 -
1144 -
1145 -
1146 -When using AT commands, the data flow needs to be adjusted to XON/XOFF
1147 -
1148 -[[image:image-20221102140638-2.png]]
1149 -
1150 -
1151 -=== 7.3.2  SecureCRT ===
1152 -
1153 -
1154 -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.
1155 -
1156 -
1157 -[[image:image-20221102140704-3.png]]
1158 -
1159 -
1160 -[[image:image-20221102140712-4.png]]
1161 -
1162 -
1163 -=== 7.3.3  PUTTY ===
1164 -
1165 -
1166 -[[image:image-20221102140748-5.png]]
1167 -
1168 -
1169 -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.
1170 -
1171 -
1172 -[[image:image-20221102140801-6.png]]
1173 -
1174 -
1175 -== 7.4 How to modify source code to compile different frequency band bin file? ==
1176 -
1177 -
1178 -(% class="box infomessage" %)
1179 -(((
1180 -(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1181 -See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1182 -)))
1183 -
1184 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1185 -
1186 -
1187 -[[image:image-20221116111844-1.png||height="227" width="782"]]
1188 -
1189 -
1190 -
1191 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1192 -
1193 -
1194 -[[image:image-20221116111844-2.png||height="262" width="781"]]
1195 -
1196 -
1197 -
1198 -**3. Compile the AS923_JP band, please refer to the intention shown**
1199 -
1200 -
1201 -[[image:image-20221116111844-3.png||height="338" width="746"]]
1202 -
1203 -
1204 -
1205 -**4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.**
1206 -
1207 -
1208 -[[image:image-20221116111844-4.png||height="641" width="739"]]
1209 -
1210 -
1211 -[[image:image-20221116111844-5.png||height="551" width="708"]]
1212 -
1213 -
1214 -= 8  Trouble Shooting =
1215 -
1216 -== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1217 -
1218 -
1219 -(((
1220 -Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1221 -)))
1222 -
1223 -
1224 -== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1225 -
1226 -
1227 -(((
1228 -ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1229 -)))
1230 -
1231 -
1232 -== 8.3  Problem after Upgrading Firmware ==
1233 -
1234 -=== 8.3.1 Continue Restart after upgrading ===
1235 -
1236 -
1237 -(((
1238 -If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1239 -)))
1240 -
1241 -
1242 -[[image:image-20221118105249-3.png]]
1243 -
1244 -
1245 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1246 -
1247 -
1248 -It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
1249 -
1250 -
1251 -
1252 -==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1253 -
1254 -
1255 -[[image:image-20221122100004-1.png||height="497" width="534"]]
1256 -
1257 - ** Figure 1  **
1258 -
1259 -
1260 - [[image:image-20221122100004-2.png||height="619" width="389"]]
1261 -
1262 - **Figure 2**
1263 -
1264 -
1265 -
1266 -After the upgrade is completed, enter AT+CFG as shown in the figure below.
1267 -
1268 -
1269 -[[image:image-20221122100004-3.png]]
1270 -
1271 -Please AT+FDR, and then enter the following instructions by the information on the label
1272 -
1273 -AT+DEUI=70B3D57ED0053981
1274 -
1275 -AT+APPEUI=D23345667BCBCCAF
1276 -
1277 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1278 -
1279 -AT+DADDR=260b4dce
1280 -
1281 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1282 -
1283 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1284 -
1285 -
1286 -
1287 -==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1288 -
1289 -
1290 -[[image:image-20221122100004-4.png]]
1291 -
1292 -
1293 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1294 -
1295 -
1296 -Please download version 1.4.2 again
1297 -
1298 -
1299 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1300 -
1301 -
1302 -1） Make Sure the device is in Open Area where can see the sky.
1303 -
1304 -2)  Set PDOP to a higher value.
1305 -
1306 -* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1307 -
1308 -* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1309 -
1310 -* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1311 -
1312 -Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
1313 -
1314 -
1315 -= 9.  Order Info =
1316 -
1317 -
1318 1318  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1319 1319  
1320 1320  (% style="color:blue" %)**XXX**(%%): The default frequency band
1321 1321  
1322 1322  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1323 -
1324 1324  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1325 -
1326 1326  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1327 -
1328 1328  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1329 -
1330 1330  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1331 -
1332 1332  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1333 -
1334 1334  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1335 1335  
1081 += 9.  Packing Info =
1336 1336  
1337 1337  
1338 -= 10.  Packing Info =
1339 -
1340 -
1341 1341  (% style="color:#037691" %)**Package Includes**:
1342 1342  
1343 1343  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1344 -
1345 1345  * USB recharge & program cable x 1
1346 1346  
1347 1347  (% style="color:#037691" %)**Dimensions and Weight**:
1348 1348  
1349 -* Device Size: 85 x 48 x 15 mm
1350 -
1091 +* Device Size: 85 x 48 x 15 cm
1351 1351  * Weight: 50g
1352 1352  
1094 += 10. Support =
1353 1353  
1354 1354  
1355 -= 11. Support =
1356 -
1357 -
1358 1358  * 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.
1359 -
1360 1360  * 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]].
1361 1361  
1100 += 11.  Reference =
1362 1362  
1363 1363  
1364 -= 12.  Reference =
1365 -
1366 -
1367 1367  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1368 -
1369 1369  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1370 -
1371 1371  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1106 +
1107 +
1667288597595-714.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 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
image-20221107145243-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -107.3 KB
Content
image-20221116111844-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.8 KB
Content
image-20221116111844-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.6 KB
Content
image-20221116111844-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -37.0 KB
Content
image-20221116111844-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -96.8 KB
Content
image-20221116111844-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -78.0 KB
Content
image-20221118104359-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -38.0 KB
Content
image-20221118105220-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -40.2 KB
Content
image-20221118105249-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -40.2 KB
Content
image-20221118105402-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -43.7 KB
Content
image-20221122100004-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -18.0 KB
Content
image-20221122100004-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -127.2 KB
Content
image-20221122100004-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -12.5 KB
Content
image-20221122100004-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content