Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)

Last modified by Xiaoling on 2023/12/27 09:15

From 149.1 to 150.1 From 216.7 to 216.8

From version 150.1

edited by Edwin Chen
on 2022/11/24 09:07

Change comment: There is no comment for this version

To version 216.7

edited by Xiaoling
on 2023/12/27 08:53

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)
Attachments (0 modified, 34 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--TrackerD -LoRaWAN Tracker User Manual
++TrackerD - LoRaWAN Tracker User Manual

Author

@@ -1,1 +1,1 @@
--XWiki.Edwin
++XWiki.Xiaoling

Content

@@ -12,6 +12,7 @@
++
  = 1.  Introduction =
  == 1.1  What is TrackerD ==
@@ -22,7 +22,7 @@
  )))
  (((
--In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.
++In TrackerD, there are various sensors such as GPS,BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.
  (((
  TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
@@ -31,15 +31,12 @@
  (((
  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.
  )))
--)))
  (((
  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.
--
--
  )))
--[[image:1664499921684-770.png||_mstalt="298194"]]
++[[image:image-20230213110119-1.png||height="382" width="834"]]
  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
@@ -53,7 +53,6 @@
  * Espressif ESP32 PICO D4
  * MCU: ESP32 PICO D4
  * Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
--* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
  * Integrated SPI flash : 4 MB
  * RAM: 448 KB
  * EEPROM: 520 KB
@@ -95,6 +95,10 @@
  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
  * Tracking: max: 38mA
++(% style="display:none" %)
++
++
++
  == 1.3  Features ==
@@ -103,7 +103,7 @@
  * SX1276/78 Wireless Chip
  * Arduino IDE Compatible
  * Open source hardware / software
--* Regular/ Real-time GPS,BLE,WIFI tracking
++* Regular/ Real-time GPS,BLE
  * Built-in3 axis accelerometer (LIS3DH)
  * Humidity / temperature sensor : GXCAS Technology GXHT3X
  * Motion sensing capability
@@ -113,6 +113,10 @@
  * Tri-color LED, Alarm button
  * Datalog
++(% style="display:none" %)
++
++
++
  == 1.4  Applications ==
@@ -119,6 +119,10 @@
  * Logistics and Supply Chain Management
  * Human tracking
++(% style="display:none" %)
++
++
++
  = 2.  Use TrackerD =
  == 2.1  How it works? ==
@@ -133,10 +133,9 @@
  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.
--[[image:1664501652064-326.png||_mstalt="293306"]]
++[[image:image-20230213110214-2.png||height="388" width="847"]]
--
  The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:
@@ -145,7 +145,7 @@
  Each TrackerD is shipped with a sticker with the default device EUI as below:
--[[image:1664501677253-891.png||_mstalt="296569"]]
++[[image:image-20230426085815-1.png||height="259" width="558"]]
  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
@@ -153,11 +153,9 @@
  **__Add APP EUI in the application:__**
--
  [[image:1664501711466-918.png||_mstalt="295828"]]
--
  [[image:1664501721248-725.png||_mstalt="294450"]]
@@ -164,7 +164,6 @@
  [[image:1664501734705-405.png||_mstalt="293306"]]
--
  **__Add APP KEY and DEV EUI:__**
@@ -171,7 +171,6 @@
  [[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"]]
--
  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
  (% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
@@ -188,7 +188,7 @@
  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
  * (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
--* (% 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.
++* (% style="color:#037691" %)**BLE:            **(%%)**          **Only obtain iBeacon info via BLE and uplink uplink. Design for Indoor tracking.
  * (% 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.
  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
@@ -199,15 +199,14 @@
  === 2.4.1  Uplink FPORT~=5, Device Status ===
--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.
++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.
--Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
++Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
++|(% 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
++|(% 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
--(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
--|=(% 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
--|=(% 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
--
  [[image:1665301570342-765.png||_mstalt="294580"]]
@@ -219,31 +219,30 @@
  (% style="color:#037691" %)**Frequency Band**:
--*0x01: EU868
++0x01: EU868
--*0x02: US915
++0x02: US915
--*0x03: IN865
++0x03: IN865
--*0x04: AU915
++0x04: AU915
--*0x05: KZ865
++0x05: KZ865
--*0x06: RU864
++0x06: RU864
--*0x07: AS923
++0x07: AS923
--*0x08: AS923-1
++0x08: AS923-1
--*0x09: AS923-2
++0x09: AS923-2
--*0x0a: AS923-3
++0x0a: AS923-3
--Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
++(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
  (% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
--
  (% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
  Use can also get the Device Status uplink through the downlink command:
@@ -251,54 +251,48 @@
  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
--(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
--|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
--|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
++|(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
++|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
--(% style="color:blue" %)**     SMOD：**
++(% style="color:blue" %)**SMOD：**
--(% style="color:red" %)**      1 :** (%%)  GPS ONLY
++(% style="color:red" %)**1 :** (%%)  GPS ONLY
--(% style="color:red" %)**      2 :** (%%)  BLE ONLY
++(% style="color:red" %)**2 :** (%%)  BLE ONLY
--(% style="color:red" %)**      3 :**  (%%) GPS/BLE Hybrid
++(% style="color:red" %)**3 :**  (%%) GPS/BLE Hybrid
--(% style="color:blue" %)**      GPS_MOD: Define how to send GPS payload**
++(% style="color:blue" %)**GPS_MOD: Define how to send GPS payload**
--(% style="color:red" %)**      0 : ** (%%)  Enable uploading on-board Temperature and humidity values
++(% style="color:red" %)**0 : ** (%%)  Enable uploading on-board Temperature and humidity values
--(% style="color:red" %)**      1 :** (%%)   Disable uploading on-board Temperature and humidity values
++(% style="color:red" %)**1 :** (%%)   Disable uploading on-board Temperature and humidity values
--(% style="color:blue" %)**      BLE_Settings:**
++(% style="color:blue" %)**BLE_Settings:**
--(% style="color:red" %)**      1: ** (%%)  BLE Positioning with Strongest iBeacon
++(% style="color:red" %)**1: ** (%%)  BLE Positioning with Strongest iBeacon
--(% _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)(%%)
--
  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
--(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
--|=(% 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
--|=(% 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"]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
++|(% 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
++|(% 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"]]
--=== 2.4.2  Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
++(% style="display:none" %)
--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,
++=== 2.4.2  Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
--(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
--|=(% scope="row" 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
--)))
--|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
++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,
++
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)
++|(% 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
++|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
@@ -307,15 +307,18 @@
  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
--(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
--|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
--|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)
++|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits
++|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]]
++(% style="display:none" %)
++
++
  ==== (% style="color:blue" %)**FLAG:**(%%) ====
--(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
--|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
--|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
++|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit
++|(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
@@ -340,7 +340,6 @@
  [[image:1664502166010-515.png||_mstalt="291395"]]
--
  ==== (% style="color:blue" %)**Alarm:**(%%) ====
  **Example: ** 0x4B & 0x40 >> 6 = 0x01
@@ -360,6 +360,8 @@
  * 3.40v ~~ 3.69v:   20% ~~ 40%
  * < 3.39v:             0~~20%
++(% style="display:none" %) (%%)
++
  ==== (% style="color:blue" %)**MOD:**(%%) ====
  **Example: ** (0x60>>6) & 0x3f =1
@@ -403,14 +403,12 @@
  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
--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)
++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)
--(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
--|=(% scope="row" style="width: 60px;" %)(((
--**Size(bytes)**
--)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
--|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
++|(% style="width:60px" %)**Size(bytes)**|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1
++|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
@@ -421,7 +421,7 @@
  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
--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.
++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.
  (% style="color:red" %)**Note for this mode:**
@@ -432,11 +432,9 @@
  The payload is 15 bytes, as below.
--(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
--|=(% scope="row" %)(((
--**Size(bytes)**
--)))|4|4|2|1|1|1|1|1
--|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
++(% border="1" style="background-color:#f2f2f2; width:500px" %)
++|**Size(bytes)**|4|4|2|1|1|1|1|1
++|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
  [[image:image-20221009160309-2.png||_mstalt="429312"]]
@@ -449,11 +449,9 @@
  User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
--(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
--|=(% scope="row" 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
--|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
++|(% 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
++|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
  iBeacon MAJOR
  )))|(% style="width:63px" %)(((
  iBeacon MINOR
@@ -476,44 +476,64 @@
  * (% style="color:#037691" %)**Measured Power: ** (%%)   The Measured Power from the strongest iBeacon.
  * (% style="color:#037691" %)**RSSI:  **    (%%) The RSSI from the strongest iBeacon.
--=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
++(% style="display:none" %) (%%)
++=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
--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.
++The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
--(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
--|=(% scope="row" style="width: 60px;" %)(((
--**Size(bytes)**
--)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
--|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
--[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
--)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
++|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
++|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
--(% class="wikigeneratedid" %)
--[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
++ [[image:image-20230302145315-1.png]]
++**alarm**=(bytes[0] & 0x40)    ~/~/ Alarm status
--* (% style="color:#037691" %)**BAT: **  (%%)    Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
--* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
--* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
++**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;     ~/~/ Battery,units:V
--=== 2.4.7  Add Payload format in TTN V3 ===
++**mod** = bytes[2] & 0xC0;
++**Lon**=(bytes[2] & 0x20)
--In TTN V3, user can add a custom payload so it shows friendly.
--In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
++=== 2.4.7  Uplink FPORT~=9, BLE Positioning with Multiple iBeacon(Since firmware 1.4.7) ===
--[[image:1664502649601-895.png||_mstalt="296985"]]
++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.
++User can set [[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**BLEMASK**>>path:#H3.2.11A0SetBLEMASKtofilterBLEiBeacon]](%%) so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
++|**Size(bytes)**|2|2|1|…..|2|2|1|2|1
++|**Value**|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|…..|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|[[Alarm & BAT>>path:#HAlarm26BAT:]]|[[FLAG>>path:#HFLAG:]]
--Add the decoder from this link:
++(% class="wikigeneratedid" id="H" %)
++[[image:image-20231023103116-1.png||height="448" width="901"]]
--[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
++* (% style="color:#037691" %)**BAT: **  (%%)     Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
++* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
++* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
++* (% style="color:#037691" %)**RSSI:  **    (%%) The RSSI from the strongest iBeacon.
++(% class="wikigeneratedid" %)
++**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.**
++payload format: (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
++
++
++=== 2.4.8  Add Payload format in TTN V3 ===
++
++
++In TTN V3, user can add a custom payload so it shows friendly.
++
++In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
++
++[[image:1664502649601-895.png||_mstalt="296985"]]
++
++
++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]]
++
  Save the change the uplink message will be parsed. As below:
  [[image:1664502676891-606.png||_mstalt="296673"]]
@@ -526,7 +526,6 @@
  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]]
--
  [[image:1664502695771-538.png||_mstalt="297349"]]
@@ -537,16 +537,56 @@
  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]]
--
  [[image:1664502715371-321.png||_mstalt="292162"]]
--== 2.7  Datalog Feature ==
++== 2.7  Integrate with Node-red ==
++~1. Install node-red, please refer to the installation method in the link:
++
++[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
++
++
++2. Import the created flow template, please refer to the import method in the link:
++
++[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
++
++
++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]]
++
++(% 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.**
++
++[[image:image-20230307135914-1.png||height="527" width="1045"]]
++
++
++[[image:image-20230307135932-2.png||height="527" width="1044"]]
++
++
++3. Display the map
++    Enter the link to the map:
++
++    Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
++
++**~    **[[image:image-20230308115430-1.png||height="548" width="1041"]]
++
++
++    Hit all input in input stream
++
++   [[image:image-20230308115616-2.png||height="563" width="1070"]]
++
++
++    View map again
++
++[[image:image-20230308115701-3.png||height="571" width="1085"]]
++
++
++== 2.8  Datalog Feature ==
++
++
  total 273 entries,by default,
--User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
++User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
  Example use case.
@@ -556,14 +556,13 @@
  [[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
--== 2.8  Alarm Mode ==
++== 2.9  Alarm Mode ==
  (((
--User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
++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.
  )))
--
  (((
  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.
  )))
@@ -581,23 +581,24 @@
  )))
--== 2.9  Transport Mode ==
++== 2.10  Transport Mode ==
--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.
++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"]]**.
--[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation.
++When device is set in Transport Mode, it will uplink more frequenctly during moving.
--[[TDC>>||anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
++* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
++* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
++* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
--[[PT>>||anchor="H3.2.1SetTransmitInterval"]] defines the threldhold to detect a motion.
++(% style="display:none" %) (%%)
++== 2.11  LED Status ==
--== 2.10  LED Status ==
--
--(% border="1.5" style="background-color:#ffffcc; width:500px" %)
--|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
++|=(% 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**
  |(% 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
  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
@@ -610,9 +610,11 @@
  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
--== 2.11  Button Function ==
++(% style="display:none" %) (%%)
++== 2.12  Button Function ==
++
  (% style="color:blue" %)**RESET button:**
  [[image:1664502835802-546.png||_mstalt="295061"]]
@@ -622,18 +622,21 @@
  (% style="color:red" %)**RED button:**
--[[image:1664502854406-763.png||_mstalt="295568"]]
++[[image:image-20230213110506-3.png]](% style="display:none" %)
++(% style="display:none" %) (%%)
--(% border="1" style="background-color:#ffffcc; width:510px" %)
--|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
++|=(% 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**
  |(% 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"]]
  |(% 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
  |(% 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.
--== 2.12  USB Port Function ==
++(% style="display:none" %) (%%)
++== 2.13  USB Port Function ==
++
  The USB interface of TrackerD has below functions:
  * Power on the device
@@ -641,6 +641,18 @@
  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
++(% style="display:none" %) (%%)
++
++== 2.14  Sleep Mode ==
++
++
++(% 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.
++
++In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
++
++Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
++
++
  = 3.  Configure TrackerD via AT command or LoRaWAN downlink =
@@ -654,7 +654,6 @@
  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.
--
  [[image:1664502999401-486.png||_mstalt="296985"]]
@@ -669,8 +669,8 @@
  [[image:1664503047675-651.png||_mstalt="295386"]]
++(% style="display:none" %) (%%)
--
  == 3.2  Command Set ==
  === 3.2.1  Set Transmit Interval ===
@@ -736,7 +736,7 @@
  (% style="color:#037691" %)**0x02 01**    (%%)   ~/~/  Exit Alarm Mode
--=== 3.2.5  Disable/Enable LED flash ===
++=== 3.2.5  Disable/Enable LED flash and buzzer ===
  Disable/Enable LED for position, downlink and uplink
@@ -775,7 +775,6 @@
  SMOD define how TrackerD scan and uplink data:
--
  * (% style="color:blue" %)**AT Command:**
  (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
@@ -784,7 +784,7 @@
  * (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
--* (% 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.
++* (% style="color:red" %)**2: BLE :                     **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
  * (% 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.
@@ -797,8 +797,7 @@
  (% style="color:#037691" %)**cc:   **
  * (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
--
--* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
++
  (% style="color:blue" %)**Example:**
@@ -808,9 +808,8 @@
    AT+SMOD=2,0,1    ~-~->    (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
--  AT+SMOD=2,0,2    ~-~->    (WiFi)SSID+Rssi+BAT+State
++  AT+SMOD=2,0,3    ~-~->    (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
--
  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
  (% style="color:#037691" %)**0xA5 01 00 00**    (%%)   ~/~/  Same as AT+SMOD=1,0,0
@@ -821,10 +821,8 @@
  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.
--
  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.
--
  * (% style="color:blue" %)**AT Command:**
  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
@@ -842,10 +842,8 @@
  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.
--
  A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
--
  * (% style="color:blue" %)**AT Command:**
  (% style="color:#037691" %)**AT+PDOP=2.5 **  (%%) **~-~->  ** Set PDOP to 2.5
@@ -860,8 +860,8 @@
  (% style="color:#037691" %)**0xAD 00 46**    (%%)  ~/~/  Set AT+PDOP=7       (0x46 / 10 =7)
++=== 3.2.10  Disable/Enable the confirmation mode ===
--=== 3.2.10 Disable/Enable the confirmation mode ===
  * (% style="color:blue" %)**AT Command:**
@@ -868,11 +868,11 @@
  (% style="color:#037691" %)**AT+CFM=xx**
--**~ Example:**
++**Example:**
--  AT+CFM=0    **~-~->   ** Disable confirmation
++AT+CFM=0    **~-~->   ** Disable confirmation
--  AT+CFM=1    **~-~->  **  Enable confirmation
++AT+CFM=1    **~-~->  **  Enable confirmation
  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
@@ -910,72 +910,167 @@
  (% style="color:blue" %)**AT Command:**
--     (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%)  ~/~/ Set BLEMASK = 123456
++(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%)  ~/~/ Set BLEMASK = 123456
--     (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%)             ~/~/ disable BLEMASK
++(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%)             ~/~/ disable BLEMASK
--(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
++(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)**
  Example:  0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
--=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
++=== 3.2.13  Disable/Enable Information printing(Since firmware 1.4.1) ===
--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.
++Users can use this feature to enable/disable Information printing.
--(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
++(% style="color:blue" %)**AT Command:**
++(% style="color:#037691" %)**AT+SHOWID=XX         **(%%)  ~/~/  (Disable (0), Enable (1), default:0)
++\\Example:  AT+SHOWID=1   ~-~->    Enable Information printing.
++
++
++=== 3.2.14  Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
++
++
++The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
++
  (% style="color:blue" %)**AT Command:**
--     (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
++(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
--     (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%)        ~/~/ disable WiFiMASK
--(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
++(% style="color:blue" %)**Downlink Payload:0X24**
--Example:  0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
++Example: 0x24 01   ~/~/ Same as AT+CHE=1
--=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
++=== 3.2.15  Get or Set Threshold for motion detect(Since firmware 1.4.3) ===
--Users can use this feature to enable/disable Information printing.
++User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
  (% style="color:blue" %)**AT Command:**
--(% style="color:#037691" %)**AT+SHOWID=XX         **(%%)  ~/~/(Disable (0), Enable (1), default:0)
--\\Example:  AT+SHOWID=1   ~-~->    Enable Information printing.
++(% style="color:#037691" %)**AT+PT=xx**
++Example:
--=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
++AT+PT=14    ~-~->    Set to detect car motion.
++AT+PT=41    ~-~->    set to detect walk motion.
--The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
++(% style="color:blue" %)**Downlink Payload:0xB4**
++
++0xB4 14          ~/~/  Same as AT+PT=14
++
++
++=== 3.2.16  Set AT command window time(Since firmware 1.4.5) ===
++
++
++AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
++
  (% style="color:blue" %)**AT Command:**
--(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
++(% style="color:#037691" %)**AT+ATST=XX**
++Example:
--(% style="color:blue" %)**Downlink Payload:0X24**
++AT+ATST=15    ~-~-> Set the time to 15 seconds
--Example: 0x24 01 ~/~/ Same as AT+CHE=1
++(% style="color:blue" %)**Downlink Payload:0XB5**
++0xB5 0F          ~/~/  Same as AT+ATST=15
--= 4.  Setting for Different Scenarios =
++=== 3.2.17  Set the stepmeter mode(Since firmware 1.4.5) ===
--= 5.  Upload Firmware =
++After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
--== 5.1  Firmware Change Log ==
++(% style="color:blue" %)**AT Command:**
++(% style="color:#037691" %)**AT+PM=xx**
++Example:
++
++AT+PM=1    ~-~->  Turn on step counting mode
++
++AT+PM=0    ~-~->  Turn OFF step counting mode
++
++(% style="color:blue" %)**Downlink Payload:0XB6**
++
++0xB6 01          ~/~/  Same as AT+PM=1
++
++
++=== 3.2.18  Set down the decline detection mode(Since firmware 1.4.5) ===
++
++
++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.
++
++(% style="color:blue" %)**AT Command:**
++
++(% style="color:#037691" %)**AT+FD=xx**
++
++**Example:**
++
++AT+FD=1    ~-~->  Turn on the Fall detection
++
++AT+FD=0    ~-~->  Turn OFF the Fall detection
++
++(% style="color:blue" %)**Downlink Payload:0XB7**
++
++0xB7 01          ~/~/  Same as AT+FD=1
++
++
++=== 3.2.19 Disable/Enable buzzer(Since firmware 1.4.6) ===
++
++
++Disable/Enable buzzer for Alarm, downlink and uplink
++
++(% style="color:blue" %)**AT Command:**
++
++(% style="color:#037691" %)**AT+BEEP=XX**
++
++Example:
++
++AT+BEEP=1    ~-~->  Turn on the buzzer
++
++AT+BEEP=0    ~-~->  Turn OFF the  buzzer
++
++(% style="color:blue" %)**Downlink Payload:0XB9**
++
++0xB9 01          ~/~/  Same as AT+BEEP=1
++
++
++=== 3.2.20 Set long press time(Since firmware 1.4.6) ===
++
++
++When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
++
++(% style="color:blue" %)**AT Command:**
++
++(% style="color:#037691" %)**AT+EAT=XX**
++
++Example:
++
++AT+EAT=2    ~-~->  Set the long press time to 2s
++
++(% style="color:blue" %)**Downlink Payload:0XBA**
++
++0xBA 02          ~/~/  Same as AT+EAT=2
++
++
++= 4.  Upload Firmware =
++
++== 4.1  Firmware Change Log ==
++
++
  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
--== 5.2  How to upgrade firmware ==
++== 4.2  How to upgrade firmware ==
  User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
@@ -1014,23 +1014,22 @@
  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
--[[image:image-20221118105220-2.png||_mstalt="426608"]]
++[[image:image-20221207120501-1.png]]
  After upgrade finish, it will show finish as below:
--[[image:image-20221118105402-4.png||_mstalt="427986"]]
++[[image:image-20221207133911-7.png]]
++= 5.  Developer Guide =
--= 6.  Developer Guide =
++== 5.1  Compile Source Code ==
--== 6.1  Compile Source Code ==
++=== 5.1.1  Set up ARDUINO compile environment ===
--=== 6.1.1  Set up ARDUINO compile environment ===
--
  * **Download the latest Arduino software (IDE) from the Arduino official website:  [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]**
  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]]
@@ -1045,13 +1045,70 @@
  [[image:1664503715811-892.png||_mstalt="295698"]]
++=== 5.1.2  Build the development environment ===
++
++
++**~1. Download and install arduino IDE**
++
++[[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]]
++
++
++**2. Download the ESP32 development package in the arduino IDE**
++
++[[image:image-20221213100007-1.png]]
++
++
++Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
++
++[[image:image-20221213100626-2.png]]
++
++
++Restart the IDE after the addition is complete, then:
++
++[[image:image-20221213100808-3.png||height="679" width="649"]]
++
++
++[[image:image-20221213101040-4.png]]
++
++
++(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
++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)**
++
++
++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:
++
++(% style="color:blue" %)**Methods as below:**
++
++~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
++
++2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
++
  (% 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.
++[[image:image-20221213102311-5.png||height="582" width="711"]]
++
++
++**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
++
++[[image:image-20221213102334-6.png]]
++
++(% style="color:red" %)**Note: This step requires a python environment**
++
++
++Either way, in the end:
++
++The final effect is to open the arduino and you can see the esp32
++
++[[image:image-20221213110952-8.png||height="866" width="711"]]
++
++
++
  [[image:image-20221024105643-1.png||_mstalt="428129"]]
  **~                                                                                Figure1**
++
  [[image:image-20221024105643-2.png||_mstalt="428493"]]
                                                                                     **Figure2**
@@ -1065,7 +1065,7 @@
  [[image:1664503752288-974.png||_mstalt="298194"]]
--== 6.2  Source Code ==
++== 5.2  Source Code ==
  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
@@ -1085,23 +1085,22 @@
  [[image:1664503824081-592.png||_mstalt="294918"]]  [[image:1664503831430-500.png||_mstalt="290784"]]
--= 7.  FAQ =
++= 6.  FAQ =
--== 7.1  How to change the LoRa Frequency Bands/Region? ==
++== 6.1  How to change the LoRa Frequency Bands/Region? ==
  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
--== 7.2  What is the pin mapping for the USB program cable? ==
++== 6.2  What is the pin mapping for the USB program cable? ==
  [[image:1664499635206-262.png||_mstalt="295360"]]
--
--(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
--|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
++(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
++|=(% 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**
  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
@@ -1111,11 +1111,14 @@
  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
--== 7.3  Notes on using different serial port tools for TrackerD ==
++(% style="display:none" %) (%%)
--=== 7.3.1  Serial port utility ===
++== 6.3  Notes on using different serial port tools for TrackerD ==
++=== 6.3.1  Serial port utility ===
++
++
  Serial port utility requires you to automatically add data streams.
  Need to adjust the data stream to RTS/CTS on physical restart.
@@ -1124,13 +1124,12 @@
  [[image:image-20221102140621-1.png||_mstalt="425672"]]
--
  When using AT commands, the data flow needs to be adjusted to XON/XOFF
  [[image:image-20221102140638-2.png||_mstalt="428727"]]
--=== 7.3.2  SecureCRT ===
++=== 6.3.2  SecureCRT ===
  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.
@@ -1142,7 +1142,7 @@
  [[image:image-20221102140712-4.png||_mstalt="427089"]]
--=== 7.3.3  PUTTY ===
++=== 6.3.3  PUTTY ===
  [[image:image-20221102140748-5.png||_mstalt="430456"]]
@@ -1154,7 +1154,7 @@
  [[image:image-20221102140801-6.png||_mstalt="427466"]]
--== 7.4 How to modify source code to compile different frequency band bin file? ==
++== 6.4 How to modify source code to compile different frequency band bin file? ==
  (% class="box infomessage" %)
@@ -1193,17 +1193,29 @@
  [[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
--= 8  Trouble Shooting =
++== 6.5 Are there example python example for BLE Indoor Positioning? ==
--== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
++[[Operating instructions for BLE indoor positioning>>doc:Main.User Manual for LoRaWAN End Nodes.TrackerD.Example of BLE indoor positioning python.WebHome]]
++
++== 6.6 Can alert mode and transport mode be used together? ==
++
++
++Yes, you can also press the panic button to sound the alarm if set to transport mode
++
++
++= 7  Trouble Shooting =
++
++== 7.1  TDC is changed to 4294947296 and cause no uplink. ==
++
++
  (((
--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
++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
  )))
--== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
++== 7.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
  (((
@@ -1211,27 +1211,33 @@
  )))
--== 8.3  Problem after Upgrading Firmware ==
++== 7.3  Problem after Upgrading Firmware ==
--=== 8.3.1 Continue Restart after upgrading ===
++=== 7.3.1  "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
--(((
--If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
--)))
++**Error Output**
--[[image:image-20221118105249-3.png||_mstalt="430664"]]
++[[image:image-20221122100004-4.png||_mstalt="424606"]]
--=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
++(((
++Some partition is missed during upgrade, please upgrade below four files as example:
++[[image:image-20221207120524-2.png]]
++)))
++
++=== 7.3.2  TrackerD's led light is always GREEN on after upgrading ===
++
++
  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
--=== 8.3.3 "flash read err" after upgrade firmware ===
++=== 7.3.3  "flash read err" after upgrade firmware ===
++
  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
  [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
@@ -1239,28 +1239,32 @@
  User need to upgrade again with below four files to solve this issue.
-- [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
++ [[image:image-20221207120530-3.png]]
                                         **Figure 2**
--=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
++=== 7.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
++
  User might erase the entire flash include keys and default settings which cause this issue.
--After the upgrade is completed, enter AT+CFG as shown in the figure below.
++After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
++
  [[image:image-20221122100004-3.png||_mstalt="424242"]]
--Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
++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.
++
  After AT+FDR. please set
--* AT+PDOP=7
--* AT+FTIME=180000
++* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
--Example:
++* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
++**Example:**
++
  AT+PDOP=7.00
  AT+FTIME=180
@@ -1278,20 +1278,13 @@
  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
++== 7.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
--=== 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 ===
--
--[[image:image-20221122100004-4.png||_mstalt="424606"]]
--
--
--== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
--
--
  Please download version 1.4.2 again
--== 8.5  How to deal with unsuccessful GPS positioning? ==
++== 7.5  How to deal with unsuccessful GPS positioning? ==
 ） Make Sure the device is in Open Area where can see the sky.
@@ -1307,9 +1307,62 @@
  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
--= 9.  Order Info =
++== 7.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
++When upgrading, use the erase button to upgrade
++
++[[image:image-20221207120536-4.png]]
++
++
++The parameters are displayed abnormally and cannot be fixed using AT+FDR
++
++[[image:image-20221128103040-2.png||height="431" width="525"]]
++
++
++Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
++
++[[image:image-20221207134028-8.png]]
++
++
++Reboot information after upgrade
++
++[[image:image-20221128111443-4.png||height="432" width="546"]]
++
++
++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
++
++[[image:image-20221128111850-5.png]]
++
++
++After the parameters return to normal, upgrade to the version you need again
++
++[[image:image-20221207120601-5.png]]
++
++
++At this point, the parameters return to normal after running AT+FDR again
++
++[[image:image-20221128112035-7.png]]
++
++
++== 7.7  If you encounter the following problems, please upgrade to the latest version ==
++
++
++~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
++
++2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
++
++
++== 7.8  Why when using some serial consoles, only inputting the first string port console will return "error"? ==
++
++
++Need to enter the entire command at once, not a single character.
++User can open a command window or copy the entire command to the serial console.
++
++
++= 8.  Order Info =
++
++
  Part Number: (% style="color:blue" %)**TrackerD-XXX**
  (% style="color:blue" %)**XXX**(%%): The default frequency band
@@ -1328,9 +1328,12 @@
  * (% style="color:red" %)**US915**(%%): Default frequency band US915
--= 10.  Packing Info =
++(% style="display:none" %) (%%)
++= 9.  Packing Info =
++
++
  (% style="color:#037691" %)**Package Includes**:
  * TrackerD LoRaWAN GPS/BLE Tracker x 1
@@ -1343,6 +1343,9 @@
  * Weight: 50g
++(% style="display:none" %) (%%)
++
++
  = 11.  Support =
@@ -1350,6 +1350,10 @@
  * 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]].
++(% style="display:none" %)
++
++
++
  = 12.  Reference =
@@ -1358,3 +1358,6 @@
  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
++
++
++)))

image-20221128102938-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+41.3 KB

Content

image-20221128103040-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+19.2 KB

Content

image-20221128110503-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+45.6 KB

Content

image-20221128111443-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+15.6 KB

Content

image-20221128111850-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+14.5 KB

Content

image-20221128111951-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+45.4 KB

Content

image-20221128112035-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+14.7 KB

Content

image-20221207120501-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+44.5 KB

Content

image-20221207120524-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+44.5 KB

Content

image-20221207120530-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+44.5 KB

Content

image-20221207120536-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+44.5 KB

Content

image-20221207120601-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+44.5 KB

Content

image-20221207133836-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.1 KB

Content

image-20221207133911-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+46.3 KB

Content

image-20221207134028-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+49.3 KB

Content

image-20221213100007-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+32.7 KB

Content

image-20221213100626-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+35.7 KB

Content

image-20221213100808-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+91.3 KB

Content

image-20221213101040-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+26.3 KB

Content

image-20221213102311-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+49.7 KB

Content

image-20221213102334-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.5 KB

Content

image-20221213102718-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+116.5 KB

Content

image-20221213110952-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+152.8 KB

Content

image-20230213110119-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+182.3 KB

Content

image-20230213110214-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+182.3 KB

Content

image-20230213110506-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+19.8 KB

Content

image-20230302145315-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+35.1 KB

Content

image-20230307135914-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+131.8 KB

Content

image-20230307135932-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+109.7 KB

Content

image-20230308115430-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+2.4 MB

Content

image-20230308115616-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+152.7 KB

Content

image-20230308115701-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+2.4 MB

Content

image-20230426085815-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+190.0 KB

Content

image-20231023103116-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+48.2 KB

Content