Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 205.2
edited by Xiaoling
on 2023/04/13 10:42
Change comment: There is no comment for this version
To version 138.1
edited by Bei Jinggeng
on 2022/11/22 10:00
Change comment: Uploaded new attachment "image-20221122100004-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -12,9 +12,9 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
17 +
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -32,17 +32,21 @@
32 32  (((
33 33  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 34  )))
35 +)))
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.
39 +
40 +
38 38  )))
39 39  
40 -[[image:image-20230213110119-1.png||height="382" width="834"]]
43 +[[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.**
44 44  
45 45  
49 +
46 46  == 1.2 Specifications ==
47 47  
48 48  
... ... @@ -93,8 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -(% style="display:none" %)
97 -
98 98  == 1.3  Features ==
99 99  
100 100  
... ... @@ -113,8 +113,6 @@
113 113  * Tri-color LED, Alarm button
114 114  * Datalog
115 115  
116 -(% style="display:none" %)
117 -
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,10 +121,9 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -(% style="display:none" %)
125 -
126 126  = 2.  Use TrackerD =
127 127  
126 +
128 128  == 2.1 How it works? ==
129 129  
130 130  
... ... @@ -131,6 +131,7 @@
131 131  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
132 132  
133 133  
133 +
134 134  == 2.2 Quick guide to connect to LoRaWAN server ==
135 135  
136 136  
... ... @@ -137,7 +137,7 @@
137 137  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
138 138  
139 139  
140 -[[image:image-20230213110214-2.png||height="388" width="847"]]
140 +[[image:1664501652064-326.png]]
141 141  
142 142  
143 143  
... ... @@ -149,7 +149,7 @@
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
151 151  
152 -[[image:1664501677253-891.png||_mstalt="296569"]]
152 +[[image:1664501677253-891.png]]
153 153  
154 154  
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -158,14 +158,14 @@
158 158  **__Add APP EUI in the application:__**
159 159  
160 160  
161 -[[image:1664501711466-918.png||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
166 166  
167 167  
168 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
169 169  
170 170  
171 171  
... ... @@ -172,20 +172,21 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
175 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
176 176  
177 177  
178 178  
179 179  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180 180  
181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
181 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
182 182  
183 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
184 184  
185 185  
186 186  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
187 187  
188 188  
189 +
189 189  == 2.3  Positioning Mode(SMOD) ==
190 190  
191 191  
... ... @@ -198,8 +198,10 @@
198 198  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
199 199  
200 200  
202 +
201 201  == 2.4  Uplink Payload ==
202 202  
205 +
203 203  === 2.4.1 Uplink FPORT~=5, Device Status ===
204 204  
205 205  
... ... @@ -209,10 +209,10 @@
209 209  
210 210  
211 211  (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
212 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)1|=(% style="width: 40px;" %)1
215 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
213 213  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
214 214  
215 -[[image:1665301570342-765.png||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
216 216  
217 217  
218 218  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -256,7 +256,7 @@
256 256  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
257 257  
258 258  (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
259 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
262 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
260 260  |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
261 261  
262 262  (% style="color:blue" %)** SMOD：**
... ... @@ -279,16 +279,15 @@
279 279  
280 280  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 281  
282 -(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
283 283  
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
286 286  
287 -(% border="1.5" style="background-color:#ffffcc; color:green; width:412.222px" %)
288 -|=(% scope="row" style="width: 75px;" %)**Size(bit)**|(% style="width:68px" %)5 Bits|(% style="width:87px" %)1 Bit|(% style="width:49px" %)1 Bit|(% style="width:126px" %)1 Bit
289 -|=(% style="width: 75px;" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
290 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
291 +|=(% 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
292 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
290 290  
291 -
292 292  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
293 293  
294 294  
... ... @@ -307,20 +307,20 @@
307 307  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
308 308  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
309 309  
310 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
311 311  
312 312  
313 313  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
314 314  
315 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:279.222px" %)
316 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:69px" %)1 bit|(% style="width:63px" %)14 bits
317 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
317 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
318 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
319 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
318 318  
319 319  ==== (% style="color:blue" %)**FLAG:**(%%) ====
320 320  
321 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:183.222px" %)
322 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 bits|(% style="width:52px" %)1 bit
323 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:52px" %)[[LON>>||anchor="HLON:"]]
323 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
324 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
325 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
324 324  
325 325  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
326 326  
... ... @@ -337,12 +337,12 @@
337 337  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:
338 338  
339 339  
340 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
341 341  
342 342  
343 343  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
344 344  
345 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
346 346  
347 347  
348 348  
... ... @@ -365,9 +365,6 @@
365 365  * 3.40v ~~ 3.69v:  20% ~~ 40%
366 366  * < 3.39v:  0~~20%
367 367  
368 -(% style="display:none" %) (%%)
369 -
370 -
371 371  ==== (% style="color:blue" %)**MOD:**(%%) ====
372 372  
373 373  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -408,6 +408,7 @@
408 408  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
409 409  
410 410  
410 +
411 411  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
412 412  
413 413  
... ... @@ -423,13 +423,14 @@
423 423  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
424 424  
425 425  (% class="wikigeneratedid" %)
426 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
427 427  
428 428  
429 +
429 429  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
430 430  
431 431  
432 -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.
433 +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.
433 433  
434 434  
435 435  (% style="color:red" %)**Note for this mode:**
... ... @@ -446,9 +446,10 @@
446 446  )))|4|4|2|1|1|1|1|1
447 447  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
448 448  
449 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
450 450  
451 451  
453 +
452 452  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
453 453  
454 454  
... ... @@ -473,7 +473,7 @@
473 473  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
474 474  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
475 475  
476 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
477 477  
478 478  
479 479  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -484,32 +484,9 @@
484 484  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
485 485  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
486 486  
487 -(% style="display:none" %) (%%)
489 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
488 488  
489 489  
490 -=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
491 -
492 -
493 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
494 -
495 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
496 -|**Size(bytes)**|2|1
497 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon
498 -
499 - [[image:image-20230302145315-1.png]]
500 -
501 -**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
502 -
503 -**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
504 -
505 -**mod** = bytes[2] & 0xC0;
506 -
507 -**Lon**=(bytes[2] & 0x20)
508 -
509 -
510 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
511 -
512 -
513 513  TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
514 514  
515 515  
... ... @@ -522,7 +522,7 @@
522 522  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
523 523  
524 524  (% class="wikigeneratedid" %)
525 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
526 526  
527 527  
528 528  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -529,21 +529,17 @@
529 529  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
530 530  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
531 531  
532 -(% style="display:none" %) (%%)
511 +=== 2.4.7  Add Payload format in TTN V3 ===
533 533  
534 534  
535 -=== 2.4.8  Add Payload format in TTN V3 ===
536 -
537 -
538 538  In TTN V3, user can add a custom payload so it shows friendly.
539 539  
540 540  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
541 541  
542 542  
543 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
544 544  
545 545  
546 -
547 547  Add the decoder from this link: 
548 548  
549 549  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -550,9 +550,10 @@
550 550  
551 551  Save the change the uplink message will be parsed. As below:
552 552  
553 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
554 554  
555 555  
531 +
556 556  == 2.5 Integrate with Datacake ==
557 557  
558 558  
... ... @@ -561,9 +561,10 @@
561 561  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]]
562 562  
563 563  
564 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
565 565  
566 566  
543 +
567 567  == 2.6 Integrate with Tago ==
568 568  
569 569  
... ... @@ -572,70 +572,31 @@
572 572  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]]
573 573  
574 574  
575 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
576 576  
577 577  
578 -== 2.7  Integrate with Node-red ==
579 579  
556 +== 2.7  Datalog Feature ==
580 580  
581 -~1. Install node-red, please refer to the installation method in the link:
582 582  
583 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
584 -
585 -
586 -2. Import the created flow template, please refer to the import method in the link:
587 -
588 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
589 - The address of the flow template:
590 -
591 - [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]
592 -
593 -(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**
594 -
595 -[[image:image-20230307135914-1.png||height="527" width="1045"]]
596 -
597 -
598 -[[image:image-20230307135932-2.png||height="527" width="1044"]]
599 -
600 -
601 -3. Display the map
602 - Enter the link to the map:
603 -
604 - Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
605 -
606 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
607 -
608 -
609 - Hit all input in input stream
610 -
611 - [[image:image-20230308115616-2.png||height="563" width="1070"]]
612 -
613 -
614 - View map again
615 -
616 -[[image:image-20230308115701-3.png||height="571" width="1085"]]
617 -
618 -
619 -== 2.8  Datalog Feature ==
620 -
621 -
622 622  total 273 entries,by default,
623 623  
624 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
625 625  
626 626  Example use case.
627 627  
628 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
629 629  
630 630  
631 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
632 632  
633 633  
634 -== 2.9  Alarm Mode ==
635 635  
572 +== 2.8 Alarm Mode ==
636 636  
574 +
637 637  (((
638 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
576 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
639 639  )))
640 640  
641 641  
... ... @@ -645,7 +645,7 @@
645 645  
646 646  
647 647  (((
648 -**Two ways to exit alarm mode:**
586 +Two ways to exit alarm mode:
649 649  )))
650 650  
651 651  * Server sends a downlink command to exit.
... ... @@ -656,23 +656,17 @@
656 656  )))
657 657  
658 658  
659 -== 2.10  Transport Mode ==
660 660  
598 +== 2.9 Transport Mode ==
661 661  
662 -In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
663 663  
664 -When device is set in Transport Mode, it will uplink more frequenctly during moving.
601 +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.
665 665  
666 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
667 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
668 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
669 669  
670 -(% style="display:none" %) (%%)
671 671  
605 +== 2.10 LED Status ==
672 672  
673 -== 2.11  LED Status ==
674 674  
675 -
676 676  (% border="1.5" style="background-color:#ffffcc; width:500px" %)
677 677  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
678 678  |(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A
... ... @@ -687,15 +687,12 @@
687 687  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
688 688  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
689 689  
690 -(% style="display:none" %) (%%)
622 +== 2.11 Button Function ==
691 691  
692 692  
693 -== 2.12  Button Function ==
694 -
695 -
696 696  (% style="color:blue" %)**RESET button:**
697 697  
698 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
699 699  
700 700  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
701 701  
... ... @@ -702,9 +702,8 @@
702 702  
703 703  (% style="color:red" %)**RED button:**
704 704  
705 -[[image:image-20230213110506-3.png]](% style="display:none" %)
634 +[[image:1664502854406-763.png]]
706 706  
707 -(% style="display:none" %) (%%)
708 708  
709 709  (% border="1" style="background-color:#ffffcc; width:510px" %)
710 710  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
... ... @@ -712,12 +712,9 @@
712 712  |(% 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
713 713  |(% 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.
714 714  
715 -(% style="display:none" %) (%%)
643 +== 2.12 USB Port Function ==
716 716  
717 717  
718 -== 2.13  USB Port Function ==
719 -
720 -
721 721  The USB interface of TrackerD has below functions:
722 722  
723 723  * Power on the device
... ... @@ -725,19 +725,6 @@
725 725  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
726 726  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
727 727  
728 -(% style="display:none" %) (%%)
729 -
730 -
731 -== 2.14  Sleep Mode ==
732 -
733 -
734 -(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
735 -
736 -In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
737 -
738 -Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
739 -
740 -
741 741  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
742 742  
743 743  
... ... @@ -746,6 +746,7 @@
746 746  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
747 747  
748 748  
661 +
749 749  == 3.1 Access AT Command ==
750 750  
751 751  
... ... @@ -752,24 +752,25 @@
752 752  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.
753 753  
754 754  
755 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
756 756  
757 757  
758 758  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:
759 759  
760 760  
761 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
762 762  
763 763  
764 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
765 765  
766 766  
767 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
768 768  
769 -(% style="display:none" %) (%%)
770 770  
683 +
771 771  == 3.2 Command Set ==
772 772  
686 +
773 773  === 3.2.1 Set Transmit Interval ===
774 774  
775 775  
... ... @@ -787,6 +787,7 @@
787 787  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
788 788  
789 789  
704 +
790 790  === 3.2.2 Set Alarm Packet transmission interval ===
791 791  
792 792  
... ... @@ -804,6 +804,7 @@
804 804  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
805 805  
806 806  
722 +
807 807  === 3.2.3 Set Transport Mode Packet transmission interval ===
808 808  
809 809  
... ... @@ -821,6 +821,7 @@
821 821  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
822 822  
823 823  
740 +
824 824  === 3.2.4 Exit Alarm ===
825 825  
826 826  
... ... @@ -833,9 +833,10 @@
833 833  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
834 834  
835 835  
836 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
837 837  
754 +=== 3.2.5 Disable/Enable LED flash ===
838 838  
756 +
839 839  Disable/Enable LED for position, downlink and uplink
840 840  
841 841  * (% style="color:blue" %)**AT Command:**
... ... @@ -850,6 +850,7 @@
850 850  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
851 851  
852 852  
771 +
853 853  === 3.2.6 Disable/Enable Transport Mode ===
854 854  
855 855  
... ... @@ -867,6 +867,7 @@
867 867  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
868 868  
869 869  
789 +
870 870  === 3.2.7 Set Positioning Mode ===
871 871  
872 872  
... ... @@ -893,9 +893,9 @@
893 893  
894 894  (% style="color:#037691" %)**cc:   **
895 895  
896 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
816 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
897 897  
898 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
818 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
899 899  
900 900  (% style="color:blue" %)**Example:**
901 901  
... ... @@ -913,6 +913,7 @@
913 913  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
914 914  
915 915  
836 +
916 916  === 3.2.8 Set MAX GPS position time ===
917 917  
918 918  
... ... @@ -919,7 +919,7 @@
919 919  Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.
920 920  
921 921  
922 -If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
843 +If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
923 923  
924 924  
925 925  * (% style="color:blue" %)**AT Command:**
... ... @@ -934,6 +934,7 @@
934 934  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
935 935  
936 936  
858 +
937 937  === 3.2.9 Set PDOP value for GPS fix accuracy ===
938 938  
939 939  
... ... @@ -957,8 +957,8 @@
957 957  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
958 958  
959 959  
960 -=== 3.2.10 Disable/Enable the confirmation mode ===
961 961  
883 +Disable/Enable the confirmation mode
962 962  
963 963  * (% style="color:blue" %)**AT Command:**
964 964  
... ... @@ -977,9 +977,10 @@
977 977  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
978 978  
979 979  
980 -=== 3.2.11  Auto Send None-ACK messages ===
981 981  
903 +=== 3.2.10  Auto Send None-ACK messages ===
982 982  
905 +
983 983  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.
984 984  
985 985  
... ... @@ -995,12 +995,13 @@
995 995  
996 996  * (% style="color:blue" %)**Downlink Command: 0x34**
997 997  
998 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
999 999  
1000 1000  
1001 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
1002 1002  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
1003 1003  
927 +
1004 1004  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.
1005 1005  
1006 1006  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -1007,18 +1007,19 @@
1007 1007  
1008 1008  (% style="color:blue" %)**AT Command:**
1009 1009  
1010 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1011 1011  
1012 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1013 1013  
1014 1014  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1015 1015  
1016 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1017 1017  
1018 1018  
1019 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1020 1020  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1021 1021  
946 +
1022 1022  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.
1023 1023  
1024 1024  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -1025,61 +1025,44 @@
1025 1025  
1026 1026  (% style="color:blue" %)**AT Command:**
1027 1027  
1028 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1029 1029  
1030 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1031 1031  
1032 1032  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1033 1033  
1034 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1035 1035  
1036 1036  
1037 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
1038 1038  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1039 1039  
965 +
1040 1040  Users can use this feature to enable/disable Information printing.
1041 1041  
1042 1042  (% style="color:blue" %)**AT Command:**
1043 1043  
1044 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
970 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1045 1045  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1046 1046  
1047 1047  
1048 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1049 1049  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1050 1050  
977 +
1051 1051  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
1052 1052  
1053 1053  (% style="color:blue" %)**AT Command:**
1054 1054  
1055 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
982 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1056 1056  
1057 1057  
1058 1058  (% style="color:blue" %)**Downlink Payload:0X24**
1059 1059  
1060 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
987 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1061 1061  
1062 1062  
1063 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1064 1064  
1065 -
1066 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1067 -
1068 -(% style="color:blue" %)**AT Command:**
1069 -
1070 -(% style="color:#037691" %)**AT+PT=xx**
1071 -
1072 - Example:
1073 -
1074 - AT+PT=14    ~-~->    Set to detect car motion.
1075 -
1076 - AT+PT=41  ~-~->    set to detect walk motion.
1077 -
1078 -
1079 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1080 -0xB4 14          ~/~/  Same as AT+PT=14
1081 -
1082 -
1083 1083  = 4. Setting for Different Scenarios =
1084 1084  
1085 1085  
... ... @@ -1086,6 +1086,7 @@
1086 1086  
1087 1087  = 5. Upload Firmware =
1088 1088  
997 +
1089 1089  == 5.1 Firmware Change Log ==
1090 1090  
1091 1091  
... ... @@ -1092,6 +1092,7 @@
1092 1092  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1093 1093  
1094 1094  
1004 +
1095 1095  == 5.2 How to upgrade firmware ==
1096 1096  
1097 1097  
... ... @@ -1112,10 +1112,10 @@
1112 1112  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1113 1113  
1114 1114  
1115 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1116 1116  
1117 1117  
1118 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1119 1119  
1120 1120  
1121 1121  
... ... @@ -1124,7 +1124,7 @@
1124 1124  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1125 1125  
1126 1126  
1127 -**Users need to use below files:**
1037 +Users need to use below files:
1128 1128  
1129 1129  boot_app0.bin @0e000
1130 1130  
... ... @@ -1131,19 +1131,22 @@
1131 1131  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1132 1132  
1133 1133  
1134 -[[image:image-20221207120501-1.png]]
1044 +[[image:image-20221118105220-2.png]]
1135 1135  
1136 1136  
1137 1137  
1138 1138  After upgrade finish, it will show finish as below:
1139 1139  
1140 -[[image:image-20221207133911-7.png]]
1050 +[[image:image-20221118105402-4.png]]
1141 1141  
1142 1142  
1053 +
1143 1143  = 6. Developer Guide =
1144 1144  
1056 +
1145 1145  == 6.1 Compile Source Code ==
1146 1146  
1059 +
1147 1147  === 6.1.1 Set up ARDUINO compile environment ===
1148 1148  
1149 1149  
... ... @@ -1152,81 +1152,24 @@
1152 1152  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]]
1153 1153  
1154 1154  
1155 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1156 1156  
1157 1157  
1158 1158  
1159 1159  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1160 1160  
1161 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1162 1162  
1163 1163  
1164 -=== 6.1.2  Build the development environment ===
1165 -
1166 -
1167 -**~1. Download and install arduino IDE**
1168 -
1169 -[[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]]
1170 -
1171 -
1172 -**2. Download the ESP32 development package in the arduino IDE**
1173 -
1174 -[[image:image-20221213100007-1.png]]
1175 -
1176 -
1177 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1178 -
1179 -[[image:image-20221213100626-2.png]]
1180 -
1181 -
1182 -Restart the IDE after the addition is complete, then:
1183 -
1184 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1185 -
1186 -
1187 -[[image:image-20221213101040-4.png]]
1188 -
1189 -
1190 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1191 -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)**
1192 -
1193 -
1194 -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:
1195 -
1196 -(% style="color:blue" %)**Methods as below:**
1197 -
1198 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1199 -
1200 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1201 -
1202 1202  (% 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.
1203 1203  
1204 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1079 +[[image:image-20221024105643-1.png]]
1205 1205  
1206 -
1207 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1208 -
1209 -[[image:image-20221213102334-6.png]]
1210 -
1211 -(% style="color:red" %)**Note: This step requires a python environment**
1212 -
1213 -
1214 -Either way, in the end:
1215 -
1216 -The final effect is to open the arduino and you can see the esp32
1217 -
1218 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1219 -
1220 -
1221 -
1222 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1223 -
1224 1224  **~ Figure1**
1225 1225  
1226 1226  
1084 +[[image:image-20221024105643-2.png]]
1227 1227  
1228 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1229 -
1230 1230   **Figure2**
1231 1231  
1232 1232  
... ... @@ -1235,31 +1235,34 @@
1235 1235  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1236 1236  
1237 1237  
1238 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1239 1239  
1240 1240  
1097 +
1241 1241  == 6.2 Source Code ==
1242 1242  
1243 1243  
1244 1244  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1245 1245  
1246 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1247 1247  
1248 1248  
1249 1249  
1250 1250  * (% style="color:blue" %)**Click to upload**
1251 1251  
1252 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1253 1253  
1254 1254  
1255 1255  
1256 1256  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1257 1257  
1258 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1259 1259  
1260 1260  
1118 +
1261 1261  = 7.  FAQ =
1262 1262  
1121 +
1263 1263  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1264 1264  
1265 1265  
... ... @@ -1266,10 +1266,11 @@
1266 1266  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1267 1267  
1268 1268  
1128 +
1269 1269  == 7.2 What is the pin mapping for the USB program cable? ==
1270 1270  
1271 1271  
1272 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1273 1273  
1274 1274  
1275 1275  
... ... @@ -1284,11 +1284,9 @@
1284 1284  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1285 1285  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1286 1286  
1287 -(% style="display:none" %) (%%)
1288 -
1289 -
1290 1290  == 7.3 Notes on using different serial port tools for TrackerD ==
1291 1291  
1149 +
1292 1292  === 7.3.1  Serial port utility ===
1293 1293  
1294 1294  
... ... @@ -1296,16 +1296,18 @@
1296 1296  
1297 1297  Need to adjust the data stream to RTS/CTS on physical restart.
1298 1298  
1157 +
1299 1299  (% class="wikigeneratedid" %)
1300 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1301 1301  
1302 1302  
1303 -
1304 1304  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1305 1305  
1306 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1307 1307  
1165 +[[image:image-20221102140638-2.png]]
1308 1308  
1167 +
1168 +
1309 1309  === 7.3.2  SecureCRT ===
1310 1310  
1311 1311  
... ... @@ -1312,22 +1312,23 @@
1312 1312  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.
1313 1313  
1314 1314  
1315 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1316 1316  
1317 1317  
1318 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1319 1319  
1320 1320  
1181 +
1321 1321  === 7.3.3  PUTTY ===
1322 1322  
1323 1323  
1324 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1325 1325  
1326 1326  
1327 1327  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.
1328 1328  
1329 1329  
1330 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1331 1331  
1332 1332  
1333 1333  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1339,58 +1339,38 @@
1339 1339  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1340 1340  )))
1341 1341  
1342 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1343 1343  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1344 1344  
1345 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1207 +2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1346 1346  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1347 1347  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1348 1348  
1349 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1213 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1350 1350  
1215 +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.
1351 1351  
1352 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1353 1353  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1354 1354  
1355 1355  
1356 -**3. Compile the AS923_JP band, please refer to the intention shown**
1357 1357  
1358 -
1359 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1360 -
1361 -
1362 -
1363 -**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.**
1364 -
1365 -
1366 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1367 -
1368 -
1369 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1370 -
1371 -
1372 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1373 -
1374 -
1375 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1376 -
1377 -
1378 -== 7.6 Can alert mode and transport mode be used together? ==
1379 -
1380 -
1381 -Yes, you can also press the panic button to sound the alarm if set to transport mode
1382 -
1383 -
1384 1384  = 8  Trouble Shooting =
1385 1385  
1225 +
1386 1386  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1387 1387  
1388 1388  
1389 1389  (((
1390 -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
1230 +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
1391 1391  )))
1392 1392  
1393 1393  
1234 +
1394 1394  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1395 1395  
1396 1396  
... ... @@ -1399,152 +1399,46 @@
1399 1399  )))
1400 1400  
1401 1401  
1243 +
1402 1402  == 8.3  Problem after Upgrading Firmware ==
1403 1403  
1404 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1246 +=== 8.3.1 Continue Restart after upgrading ===
1405 1405  
1406 1406  
1407 -**Error Output**
1408 -
1409 -
1410 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1411 -
1412 -
1413 1413  (((
1414 -Some partition is missed during upgrade, please upgrade below four files as example:
1415 -
1416 -[[image:image-20221207120524-2.png]]
1250 +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
1417 1417  )))
1418 1418  
1419 1419  
1420 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1254 +[[image:image-20221118105249-3.png]]
1421 1421  
1422 1422  
1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 +
1423 1423  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
1424 1424  
1425 1425  
1426 -=== 8.3.3 "flash read err" after upgrade firmware ===
1262 +(((
1263 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1427 1427  
1428 -
1429 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1430 -
1431 -
1432 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1433 -
1434 -
1435 -User need to upgrade again with below four files to solve this issue.
1436 -
1437 - [[image:image-20221207120530-3.png]]
1438 -
1439 - **Figure 2**
1440 -
1441 -
1442 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1443 -
1444 -
1445 -User might erase the entire flash include keys and default settings which cause this issue.
1446 -
1447 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1448 -
1449 -
1450 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1451 -
1452 -
1453 -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.
1454 -
1455 -After AT+FDR. please set
1456 -
1457 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1458 -
1459 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1460 -
1461 -**Example:**
1462 -
1463 -AT+PDOP=7.00
1464 -
1465 -AT+FTIME=180
1466 -
1467 -AT+DEUI=70B3D57ED0053981  
1468 -
1469 -AT+APPEUI=D23345667BCBCCAF
1470 -
1471 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1472 -
1473 -AT+DADDR=260b4dce    ( no need for OTAA)
1474 -
1475 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1476 -
1477 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1478 -
1479 -
1480 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1481 -
1482 -
1483 -Please download version 1.4.2 again
1484 -
1485 -
1486 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1487 -
1488 -
1489 -1） Make Sure the device is in Open Area where can see the sky.
1490 -
1265 +1） Make Sure the device is in Open Area where can see the sky. 
1491 1491  2)  Set PDOP to a higher value.
1492 1492  
1493 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1268 + AT+PDOP=2(can be positioned precisely.）
1494 1494  
1495 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1270 + AT+PDOP=7(Quickly locate in open spaces）
1496 1496  
1497 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1272 + AT+PDOP=14.7(Positioning can be acquired in complex environments）
1498 1498  
1499 1499  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
1275 +)))
1500 1500  
1501 1501  
1502 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1278 +== 8.6 When positioning, it will restart or the PDOP setting is unsuccessful ==
1503 1503  
1280 +Please download version 1.4.2 again
1504 1504  
1505 -When upgrading, use the erase button to upgrade
1506 1506  
1507 -[[image:image-20221207120536-4.png]]
1508 -
1509 -
1510 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1511 -
1512 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1513 -
1514 -
1515 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1516 -
1517 -[[image:image-20221207134028-8.png]]
1518 -
1519 -
1520 -Reboot information after upgrade
1521 -
1522 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1523 -
1524 -
1525 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal
1526 -
1527 -[[image:image-20221128111850-5.png]]
1528 -
1529 -
1530 -After the parameters return to normal, upgrade to the version you need again
1531 -
1532 -[[image:image-20221207120601-5.png]]
1533 -
1534 -
1535 -At this point, the parameters return to normal after running AT+FDR again
1536 -
1537 -[[image:image-20221128112035-7.png]]
1538 -
1539 -
1540 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1541 -
1542 -
1543 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1544 -
1545 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1546 -
1547 -
1548 1548  = 9.  Order Info =
1549 1549  
1550 1550  
... ... @@ -1553,22 +1553,13 @@
1553 1553  (% style="color:blue" %)**XXX**(%%): The default frequency band
1554 1554  
1555 1555  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1556 -
1557 1557  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1558 -
1559 1559  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1560 -
1561 1561  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1562 -
1563 1563  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1564 -
1565 1565  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1566 -
1567 1567  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1568 1568  
1569 -(% style="display:none" %) (%%)
1570 -
1571 -
1572 1572  = 10.  Packing Info =
1573 1573  
1574 1574  
... ... @@ -1575,36 +1575,22 @@
1575 1575  (% style="color:#037691" %)**Package Includes**:
1576 1576  
1577 1577  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1578 -
1579 1579  * USB recharge & program cable x 1
1580 1580  
1581 1581  (% style="color:#037691" %)**Dimensions and Weight**:
1582 1582  
1583 1583  * Device Size: 85 x 48 x 15 mm
1584 -
1585 1585  * Weight: 50g
1586 1586  
1587 -(% style="display:none" %) (%%)
1588 -
1589 -
1590 1590  = 11. Support =
1591 1591  
1592 1592  
1593 1593  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1594 -
1595 1595  * 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]].
1596 1596  
1597 -(% style="display:none" %) (%%)
1598 -
1599 -
1600 1600  = 12.  Reference =
1601 1601  
1602 1602  
1603 1603  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1604 -
1605 1605  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1606 -
1607 1607  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1608 -
1609 -
1610 -)))
image-20221122100004-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -127.2 KB
Content
image-20221122100004-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -12.5 KB
Content
image-20221122100004-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
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
image-20230213110119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.3 KB
Content
image-20230213110214-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.3 KB
Content
image-20230213110506-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.8 KB
Content
image-20230302145315-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20230307135914-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -131.8 KB
Content
image-20230307135932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -109.7 KB
Content
image-20230308115430-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 MB
Content
image-20230308115616-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.7 KB
Content
image-20230308115701-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 MB
Content