Changes for page TrackerD -- LoRaWAN Tracker User Manual

Last modified by Xiaoling on 2025/04/27 16:48

From 50.1 to 49.1 From 51.27 to 51.26

From version 51.26

edited by Xiaoling
on 2022/09/30 15:11

Change comment: There is no comment for this version

To version 50.1

edited by Xiaoling
on 2022/09/30 10:10

Change comment: Uploaded new attachment "1664503831430-500.png", version {1}

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- 1664505654417-133.png

Details

Page properties

Content

@@ -1,13 +7,6 @@
--(% style="text-align:center" %)
--[[image:1664505654417-133.png]]
--
--
--
--
  (% class="wikigeneratedid" %)
  **Table of Contents:**
--{{toc/}}
@@ -14,10 +14,9 @@
  = 1.  Introduction =
++== 1.1  OverView ==
--== 1.1  What is TrackerD ==
--
  (((
  TrackerD is an (% style="color:blue" %)**Open Source LoRaWAN Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**.
  )))
@@ -25,14 +25,10 @@
  (((
  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.
--(((
  TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
--)))
--(((
  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.
@@ -46,7 +46,6 @@
  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
--
  == 1.2  Specifications ==
@@ -61,11 +61,13 @@
  * EEPROM: 520 KB
  * Clock Speed: 32Mhz
++
  (% style="color:blue" %)**Common DC Characteristics:**
  * Supply Voltage: 5V via USB port or Internal li-on battery
  * Operating Temperature: -40 ~~ 60°C
++
  (% style="color:blue" %)**LoRa Spec:**
  * Frequency Range,
@@ -87,10 +87,12 @@
  * Packet engine up to 256 bytes with CRC.
  * LoRaWAN 1.0.3 Specification
++
  (% style="color:blue" %)**Battery:**
  * 1000mA Li-on Battery power (for model TrackerD)
++
  (% style="color:blue" %)**Power Consumption**
  * Sleeping Mode: 200uA
@@ -97,6 +97,9 @@
  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
  * Tracking: max: 38mA
++
++
++
  == 1.3  Features ==
@@ -103,7 +103,7 @@
  * LoRaWAN 1.0.3 Class A
  * ESP32 PICO D4
  * SX1276/78 Wireless Chip
--**    Arduino IDE Compatible
++*    Arduino IDE Compatible
  * Open source hardware / software
  * Regular/ Real-time GPS,BLE,WIFI tracking
  * Built-in3 axis accelerometer (LIS3DH)
@@ -115,6 +115,8 @@
  * Tri-color LED, Alarm button
  * Datalog
++
++
  == 1.4  Applications ==
@@ -121,9 +121,11 @@
  * Logistics and Supply Chain Management
  * Human tracking
--= 2.1  Use TrackerD =
++
++= 2.1  Use TrackerD =
++
  == 2.1  How it works? ==
@@ -130,248 +130,240 @@
  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
--
  == 2.2  Quick guide to connect to LoRaWAN server ==
++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.
--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:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
--[[image:1664501652064-326.png]]
--
--
  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:
++**(% style="color:blue" %)Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
--(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
--
  Each TrackerD is shipped with a sticker with the default device EUI as below:
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
--[[image:1664501677253-891.png]]
++
  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
--**__Add APP EUI in the application:__**
++Add APP EUI in the application
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
--[[image:1664501711466-918.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
--[[image:1664501721248-725.png]]
--[[image:1664501734705-405.png]]
++Add APP KEY and DEV EUI
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
--**__Add APP KEY and DEV EUI:__**
--[[image:1664501784668-703.png]]
++**(% style="color:blue" %)Step 2**:(%%) Power on TrackerD by using the on board switch.
++**(% style="color:blue" %)Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
--(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
++**(% style="color:blue" %)Positioning Mode(SMOD):**
++* **GPS ONLY(Factory Settings): **only get GPS location info.
++* **BLE ONLY: **Only obtain iBeacon info via BLE. Design for Indoor tracking.
++* **GPS/BLE Hybrid: **Combination for Indoor and Outdoor tracking.
--(% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
++User can switch modes by [[changing SMOD>>path:#Positioning_Mode]].
--(% style="color:blue" %)**Positioning Mode(SMOD):**
++== 2.3  Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- ==
--* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
--* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
--* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
--User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
++=== 2.3.1  Uplink FPORT=5, Device Status ===
--== 2.3  Uplink Payload ==
++=== 2.3.2  Uplink FPORT= , Realtime GNSS Positioning ===
++The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won’t work on DR0 on US915/AU915 frequency band. )
--=== 2.3.1  Uplink FPORT~=5, Device Status ===
++|(((
++**Size**
++**(bytes)**
++)))|4|4|2|1|(((
++2
--=== 2.3.2  Uplink FPORT~= , Realtime GNSS Positioning ===
++(optional )
++)))|(((
++2
--
--The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
--
--
--(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
--|=(% scope="row" style="width: 50px;" %)(((
--**Size(bytes)**
--)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
--2(optional)
--)))|(% style="width:87px" %)(((
--2(optional)
++(optional)
  )))
--|=(% 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:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
++|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|(((
++[[Alarm &>>path:#Alarm]]
--[[image:1664501958445-288.png]]
++[[BAT>>path:#Alarm]]
++)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]]
--==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
--(% 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:"]]
--==== (% style="color:blue" %)**FLAG:**(%%) ====
++**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" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
--|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H2.3.4BLEpositioningPayload28Fport229"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version
++|**Size(bit)**|1 bit|1bit|14 bits
++|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]]
--**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
++**FLAG:**
++|**Size(bit)**|2 bits|1bit|5 bits
++|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version
--==== (% style="color:blue" %)**Location info:**(%%) ====
--* Latitude: 02863D68     ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://      //value = 02863D68 /1000000 = 42.351976//
--* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://      //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
++**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A  **
--(% style="color:red" %)**Important note:**
--1.  When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
++**Location info:**
--2.  In firmware version v1.5, Roll & Pitch is disabled by default.
++* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~://
--3.  When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
++//value = 02863D68 /1000000 = 42.351976//
++* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://
--[[image:1664502116362-706.png]]
++//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
++Important note:
--4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
++1. When power is low (<2.84v), GPS won’t be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
++1. In firmware version v1.5, Roll & Pitch is disabled by default.
++1. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
--[[image:1664502166010-515.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
++1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
--==== (% style="color:blue" %)**Alarm:**(%%) ====
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
--Example:  0x4B & 0x40 >> 6 = 0x01
++* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01
++* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV).
++The battery info shows the current voltage, for **TrackerD** version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
--==== (% style="color:blue" %)**BAT:**(%%) ====
--Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
++* > 4.0v : 80% ~~ 100%
++* 3.85v ~~3.99v: 60% ~~ 80%
++* 3.70v ~~ 3.84v: 40% ~~ 60%
++* 3.40v ~~ 3.69v: 20% ~~ 40%
++* < 3.39v: 0~~20%
--The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
++* **LON: **Enable/Disable LED activity for uplink
--* > 4.0v :              80% ~~ 100%
--* 3.85v ~~3.99v:    60% ~~ 80%
--* 3.70v ~~ 3.84v:   40% ~~ 60%
--* 3.40v ~~ 3.69v:   20% ~~ 40%
--* < 3.39v:             0~~20%
++0x00: Disable LED indicator.
++0x01: Enable LED indicator (Default Value)
--==== (% style="color:blue" %)**LON:**(%%) ====
++* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
++* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree
--
--Enable/Disable LED activity for uplink
--0x00:   Disable LED indicator.
--0x01:   Enable LED indicator (Default Value)
++=== 2.3.3  Uplink FPORT= , History GNSS Positioning ===
--==== (% style="color:blue" %)**Hum:**(%%) ====
--0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
++=== 2.3.4  BLE positioning Payload(Fport=2) ===
++Different MODE has different payload:
--==== (% style="color:blue" %)**Tem:**(%%) ====
++**MODE=2**
--011A =if (0x011A & 0x8000 = 1 ):   value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
++|(((
++**Size**
++**(bytes)**
++)))|16|4|4|2|4|2|1
++|**Value**|[[UUID>>path:#Location]]|(((
++iBeacon
++MAJOR
++)))|(((
++iBeacon
--=== 2.3.3  Uplink FPORT~= , History GNSS Positioning ===
++MINOR
++)))|(((
++iBeacon Measured
++Power
++)))|(((
++iBeacon
++RSSI
++)))|(((
++[[Alarm &>>path:#Alarm]]
--=== 2.3.4  BLE positioning Payload(Fport2) ===
++[[BAT>>path:#Alarm]]
++)))|[[FLAG>>path:#Flag]]
--Different MODE has different payload:
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
--**MODE=2**
--(% 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" %)(((
--iBeacon MAJOR
--)))|(% style="width:63px" %)(((
--iBeacon MINOR
--)))|(% style="width:71px" %)(((
--iBeacon Measured Power
--)))|(% style="width:50px" %)(((
--iBeacon RSSI
--)))|(% style="width:47px" %)(((
--[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
--)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
++* **BAT**: Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
++* **MODE: **Define the payload format.
++* **UUID: **The uuid from the strongest iBeacon.
++* **MAJOR**: The MAJOR from the strongest iBeacon.
++* **MINOR**: The MAJOR from the strongest iBeacon.
++* **Measured** **Power**: The Measured Power from the strongest iBeacon.
++* **RSSI**: The RSSI from the strongest iBeacon.
--[[image:1664502425687-834.png]]
--* (% style="color:#037691" %)**BAT: **  (%%)    Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
--* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
--* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
--* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
--* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
--* (% style="color:#037691" %)**Measured Power: ** (%%)   The Measured Power from the strongest iBeacon.
--* (% style="color:#037691" %)**RSSI:  **    (%%) The RSSI from the strongest iBeacon.
--
  === 2.3.5  Add Payload format in TTN V3 ===
--
  In TTN V3, use can add a custom payload so it shows friendly.
--In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
++In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
--[[image:1664502649601-895.png]]
--
--
  Add the decoder from this link:
  Save the change the uplink message will be parsed. As below:
--[[image:1664502676891-606.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
++
++
  == 2.4  Integrate with Datacake ==
  After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
--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]]
++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:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
--[[image:1664502695771-538.png]]
--
--
  == 2.5  Integrate with Tago ==
@@ -379,8 +379,8 @@
  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:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
--[[image:1664502715371-321.png]]
@@ -387,10 +387,10 @@
  == 2.6  Alarm Mode ==
--User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
++User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
--Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
++Once enter Alarm mode, the **GREEN LED** will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
  Two ways to exit alarm mode:
@@ -398,239 +398,230 @@
  * Server send a downlink command to exit.
  * User fast press the RED button 10 times.
--When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
++When exit alarm mode, **RED LED** will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
++== 2.7  Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
--== 2.7  Sports Mode ==
--
  == 2.8  LED Status ==
--(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
--|(% style="width:150px" %)**Event**|(% style="width:200px" %)**Action**|(% style="width:150px" %)**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
--|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
--|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
--|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
--|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
--|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
--|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
--|(% 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
++|**Event**|**Action**|**AT+LON to control on/off**
++|**Power On**|**BLUE, RED , Green** flash once|N/A
++|**Join request**|**Green** led fast blink once (200ms)|Yes
++|**Join Success**|**Green** led on 5 second|N/A
++|**Fixing Location**|**BLUE **blinks 200ms per second|Yes
++|**Fixed and uplink**|**GREEN **blinks twice (200ms per blink)|Yes
++|**Fail Fix and uplink**|**RED **blinks twice (200ms per blink)|Yes
++|**Enter Alarm mode**|**RED **on for 3 seconds|Yes
++|**Uplink under Alarm**|**RED **on for 1 second|Yes
++|**Exit Alarm**|**BLUE **led on 5 second|Yes
++|**Get Downlink**|**GREEN** led on 1 second|Yes
++|**Movement Detect**|**RED **on 500ms|N/A
--== 2.9  Button Function ==
--(% style="color:green" %)**RESET button:**
--[[image:1664502835802-546.png]]
++== 2.9  Button Function ==
++
++**RESET button:**
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
++
  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
--(% style="color:red" %)**RED button:**
++**RED button:**
--[[image:1664502854406-763.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
++|**Function**|**Action**|**Description**
++|Send Alarm|Keep Pressing **RED** button for more than 5 seconds|Enter Alarm Mode.  See [[Alarm Mode>>path:#Alarm_Mode]]
++|Exit Alarm Mode|Fast press the **RED** button 10 times|Exit Alarm Mode
++|Enter Deep Sleep Mode|Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy.
--(% border="2" style="background-color:#ffffcc; color:green; width:627px" %)
--|(% style="width:135px" %)**Function**|(% style="width:220px" %)**Action**|(% style="width:265px" %)**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.6AlarmMode"]]
--|(% 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.10  USB Port Function ==
++== 2.10  USB Port Function ==
++
  The USB interface of TrackerD has below functions:
  * Power on the device
  * Recharge the battery
--* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
--* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
++* [[Configure Device>>path:#AT_Command]]
++* [[Upgrade Firmware>>path:#upgrade_image]]
--= 3.  Configure TrackerD via AT command or LoRaWAN downlink =
--User can configure TrackerD via AT Command or LoRaWAN Downlink.
--LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
++= 3.  Configure TrackerD via AT command or LoRaWAN downlink =
--== 3.1  Access AT Command ==
++User can configure TrackerD via AT Command or LoRaWAN Downlink.
++LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
--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.
++== 3.1  Access AT Command ==
--[[image:1664502999401-486.png]]
++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:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
--In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
++In PC, User needs to set serial tool baud rate to **115200** to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
--[[image:1664503022490-662.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
--[[image:1664503035713-500.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
--[[image:1664503047675-651.png]]
--
--
  == 3.2  Command Set ==
  === 3.2.1  Set Transmit Interval ===
--
  Set device uplink interval.
--* (% style="color:blue" %)**AT Command:**
++* AT Command:
--(% style="color:#037691" %)**AT+TDC=xxx **
++AT+TDC=xxx
--Example:   AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
++Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
--* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
++* Downlink Payload (prefix 0x01):
--(% style="color:#037691" %)**0x01 00 01 2C**  (%%)   ~/~/  Same as AT+TDC=300000
++0x01 00 01 2C     ~/~/ Same as AT+TDC=300000
--
  === 3.2.2  Set Alarm Packet transmission interval ===
--
  Set alarm packet transmit interval
--* (% style="color:blue" %)**AT Command:**
++* AT Command:
--(% style="color:#037691" %)**AT+ATDC=xx. **
++AT+ATDC=xx.
--Example:  AT+ATDC=60000    **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
++Example: AT+ATDC=60000  à Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
--* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
++* Downlink Payload (prefix 0xB1):
--(% style="color:#037691" %)**0xB1 00 00 3C **   (%%)     ~/~/  Same as AT+ATDC=60000
++0xB1 00 00 3C    ~/~/Same as AT+ATDC=60000
++=== 3.3.3  Set Sports Mode Packet transmission interval ===
--=== 3.2.3  Set Sports Mode Packet transmission interval ===
--
--
  Set sports packet transmit interval
--* (% style="color:blue" %)**AT Command:**
++* AT Command:
--(% style="color:#037691" %)**AT+MTDC=xx. **
++AT+MTDC=xx.
-- Example:  AT+MTDC=300000    **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
++ Example: AT+MTDC=300000  à Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
--* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
++* Downlink Payload (prefix 0x03):
--(% style="color:#037691" %)**0x03 00 01 2C**  (%%)     ~/~/  Same as AT+ MTDC=3000000
++0x03 00 01 2C    ~/~/Same as AT+ MTDC=3000000
--=== 3.2.4  Exit Alarm ===
++=== 3.3.4  Exit Alarm ===
--
  Server send downlink command to exit Alarm mode
--* (% style="color:blue" %)**AT Command: No AT Command**
++* AT Command:
--* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
++No AT Command
--(% style="color:#037691" %)**0x02 01**    (%%)   ~/~/  Exit Alarm Mode
++* Downlink Payload (prefix 0x02):
++0x02 01     ~/~/ Exit Alarm Mode
--=== 3.2.5  Disable/Enable LED flash ===
++=== 3.3.5  Disable/Enable LED flash ===
  Disable/Enable LED for position, downlink and uplink
--* (% style="color:blue" %)**AT Command:**
++* AT Command:
--(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
++AT+LON=xx.  (Disable (0), Enable (1), default:1)
-- Example: AT+LON=0   **~-~-> ** Disable LED for position, downlink and uplink.
++ Example: AT+LON=0 à Disable LED for position, downlink and uplink.
--* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
++* Downlink Payload (prefix 0xAE):
--(% style="color:#037691" %)**0xAE 00 **   (%%)    ~/~/  Same as AT+LON=0
++0xAE 00    ~/~/Same as AT+LON=0
--=== 3.2.6  Disable/Enable movement detect (Debug Only) ===
++=== 3.3.6  Disable/Enable movement detect (Debug Only) ===
  User can use this feature to check and set thread hole of movement detect
--* (% style="color:blue" %)**AT Command:**
++* AT Command:
--(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
++AT+INTWK=xx.  (Disable (0), Enable (1), default:0)
-- Example:  AT+ INTWK =1   **~-~->   ** Enable detect movement.
++ Example: AT+ INTWK =1 à Enable detect movement.
--* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
++* Downlink Payload (prefix 0xAF):
--(% style="color:#037691" %)**0xAF 01 ** (%%)    ~/~/  Same as AT+ INTWK =1
++0xAF 01    ~/~/Same as AT+ INTWK =1
--=== 3.2.7  Set Positioning Mode ===
++=== 3.3.7  Set Positioning Mode ===
--
  SMOD define the how TrackerD scan and uplink date.
--GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
++GPS室外定位模式：设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
--BLE室内定位模式：   设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
++    BLE室内定位模式：设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
--GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
++    GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
--运动模式：               设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
++运动模式：设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
--* (% style="color:blue" %)**AT Command:**
--(% style="color:#037691" %)**AT+SMOD=xx. **
++* AT Command:
++AT+SMOD=xx.
-- **Example:**
++ Example:
--  AT+ SMOD =1,0    **~-~-> ** GPS+ BAT+ State+Tem&Hum
++  AT+ SMOD =1,0    à GPS+ BAT+ State+Tem&Hum
--  AT+ SMOD =1,1    **~-~->**  GPS +BAT State
++  AT+ SMOD =1,1    à GPS +BAT State
--  AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
++  AT+ SMOD =2,3    à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
--* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
++* Downlink Payload (prefix 0xA5):
--(% style="color:#037691" %)**0xA5 01 00**    (%%)   ~/~/  Same as AT+ SMOD =1,0
++0xA5 01 00     ~/~/ Same as AT+ SMOD =1,0
++=== 3.3.8  Set MAX GPS position time ===
--=== 3.2.8  Set MAX GPS position time ===
--
--
  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.
@@ -637,60 +637,60 @@
  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:**
++* AT Command:
--(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
++AT+FTIME=xx  à Set to use xx as max fix time.
--Example:  AT+FTIME=150
++Example: AT+FTIME=150
--* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
++* Downlink Payload (prefix 0xAA):
--(% style="color:#037691" %)**0xAA 00 96 ** (%%)      ~/~/  Set AT+FTIME=150
++0xAA 00 96      ~/~/Set AT+FTIME=150
++
  === 3.3.9  Set PDOP value for GPS fix accuracy ===
++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.
--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:**
++* AT Command:
--(% style="color:#037691" %)**AT+PDOP=2.5 **  (%%) **~-~->  ** Set PDOP to 2.5
++AT+PDOP=2.5  à Set PDOP to 2.5
--* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
++* Downlink Payload (prefix 0xAD):
--(% style="color:#037691" %)**0xAD 00 0A**   (%%)   ~/~/  Set AT+PDOP=1       (0x0A / 10 =1)
++0xAD 00 0A    ~/~/Set AT+PDOP=1    (0x0A / 10 =1)
--(% style="color:#037691" %)**0xAD 00 19**   (%%)   ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
++0xAD 00 19    ~/~/Set AT+PDOP=2.5    (0x19 / 10 =2.5)
--(% style="color:#037691" %)**0xAD 00 46**    (%%)  ~/~/  Set AT+PDOP=7       (0x46 / 10 =7)
++0xAD 00 46     ~/~/Set AT+PDOP=7     (0x46 / 10 =7)
++Disable/Enable the confirmation mode
++* AT Command:
--Disable/Enable the confirmation mode
++AT+CFM=xx.
--* (% style="color:blue" %)**AT Command:**
++ Example:
--(% style="color:#037691" %)**AT+CFM=xx. **
++  AT+ CFM=0    à Disable confirmation
++  AT+ CFM=1    à Enable confirmation
--**~ Example:**
--  AT+ CFM=0    **~-~->   ** Disable confirmation
++* Downlink Payload (prefix 0x05):
--  AT+ CFM=1    **~-~->  **  Enable confirmation
++0x05 01      ~/~/ Same as AT+ SMOD =1
--* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
--(% style="color:#037691" %)**0x05 01 **(%%)         ~/~/  Same as AT+ SMOD =1
@@ -703,39 +703,35 @@
  == 5.1  Firmware Change Log ==
--
  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
--
  == 5.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:
--User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
++**(% style="color:blue" %)Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
--(% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
++**(% style="color:blue" %)Step2:** (%%) Install CH9102 driver in the PC.
--
--(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
--
  After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
--(% style="color:blue" %)**Step3：**(%%) Download and Install Flash Tool:  [[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]
++**(% style="color:blue" %)Step3：**(%%) Download and Install Flash Tool:
++[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]
--(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
++**(% style="color:blue" %)Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
--[[image:1664503563660-578.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]]
--[[image:1664503574618-659.png]]
++**(% style="color:blue" %)Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
--(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
--
  [[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
@@ -745,17 +745,16 @@
  ESP_LORA-eeprom-class.bin @ 0x10000
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]]
--[[image:1664503593459-435.png]]
++After upgrade finish, it will show finish as below:
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]]
--After upgrade finish, it will show finish as below:
--[[image:1664503611848-385.png]]
--
  = 6.  Developer Guide =
@@ -765,26 +765,28 @@
  === 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]]
++* Download the latest Arduino software (IDE) from the Arduino official website
--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]]
++[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]
++Install IDE on PC, open and click File ~-~-> Preference, add the following URL  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
--[[image:1664503635019-941.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
++* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it.
--* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) find the esp32 information and install it.
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
--[[image:1664503715811-892.png]]
++* Download the latest TrackerD from the dragino github
++[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
--* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
--Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
++Put the Library in the TrackerD directory into the libraries file in the Arduino directory
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
--[[image:1664503752288-974.png]]
@@ -791,21 +791,21 @@
  == 6.2  Source Code ==
--* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
++* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
--[[image:1664503794261-827.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
++* Click to upload
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
--* (% style="color:blue" %)**Click to upload**
++* Check the result, if the upload is successful, as shown below, open the serial port to view the data
--[[image:1664503808294-336.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]]
--* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
--[[image:1664503824081-592.png]]  [[image:1664503831430-500.png]]
@@ -812,10 +812,11 @@
  = 7.  FAQ =
++
  == 7.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.
++User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
@@ -845,6 +845,7 @@
  (% style="color:blue" %)**XXX**(%%): The default frequency band
  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
++* (% style="color:red" %)**CN470**(%%): Default frequency band CN470
  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
@@ -852,25 +852,33 @@
  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
  * (% style="color:red" %)**US915**(%%): Default frequency band US915
++
  = 9.  Packing Info =
  **Package Includes**:
--* TrackerD LoRaWAN GPS/BLE Tracker x 1
--* USB recharge & program cable x 1
++* TrackerD x 1
++* Rechargeable cable x 1
++* Program Cable x 1
  **Dimensions and Weight**:
--* Device Size: 85 x 48 x 15 cm
--* Weight: 50g
++* Device Size: 85 x 48 x 15 mm/pcs
++* Weight: 55g/pcs
--= 10.  Support =
++= 10.  Support =
++
  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
--* 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]]
++* 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]]
++
++
++
++
  = 11.  Reference =

1664505654417-133.png

Author

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

Size

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

Content