Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 113.8
edited by Xiaoling
on 2022/11/09 17:05
Change comment: There is no comment for this version
To version 156.1
edited by Bei Jinggeng
on 2022/11/28 10:29
Change comment: Uploaded new attachment "image-20221128102938-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png]]
2 +[[image:1664505654417-133.png||_mstalt="293696"]]
3 3  
4 4  
5 5  
... ... @@ -14,7 +14,6 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 -
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -32,21 +32,17 @@
32 32  (((
33 33  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 minimizing 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.
39 -
40 -
41 41  )))
42 42  
43 -[[image:1664499921684-770.png]]
39 +[[image:1664499921684-770.png||_mstalt="298194"]]
44 44  
45 45  
46 46  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47 47  
48 48  
49 -
50 50  == 1.2 Specifications ==
51 51  
52 52  
... ... @@ -129,7 +129,6 @@
129 129  
130 130  = 2.  Use TrackerD =
131 131  
132 -
133 133  == 2.1 How it works? ==
134 134  
135 135  
... ... @@ -136,7 +136,6 @@
136 136  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.
137 137  
138 138  
139 -
140 140  == 2.2 Quick guide to connect to LoRaWAN server ==
141 141  
142 142  
... ... @@ -143,7 +143,7 @@
143 143  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
144 144  
145 145  
146 -[[image:1664501652064-326.png]]
139 +[[image:1664501652064-326.png||_mstalt="293306"]]
147 147  
148 148  
149 149  
... ... @@ -155,7 +155,7 @@
155 155  Each TrackerD is shipped with a sticker with the default device EUI as below:
156 156  
157 157  
158 -[[image:1664501677253-891.png]]
151 +[[image:1664501677253-891.png||_mstalt="296569"]]
159 159  
160 160  
161 161  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -164,14 +164,14 @@
164 164  **__Add APP EUI in the application:__**
165 165  
166 166  
167 -[[image:1664501711466-918.png]]
160 +[[image:1664501711466-918.png||_mstalt="295828"]]
168 168  
169 169  
170 170  
171 -[[image:1664501721248-725.png]]
164 +[[image:1664501721248-725.png||_mstalt="294450"]]
172 172  
173 173  
174 -[[image:1664501734705-405.png]]
167 +[[image:1664501734705-405.png||_mstalt="293306"]]
175 175  
176 176  
177 177  
... ... @@ -178,17 +178,20 @@
178 178  **__Add APP KEY and DEV EUI:__**
179 179  
180 180  
181 -[[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"]]
174 +[[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||_mstalt="298233" alt="1654671889112-678.png"]]
182 182  
183 183  
184 184  
185 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
178 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
186 186  
180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
187 187  
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.
182 +[[image:1664502835802-546.png||_mstalt="295061"]]
189 189  
190 190  
185 +(% 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.
191 191  
187 +
192 192  == 2.3  Positioning Mode(SMOD) ==
193 193  
194 194  
... ... @@ -201,10 +201,8 @@
201 201  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
202 202  
203 203  
204 -
205 205  == 2.4  Uplink Payload ==
206 206  
207 -
208 208  === 2.4.1 Uplink FPORT~=5, Device Status ===
209 209  
210 210  
... ... @@ -217,7 +217,7 @@
217 217  |=(% 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
218 218  |=(% 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
219 219  
220 -[[image:1665301570342-765.png]]
214 +[[image:1665301570342-765.png||_mstalt="294580"]]
221 221  
222 222  
223 223  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -284,7 +284,7 @@
284 284  
285 285  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
286 286  
287 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
281 +(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
288 288  
289 289  
290 290  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -313,7 +313,7 @@
313 313  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
314 314  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
315 315  
316 -[[image:1665301636888-168.png]]
310 +[[image:1665301636888-168.png||_mstalt="298012"]]
317 317  
318 318  
319 319  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -322,8 +322,6 @@
322 322  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
323 323  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
324 324  
325 -
326 -
327 327  ==== (% style="color:blue" %)**FLAG:**(%%) ====
328 328  
329 329  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -345,12 +345,12 @@
345 345  2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
346 346  
347 347  
348 -[[image:1664502116362-706.png]]
340 +[[image:1664502116362-706.png||_mstalt="293306"]]
349 349  
350 350  
351 351  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
352 352  
353 -[[image:1664502166010-515.png]]
345 +[[image:1664502166010-515.png||_mstalt="291395"]]
354 354  
355 355  
356 356  
... ... @@ -415,7 +415,6 @@
415 415  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
416 416  
417 417  
418 -
419 419  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
420 420  
421 421  
... ... @@ -431,14 +431,13 @@
431 431  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
432 432  
433 433  (% class="wikigeneratedid" %)
434 -[[image:1665301687277-443.png]]
425 +[[image:1665301687277-443.png||_mstalt="296140"]]
435 435  
436 436  
437 -
438 438  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
439 439  
440 440  
441 -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.
431 +Set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-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.
442 442  
443 443  
444 444  (% style="color:red" %)**Note for this mode:**
... ... @@ -455,10 +455,9 @@
455 455  )))|4|4|2|1|1|1|1|1
456 456  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
457 457  
458 -[[image:image-20221009160309-2.png]]
448 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
459 459  
460 460  
461 -
462 462  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
463 463  
464 464  
... ... @@ -483,7 +483,7 @@
483 483  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
484 484  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
485 485  
486 -[[image:1664502425687-834.png]]
475 +[[image:1664502425687-834.png||_mstalt="296738"]]
487 487  
488 488  
489 489  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -490,7 +490,7 @@
490 490  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
491 491  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
492 492  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
493 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
482 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
494 494  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
495 495  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
496 496  
... ... @@ -511,7 +511,7 @@
511 511  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
512 512  
513 513  (% class="wikigeneratedid" %)
514 -[[image:1667288597595-714.png||height="212" width="1151"]]
503 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
515 515  
516 516  
517 517  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -528,9 +528,10 @@
528 528  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
529 529  
530 530  
531 -[[image:1664502649601-895.png]]
520 +[[image:1664502649601-895.png||_mstalt="296985"]]
532 532  
533 533  
523 +
534 534  Add the decoder from this link: 
535 535  
536 536  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -537,10 +537,9 @@
537 537  
538 538  Save the change the uplink message will be parsed. As below:
539 539  
540 -[[image:1664502676891-606.png]]
530 +[[image:1664502676891-606.png||_mstalt="296673"]]
541 541  
542 542  
543 -
544 544  == 2.5 Integrate with Datacake ==
545 545  
546 546  
... ... @@ -549,10 +549,9 @@
549 549  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]]
550 550  
551 551  
552 -[[image:1664502695771-538.png]]
541 +[[image:1664502695771-538.png||_mstalt="297349"]]
553 553  
554 554  
555 -
556 556  == 2.6 Integrate with Tago ==
557 557  
558 558  
... ... @@ -561,26 +561,24 @@
561 561  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]]
562 562  
563 563  
564 -[[image:1664502715371-321.png]]
552 +[[image:1664502715371-321.png||_mstalt="292162"]]
565 565  
566 566  
567 -
568 568  == 2.7  Datalog Feature ==
569 569  
570 570  
571 571  total 273 entries,by default,
572 572  
573 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
560 +User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
574 574  
575 575  Example use case.
576 576  
577 -[[image:image-20221009234703-2.png||height="328" width="899"]]
564 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
578 578  
579 579  
580 -[[image:image-20221009234629-1.png||height="390" width="577"]]
567 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
581 581  
582 582  
583 -
584 584  == 2.8 Alarm Mode ==
585 585  
586 586  
... ... @@ -595,7 +595,7 @@
595 595  
596 596  
597 597  (((
598 -Two ways to exit alarm mode:
584 +**Two ways to exit alarm mode:**
599 599  )))
600 600  
601 601  * Server sends a downlink command to exit.
... ... @@ -606,14 +606,17 @@
606 606  )))
607 607  
608 608  
609 -
610 610  == 2.9 Transport Mode ==
611 611  
612 612  
613 613  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.
614 614  
600 +* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
601 +* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
602 +* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
615 615  
616 616  
605 +
617 617  == 2.10 LED Status ==
618 618  
619 619  
... ... @@ -638,7 +638,7 @@
638 638  
639 639  (% style="color:blue" %)**RESET button:**
640 640  
641 -[[image:1664502835802-546.png]]
630 +[[image:1664502835802-546.png||_mstalt="295061"]]
642 642  
643 643  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
644 644  
... ... @@ -645,7 +645,7 @@
645 645  
646 646  (% style="color:red" %)**RED button:**
647 647  
648 -[[image:1664502854406-763.png]]
637 +[[image:1664502854406-763.png||_mstalt="295568"]]
649 649  
650 650  
651 651  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -676,7 +676,6 @@
676 676  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
677 677  
678 678  
679 -
680 680  == 3.1 Access AT Command ==
681 681  
682 682  
... ... @@ -683,25 +683,23 @@
683 683  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.
684 684  
685 685  
686 -[[image:1664502999401-486.png]]
674 +[[image:1664502999401-486.png||_mstalt="296985"]]
687 687  
688 688  
689 689  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:
690 690  
691 691  
692 -[[image:1664503022490-662.png]]
680 +[[image:1664503022490-662.png||_mstalt="293332"]]
693 693  
694 694  
695 -[[image:1664503035713-500.png]]
683 +[[image:1664503035713-500.png||_mstalt="291096"]]
696 696  
697 697  
698 -[[image:1664503047675-651.png]]
686 +[[image:1664503047675-651.png||_mstalt="295386"]]
699 699  
700 700  
701 -
702 702  == 3.2 Command Set ==
703 703  
704 -
705 705  === 3.2.1 Set Transmit Interval ===
706 706  
707 707  
... ... @@ -719,7 +719,6 @@
719 719  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
720 720  
721 721  
722 -
723 723  === 3.2.2 Set Alarm Packet transmission interval ===
724 724  
725 725  
... ... @@ -737,7 +737,6 @@
737 737  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
738 738  
739 739  
740 -
741 741  === 3.2.3 Set Transport Mode Packet transmission interval ===
742 742  
743 743  
... ... @@ -755,7 +755,6 @@
755 755  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
756 756  
757 757  
758 -
759 759  === 3.2.4 Exit Alarm ===
760 760  
761 761  
... ... @@ -768,7 +768,6 @@
768 768  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
769 769  
770 770  
771 -
772 772  === 3.2.5 Disable/Enable LED flash ===
773 773  
774 774  
... ... @@ -786,7 +786,6 @@
786 786  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
787 787  
788 788  
789 -
790 790  === 3.2.6 Disable/Enable Transport Mode ===
791 791  
792 792  
... ... @@ -804,7 +804,6 @@
804 804  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
805 805  
806 806  
807 -
808 808  === 3.2.7 Set Positioning Mode ===
809 809  
810 810  
... ... @@ -831,9 +831,9 @@
831 831  
832 832  (% style="color:#037691" %)**cc:   **
833 833  
834 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
814 +* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
835 835  
836 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
816 +* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
837 837  
838 838  (% style="color:blue" %)**Example:**
839 839  
... ... @@ -851,7 +851,6 @@
851 851  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
852 852  
853 853  
854 -
855 855  === 3.2.8 Set MAX GPS position time ===
856 856  
857 857  
... ... @@ -858,7 +858,7 @@
858 858  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.
859 859  
860 860  
861 -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.
840 +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.
862 862  
863 863  
864 864  * (% style="color:blue" %)**AT Command:**
... ... @@ -873,7 +873,6 @@
873 873  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
874 874  
875 875  
876 -
877 877  === 3.2.9 Set PDOP value for GPS fix accuracy ===
878 878  
879 879  
... ... @@ -898,8 +898,9 @@
898 898  
899 899  
900 900  
901 -Disable/Enable the confirmation mode
879 +=== 3.2.10 Disable/Enable the confirmation mode ===
902 902  
881 +
903 903  * (% style="color:blue" %)**AT Command:**
904 904  
905 905  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -917,10 +917,9 @@
917 917  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
918 918  
919 919  
899 +=== 3.2.11  Auto Send None-ACK messages ===
920 920  
921 -=== 3.2.10  Auto Send None-ACK messages ===
922 922  
923 -
924 924  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.
925 925  
926 926  
... ... @@ -936,13 +936,12 @@
936 936  
937 937  * (% style="color:blue" %)**Downlink Command: 0x34**
938 938  
939 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
940 940  
941 941  
920 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
942 942  
943 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
944 944  
945 -
946 946  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.
947 947  
948 948  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -949,19 +949,18 @@
949 949  
950 950  (% style="color:blue" %)**AT Command:**
951 951  
952 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
953 953  
954 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
955 955  
956 956  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
957 957  
958 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
935 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
959 959  
960 960  
938 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
961 961  
962 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
963 963  
964 -
965 965  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.
966 966  
967 967  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -968,19 +968,18 @@
968 968  
969 969  (% style="color:blue" %)**AT Command:**
970 970  
971 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
972 972  
973 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
974 974  
975 975  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
976 976  
977 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
953 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
978 978  
979 979  
956 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
980 980  
981 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
982 982  
983 -
984 984  Users can use this feature to enable/disable Information printing.
985 985  
986 986  (% style="color:blue" %)**AT Command:**
... ... @@ -989,10 +989,9 @@
989 989  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
990 990  
991 991  
967 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
992 992  
993 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
994 994  
995 -
996 996  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
997 997  
998 998  (% style="color:blue" %)**AT Command:**
... ... @@ -1005,7 +1005,26 @@
1005 1005  Example: 0x24 01 ~/~/ Same as AT+CHE=1
1006 1006  
1007 1007  
982 +=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1008 1008  
984 +User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
985 +
986 +(% style="color:blue" %)**AT Command:**
987 +
988 +(% style="color:#037691" %)**AT+PT=xx**
989 +
990 + Example:
991 +
992 + AT+PT=14    ~-~->    Set to detect car motion.
993 +
994 + AT+PT=41   ~-~->    set to detect walk motion.
995 +
996 +
997 +(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
998 +0xB4 14          ~/~/  Same as AT+PT=14
999 +
1000 +
1001 +
1009 1009  = 4. Setting for Different Scenarios =
1010 1010  
1011 1011  
... ... @@ -1012,7 +1012,6 @@
1012 1012  
1013 1013  = 5. Upload Firmware =
1014 1014  
1015 -
1016 1016  == 5.1 Firmware Change Log ==
1017 1017  
1018 1018  
... ... @@ -1019,7 +1019,6 @@
1019 1019  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1020 1020  
1021 1021  
1022 -
1023 1023  == 5.2 How to upgrade firmware ==
1024 1024  
1025 1025  
... ... @@ -1040,10 +1040,10 @@
1040 1040  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1041 1041  
1042 1042  
1043 -[[image:1664503563660-578.png]]
1034 +[[image:1664503563660-578.png||_mstalt="296777"]]
1044 1044  
1045 1045  
1046 -[[image:1664503574618-659.png]]
1037 +[[image:1664503574618-659.png||_mstalt="297986"]]
1047 1047  
1048 1048  
1049 1049  
... ... @@ -1052,29 +1052,27 @@
1052 1052  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1053 1053  
1054 1054  
1055 -Users need to use below files:
1046 +**Users need to use below files:**
1056 1056  
1057 1057  boot_app0.bin @0e000
1058 1058  
1059 -ESP_LORA-eeprom-class.bin @ 0x10000
1050 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1060 1060  
1061 1061  
1062 -[[image:1664503593459-435.png]]
1053 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1063 1063  
1064 1064  
1065 1065  
1066 1066  After upgrade finish, it will show finish as below:
1067 1067  
1068 -[[image:1664503611848-385.png]]
1059 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1069 1069  
1070 1070  
1071 1071  
1072 1072  = 6. Developer Guide =
1073 1073  
1074 -
1075 1075  == 6.1 Compile Source Code ==
1076 1076  
1077 -
1078 1078  === 6.1.1 Set up ARDUINO compile environment ===
1079 1079  
1080 1080  
... ... @@ -1083,23 +1083,23 @@
1083 1083  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]]
1084 1084  
1085 1085  
1086 -[[image:1664503635019-941.png]]
1075 +[[image:1664503635019-941.png||_mstalt="294658"]]
1087 1087  
1088 1088  
1089 1089  
1090 1090  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1091 1091  
1092 -[[image:1664503715811-892.png]]
1081 +[[image:1664503715811-892.png||_mstalt="295698"]]
1093 1093  
1094 1094  
1095 1095  (% 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.
1096 1096  
1097 -[[image:image-20221024105643-1.png]]
1086 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1098 1098  
1099 1099  **~ Figure1**
1100 1100  
1101 1101  
1102 -[[image:image-20221024105643-2.png]]
1091 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1103 1103  
1104 1104   **Figure2**
1105 1105  
... ... @@ -1109,34 +1109,31 @@
1109 1109  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1110 1110  
1111 1111  
1112 -[[image:1664503752288-974.png]]
1101 +[[image:1664503752288-974.png||_mstalt="298194"]]
1113 1113  
1114 1114  
1115 -
1116 1116  == 6.2 Source Code ==
1117 1117  
1118 1118  
1119 1119  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1120 1120  
1121 -[[image:1664503794261-827.png]]
1109 +[[image:1664503794261-827.png||_mstalt="296387"]]
1122 1122  
1123 1123  
1124 1124  
1125 1125  * (% style="color:blue" %)**Click to upload**
1126 1126  
1127 -[[image:1664503808294-336.png]]
1115 +[[image:1664503808294-336.png||_mstalt="295711"]]
1128 1128  
1129 1129  
1130 1130  
1131 1131  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1132 1132  
1133 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1121 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1134 1134  
1135 1135  
1136 -
1137 1137  = 7.  FAQ =
1138 1138  
1139 -
1140 1140  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1141 1141  
1142 1142  
... ... @@ -1143,11 +1143,10 @@
1143 1143  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1144 1144  
1145 1145  
1146 -
1147 1147  == 7.2 What is the pin mapping for the USB program cable? ==
1148 1148  
1149 1149  
1150 -[[image:1664499635206-262.png]]
1135 +[[image:1664499635206-262.png||_mstalt="295360"]]
1151 1151  
1152 1152  
1153 1153  
... ... @@ -1166,7 +1166,6 @@
1166 1166  
1167 1167  == 7.3 Notes on using different serial port tools for TrackerD ==
1168 1168  
1169 -
1170 1170  === 7.3.1  Serial port utility ===
1171 1171  
1172 1172  
... ... @@ -1174,18 +1174,16 @@
1174 1174  
1175 1175  Need to adjust the data stream to RTS/CTS on physical restart.
1176 1176  
1177 -
1178 1178  (% class="wikigeneratedid" %)
1179 -[[image:image-20221102140621-1.png]]
1162 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1180 1180  
1181 1181  
1165 +
1182 1182  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1183 1183  
1168 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1184 1184  
1185 -[[image:image-20221102140638-2.png]]
1186 1186  
1187 -
1188 -
1189 1189  === 7.3.2  SecureCRT ===
1190 1190  
1191 1191  
... ... @@ -1192,38 +1192,73 @@
1192 1192  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.
1193 1193  
1194 1194  
1195 -[[image:image-20221102140704-3.png]]
1177 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1196 1196  
1197 1197  
1198 -[[image:image-20221102140712-4.png]]
1180 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1199 1199  
1200 1200  
1201 -
1202 1202  === 7.3.3  PUTTY ===
1203 1203  
1204 1204  
1205 -[[image:image-20221102140748-5.png]]
1186 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1206 1206  
1207 1207  
1208 1208  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.
1209 1209  
1210 1210  
1211 -[[image:image-20221102140801-6.png]]
1192 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1212 1212  
1213 1213  
1195 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1214 1214  
1215 -= 8  Trouble Shooting =
1216 1216  
1198 +(% class="box infomessage" %)
1199 +(((
1200 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1201 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1202 +)))
1217 1217  
1204 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1205 +
1206 +
1207 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1208 +
1209 +
1210 +
1211 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1212 +
1213 +
1214 +[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1215 +
1216 +
1217 +
1218 +**3. Compile the AS923_JP band, please refer to the intention shown**
1219 +
1220 +
1221 +[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1222 +
1223 +
1224 +
1225 +**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.**
1226 +
1227 +
1228 +[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1229 +
1230 +
1231 +[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1232 +
1233 +
1234 += 8  Trouble Shooting =
1235 +
1218 1218  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1219 1219  
1220 1220  
1221 1221  (((
1222 -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
1240 +Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**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
1223 1223  )))
1224 1224  
1225 1225  
1226 -
1227 1227  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1228 1228  
1229 1229  
... ... @@ -1232,19 +1232,106 @@
1232 1232  )))
1233 1233  
1234 1234  
1252 +== 8.3  Problem after Upgrading Firmware ==
1235 1235  
1236 -== 8.3  The reason why it has been restarted after upgrading（V.1.4.1） ==
1254 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1237 1237  
1238 1238  
1257 +**Error Output**
1258 +
1259 +
1260 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1261 +
1262 +
1239 1239  (((
1240 -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
1264 +Some partition is missed during upgrade, please upgrade below four files as example:
1265 +
1266 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1241 1241  )))
1242 1242  
1243 1243  
1244 -[[image:image-20221107145243-1.png||height="695" width="443"]]
1270 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1245 1245  
1246 1246  
1273 +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
1247 1247  
1275 +
1276 +=== 8.3.3 "flash read err" after upgrade firmware ===
1277 +
1278 +
1279 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1280 +
1281 +
1282 +[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1283 +
1284 +
1285 +User need to upgrade again with below four files to solve this issue.
1286 +
1287 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1288 +
1289 + **Figure 2**
1290 +
1291 +
1292 +=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1293 +
1294 +
1295 +User might erase the entire flash include keys and default settings which cause this issue.
1296 +
1297 +After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1298 +
1299 +
1300 +[[image:image-20221122100004-3.png||_mstalt="424242"]]
1301 +
1302 +
1303 +Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1304 +
1305 +After AT+FDR. please set
1306 +
1307 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1308 +
1309 +* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1310 +
1311 +**Example:**
1312 +
1313 +AT+PDOP=7.00
1314 +
1315 +AT+FTIME=180
1316 +
1317 +AT+DEUI=70B3D57ED0053981  
1318 +
1319 +AT+APPEUI=D23345667BCBCCAF
1320 +
1321 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1322 +
1323 +AT+DADDR=260b4dce    ( no need for OTAA)
1324 +
1325 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1326 +
1327 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1328 +
1329 +
1330 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1331 +
1332 +
1333 +Please download version 1.4.2 again
1334 +
1335 +
1336 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1337 +
1338 +
1339 +1） Make Sure the device is in Open Area where can see the sky.
1340 +
1341 +2)  Set PDOP to a higher value.
1342 +
1343 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1344 +
1345 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1346 +
1347 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1348 +
1349 +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
1350 +
1351 +
1248 1248  = 9.  Order Info =
1249 1249  
1250 1250  
... ... @@ -1253,11 +1253,17 @@
1253 1253  (% style="color:blue" %)**XXX**(%%): The default frequency band
1254 1254  
1255 1255  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1360 +
1256 1256  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1362 +
1257 1257  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1364 +
1258 1258  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1366 +
1259 1259  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1368 +
1260 1260  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1370 +
1261 1261  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1262 1262  
1263 1263  
... ... @@ -1268,11 +1268,13 @@
1268 1268  (% style="color:#037691" %)**Package Includes**:
1269 1269  
1270 1270  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1381 +
1271 1271  * USB recharge & program cable x 1
1272 1272  
1273 1273  (% style="color:#037691" %)**Dimensions and Weight**:
1274 1274  
1275 1275  * Device Size: 85 x 48 x 15 mm
1387 +
1276 1276  * Weight: 50g
1277 1277  
1278 1278  
... ... @@ -1281,6 +1281,7 @@
1281 1281  
1282 1282  
1283 1283  * 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.
1396 +
1284 1284  * 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]].
1285 1285  
1286 1286  
... ... @@ -1289,7 +1289,8 @@
1289 1289  
1290 1290  
1291 1291  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1405 +
1292 1292  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1293 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1294 1294  
1295 -
1408 +* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1409 +)))
image-20221116111844-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +15.8 KB
Content
image-20221116111844-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
image-20221116111844-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +37.0 KB
Content
image-20221116111844-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +96.8 KB
Content
image-20221116111844-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +78.0 KB
Content
image-20221118104359-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +38.0 KB
Content
image-20221118105220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20221118105249-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20221118105402-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.7 KB
Content
image-20221122100004-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +18.0 KB
Content
image-20221122100004-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +127.2 KB
Content
image-20221122100004-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +12.5 KB
Content
image-20221122100004-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20221128102938-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +41.3 KB
Content