Changes for page TrackerD -- LoRaWAN Tracker User Manual

Last modified by Bei Jinggeng on 2025/08/01 17:45

From 59.2 to 59.3 From 144.1 to 145.1

From version 59.3

edited by Edwin Chen
on 2022/10/08 18:10

Change comment: There is no comment for this version

To version 144.1

edited by Edwin Chen
on 2022/11/22 12:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 31 added, 0 removed)

Details

Page properties

Content

@@ -1,5 +3,3 @@
--==   ==
--
  (% style="text-align:center" %)
  [[image:1664505654417-133.png]]
@@ -16,7 +16,6 @@
  = 1.  Introduction =
--
  == 1.1  What is TrackerD ==
@@ -48,7 +48,6 @@
  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
--
  == 1.2  Specifications ==
@@ -99,6 +99,7 @@
  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
  * Tracking: max: 38mA
++
  == 1.3  Features ==
@@ -117,6 +117,7 @@
  * Tri-color LED, Alarm button
  * Datalog
++
  == 1.4  Applications ==
@@ -123,8 +123,8 @@
  * Logistics and Supply Chain Management
  * Human tracking
--= 2.1  Use TrackerD =
++= 2.  Use TrackerD =
  == 2.1  How it works? ==
@@ -132,7 +132,6 @@
  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 ==
@@ -174,48 +174,57 @@
  **__Add APP KEY and DEV EUI:__**
--[[image:1664501784668-703.png]]
++[[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||alt="1654671889112-678.png"]]
++(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
--(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
++(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
++[[image:1664502835802-546.png]]
++
  (% 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.
--== 2.3 Positioning Mode(SMOD) ==
++== 2.3  Positioning Mode(SMOD) ==
++
  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 ONLY:              **(%%)Only obtain iBeacon info via BLE and 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.
++* (% 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" %)**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"]].
--== 2.3  Uplink Payload ==
++== 2.4  Uplink Payload ==
++=== 2.4.1  Uplink FPORT~=5, Device Status ===
--=== 2.3.1  Uplink FPORT~=5, Device Status ===
--Uplink the device configures with FPORT=5. Once LGT92 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours.
++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.
--|=(% style="width: 150px;" %)**Size (bytes)**|=(% style="width: 233px;" %)**1**|=(% style="width: 150px;" %)**2**|=(% style="width: 164px;" %)**1**|=(% style="width: 215px;" %)**1**|=(% style="width: 94px;" %)2|=(% style="width: 516px;" %)**2**|=(% style="width: 516px;" %)1
--|(% style="width:150px" %)**Value**|(% style="width:233px" %)Sensor Model|(% style="width:150px" %)Firmware Version|(% style="width:164px" %)Frequency Band|(% style="width:215px" %)Sub-band|(% style="width:94px" %)BAT|(% style="width:516px" %)SMOD|(% style="width:516px" %)Status
++Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
--[[image:image-20221006181357-2.png]]
--Example Payload (FPort=5):  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]]
++(% 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
--**Sensor Model**: For TrackerD, this value is 0x13.
++[[image:1665301570342-765.png]]
--**Firmware Version**: 0x0100, Means: v1.0.0 version.
--**Frequency Band**:
++(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
++(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
++
++(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
++
++(% style="color:#037691" %)**Frequency Band**:
++
  *0x01: EU868
  *0x02: US915
@@ -236,27 +236,64 @@
  *0x0a: AS923-3
--**Sub-Band**: value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
++Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
--**BAT**: shows the battery voltage for TrackerD.
++(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
--Ex1: 0x0B3A = 2874mV
++(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
++
  Use can also get the Device Status uplink through the downlink command:
--=== 2.3.2  Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
++(% 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
--User can use **AT+SMOD=1,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band.
++(% style="color:blue" %)**     SMOD：**
++(% style="color:red" %)**      1 :** (%%)  GPS ONLY
--(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
--|=(% scope="row" style="width: 50px;" %)(((
++(% style="color:red" %)**      2 :** (%%)  BLE ONLY
++
++(% style="color:red" %)**      3 :**  (%%) GPS/BLE Hybrid
++
++
++(% 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" %)**      1 :** (%%)   Disable uploading on-board Temperature and humidity values
++
++
++(% style="color:blue" %)**      BLE_Settings:**
++
++(% style="color:red" %)**      1: ** (%%)  BLE Positioning with Strongest iBeacon
++
++(% style="color:red" %)**      2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% 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"]]
++
++
++=== 2.4.2  Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
++
++
++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,
++
++
++(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
++|=(% scope="row" style="width: 60px;" %)(((
  **Size(bytes)**
--)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
++)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
--)))|(% style="width:87px" %)(((
++)))|(% style="width:30px" %)(((
  )))
  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
@@ -263,7 +263,7 @@
  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
--[[image:1664501958445-288.png]]
++[[image:1665301636888-168.png]]
  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
@@ -272,10 +272,11 @@
  |=(% 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:**(%%) ====
--(% 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
++(% 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:"]]
  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
@@ -286,7 +286,6 @@
  * 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//
--
  (% style="color:red" %)**Important note:**
 .  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.
@@ -305,12 +305,12 @@
  ==== (% style="color:blue" %)**Alarm:**(%%) ====
--Example:  0x4B & 0x40 >> 6 = 0x01
++**Example: ** 0x4B & 0x40 >> 6 = 0x01
  ==== (% style="color:blue" %)**BAT:**(%%) ====
--Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
++**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
  (((
  The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
@@ -323,16 +323,33 @@
  * < 3.39v:             0~~20%
++==== (% style="color:blue" %)**MOD:**(%%) ====
++
++**Example: ** (0x60>>6) & 0x3f =1
++
++**Set the format of GPS data uplink link：**
++
++(% style="color:#037691" %)**0x00:** (%%)  Enable uploading on-board Temperature and humidity values
++(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
++
++
++**Set the format of BLE data uplink link：**
++
++(% style="color:#037691" %)**0x01: ** (%%)  BLE Positioning with Strongest iBeacon
++
++
  ==== (% style="color:blue" %)**LON:**(%%) ====
++**Example:** (0x60>>5) & 0x01=1.
++
  Enable/Disable LED activity for uplink
  (((
--0x00:   Disable LED indicator.
++(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
  )))
  (((
--0x01:   Enable LED indicator (Default Value)
++(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
  )))
@@ -346,39 +346,55 @@
 A =if (0x011A & 0x8000 = 1 ):   value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
--=== 2.3.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
++=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
--The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
++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)
--(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
--|=(% scope="row" style="width: 50px;" %)(((
++
++(% 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:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
++)))|(% 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" %)(((
  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
++(% class="wikigeneratedid" %)
++[[image:1665301687277-443.png]]
--=== 2.3.4  Uplink FPORT~=4, History GNSS Positioning ===
++=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
--Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
--**Note for this mode:**
++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.
++
++(% style="color:red" %)**Note for this mode:**
++
  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
--* b) TrackerD will send data in **CONFIRMED Mode** when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
++* b)  TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
++* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
  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
++[[image:image-20221009160309-2.png]]
--=== 2.3.5  BLE positioning Payload(Fport2) ===
++=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
--Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
++TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink.
++
++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)**
@@ -398,19 +398,43 @@
  [[image:1664502425687-834.png]]
--* (% style="color:#037691" %)**BAT: **  (%%)    Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
++* (% 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" %)**MINOR:**  (%%)The MINOR 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 ===
++=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
--In TTN V3, use can add a custom payload so it shows friendly.
++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.
++
++
++(% 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:"]]
++
++(% class="wikigeneratedid" %)
++[[image:1667288597595-714.png||height="212" width="1151"]]
++
++
++* (% 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.
++
++
++=== 2.4.7  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**
@@ -417,53 +417,56 @@
  [[image:1664502649601-895.png]]
--Add the decoder from this link:
++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]]
++== 2.5  Integrate with Datacake ==
--== 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]]
--)))
  [[image:1664502695771-538.png]]
++== 2.6  Integrate with Tago ==
--== 2.5  Integrate with Tago ==
++After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot.
--(((
--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/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
--)))
  [[image:1664502715371-321.png]]
++== 2.7  Datalog Feature ==
--== 2.6 Datalog Feature ==
++total 273 entries,by default,
--== 2.6  Alarm Mode ==
++User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
++Example use case.
++[[image:image-20221009234703-2.png||height="328" width="899"]]
++
++
++[[image:image-20221009234629-1.png||height="390" width="577"]]
++
++
++== 2.8  Alarm Mode ==
++
++
  (((
  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
  )))
@@ -470,15 +470,15 @@
  (((
--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 (% 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.
  )))
  (((
--Two ways to exit alarm mode:
++**Two ways to exit alarm mode:**
  )))
--* Server send a downlink command to exit.
++* Server sends a downlink command to exit.
  * User fast press the RED button 10 times.
  (((
@@ -486,23 +486,22 @@
  )))
++== 2.9  Transport Mode ==
--== 2.7  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.
--== 2.8  LED Status ==
++== 2.10  LED Status ==
--(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
++(% 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**
  |(% 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" %)**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
@@ -510,9 +510,10 @@
  |(% 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.9  Button Function ==
++== 2.11  Button Function ==
++
  (% style="color:blue" %)**RESET button:**
  [[image:1664502835802-546.png]]
@@ -525,15 +525,16 @@
  [[image:1664502854406-763.png]]
--(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
--|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**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"]]
++(% border="1" style="background-color:#ffffcc; width:510px" %)
++|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**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.10  USB Port Function ==
++== 2.12  USB Port Function ==
++
  The USB interface of TrackerD has below functions:
  * Power on the device
@@ -541,6 +541,7 @@
  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
++
  = 3.  Configure TrackerD via AT command or LoRaWAN downlink =
@@ -549,7 +549,6 @@
  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
--
  == 3.1  Access AT Command ==
@@ -565,11 +565,9 @@
  [[image:1664503022490-662.png]]
--
  [[image:1664503035713-500.png]]
--
  [[image:1664503047675-651.png]]
@@ -576,7 +576,6 @@
  == 3.2  Command Set ==
--
  === 3.2.1  Set Transmit Interval ===
@@ -594,7 +594,6 @@
  (% style="color:#037691" %)**0x01 00 01 2C**  (%%)   ~/~/  Same as AT+TDC=300000
--
  === 3.2.2  Set Alarm Packet transmission interval ===
@@ -612,7 +612,6 @@
  (% style="color:#037691" %)**0xB1 00 00 3C **   (%%)     ~/~/  Same as AT+ATDC=60000
--
  === 3.2.3  Set Transport Mode Packet transmission interval ===
@@ -627,10 +627,9 @@
  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
--(% style="color:#037691" %)**0x03 00 01 2C**  (%%)     ~/~/  Same as AT+ MTDC=3000000
++(% style="color:#037691" %)**0x03 00 01 2C**  (%%)     ~/~/  Same as AT+MTDC=3000000
--
  === 3.2.4  Exit Alarm ===
@@ -643,7 +643,6 @@
  (% style="color:#037691" %)**0x02 01**    (%%)   ~/~/  Exit Alarm Mode
--
  === 3.2.5  Disable/Enable LED flash ===
@@ -661,7 +661,6 @@
  (% style="color:#037691" %)**0xAE 00 **   (%%)    ~/~/  Same as AT+LON=0
--
  === 3.2.6  Disable/Enable Transport Mode ===
@@ -671,41 +671,60 @@
  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
--Example:  AT+ INTWK =1   **~-~->   ** Enable Transport Mode.
++Example:  AT+INTWK=1   **~-~->   ** Enable Transport Mode.
  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
--(% style="color:#037691" %)**0xAF 01 ** (%%)    ~/~/  Same as AT+ INTWK =1
++(% style="color:#037691" %)**0xAF 01 ** (%%)    ~/~/  Same as AT+INTWK=1
--
  === 3.2.7  Set Positioning Mode ===
--SMOD define the how TrackerD scan and uplink data:
++SMOD define how TrackerD scan and uplink data:
  * (% style="color:blue" %)**AT Command:**
--(% style="color:#037691" %)**AT+SMOD=xx. **
++(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
++(% style="color:#037691" %)** aa:**
-- **Example:**
++* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
--  AT+ SMOD =1,0    **~-~-> ** GPS+ BAT+ State+Tem&Hum
++* (% 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.
--  AT+ SMOD =1,1    **~-~->**  GPS +BAT State
++* (% 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.
--  AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
++(% style="color:#037691" %)**bb:**
++* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
--* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
++* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
--(% style="color:#037691" %)**0xA5 01 00**    (%%)   ~/~/  Same as AT+ SMOD =1,0
++(% style="color:#037691" %)**cc:   **
++* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
++
++* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
++(% style="color:blue" %)**Example:**
++  AT+SMOD=1,0,0    ~-~->    GPS+ BAT+ State+Tem&Hum
++
++  AT+SMOD=1,1,0    ~-~->    GPS +BAT State
++
++  AT+SMOD=2,0,1    ~-~->    (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
++
++  AT+SMOD=2,0,2    ~-~->    (WiFi)SSID+Rssi+BAT+State
++
++
++* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
++
++(% style="color:#037691" %)**0xA5 01 00 00**    (%%)   ~/~/  Same as AT+SMOD=1,0,0
++
++
  === 3.2.8  Set MAX GPS position time ===
@@ -712,7 +712,7 @@
  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.
++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:**
@@ -719,7 +719,7 @@
  (% style="color:#037691" %)**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):**
@@ -727,10 +727,9 @@
  (% style="color:#037691" %)**0xAA 00 96 ** (%%)      ~/~/  Set AT+FTIME=150
++=== 3.2.9  Set PDOP value for GPS fix accuracy ===
--=== 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.
@@ -752,26 +752,108 @@
--Disable/Enable the confirmation mode
++**Disable/Enable the confirmation mode**
  * (% style="color:blue" %)**AT Command:**
--(% style="color:#037691" %)**AT+CFM=xx. **
++(% style="color:#037691" %)**AT+CFM=xx**
  **~ 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):**
--(% style="color:#037691" %)**0x05 01 **(%%)         ~/~/  Same as AT+ SMOD =1
++(% style="color:#037691" %)**0x05 01 **(%%)         ~/~/  Same as AT+CFM=1
++=== 3.2.10  Auto Send None-ACK messages ===
++
++TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
++
++
++* (% style="color:blue" %)**AT Command: AT+PNACKMD**
++
++The default factory setting is 0.
++
++
++**Command Example Function Response:**
++
++(% style="color:#037691" %)**AT+PNACKMD=1**  (%%)  ~/~/  Poll None-ACK message OK
++
++
++* (% style="color:blue" %)**Downlink Command: 0x34**
++
++Example: 0x3401     ~/~/  Same as AT+PNACKMD=1
++
++
++=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
++
++
++BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
++
++(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
++
++(% style="color:blue" %)**AT Command:**
++
++     (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%)  ~/~/ Set BLEMASK = 123456
++
++     (% style="color:#037691" %)**AT+BLEMASK=0**  (%%)             ~/~/ disable BLEMASK
++
++(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
++
++Example:  0xB2010203040506    ~/~/ Set BLEMASK to 123456
++
++
++=== 3.2.12  Set WiFIMASK to filter WiFi SSID（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.
++
++(% 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+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
++
++     (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%)        ~/~/ disable WiFiMASK
++
++(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
++
++Example:  0xB3010203040506    ~/~/ Set WiFiMASK to 123456
++
++
++=== 3.2.13  Disable/Enable Information printing（Since firmware 1.4.1） ===
++
++
++Users can use this feature to enable/disable Information printing.
++
++(% 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:**
++
++(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
++
++
++(% style="color:blue" %)**Downlink Payload:0X24**
++
++Example: 0x24 01 ~/~/ Same as AT+CHE=1
++
++
  = 4.  Setting for Different Scenarios =
@@ -778,7 +778,6 @@
  = 5.  Upload Firmware =
--
  == 5.1  Firmware Change Log ==
@@ -785,7 +785,6 @@
  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
--
  == 5.2  How to upgrade firmware ==
@@ -812,34 +812,33 @@
  [[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:
--[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
++[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
--Users need to use below files:
++**Users need to use below files:**
  boot_app0.bin @0e000
--ESP_LORA-eeprom-class.bin @ 0x10000
++US915.bin @ 0x10000(Select the bin file of the frequency band you need)
--[[image:1664503593459-435.png]]
++[[image:image-20221118105220-2.png]]
  After upgrade finish, it will show finish as below:
--[[image:1664503611848-385.png]]
++[[image:image-20221118105402-4.png]]
  = 6.  Developer Guide =
--
  == 6.1  Compile Source Code ==
--
  === 6.1.1  Set up ARDUINO compile environment ===
@@ -851,12 +851,24 @@
  [[image:1664503635019-941.png]]
++
  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
  [[image:1664503715811-892.png]]
++(% 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-20221024105643-1.png]]
++
++**~                                                                                Figure1**
++
++
++[[image:image-20221024105643-2.png]]
++
++                                                                                   **Figure2**
++
++
  * **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:
@@ -865,7 +865,6 @@
  [[image:1664503752288-974.png]]
--
  == 6.2  Source Code ==
@@ -886,10 +886,8 @@
  [[image:1664503824081-592.png]]  [[image:1664503831430-500.png]]
--
  = 7.  FAQ =
--
  == 7.1  How to change the LoRa Frequency Bands/Region? ==
@@ -896,7 +896,6 @@
  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? ==
@@ -915,45 +915,246 @@
  |(% 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
--= 8.  Order Info =
++== 7.3  Notes on using different serial port tools for TrackerD ==
++=== 7.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.
++
++(% class="wikigeneratedid" %)
++[[image:image-20221102140621-1.png]]
++
++
++
++When using AT commands, the data flow needs to be adjusted to XON/XOFF
++
++[[image:image-20221102140638-2.png]]
++
++
++=== 7.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.
++
++
++[[image:image-20221102140704-3.png]]
++
++
++[[image:image-20221102140712-4.png]]
++
++
++=== 7.3.3  PUTTY ===
++
++
++[[image:image-20221102140748-5.png]]
++
++
++Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty.
++
++
++[[image:image-20221102140801-6.png]]
++
++
++== 7.4 How to modify source code to compile different frequency band bin file? ==
++
++
++(% class="box infomessage" %)
++(((
++(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
++See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
++)))
++
++**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
++
++
++[[image:image-20221116111844-1.png||height="227" width="782"]]
++
++
++
++**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
++
++
++[[image:image-20221116111844-2.png||height="262" width="781"]]
++
++
++
++**3. Compile the AS923_JP band, please refer to the intention shown**
++
++
++[[image:image-20221116111844-3.png||height="338" width="746"]]
++
++
++
++**4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.**
++
++
++[[image:image-20221116111844-4.png||height="641" width="739"]]
++
++
++[[image:image-20221116111844-5.png||height="551" width="708"]]
++
++
++= 8  Trouble Shooting =
++
++== 8.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
++)))
++
++
++== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
++
++
++(((
++ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
++)))
++
++
++== 8.3  Problem after Upgrading Firmware ==
++
++=== 8.3.1 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
++)))
++
++
++[[image:image-20221118105249-3.png]]
++
++
++=== 8.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 ===
++
++Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
++
++[[image:image-20221122100004-1.png||height="497" width="534"]]
++
++
++User need to upgrade again with below four files to solve this issue.
++
++ [[image:image-20221122100004-2.png||height="619" width="389"]]
++
++                                       **Figure 2**
++
++
++=== 8.3.3 "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.
++
++[[image:image-20221122100004-3.png]]
++
++Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
++
++
++Example:
++
++AT+DEUI=70B3D57ED0053981
++
++AT+APPEUI=D23345667BCBCCAF
++
++AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
++
++AT+DADDR=260b4dce    ( no need for OTAA)
++
++AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
++
++AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
++
++
++
++==== 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]]
++
++
++== 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? ==
++
++
++1） Make Sure the device is in Open Area where can see the sky.
++
++2)   Set PDOP to a higher value.
++
++*     (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
++
++*     (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
++
++*     (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
++
++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 =
++
++
  Part Number: (% style="color:blue" %)**TrackerD-XXX**
  (% style="color:blue" %)**XXX**(%%): The default frequency band
  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
++
  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
++
  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
++
  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
++
  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
++
  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
++
  * (% style="color:red" %)**US915**(%%): Default frequency band US915
--= 9.  Packing Info =
++= 10.  Packing Info =
++
  (% style="color:#037691" %)**Package Includes**:
  * TrackerD LoRaWAN GPS/BLE Tracker x 1
++
  * USB recharge & program cable x 1
  (% style="color:#037691" %)**Dimensions and Weight**:
--* Device Size: 85 x 48 x 15 cm
++* Device Size: 85 x 48 x 15 mm
++
  * Weight: 50g
--= 10.  Support =
++= 11.  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]].
--= 11.  Reference =
++= 12.  Reference =
++
  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
++
  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
--* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
--
++* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]

1665301570342-765.png

Author

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

Size

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

Content

1665301636888-168.png

Author

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

Size

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

Content

1665301687277-443.png

Author

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

Size

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

Content

1665301786397-168.png

Author

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

Size

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

Content

1667288597595-714.png

Author

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

Size

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

Content

image-20221009160220-1.png

Author

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

Size

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

Content

image-20221009160309-2.png

Author

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

Size

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

Content

image-20221009234629-1.png

Author

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

Size

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

Content

image-20221009234703-2.png

Author

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

Size

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

Content

image-20221024105643-1.png

Author

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

Size

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

Content

image-20221024105643-2.png

Author

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

Size

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

Content

image-20221102140621-1.png

Author

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

Size

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

Content

image-20221102140638-2.png

Author

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

Size

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

Content

image-20221102140704-3.png

Author

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

Size

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

Content

image-20221102140712-4.png

Author

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

Size

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

Content

image-20221102140748-5.png

Author

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

Size

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

Content

image-20221102140801-6.png

Author

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

Size

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

Content

image-20221107145243-1.png

Author

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

Size

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

Content

image-20221116111844-1.png

Author

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

Size

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

Content

image-20221116111844-2.png

Author

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

Size

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

Content

image-20221116111844-3.png

Author

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

Size

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

Content

image-20221116111844-4.png

Author

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

Size

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

Content

image-20221116111844-5.png

Author

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

Size

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

Content

image-20221118104359-1.png

Author

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

Size

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

Content

image-20221118105220-2.png

Author

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

Size

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

Content

image-20221118105249-3.png

Author

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

Size

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

Content

image-20221118105402-4.png

Author

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

Size

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

Content

image-20221122100004-1.png

Author

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

Size

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

Content

image-20221122100004-2.png

Author

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

Size

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

Content

image-20221122100004-3.png

Author

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

Size

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

Content

image-20221122100004-4.png

Author

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

Size

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

Content