Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 115.1
edited by Bei Jinggeng
on 2022/11/15 14:38
Change comment: There is no comment for this version
To version 49.1
edited by Xiaoling
on 2022/09/30 10:10
Change comment: Uploaded new attachment "1664503824081-592.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
Content
... ... @@ -1,13 +7,6 @@
1 -(% style="text-align:center" %)
2 -[[image:1664505654417-133.png]]
3 -
4 -
5 -
6 -
7 7  (% class="wikigeneratedid" %)
8 8  **Table of Contents:**
9 9  
10 -{{toc/}}
11 11  
12 12  
13 13  
... ... @@ -14,10 +14,9 @@
14 14  
15 15  = 1.  Introduction =
16 16  
10 +== 1.1  OverView ==
17 17  
18 -== 1.1  What is TrackerD ==
19 19  
20 -
21 21  (((
22 22  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**.
23 23  )))
... ... @@ -25,14 +25,10 @@
25 25  (((
26 26  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.
27 27  
28 -(((
29 29  TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
30 -)))
31 31  
32 -(((
33 33  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 34  )))
35 -)))
36 36  
37 37  (((
38 38  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 @@
46 46  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47 47  
48 48  
49 -
50 50  == 1.2 Specifications ==
51 51  
52 52  
... ... @@ -61,11 +61,13 @@
61 61  * EEPROM: 520 KB
62 62  * Clock Speed: 32Mhz
63 63  
51 +
64 64  (% style="color:blue" %)**Common DC Characteristics:**
65 65  
66 66  * Supply Voltage: 5V via USB port or Internal li-on battery
67 67  * Operating Temperature: -40 ~~ 60°C
68 68  
57 +
69 69  (% style="color:blue" %)**LoRa Spec:**
70 70  
71 71  * Frequency Range,
... ... @@ -87,10 +87,12 @@
87 87  * Packet engine up to 256 bytes with CRC.
88 88  * LoRaWAN 1.0.3 Specification
89 89  
79 +
90 90  (% style="color:blue" %)**Battery:**
91 91  
92 92  * 1000mA Li-on Battery power (for model TrackerD)
93 93  
84 +
94 94  (% style="color:blue" %)**Power Consumption**
95 95  
96 96  * Sleeping Mode: 200uA
... ... @@ -97,6 +97,9 @@
97 97  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 98  * Tracking: max: 38mA
99 99  
91 +
92 +
93 +
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -103,7 +103,7 @@
103 103  * LoRaWAN 1.0.3 Class A
104 104  * ESP32 PICO D4
105 105  * SX1276/78 Wireless Chip
106 -* Arduino IDE Compatible
100 +* Arduino IDE Compatible
107 107  * Open source hardware / software
108 108  * Regular/ Real-time GPS,BLE,WIFI tracking
109 109  * Built-in3 axis accelerometer (LIS3DH)
... ... @@ -115,6 +115,8 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
112 +
113 +
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,9 +121,11 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -= 2.  Use TrackerD =
125 125  
126 126  
122 +
123 += 2.1 Use TrackerD =
124 +
127 127  == 2.1 How it works? ==
128 128  
129 129  
... ... @@ -130,551 +130,352 @@
130 130  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
131 131  
132 132  
133 -
134 134  == 2.2 Quick guide to connect to LoRaWAN server ==
135 135  
133 +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.
136 136  
137 -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. 
138 138  
136 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
139 139  
140 -[[image:1664501652064-326.png]]
141 141  
142 -
143 -
144 144  The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:
145 145  
141 +**(% style="color:blue" %)Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
146 146  
147 -(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
148 -
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
145 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
151 151  
152 -[[image:1664501677253-891.png]]
153 153  
154 154  
149 +
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
156 156  
157 157  
158 -**__Add APP EUI in the application:__**
153 +Add APP EUI in the application
159 159  
155 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
160 160  
161 -[[image:1664501711466-918.png]]
157 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
162 162  
163 163  
160 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
164 164  
165 -[[image:1664501721248-725.png]]
166 166  
167 167  
168 -[[image:1664501734705-405.png]]
164 +Add APP KEY and DEV EUI
169 169  
166 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
170 170  
171 171  
172 -**__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[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"]]
171 +**(% style="color:blue" %)Step 2**:(%%) Power on TrackerD by using the on board switch.
176 176  
177 177  
174 +**(% 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.
178 178  
179 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
180 180  
177 +**(% style="color:blue" %)Positioning Mode(SMOD):**
181 181  
182 -(% 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.
179 +* **GPS ONLY(Factory Settings): **only get GPS location info.
180 +* **BLE ONLY: **Only obtain iBeacon info via BLE. Design for Indoor tracking.
181 +* **GPS/BLE Hybrid: **Combination for Indoor and Outdoor tracking.
183 183  
183 +User can switch modes by [[changing SMOD>>path:#Positioning_Mode]].
184 184  
185 185  
186 -== 2.3  Positioning Mode(SMOD) ==
186 +== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- ==
187 187  
188 188  
189 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
189 +=== 2.3.1 Uplink FPORT=5, Device Status ===
190 190  
191 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
192 -* (% 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.
193 -* (% 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.
194 194  
195 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
196 196  
193 +=== 2.3.2 Uplink FPORT= , Realtime GNSS Positioning ===
197 197  
195 +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. )
198 198  
199 -== 2.4  Uplink Payload ==
200 200  
198 +|(((
199 +**Size**
201 201  
202 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
201 +**(bytes)**
202 +)))|4|4|2|1|(((
203 +2
203 203  
204 -
205 -Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
206 -
207 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
208 -
209 -
210 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
211 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
212 -|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
213 -
214 -[[image:1665301570342-765.png]]
215 -
216 -
217 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
218 -
219 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
220 -
221 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
222 -
223 -(% style="color:#037691" %)**Frequency Band**:
224 -
225 -*0x01: EU868
226 -
227 -*0x02: US915
228 -
229 -*0x03: IN865
230 -
231 -*0x04: AU915
232 -
233 -*0x05: KZ865
234 -
235 -*0x06: RU864
236 -
237 -*0x07: AS923
238 -
239 -*0x08: AS923-1
240 -
241 -*0x09: AS923-2
242 -
243 -*0x0a: AS923-3
244 -
245 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
246 -
247 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
248 -
249 -
250 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
251 -
252 -Use can also get the Device Status uplink through the downlink command:
253 -
254 -
255 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
256 -
257 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
258 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
259 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
260 -
261 -(% style="color:blue" %)** SMOD：**
262 -
263 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
264 -
265 -(% style="color:red" %)** 2 :** (%%) BLE ONLY
266 -
267 -(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
268 -
269 -
270 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
271 -
272 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
273 -
274 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
275 -
276 -
277 -(% style="color:blue" %)** BLE_Settings:**
278 -
279 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
280 -
281 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
282 -
283 -
284 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
285 -
286 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
287 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
288 -|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
289 -
290 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
291 -
292 -
293 -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,
294 -
295 -
296 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
297 -|=(% scope="row" style="width: 60px;" %)(((
298 -**Size(bytes)**
299 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
205 +(optional )
206 +)))|(((
300 300  2
301 -)))|(% style="width:30px" %)(((
302 -2
303 -)))
304 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
305 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
306 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
307 307  
308 -[[image:1665301636888-168.png]]
309 -
310 -
311 -==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
312 -
313 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
314 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
315 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
316 -
317 -==== (% style="color:blue" %)**FLAG:**(%%) ====
318 -
319 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
320 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
321 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
322 -
323 -**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
324 -
325 -
326 -==== (% style="color:blue" %)**Location info:**(%%) ====
327 -
328 -* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
329 -* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
330 -
331 -(% style="color:red" %)**Important note:**
332 -
333 -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.
334 -
335 -2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
336 -
337 -
338 -[[image:1664502116362-706.png]]
339 -
340 -
341 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
342 -
343 -[[image:1664502166010-515.png]]
344 -
345 -
346 -
347 -==== (% style="color:blue" %)**Alarm:**(%%) ====
348 -
349 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
350 -
351 -
352 -==== (% style="color:blue" %)**BAT:**(%%) ====
353 -
354 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
355 -
356 -(((
357 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
209 +(optional)
358 358  )))
211 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|(((
212 +[[Alarm &>>path:#Alarm]]
359 359  
360 -* > 4.0v :  80% ~~ 100%
361 -* 3.85v ~~3.99v:  60% ~~ 80%
362 -* 3.70v ~~ 3.84v:  40% ~~ 60%
363 -* 3.40v ~~ 3.69v:  20% ~~ 40%
364 -* < 3.39v:  0~~20%
214 +[[BAT>>path:#Alarm]]
215 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]]
365 365  
366 -==== (% style="color:blue" %)**MOD:**(%%) ====
367 367  
368 -**Example: ** (0x60>>6) & 0x3f =1
218 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
369 369  
370 -**Set the format of GPS data uplink link：**
371 371  
372 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
373 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
221 +**Alarm & BAT:**
374 374  
223 +|**Size(bit)**|1 bit|1bit|14 bits
224 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]]
375 375  
376 -**Set the format of BLE data uplink link：**
226 +**FLAG:**
377 377  
378 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
228 +|**Size(bit)**|2 bits|1bit|5 bits
229 +|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version
379 379  
380 380  
381 -==== (% style="color:blue" %)**LON:**(%%) ====
382 382  
383 -**Example:** (0x60>>5) & 0x01=1.
233 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A **
384 384  
385 -Enable/Disable LED activity for uplink
386 386  
387 -(((
388 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
389 -)))
236 +**Location info:**
390 390  
391 -(((
392 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
393 -)))
238 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~://
394 394  
240 +//value = 02863D68 /1000000 = 42.351976//
395 395  
396 -==== (% style="color:blue" %)**Hum:**(%%) ====
242 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://
397 397  
398 -0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
244 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
399 399  
400 400  
401 -==== (% style="color:blue" %)**Tem:**(%%) ====
247 +Important note:
402 402  
403 -011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
249 +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.
250 +1. In firmware version v1.5, Roll & Pitch is disabled by default.
251 +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:
404 404  
253 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
405 405  
406 406  
407 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
256 +1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
408 408  
258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
409 409  
410 -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)
260 +* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01
261 +* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV).
411 411  
263 +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: \
412 412  
413 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
414 -|=(% scope="row" style="width: 60px;" %)(((
415 -**Size(bytes)**
416 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
417 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
418 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
419 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
420 420  
421 -(% class="wikigeneratedid" %)
422 -[[image:1665301687277-443.png]]
266 +* > 4.0v : 80% ~~ 100%
267 +* 3.85v ~~3.99v: 60% ~~ 80%
268 +* 3.70v ~~ 3.84v: 40% ~~ 60%
269 +* 3.40v ~~ 3.69v: 20% ~~ 40%
270 +* < 3.39v: 0~~20%
423 423  
424 424  
273 +* **LON: **Enable/Disable LED activity for uplink
425 425  
426 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
275 +0x00: Disable LED indicator.
427 427  
277 +0x01: Enable LED indicator (Default Value)
428 428  
429 -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.
430 430  
280 +* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
281 +* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree
431 431  
432 -(% style="color:red" %)**Note for this mode:**
433 433  
434 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
435 -* 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.
436 -* 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
437 437  
438 -The payload is 15 bytes, as below.
285 +=== 2.3.3 Uplink FPORT= , History GNSS Positioning ===
439 439  
440 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
441 -|=(% scope="row" %)(((
442 -**Size(bytes)**
443 -)))|4|4|2|1|1|1|1|1
444 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
445 445  
446 -[[image:image-20221009160309-2.png]]
447 447  
289 +=== 2.3.4 BLE positioning Payload(Fport=2) ===
448 448  
291 +Different MODE has different payload:
449 449  
450 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
293 +**MODE=2**
451 451  
295 +|(((
296 +**Size**
452 452  
453 -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.
298 +**(bytes)**
299 +)))|16|4|4|2|4|2|1
300 +|**Value**|[[UUID>>path:#Location]]|(((
301 +iBeacon
454 454  
455 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
303 +MAJOR
304 +)))|(((
305 +iBeacon
456 456  
307 +MINOR
308 +)))|(((
309 +iBeacon Measured
457 457  
458 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
459 -|=(% scope="row" style="width: 60px;" %)(((
460 -**Size(bytes)**
461 -)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
462 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
463 -iBeacon MAJOR
464 -)))|(% style="width:63px" %)(((
465 -iBeacon MINOR
466 -)))|(% style="width:71px" %)(((
467 -iBeacon Measured Power
468 -)))|(% style="width:50px" %)(((
469 -iBeacon RSSI
470 -)))|(% style="width:47px" %)(((
471 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
472 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
311 +Power
312 +)))|(((
313 +iBeacon
473 473  
474 -[[image:1664502425687-834.png]]
315 +RSSI
316 +)))|(((
317 +[[Alarm &>>path:#Alarm]]
475 475  
319 +[[BAT>>path:#Alarm]]
320 +)))|[[FLAG>>path:#Flag]]
476 476  
477 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
478 -* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
479 -* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
480 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
481 -* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
482 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
483 -* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
484 484  
485 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
323 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
486 486  
487 487  
488 -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.
326 +* **BAT**: Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
327 +* **MODE: **Define the payload format.
328 +* **UUID: **The uuid from the strongest iBeacon.
329 +* **MAJOR**: The MAJOR from the strongest iBeacon.
330 +* **MINOR**: The MAJOR from the strongest iBeacon.
331 +* **Measured** **Power**: The Measured Power from the strongest iBeacon.
332 +* **RSSI**: The RSSI from the strongest iBeacon.
489 489  
490 490  
491 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
492 -|=(% scope="row" style="width: 60px;" %)(((
493 -**Size(bytes)**
494 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
495 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
496 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
497 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
498 498  
499 -(% class="wikigeneratedid" %)
500 -[[image:1667288597595-714.png||height="212" width="1151"]]
336 +=== 2.3.5 Add Payload format in TTN V3 ===
501 501  
338 +In TTN V3, use can add a custom payload so it shows friendly.
502 502  
503 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
504 -* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
505 -* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
340 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
506 506  
507 -=== 2.4.7  Add Payload format in TTN V3 ===
342 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
508 508  
344 +Add the decoder from this link:
509 509  
510 -In TTN V3, user can add a custom payload so it shows friendly.
511 511  
512 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
347 +Save the change the uplink message will be parsed. As below:
513 513  
349 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
514 514  
515 -[[image:1664502649601-895.png]]
516 516  
517 517  
518 -Add the decoder from this link: 
519 519  
520 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
521 521  
522 -Save the change the uplink message will be parsed. As below:
355 +== 2.4 Integrate with Datacake ==
523 523  
524 -[[image:1664502676891-606.png]]
525 525  
526 -
527 -
528 -== 2.5 Integrate with Datacake ==
529 -
530 -
531 531  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.
532 532  
533 -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]]
360 +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]]
534 534  
362 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
535 535  
536 -[[image:1664502695771-538.png]]
537 537  
365 +== 2.5 Integrate with Tago ==
538 538  
539 539  
540 -== 2.6 Integrate with Tago ==
368 +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.
541 541  
542 -
543 -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.
544 -
545 545  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]]
546 546  
372 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
547 547  
548 -[[image:1664502715371-321.png]]
549 549  
550 550  
551 551  
552 -== 2.7  Datalog Feature ==
377 +== 2.6 Alarm Mode ==
553 553  
554 554  
555 -total 273 entries,by default,
380 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
556 556  
557 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
558 558  
559 -Example use case.
383 +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.
560 560  
561 -[[image:image-20221009234703-2.png||height="328" width="899"]]
562 562  
563 -
564 -[[image:image-20221009234629-1.png||height="390" width="577"]]
565 -
566 -
567 -
568 -== 2.8 Alarm Mode ==
569 -
570 -
571 -(((
572 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
573 -)))
574 -
575 -
576 -(((
577 -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.
578 -)))
579 -
580 -
581 -(((
582 582  Two ways to exit alarm mode:
583 -)))
584 584  
585 -* Server sends a downlink command to exit.
388 +* Server send a downlink command to exit.
586 586  * User fast press the RED button 10 times.
587 587  
588 -(((
589 -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.
590 -)))
391 +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.
591 591  
592 592  
394 +== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
593 593  
594 -== 2.9 Transport Mode ==
595 595  
596 596  
597 -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.
398 +== 2.8 LED Status ==
598 598  
599 599  
401 +|**Event**|**Action**|**AT+LON to control on/off**
402 +|**Power On**|**BLUE, RED , Green** flash once|N/A
403 +|**Join request**|**Green** led fast blink once (200ms)|Yes
404 +|**Join Success**|**Green** led on 5 second|N/A
405 +|**Fixing Location**|**BLUE **blinks 200ms per second|Yes
406 +|**Fixed and uplink**|**GREEN **blinks twice (200ms per blink)|Yes
407 +|**Fail Fix and uplink**|**RED **blinks twice (200ms per blink)|Yes
408 +|**Enter Alarm mode**|**RED **on for 3 seconds|Yes
409 +|**Uplink under Alarm**|**RED **on for 1 second|Yes
410 +|**Exit Alarm**|**BLUE **led on 5 second|Yes
411 +|**Get Downlink**|**GREEN** led on 1 second|Yes
412 +|**Movement Detect**|**RED **on 500ms|N/A
600 600  
601 -== 2.10 LED Status ==
602 602  
603 603  
604 -(% border="1.5" style="background-color:#ffffcc; width:500px" %)
605 -|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
606 -|(% 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
607 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
608 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
609 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
610 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
611 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
612 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
613 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
614 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
615 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
616 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
617 617  
618 -== 2.11 Button Function ==
619 619  
418 +== 2.9 Button Function ==
620 620  
621 -(% style="color:blue" %)**RESET button:**
420 +**RESET button:**
622 622  
623 -[[image:1664502835802-546.png]]
422 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
624 624  
625 625  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
626 626  
627 627  
628 -(% style="color:red" %)**RED button:**
427 +**RED button:**
629 629  
630 -[[image:1664502854406-763.png]]
429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
631 631  
431 +|**Function**|**Action**|**Description**
432 +|Send Alarm|Keep Pressing **RED** button for more than 5 seconds|Enter Alarm Mode.  See [[Alarm Mode>>path:#Alarm_Mode]]
433 +|Exit Alarm Mode|Fast press the **RED** button 10 times|Exit Alarm Mode
434 +|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.
632 632  
633 -(% border="1" style="background-color:#ffffcc; width:510px" %)
634 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
635 -|(% 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"]]
636 -|(% 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
637 -|(% 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.
638 638  
639 -== 2.12 USB Port Function ==
640 640  
641 641  
439 +== 2.10 USB Port Function ==
440 +
642 642  The USB interface of TrackerD has below functions:
643 643  
644 644  * Power on the device
645 645  * Recharge the battery
646 -* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
647 -* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
445 +* [[Configure Device>>path:#AT_Command]]
446 +* [[Upgrade Firmware>>path:#upgrade_image]]
648 648  
649 -= 3. Configure TrackerD via AT command or LoRaWAN downlink =
650 650  
651 651  
652 -User can configure TrackerD via AT Command or LoRaWAN Downlink.
653 653  
654 -LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
655 655  
452 += 3. Configure TrackerD via AT command or LoRaWAN downlink =
656 656  
657 657  
658 -== 3.1 Access AT Command ==
455 +User can configure TrackerD via AT Command or LoRaWAN Downlink.
659 659  
457 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
660 660  
661 -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.
662 662  
460 +== 3.1 Access AT Command ==
663 663  
664 -[[image:1664502999401-486.png]]
462 +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. ...
665 665  
464 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
666 666  
667 -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:
668 668  
467 +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:
669 669  
670 -[[image:1664503022490-662.png]]
671 671  
470 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
672 672  
673 -[[image:1664503035713-500.png]]
674 674  
675 675  
676 -[[image:1664503047675-651.png]]
474 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
677 677  
476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
678 678  
679 679  
680 680  == 3.2 Command Set ==
... ... @@ -682,157 +682,137 @@
682 682  
683 683  === 3.2.1 Set Transmit Interval ===
684 684  
685 -
686 686  Set device uplink interval.
687 687  
688 -* (% style="color:blue" %)**AT Command:**
486 +* AT Command:
689 689  
690 -(% style="color:#037691" %)**AT+TDC=xxx **
488 +AT+TDC=xxx
691 691  
692 -Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
490 +Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
693 693  
694 694  
695 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
493 +* Downlink Payload (prefix 0x01):
696 696  
697 -(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
495 +0x01 00 01 2C     ~/~/ Same as AT+TDC=300000
698 698  
699 699  
700 -
701 701  === 3.2.2 Set Alarm Packet transmission interval ===
702 702  
703 -
704 704  Set alarm packet transmit interval
705 705  
706 -* (% style="color:blue" %)**AT Command:**
502 +* AT Command:
707 707  
708 -(% style="color:#037691" %)**AT+ATDC=xx. **
504 +AT+ATDC=xx.
709 709  
710 -Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
506 +Example: AT+ATDC=60000  à Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
711 711  
712 712  
713 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
509 +* Downlink Payload (prefix 0xB1):
714 714  
715 -(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
511 +0xB1 00 00 3C    ~/~/Same as AT+ATDC=60000
716 716  
717 717  
514 +=== 3.3.3 Set Sports Mode Packet transmission interval ===
718 718  
719 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
516 +Set sports packet transmit interval
720 720  
518 +* AT Command:
721 721  
722 -Set Transport Mode packet transmit interval
520 +AT+MTDC=xx.
723 723  
724 -* (% style="color:blue" %)**AT Command:**
522 + Example: AT+MTDC=300000  à Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
725 725  
726 -(% style="color:#037691" %)**AT+MTDC=xx. **
727 727  
728 -Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
525 +* Downlink Payload (prefix 0x03):
729 729  
527 +0x03 00 01 2C    ~/~/Same as AT+ MTDC=3000000
730 730  
731 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
732 732  
733 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
734 734  
531 +=== 3.3.4 Exit Alarm ===
735 735  
736 -
737 -=== 3.2.4 Exit Alarm ===
738 -
739 -
740 740  Server send downlink command to exit Alarm mode
741 741  
742 -* (% style="color:blue" %)**AT Command: No AT Command**
535 +* AT Command:
743 743  
744 -* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
537 +No AT Command
745 745  
746 -(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
747 747  
540 +* Downlink Payload (prefix 0x02):
748 748  
542 +0x02 01     ~/~/ Exit Alarm Mode
749 749  
750 -=== 3.2.5 Disable/Enable LED flash ===
751 751  
545 +=== 3.3.5 Disable/Enable LED flash ===
752 752  
753 753  Disable/Enable LED for position, downlink and uplink
754 754  
755 -* (% style="color:blue" %)**AT Command:**
549 +* AT Command:
756 756  
757 -(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
551 +AT+LON=xx.  (Disable (0), Enable (1), default:1)
758 758  
759 -Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
553 + Example: AT+LON=0 à Disable LED for position, downlink and uplink.
760 760  
761 761  
762 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
556 +* Downlink Payload (prefix 0xAE):
763 763  
764 -(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
558 +0xAE 00    ~/~/Same as AT+LON=0
765 765  
766 766  
767 767  
768 -=== 3.2.6 Disable/Enable Transport Mode ===
769 769  
563 +=== 3.3.6 Disable/Enable movement detect (Debug Only) ===
770 770  
771 -Users can use this feature to enable/disable Transport Mode.
565 +User can use this feature to check and set thread hole of movement detect
772 772  
773 -* (% style="color:blue" %)**AT Command:**
567 +* AT Command:
774 774  
775 -(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
569 +AT+INTWK=xx.  (Disable (0), Enable (1), default:0)
776 776  
777 -Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
571 + Example: AT+ INTWK =1 à Enable detect movement.
778 778  
779 779  
780 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
574 +* Downlink Payload (prefix 0xAF):
781 781  
782 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
576 +0xAF 01    ~/~/Same as AT+ INTWK =1
783 783  
784 784  
785 785  
786 -=== 3.2.7 Set Positioning Mode ===
580 +=== 3.3.7 Set Positioning Mode ===
787 787  
582 +SMOD define the how TrackerD scan and uplink date.
788 788  
789 -SMOD define how TrackerD scan and uplink data:
584 +GPS室外定位模式：设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
790 790  
586 + BLE室内定位模式：设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
791 791  
792 -* (% style="color:blue" %)**AT Command:**
588 + GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
793 793  
794 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
590 +运动模式：设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
795 795  
796 -(% style="color:#037691" %)** aa:**
797 797  
798 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
799 799  
800 -* (% 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.
801 801  
802 -* (% 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.
595 +* AT Command:
803 803  
804 -(% style="color:#037691" %)**bb:**
597 +AT+SMOD=xx.
805 805  
806 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
599 + Example:
807 807  
808 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
601 + AT+ SMOD =1,0    à GPS+ BAT+ State+Tem&Hum
809 809  
810 -(% style="color:#037691" %)**cc:   **
603 + AT+ SMOD =1,1    à GPS +BAT State
811 811  
812 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
813 -
814 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
605 + AT+ SMOD =2,3    à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
815 815  
816 -(% style="color:blue" %)**Example:**
817 817  
818 - AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
608 +* Downlink Payload (prefix 0xA5):
819 819  
820 - AT+SMOD=1,1,0 ~-~->  GPS +BAT State
610 +0xA5 01 00     ~/~/ Same as AT+ SMOD =1,0
821 821  
822 - AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
823 823  
824 - AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
613 +=== 3.3.8 Set MAX GPS position time ===
825 825  
826 -
827 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
828 -
829 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
830 -
831 -
832 -
833 -=== 3.2.8 Set MAX GPS position time ===
834 -
835 -
836 836  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.
837 837  
838 838  
... ... @@ -839,151 +839,63 @@
839 839  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.
840 840  
841 841  
842 -* (% style="color:blue" %)**AT Command:**
621 +* AT Command:
843 843  
844 -(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
623 +AT+FTIME=xx  à Set to use xx as max fix time.
845 845  
846 -**Example:**  AT+FTIME=150
625 +Example: AT+FTIME=150
847 847  
848 848  
849 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
628 +* Downlink Payload (prefix 0xAA):
850 850  
851 -(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
630 +0xAA 00 96      ~/~/Set AT+FTIME=150
852 852  
853 853  
854 854  
855 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
856 856  
635 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
857 857  
858 -PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
637 +PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can’t get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
859 859  
860 860  
861 861  A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
862 862  
863 863  
864 -* (% style="color:blue" %)**AT Command:**
643 +* AT Command:
865 865  
866 -(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
645 +AT+PDOP=2.5  à Set PDOP to 2.5
867 867  
868 868  
869 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
648 +* Downlink Payload (prefix 0xAD):
870 870  
871 -(% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
650 +0xAD 00 0A    ~/~/Set AT+PDOP=1    (0x0A / 10 =1)
872 872  
873 -(% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
652 +0xAD 00 19    ~/~/Set AT+PDOP=2.5    (0x19 / 10 =2.5)
874 874  
875 -(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
654 +0xAD 00 46    ~/~/Set AT+PDOP=7     (0x46 / 10 =7)
876 876  
877 -
878 -
879 879  Disable/Enable the confirmation mode
880 880  
881 -* (% style="color:blue" %)**AT Command:**
658 +* AT Command:
882 882  
883 -(% style="color:#037691" %)**AT+CFM=xx**
660 +AT+CFM=xx.
884 884  
662 + Example:
885 885  
886 -**~ Example:**
664 + AT+ CFM=0    à Disable confirmation
887 887  
888 - AT+CFM=0    **~-~->   ** Disable confirmation
666 + AT+ CFM=1    à Enable confirmation
889 889  
890 - AT+CFM=1    **~-~->  ** Enable confirmation
891 891  
669 +* Downlink Payload (prefix 0x05):
892 892  
893 -* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
671 +0x05 01      ~/~/ Same as AT+ SMOD =1
894 894  
895 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
896 896  
897 897  
898 898  
899 -=== 3.2.10  Auto Send None-ACK messages ===
900 900  
901 901  
902 -TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
903 -
904 -
905 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
906 -
907 -The default factory setting is 0.
908 -
909 -
910 -**Command Example Function Response:**
911 -
912 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
913 -
914 -
915 -* (% style="color:blue" %)**Downlink Command: 0x34**
916 -
917 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
918 -
919 -
920 -
921 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
922 -
923 -
924 -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.
925 -
926 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
927 -
928 -(% style="color:blue" %)**AT Command:**
929 -
930 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
931 -
932 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
933 -
934 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
935 -
936 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
937 -
938 -
939 -
940 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
941 -
942 -
943 -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.
944 -
945 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
946 -
947 -(% style="color:blue" %)**AT Command:**
948 -
949 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
950 -
951 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
952 -
953 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
954 -
955 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
956 -
957 -
958 -
959 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
960 -
961 -
962 -Users can use this feature to enable/disable Information printing.
963 -
964 -(% style="color:blue" %)**AT Command:**
965 -
966 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
967 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
968 -
969 -
970 -
971 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
972 -
973 -
974 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
975 -
976 -(% style="color:blue" %)**AT Command:**
977 -
978 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
979 -
980 -
981 -(% style="color:blue" %)**Downlink Payload:0X24**
982 -
983 -Example: 0x24 01 ~/~/ Same as AT+CHE=1
984 -
985 -
986 -
987 987  = 4. Setting for Different Scenarios =
988 988  
989 989  
... ... @@ -993,43 +993,38 @@
993 993  
994 994  == 5.1 Firmware Change Log ==
995 995  
996 -
997 997  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
998 998  
999 999  
1000 -
1001 1001  == 5.2 How to upgrade firmware ==
1002 1002  
692 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
1003 1003  
1004 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
1005 1005  
695 +**(% style="color:blue" %)Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
1006 1006  
1007 -(% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
697 +**(% style="color:blue" %)Step2:** (%%) Install CH9102 driver in the PC.
1008 1008  
1009 -
1010 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
1011 -
1012 1012  After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
1013 1013  
1014 1014  
1015 -(% 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]]
702 +**(% style="color:blue" %)Step3：**(%%) Download and Install Flash Tool:
1016 1016  
704 +[[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]]
1017 1017  
1018 -(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
706 +**(% style="color:blue" %)Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1019 1019  
1020 1020  
1021 -[[image:1664503563660-578.png]]
709 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]]
1022 1022  
711 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]]
1023 1023  
1024 -[[image:1664503574618-659.png]]
1025 1025  
714 +**(% style="color:blue" %)Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1026 1026  
716 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1027 1027  
1028 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1029 1029  
1030 -[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1031 -
1032 -
1033 1033  Users need to use below files:
1034 1034  
1035 1035  boot_app0.bin @0e000
... ... @@ -1036,17 +1036,16 @@
1036 1036  
1037 1037  ESP_LORA-eeprom-class.bin @ 0x10000
1038 1038  
725 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]]
1039 1039  
1040 -[[image:1664503593459-435.png]]
727 +After upgrade finish, it will show finish as below:
1041 1041  
729 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]]
1042 1042  
1043 1043  
1044 -After upgrade finish, it will show finish as below:
1045 1045  
1046 -[[image:1664503611848-385.png]]
1047 1047  
1048 1048  
1049 -
1050 1050  = 6. Developer Guide =
1051 1051  
1052 1052  
... ... @@ -1056,59 +1056,49 @@
1056 1056  === 6.1.1 Set up ARDUINO compile environment ===
1057 1057  
1058 1058  
1059 -* **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]]**
744 +* Download the latest Arduino software (IDE) from the Arduino official website
1060 1060  
1061 -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]]
746 +[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]
1062 1062  
748 +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]]
1063 1063  
1064 -[[image:1664503635019-941.png]]
750 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
1065 1065  
752 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it.
1066 1066  
754 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
1067 1067  
1068 -* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1069 1069  
1070 -[[image:1664503715811-892.png]]
757 +* Download the latest TrackerD from the dragino github
1071 1071  
759 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
1072 1072  
1073 -(% 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.
1074 1074  
1075 -[[image:image-20221024105643-1.png]]
762 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory
1076 1076  
1077 -**~ Figure1**
764 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1078 1078  
1079 1079  
1080 -[[image:image-20221024105643-2.png]]
1081 1081  
1082 - **Figure2**
1083 1083  
1084 -
1085 -* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1086 -
1087 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1088 -
1089 -
1090 -[[image:1664503752288-974.png]]
1091 -
1092 -
1093 -
1094 1094  == 6.2 Source Code ==
1095 1095  
1096 1096  
1097 -* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
772 +* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
1098 1098  
1099 -[[image:1664503794261-827.png]]
774 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1100 1100  
776 +* Click to upload
1101 1101  
778 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1102 1102  
1103 -* (% style="color:blue" %)**Click to upload**
780 +* Check the result, if the upload is successful, as shown below, open the serial port to view the data
1104 1104  
1105 -[[image:1664503808294-336.png]]
1106 1106  
783 +[[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]]
1107 1107  
1108 1108  
1109 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1110 1110  
1111 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1112 1112  
1113 1113  
1114 1114  
... ... @@ -1115,10 +1115,11 @@
1115 1115  = 7.  FAQ =
1116 1116  
1117 1117  
793 +
1118 1118  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1119 1119  
1120 1120  
1121 -User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
797 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1122 1122  
1123 1123  
1124 1124  
... ... @@ -1129,8 +1129,8 @@
1129 1129  
1130 1130  
1131 1131  
1132 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1133 -|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
808 +(% border="2" style="background-color:#ffffcc; color:green; width:314px" %)
809 +|(% style="width:118px" %)**Pin**|(% style="width:67px" %)**Color**|(% style="width:123px" %)**USB Pin**
1134 1134  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1135 1135  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1136 1136  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
... ... @@ -1140,99 +1140,15 @@
1140 1140  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1141 1141  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1142 1142  
1143 -== 7.3 Notes on using different serial port tools for TrackerD ==
819 += 8.  Order Info =
1144 1144  
1145 1145  
1146 -=== 7.3.1  Serial port utility ===
1147 -
1148 -
1149 -Serial port utility requires you to automatically add data streams.
1150 -
1151 -Need to adjust the data stream to RTS/CTS on physical restart.
1152 -
1153 -
1154 -(% class="wikigeneratedid" %)
1155 -[[image:image-20221102140621-1.png]]
1156 -
1157 -
1158 -When using AT commands, the data flow needs to be adjusted to XON/XOFF
1159 -
1160 -
1161 -[[image:image-20221102140638-2.png]]
1162 -
1163 -
1164 -
1165 -=== 7.3.2  SecureCRT ===
1166 -
1167 -
1168 -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.
1169 -
1170 -
1171 -[[image:image-20221102140704-3.png]]
1172 -
1173 -
1174 -[[image:image-20221102140712-4.png]]
1175 -
1176 -
1177 -
1178 -=== 7.3.3  PUTTY ===
1179 -
1180 -
1181 -[[image:image-20221102140748-5.png]]
1182 -
1183 -
1184 -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.
1185 -
1186 -
1187 -[[image:image-20221102140801-6.png]]
1188 -
1189 -
1190 -
1191 -= 8  Trouble Shooting =
1192 -
1193 -
1194 -== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1195 -
1196 -
1197 -(((
1198 -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
1199 -)))
1200 -
1201 -
1202 -
1203 -== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1204 -
1205 -
1206 -(((
1207 -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.
1208 -)))
1209 -
1210 -
1211 -
1212 -== 8.3  The reason why it has been restarted after upgrading（V.1.4.1） ==
1213 -
1214 -
1215 -(((
1216 -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
1217 -)))
1218 -
1219 -
1220 -[[image:image-20221107145243-1.png||height="695" width="443"]]
1221 -
1222 -
1223 -== 8.4 If the device's led light is always on when upgrading（since firmware 1.4.1） ==
1224 -
1225 -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.
1226 -
1227 -
1228 -= 9.  Order Info =
1229 -
1230 -
1231 1231  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1232 1232  
1233 1233  (% style="color:blue" %)**XXX**(%%): The default frequency band
1234 1234  
1235 1235  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
827 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470
1236 1236  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1237 1237  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1238 1238  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
... ... @@ -1240,30 +1240,36 @@
1240 1240  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1241 1241  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1242 1242  
1243 -= 10.  Packing Info =
1244 1244  
836 += 9.  Packing Info =
1245 1245  
1246 -(% style="color:#037691" %)**Package Includes**:
1247 1247  
1248 -* TrackerD LoRaWAN GPS/BLE Tracker x 1
1249 -* USB recharge & program cable x 1
839 +**Package Includes**:
1250 1250  
1251 -(% style="color:#037691" %)**Dimensions and Weight**:
841 +* TrackerD x 1
842 +* Rechargeable cable x 1
843 +* Program Cable x 1
1252 1252  
1253 -* Device Size: 85 x 48 x 15 mm
1254 -* Weight: 50g
845 +**Dimensions and Weight**:
1255 1255  
1256 -= 11. Support =
847 +* Device Size: 85 x 48 x 15 mm/pcs
848 +* Weight: 55g/pcs
1257 1257  
1258 1258  
851 +
852 += 10. Support =
853 +
1259 1259  * 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.
1260 -* 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]].
855 +* 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
1261 1261  
1262 -= 12.  Reference =
857 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1263 1263  
1264 1264  
860 +
861 +
862 += 11.  Reference =
863 +
864 +
1265 1265  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1266 1266  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1267 1267  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1268 -
1269 -
1664503831430-500.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
1664505654417-133.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.5 KB
Content
1665301570342-765.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1665301636888-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.6 KB
Content
1665301687277-443.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1665301786397-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1667288597595-714.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20221006181316-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.7 KB
Content
image-20221006181357-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -88.0 KB
Content
image-20221009160220-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.4 KB
Content
image-20221009160309-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -57.2 KB
Content
image-20221009234629-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -222.9 KB
Content
image-20221009234703-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -136.4 KB
Content
image-20221024105643-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.3 KB
Content
image-20221024105643-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.5 KB
Content
image-20221102140621-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content
image-20221102140638-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -40.8 KB
Content
image-20221102140704-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -15.5 KB
Content
image-20221102140712-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -73.2 KB
Content
image-20221102140748-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20221102140801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -21.0 KB
Content
image-20221107145243-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -107.3 KB
Content