Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 60.2
edited by Edwin Chen
on 2022/10/08 18:26
Change comment: There is no comment for this version
To version 19.2
edited by Xiaoling
on 2022/09/30 09:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,15 +9,6 @@
1 -== ==
2 -
3 -(% style="text-align:center" %)
4 -[[image:1664505654417-133.png]]
5 -
6 -
7 -
8 -
9 9  (% class="wikigeneratedid" %)
10 10  **Table of Contents:**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
... ... @@ -16,10 +16,9 @@
16 16  
17 17  = 1.  Introduction =
18 18  
10 +== 1.1  OverView ==
19 19  
20 -== 1.1  What is TrackerD ==
21 21  
22 -
23 23  (((
24 24  TrackerD is an (% style="color:blue" %)**Open Source LoRaWAN Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**.
25 25  )))
... ... @@ -27,14 +27,10 @@
27 27  (((
28 28  In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.
29 29  
30 -(((
31 31  TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
32 -)))
33 33  
34 -(((
35 35  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.
36 36  )))
37 -)))
38 38  
39 39  (((
40 40  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.
... ... @@ -48,7 +48,6 @@
48 48  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
49 49  
50 50  
51 -
52 52  == 1.2 Specifications ==
53 53  
54 54  
... ... @@ -63,11 +63,13 @@
63 63  * EEPROM: 520 KB
64 64  * Clock Speed: 32Mhz
65 65  
51 +
66 66  (% style="color:blue" %)**Common DC Characteristics:**
67 67  
68 68  * Supply Voltage: 5V via USB port or Internal li-on battery
69 69  * Operating Temperature: -40 ~~ 60°C
70 70  
57 +
71 71  (% style="color:blue" %)**LoRa Spec:**
72 72  
73 73  * Frequency Range,
... ... @@ -89,10 +89,12 @@
89 89  * Packet engine up to 256 bytes with CRC.
90 90  * LoRaWAN 1.0.3 Specification
91 91  
79 +
92 92  (% style="color:blue" %)**Battery:**
93 93  
94 94  * 1000mA Li-on Battery power (for model TrackerD)
95 95  
84 +
96 96  (% style="color:blue" %)**Power Consumption**
97 97  
98 98  * Sleeping Mode: 200uA
... ... @@ -99,6 +99,9 @@
99 99  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
100 100  * Tracking: max: 38mA
101 101  
91 +
92 +
93 +
102 102  == 1.3  Features ==
103 103  
104 104  
... ... @@ -105,7 +105,7 @@
105 105  * LoRaWAN 1.0.3 Class A
106 106  * ESP32 PICO D4
107 107  * SX1276/78 Wireless Chip
108 -* Arduino IDE Compatible
100 +* Arduino IDE Compatible
109 109  * Open source hardware / software
110 110  * Regular/ Real-time GPS,BLE,WIFI tracking
111 111  * Built-in3 axis accelerometer (LIS3DH)
... ... @@ -117,6 +117,8 @@
117 117  * Tri-color LED, Alarm button
118 118  * Datalog
119 119  
112 +
113 +
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -123,607 +123,536 @@
123 123  * Logistics and Supply Chain Management
124 124  * Human tracking
125 125  
126 -= 2.1 Use TrackerD =
127 127  
128 128  
129 -== 2.1 How it works? ==
130 130  
123 +1. Use TrackerD
124 +11. How it works?
131 131  
126 +
132 132  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.
133 133  
134 134  
130 +1.
131 +11. Quick guide to connect to LoRaWAN server
135 135  
136 -== 2.2 Quick guide to connect to LoRaWAN server ==
133 +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.
137 137  
138 138  
139 -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. 
136 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
140 140  
141 141  
142 -[[image:1664501652064-326.png]]
143 -
144 -
145 -
146 146  The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:
147 147  
141 +**Step 1**: Create a device in TTN V3 with the OTAA keys from TrackerD.
148 148  
149 -(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
150 -
151 151  Each TrackerD is shipped with a sticker with the default device EUI as below:
152 152  
145 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
153 153  
154 -[[image:1664501677253-891.png]]
155 155  
156 156  
149 +
157 157  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
158 158  
159 159  
160 -**__Add APP EUI in the application:__**
153 +Add APP EUI in the application
161 161  
155 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
162 162  
163 -[[image:1664501711466-918.png]]
157 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
164 164  
165 165  
160 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
166 166  
167 -[[image:1664501721248-725.png]]
168 168  
169 169  
170 -[[image:1664501734705-405.png]]
164 +Add APP KEY and DEV EUI
171 171  
166 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
172 172  
173 173  
174 -**__Add APP KEY and DEV EUI:__**
175 175  
176 176  
177 -[[image:1664501784668-703.png]]
171 +**Step 2**: Power on TrackerD by using the on board switch.
178 178  
179 179  
174 +**Step 3:** TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
180 180  
181 181  
182 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
177 +**Positioning Mode(SMOD):**
183 183  
179 +* **GPS ONLY(Factory Settings): **only get GPS location info.
180 +* **BLE ONLY: **Only obtain iBeacon info via BLE. Design for Indoor tracking.
181 +* **GPS/BLE Hybrid: **Combination for Indoor and Outdoor tracking.
184 184  
185 -(% 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.
183 +User can switch modes by [[changing SMOD>>path:#Positioning_Mode]].
186 186  
187 187  
188 -== 2.3 Positioning Mode(SMOD) ==
186 +1.
187 +11. Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~-
189 189  
190 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191 191  
192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
193 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
194 -* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
190 +1.
191 +11.
192 +111. Uplink FPORT=5, Device Status
195 195  
196 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197 197  
198 198  
199 -== 2.3 Uplink Payload ==
196 +1.
197 +11.
198 +111. Uplink FPORT= , Realtime GNSS Positioning
200 200  
200 +The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won’t work on DR0 on US915/AU915 frequency band. )
201 201  
202 -=== 2.3.1 Uplink FPORT~=5, Device Status ===
203 203  
204 -Uplink the device configures with FPORT=5. Once LGT92 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours.
203 +|(((
204 +**Size**
205 205  
206 -|=(% style="width: 150px;" %)**Size (bytes)**|=(% style="width: 233px;" %)**1**|=(% style="width: 150px;" %)**2**|=(% style="width: 164px;" %)**1**|=(% style="width: 215px;" %)**1**|=(% style="width: 94px;" %)2|=(% style="width: 516px;" %)**2**|=(% style="width: 516px;" %)1
207 -|(% style="width:150px" %)**Value**|(% style="width:233px" %)Sensor Model|(% style="width:150px" %)Firmware Version|(% style="width:164px" %)Frequency Band|(% style="width:215px" %)Sub-band|(% style="width:94px" %)BAT|(% style="width:516px" %)SMOD|(% style="width:516px" %)Status
206 +**(bytes)**
207 +)))|4|4|2|1|(((
208 +2
208 208  
209 -[[image:image-20221006181357-2.png]]
210 -
211 -Example Payload (FPort=5):  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]]
212 -
213 -**Sensor Model**: For TrackerD, this value is 0x13.
214 -
215 -**Firmware Version**: 0x0100, Means: v1.0.0 version.
216 -
217 -**Frequency Band**:
218 -
219 -*0x01: EU868
220 -
221 -*0x02: US915
222 -
223 -*0x03: IN865
224 -
225 -*0x04: AU915
226 -
227 -*0x05: KZ865
228 -
229 -*0x06: RU864
230 -
231 -*0x07: AS923
232 -
233 -*0x08: AS923-1
234 -
235 -*0x09: AS923-2
236 -
237 -*0x0a: AS923-3
238 -
239 -**Sub-Band**: value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
240 -
241 -**BAT**: shows the battery voltage for TrackerD.
242 -
243 -Ex1: 0x0B3A = 2874mV
244 -
245 -Use can also get the Device Status uplink through the downlink command:
246 -
247 -
248 -=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
249 -
250 -
251 -User can use **AT+SMOD=1,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band.
252 -
253 -
254 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
255 -|=(% scope="row" style="width: 50px;" %)(((
256 -**Size(bytes)**
257 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
210 +(optional )
211 +)))|(((
258 258  2
259 -)))|(% style="width:87px" %)(((
260 -2
213 +
214 +(optional)
261 261  )))
262 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
263 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
264 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
216 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|(((
217 +[[Alarm &>>path:#Alarm]]
265 265  
266 -[[image:1664501958445-288.png]]
219 +[[BAT>>path:#Alarm]]
220 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]]
267 267  
268 268  
269 -==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
223 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
270 270  
271 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
272 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
273 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
274 274  
275 -==== (% style="color:blue" %)**FLAG:**(%%) ====
226 +**Alarm & BAT:**
276 276  
277 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
278 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
279 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
228 +|**Size(bit)**|1 bit|1bit|14 bits
229 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]]
280 280  
281 -**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
231 +**FLAG:**
282 282  
233 +|**Size(bit)**|2 bits|1bit|5 bits
234 +|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version
283 283  
284 -==== (% style="color:blue" %)**Location info:**(%%) ====
285 285  
286 -* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
287 -* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
288 288  
289 -(% style="color:red" %)**Important note:**
238 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A **
290 290  
291 -1.  When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
292 292  
293 -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:
241 +**Location info:**
294 294  
243 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~://
295 295  
296 -[[image:1664502116362-706.png]]
245 +//value = 02863D68 /1000000 = 42.351976//
297 297  
247 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://
298 298  
299 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
249 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
300 300  
301 -[[image:1664502166010-515.png]]
302 302  
252 +Important note:
303 303  
254 +1. When power is low (<2.84v), GPS won’t be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
255 +1. In firmware version v1.5, Roll & Pitch is disabled by default.
256 +1. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
304 304  
305 -==== (% style="color:blue" %)**Alarm:**(%%) ====
258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
306 306  
307 -Example:  0x4B & 0x40 >> 6 = 0x01
308 308  
261 +1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
309 309  
310 -==== (% style="color:blue" %)**BAT:**(%%) ====
263 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
311 311  
312 -Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
265 +* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01
266 +* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV).
313 313  
314 -(((
315 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
316 -)))
268 +The battery info shows the current voltage, for **TrackerD** version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
317 317  
318 -* > 4.0v :  80% ~~ 100%
319 -* 3.85v ~~3.99v:  60% ~~ 80%
320 -* 3.70v ~~ 3.84v:  40% ~~ 60%
321 -* 3.40v ~~ 3.69v:  20% ~~ 40%
322 -* < 3.39v:  0~~20%
323 323  
324 -==== (% style="color:blue" %)**LON:**(%%) ====
271 +* > 4.0v : 80% ~~ 100%
272 +* 3.85v ~~3.99v: 60% ~~ 80%
273 +* 3.70v ~~ 3.84v: 40% ~~ 60%
274 +* 3.40v ~~ 3.69v: 20% ~~ 40%
275 +* < 3.39v: 0~~20%
325 325  
326 -Enable/Disable LED activity for uplink
327 327  
328 -(((
329 -0x00:  Disable LED indicator.
330 -)))
278 +* **LON: **Enable/Disable LED activity for uplink
331 331  
332 -(((
333 -0x01:  Enable LED indicator (Default Value)
334 -)))
280 +0x00: Disable LED indicator.
335 335  
282 +0x01: Enable LED indicator (Default Value)
336 336  
337 -==== (% style="color:blue" %)**Hum:**(%%) ====
338 338  
339 -0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
285 +* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
286 +* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree
340 340  
341 341  
342 -==== (% style="color:blue" %)**Tem:**(%%) ====
343 343  
344 -011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
290 +1.
291 +11.
292 +111. Uplink FPORT= , History GNSS Positioning
345 345  
346 346  
347 -=== 2.3.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
348 348  
349 -The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
296 +1.
297 +11.
298 +111. BLE positioning Payload(Fport=2)
350 350  
300 +Different MODE has different payload:
351 351  
352 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
353 -|=(% scope="row" style="width: 50px;" %)(((
354 -**Size(bytes)**
355 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
356 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
357 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
358 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
302 +**MODE=2**
359 359  
304 +|(((
305 +**Size**
360 360  
361 -=== 2.3.4  Uplink FPORT~=4, History GNSS Positioning ===
307 +**(bytes)**
308 +)))|16|4|4|2|4|2|1
309 +|**Value**|[[UUID>>path:#Location]]|(((
310 +iBeacon
362 362  
363 -Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-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.
312 +MAJOR
313 +)))|(((
314 +iBeacon
364 364  
365 -**Note for this mode:**
316 +MINOR
317 +)))|(((
318 +iBeacon Measured
366 366  
367 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
368 -* b) TrackerD will send data in **CONFIRMED Mode** when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
320 +Power
321 +)))|(((
322 +iBeacon
369 369  
370 -The payload is 15 bytes, as below.
324 +RSSI
325 +)))|(((
326 +[[Alarm &>>path:#Alarm]]
371 371  
328 +[[BAT>>path:#Alarm]]
329 +)))|[[FLAG>>path:#Flag]]
372 372  
373 373  
374 -=== 2.3.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
332 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
375 375  
376 376  
377 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
378 -|=(% scope="row" style="width: 60px;" %)(((
379 -**Size(bytes)**
380 -)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
381 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
382 -iBeacon MAJOR
383 -)))|(% style="width:63px" %)(((
384 -iBeacon MINOR
385 -)))|(% style="width:71px" %)(((
386 -iBeacon Measured Power
387 -)))|(% style="width:50px" %)(((
388 -iBeacon RSSI
389 -)))|(% style="width:47px" %)(((
390 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
391 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
335 +* **BAT**: Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
336 +* **MODE: **Define the payload format.
337 +* **UUID: **The uuid from the strongest iBeacon.
338 +* **MAJOR**: The MAJOR from the strongest iBeacon.
339 +* **MINOR**: The MAJOR from the strongest iBeacon.
340 +* **Measured** **Power**: The Measured Power from the strongest iBeacon.
341 +* **RSSI**: The RSSI from the strongest iBeacon.
392 392  
393 -[[image:1664502425687-834.png]]
394 394  
344 +1.
345 +11.
346 +111. Add Payload format in TTN V3
395 395  
396 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
397 -* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
398 -* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
399 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
400 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
401 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
402 -* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
403 -
404 -=== 2.3.5 Add Payload format in TTN V3 ===
405 -
406 -
407 407  In TTN V3, use can add a custom payload so it shows friendly.
408 408  
409 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
350 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
410 410  
352 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
411 411  
412 -[[image:1664502649601-895.png]]
413 -
414 -
415 415  Add the decoder from this link:
416 416  
417 417  
418 418  Save the change the uplink message will be parsed. As below:
419 419  
420 -[[image:1664502676891-606.png]]
359 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
421 421  
422 422  
423 423  
424 -== 2.4 Integrate with Datacake ==
425 425  
426 426  
427 -(((
428 -After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
429 -)))
365 +1.
366 +11. Integrate with Datacake
430 430  
431 -(((
432 -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]]
433 -)))
434 434  
369 +After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
435 435  
436 -[[image:1664502695771-538.png]]
371 +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]]
437 437  
373 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
438 438  
439 439  
440 -== 2.5 Integrate with Tago ==
376 +1.
377 +11. Integrate with Tago
441 441  
442 442  
443 -(((
444 444  After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
445 -)))
446 446  
447 -(((
448 448  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]]
449 -)))
450 450  
384 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
451 451  
452 -[[image:1664502715371-321.png]]
453 453  
454 454  
455 455  
456 -== 2.6 Datalog Feature ==
389 +1.
390 +11. Alarm Mode
457 457  
458 458  
459 -== 2.6 Alarm Mode ==
393 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
460 460  
461 461  
462 -(((
463 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
464 -)))
396 +Once enter Alarm mode, the **GREEN LED** will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
465 465  
466 466  
467 -(((
468 -Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
469 -)))
470 -
471 -
472 -(((
473 473  Two ways to exit alarm mode:
474 -)))
475 475  
476 476  * Server send a downlink command to exit.
477 477  * User fast press the RED button 10 times.
478 478  
479 -(((
480 -When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
481 -)))
404 +When exit alarm mode, **RED LED** will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
482 482  
483 483  
407 +1.
408 +11. Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--
484 484  
485 -== 2.7 Transport Mode ==
486 486  
487 487  
488 -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.
412 +1.
413 +11. LED Status
489 489  
490 490  
491 -== 2.8 LED Status ==
416 +|**Event**|**Action**|**AT+LON to control on/off**
417 +|**Power On**|**BLUE, RED , Green** flash once|N/A
418 +|**Join request**|**Green** led fast blink once (200ms)|Yes
419 +|**Join Success**|**Green** led on 5 second|N/A
420 +|**Fixing Location**|**BLUE **blinks 200ms per second|Yes
421 +|**Fixed and uplink**|**GREEN **blinks twice (200ms per blink)|Yes
422 +|**Fail Fix and uplink**|**RED **blinks twice (200ms per blink)|Yes
423 +|**Enter Alarm mode**|**RED **on for 3 seconds|Yes
424 +|**Uplink under Alarm**|**RED **on for 1 second|Yes
425 +|**Exit Alarm**|**BLUE **led on 5 second|Yes
426 +|**Get Downlink**|**GREEN** led on 1 second|Yes
427 +|**Movement Detect**|**RED **on 500ms|N/A
492 492  
493 493  
494 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
495 -|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
496 -|(% 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
497 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
498 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
499 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
500 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
501 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
502 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
503 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
504 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
505 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
506 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
507 507  
508 -== 2.9 Button Function ==
509 509  
510 510  
511 -(% style="color:blue" %)**RESET button:**
433 +1.
434 +11. Button Function
512 512  
513 -[[image:1664502835802-546.png]]
436 +**RESET button:**
514 514  
438 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
439 +
515 515  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
516 516  
517 517  
518 -(% style="color:red" %)**RED button:**
443 +**RED button:**
519 519  
520 -[[image:1664502854406-763.png]]
445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
521 521  
447 +|**Function**|**Action**|**Description**
448 +|Send Alarm|Keep Pressing **RED** button for more than 5 seconds|Enter Alarm Mode.  See [[Alarm Mode>>path:#Alarm_Mode]]
449 +|Exit Alarm Mode|Fast press the **RED** button 10 times|Exit Alarm Mode
450 +|Enter Deep Sleep Mode|Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy.
522 522  
523 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
524 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
525 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
526 -|(% 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
527 -|(% 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.
528 528  
529 -== 2.10 USB Port Function ==
530 530  
531 531  
455 +1.
456 +11. USB Port Function
457 +
532 532  The USB interface of TrackerD has below functions:
533 533  
534 534  * Power on the device
535 535  * Recharge the battery
536 -* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
537 -* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
462 +* [[Configure Device>>path:#AT_Command]]
463 +* [[Upgrade Firmware>>path:#upgrade_image]]
538 538  
539 -= 3. Configure TrackerD via AT command or LoRaWAN downlink =
540 540  
541 541  
542 -User can configure TrackerD via AT Command or LoRaWAN Downlink.
543 543  
544 -LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
545 545  
469 +1. Configure TrackerD via AT command or LoRaWAN downlink
546 546  
547 547  
548 -== 3.1 Access AT Command ==
472 +User can configure TrackerD via AT Command or LoRaWAN Downlink.
549 549  
474 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
550 550  
551 -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.
552 552  
477 +1.
478 +11. Access AT Command
553 553  
554 -[[image:1664502999401-486.png]]
480 +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. ...
555 555  
482 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
556 556  
557 -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:
558 558  
485 +In PC, User needs to set serial tool baud rate to **115200** to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
559 559  
560 -[[image:1664503022490-662.png]]
561 561  
488 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
562 562  
563 563  
564 -[[image:1664503035713-500.png]]
565 565  
492 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
566 566  
494 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
567 567  
568 -[[image:1664503047675-651.png]]
569 569  
497 +1.
498 +11. Command Set
570 570  
571 571  
572 -== 3.2 Command Set ==
501 +1.
502 +11.
503 +111. Set Transmit Interval
573 573  
574 -
575 -=== 3.2.1 Set Transmit Interval ===
576 -
577 -
578 578  Set device uplink interval.
579 579  
580 -* (% style="color:blue" %)**AT Command:**
507 +* AT Command:
581 581  
582 -(% style="color:#037691" %)**AT+TDC=xxx **
509 +AT+TDC=xxx
583 583  
584 -Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
511 +Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
585 585  
586 586  
587 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
514 +* Downlink Payload (prefix 0x01):
588 588  
589 -(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
516 +0x01 00 01 2C     ~/~/ Same as AT+TDC=300000
590 590  
591 591  
519 +1.
520 +11.
521 +111. Set Alarm Packet transmission interval
592 592  
593 -=== 3.2.2 Set Alarm Packet transmission interval ===
594 -
595 -
596 596  Set alarm packet transmit interval
597 597  
598 -* (% style="color:blue" %)**AT Command:**
525 +* AT Command:
599 599  
600 -(% style="color:#037691" %)**AT+ATDC=xx. **
527 +AT+ATDC=xx.
601 601  
602 -Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
529 +Example: AT+ATDC=60000  à Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
603 603  
604 604  
605 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
532 +* Downlink Payload (prefix 0xB1):
606 606  
607 -(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
534 +0xB1 00 00 3C    ~/~/Same as AT+ATDC=60000
608 608  
609 609  
537 +1.
538 +11.
539 +111. Set Sports Mode Packet transmission interval
610 610  
611 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
541 +Set sports packet transmit interval
612 612  
543 +* AT Command:
613 613  
614 -Set Transport Mode packet transmit interval
545 +AT+MTDC=xx.
615 615  
616 -* (% style="color:blue" %)**AT Command:**
547 + Example: AT+MTDC=300000  à Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
617 617  
618 -(% style="color:#037691" %)**AT+MTDC=xx. **
619 619  
620 -Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
550 +* Downlink Payload (prefix 0x03):
621 621  
552 +0x03 00 01 2C    ~/~/Same as AT+ MTDC=3000000
622 622  
623 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
624 624  
625 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
626 626  
556 +1.
557 +11.
558 +111. Exit Alarm
627 627  
628 -
629 -=== 3.2.4 Exit Alarm ===
630 -
631 -
632 632  Server send downlink command to exit Alarm mode
633 633  
634 -* (% style="color:blue" %)**AT Command: No AT Command**
562 +* AT Command:
635 635  
636 -* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
564 +No AT Command
637 637  
638 -(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
639 639  
567 +* Downlink Payload (prefix 0x02):
640 640  
569 +0x02 01     ~/~/ Exit Alarm Mode
641 641  
642 -=== 3.2.5 Disable/Enable LED flash ===
643 643  
572 +1.
573 +11.
574 +111. Disable/Enable LED flash
644 644  
645 645  Disable/Enable LED for position, downlink and uplink
646 646  
647 -* (% style="color:blue" %)**AT Command:**
578 +* AT Command:
648 648  
649 -(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
580 +AT+LON=xx.  (Disable (0), Enable (1), default:1)
650 650  
651 -Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
582 + Example: AT+LON=0 à Disable LED for position, downlink and uplink.
652 652  
653 653  
654 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
585 +* Downlink Payload (prefix 0xAE):
655 655  
656 -(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
587 +0xAE 00    ~/~/Same as AT+LON=0
657 657  
658 658  
659 659  
660 -=== 3.2.6 Disable/Enable Transport Mode ===
661 661  
592 +1.
593 +11.
594 +111. Disable/Enable movement detect (Debug Only)
662 662  
663 -Users can use this feature to enable/disable Transport Mode.
596 +User can use this feature to check and set thread hole of movement detect
664 664  
665 -* (% style="color:blue" %)**AT Command:**
598 +* AT Command:
666 666  
667 -(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
600 +AT+INTWK=xx.  (Disable (0), Enable (1), default:0)
668 668  
669 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
602 + Example: AT+ INTWK =1 à Enable detect movement.
670 670  
671 671  
672 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
605 +* Downlink Payload (prefix 0xAF):
673 673  
674 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
607 +0xAF 01    ~/~/Same as AT+ INTWK =1
675 675  
676 676  
677 677  
678 -=== 3.2.7 Set Positioning Mode ===
611 +1.
612 +11.
613 +111. Set Positioning Mode
679 679  
615 +SMOD define the how TrackerD scan and uplink date.
680 680  
681 -SMOD define the how TrackerD scan and uplink data:
617 +GPS室外定位模式：设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
682 682  
619 + BLE室内定位模式：设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
683 683  
684 -* (% style="color:blue" %)**AT Command:**
621 + GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
685 685  
686 -(% style="color:#037691" %)**AT+SMOD=aa,bb**
623 +运动模式：设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
687 687  
688 -(% style="color:#037691" %)** aa:**
689 689  
690 -* (% style="color:#037691" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
691 -* (% style="color:#037691" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
692 -* (% style="color:#037691" %)**3: GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning
693 693  
694 694  
695 -(% style="color:#037691" %)**bb:**
628 +* AT Command:
696 696  
697 -(% style="color:#037691" %)** if aa = 1: **
630 +AT+SMOD=xx.
698 698  
699 -* (% style="color:#037691" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
700 -* (% style="color:#037691" %)**1 :**(%%)  GPS +BAT State
632 + Example:
701 701  
634 + AT+ SMOD =1,0    à GPS+ BAT+ State+Tem&Hum
702 702  
703 -(% style="color:#037691" %)** if aa = 2: **
636 + AT+ SMOD =1,1    à GPS +BAT State
704 704  
705 -* (% style="color:#037691" %)**3 :  **(%%)(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
638 + AT+ SMOD =2,3    à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
706 706  
707 707  
641 +* Downlink Payload (prefix 0xA5):
708 708  
709 - **Example:**
643 +0xA5 01 00     ~/~/ Same as AT+ SMOD =1,0
710 710  
711 - AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
712 712  
713 - AT+ SMOD =1,1    **~-~->**  GPS +BAT State
646 +1.
647 +11.
648 +111. Set MAX GPS position time
714 714  
715 - AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
716 -
717 -
718 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
719 -
720 -(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
721 -
722 -
723 -
724 -=== 3.2.8 Set MAX GPS position time ===
725 -
726 -
727 727  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.
728 728  
729 729  
... ... @@ -730,105 +730,102 @@
730 730  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.
731 731  
732 732  
733 -* (% style="color:blue" %)**AT Command:**
656 +* AT Command:
734 734  
735 -(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
658 +AT+FTIME=xx  à Set to use xx as max fix time.
736 736  
737 -Example:  AT+FTIME=150
660 +Example: AT+FTIME=150
738 738  
739 739  
740 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
663 +* Downlink Payload (prefix 0xAA):
741 741  
742 -(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
665 +0xAA 00 96      ~/~/Set AT+FTIME=150
743 743  
744 744  
745 745  
746 -=== 3.3.9 Set PDOP value for GPS fix accuracy ===
747 747  
670 +1.
671 +11.
672 +111. Set PDOP value for GPS fix accuracy
748 748  
749 -PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
674 +PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can’t get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
750 750  
751 751  
752 752  A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
753 753  
754 754  
755 -* (% style="color:blue" %)**AT Command:**
680 +* AT Command:
756 756  
757 -(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
682 +AT+PDOP=2.5  à Set PDOP to 2.5
758 758  
759 759  
760 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
685 +* Downlink Payload (prefix 0xAD):
761 761  
762 -(% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
687 +0xAD 00 0A    ~/~/Set AT+PDOP=1    (0x0A / 10 =1)
763 763  
764 -(% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
689 +0xAD 00 19    ~/~/Set AT+PDOP=2.5    (0x19 / 10 =2.5)
765 765  
766 -(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
691 +0xAD 00 46    ~/~/Set AT+PDOP=7     (0x46 / 10 =7)
767 767  
768 -
769 -
770 770  Disable/Enable the confirmation mode
771 771  
772 -* (% style="color:blue" %)**AT Command:**
695 +* AT Command:
773 773  
774 -(% style="color:#037691" %)**AT+CFM=xx. **
697 +AT+CFM=xx.
775 775  
699 + Example:
776 776  
777 -**~ Example:**
701 + AT+ CFM=0    à Disable confirmation
778 778  
779 - AT+ CFM=0    **~-~->   ** Disable confirmation
703 + AT+ CFM=1    à Enable confirmation
780 780  
781 - AT+ CFM=1    **~-~->  ** Enable confirmation
782 782  
706 +* Downlink Payload (prefix 0x05):
783 783  
784 -* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
708 +0x05 01      ~/~/ Same as AT+ SMOD =1
785 785  
786 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
787 787  
788 788  
789 789  
790 -= 4. Setting for Different Scenarios =
791 791  
792 792  
715 +1. Setting for Different Scenarios
793 793  
794 -= 5. Upload Firmware =
795 795  
796 796  
797 -== 5.1 Firmware Change Log ==
719 +1. Upload Firmware
720 +11. Firmware Change Log
798 798  
799 -
800 800  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
801 801  
802 802  
725 +1.
726 +11. How to upgrade firmware
803 803  
804 -== 5.2 How to upgrade firmware ==
728 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
805 805  
806 806  
807 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
731 +**Step1:  **Connect TrackerD and PC via USB cable shipped with TrackerD.
808 808  
733 +**Step2:**  Install CH9102 driver in the PC.
809 809  
810 -(% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
811 -
812 -
813 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
814 -
815 815  After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
816 816  
817 817  
818 -(% style="color:blue" %)**Step3:  **(%%)Download and Install Flash Tool:  [[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]
738 +**Step3：** Download and Install Flash Tool:
819 819  
740 +[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]
820 820  
821 -(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
742 +**Step4:**  Run Flash Download Tool and configure chip type to ESP32
822 822  
823 823  
824 -[[image:1664503563660-578.png]]
745 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]]
825 825  
747 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]]
826 826  
827 -[[image:1664503574618-659.png]]
828 828  
750 +**Step5:**  Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
829 829  
830 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
831 -
832 832  [[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
833 833  
834 834  
... ... @@ -838,77 +838,75 @@
838 838  
839 839  ESP_LORA-eeprom-class.bin @ 0x10000
840 840  
761 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]]
841 841  
842 -[[image:1664503593459-435.png]]
843 -
844 -
845 -
846 846  After upgrade finish, it will show finish as below:
847 847  
848 -[[image:1664503611848-385.png]]
765 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]]
849 849  
850 850  
851 851  
852 -= 6. Developer Guide =
853 853  
854 854  
855 -== 6.1 Compile Source Code ==
771 +1. Developer Guide
856 856  
857 857  
858 -=== 6.1.1 Set up ARDUINO compile environment ===
774 +*
775 +*1. Compile Source Code
776 +*11. Set up ARDUINO compile environment
777 +* Download the latest Arduino software (IDE) from the Arduino official website
859 859  
779 +[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]
860 860  
861 -* **Download the latest Arduino software (IDE) from the Arduino official website:  [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]**
781 +Install IDE on PC, open and click 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]]
862 862  
863 -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]]
783 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
864 864  
785 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it.
865 865  
866 -[[image:1664503635019-941.png]]
787 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
867 867  
868 868  
869 -* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
790 +* Download the latest TrackerD from the dragino github
870 870  
871 -[[image:1664503715811-892.png]]
792 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
872 872  
873 873  
795 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory
874 874  
875 -* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
797 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
876 876  
877 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
878 878  
879 879  
880 -[[image:1664503752288-974.png]]
881 881  
802 +*
803 +*1. Source Code
804 +* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
882 882  
806 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
883 883  
884 -== 6.2 Source Code ==
808 +* Click to upload
885 885  
810 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
886 886  
887 -* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
812 +* Check the result, if the upload is successful, as shown below, open the serial port to view the data
888 888  
889 -[[image:1664503794261-827.png]]
890 890  
815 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]]
891 891  
892 892  
893 -* (% style="color:blue" %)**Click to upload**
894 894  
895 -[[image:1664503808294-336.png]]
896 896  
897 897  
898 898  
899 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
900 -
901 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
902 -
903 -
904 -
905 905  = 7.  FAQ =
906 906  
907 907  
825 +
908 908  == 7.1 How to change the LoRa Frequency Bands/Region? ==
909 909  
910 910  
911 -User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
829 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
912 912  
913 913  
914 914  
... ... @@ -919,8 +919,8 @@
919 919  
920 920  
921 921  
922 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
923 -|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
840 +(% border="2" style="background-color:#ffffcc; color:green; width:314px" %)
841 +|(% style="width:118px" %)**Pin**|(% style="width:67px" %)**Color**|(% style="width:123px" %)**USB Pin**
924 924  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
925 925  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
926 926  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
... ... @@ -938,6 +938,7 @@
938 938  (% style="color:blue" %)**XXX**(%%): The default frequency band
939 939  
940 940  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
859 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470
941 941  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
942 942  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
943 943  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
... ... @@ -945,25 +945,33 @@
945 945  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
946 946  * (% style="color:red" %)**US915**(%%): Default frequency band US915
947 947  
867 +
948 948  = 9.  Packing Info =
949 949  
950 950  
951 -(% style="color:#037691" %)**Package Includes**:
871 +**Package Includes**:
952 952  
953 -* TrackerD LoRaWAN GPS/BLE Tracker x 1
954 -* USB recharge & program cable x 1
873 +* TrackerD x 1
874 +* Rechargeable cable x 1
875 +* Program Cable x 1
955 955  
956 -(% style="color:#037691" %)**Dimensions and Weight**:
877 +**Dimensions and Weight**:
957 957  
958 -* Device Size: 85 x 48 x 15 cm
959 -* Weight: 50g
879 +* Device Size: 85 x 48 x 15 mm/pcs
880 +* Weight: 55g/pcs
960 960  
961 -= 10. Support =
962 962  
963 963  
884 += 10. Support =
885 +
964 964  * 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.
965 -* 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]].
887 +* 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
966 966  
889 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
890 +
891 +
892 +
893 +
967 967  = 11.  Reference =
968 968  
969 969  
... ... @@ -970,5 +970,3 @@
970 970  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
971 971  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
972 972  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
973 -
974 -
1664501652064-326.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.9 KB
Content
1664501677253-891.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -202.7 KB
Content
1664501711466-918.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
1664501721248-725.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -55.6 KB
Content
1664501734705-405.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.1 KB
Content
1664501784668-703.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
1664501958445-288.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
1664502116362-706.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
1664502166010-515.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
1664502425687-834.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -38.2 KB
Content
1664502649601-895.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.2 KB
Content
1664502676891-606.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.3 KB
Content
1664502695771-538.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -54.7 KB
Content
1664502715371-321.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.9 KB
Content
1664502835802-546.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -37.8 KB
Content
1664502854406-763.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.3 KB
Content
1664502999401-486.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -916.7 KB
Content
1664503022490-662.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.6 KB
Content
1664503035713-500.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -354.0 KB
Content
1664503047675-651.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -199.1 KB
Content
1664503563660-578.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -38.1 KB
Content
1664503574618-659.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -139.8 KB
Content
1664503593459-435.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.3 KB
Content
1664503611848-385.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -175.9 KB
Content
1664503635019-941.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -161.8 KB
Content
1664503715811-892.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.6 KB
Content
1664503752288-974.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -112.6 KB
Content
1664503794261-827.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.5 KB
Content
1664503808294-336.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -161.6 KB
Content
1664503824081-592.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.4 KB
Content
1664503831430-500.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
1664505654417-133.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.5 KB
Content
image-20221006181316-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.7 KB
Content
image-20221006181357-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -88.0 KB
Content