Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 184.2
edited by Xiaoling
on 2022/12/13 14:34
Change comment: There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2022/11/22 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -12,7 +12,6 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
18 18  == 1.1  What is TrackerD ==
... ... @@ -32,12 +32,15 @@
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  )))
34 +)))
35 35  
36 36  (((
37 37  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.
38 +
39 +
38 38  )))
39 39  
40 -[[image:1664499921684-770.png||_mstalt="298194"]]
42 +[[image:1664499921684-770.png]]
41 41  
42 42  
43 43  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
... ... @@ -93,8 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -
97 -
98 98  == 1.3  Features ==
99 99  
100 100  
... ... @@ -113,8 +113,6 @@
113 113  * Tri-color LED, Alarm button
114 114  * Datalog
115 115  
116 -
117 -
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,8 +121,6 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -
125 -
126 126  = 2.  Use TrackerD =
127 127  
128 128  == 2.1 How it works? ==
... ... @@ -137,7 +137,7 @@
137 137  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. 
138 138  
139 139  
140 -[[image:1664501652064-326.png||_mstalt="293306"]]
136 +[[image:1664501652064-326.png]]
141 141  
142 142  
143 143  
... ... @@ -149,7 +149,7 @@
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
151 151  
152 -[[image:1664501677253-891.png||_mstalt="296569"]]
148 +[[image:1664501677253-891.png]]
153 153  
154 154  
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -158,14 +158,14 @@
158 158  **__Add APP EUI in the application:__**
159 159  
160 160  
161 -[[image:1664501711466-918.png||_mstalt="295828"]]
157 +[[image:1664501711466-918.png]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png||_mstalt="294450"]]
161 +[[image:1664501721248-725.png]]
166 166  
167 167  
168 -[[image:1664501734705-405.png||_mstalt="293306"]]
164 +[[image:1664501734705-405.png]]
169 169  
170 170  
171 171  
... ... @@ -172,15 +172,15 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[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"]]
171 +[[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"]]
176 176  
177 177  
178 178  
179 179  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180 180  
181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
182 182  
183 -[[image:1664502835802-546.png||_mstalt="295061"]]
179 +[[image:1664502835802-546.png]]
184 184  
185 185  
186 186  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
... ... @@ -212,7 +212,7 @@
212 212  |=(% 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
213 213  |=(% 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
214 214  
215 -[[image:1665301570342-765.png||_mstalt="294580"]]
211 +[[image:1665301570342-765.png]]
216 216  
217 217  
218 218  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -279,7 +279,7 @@
279 279  
280 280  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 281  
282 -(% _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)(%%)  
278 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
283 283  
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -288,8 +288,6 @@
288 288  |=(% 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
289 289  |=(% 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"]]
290 290  
291 -
292 -
293 293  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294 294  
295 295  
... ... @@ -308,7 +308,7 @@
308 308  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309 309  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
310 310  
311 -[[image:1665301636888-168.png||_mstalt="298012"]]
305 +[[image:1665301636888-168.png]]
312 312  
313 313  
314 314  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -338,12 +338,12 @@
338 338  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:
339 339  
340 340  
341 -[[image:1664502116362-706.png||_mstalt="293306"]]
335 +[[image:1664502116362-706.png]]
342 342  
343 343  
344 344  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
345 345  
346 -[[image:1664502166010-515.png||_mstalt="291395"]]
340 +[[image:1664502166010-515.png]]
347 347  
348 348  
349 349  
... ... @@ -421,13 +421,13 @@
421 421  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
422 422  
423 423  (% class="wikigeneratedid" %)
424 -[[image:1665301687277-443.png||_mstalt="296140"]]
418 +[[image:1665301687277-443.png]]
425 425  
426 426  
427 427  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
428 428  
429 429  
430 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-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.
424 +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 431  
432 432  
433 433  (% style="color:red" %)**Note for this mode:**
... ... @@ -444,7 +444,7 @@
444 444  )))|4|4|2|1|1|1|1|1
445 445  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
446 446  
447 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
441 +[[image:image-20221009160309-2.png]]
448 448  
449 449  
450 450  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -471,7 +471,7 @@
471 471  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
472 472  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
473 473  
474 -[[image:1664502425687-834.png||_mstalt="296738"]]
468 +[[image:1664502425687-834.png]]
475 475  
476 476  
477 477  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -482,8 +482,6 @@
482 482  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
483 483  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
484 484  
485 -
486 -
487 487  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
488 488  
489 489  
... ... @@ -499,7 +499,7 @@
499 499  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
500 500  
501 501  (% class="wikigeneratedid" %)
502 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
494 +[[image:1667288597595-714.png||height="212" width="1151"]]
503 503  
504 504  
505 505  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -506,8 +506,6 @@
506 506  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
507 507  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
508 508  
509 -
510 -
511 511  === 2.4.7  Add Payload format in TTN V3 ===
512 512  
513 513  
... ... @@ -516,7 +516,7 @@
516 516  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
517 517  
518 518  
519 -[[image:1664502649601-895.png||_mstalt="296985"]]
509 +[[image:1664502649601-895.png]]
520 520  
521 521  
522 522  
... ... @@ -526,7 +526,7 @@
526 526  
527 527  Save the change the uplink message will be parsed. As below:
528 528  
529 -[[image:1664502676891-606.png||_mstalt="296673"]]
519 +[[image:1664502676891-606.png]]
530 530  
531 531  
532 532  == 2.5 Integrate with Datacake ==
... ... @@ -537,7 +537,7 @@
537 537  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]]
538 538  
539 539  
540 -[[image:1664502695771-538.png||_mstalt="297349"]]
530 +[[image:1664502695771-538.png]]
541 541  
542 542  
543 543  == 2.6 Integrate with Tago ==
... ... @@ -548,7 +548,7 @@
548 548  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]]
549 549  
550 550  
551 -[[image:1664502715371-321.png||_mstalt="292162"]]
541 +[[image:1664502715371-321.png]]
552 552  
553 553  
554 554  == 2.7  Datalog Feature ==
... ... @@ -556,14 +556,14 @@
556 556  
557 557  total 273 entries,by default,
558 558  
559 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
560 560  
561 561  Example use case.
562 562  
563 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||height="328" width="899"]]
564 564  
565 565  
566 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||height="390" width="577"]]
567 567  
568 568  
569 569  == 2.8 Alarm Mode ==
... ... @@ -596,12 +596,7 @@
596 596  
597 597  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.
598 598  
599 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
600 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
601 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
602 602  
603 -
604 -
605 605  == 2.10 LED Status ==
606 606  
607 607  
... ... @@ -619,14 +619,12 @@
619 619  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
620 620  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
621 621  
622 -
623 -
624 624  == 2.11 Button Function ==
625 625  
626 626  
627 627  (% style="color:blue" %)**RESET button:**
628 628  
629 -[[image:1664502835802-546.png||_mstalt="295061"]]
612 +[[image:1664502835802-546.png]]
630 630  
631 631  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
632 632  
... ... @@ -633,7 +633,7 @@
633 633  
634 634  (% style="color:red" %)**RED button:**
635 635  
636 -[[image:1664502854406-763.png||_mstalt="295568"]]
619 +[[image:1664502854406-763.png]]
637 637  
638 638  
639 639  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -642,8 +642,6 @@
642 642  |(% 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
643 643  |(% 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.
644 644  
645 -
646 -
647 647  == 2.12 USB Port Function ==
648 648  
649 649  
... ... @@ -654,8 +654,6 @@
654 654  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
655 655  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
656 656  
657 -
658 -
659 659  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
660 660  
661 661  
... ... @@ -670,21 +670,22 @@
670 670  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.
671 671  
672 672  
673 -[[image:1664502999401-486.png||_mstalt="296985"]]
652 +[[image:1664502999401-486.png]]
674 674  
675 675  
676 676  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:
677 677  
678 678  
679 -[[image:1664503022490-662.png||_mstalt="293332"]]
658 +[[image:1664503022490-662.png]]
680 680  
681 681  
682 -[[image:1664503035713-500.png||_mstalt="291096"]]
661 +[[image:1664503035713-500.png]]
683 683  
684 684  
685 -[[image:1664503047675-651.png||_mstalt="295386"]]
664 +[[image:1664503047675-651.png]]
686 686  
687 687  
667 +
688 688  == 3.2 Command Set ==
689 689  
690 690  === 3.2.1 Set Transmit Interval ===
... ... @@ -810,9 +810,9 @@
810 810  
811 811  (% style="color:#037691" %)**cc:   **
812 812  
813 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
814 814  
815 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
795 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
816 816  
817 817  (% style="color:blue" %)**Example:**
818 818  
... ... @@ -874,8 +874,8 @@
874 874  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
875 875  
876 876  
877 -=== 3.2.10 Disable/Enable the confirmation mode ===
878 878  
858 +**Disable/Enable the confirmation mode**
879 879  
880 880  * (% style="color:blue" %)**AT Command:**
881 881  
... ... @@ -894,7 +894,7 @@
894 894  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
895 895  
896 896  
897 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
898 898  
899 899  
900 900  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.
... ... @@ -912,10 +912,10 @@
912 912  
913 913  * (% style="color:blue" %)**Downlink Command: 0x34**
914 914  
915 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
916 916  
917 917  
918 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
919 919  
920 920  
921 921  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.
... ... @@ -924,16 +924,16 @@
924 924  
925 925  (% style="color:blue" %)**AT Command:**
926 926  
927 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
907 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
928 928  
929 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
909 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
930 930  
931 931  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
932 932  
933 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
934 934  
935 935  
936 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
916 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
937 937  
938 938  
939 939  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,16 +942,16 @@
942 942  
943 943  (% style="color:blue" %)**AT Command:**
944 944  
945 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
925 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
946 946  
947 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
927 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
948 948  
949 949  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
950 950  
951 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
952 952  
953 953  
954 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
934 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
955 955  
956 956  
957 957  Users can use this feature to enable/disable Information printing.
... ... @@ -958,11 +958,11 @@
958 958  
959 959  (% style="color:blue" %)**AT Command:**
960 960  
961 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
941 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
962 962  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
963 963  
964 964  
965 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
966 966  
967 967  
968 968  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -969,34 +969,14 @@
969 969  
970 970  (% style="color:blue" %)**AT Command:**
971 971  
972 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
973 973  
974 974  
975 975  (% style="color:blue" %)**Downlink Payload:0X24**
976 976  
977 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
978 978  
979 979  
980 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
981 -
982 -
983 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
984 -
985 -(% style="color:blue" %)**AT Command:**
986 -
987 -(% style="color:#037691" %)**AT+PT=xx**
988 -
989 - Example:
990 -
991 - AT+PT=14    ~-~->    Set to detect car motion.
992 -
993 - AT+PT=41  ~-~->    set to detect walk motion.
994 -
995 -
996 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
997 -0xB4 14          ~/~/  Same as AT+PT=14
998 -
999 -
1000 1000  = 4. Setting for Different Scenarios =
1001 1001  
1002 1002  
... ... @@ -1029,10 +1029,10 @@
1029 1029  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1030 1030  
1031 1031  
1032 -[[image:1664503563660-578.png||_mstalt="296777"]]
992 +[[image:1664503563660-578.png]]
1033 1033  
1034 1034  
1035 -[[image:1664503574618-659.png||_mstalt="297986"]]
995 +[[image:1664503574618-659.png]]
1036 1036  
1037 1037  
1038 1038  
... ... @@ -1048,15 +1048,16 @@
1048 1048  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1049 1049  
1050 1050  
1051 -[[image:image-20221207120501-1.png]]
1011 +[[image:image-20221118105220-2.png]]
1052 1052  
1053 1053  
1054 1054  
1055 1055  After upgrade finish, it will show finish as below:
1056 1056  
1057 -[[image:image-20221207133911-7.png]]
1017 +[[image:image-20221118105402-4.png]]
1058 1058  
1059 1059  
1020 +
1060 1060  = 6. Developer Guide =
1061 1061  
1062 1062  == 6.1 Compile Source Code ==
... ... @@ -1069,71 +1069,24 @@
1069 1069  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]]
1070 1070  
1071 1071  
1072 -[[image:1664503635019-941.png||_mstalt="294658"]]
1033 +[[image:1664503635019-941.png]]
1073 1073  
1074 1074  
1075 1075  
1076 1076  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1077 1077  
1078 -[[image:1664503715811-892.png||_mstalt="295698"]]
1039 +[[image:1664503715811-892.png]]
1079 1079  
1080 1080  
1081 -=== 6.1.2 Build the development environment ===
1082 -
1083 -~1. Download and install arduino IDE
1084 -
1085 -[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1086 -
1087 -
1088 -2. Download the ESP32 development package in the arduino IDE
1089 -
1090 -[[image:image-20221213100007-1.png]]
1091 -
1092 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1093 -
1094 -[[image:image-20221213100626-2.png]]
1095 -
1096 -Restart the IDE after the addition is complete, then:
1097 -
1098 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1099 -
1100 -[[image:image-20221213101040-4.png]]
1101 -
1102 -**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1103 -Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1104 -
1105 -Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1106 -
1107 -Methods as below:
1108 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1109 -
1110 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1111 -
1112 1112  (% 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.
1113 1113  
1114 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1044 +[[image:image-20221024105643-1.png]]
1115 1115  
1116 -3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)
1117 -
1118 -[[image:image-20221213102334-6.png]]
1119 -
1120 -**Note: This step requires a python environment**
1121 -
1122 -Either way, in the end:
1123 -The final effect is to open the arduino and you can see the esp32
1124 -
1125 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1126 -
1127 -
1128 -
1129 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1130 -
1131 1131  **~ Figure1**
1132 1132  
1133 1133  
1049 +[[image:image-20221024105643-2.png]]
1134 1134  
1135 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1136 -
1137 1137   **Figure2**
1138 1138  
1139 1139  
... ... @@ -1142,7 +1142,7 @@
1142 1142  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1143 1143  
1144 1144  
1145 -[[image:1664503752288-974.png||_mstalt="298194"]]
1059 +[[image:1664503752288-974.png]]
1146 1146  
1147 1147  
1148 1148  == 6.2 Source Code ==
... ... @@ -1150,19 +1150,19 @@
1150 1150  
1151 1151  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1152 1152  
1153 -[[image:1664503794261-827.png||_mstalt="296387"]]
1067 +[[image:1664503794261-827.png]]
1154 1154  
1155 1155  
1156 1156  
1157 1157  * (% style="color:blue" %)**Click to upload**
1158 1158  
1159 -[[image:1664503808294-336.png||_mstalt="295711"]]
1073 +[[image:1664503808294-336.png]]
1160 1160  
1161 1161  
1162 1162  
1163 1163  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1164 1164  
1165 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1079 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1166 1166  
1167 1167  
1168 1168  = 7.  FAQ =
... ... @@ -1176,7 +1176,7 @@
1176 1176  == 7.2 What is the pin mapping for the USB program cable? ==
1177 1177  
1178 1178  
1179 -[[image:1664499635206-262.png||_mstalt="295360"]]
1093 +[[image:1664499635206-262.png]]
1180 1180  
1181 1181  
1182 1182  
... ... @@ -1191,8 +1191,6 @@
1191 1191  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1192 1192  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1193 1193  
1194 -
1195 -
1196 1196  == 7.3 Notes on using different serial port tools for TrackerD ==
1197 1197  
1198 1198  === 7.3.1  Serial port utility ===
... ... @@ -1203,13 +1203,13 @@
1203 1203  Need to adjust the data stream to RTS/CTS on physical restart.
1204 1204  
1205 1205  (% class="wikigeneratedid" %)
1206 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1118 +[[image:image-20221102140621-1.png]]
1207 1207  
1208 1208  
1209 1209  
1210 1210  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1211 1211  
1212 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1124 +[[image:image-20221102140638-2.png]]
1213 1213  
1214 1214  
1215 1215  === 7.3.2  SecureCRT ===
... ... @@ -1218,22 +1218,22 @@
1218 1218  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.
1219 1219  
1220 1220  
1221 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1133 +[[image:image-20221102140704-3.png]]
1222 1222  
1223 1223  
1224 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1136 +[[image:image-20221102140712-4.png]]
1225 1225  
1226 1226  
1227 1227  === 7.3.3  PUTTY ===
1228 1228  
1229 1229  
1230 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1142 +[[image:image-20221102140748-5.png]]
1231 1231  
1232 1232  
1233 1233  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.
1234 1234  
1235 1235  
1236 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1148 +[[image:image-20221102140801-6.png]]
1237 1237  
1238 1238  
1239 1239  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1248,7 +1248,7 @@
1248 1248  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1249 1249  
1250 1250  
1251 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1163 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1252 1252  
1253 1253  
1254 1254  
... ... @@ -1255,7 +1255,7 @@
1255 1255  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1256 1256  
1257 1257  
1258 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1170 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1259 1259  
1260 1260  
1261 1261  
... ... @@ -1262,7 +1262,7 @@
1262 1262  **3. Compile the AS923_JP band, please refer to the intention shown**
1263 1263  
1264 1264  
1265 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1177 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1266 1266  
1267 1267  
1268 1268  
... ... @@ -1269,10 +1269,10 @@
1269 1269  **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.**
1270 1270  
1271 1271  
1272 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1184 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1273 1273  
1274 1274  
1275 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1187 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1276 1276  
1277 1277  
1278 1278  = 8  Trouble Shooting =
... ... @@ -1281,7 +1281,7 @@
1281 1281  
1282 1282  
1283 1283  (((
1284 -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
1196 +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
1285 1285  )))
1286 1286  
1287 1287  
... ... @@ -1295,69 +1295,50 @@
1295 1295  
1296 1296  == 8.3  Problem after Upgrading Firmware ==
1297 1297  
1298 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1210 +=== 8.3.1 Continue Restart after upgrading ===
1299 1299  
1300 1300  
1301 -**Error Output**
1302 -
1303 -
1304 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1305 -
1306 -
1307 1307  (((
1308 -Some partition is missed during upgrade, please upgrade below four files as example:
1309 -
1310 -[[image:image-20221207120524-2.png]]
1214 +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
1311 1311  )))
1312 1312  
1313 1313  
1314 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1218 +[[image:image-20221118105249-3.png]]
1315 1315  
1316 1316  
1317 -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
1221 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1318 1318  
1319 1319  
1320 -=== 8.3.3 "flash read err" after upgrade firmware ===
1224 +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
1321 1321  
1322 1322  
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 +
1323 1323  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1324 1324  
1231 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1325 1325  
1326 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1327 1327  
1328 -
1329 1329  User need to upgrade again with below four files to solve this issue.
1330 1330  
1331 - [[image:image-20221207120530-3.png]]
1236 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1332 1332  
1333 1333   **Figure 2**
1334 1334  
1335 1335  
1336 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1337 1337  
1338 -
1339 1339  User might erase the entire flash include keys and default settings which cause this issue.
1340 1340  
1341 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1342 1342  
1247 +[[image:image-20221122100004-3.png]]
1343 1343  
1344 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1345 1345  
1346 1346  
1347 -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.
1252 +Example:
1348 1348  
1349 -After AT+FDR. please set
1350 -
1351 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1352 -
1353 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1354 -
1355 -**Example:**
1356 -
1357 -AT+PDOP=7.00
1358 -
1359 -AT+FTIME=180
1360 -
1361 1361  AT+DEUI=70B3D57ED0053981  
1362 1362  
1363 1363  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1371,6 +1371,13 @@
1371 1371  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1372 1372  
1373 1373  
1267 +
1268 +=== 8.3.4  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 ===
1269 +
1270 +
1271 +[[image:image-20221122100004-4.png]]
1272 +
1273 +
1374 1374  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1375 1375  
1376 1376  
... ... @@ -1384,53 +1384,15 @@
1384 1384  
1385 1385  2)  Set PDOP to a higher value.
1386 1386  
1387 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1388 1388  
1389 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1289 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1390 1390  
1391 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1291 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1392 1392  
1393 1393  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
1394 1394  
1395 1395  
1396 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1397 -
1398 -
1399 -When upgrading, use the erase button to upgrade
1400 -
1401 -[[image:image-20221207120536-4.png]]
1402 -
1403 -
1404 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1405 -
1406 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1407 -
1408 -
1409 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1410 -
1411 -[[image:image-20221207134028-8.png]]
1412 -
1413 -
1414 -Reboot information after upgrade
1415 -
1416 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1417 -
1418 -
1419 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1420 -
1421 -[[image:image-20221128111850-5.png]]
1422 -
1423 -
1424 -After the parameters return to normal, upgrade to the version you need again
1425 -
1426 -[[image:image-20221207120601-5.png]]
1427 -
1428 -
1429 -At this point, the parameters return to normal after running AT+FDR again
1430 -
1431 -[[image:image-20221128112035-7.png]]
1432 -
1433 -
1434 1434  = 9.  Order Info =
1435 1435  
1436 1436  
... ... @@ -1452,8 +1452,6 @@
1452 1452  
1453 1453  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1454 1454  
1455 -
1456 -
1457 1457  = 10.  Packing Info =
1458 1458  
1459 1459  
... ... @@ -1469,8 +1469,6 @@
1469 1469  
1470 1470  * Weight: 50g
1471 1471  
1472 -
1473 -
1474 1474  = 11. Support =
1475 1475  
1476 1476  
... ... @@ -1478,8 +1478,6 @@
1478 1478  
1479 1479  * 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]].
1480 1480  
1481 -
1482 -
1483 1483  = 12.  Reference =
1484 1484  
1485 1485  
... ... @@ -1488,4 +1488,3 @@
1488 1488  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1489 1489  
1490 1490  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1491 -)))
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
image-20221207120501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120524-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120530-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120536-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120601-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207133836-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
image-20221207133911-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20221207134028-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20221213100007-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.7 KB
Content
image-20221213100626-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.7 KB
Content
image-20221213100808-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20221213101040-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -26.3 KB
Content
image-20221213102311-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.7 KB
Content
image-20221213102334-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 KB
Content
image-20221213102718-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20221213110952-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.8 KB
Content