Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 188.1
edited by Bei Jinggeng
on 2023/01/06 11:45
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
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.**
... ... @@ -94,6 +94,7 @@
94 94  * Tracking: max: 38mA
95 95  
96 96  
99 +
97 97  == 1.3  Features ==
98 98  
99 99  
... ... @@ -113,6 +113,7 @@
113 113  * Datalog
114 114  
115 115  
119 +
116 116  == 1.4  Applications ==
117 117  
118 118  
... ... @@ -120,6 +120,7 @@
120 120  * Human tracking
121 121  
122 122  
127 +
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"]]
142 +[[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"]]
154 +[[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"]]
163 +[[image:1664501711466-918.png]]
159 159  
160 160  
161 161  
162 -[[image:1664501721248-725.png||_mstalt="294450"]]
167 +[[image:1664501721248-725.png]]
163 163  
164 164  
165 -[[image:1664501734705-405.png||_mstalt="293306"]]
170 +[[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"]]
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"]]
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"]]
183 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
179 179  
180 -[[image:1664502835802-546.png||_mstalt="295061"]]
185 +[[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"]]
217 +[[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)(%%)  
284 +(% 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
... ... @@ -286,6 +286,7 @@
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 288  
294 +
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"]]
313 +[[image:1665301636888-168.png]]
308 308  
309 309  
310 310  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -313,6 +313,8 @@
313 313  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
314 314  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
315 315  
322 +
323 +
316 316  ==== (% style="color:blue" %)**FLAG:**(%%) ====
317 317  
318 318  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -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"]]
345 +[[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"]]
350 +[[image:1664502166010-515.png]]
343 343  
344 344  
345 345  
... ... @@ -362,6 +362,8 @@
362 362  * 3.40v ~~ 3.69v:  20% ~~ 40%
363 363  * < 3.39v:  0~~20%
364 364  
373 +
374 +
365 365  ==== (% style="color:blue" %)**MOD:**(%%) ====
366 366  
367 367  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -417,13 +417,13 @@
417 417  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
418 418  
419 419  (% class="wikigeneratedid" %)
420 -[[image:1665301687277-443.png||_mstalt="296140"]]
430 +[[image:1665301687277-443.png]]
421 421  
422 422  
423 423  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
424 424  
425 425  
426 -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.
427 427  
428 428  
429 429  (% style="color:red" %)**Note for this mode:**
... ... @@ -440,7 +440,7 @@
440 440  )))|4|4|2|1|1|1|1|1
441 441  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
442 442  
443 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
453 +[[image:image-20221009160309-2.png]]
444 444  
445 445  
446 446  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -467,7 +467,7 @@
467 467  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
468 468  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
469 469  
470 -[[image:1664502425687-834.png||_mstalt="296738"]]
480 +[[image:1664502425687-834.png]]
471 471  
472 472  
473 473  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -479,6 +479,7 @@
479 479  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
480 480  
481 481  
492 +
482 482  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
483 483  
484 484  
... ... @@ -494,7 +494,7 @@
494 494  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
495 495  
496 496  (% class="wikigeneratedid" %)
497 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
508 +[[image:1667288597595-714.png||height="212" width="1151"]]
498 498  
499 499  
500 500  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -502,6 +502,7 @@
502 502  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
503 503  
504 504  
516 +
505 505  === 2.4.7  Add Payload format in TTN V3 ===
506 506  
507 507  
... ... @@ -510,7 +510,7 @@
510 510  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
511 511  
512 512  
513 -[[image:1664502649601-895.png||_mstalt="296985"]]
525 +[[image:1664502649601-895.png]]
514 514  
515 515  
516 516  
... ... @@ -520,7 +520,7 @@
520 520  
521 521  Save the change the uplink message will be parsed. As below:
522 522  
523 -[[image:1664502676891-606.png||_mstalt="296673"]]
535 +[[image:1664502676891-606.png]]
524 524  
525 525  
526 526  == 2.5 Integrate with Datacake ==
... ... @@ -531,7 +531,7 @@
531 531  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]]
532 532  
533 533  
534 -[[image:1664502695771-538.png||_mstalt="297349"]]
546 +[[image:1664502695771-538.png]]
535 535  
536 536  
537 537  == 2.6 Integrate with Tago ==
... ... @@ -542,7 +542,7 @@
542 542  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]]
543 543  
544 544  
545 -[[image:1664502715371-321.png||_mstalt="292162"]]
557 +[[image:1664502715371-321.png]]
546 546  
547 547  
548 548  == 2.7  Datalog Feature ==
... ... @@ -550,14 +550,14 @@
550 550  
551 551  total 273 entries,by default,
552 552  
553 -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.
554 554  
555 555  Example use case.
556 556  
557 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
569 +[[image:image-20221009234703-2.png||height="328" width="899"]]
558 558  
559 559  
560 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
572 +[[image:image-20221009234629-1.png||height="390" width="577"]]
561 561  
562 562  
563 563  == 2.8 Alarm Mode ==
... ... @@ -590,11 +590,7 @@
590 590  
591 591  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.
592 592  
593 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
594 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
595 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
596 596  
597 -
598 598  == 2.10 LED Status ==
599 599  
600 600  
... ... @@ -613,12 +613,13 @@
613 613  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
614 614  
615 615  
624 +
616 616  == 2.11 Button Function ==
617 617  
618 618  
619 619  (% style="color:blue" %)**RESET button:**
620 620  
621 -[[image:1664502835802-546.png||_mstalt="295061"]]
630 +[[image:1664502835802-546.png]]
622 622  
623 623  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
624 624  
... ... @@ -625,7 +625,7 @@
625 625  
626 626  (% style="color:red" %)**RED button:**
627 627  
628 -[[image:1664502854406-763.png||_mstalt="295568"]]
637 +[[image:1664502854406-763.png]]
629 629  
630 630  
631 631  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -635,6 +635,7 @@
635 635  |(% 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.
636 636  
637 637  
647 +
638 638  == 2.12 USB Port Function ==
639 639  
640 640  
... ... @@ -646,6 +646,7 @@
646 646  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
647 647  
648 648  
659 +
649 649  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
650 650  
651 651  
... ... @@ -660,21 +660,22 @@
660 660  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.
661 661  
662 662  
663 -[[image:1664502999401-486.png||_mstalt="296985"]]
674 +[[image:1664502999401-486.png]]
664 664  
665 665  
666 666  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:
667 667  
668 668  
669 -[[image:1664503022490-662.png||_mstalt="293332"]]
680 +[[image:1664503022490-662.png]]
670 670  
671 671  
672 -[[image:1664503035713-500.png||_mstalt="291096"]]
683 +[[image:1664503035713-500.png]]
673 673  
674 674  
675 -[[image:1664503047675-651.png||_mstalt="295386"]]
686 +[[image:1664503047675-651.png]]
676 676  
677 677  
689 +
678 678  == 3.2 Command Set ==
679 679  
680 680  === 3.2.1 Set Transmit Interval ===
... ... @@ -740,7 +740,7 @@
740 740  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
741 741  
742 742  
743 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
755 +=== 3.2.5 Disable/Enable LED flash ===
744 744  
745 745  
746 746  Disable/Enable LED for position, downlink and uplink
... ... @@ -800,9 +800,9 @@
800 800  
801 801  (% style="color:#037691" %)**cc:   **
802 802  
803 -* (% _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  
804 804  
805 -* (% _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(%%))  
806 806  
807 807  (% style="color:blue" %)**Example:**
808 808  
... ... @@ -864,8 +864,8 @@
864 864  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
865 865  
866 866  
867 -=== 3.2.10 Disable/Enable the confirmation mode ===
868 868  
880 +**Disable/Enable the confirmation mode**
869 869  
870 870  * (% style="color:blue" %)**AT Command:**
871 871  
... ... @@ -884,7 +884,7 @@
884 884  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
885 885  
886 886  
887 -=== 3.2.11  Auto Send None-ACK messages ===
899 +=== 3.2.10  Auto Send None-ACK messages ===
888 888  
889 889  
890 890  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.
... ... @@ -902,10 +902,10 @@
902 902  
903 903  * (% style="color:blue" %)**Downlink Command: 0x34**
904 904  
905 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
906 906  
907 907  
908 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
920 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
909 909  
910 910  
911 911  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.
... ... @@ -914,16 +914,16 @@
914 914  
915 915  (% style="color:blue" %)**AT Command:**
916 916  
917 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
918 918  
919 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
920 920  
921 921  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
922 922  
923 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
935 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
924 924  
925 925  
926 -=== 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） ===
927 927  
928 928  
929 929  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.
... ... @@ -932,16 +932,16 @@
932 932  
933 933  (% style="color:blue" %)**AT Command:**
934 934  
935 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
936 936  
937 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
938 938  
939 939  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
940 940  
941 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
953 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
942 942  
943 943  
944 -=== 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） ===
945 945  
946 946  
947 947  Users can use this feature to enable/disable Information printing.
... ... @@ -948,11 +948,11 @@
948 948  
949 949  (% style="color:blue" %)**AT Command:**
950 950  
951 -(% 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)
952 952  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
953 953  
954 954  
955 -=== 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） ===
956 956  
957 957  
958 958  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -959,34 +959,14 @@
959 959  
960 960  (% style="color:blue" %)**AT Command:**
961 961  
962 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
974 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
963 963  
964 964  
965 965  (% style="color:blue" %)**Downlink Payload:0X24**
966 966  
967 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
979 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
968 968  
969 969  
970 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
971 -
972 -
973 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
974 -
975 -(% style="color:blue" %)**AT Command:**
976 -
977 -(% style="color:#037691" %)**AT+PT=xx**
978 -
979 - Example:
980 -
981 - AT+PT=14    ~-~->    Set to detect car motion.
982 -
983 - AT+PT=41  ~-~->    set to detect walk motion.
984 -
985 -
986 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
987 -0xB4 14          ~/~/  Same as AT+PT=14
988 -
989 -
990 990  = 4. Setting for Different Scenarios =
991 991  
992 992  
... ... @@ -1019,10 +1019,10 @@
1019 1019  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1020 1020  
1021 1021  
1022 -[[image:1664503563660-578.png||_mstalt="296777"]]
1014 +[[image:1664503563660-578.png]]
1023 1023  
1024 1024  
1025 -[[image:1664503574618-659.png||_mstalt="297986"]]
1017 +[[image:1664503574618-659.png]]
1026 1026  
1027 1027  
1028 1028  
... ... @@ -1038,15 +1038,16 @@
1038 1038  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1039 1039  
1040 1040  
1041 -[[image:image-20221207120501-1.png]]
1033 +[[image:image-20221118105220-2.png]]
1042 1042  
1043 1043  
1044 1044  
1045 1045  After upgrade finish, it will show finish as below:
1046 1046  
1047 -[[image:image-20221207133911-7.png]]
1039 +[[image:image-20221118105402-4.png]]
1048 1048  
1049 1049  
1042 +
1050 1050  = 6. Developer Guide =
1051 1051  
1052 1052  == 6.1 Compile Source Code ==
... ... @@ -1059,80 +1059,24 @@
1059 1059  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]]
1060 1060  
1061 1061  
1062 -[[image:1664503635019-941.png||_mstalt="294658"]]
1055 +[[image:1664503635019-941.png]]
1063 1063  
1064 1064  
1065 1065  
1066 1066  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1067 1067  
1068 -[[image:1664503715811-892.png||_mstalt="295698"]]
1061 +[[image:1664503715811-892.png]]
1069 1069  
1070 1070  
1071 -=== 6.1.2  Build the development environment ===
1072 -
1073 -
1074 -**~1. Download and install arduino IDE**
1075 -
1076 -[[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]]
1077 -
1078 -
1079 -**2. Download the ESP32 development package in the arduino IDE**
1080 -
1081 -[[image:image-20221213100007-1.png]]
1082 -
1083 -
1084 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1085 -
1086 -[[image:image-20221213100626-2.png]]
1087 -
1088 -
1089 -Restart the IDE after the addition is complete, then:
1090 -
1091 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1092 -
1093 -
1094 -[[image:image-20221213101040-4.png]]
1095 -
1096 -
1097 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1098 -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)**
1099 -
1100 -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:
1101 -
1102 -(% style="color:blue" %)**Methods as below:**
1103 -
1104 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1105 -
1106 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1107 -
1108 1108  (% 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.
1109 1109  
1110 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1066 +[[image:image-20221024105643-1.png]]
1111 1111  
1112 -
1113 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1114 -
1115 -[[image:image-20221213102334-6.png]]
1116 -
1117 -(% style="color:red" %)**Note: This step requires a python environment**
1118 -
1119 -
1120 -Either way, in the end:
1121 -
1122 -The final effect is to open the arduino and you can see the esp32
1123 -
1124 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1125 -
1126 -
1127 -
1128 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1129 -
1130 1130  **~ Figure1**
1131 1131  
1132 1132  
1071 +[[image:image-20221024105643-2.png]]
1133 1133  
1134 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1135 -
1136 1136   **Figure2**
1137 1137  
1138 1138  
... ... @@ -1141,7 +1141,7 @@
1141 1141  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1142 1142  
1143 1143  
1144 -[[image:1664503752288-974.png||_mstalt="298194"]]
1081 +[[image:1664503752288-974.png]]
1145 1145  
1146 1146  
1147 1147  == 6.2 Source Code ==
... ... @@ -1149,19 +1149,19 @@
1149 1149  
1150 1150  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1151 1151  
1152 -[[image:1664503794261-827.png||_mstalt="296387"]]
1089 +[[image:1664503794261-827.png]]
1153 1153  
1154 1154  
1155 1155  
1156 1156  * (% style="color:blue" %)**Click to upload**
1157 1157  
1158 -[[image:1664503808294-336.png||_mstalt="295711"]]
1095 +[[image:1664503808294-336.png]]
1159 1159  
1160 1160  
1161 1161  
1162 1162  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1163 1163  
1164 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1101 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1165 1165  
1166 1166  
1167 1167  = 7.  FAQ =
... ... @@ -1175,7 +1175,7 @@
1175 1175  == 7.2 What is the pin mapping for the USB program cable? ==
1176 1176  
1177 1177  
1178 -[[image:1664499635206-262.png||_mstalt="295360"]]
1115 +[[image:1664499635206-262.png]]
1179 1179  
1180 1180  
1181 1181  
... ... @@ -1191,6 +1191,7 @@
1191 1191  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1192 1192  
1193 1193  
1131 +
1194 1194  == 7.3 Notes on using different serial port tools for TrackerD ==
1195 1195  
1196 1196  === 7.3.1  Serial port utility ===
... ... @@ -1201,13 +1201,13 @@
1201 1201  Need to adjust the data stream to RTS/CTS on physical restart.
1202 1202  
1203 1203  (% class="wikigeneratedid" %)
1204 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1142 +[[image:image-20221102140621-1.png]]
1205 1205  
1206 1206  
1207 1207  
1208 1208  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1209 1209  
1210 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1148 +[[image:image-20221102140638-2.png]]
1211 1211  
1212 1212  
1213 1213  === 7.3.2  SecureCRT ===
... ... @@ -1216,22 +1216,22 @@
1216 1216  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.
1217 1217  
1218 1218  
1219 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1157 +[[image:image-20221102140704-3.png]]
1220 1220  
1221 1221  
1222 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1160 +[[image:image-20221102140712-4.png]]
1223 1223  
1224 1224  
1225 1225  === 7.3.3  PUTTY ===
1226 1226  
1227 1227  
1228 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1166 +[[image:image-20221102140748-5.png]]
1229 1229  
1230 1230  
1231 1231  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.
1232 1232  
1233 1233  
1234 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1172 +[[image:image-20221102140801-6.png]]
1235 1235  
1236 1236  
1237 1237  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1246,7 +1246,7 @@
1246 1246  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1247 1247  
1248 1248  
1249 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1187 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1250 1250  
1251 1251  
1252 1252  
... ... @@ -1253,7 +1253,7 @@
1253 1253  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1254 1254  
1255 1255  
1256 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1194 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1257 1257  
1258 1258  
1259 1259  
... ... @@ -1260,7 +1260,7 @@
1260 1260  **3. Compile the AS923_JP band, please refer to the intention shown**
1261 1261  
1262 1262  
1263 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1201 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1264 1264  
1265 1265  
1266 1266  
... ... @@ -1267,18 +1267,12 @@
1267 1267  **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.**
1268 1268  
1269 1269  
1270 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1208 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1271 1271  
1272 1272  
1273 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1211 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1274 1274  
1275 1275  
1276 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1277 -
1278 -
1279 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1280 -
1281 -
1282 1282  = 8  Trouble Shooting =
1283 1283  
1284 1284  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1285,7 +1285,7 @@
1285 1285  
1286 1286  
1287 1287  (((
1288 -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
1289 1289  )))
1290 1290  
1291 1291  
... ... @@ -1299,82 +1299,65 @@
1299 1299  
1300 1300  == 8.3  Problem after Upgrading Firmware ==
1301 1301  
1302 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1234 +=== 8.3.1 Continue Restart after upgrading ===
1303 1303  
1304 1304  
1305 -**Error Output**
1306 -
1307 -
1308 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1309 -
1310 -
1311 1311  (((
1312 -Some partition is missed during upgrade, please upgrade below four files as example:
1313 -
1314 -[[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
1315 1315  )))
1316 1316  
1317 1317  
1318 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1242 +[[image:image-20221118105249-3.png]]
1319 1319  
1320 1320  
1321 -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 ===
1322 1322  
1323 1323  
1324 -=== 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
1325 1325  
1326 1326  
1327 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1328 1328  
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 ====
1329 1329  
1330 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1331 1331  
1255 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1332 1332  
1333 -User need to upgrade again with below four files to solve this issue.
1257 + ** Figure 1  **
1334 1334  
1335 - [[image:image-20221207120530-3.png]]
1336 1336  
1260 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1261 +
1337 1337   **Figure 2**
1338 1338  
1339 1339  
1340 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1341 1341  
1266 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1342 1342  
1343 -User might erase the entire flash include keys and default settings which cause this issue.
1344 1344  
1345 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1269 +[[image:image-20221122100004-3.png]]
1346 1346  
1271 +Please AT+FDR, and then enter the following instructions by the information on the label
1347 1347  
1348 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1273 +AT+DEUI=70B3D57ED0053981
1349 1349  
1275 +AT+APPEUI=D23345667BCBCCAF
1350 1350  
1351 -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
1352 1352  
1353 -After AT+FDR. please set
1279 +AT+DADDR=260b4dce
1354 1354  
1355 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1281 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1356 1356  
1357 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1283 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1358 1358  
1359 -**Example:**
1360 1360  
1361 -AT+PDOP=7.00
1362 1362  
1363 -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 ====
1364 1364  
1365 -AT+DEUI=70B3D57ED0053981  
1366 1366  
1367 -AT+APPEUI=D23345667BCBCCAF
1290 +[[image:image-20221122100004-4.png]]
1368 1368  
1369 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1370 1370  
1371 -AT+DADDR=260b4dce    ( no need for OTAA)
1372 -
1373 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1374 -
1375 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1376 -
1377 -
1378 1378  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1379 1379  
1380 1380  
... ... @@ -1388,61 +1388,15 @@
1388 1388  
1389 1389  2)  Set PDOP to a higher value.
1390 1390  
1391 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1306 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1392 1392  
1393 -* (% _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）
1394 1394  
1395 -* (% _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）
1396 1396  
1397 1397  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
1398 1398  
1399 1399  
1400 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1401 -
1402 -
1403 -When upgrading, use the erase button to upgrade
1404 -
1405 -[[image:image-20221207120536-4.png]]
1406 -
1407 -
1408 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1409 -
1410 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1411 -
1412 -
1413 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1414 -
1415 -[[image:image-20221207134028-8.png]]
1416 -
1417 -
1418 -Reboot information after upgrade
1419 -
1420 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1421 -
1422 -
1423 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1424 -
1425 -[[image:image-20221128111850-5.png]]
1426 -
1427 -
1428 -After the parameters return to normal, upgrade to the version you need again
1429 -
1430 -[[image:image-20221207120601-5.png]]
1431 -
1432 -
1433 -At this point, the parameters return to normal after running AT+FDR again
1434 -
1435 -[[image:image-20221128112035-7.png]]
1436 -
1437 -
1438 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1439 -
1440 -
1441 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1442 -
1443 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1444 -
1445 -
1446 1446  = 9.  Order Info =
1447 1447  
1448 1448  
... ... @@ -1465,6 +1465,7 @@
1465 1465  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1466 1466  
1467 1467  
1337 +
1468 1468  = 10.  Packing Info =
1469 1469  
1470 1470  
... ... @@ -1481,6 +1481,7 @@
1481 1481  * Weight: 50g
1482 1482  
1483 1483  
1354 +
1484 1484  = 11. Support =
1485 1485  
1486 1486  
... ... @@ -1489,6 +1489,7 @@
1489 1489  * 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]].
1490 1490  
1491 1491  
1363 +
1492 1492  = 12.  Reference =
1493 1493  
1494 1494  
... ... @@ -1497,4 +1497,3 @@
1497 1497  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1498 1498  
1499 1499  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1500 -)))
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