Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 186.2
edited by Xiaoling
on 2022/12/16 10:34
Change comment: There is no comment for this version
To version 143.2
edited by Xiaoling
on 2022/11/22 10:54
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,6 +93,8 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
98 +
99 +
96 96  == 1.3  Features ==
97 97  
98 98  
... ... @@ -111,6 +111,8 @@
111 111  * Tri-color LED, Alarm button
112 112  * Datalog
113 113  
118 +
119 +
114 114  == 1.4  Applications ==
115 115  
116 116  
... ... @@ -117,6 +117,8 @@
117 117  * Logistics and Supply Chain Management
118 118  * Human tracking
119 119  
126 +
127 +
120 120  = 2.  Use TrackerD =
121 121  
122 122  == 2.1 How it works? ==
... ... @@ -131,7 +131,7 @@
131 131  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. 
132 132  
133 133  
134 -[[image:1664501652064-326.png||_mstalt="293306"]]
142 +[[image:1664501652064-326.png]]
135 135  
136 136  
137 137  
... ... @@ -143,7 +143,7 @@
143 143  Each TrackerD is shipped with a sticker with the default device EUI as below:
144 144  
145 145  
146 -[[image:1664501677253-891.png||_mstalt="296569"]]
154 +[[image:1664501677253-891.png]]
147 147  
148 148  
149 149  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -152,14 +152,14 @@
152 152  **__Add APP EUI in the application:__**
153 153  
154 154  
155 -[[image:1664501711466-918.png||_mstalt="295828"]]
163 +[[image:1664501711466-918.png]]
156 156  
157 157  
158 158  
159 -[[image:1664501721248-725.png||_mstalt="294450"]]
167 +[[image:1664501721248-725.png]]
160 160  
161 161  
162 -[[image:1664501734705-405.png||_mstalt="293306"]]
170 +[[image:1664501734705-405.png]]
163 163  
164 164  
165 165  
... ... @@ -166,15 +166,15 @@
166 166  **__Add APP KEY and DEV EUI:__**
167 167  
168 168  
169 -[[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"]]
177 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
170 170  
171 171  
172 172  
173 173  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
174 174  
175 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
183 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
176 176  
177 -[[image:1664502835802-546.png||_mstalt="295061"]]
185 +[[image:1664502835802-546.png]]
178 178  
179 179  
180 180  (% 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.
... ... @@ -206,7 +206,7 @@
206 206  |=(% 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
207 207  |=(% 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
208 208  
209 -[[image:1665301570342-765.png||_mstalt="294580"]]
217 +[[image:1665301570342-765.png]]
210 210  
211 211  
212 212  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -273,7 +273,7 @@
273 273  
274 274  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
275 275  
276 -(% _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)(%%)  
284 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
277 277  
278 278  
279 279  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -282,6 +282,8 @@
282 282  |=(% 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
283 283  |=(% 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"]]
284 284  
293 +
294 +
285 285  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
286 286  
287 287  
... ... @@ -300,7 +300,7 @@
300 300  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
301 301  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
302 302  
303 -[[image:1665301636888-168.png||_mstalt="298012"]]
313 +[[image:1665301636888-168.png]]
304 304  
305 305  
306 306  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -309,6 +309,8 @@
309 309  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
310 310  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
311 311  
322 +
323 +
312 312  ==== (% style="color:blue" %)**FLAG:**(%%) ====
313 313  
314 314  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -330,12 +330,12 @@
330 330  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:
331 331  
332 332  
333 -[[image:1664502116362-706.png||_mstalt="293306"]]
345 +[[image:1664502116362-706.png]]
334 334  
335 335  
336 336  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
337 337  
338 -[[image:1664502166010-515.png||_mstalt="291395"]]
350 +[[image:1664502166010-515.png]]
339 339  
340 340  
341 341  
... ... @@ -358,6 +358,8 @@
358 358  * 3.40v ~~ 3.69v:  20% ~~ 40%
359 359  * < 3.39v:  0~~20%
360 360  
373 +
374 +
361 361  ==== (% style="color:blue" %)**MOD:**(%%) ====
362 362  
363 363  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -413,13 +413,13 @@
413 413  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
414 414  
415 415  (% class="wikigeneratedid" %)
416 -[[image:1665301687277-443.png||_mstalt="296140"]]
430 +[[image:1665301687277-443.png]]
417 417  
418 418  
419 419  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
420 420  
421 421  
422 -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.
436 +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.
423 423  
424 424  
425 425  (% style="color:red" %)**Note for this mode:**
... ... @@ -436,7 +436,7 @@
436 436  )))|4|4|2|1|1|1|1|1
437 437  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
438 438  
439 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
453 +[[image:image-20221009160309-2.png]]
440 440  
441 441  
442 442  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -463,7 +463,7 @@
463 463  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
464 464  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
465 465  
466 -[[image:1664502425687-834.png||_mstalt="296738"]]
480 +[[image:1664502425687-834.png]]
467 467  
468 468  
469 469  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -474,6 +474,8 @@
474 474  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
475 475  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
476 476  
491 +
492 +
477 477  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
478 478  
479 479  
... ... @@ -489,7 +489,7 @@
489 489  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
490 490  
491 491  (% class="wikigeneratedid" %)
492 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
508 +[[image:1667288597595-714.png||height="212" width="1151"]]
493 493  
494 494  
495 495  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -496,6 +496,8 @@
496 496  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
497 497  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
498 498  
515 +
516 +
499 499  === 2.4.7  Add Payload format in TTN V3 ===
500 500  
501 501  
... ... @@ -504,7 +504,7 @@
504 504  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
505 505  
506 506  
507 -[[image:1664502649601-895.png||_mstalt="296985"]]
525 +[[image:1664502649601-895.png]]
508 508  
509 509  
510 510  
... ... @@ -514,7 +514,7 @@
514 514  
515 515  Save the change the uplink message will be parsed. As below:
516 516  
517 -[[image:1664502676891-606.png||_mstalt="296673"]]
535 +[[image:1664502676891-606.png]]
518 518  
519 519  
520 520  == 2.5 Integrate with Datacake ==
... ... @@ -525,7 +525,7 @@
525 525  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]]
526 526  
527 527  
528 -[[image:1664502695771-538.png||_mstalt="297349"]]
546 +[[image:1664502695771-538.png]]
529 529  
530 530  
531 531  == 2.6 Integrate with Tago ==
... ... @@ -536,7 +536,7 @@
536 536  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]]
537 537  
538 538  
539 -[[image:1664502715371-321.png||_mstalt="292162"]]
557 +[[image:1664502715371-321.png]]
540 540  
541 541  
542 542  == 2.7  Datalog Feature ==
... ... @@ -544,14 +544,14 @@
544 544  
545 545  total 273 entries,by default,
546 546  
547 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
565 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
548 548  
549 549  Example use case.
550 550  
551 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
569 +[[image:image-20221009234703-2.png||height="328" width="899"]]
552 552  
553 553  
554 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
572 +[[image:image-20221009234629-1.png||height="390" width="577"]]
555 555  
556 556  
557 557  == 2.8 Alarm Mode ==
... ... @@ -584,9 +584,6 @@
584 584  
585 585  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.
586 586  
587 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
588 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
589 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
590 590  
591 591  == 2.10 LED Status ==
592 592  
... ... @@ -605,12 +605,14 @@
605 605  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
606 606  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
607 607  
623 +
624 +
608 608  == 2.11 Button Function ==
609 609  
610 610  
611 611  (% style="color:blue" %)**RESET button:**
612 612  
613 -[[image:1664502835802-546.png||_mstalt="295061"]]
630 +[[image:1664502835802-546.png]]
614 614  
615 615  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
616 616  
... ... @@ -617,7 +617,7 @@
617 617  
618 618  (% style="color:red" %)**RED button:**
619 619  
620 -[[image:1664502854406-763.png||_mstalt="295568"]]
637 +[[image:1664502854406-763.png]]
621 621  
622 622  
623 623  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -626,6 +626,8 @@
626 626  |(% 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
627 627  |(% 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.
628 628  
646 +
647 +
629 629  == 2.12 USB Port Function ==
630 630  
631 631  
... ... @@ -636,6 +636,8 @@
636 636  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
637 637  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
638 638  
658 +
659 +
639 639  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
640 640  
641 641  
... ... @@ -650,21 +650,22 @@
650 650  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.
651 651  
652 652  
653 -[[image:1664502999401-486.png||_mstalt="296985"]]
674 +[[image:1664502999401-486.png]]
654 654  
655 655  
656 656  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:
657 657  
658 658  
659 -[[image:1664503022490-662.png||_mstalt="293332"]]
680 +[[image:1664503022490-662.png]]
660 660  
661 661  
662 -[[image:1664503035713-500.png||_mstalt="291096"]]
683 +[[image:1664503035713-500.png]]
663 663  
664 664  
665 -[[image:1664503047675-651.png||_mstalt="295386"]]
686 +[[image:1664503047675-651.png]]
666 666  
667 667  
689 +
668 668  == 3.2 Command Set ==
669 669  
670 670  === 3.2.1 Set Transmit Interval ===
... ... @@ -790,9 +790,9 @@
790 790  
791 791  (% style="color:#037691" %)**cc:   **
792 792  
793 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
815 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
794 794  
795 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
817 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
796 796  
797 797  (% style="color:blue" %)**Example:**
798 798  
... ... @@ -854,8 +854,8 @@
854 854  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
855 855  
856 856  
857 -=== 3.2.10 Disable/Enable the confirmation mode ===
858 858  
880 +**Disable/Enable the confirmation mode**
859 859  
860 860  * (% style="color:blue" %)**AT Command:**
861 861  
... ... @@ -874,7 +874,7 @@
874 874  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
875 875  
876 876  
877 -=== 3.2.11  Auto Send None-ACK messages ===
899 +=== 3.2.10  Auto Send None-ACK messages ===
878 878  
879 879  
880 880  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.
... ... @@ -892,10 +892,10 @@
892 892  
893 893  * (% style="color:blue" %)**Downlink Command: 0x34**
894 894  
895 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
896 896  
897 897  
898 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
920 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
899 899  
900 900  
901 901  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.
... ... @@ -904,16 +904,16 @@
904 904  
905 905  (% style="color:blue" %)**AT Command:**
906 906  
907 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
908 908  
909 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
910 910  
911 911  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
912 912  
913 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
935 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
914 914  
915 915  
916 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
938 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
917 917  
918 918  
919 919  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.
... ... @@ -922,16 +922,16 @@
922 922  
923 923  (% style="color:blue" %)**AT Command:**
924 924  
925 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
926 926  
927 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
928 928  
929 929  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
930 930  
931 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
953 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
932 932  
933 933  
934 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
956 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
935 935  
936 936  
937 937  Users can use this feature to enable/disable Information printing.
... ... @@ -938,11 +938,11 @@
938 938  
939 939  (% style="color:blue" %)**AT Command:**
940 940  
941 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
963 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
942 942  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
943 943  
944 944  
945 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
967 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
946 946  
947 947  
948 948  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -949,34 +949,14 @@
949 949  
950 950  (% style="color:blue" %)**AT Command:**
951 951  
952 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
974 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
953 953  
954 954  
955 955  (% style="color:blue" %)**Downlink Payload:0X24**
956 956  
957 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
979 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
958 958  
959 959  
960 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
961 -
962 -
963 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
964 -
965 -(% style="color:blue" %)**AT Command:**
966 -
967 -(% style="color:#037691" %)**AT+PT=xx**
968 -
969 - Example:
970 -
971 - AT+PT=14    ~-~->    Set to detect car motion.
972 -
973 - AT+PT=41  ~-~->    set to detect walk motion.
974 -
975 -
976 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
977 -0xB4 14          ~/~/  Same as AT+PT=14
978 -
979 -
980 980  = 4. Setting for Different Scenarios =
981 981  
982 982  
... ... @@ -1009,10 +1009,10 @@
1009 1009  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1010 1010  
1011 1011  
1012 -[[image:1664503563660-578.png||_mstalt="296777"]]
1014 +[[image:1664503563660-578.png]]
1013 1013  
1014 1014  
1015 -[[image:1664503574618-659.png||_mstalt="297986"]]
1017 +[[image:1664503574618-659.png]]
1016 1016  
1017 1017  
1018 1018  
... ... @@ -1028,15 +1028,16 @@
1028 1028  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1029 1029  
1030 1030  
1031 -[[image:image-20221207120501-1.png]]
1033 +[[image:image-20221118105220-2.png]]
1032 1032  
1033 1033  
1034 1034  
1035 1035  After upgrade finish, it will show finish as below:
1036 1036  
1037 -[[image:image-20221207133911-7.png]]
1039 +[[image:image-20221118105402-4.png]]
1038 1038  
1039 1039  
1042 +
1040 1040  = 6. Developer Guide =
1041 1041  
1042 1042  == 6.1 Compile Source Code ==
... ... @@ -1049,80 +1049,24 @@
1049 1049  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]]
1050 1050  
1051 1051  
1052 -[[image:1664503635019-941.png||_mstalt="294658"]]
1055 +[[image:1664503635019-941.png]]
1053 1053  
1054 1054  
1055 1055  
1056 1056  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1057 1057  
1058 -[[image:1664503715811-892.png||_mstalt="295698"]]
1061 +[[image:1664503715811-892.png]]
1059 1059  
1060 1060  
1061 -=== 6.1.2 Build the development environment ===
1062 -
1063 -
1064 -**~1. Download and install arduino IDE**
1065 -
1066 -[[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]]
1067 -
1068 -
1069 -**2. Download the ESP32 development package in the arduino IDE**
1070 -
1071 -[[image:image-20221213100007-1.png]]
1072 -
1073 -
1074 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1075 -
1076 -[[image:image-20221213100626-2.png]]
1077 -
1078 -
1079 -Restart the IDE after the addition is complete, then:
1080 -
1081 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1082 -
1083 -
1084 -[[image:image-20221213101040-4.png]]
1085 -
1086 -
1087 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1088 -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)**
1089 -
1090 -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:
1091 -
1092 -(% style="color:blue" %)**Methods as below:**
1093 -
1094 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1095 -
1096 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1097 -
1098 1098  (% 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.
1099 1099  
1100 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1066 +[[image:image-20221024105643-1.png]]
1101 1101  
1102 -
1103 -3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)
1104 -
1105 -[[image:image-20221213102334-6.png]]
1106 -
1107 -(% style="color:red" %)**Note: This step requires a python environment**
1108 -
1109 -
1110 -Either way, in the end:
1111 -
1112 -The final effect is to open the arduino and you can see the esp32
1113 -
1114 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1115 -
1116 -
1117 -
1118 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1119 -
1120 1120  **~ Figure1**
1121 1121  
1122 1122  
1071 +[[image:image-20221024105643-2.png]]
1123 1123  
1124 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1125 -
1126 1126   **Figure2**
1127 1127  
1128 1128  
... ... @@ -1131,7 +1131,7 @@
1131 1131  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1132 1132  
1133 1133  
1134 -[[image:1664503752288-974.png||_mstalt="298194"]]
1081 +[[image:1664503752288-974.png]]
1135 1135  
1136 1136  
1137 1137  == 6.2 Source Code ==
... ... @@ -1139,19 +1139,19 @@
1139 1139  
1140 1140  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1141 1141  
1142 -[[image:1664503794261-827.png||_mstalt="296387"]]
1089 +[[image:1664503794261-827.png]]
1143 1143  
1144 1144  
1145 1145  
1146 1146  * (% style="color:blue" %)**Click to upload**
1147 1147  
1148 -[[image:1664503808294-336.png||_mstalt="295711"]]
1095 +[[image:1664503808294-336.png]]
1149 1149  
1150 1150  
1151 1151  
1152 1152  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1153 1153  
1154 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1101 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1155 1155  
1156 1156  
1157 1157  = 7.  FAQ =
... ... @@ -1165,7 +1165,7 @@
1165 1165  == 7.2 What is the pin mapping for the USB program cable? ==
1166 1166  
1167 1167  
1168 -[[image:1664499635206-262.png||_mstalt="295360"]]
1115 +[[image:1664499635206-262.png]]
1169 1169  
1170 1170  
1171 1171  
... ... @@ -1192,13 +1192,13 @@
1192 1192  Need to adjust the data stream to RTS/CTS on physical restart.
1193 1193  
1194 1194  (% class="wikigeneratedid" %)
1195 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1142 +[[image:image-20221102140621-1.png]]
1196 1196  
1197 1197  
1198 1198  
1199 1199  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1200 1200  
1201 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1148 +[[image:image-20221102140638-2.png]]
1202 1202  
1203 1203  
1204 1204  === 7.3.2  SecureCRT ===
... ... @@ -1207,22 +1207,22 @@
1207 1207  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.
1208 1208  
1209 1209  
1210 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1157 +[[image:image-20221102140704-3.png]]
1211 1211  
1212 1212  
1213 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1160 +[[image:image-20221102140712-4.png]]
1214 1214  
1215 1215  
1216 1216  === 7.3.3  PUTTY ===
1217 1217  
1218 1218  
1219 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1166 +[[image:image-20221102140748-5.png]]
1220 1220  
1221 1221  
1222 1222  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.
1223 1223  
1224 1224  
1225 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1172 +[[image:image-20221102140801-6.png]]
1226 1226  
1227 1227  
1228 1228  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1237,7 +1237,7 @@
1237 1237  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1238 1238  
1239 1239  
1240 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1187 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1241 1241  
1242 1242  
1243 1243  
... ... @@ -1244,7 +1244,7 @@
1244 1244  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1245 1245  
1246 1246  
1247 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1194 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1248 1248  
1249 1249  
1250 1250  
... ... @@ -1251,7 +1251,7 @@
1251 1251  **3. Compile the AS923_JP band, please refer to the intention shown**
1252 1252  
1253 1253  
1254 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1201 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1255 1255  
1256 1256  
1257 1257  
... ... @@ -1258,10 +1258,10 @@
1258 1258  **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.**
1259 1259  
1260 1260  
1261 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1208 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1262 1262  
1263 1263  
1264 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1211 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1265 1265  
1266 1266  
1267 1267  = 8  Trouble Shooting =
... ... @@ -1270,7 +1270,7 @@
1270 1270  
1271 1271  
1272 1272  (((
1273 -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
1220 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1274 1274  )))
1275 1275  
1276 1276  
... ... @@ -1284,82 +1284,65 @@
1284 1284  
1285 1285  == 8.3  Problem after Upgrading Firmware ==
1286 1286  
1287 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1234 +=== 8.3.1 Continue Restart after upgrading ===
1288 1288  
1289 1289  
1290 -**Error Output**
1291 -
1292 -
1293 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1294 -
1295 -
1296 1296  (((
1297 -Some partition is missed during upgrade, please upgrade below four files as example:
1298 -
1299 -[[image:image-20221207120524-2.png]]
1238 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1300 1300  )))
1301 1301  
1302 1302  
1303 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1242 +[[image:image-20221118105249-3.png]]
1304 1304  
1305 1305  
1306 -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
1245 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1307 1307  
1308 1308  
1309 -=== 8.3.3 "flash read err" after upgrade firmware ===
1248 +It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
1310 1310  
1311 1311  
1312 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1313 1313  
1252 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1314 1314  
1315 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1316 1316  
1255 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1317 1317  
1318 -User need to upgrade again with below four files to solve this issue.
1257 + ** Figure 1  **
1319 1319  
1320 - [[image:image-20221207120530-3.png]]
1321 1321  
1260 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1261 +
1322 1322   **Figure 2**
1323 1323  
1324 1324  
1325 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1326 1326  
1266 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1327 1327  
1328 -User might erase the entire flash include keys and default settings which cause this issue.
1329 1329  
1330 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1269 +[[image:image-20221122100004-3.png]]
1331 1331  
1271 +Please AT+FDR, and then enter the following instructions by the information on the label
1332 1332  
1333 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1273 +AT+DEUI=70B3D57ED0053981
1334 1334  
1275 +AT+APPEUI=D23345667BCBCCAF
1335 1335  
1336 -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.
1277 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1337 1337  
1338 -After AT+FDR. please set
1279 +AT+DADDR=260b4dce
1339 1339  
1340 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1281 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1341 1341  
1342 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1283 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1343 1343  
1344 -**Example:**
1345 1345  
1346 -AT+PDOP=7.00
1347 1347  
1348 -AT+FTIME=180
1287 +==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1349 1349  
1350 -AT+DEUI=70B3D57ED0053981  
1351 1351  
1352 -AT+APPEUI=D23345667BCBCCAF
1290 +[[image:image-20221122100004-4.png]]
1353 1353  
1354 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1355 1355  
1356 -AT+DADDR=260b4dce    ( no need for OTAA)
1357 -
1358 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1359 -
1360 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1361 -
1362 -
1363 1363  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1364 1364  
1365 1365  
... ... @@ -1373,61 +1373,15 @@
1373 1373  
1374 1374  2)  Set PDOP to a higher value.
1375 1375  
1376 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1306 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1377 1377  
1378 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1308 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1379 1379  
1380 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1310 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1381 1381  
1382 1382  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
1383 1383  
1384 1384  
1385 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1386 -
1387 -
1388 -When upgrading, use the erase button to upgrade
1389 -
1390 -[[image:image-20221207120536-4.png]]
1391 -
1392 -
1393 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1394 -
1395 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1396 -
1397 -
1398 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1399 -
1400 -[[image:image-20221207134028-8.png]]
1401 -
1402 -
1403 -Reboot information after upgrade
1404 -
1405 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1406 -
1407 -
1408 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1409 -
1410 -[[image:image-20221128111850-5.png]]
1411 -
1412 -
1413 -After the parameters return to normal, upgrade to the version you need again
1414 -
1415 -[[image:image-20221207120601-5.png]]
1416 -
1417 -
1418 -At this point, the parameters return to normal after running AT+FDR again
1419 -
1420 -[[image:image-20221128112035-7.png]]
1421 -
1422 -
1423 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1424 -
1425 -
1426 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1427 -
1428 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1429 -
1430 -
1431 1431  = 9.  Order Info =
1432 1432  
1433 1433  
... ... @@ -1485,4 +1485,3 @@
1485 1485  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1486 1486  
1487 1487  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1488 -)))
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