Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 155.4
edited by Xiaoling
on 2022/11/24 17:21
Change comment: There is no comment for this version
To version 54.1
edited by Edwin Chen
on 2022/10/06 18:13
Change comment: Uploaded new attachment "image-20221006181357-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
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  
... ... @@ -14,6 +14,7 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 +
17 17  == 1.1  What is TrackerD ==
18 18  
19 19  
... ... @@ -31,17 +31,21 @@
31 31  (((
32 32  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.
33 33  )))
35 +)))
34 34  
35 35  (((
36 36  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 +
37 37  )))
38 38  
39 -[[image:1664499921684-770.png||_mstalt="298194"]]
43 +[[image:1664499921684-770.png]]
40 40  
41 41  
42 42  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
43 43  
44 44  
49 +
45 45  == 1.2 Specifications ==
46 46  
47 47  
... ... @@ -93,7 +93,6 @@
93 93  * Tracking: max: 38mA
94 94  
95 95  
96 -
97 97  == 1.3  Features ==
98 98  
99 99  
... ... @@ -113,7 +113,6 @@
113 113  * Datalog
114 114  
115 115  
116 -
117 117  == 1.4  Applications ==
118 118  
119 119  
... ... @@ -121,8 +121,8 @@
121 121  * Human tracking
122 122  
123 123  
127 += 2.1 Use TrackerD =
124 124  
125 -= 2.  Use TrackerD =
126 126  
127 127  == 2.1 How it works? ==
128 128  
... ... @@ -130,6 +130,7 @@
130 130  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.
131 131  
132 132  
136 +
133 133  == 2.2 Quick guide to connect to LoRaWAN server ==
134 134  
135 135  
... ... @@ -136,7 +136,7 @@
136 136  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 -[[image:1664501652064-326.png||_mstalt="293306"]]
143 +[[image:1664501652064-326.png]]
140 140  
141 141  
142 142  
... ... @@ -148,7 +148,7 @@
148 148  Each TrackerD is shipped with a sticker with the default device EUI as below:
149 149  
150 150  
151 -[[image:1664501677253-891.png||_mstalt="296569"]]
155 +[[image:1664501677253-891.png]]
152 152  
153 153  
154 154  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -157,14 +157,14 @@
157 157  **__Add APP EUI in the application:__**
158 158  
159 159  
160 -[[image:1664501711466-918.png||_mstalt="295828"]]
164 +[[image:1664501711466-918.png]]
161 161  
162 162  
163 163  
164 -[[image:1664501721248-725.png||_mstalt="294450"]]
168 +[[image:1664501721248-725.png]]
165 165  
166 166  
167 -[[image:1664501734705-405.png||_mstalt="293306"]]
171 +[[image:1664501734705-405.png]]
168 168  
169 169  
170 170  
... ... @@ -171,143 +171,53 @@
171 171  **__Add APP KEY and DEV EUI:__**
172 172  
173 173  
174 -[[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"]]
178 +[[image:1664501784668-703.png]]
175 175  
176 176  
177 177  
178 -(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179 179  
180 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
183 +(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
181 181  
182 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 183  
184 -
185 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.
186 186  
187 187  
188 -== 2.3  Positioning Mode(SMOD) ==
189 += 2.3 Positioning Mode(SMOD) =
189 189  
191 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
192 +* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
193 +* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
190 190  
191 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
195 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
192 192  
193 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
194 -* (% style="color:#037691" %)**BLE or WiFi ONLY:            **(%%)** **Only obtain iBeacon info via BLE and uplink  or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking.
195 -* (% 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.
196 196  
197 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
198 198  
199 +== 2.3 Uplink Payload ==
199 199  
200 -== 2.4  Uplink Payload ==
201 201  
202 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
202 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
203 203  
204 204  
205 -Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
206 206  
207 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
206 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
208 208  
209 209  
210 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
211 -|=(% 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
212 -|=(% 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
209 +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. )
213 213  
214 -[[image:1665301570342-765.png||_mstalt="294580"]]
215 215  
216 -
217 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
218 -
219 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
220 -
221 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
222 -
223 -(% style="color:#037691" %)**Frequency Band**:
224 -
225 -*0x01: EU868
226 -
227 -*0x02: US915
228 -
229 -*0x03: IN865
230 -
231 -*0x04: AU915
232 -
233 -*0x05: KZ865
234 -
235 -*0x06: RU864
236 -
237 -*0x07: AS923
238 -
239 -*0x08: AS923-1
240 -
241 -*0x09: AS923-2
242 -
243 -*0x0a: AS923-3
244 -
245 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
246 -
247 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
248 -
249 -
250 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
251 -
252 -Use can also get the Device Status uplink through the downlink command:
253 -
254 -
255 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
256 -
257 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
258 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
259 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
260 -
261 -(% style="color:blue" %)** SMOD：**
262 -
263 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
264 -
265 -(% style="color:red" %)** 2 :** (%%) BLE ONLY
266 -
267 -(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
268 -
269 -
270 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
271 -
272 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
273 -
274 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
275 -
276 -
277 -(% style="color:blue" %)** BLE_Settings:**
278 -
279 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
280 -
281 -(% _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)(%%)  
282 -
283 -
284 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
285 -
286 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
287 -|=(% 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
288 -|=(% 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"]]
289 -
290 -
291 -
292 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
293 -
294 -
295 -Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
296 -
297 -
298 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
299 -|=(% scope="row" style="width: 60px;" %)(((
212 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
213 +|=(% scope="row" style="width: 50px;" %)(((
300 300  **Size(bytes)**
301 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
302 -2
303 -)))|(% style="width:30px" %)(((
304 -2
215 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
216 +2(optional)
217 +)))|(% style="width:87px" %)(((
218 +2(optional)
305 305  )))
306 306  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
307 307  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
308 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
222 +)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
309 309  
310 -[[image:1665301636888-168.png||_mstalt="298012"]]
224 +[[image:1664501958445-288.png]]
311 311  
312 312  
313 313  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -318,9 +318,9 @@
318 318  
319 319  ==== (% style="color:blue" %)**FLAG:**(%%) ====
320 320  
321 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
322 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
323 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
235 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
236 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
237 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 
324 324  
325 325  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
326 326  
... ... @@ -330,33 +330,37 @@
330 330  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
331 331  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
332 332  
247 +
333 333  (% style="color:red" %)**Important note:**
334 334  
335 335  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.
336 336  
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:
252 +2.  In firmware version v1.5, Roll & Pitch is disabled by default.
338 338  
254 +3.  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:
339 339  
340 -[[image:1664502116362-706.png||_mstalt="293306"]]
341 341  
257 +[[image:1664502116362-706.png]]
342 342  
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"]]
346 346  
261 +4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
347 347  
263 +[[image:1664502166010-515.png]]
348 348  
265 +
266 +
349 349  ==== (% style="color:blue" %)**Alarm:**(%%) ====
350 350  
351 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
269 +Example:  0x4B & 0x40 >> 6 = 0x01
352 352  
353 353  
354 354  ==== (% style="color:blue" %)**BAT:**(%%) ====
355 355  
356 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
274 +Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
357 357  
358 358  (((
359 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
277 +The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
360 360  )))
361 361  
362 362  * > 4.0v :  80% ~~ 100%
... ... @@ -366,34 +366,17 @@
366 366  * < 3.39v:  0~~20%
367 367  
368 368  
369 -
370 -==== (% style="color:blue" %)**MOD:**(%%) ====
371 -
372 -**Example: ** (0x60>>6) & 0x3f =1
373 -
374 -**Set the format of GPS data uplink link：**
375 -
376 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
377 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
378 -
379 -
380 -**Set the format of BLE data uplink link：**
381 -
382 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
383 -
384 -
385 385  ==== (% style="color:blue" %)**LON:**(%%) ====
386 386  
387 -**Example:** (0x60>>5) & 0x01=1.
388 388  
389 389  Enable/Disable LED activity for uplink
390 390  
391 391  (((
392 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
293 +0x00:  Disable LED indicator.
393 393  )))
394 394  
395 395  (((
396 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
297 +0x01:  Enable LED indicator (Default Value)
397 397  )))
398 398  
399 399  
... ... @@ -407,55 +407,16 @@
407 407  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
408 408  
409 409  
410 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
411 411  
312 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
412 412  
413 -The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
414 414  
415 415  
416 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
417 -|=(% scope="row" style="width: 60px;" %)(((
418 -**Size(bytes)**
419 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
420 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
421 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
422 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
316 +=== 2.3.4 BLE positioning Payload(Fport2) ===
423 423  
424 -(% class="wikigeneratedid" %)
425 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 426  
319 +Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
427 427  
428 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
429 -
430 -
431 -Set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-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.
432 -
433 -
434 -(% style="color:red" %)**Note for this mode:**
435 -
436 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
437 -* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=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.
438 -* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
439 -
440 -The payload is 15 bytes, as below.
441 -
442 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
443 -|=(% scope="row" %)(((
444 -**Size(bytes)**
445 -)))|4|4|2|1|1|1|1|1
446 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
447 -
448 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
449 -
450 -
451 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
452 -
453 -
454 -TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink.
455 -
456 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
457 -
458 -
459 459  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
460 460  |=(% scope="row" style="width: 60px;" %)(((
461 461  **Size(bytes)**
... ... @@ -472,104 +472,73 @@
472 472  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
473 473  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
474 474  
475 -[[image:1664502425687-834.png||_mstalt="296738"]]
337 +[[image:1664502425687-834.png]]
476 476  
477 477  
478 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
340 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
479 479  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
480 480  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
481 481  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
482 -* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
344 +* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
483 483  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
484 484  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
485 485  
486 486  
349 +=== 2.3.5 Add Payload format in TTN V3 ===
487 487  
488 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
489 489  
352 +In TTN V3, use can add a custom payload so it shows friendly.
490 490  
491 -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.
492 -
493 -
494 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
495 -|=(% scope="row" style="width: 60px;" %)(((
496 -**Size(bytes)**
497 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
498 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
499 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
500 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
501 -
502 -(% class="wikigeneratedid" %)
503 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 -
505 -
506 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
507 -* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
508 -* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
509 -
510 -
511 -
512 -=== 2.4.7  Add Payload format in TTN V3 ===
513 -
514 -
515 -In TTN V3, user can add a custom payload so it shows friendly.
516 -
517 517  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
518 518  
519 519  
520 -[[image:1664502649601-895.png||_mstalt="296985"]]
357 +[[image:1664502649601-895.png]]
521 521  
522 522  
360 +Add the decoder from this link:
523 523  
524 -Add the decoder from this link: 
525 525  
526 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
527 -
528 528  Save the change the uplink message will be parsed. As below:
529 529  
530 -[[image:1664502676891-606.png||_mstalt="296673"]]
365 +[[image:1664502676891-606.png]]
531 531  
532 532  
533 -== 2.5 Integrate with Datacake ==
534 534  
369 +== 2.4 Integrate with Datacake ==
535 535  
371 +
372 +(((
536 536  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.
374 +)))
537 537  
376 +(((
538 538  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]]
378 +)))
539 539  
540 540  
541 -[[image:1664502695771-538.png||_mstalt="297349"]]
381 +[[image:1664502695771-538.png]]
542 542  
543 543  
544 -== 2.6 Integrate with Tago ==
545 545  
385 +== 2.5 Integrate with Tago ==
546 546  
547 -After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot.
548 548  
388 +(((
389 +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.
390 +)))
391 +
392 +(((
549 549  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]]
394 +)))
550 550  
551 551  
552 -[[image:1664502715371-321.png||_mstalt="292162"]]
397 +[[image:1664502715371-321.png]]
553 553  
554 554  
555 -== 2.7  Datalog Feature ==
556 556  
401 +== 2.6 Alarm Mode ==
557 557  
558 -total 273 entries,by default,
559 559  
560 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 -
562 -Example use case.
563 -
564 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 -
566 -
567 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 -
569 -
570 -== 2.8 Alarm Mode ==
571 -
572 -
573 573  (((
574 574  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
575 575  )))
... ... @@ -576,15 +576,15 @@
576 576  
577 577  
578 578  (((
579 -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 exits alert mode.
410 +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.
580 580  )))
581 581  
582 582  
583 583  (((
584 -**Two ways to exit alarm mode:**
415 +Two ways to exit alarm mode:
585 585  )))
586 586  
587 -* Server sends a downlink command to exit.
418 +* Server send a downlink command to exit.
588 588  * User fast press the RED button 10 times.
589 589  
590 590  (((
... ... @@ -592,27 +592,21 @@
592 592  )))
593 593  
594 594  
595 -== 2.9 Transport Mode ==
596 596  
427 +== 2.7 Sports Mode ==
597 597  
598 -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.
599 599  
600 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
601 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
602 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
603 603  
431 +== 2.8 LED Status ==
604 604  
605 605  
606 -== 2.10 LED Status ==
607 -
608 -
609 -(% border="1.5" style="background-color:#ffffcc; width:500px" %)
434 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
610 610  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
611 611  |(% 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
612 612  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
613 613  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
614 614  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
615 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
440 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
616 616  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
617 617  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
618 618  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -621,13 +621,12 @@
621 621  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
622 622  
623 623  
449 +== 2.9 Button Function ==
624 624  
625 -== 2.11 Button Function ==
626 626  
627 -
628 628  (% style="color:blue" %)**RESET button:**
629 629  
630 -[[image:1664502835802-546.png||_mstalt="295061"]]
454 +[[image:1664502835802-546.png]]
631 631  
632 632  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
633 633  
... ... @@ -634,20 +634,19 @@
634 634  
635 635  (% style="color:red" %)**RED button:**
636 636  
637 -[[image:1664502854406-763.png||_mstalt="295568"]]
461 +[[image:1664502854406-763.png]]
638 638  
639 639  
640 -(% border="1" style="background-color:#ffffcc; width:510px" %)
641 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
642 -|(% 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.8AlarmMode"]]
464 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
465 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
466 +|(% 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"]]
643 643  |(% 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
644 644  |(% 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.
645 645  
646 646  
471 +== 2.10 USB Port Function ==
647 647  
648 -== 2.12 USB Port Function ==
649 649  
650 -
651 651  The USB interface of TrackerD has below functions:
652 652  
653 653  * Power on the device
... ... @@ -656,7 +656,6 @@
656 656  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
657 657  
658 658  
659 -
660 660  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
661 661  
662 662  
... ... @@ -665,6 +665,7 @@
665 665  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
666 666  
667 667  
490 +
668 668  == 3.1 Access AT Command ==
669 669  
670 670  
... ... @@ -671,23 +671,27 @@
671 671  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.
672 672  
673 673  
674 -[[image:1664502999401-486.png||_mstalt="296985"]]
497 +[[image:1664502999401-486.png]]
675 675  
676 676  
677 677  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:
678 678  
679 679  
680 -[[image:1664503022490-662.png||_mstalt="293332"]]
503 +[[image:1664503022490-662.png]]
681 681  
682 682  
683 -[[image:1664503035713-500.png||_mstalt="291096"]]
684 684  
507 +[[image:1664503035713-500.png]]
685 685  
686 -[[image:1664503047675-651.png||_mstalt="295386"]]
687 687  
688 688  
511 +[[image:1664503047675-651.png]]
512 +
513 +
514 +
689 689  == 3.2 Command Set ==
690 690  
517 +
691 691  === 3.2.1 Set Transmit Interval ===
692 692  
693 693  
... ... @@ -705,6 +705,7 @@
705 705  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
706 706  
707 707  
535 +
708 708  === 3.2.2 Set Alarm Packet transmission interval ===
709 709  
710 710  
... ... @@ -722,23 +722,25 @@
722 722  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
723 723  
724 724  
725 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
726 726  
554 +=== 3.2.3 Set Sports Mode Packet transmission interval ===
727 727  
728 -Set Transport Mode packet transmit interval
729 729  
557 +Set sports packet transmit interval
558 +
730 730  * (% style="color:blue" %)**AT Command:**
731 731  
732 732  (% style="color:#037691" %)**AT+MTDC=xx. **
733 733  
734 -Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
563 +Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
735 735  
736 736  
737 737  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
738 738  
739 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
568 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
740 740  
741 741  
571 +
742 742  === 3.2.4 Exit Alarm ===
743 743  
744 744  
... ... @@ -751,6 +751,7 @@
751 751  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
752 752  
753 753  
584 +
754 754  === 3.2.5 Disable/Enable LED flash ===
755 755  
756 756  
... ... @@ -768,69 +768,60 @@
768 768  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
769 769  
770 770  
771 -=== 3.2.6 Disable/Enable Transport Mode ===
772 772  
603 +=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
773 773  
774 -Users can use this feature to enable/disable Transport Mode.
775 775  
606 +User can use this feature to check and set thread hole of movement detect
607 +
776 776  * (% style="color:blue" %)**AT Command:**
777 777  
778 778  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
779 779  
780 -Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
612 +Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
781 781  
782 782  
783 783  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
784 784  
785 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
617 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
786 786  
787 787  
620 +
788 788  === 3.2.7 Set Positioning Mode ===
789 789  
790 790  
791 -SMOD define how TrackerD scan and uplink data:
624 +SMOD define the how TrackerD scan and uplink date.
792 792  
626 +GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
793 793  
794 -* (% style="color:blue" %)**AT Command:**
628 +BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
795 795  
796 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
630 +GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
797 797  
798 -(% style="color:#037691" %)** aa:**
632 +运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
799 799  
800 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
801 801  
802 -* (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
803 803  
804 -* (% style="color:red" %)**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.
636 +* (% style="color:blue" %)**AT Command:**
805 805  
806 -(% style="color:#037691" %)**bb:**
638 +(% style="color:#037691" %)**AT+SMOD=xx. **
807 807  
808 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
809 809  
810 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
641 + **Example:**
811 811  
812 -(% style="color:#037691" %)**cc:   **
643 + AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
813 813  
814 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
815 -
816 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
645 + AT+ SMOD =1,1    **~-~->**  GPS +BAT State
817 817  
818 -(% style="color:blue" %)**Example:**
647 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
819 819  
820 - AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
821 821  
822 - AT+SMOD=1,1,0 ~-~->  GPS +BAT State
823 -
824 - AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
825 -
826 - AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
827 -
828 -
829 829  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
830 830  
831 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
652 +(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
832 832  
833 833  
655 +
834 834  === 3.2.8 Set MAX GPS position time ===
835 835  
836 836  
... ... @@ -837,7 +837,7 @@
837 837  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.
838 838  
839 839  
840 -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.
662 +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.
841 841  
842 842  
843 843  * (% style="color:blue" %)**AT Command:**
... ... @@ -844,7 +844,7 @@
844 844  
845 845  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
846 846  
847 -**Example:**  AT+FTIME=150
669 +Example:  AT+FTIME=150
848 848  
849 849  
850 850  * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
... ... @@ -852,9 +852,10 @@
852 852  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
853 853  
854 854  
855 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
856 856  
678 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
857 857  
680 +
858 858  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.
859 859  
860 860  
... ... @@ -876,129 +876,26 @@
876 876  
877 877  
878 878  
879 -=== 3.2.10 Disable/Enable the confirmation mode ===
702 +Disable/Enable the confirmation mode
880 880  
881 -
882 882  * (% style="color:blue" %)**AT Command:**
883 883  
884 -(% style="color:#037691" %)**AT+CFM=xx**
706 +(% style="color:#037691" %)**AT+CFM=xx. **
885 885  
886 886  
887 887  **~ Example:**
888 888  
889 - AT+CFM=0    **~-~->   ** Disable confirmation
711 + AT+ CFM=0    **~-~->   ** Disable confirmation
890 890  
891 - AT+CFM=1    **~-~->  ** Enable confirmation
713 + AT+ CFM=1    **~-~->  ** Enable confirmation
892 892  
893 893  
894 894  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
895 895  
896 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
718 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
897 897  
898 898  
899 -=== 3.2.11  Auto Send None-ACK messages ===
900 900  
901 -
902 -TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
903 -
904 -
905 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
906 -
907 -The default factory setting is 0.
908 -
909 -
910 -**Command Example Function Response:**
911 -
912 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
913 -
914 -
915 -* (% style="color:blue" %)**Downlink Command: 0x34**
916 -
917 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
918 -
919 -
920 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
921 -
922 -
923 -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.
924 -
925 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
926 -
927 -(% style="color:blue" %)**AT Command:**
928 -
929 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
930 -
931 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
932 -
933 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
934 -
935 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
936 -
937 -
938 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
939 -
940 -
941 -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.
942 -
943 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
944 -
945 -(% style="color:blue" %)**AT Command:**
946 -
947 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
948 -
949 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
950 -
951 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
952 -
953 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
954 -
955 -
956 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
957 -
958 -
959 -Users can use this feature to enable/disable Information printing.
960 -
961 -(% style="color:blue" %)**AT Command:**
962 -
963 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
964 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
965 -
966 -
967 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
968 -
969 -
970 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
971 -
972 -(% style="color:blue" %)**AT Command:**
973 -
974 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
975 -
976 -
977 -(% style="color:blue" %)**Downlink Payload:0X24**
978 -
979 -Example: 0x24 01 ~/~/ Same as AT+CHE=1
980 -
981 -
982 -=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
983 -
984 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
985 -
986 -(% style="color:blue" %)**AT Command:**
987 -
988 -(% style="color:#037691" %)**AT+PT=xx**
989 -
990 - Example:
991 -
992 - AT+PT=14    ~-~->    Set to detect car motion.
993 -
994 - AT+PT=41   ~-~->    set to detect walk motion.
995 -
996 -
997 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
998 -0xB4 14          ~/~/  Same as AT+PT=14
999 -
1000 -
1001 -
1002 1002  = 4. Setting for Different Scenarios =
1003 1003  
1004 1004  
... ... @@ -1005,6 +1005,7 @@
1005 1005  
1006 1006  = 5. Upload Firmware =
1007 1007  
728 +
1008 1008  == 5.1 Firmware Change Log ==
1009 1009  
1010 1010  
... ... @@ -1011,6 +1011,7 @@
1011 1011  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1012 1012  
1013 1013  
735 +
1014 1014  == 5.2 How to upgrade firmware ==
1015 1015  
1016 1016  
... ... @@ -1031,39 +1031,40 @@
1031 1031  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1032 1032  
1033 1033  
1034 -[[image:1664503563660-578.png||_mstalt="296777"]]
756 +[[image:1664503563660-578.png]]
1035 1035  
1036 1036  
1037 -[[image:1664503574618-659.png||_mstalt="297986"]]
759 +[[image:1664503574618-659.png]]
1038 1038  
1039 1039  
1040 -
1041 1041  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1042 1042  
1043 -[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
764 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1044 1044  
1045 1045  
1046 -**Users need to use below files:**
767 +Users need to use below files:
1047 1047  
1048 1048  boot_app0.bin @0e000
1049 1049  
1050 -US915.bin @ 0x10000(Select the bin file of the frequency band you need)
771 +ESP_LORA-eeprom-class.bin @ 0x10000
1051 1051  
1052 1052  
1053 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
774 +[[image:1664503593459-435.png]]
1054 1054  
1055 1055  
1056 1056  
1057 1057  After upgrade finish, it will show finish as below:
1058 1058  
1059 -[[image:image-20221118105402-4.png||_mstalt="427986"]]
780 +[[image:1664503611848-385.png]]
1060 1060  
1061 1061  
1062 1062  
1063 1063  = 6. Developer Guide =
1064 1064  
786 +
1065 1065  == 6.1 Compile Source Code ==
1066 1066  
789 +
1067 1067  === 6.1.1 Set up ARDUINO compile environment ===
1068 1068  
1069 1069  
... ... @@ -1072,57 +1072,48 @@
1072 1072  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]]
1073 1073  
1074 1074  
1075 -[[image:1664503635019-941.png||_mstalt="294658"]]
798 +[[image:1664503635019-941.png]]
1076 1076  
1077 1077  
1078 -
1079 1079  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1080 1080  
1081 -[[image:1664503715811-892.png||_mstalt="295698"]]
803 +[[image:1664503715811-892.png]]
1082 1082  
1083 1083  
1084 -(% 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.
1085 1085  
1086 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1087 -
1088 -**~ Figure1**
1089 -
1090 -
1091 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1092 -
1093 - **Figure2**
1094 -
1095 -
1096 1096  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1097 1097  
1098 1098  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1099 1099  
1100 1100  
1101 -[[image:1664503752288-974.png||_mstalt="298194"]]
812 +[[image:1664503752288-974.png]]
1102 1102  
1103 1103  
815 +
1104 1104  == 6.2 Source Code ==
1105 1105  
1106 1106  
1107 1107  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1108 1108  
1109 -[[image:1664503794261-827.png||_mstalt="296387"]]
821 +[[image:1664503794261-827.png]]
1110 1110  
1111 1111  
1112 1112  
1113 1113  * (% style="color:blue" %)**Click to upload**
1114 1114  
1115 -[[image:1664503808294-336.png||_mstalt="295711"]]
827 +[[image:1664503808294-336.png]]
1116 1116  
1117 1117  
1118 1118  
1119 1119  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1120 1120  
1121 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
833 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1122 1122  
1123 1123  
836 +
1124 1124  = 7.  FAQ =
1125 1125  
839 +
1126 1126  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1127 1127  
1128 1128  
... ... @@ -1129,10 +1129,11 @@
1129 1129  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1130 1130  
1131 1131  
846 +
1132 1132  == 7.2 What is the pin mapping for the USB program cable? ==
1133 1133  
1134 1134  
1135 -[[image:1664499635206-262.png||_mstalt="295360"]]
850 +[[image:1664499635206-262.png]]
1136 1136  
1137 1137  
1138 1138  
... ... @@ -1149,261 +1149,48 @@
1149 1149  
1150 1150  
1151 1151  
1152 -== 7.3 Notes on using different serial port tools for TrackerD ==
867 += 8.  Order Info =
1153 1153  
1154 -=== 7.3.1  Serial port utility ===
1155 1155  
1156 -
1157 -Serial port utility requires you to automatically add data streams.
1158 -
1159 -Need to adjust the data stream to RTS/CTS on physical restart.
1160 -
1161 -(% class="wikigeneratedid" %)
1162 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1163 -
1164 -
1165 -
1166 -When using AT commands, the data flow needs to be adjusted to XON/XOFF
1167 -
1168 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1169 -
1170 -
1171 -=== 7.3.2  SecureCRT ===
1172 -
1173 -
1174 -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.
1175 -
1176 -
1177 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1178 -
1179 -
1180 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1181 -
1182 -
1183 -=== 7.3.3  PUTTY ===
1184 -
1185 -
1186 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1187 -
1188 -
1189 -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.
1190 -
1191 -
1192 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1193 -
1194 -
1195 -== 7.4 How to modify source code to compile different frequency band bin file? ==
1196 -
1197 -
1198 -(% class="box infomessage" %)
1199 -(((
1200 -(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1201 -See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1202 -)))
1203 -
1204 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1205 -
1206 -
1207 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1208 -
1209 -
1210 -
1211 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1212 -
1213 -
1214 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1215 -
1216 -
1217 -
1218 -**3. Compile the AS923_JP band, please refer to the intention shown**
1219 -
1220 -
1221 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1222 -
1223 -
1224 -
1225 -**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.**
1226 -
1227 -
1228 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1229 -
1230 -
1231 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1232 -
1233 -
1234 -= 8  Trouble Shooting =
1235 -
1236 -== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1237 -
1238 -
1239 -(((
1240 -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
1241 -)))
1242 -
1243 -
1244 -== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1245 -
1246 -
1247 -(((
1248 -ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1249 -)))
1250 -
1251 -
1252 -== 8.3  Problem after Upgrading Firmware ==
1253 -
1254 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1255 -
1256 -
1257 -**Error Output**
1258 -
1259 -
1260 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1261 -
1262 -
1263 -(((
1264 -Some partition is missed during upgrade, please upgrade below four files as example:
1265 -
1266 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1267 -)))
1268 -
1269 -
1270 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1271 -
1272 -
1273 -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
1274 -
1275 -
1276 -=== 8.3.3 "flash read err" after upgrade firmware ===
1277 -
1278 -
1279 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1280 -
1281 -
1282 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1283 -
1284 -
1285 -User need to upgrade again with below four files to solve this issue.
1286 -
1287 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1288 -
1289 - **Figure 2**
1290 -
1291 -
1292 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1293 -
1294 -
1295 -User might erase the entire flash include keys and default settings which cause this issue.
1296 -
1297 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1298 -
1299 -
1300 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1301 -
1302 -
1303 -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.
1304 -
1305 -After AT+FDR. please set
1306 -
1307 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1308 -
1309 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1310 -
1311 -**Example:**
1312 -
1313 -AT+PDOP=7.00
1314 -
1315 -AT+FTIME=180
1316 -
1317 -AT+DEUI=70B3D57ED0053981  
1318 -
1319 -AT+APPEUI=D23345667BCBCCAF
1320 -
1321 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1322 -
1323 -AT+DADDR=260b4dce    ( no need for OTAA)
1324 -
1325 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1326 -
1327 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1328 -
1329 -
1330 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1331 -
1332 -
1333 -Please download version 1.4.2 again
1334 -
1335 -
1336 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1337 -
1338 -
1339 -1） Make Sure the device is in Open Area where can see the sky.
1340 -
1341 -2)  Set PDOP to a higher value.
1342 -
1343 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1344 -
1345 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1346 -
1347 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1348 -
1349 -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
1350 -
1351 -
1352 -= 9.  Order Info =
1353 -
1354 -
1355 1355  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1356 1356  
1357 1357  (% style="color:blue" %)**XXX**(%%): The default frequency band
1358 1358  
1359 1359  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1360 -
1361 1361  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1362 -
1363 1363  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1364 -
1365 1365  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1366 -
1367 1367  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1368 -
1369 1369  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1370 -
1371 1371  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1372 1372  
1373 1373  
883 += 9.  Packing Info =
1374 1374  
1375 -= 10.  Packing Info =
1376 1376  
1377 -
1378 1378  (% style="color:#037691" %)**Package Includes**:
1379 1379  
1380 1380  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1381 -
1382 1382  * USB recharge & program cable x 1
1383 1383  
1384 1384  (% style="color:#037691" %)**Dimensions and Weight**:
1385 1385  
1386 -* Device Size: 85 x 48 x 15 mm
1387 -
893 +* Device Size: 85 x 48 x 15 cm
1388 1388  * Weight: 50g
1389 1389  
1390 1390  
897 += 10. Support =
1391 1391  
1392 -= 11. Support =
1393 1393  
1394 -
1395 1395  * 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.
1396 -
1397 1397  * 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]].
1398 1398  
1399 1399  
904 += 11.  Reference =
1400 1400  
1401 -= 12.  Reference =
1402 1402  
1403 -
1404 1404  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1405 -
1406 1406  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1407 -
1408 1408  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1409 -)))
910 +
911 +
1665301570342-765.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1665301636888-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.6 KB
Content
1665301687277-443.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1665301786397-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1667288597595-714.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20221009160220-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.4 KB
Content
image-20221009160309-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -57.2 KB
Content
image-20221009234629-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -222.9 KB
Content
image-20221009234703-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -136.4 KB
Content
image-20221024105643-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.3 KB
Content
image-20221024105643-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.5 KB
Content
image-20221102140621-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content
image-20221102140638-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -40.8 KB
Content
image-20221102140704-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -15.5 KB
Content
image-20221102140712-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -73.2 KB
Content
image-20221102140748-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20221102140801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -21.0 KB
Content
image-20221107145243-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -107.3 KB
Content
image-20221116111844-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.8 KB
Content
image-20221116111844-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.6 KB
Content
image-20221116111844-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -37.0 KB
Content
image-20221116111844-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -96.8 KB
Content
image-20221116111844-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -78.0 KB
Content
image-20221118104359-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -38.0 KB
Content
image-20221118105220-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -40.2 KB
Content
image-20221118105249-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -40.2 KB
Content
image-20221118105402-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -43.7 KB
Content
image-20221122100004-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -18.0 KB
Content
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