Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 187.1
edited by Edwin Chen
on 2022/12/21 10:06
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
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,7 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -
97 97  == 1.3  Features ==
98 98  
99 99  
... ... @@ -112,7 +112,6 @@
112 112  * Tri-color LED, Alarm button
113 113  * Datalog
114 114  
115 -
116 116  == 1.4  Applications ==
117 117  
118 118  
... ... @@ -119,7 +119,6 @@
119 119  * Logistics and Supply Chain Management
120 120  * Human tracking
121 121  
122 -
123 123  = 2.  Use TrackerD =
124 124  
125 125  == 2.1 How it works? ==
... ... @@ -134,7 +134,7 @@
134 134  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. 
135 135  
136 136  
137 -[[image:1664501652064-326.png||_mstalt="293306"]]
136 +[[image:1664501652064-326.png]]
138 138  
139 139  
140 140  
... ... @@ -146,7 +146,7 @@
146 146  Each TrackerD is shipped with a sticker with the default device EUI as below:
147 147  
148 148  
149 -[[image:1664501677253-891.png||_mstalt="296569"]]
148 +[[image:1664501677253-891.png]]
150 150  
151 151  
152 152  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -155,14 +155,14 @@
155 155  **__Add APP EUI in the application:__**
156 156  
157 157  
158 -[[image:1664501711466-918.png||_mstalt="295828"]]
157 +[[image:1664501711466-918.png]]
159 159  
160 160  
161 161  
162 -[[image:1664501721248-725.png||_mstalt="294450"]]
161 +[[image:1664501721248-725.png]]
163 163  
164 164  
165 -[[image:1664501734705-405.png||_mstalt="293306"]]
164 +[[image:1664501734705-405.png]]
166 166  
167 167  
168 168  
... ... @@ -169,15 +169,15 @@
169 169  **__Add APP KEY and DEV EUI:__**
170 170  
171 171  
172 -[[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"]]
173 173  
174 174  
175 175  
176 176  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
177 177  
178 -(% 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]]
179 179  
180 -[[image:1664502835802-546.png||_mstalt="295061"]]
179 +[[image:1664502835802-546.png]]
181 181  
182 182  
183 183  (% 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.
... ... @@ -209,7 +209,7 @@
209 209  |=(% 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
210 210  |=(% 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
211 211  
212 -[[image:1665301570342-765.png||_mstalt="294580"]]
211 +[[image:1665301570342-765.png]]
213 213  
214 214  
215 215  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -276,7 +276,7 @@
276 276  
277 277  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
278 278  
279 -(% _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)(%%)  
280 280  
281 281  
282 282  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -285,7 +285,6 @@
285 285  |=(% 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
286 286  |=(% 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"]]
287 287  
288 -
289 289  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
290 290  
291 291  
... ... @@ -304,7 +304,7 @@
304 304  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
305 305  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
306 306  
307 -[[image:1665301636888-168.png||_mstalt="298012"]]
305 +[[image:1665301636888-168.png]]
308 308  
309 309  
310 310  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -334,12 +334,12 @@
334 334  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:
335 335  
336 336  
337 -[[image:1664502116362-706.png||_mstalt="293306"]]
335 +[[image:1664502116362-706.png]]
338 338  
339 339  
340 340  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
341 341  
342 -[[image:1664502166010-515.png||_mstalt="291395"]]
340 +[[image:1664502166010-515.png]]
343 343  
344 344  
345 345  
... ... @@ -362,7 +362,6 @@
362 362  * 3.40v ~~ 3.69v:  20% ~~ 40%
363 363  * < 3.39v:  0~~20%
364 364  
365 -
366 366  ==== (% style="color:blue" %)**MOD:**(%%) ====
367 367  
368 368  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -418,13 +418,13 @@
418 418  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
419 419  
420 420  (% class="wikigeneratedid" %)
421 -[[image:1665301687277-443.png||_mstalt="296140"]]
418 +[[image:1665301687277-443.png]]
422 422  
423 423  
424 424  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
425 425  
426 426  
427 -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.
428 428  
429 429  
430 430  (% style="color:red" %)**Note for this mode:**
... ... @@ -441,7 +441,7 @@
441 441  )))|4|4|2|1|1|1|1|1
442 442  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
443 443  
444 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
441 +[[image:image-20221009160309-2.png]]
445 445  
446 446  
447 447  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -468,7 +468,7 @@
468 468  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
469 469  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
470 470  
471 -[[image:1664502425687-834.png||_mstalt="296738"]]
468 +[[image:1664502425687-834.png]]
472 472  
473 473  
474 474  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -479,7 +479,6 @@
479 479  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
480 480  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
481 481  
482 -
483 483  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
484 484  
485 485  
... ... @@ -495,7 +495,7 @@
495 495  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
496 496  
497 497  (% class="wikigeneratedid" %)
498 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
494 +[[image:1667288597595-714.png||height="212" width="1151"]]
499 499  
500 500  
501 501  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -502,7 +502,6 @@
502 502  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
503 503  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
504 504  
505 -
506 506  === 2.4.7  Add Payload format in TTN V3 ===
507 507  
508 508  
... ... @@ -511,7 +511,7 @@
511 511  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
512 512  
513 513  
514 -[[image:1664502649601-895.png||_mstalt="296985"]]
509 +[[image:1664502649601-895.png]]
515 515  
516 516  
517 517  
... ... @@ -521,7 +521,7 @@
521 521  
522 522  Save the change the uplink message will be parsed. As below:
523 523  
524 -[[image:1664502676891-606.png||_mstalt="296673"]]
519 +[[image:1664502676891-606.png]]
525 525  
526 526  
527 527  == 2.5 Integrate with Datacake ==
... ... @@ -532,7 +532,7 @@
532 532  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]]
533 533  
534 534  
535 -[[image:1664502695771-538.png||_mstalt="297349"]]
530 +[[image:1664502695771-538.png]]
536 536  
537 537  
538 538  == 2.6 Integrate with Tago ==
... ... @@ -543,7 +543,7 @@
543 543  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]]
544 544  
545 545  
546 -[[image:1664502715371-321.png||_mstalt="292162"]]
541 +[[image:1664502715371-321.png]]
547 547  
548 548  
549 549  == 2.7  Datalog Feature ==
... ... @@ -551,14 +551,14 @@
551 551  
552 552  total 273 entries,by default,
553 553  
554 -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.
555 555  
556 556  Example use case.
557 557  
558 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||height="328" width="899"]]
559 559  
560 560  
561 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||height="390" width="577"]]
562 562  
563 563  
564 564  == 2.8 Alarm Mode ==
... ... @@ -591,11 +591,7 @@
591 591  
592 592  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.
593 593  
594 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
595 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
596 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
597 597  
598 -
599 599  == 2.10 LED Status ==
600 600  
601 601  
... ... @@ -613,13 +613,12 @@
613 613  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
614 614  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
615 615  
616 -
617 617  == 2.11 Button Function ==
618 618  
619 619  
620 620  (% style="color:blue" %)**RESET button:**
621 621  
622 -[[image:1664502835802-546.png||_mstalt="295061"]]
612 +[[image:1664502835802-546.png]]
623 623  
624 624  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
625 625  
... ... @@ -626,7 +626,7 @@
626 626  
627 627  (% style="color:red" %)**RED button:**
628 628  
629 -[[image:1664502854406-763.png||_mstalt="295568"]]
619 +[[image:1664502854406-763.png]]
630 630  
631 631  
632 632  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -635,7 +635,6 @@
635 635  |(% 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
636 636  |(% 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.
637 637  
638 -
639 639  == 2.12 USB Port Function ==
640 640  
641 641  
... ... @@ -646,7 +646,6 @@
646 646  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
647 647  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
648 648  
649 -
650 650  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
651 651  
652 652  
... ... @@ -661,21 +661,22 @@
661 661  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.
662 662  
663 663  
664 -[[image:1664502999401-486.png||_mstalt="296985"]]
652 +[[image:1664502999401-486.png]]
665 665  
666 666  
667 667  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:
668 668  
669 669  
670 -[[image:1664503022490-662.png||_mstalt="293332"]]
658 +[[image:1664503022490-662.png]]
671 671  
672 672  
673 -[[image:1664503035713-500.png||_mstalt="291096"]]
661 +[[image:1664503035713-500.png]]
674 674  
675 675  
676 -[[image:1664503047675-651.png||_mstalt="295386"]]
664 +[[image:1664503047675-651.png]]
677 677  
678 678  
667 +
679 679  == 3.2 Command Set ==
680 680  
681 681  === 3.2.1 Set Transmit Interval ===
... ... @@ -801,9 +801,9 @@
801 801  
802 802  (% style="color:#037691" %)**cc:   **
803 803  
804 -* (% _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  
805 805  
806 -* (% _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(%%))  
807 807  
808 808  (% style="color:blue" %)**Example:**
809 809  
... ... @@ -865,8 +865,8 @@
865 865  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
866 866  
867 867  
868 -=== 3.2.10 Disable/Enable the confirmation mode ===
869 869  
858 +**Disable/Enable the confirmation mode**
870 870  
871 871  * (% style="color:blue" %)**AT Command:**
872 872  
... ... @@ -885,7 +885,7 @@
885 885  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
886 886  
887 887  
888 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
889 889  
890 890  
891 891  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.
... ... @@ -903,10 +903,10 @@
903 903  
904 904  * (% style="color:blue" %)**Downlink Command: 0x34**
905 905  
906 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
907 907  
908 908  
909 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
910 910  
911 911  
912 912  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.
... ... @@ -915,16 +915,16 @@
915 915  
916 916  (% style="color:blue" %)**AT Command:**
917 917  
918 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
907 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
919 919  
920 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
909 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
921 921  
922 922  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
923 923  
924 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
925 925  
926 926  
927 -=== 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） ===
928 928  
929 929  
930 930  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.
... ... @@ -933,16 +933,16 @@
933 933  
934 934  (% style="color:blue" %)**AT Command:**
935 935  
936 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
925 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
937 937  
938 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
927 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
939 939  
940 940  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
941 941  
942 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
943 943  
944 944  
945 -=== 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） ===
946 946  
947 947  
948 948  Users can use this feature to enable/disable Information printing.
... ... @@ -949,11 +949,11 @@
949 949  
950 950  (% style="color:blue" %)**AT Command:**
951 951  
952 -(% 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)
953 953  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
954 954  
955 955  
956 -=== 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） ===
957 957  
958 958  
959 959  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -960,34 +960,14 @@
960 960  
961 961  (% style="color:blue" %)**AT Command:**
962 962  
963 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
964 964  
965 965  
966 966  (% style="color:blue" %)**Downlink Payload:0X24**
967 967  
968 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
969 969  
970 970  
971 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
972 -
973 -
974 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
975 -
976 -(% style="color:blue" %)**AT Command:**
977 -
978 -(% style="color:#037691" %)**AT+PT=xx**
979 -
980 - Example:
981 -
982 - AT+PT=14    ~-~->    Set to detect car motion.
983 -
984 - AT+PT=41  ~-~->    set to detect walk motion.
985 -
986 -
987 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
988 -0xB4 14          ~/~/  Same as AT+PT=14
989 -
990 -
991 991  = 4. Setting for Different Scenarios =
992 992  
993 993  
... ... @@ -1020,10 +1020,10 @@
1020 1020  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1021 1021  
1022 1022  
1023 -[[image:1664503563660-578.png||_mstalt="296777"]]
992 +[[image:1664503563660-578.png]]
1024 1024  
1025 1025  
1026 -[[image:1664503574618-659.png||_mstalt="297986"]]
995 +[[image:1664503574618-659.png]]
1027 1027  
1028 1028  
1029 1029  
... ... @@ -1039,15 +1039,16 @@
1039 1039  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1040 1040  
1041 1041  
1042 -[[image:image-20221207120501-1.png]]
1011 +[[image:image-20221118105220-2.png]]
1043 1043  
1044 1044  
1045 1045  
1046 1046  After upgrade finish, it will show finish as below:
1047 1047  
1048 -[[image:image-20221207133911-7.png]]
1017 +[[image:image-20221118105402-4.png]]
1049 1049  
1050 1050  
1020 +
1051 1051  = 6. Developer Guide =
1052 1052  
1053 1053  == 6.1 Compile Source Code ==
... ... @@ -1060,80 +1060,24 @@
1060 1060  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]]
1061 1061  
1062 1062  
1063 -[[image:1664503635019-941.png||_mstalt="294658"]]
1033 +[[image:1664503635019-941.png]]
1064 1064  
1065 1065  
1066 1066  
1067 1067  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1068 1068  
1069 -[[image:1664503715811-892.png||_mstalt="295698"]]
1039 +[[image:1664503715811-892.png]]
1070 1070  
1071 1071  
1072 -=== 6.1.2  Build the development environment ===
1073 -
1074 -
1075 -**~1. Download and install arduino IDE**
1076 -
1077 -[[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]]
1078 -
1079 -
1080 -**2. Download the ESP32 development package in the arduino IDE**
1081 -
1082 -[[image:image-20221213100007-1.png]]
1083 -
1084 -
1085 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1086 -
1087 -[[image:image-20221213100626-2.png]]
1088 -
1089 -
1090 -Restart the IDE after the addition is complete, then:
1091 -
1092 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1093 -
1094 -
1095 -[[image:image-20221213101040-4.png]]
1096 -
1097 -
1098 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1099 -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)**
1100 -
1101 -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:
1102 -
1103 -(% style="color:blue" %)**Methods as below:**
1104 -
1105 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1106 -
1107 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1108 -
1109 1109  (% 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.
1110 1110  
1111 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1044 +[[image:image-20221024105643-1.png]]
1112 1112  
1113 -
1114 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1115 -
1116 -[[image:image-20221213102334-6.png]]
1117 -
1118 -(% style="color:red" %)**Note: This step requires a python environment**
1119 -
1120 -
1121 -Either way, in the end:
1122 -
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,7 +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 1195  == 7.3 Notes on using different serial port tools for TrackerD ==
1196 1196  
1197 1197  === 7.3.1  Serial port utility ===
... ... @@ -1202,13 +1202,13 @@
1202 1202  Need to adjust the data stream to RTS/CTS on physical restart.
1203 1203  
1204 1204  (% class="wikigeneratedid" %)
1205 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1118 +[[image:image-20221102140621-1.png]]
1206 1206  
1207 1207  
1208 1208  
1209 1209  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1210 1210  
1211 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1124 +[[image:image-20221102140638-2.png]]
1212 1212  
1213 1213  
1214 1214  === 7.3.2  SecureCRT ===
... ... @@ -1217,22 +1217,22 @@
1217 1217  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.
1218 1218  
1219 1219  
1220 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1133 +[[image:image-20221102140704-3.png]]
1221 1221  
1222 1222  
1223 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1136 +[[image:image-20221102140712-4.png]]
1224 1224  
1225 1225  
1226 1226  === 7.3.3  PUTTY ===
1227 1227  
1228 1228  
1229 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1142 +[[image:image-20221102140748-5.png]]
1230 1230  
1231 1231  
1232 1232  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.
1233 1233  
1234 1234  
1235 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1148 +[[image:image-20221102140801-6.png]]
1236 1236  
1237 1237  
1238 1238  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1247,7 +1247,7 @@
1247 1247  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1248 1248  
1249 1249  
1250 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1163 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1251 1251  
1252 1252  
1253 1253  
... ... @@ -1254,7 +1254,7 @@
1254 1254  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1255 1255  
1256 1256  
1257 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1170 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1258 1258  
1259 1259  
1260 1260  
... ... @@ -1261,7 +1261,7 @@
1261 1261  **3. Compile the AS923_JP band, please refer to the intention shown**
1262 1262  
1263 1263  
1264 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1177 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1265 1265  
1266 1266  
1267 1267  
... ... @@ -1268,16 +1268,12 @@
1268 1268  **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.**
1269 1269  
1270 1270  
1271 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1184 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1272 1272  
1273 1273  
1274 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1187 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1275 1275  
1276 1276  
1277 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1278 -
1279 -
1280 -
1281 1281  = 8  Trouble Shooting =
1282 1282  
1283 1283  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1284,7 +1284,7 @@
1284 1284  
1285 1285  
1286 1286  (((
1287 -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
1288 1288  )))
1289 1289  
1290 1290  
... ... @@ -1298,69 +1298,50 @@
1298 1298  
1299 1299  == 8.3  Problem after Upgrading Firmware ==
1300 1300  
1301 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1210 +=== 8.3.1 Continue Restart after upgrading ===
1302 1302  
1303 1303  
1304 -**Error Output**
1305 -
1306 -
1307 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1308 -
1309 -
1310 1310  (((
1311 -Some partition is missed during upgrade, please upgrade below four files as example:
1312 -
1313 -[[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
1314 1314  )))
1315 1315  
1316 1316  
1317 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1218 +[[image:image-20221118105249-3.png]]
1318 1318  
1319 1319  
1320 -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 ===
1321 1321  
1322 1322  
1323 -=== 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
1324 1324  
1325 1325  
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 +
1326 1326  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1327 1327  
1231 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1328 1328  
1329 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1330 1330  
1331 -
1332 1332  User need to upgrade again with below four files to solve this issue.
1333 1333  
1334 - [[image:image-20221207120530-3.png]]
1236 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1335 1335  
1336 1336   **Figure 2**
1337 1337  
1338 1338  
1339 -=== 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 ===
1340 1340  
1341 -
1342 1342  User might erase the entire flash include keys and default settings which cause this issue.
1343 1343  
1344 -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.
1345 1345  
1247 +[[image:image-20221122100004-3.png]]
1346 1346  
1347 -[[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.
1348 1348  
1349 1349  
1350 -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:
1351 1351  
1352 -After AT+FDR. please set
1353 -
1354 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1355 -
1356 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1357 -
1358 -**Example:**
1359 -
1360 -AT+PDOP=7.00
1361 -
1362 -AT+FTIME=180
1363 -
1364 1364  AT+DEUI=70B3D57ED0053981  
1365 1365  
1366 1366  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1374,6 +1374,13 @@
1374 1374  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1375 1375  
1376 1376  
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 +
1377 1377  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1378 1378  
1379 1379  
... ... @@ -1387,61 +1387,15 @@
1387 1387  
1388 1388  2)  Set PDOP to a higher value.
1389 1389  
1390 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1391 1391  
1392 -* (% _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）
1393 1393  
1394 -* (% _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）
1395 1395  
1396 1396  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
1397 1397  
1398 1398  
1399 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1400 -
1401 -
1402 -When upgrading, use the erase button to upgrade
1403 -
1404 -[[image:image-20221207120536-4.png]]
1405 -
1406 -
1407 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1408 -
1409 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1410 -
1411 -
1412 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1413 -
1414 -[[image:image-20221207134028-8.png]]
1415 -
1416 -
1417 -Reboot information after upgrade
1418 -
1419 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1420 -
1421 -
1422 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1423 -
1424 -[[image:image-20221128111850-5.png]]
1425 -
1426 -
1427 -After the parameters return to normal, upgrade to the version you need again
1428 -
1429 -[[image:image-20221207120601-5.png]]
1430 -
1431 -
1432 -At this point, the parameters return to normal after running AT+FDR again
1433 -
1434 -[[image:image-20221128112035-7.png]]
1435 -
1436 -
1437 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1438 -
1439 -
1440 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1441 -
1442 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1443 -
1444 -
1445 1445  = 9.  Order Info =
1446 1446  
1447 1447  
... ... @@ -1463,7 +1463,6 @@
1463 1463  
1464 1464  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1465 1465  
1466 -
1467 1467  = 10.  Packing Info =
1468 1468  
1469 1469  
... ... @@ -1479,7 +1479,6 @@
1479 1479  
1480 1480  * Weight: 50g
1481 1481  
1482 -
1483 1483  = 11. Support =
1484 1484  
1485 1485  
... ... @@ -1487,7 +1487,6 @@
1487 1487  
1488 1488  * 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]].
1489 1489  
1490 -
1491 1491  = 12.  Reference =
1492 1492  
1493 1493  
... ... @@ -1496,4 +1496,3 @@
1496 1496  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1497 1497  
1498 1498  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1499 -)))
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