Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 215.1
edited by Bei Jinggeng
on 2023/10/23 13:35
Change comment: There is no comment for this version
To version 154.1
edited by Edwin Chen
on 2022/11/24 09:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Edwin
Content
... ... @@ -12,7 +12,6 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
18 18  == 1.1  What is TrackerD ==
... ... @@ -32,12 +32,15 @@
32 32  (((
33 33  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 34  )))
34 +)))
35 35  
36 36  (((
37 37  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
38 +
39 +
38 38  )))
39 39  
40 -[[image:image-20230213110119-1.png||height="382" width="834"]]
42 +[[image:1664499921684-770.png||_mstalt="298194"]]
41 41  
42 42  
43 43  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
... ... @@ -93,10 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -(% style="display:none" %)
97 -
98 -
99 -
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,10 +115,6 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
118 -(% style="display:none" %)
119 -
120 -
121 -
122 122  == 1.4  Applications ==
123 123  
124 124  
... ... @@ -125,10 +125,6 @@
125 125  * Logistics and Supply Chain Management
126 126  * Human tracking
127 127  
128 -(% style="display:none" %)
129 -
130 -
131 -
132 132  = 2.  Use TrackerD =
133 133  
134 134  == 2.1 How it works? ==
... ... @@ -143,7 +143,7 @@
143 143  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. 
144 144  
145 145  
146 -[[image:image-20230213110214-2.png||height="388" width="847"]]
136 +[[image:1664501652064-326.png||_mstalt="293306"]]
147 147  
148 148  
149 149  
... ... @@ -155,7 +155,7 @@
155 155  Each TrackerD is shipped with a sticker with the default device EUI as below:
156 156  
157 157  
158 -[[image:image-20230426085815-1.png||height="259" width="558"]]
148 +[[image:1664501677253-891.png||_mstalt="296569"]]
159 159  
160 160  
161 161  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -209,14 +209,15 @@
209 209  === 2.4.1 Uplink FPORT~=5, Device Status ===
210 210  
211 211  
212 -Uplink the device configures with (% style="color:blue" %)**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.
202 +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.
213 213  
214 -Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
204 +Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
215 215  
216 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
217 -|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1
218 -|(% 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
219 219  
207 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
208 +|=(% 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
209 +|=(% 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
210 +
220 220  [[image:1665301570342-765.png||_mstalt="294580"]]
221 221  
222 222  
... ... @@ -228,30 +228,31 @@
228 228  
229 229  (% style="color:#037691" %)**Frequency Band**:
230 230  
231 -0x01: EU868
222 +*0x01: EU868
232 232  
233 -0x02: US915
224 +*0x02: US915
234 234  
235 -0x03: IN865
226 +*0x03: IN865
236 236  
237 -0x04: AU915
228 +*0x04: AU915
238 238  
239 -0x05: KZ865
230 +*0x05: KZ865
240 240  
241 -0x06: RU864
232 +*0x06: RU864
242 242  
243 -0x07: AS923
234 +*0x07: AS923
244 244  
245 -0x08: AS923-1
236 +*0x08: AS923-1
246 246  
247 -0x09: AS923-2
238 +*0x09: AS923-2
248 248  
249 -0x0a: AS923-3
240 +*0x0a: AS923-3
250 250  
251 -(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
242 +Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
252 252  
253 253  (% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
254 254  
246 +
255 255  (% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
256 256  
257 257  Use can also get the Device Status uplink through the downlink command:
... ... @@ -259,52 +259,54 @@
259 259  
260 260  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
261 261  
262 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
263 -|(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
264 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
254 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
255 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
256 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
265 265  
266 -(% style="color:blue" %)**SMOD：**
258 +(% style="color:blue" %)** SMOD：**
267 267  
268 -(% style="color:red" %)**1 :** (%%) GPS ONLY
260 +(% style="color:red" %)** 1 :** (%%) GPS ONLY
269 269  
270 -(% style="color:red" %)**2 :** (%%) BLE ONLY
262 +(% style="color:red" %)** 2 :** (%%) BLE ONLY
271 271  
272 -(% style="color:red" %)**3 :**  (%%) GPS/BLE Hybrid
264 +(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
273 273  
274 274  
275 -(% style="color:blue" %)**GPS_MOD: Define how to send GPS payload**
267 +(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
276 276  
277 -(% style="color:red" %)**0 : ** (%%) Enable uploading on-board Temperature and humidity values
269 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
278 278  
279 -(% style="color:red" %)**1 :** (%%) Disable uploading on-board Temperature and humidity values
271 +(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
280 280  
281 281  
282 -(% style="color:blue" %)**BLE_Settings:**
274 +(% style="color:blue" %)** BLE_Settings:**
283 283  
284 -(% style="color:red" %)**1: ** (%%) BLE Positioning with Strongest iBeacon
276 +(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
285 285  
286 -(% _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)(%%)  
278 +(% _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)(%%)  
287 287  
288 288  
289 289  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
290 290  
291 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
292 -|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:88px" %)1 Bit|(% style="width:50px" %)1 Bit|(% style="width:128px" %)1 Bit
293 -|(% style="width:75px" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
283 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
284 +|=(% 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
285 +|=(% 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"]]
294 294  
295 -(% style="display:none" %)
296 -
297 -
298 -
299 299  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
300 300  
301 301  
302 -Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
290 +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,
303 303  
304 304  
305 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)
306 -|(% style="width:60px" %)**Size(bytes)**|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)2|(% style="width:30px" %)2
307 -|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
293 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
294 +|=(% scope="row" style="width: 60px;" %)(((
295 +**Size(bytes)**
296 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
297 +2
298 +)))|(% style="width:30px" %)(((
299 +2
300 +)))
301 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
308 308  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309 309  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
310 310  
... ... @@ -313,18 +313,15 @@
313 313  
314 314  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
315 315  
316 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)
317 -|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits
318 -|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]] 
310 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
311 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
312 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
319 319  
320 -(% style="display:none" %)
321 -
322 -
323 323  ==== (% style="color:blue" %)**FLAG:**(%%) ====
324 324  
325 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
326 -|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit
327 -|(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
316 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
317 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
318 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
328 328  
329 329  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
330 330  
... ... @@ -369,9 +369,6 @@
369 369  * 3.40v ~~ 3.69v:  20% ~~ 40%
370 370  * < 3.39v:  0~~20%
371 371  
372 -(% style="display:none" %) (%%)
373 -
374 -
375 375  ==== (% style="color:blue" %)**MOD:**(%%) ====
376 376  
377 377  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -415,12 +415,14 @@
415 415  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
416 416  
417 417  
418 -The default uplink payload includes total 11 bytes ((% style="color:blue" %)**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)
406 +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)
419 419  
420 420  
421 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
422 -|(% style="width:60px" %)**Size(bytes)**|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1
423 -|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
409 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
410 +|=(% scope="row" style="width: 60px;" %)(((
411 +**Size(bytes)**
412 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
413 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
424 424  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
425 425  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
426 426  
... ... @@ -431,7 +431,7 @@
431 431  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
432 432  
433 433  
434 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
424 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
435 435  
436 436  
437 437  (% style="color:red" %)**Note for this mode:**
... ... @@ -442,9 +442,11 @@
442 442  
443 443  The payload is 15 bytes, as below.
444 444  
445 -(% border="1" style="background-color:#f2f2f2; width:500px" %)
446 -|**Size(bytes)**|4|4|2|1|1|1|1|1
447 -|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
435 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
436 +|=(% scope="row" %)(((
437 +**Size(bytes)**
438 +)))|4|4|2|1|1|1|1|1
439 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
448 448  
449 449  [[image:image-20221009160309-2.png||_mstalt="429312"]]
450 450  
... ... @@ -457,9 +457,11 @@
457 457  User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
458 458  
459 459  
460 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
461 -|(% style="width:60px" %)**Size(bytes)**|(% 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
462 -|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
452 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
453 +|=(% scope="row" style="width: 60px;" %)(((
454 +**Size(bytes)**
455 +)))|(% 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
456 +|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
463 463  iBeacon MAJOR
464 464  )))|(% style="width:63px" %)(((
465 465  iBeacon MINOR
... ... @@ -482,86 +482,44 @@
482 482  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
483 483  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
484 484  
485 -(% style="display:none" %) (%%)
479 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
486 486  
487 487  
488 -=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
489 -
490 -
491 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
492 -
493 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
494 -|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
495 -|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
496 -
497 - [[image:image-20230302145315-1.png]]
498 -
499 -**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
500 -
501 -**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
502 -
503 -**mod** = bytes[2] & 0xC0;
504 -
505 -**Lon**=(bytes[2] & 0x20)
506 -
507 -
508 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
509 -
510 -
511 511  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.
512 512  
513 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
514 -|(% style="width:65px" %)(((
484 +
485 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
486 +|=(% scope="row" style="width: 60px;" %)(((
515 515  **Size(bytes)**
516 -)))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
517 -|(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
488 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
489 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
518 518  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
519 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
491 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
520 520  
521 521  (% class="wikigeneratedid" %)
522 522  [[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
523 523  
496 +
524 524  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
525 525  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
526 526  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
527 527  
528 -(% style="display:none" %) (%%)
501 +=== 2.4.7  Add Payload format in TTN V3 ===
529 529  
530 -=== 2.4.8  Uplink FPORT~=9, BLE Positioning with Multiple iBeacon（Since firmware 1.4.7） ===
531 531  
532 -TrackerD supports BLE scanning for indoor positioning. Users can set SMOD to BLE pure or GPS/BLE Hybrid, so TrackerD will scan up to 40 BLE iBeacons and send uplinks.
533 -
534 -User can set [[(% class="wikiinternallink wikiinternallink" %)**BLEMASK**>>path:#H3.2.11A0SetBLEMASKtofilterBLEiBeacon]](%%) so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
535 -
536 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
537 -|**Size(bytes)**|2|2|2|…..|2|2|2|2|1
538 -|**Value**|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|…..|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|[[Alarm & BAT>>path:#HAlarm26BAT:]]|[[FLAG>>path:#HFLAG:]]
539 -
540 -=== [[image:image-20231023103116-1.png||height="448" width="901"]] ===
541 -
542 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
543 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
544 -* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
545 -* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
546 -
547 -(% class="wikigeneratedid" %)
548 -Note: This mode does not have a fixed decoder. Its decoder depends on the number of beacons and can be parsed according to the order of the payload.
549 -payload format: (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
550 -
551 -=== ===
552 -
553 -=== 2.4.9  Add Payload format in TTN V3 ===
554 -
555 -
556 556  In TTN V3, user can add a custom payload so it shows friendly.
557 557  
558 558  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
559 559  
508 +
560 560  [[image:1664502649601-895.png||_mstalt="296985"]]
561 561  
562 562  
563 -Add the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
564 564  
513 +Add the decoder from this link: 
514 +
515 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
516 +
565 565  Save the change the uplink message will be parsed. As below:
566 566  
567 567  [[image:1664502676891-606.png||_mstalt="296673"]]
... ... @@ -574,6 +574,7 @@
574 574  
575 575  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]]
576 576  
529 +
577 577  [[image:1664502695771-538.png||_mstalt="297349"]]
578 578  
579 579  
... ... @@ -584,56 +584,16 @@
584 584  
585 585  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]]
586 586  
540 +
587 587  [[image:1664502715371-321.png||_mstalt="292162"]]
588 588  
589 589  
590 -== 2.7  Integrate with Node-red ==
544 +== 2.7  Datalog Feature ==
591 591  
592 592  
593 -~1. Install node-red, please refer to the installation method in the link:
594 -
595 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
596 -
597 -
598 -2. Import the created flow template, please refer to the import method in the link:
599 -
600 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
601 -
602 -
603 -The address of the flow template: [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]
604 -
605 -(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**
606 -
607 -[[image:image-20230307135914-1.png||height="527" width="1045"]]
608 -
609 -
610 -[[image:image-20230307135932-2.png||height="527" width="1044"]]
611 -
612 -
613 -3. Display the map
614 - Enter the link to the map:
615 -
616 - Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
617 -
618 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
619 -
620 -
621 - Hit all input in input stream
622 -
623 - [[image:image-20230308115616-2.png||height="563" width="1070"]]
624 -
625 -
626 - View map again
627 -
628 -[[image:image-20230308115701-3.png||height="571" width="1085"]]
629 -
630 -
631 -== 2.8  Datalog Feature ==
632 -
633 -
634 634  total 273 entries,by default,
635 635  
636 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
637 637  
638 638  Example use case.
639 639  
... ... @@ -643,11 +643,11 @@
643 643  [[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
644 644  
645 645  
646 -== 2.9  Alarm Mode ==
559 +== 2.8 Alarm Mode ==
647 647  
648 648  
649 649  (((
650 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
563 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
651 651  )))
652 652  
653 653  
... ... @@ -668,25 +668,20 @@
668 668  )))
669 669  
670 670  
671 -== 2.10  Transport Mode ==
584 +== 2.9 Transport Mode ==
672 672  
673 673  
674 -In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
587 +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.
675 675  
676 -When device is set in Transport Mode, it will uplink more frequenctly during moving.
677 -
678 678  * **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
679 679  * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
680 680  * **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
681 681  
682 -(% style="display:none" %) (%%)
593 +== 2.10 LED Status ==
683 683  
684 684  
685 -== 2.11  LED Status ==
686 -
687 -
688 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
689 -|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**Event**|=(% style="width: 200px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**AT+LON to control on/off**
596 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
597 +|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
690 690  |(% 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
691 691  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
692 692  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
... ... @@ -699,12 +699,9 @@
699 699  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
700 700  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
701 701  
702 -(% style="display:none" %) (%%)
610 +== 2.11 Button Function ==
703 703  
704 704  
705 -== 2.12  Button Function ==
706 -
707 -
708 708  (% style="color:blue" %)**RESET button:**
709 709  
710 710  [[image:1664502835802-546.png||_mstalt="295061"]]
... ... @@ -714,22 +714,18 @@
714 714  
715 715  (% style="color:red" %)**RED button:**
716 716  
717 -[[image:image-20230213110506-3.png]](% style="display:none" %)
622 +[[image:1664502854406-763.png||_mstalt="295568"]]
718 718  
719 -(% style="display:none" %) (%%)
720 720  
721 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
722 -|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Description**
625 +(% border="1" style="background-color:#ffffcc; width:510px" %)
626 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
723 723  |(% 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"]]
724 724  |(% 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
725 725  |(% 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.
726 726  
727 -(% style="display:none" %) (%%)
631 +== 2.12 USB Port Function ==
728 728  
729 729  
730 -== 2.13  USB Port Function ==
731 -
732 -
733 733  The USB interface of TrackerD has below functions:
734 734  
735 735  * Power on the device
... ... @@ -737,19 +737,6 @@
737 737  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
738 738  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
739 739  
740 -(% style="display:none" %) (%%)
741 -
742 -
743 -== 2.14  Sleep Mode ==
744 -
745 -
746 -(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
747 -
748 -In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
749 -
750 -Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
751 -
752 -
753 753  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
754 754  
755 755  
... ... @@ -763,6 +763,7 @@
763 763  
764 764  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.
765 765  
654 +
766 766  [[image:1664502999401-486.png||_mstalt="296985"]]
767 767  
768 768  
... ... @@ -777,8 +777,8 @@
777 777  
778 778  [[image:1664503047675-651.png||_mstalt="295386"]]
779 779  
780 -(% style="display:none" %) (%%)
781 781  
670 +
782 782  == 3.2 Command Set ==
783 783  
784 784  === 3.2.1 Set Transmit Interval ===
... ... @@ -844,7 +844,7 @@
844 844  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
845 845  
846 846  
847 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
736 +=== 3.2.5 Disable/Enable LED flash ===
848 848  
849 849  
850 850  Disable/Enable LED for position, downlink and uplink
... ... @@ -883,6 +883,7 @@
883 883  
884 884  SMOD define how TrackerD scan and uplink data:
885 885  
775 +
886 886  * (% style="color:blue" %)**AT Command:**
887 887  
888 888  (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
... ... @@ -917,7 +917,6 @@
917 917  
918 918   AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
919 919  
920 - AT+SMOD=2,0,3  ~-~->  (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
921 921  
922 922  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
923 923  
... ... @@ -929,8 +929,10 @@
929 929  
930 930  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.
931 931  
821 +
932 932  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.
933 933  
824 +
934 934  * (% style="color:blue" %)**AT Command:**
935 935  
936 936  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
... ... @@ -948,8 +948,10 @@
948 948  
949 949  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.
950 950  
842 +
951 951  A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
952 952  
845 +
953 953  * (% style="color:blue" %)**AT Command:**
954 954  
955 955  (% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
... ... @@ -964,8 +964,8 @@
964 964  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
965 965  
966 966  
967 -=== 3.2.10 Disable/Enable the confirmation mode ===
968 968  
861 +=== 3.2.10 Disable/Enable the confirmation mode ===
969 969  
970 970  * (% style="color:blue" %)**AT Command:**
971 971  
... ... @@ -972,11 +972,11 @@
972 972  (% style="color:#037691" %)**AT+CFM=xx**
973 973  
974 974  
975 -**Example:**
868 +**~ Example:**
976 976  
977 -AT+CFM=0    **~-~->   ** Disable confirmation
870 + AT+CFM=0    **~-~->   ** Disable confirmation
978 978  
979 -AT+CFM=1    **~-~->  ** Enable confirmation
872 + AT+CFM=1    **~-~->  ** Enable confirmation
980 980  
981 981  
982 982  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
... ... @@ -1014,9 +1014,9 @@
1014 1014  
1015 1015  (% style="color:blue" %)**AT Command:**
1016 1016  
1017 -(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
910 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1018 1018  
1019 -(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
912 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1020 1020  
1021 1021  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1022 1022  
... ... @@ -1032,9 +1032,9 @@
1032 1032  
1033 1033  (% style="color:blue" %)**AT Command:**
1034 1034  
1035 -(% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
928 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1036 1036  
1037 -(% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
930 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1038 1038  
1039 1039  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1040 1040  
... ... @@ -1048,11 +1048,11 @@
1048 1048  
1049 1049  (% style="color:blue" %)**AT Command:**
1050 1050  
1051 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
944 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1052 1052  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1053 1053  
1054 1054  
1055 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
948 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1056 1056  
1057 1057  
1058 1058  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -1059,17 +1059,16 @@
1059 1059  
1060 1060  (% style="color:blue" %)**AT Command:**
1061 1061  
1062 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
955 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1063 1063  
1064 1064  
1065 1065  (% style="color:blue" %)**Downlink Payload:0X24**
1066 1066  
1067 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
960 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1068 1068  
1069 1069  
1070 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
963 +=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1071 1071  
1072 -
1073 1073  User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1074 1074  
1075 1075  (% style="color:blue" %)**AT Command:**
... ... @@ -1076,114 +1076,18 @@
1076 1076  
1077 1077  (% style="color:#037691" %)**AT+PT=xx**
1078 1078  
1079 -Example:
971 + Example:
1080 1080  
1081 -AT+PT=14    ~-~->    Set to detect car motion.
973 + AT+PT=14    ~-~->    Set to detect car motion.
1082 1082  
1083 -AT+PT=41  ~-~->    set to detect walk motion.
975 + AT+PT=41   ~-~->    set to detect walk motion.
1084 1084  
1085 1085  
1086 -(% style="color:blue" %)**Downlink Payload:0xB4**
1087 -
978 +(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1088 1088  0xB4 14          ~/~/  Same as AT+PT=14
1089 1089  
1090 1090  
1091 -=== 3.2.17  Set AT command window time（Since firmware 1.4.5） ===
1092 1092  
1093 -
1094 -AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1095 -
1096 -(% style="color:blue" %)**AT Command:**
1097 -
1098 -(% style="color:#037691" %)**AT+ATST=XX**
1099 -
1100 -Example:
1101 -
1102 -AT+ATST=15    ~-~-> Set the time to 15 seconds
1103 -
1104 -(% style="color:blue" %)**Downlink Payload:0XB5**
1105 -
1106 -0xB5 0F          ~/~/  Same as AT+ATST=15
1107 -
1108 -
1109 -=== 3.2.18  Set the stepmeter mode（Since firmware 1.4.5） ===
1110 -
1111 -
1112 -After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1113 -
1114 -(% style="color:blue" %)**AT Command:**
1115 -
1116 -(% style="color:#037691" %)**AT+PM=xx**
1117 -
1118 -Example:
1119 -
1120 -AT+PM=1    ~-~->  Turn on step counting mode
1121 -
1122 -AT+PM=0    ~-~->  Turn OFF step counting mode
1123 -
1124 -(% style="color:blue" %)**Downlink Payload:0XB6**
1125 -
1126 -0xB6 01          ~/~/  Same as AT+PM=1
1127 -
1128 -
1129 -=== 3.2.19  Set down the decline detection mode（Since firmware 1.4.5） ===
1130 -
1131 -
1132 -This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.
1133 -
1134 -(% style="color:blue" %)**AT Command:**
1135 -
1136 -(% style="color:#037691" %)**AT+FD=xx**
1137 -
1138 -**Example:**
1139 -
1140 -AT+FD=1    ~-~->  Turn on the Fall detection
1141 -
1142 -AT+FD=0    ~-~->  Turn OFF the Fall detection
1143 -
1144 -(% style="color:blue" %)**Downlink Payload:0XB7**
1145 -
1146 -0xB7 01          ~/~/  Same as AT+FD=1
1147 -
1148 -
1149 -=== 3.2.20 Disable/Enable buzzer（Since firmware 1.4.6） ===
1150 -
1151 -
1152 -Disable/Enable buzzer for Alarm, downlink and uplink
1153 -
1154 -(% style="color:blue" %)**AT Command:**
1155 -
1156 -(% style="color:#037691" %)**AT+BEEP=XX**
1157 -
1158 -Example:
1159 -
1160 -AT+BEEP=1 ~-~-> Turn on the buzzer
1161 -
1162 -AT+BEEP=0 ~-~-> Turn OFF the buzzer
1163 -
1164 -(% style="color:blue" %)**Downlink Payload:0XB9**
1165 -
1166 -0xB9 01 ~/~/ Same as AT+BEEP=1
1167 -
1168 -
1169 -=== 3.2.21 Set long press time（Since firmware 1.4.6） ===
1170 -
1171 -
1172 -When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
1173 -
1174 -(% style="color:blue" %)**AT Command:**
1175 -
1176 -(% style="color:#037691" %)**AT+EAT=XX**
1177 -
1178 -Example:
1179 -
1180 -AT+EAT=2 ~-~-> Set the long press time to 2s
1181 -
1182 -(% style="color:blue" %)**Downlink Payload:0XBA**
1183 -
1184 -0xBA 02 ~/~/ Same as AT+EAT=2
1185 -
1186 -
1187 1187  = 4. Setting for Different Scenarios =
1188 1188  
1189 1189  
... ... @@ -1235,15 +1235,16 @@
1235 1235  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1236 1236  
1237 1237  
1238 -[[image:image-20221207120501-1.png]]
1034 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1239 1239  
1240 1240  
1241 1241  
1242 1242  After upgrade finish, it will show finish as below:
1243 1243  
1244 -[[image:image-20221207133911-7.png]]
1040 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1245 1245  
1246 1246  
1043 +
1247 1247  = 6. Developer Guide =
1248 1248  
1249 1249  == 6.1 Compile Source Code ==
... ... @@ -1265,70 +1265,13 @@
1265 1265  [[image:1664503715811-892.png||_mstalt="295698"]]
1266 1266  
1267 1267  
1268 -=== 6.1.2  Build the development environment ===
1269 -
1270 -
1271 -**~1. Download and install arduino IDE**
1272 -
1273 -[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1274 -
1275 -
1276 -**2. Download the ESP32 development package in the arduino IDE**
1277 -
1278 -[[image:image-20221213100007-1.png]]
1279 -
1280 -
1281 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1282 -
1283 -[[image:image-20221213100626-2.png]]
1284 -
1285 -
1286 -Restart the IDE after the addition is complete, then:
1287 -
1288 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1289 -
1290 -
1291 -[[image:image-20221213101040-4.png]]
1292 -
1293 -
1294 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1295 -Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1296 -
1297 -
1298 -Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1299 -
1300 -(% style="color:blue" %)**Methods as below:**
1301 -
1302 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1303 -
1304 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1305 -
1306 1306  (% 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.
1307 1307  
1308 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1309 -
1310 -
1311 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1312 -
1313 -[[image:image-20221213102334-6.png]]
1314 -
1315 -(% style="color:red" %)**Note: This step requires a python environment**
1316 -
1317 -
1318 -Either way, in the end:
1319 -
1320 -The final effect is to open the arduino and you can see the esp32
1321 -
1322 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1323 -
1324 -
1325 -
1326 1326  [[image:image-20221024105643-1.png||_mstalt="428129"]]
1327 1327  
1328 1328  **~ Figure1**
1329 1329  
1330 1330  
1331 -
1332 1332  [[image:image-20221024105643-2.png||_mstalt="428493"]]
1333 1333  
1334 1334   **Figure2**
... ... @@ -1376,8 +1376,9 @@
1376 1376  [[image:1664499635206-262.png||_mstalt="295360"]]
1377 1377  
1378 1378  
1379 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1380 -|=(% style="width: 120px;background-color:#D9E2F3;color:#0070C0" %)**Pin**|=(% style="width: 69px;background-color:#D9E2F3;color:#0070C0" %)**Color**|=(% style="width: 125px;background-color:#D9E2F3;color:#0070C0" %)**USB Pin**
1119 +
1120 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1121 +|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
1381 1381  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1382 1382  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1383 1383  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
... ... @@ -1387,9 +1387,6 @@
1387 1387  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1388 1388  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1389 1389  
1390 -(% style="display:none" %) (%%)
1391 -
1392 -
1393 1393  == 7.3 Notes on using different serial port tools for TrackerD ==
1394 1394  
1395 1395  === 7.3.1  Serial port utility ===
... ... @@ -1403,6 +1403,7 @@
1403 1403  [[image:image-20221102140621-1.png||_mstalt="425672"]]
1404 1404  
1405 1405  
1144 +
1406 1406  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1407 1407  
1408 1408  [[image:image-20221102140638-2.png||_mstalt="428727"]]
... ... @@ -1471,18 +1471,6 @@
1471 1471  [[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1472 1472  
1473 1473  
1474 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1475 -
1476 -
1477 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1478 -
1479 -
1480 -== 7.6 Can alert mode and transport mode be used together? ==
1481 -
1482 -
1483 -Yes, you can also press the panic button to sound the alarm if set to transport mode
1484 -
1485 -
1486 1486  = 8  Trouble Shooting =
1487 1487  
1488 1488  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1489,7 +1489,7 @@
1489 1489  
1490 1490  
1491 1491  (((
1492 -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
1219 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1493 1493  )))
1494 1494  
1495 1495  
... ... @@ -1503,31 +1503,29 @@
1503 1503  
1504 1504  == 8.3  Problem after Upgrading Firmware ==
1505 1505  
1506 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1233 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1507 1507  
1235 +Error Output
1508 1508  
1509 -**Error Output**
1510 -
1511 -
1512 1512  [[image:image-20221122100004-4.png||_mstalt="424606"]]
1513 1513  
1514 -
1515 1515  (((
1516 1516  Some partition is missed during upgrade, please upgrade below four files as example:
1517 1517  
1518 -[[image:image-20221207120524-2.png]]
1242 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1519 1519  )))
1520 1520  
1521 1521  
1522 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1523 1523  
1524 1524  
1525 -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
1248 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1526 1526  
1527 1527  
1528 -=== 8.3.3 "flash read err" after upgrade firmware ===
1251 +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
1529 1529  
1530 1530  
1254 +=== 8.3.3 "flash read err" after upgrade firmware ===
1255 +
1531 1531  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1532 1532  
1533 1533  [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
... ... @@ -1535,32 +1535,28 @@
1535 1535  
1536 1536  User need to upgrade again with below four files to solve this issue.
1537 1537  
1538 - [[image:image-20221207120530-3.png]]
1263 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1539 1539  
1540 1540   **Figure 2**
1541 1541  
1542 1542  
1543 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1268 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1544 1544  
1545 -
1546 1546  User might erase the entire flash include keys and default settings which cause this issue.
1547 1547  
1548 -After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1549 1549  
1550 -
1551 1551  [[image:image-20221122100004-3.png||_mstalt="424242"]]
1552 1552  
1276 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1553 1553  
1554 -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.
1555 -
1556 1556  After AT+FDR. please set
1557 1557  
1558 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1280 +* AT+PDOP=7
1281 +* AT+FTIME=180000
1559 1559  
1560 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1283 +Example:
1561 1561  
1562 -**Example:**
1563 -
1564 1564  AT+PDOP=7.00
1565 1565  
1566 1566  AT+FTIME=180
... ... @@ -1578,6 +1578,13 @@
1578 1578  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1579 1579  
1580 1580  
1302 +
1303 +=== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===
1304 +
1305 +
1306 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1307 +
1308 +
1581 1581  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1582 1582  
1583 1583  
... ... @@ -1600,59 +1600,6 @@
1600 1600  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
1601 1601  
1602 1602  
1603 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1604 -
1605 -
1606 -When upgrading, use the erase button to upgrade
1607 -
1608 -[[image:image-20221207120536-4.png]]
1609 -
1610 -
1611 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1612 -
1613 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1614 -
1615 -
1616 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1617 -
1618 -[[image:image-20221207134028-8.png]]
1619 -
1620 -
1621 -Reboot information after upgrade
1622 -
1623 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1624 -
1625 -
1626 -Use (% style="color:blue" %)**AT+FDR**(%%) command to reset and then use (% style="color:blue" %)**AT+CFG**(%%) to check whether the configuration is back to normal
1627 -
1628 -[[image:image-20221128111850-5.png]]
1629 -
1630 -
1631 -After the parameters return to normal, upgrade to the version you need again
1632 -
1633 -[[image:image-20221207120601-5.png]]
1634 -
1635 -
1636 -At this point, the parameters return to normal after running AT+FDR again
1637 -
1638 -[[image:image-20221128112035-7.png]]
1639 -
1640 -
1641 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1642 -
1643 -
1644 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1645 -
1646 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1647 -
1648 -
1649 -== 8.8  Why when using some serial consoles, only inputting the first string port console will return "error"? ==
1650 -
1651 -
1652 -Need to enter the entire command at once, not a single character.
1653 -User can open a command window or copy the entire command to the serial console.
1654 -
1655 -
1656 1656  = 9.  Order Info =
1657 1657  
1658 1658  
... ... @@ -1674,9 +1674,6 @@
1674 1674  
1675 1675  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1676 1676  
1677 -(% style="display:none" %) (%%)
1678 -
1679 -
1680 1680  = 10.  Packing Info =
1681 1681  
1682 1682  
... ... @@ -1692,9 +1692,6 @@
1692 1692  
1693 1693  * Weight: 50g
1694 1694  
1695 -(% style="display:none" %) (%%)
1696 -
1697 -
1698 1698  = 11. Support =
1699 1699  
1700 1700  
... ... @@ -1702,10 +1702,6 @@
1702 1702  
1703 1703  * 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]].
1704 1704  
1705 -(% style="display:none" %)
1706 -
1707 -
1708 -
1709 1709  = 12.  Reference =
1710 1710  
1711 1711  
... ... @@ -1714,6 +1714,3 @@
1714 1714  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1715 1715  
1716 1716  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1717 -
1718 -
1719 -)))
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
image-20221207120501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120524-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120530-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120536-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120601-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207133836-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
image-20221207133911-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20221207134028-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20221213100007-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.7 KB
Content
image-20221213100626-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.7 KB
Content
image-20221213100808-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20221213101040-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -26.3 KB
Content
image-20221213102311-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.7 KB
Content
image-20221213102334-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 KB
Content
image-20221213102718-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20221213110952-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.8 KB
Content
image-20230213110119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.3 KB
Content
image-20230213110214-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.3 KB
Content
image-20230213110506-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.8 KB
Content
image-20230302145315-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20230307135914-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -131.8 KB
Content
image-20230307135932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -109.7 KB
Content
image-20230308115430-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 MB
Content
image-20230308115616-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.7 KB
Content
image-20230308115701-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 MB
Content
image-20230426085815-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -190.0 KB
Content
image-20231023103116-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -48.2 KB
Content