Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 87.1
edited by Kilight Cao
on 2022/11/01 15:55
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.Kilight
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.1 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,552 +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:1664501784668-703.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 179  
180 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
177 +**(% style="color:blue" %)Positioning Mode(SMOD):**
181 181  
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.
182 182  
183 -(% 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.
183 +User can switch modes by [[changing SMOD>>path:#Positioning_Mode]].
184 184  
185 185  
186 +== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- ==
186 186  
187 -== 2.3  Positioning Mode(SMOD) ==
188 188  
189 +=== 2.3.1 Uplink FPORT=5, Device Status ===
189 189  
190 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191 191  
192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
193 -* (% 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.
194 -* (% 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.
195 195  
196 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
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 199  
200 -== 2.4  Uplink Payload ==
198 +|(((
199 +**Size**
201 201  
201 +**(bytes)**
202 +)))|4|4|2|1|(((
203 +2
202 202  
203 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
204 -
205 -
206 -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.
207 -
208 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
209 -
210 -
211 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
212 -|=(% 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
213 -|=(% 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
214 -
215 -[[image:1665301570342-765.png]]
216 -
217 -
218 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
219 -
220 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
221 -
222 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
223 -
224 -(% style="color:#037691" %)**Frequency Band**:
225 -
226 -*0x01: EU868
227 -
228 -*0x02: US915
229 -
230 -*0x03: IN865
231 -
232 -*0x04: AU915
233 -
234 -*0x05: KZ865
235 -
236 -*0x06: RU864
237 -
238 -*0x07: AS923
239 -
240 -*0x08: AS923-1
241 -
242 -*0x09: AS923-2
243 -
244 -*0x0a: AS923-3
245 -
246 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
247 -
248 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
249 -
250 -
251 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
252 -
253 -Use can also get the Device Status uplink through the downlink command:
254 -
255 -
256 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
257 -
258 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
259 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
260 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
261 -
262 -(% style="color:blue" %)** SMOD：**
263 -
264 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
265 -
266 -(% style="color:red" %)** 2 :** (%%) BLE ONLY
267 -
268 -(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
269 -
270 -
271 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
272 -
273 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
274 -
275 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
276 -
277 -
278 -(% style="color:blue" %)** BLE_Settings:**
279 -
280 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 -
282 -
283 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
284 -
285 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
286 -|=(% 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
287 -|=(% 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"]]
288 -
289 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
290 -
291 -
292 -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,
293 -
294 -
295 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
296 -|=(% scope="row" style="width: 60px;" %)(((
297 -**Size(bytes)**
298 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
205 +(optional )
206 +)))|(((
299 299  2
300 -)))|(% style="width:30px" %)(((
301 -2
302 -)))
303 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
304 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
305 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
306 306  
307 -[[image:1665301636888-168.png]]
308 -
309 -
310 -==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
311 -
312 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
313 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
314 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
315 -
316 -==== (% style="color:blue" %)**FLAG:**(%%) ====
317 -
318 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
319 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
320 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
321 -
322 -**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
323 -
324 -
325 -==== (% style="color:blue" %)**Location info:**(%%) ====
326 -
327 -* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
328 -* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
329 -
330 -(% style="color:red" %)**Important note:**
331 -
332 -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.
333 -
334 -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:
335 -
336 -
337 -[[image:1664502116362-706.png]]
338 -
339 -
340 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
341 -
342 -[[image:1664502166010-515.png]]
343 -
344 -
345 -
346 -==== (% style="color:blue" %)**Alarm:**(%%) ====
347 -
348 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
349 -
350 -
351 -==== (% style="color:blue" %)**BAT:**(%%) ====
352 -
353 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
354 -
355 -(((
356 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
209 +(optional)
357 357  )))
211 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|(((
212 +[[Alarm &>>path:#Alarm]]
358 358  
359 -* > 4.0v :  80% ~~ 100%
360 -* 3.85v ~~3.99v:  60% ~~ 80%
361 -* 3.70v ~~ 3.84v:  40% ~~ 60%
362 -* 3.40v ~~ 3.69v:  20% ~~ 40%
363 -* < 3.39v:  0~~20%
214 +[[BAT>>path:#Alarm]]
215 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]]
364 364  
365 -==== (% style="color:blue" %)**MOD:**(%%) ====
366 366  
367 -**Example: ** (0x60>>6) & 0x3f =1
218 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
368 368  
369 -**Set the format of GPS data uplink link：**
370 370  
371 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
372 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
221 +**Alarm & BAT:**
373 373  
223 +|**Size(bit)**|1 bit|1bit|14 bits
224 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]]
374 374  
375 -**Set the format of BLE data uplink link：**
226 +**FLAG:**
376 376  
377 -(% 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
378 378  
379 379  
380 -==== (% style="color:blue" %)**LON:**(%%) ====
381 381  
382 -**Example:** (0x60>>5) & 0x01=1.
233 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A **
383 383  
384 -Enable/Disable LED activity for uplink
385 385  
386 -(((
387 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
388 -)))
236 +**Location info:**
389 389  
390 -(((
391 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
392 -)))
238 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~://
393 393  
240 +//value = 02863D68 /1000000 = 42.351976//
394 394  
395 -==== (% style="color:blue" %)**Hum:**(%%) ====
242 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://
396 396  
397 -0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
244 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
398 398  
399 399  
400 -==== (% style="color:blue" %)**Tem:**(%%) ====
247 +Important note:
401 401  
402 -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:
403 403  
253 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
404 404  
405 405  
406 -=== 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:
407 407  
258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
408 408  
409 -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).
410 410  
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: \
411 411  
412 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
413 -|=(% scope="row" style="width: 60px;" %)(((
414 -**Size(bytes)**
415 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
416 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
417 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
418 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
419 419  
420 -(% class="wikigeneratedid" %)
421 -[[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%
422 422  
423 423  
273 +* **LON: **Enable/Disable LED activity for uplink
424 424  
425 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
275 +0x00: Disable LED indicator.
426 426  
277 +0x01: Enable LED indicator (Default Value)
427 427  
428 -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.
429 429  
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
430 430  
431 -(% style="color:red" %)**Note for this mode:**
432 432  
433 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
434 -* b) TrackerD will send data in (% style="color:blue" %)**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.
435 -* 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
436 436  
437 -The payload is 15 bytes, as below.
285 +=== 2.3.3 Uplink FPORT= , History GNSS Positioning ===
438 438  
439 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
440 -|=(% scope="row" %)(((
441 -**Size(bytes)**
442 -)))|4|4|2|1|1|1|1|1
443 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
444 444  
445 -[[image:image-20221009160309-2.png]]
446 446  
289 +=== 2.3.4 BLE positioning Payload(Fport=2) ===
447 447  
291 +Different MODE has different payload:
448 448  
449 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
293 +**MODE=2**
450 450  
295 +|(((
296 +**Size**
451 451  
452 -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
453 453  
454 -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
455 455  
307 +MINOR
308 +)))|(((
309 +iBeacon Measured
456 456  
457 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
458 -|=(% scope="row" style="width: 60px;" %)(((
459 -**Size(bytes)**
460 -)))|(% 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
461 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
462 -iBeacon MAJOR
463 -)))|(% style="width:63px" %)(((
464 -iBeacon MINOR
465 -)))|(% style="width:71px" %)(((
466 -iBeacon Measured Power
467 -)))|(% style="width:50px" %)(((
468 -iBeacon RSSI
469 -)))|(% style="width:47px" %)(((
470 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
471 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
311 +Power
312 +)))|(((
313 +iBeacon
472 472  
473 -[[image:1664502425687-834.png]]
315 +RSSI
316 +)))|(((
317 +[[Alarm &>>path:#Alarm]]
474 474  
319 +[[BAT>>path:#Alarm]]
320 +)))|[[FLAG>>path:#Flag]]
475 475  
476 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
477 -* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
478 -* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
479 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
480 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
481 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
482 -* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
483 483  
323 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
484 484  
485 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID ===
486 486  
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.
487 487  
488 -TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
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:"]]
336 +=== 2.3.5 Add Payload format in TTN V3 ===
498 498  
499 -(% class="wikigeneratedid" %)
500 -[[image:1667288597595-714.png||height="212" width="1151"]]
338 +In TTN V3, use can add a custom payload so it shows friendly.
501 501  
340 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
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.
342 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
506 506  
344 +Add the decoder from this link:
507 507  
508 -=== 2.4.7  Add Payload format in TTN V3 ===
509 509  
347 +Save the change the uplink message will be parsed. As below:
510 510  
511 -In TTN V3, user can add a custom payload so it shows friendly.
349 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
512 512  
513 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
514 514  
515 515  
516 -[[image:1664502649601-895.png]]
517 517  
518 518  
519 -Add the decoder from this link: 
355 +== 2.4 Integrate with Datacake ==
520 520  
521 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
522 522  
523 -Save the change the uplink message will be parsed. As below:
358 +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.
524 524  
525 -[[image:1664502676891-606.png]]
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]]
526 526  
362 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
527 527  
528 528  
529 -== 2.5 Integrate with Datacake ==
365 +== 2.5 Integrate with Tago ==
530 530  
531 531  
532 532  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.
533 533  
534 -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]]
535 -
536 -[[image:1664502695771-538.png]]
537 -
538 -
539 -
540 -== 2.6 Integrate with Tago ==
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 548  
549 -[[image:1664502715371-321.png]]
550 550  
551 551  
377 +== 2.6 Alarm Mode ==
552 552  
553 -== 2.7  Datalog Feature ==
554 554  
380 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
555 555  
556 -total 273 entries,by default,
557 557  
558 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
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.
559 559  
560 -Example use case.
561 561  
562 -[[image:image-20221009234703-2.png||height="328" width="899"]]
563 -
564 -
565 -[[image:image-20221009234629-1.png||height="390" width="577"]]
566 -
567 -
568 -
569 -== 2.8 Alarm Mode ==
570 -
571 -
572 -(((
573 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
574 -)))
575 -
576 -
577 -(((
578 -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.
579 -)))
580 -
581 -
582 -(((
583 583  Two ways to exit alarm mode:
584 -)))
585 585  
586 -* Server sends a downlink command to exit.
388 +* Server send a downlink command to exit.
587 587  * User fast press the RED button 10 times.
588 588  
589 -(((
590 -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.
591 -)))
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.
592 592  
593 593  
394 +== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
594 594  
595 -== 2.9 Transport Mode ==
596 596  
597 597  
598 -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 ==
599 599  
600 600  
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
601 601  
602 -== 2.10 LED Status ==
603 603  
604 604  
605 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
606 -|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
607 -|(% 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
608 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
609 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
610 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
611 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
612 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
613 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
614 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
615 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
616 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
617 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
618 618  
619 -== 2.11 Button Function ==
620 620  
418 +== 2.9 Button Function ==
621 621  
622 -(% style="color:blue" %)**RESET button:**
420 +**RESET button:**
623 623  
624 -[[image:1664502835802-546.png]]
422 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
625 625  
626 626  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
627 627  
628 628  
629 -(% style="color:red" %)**RED button:**
427 +**RED button:**
630 630  
631 -[[image:1664502854406-763.png]]
429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
632 632  
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.
633 633  
634 -(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
635 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
636 -|(% 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"]]
637 -|(% 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
638 -|(% 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.
639 639  
640 -== 2.12 USB Port Function ==
641 641  
642 642  
439 +== 2.10 USB Port Function ==
440 +
643 643  The USB interface of TrackerD has below functions:
644 644  
645 645  * Power on the device
646 646  * Recharge the battery
647 -* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
648 -* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
445 +* [[Configure Device>>path:#AT_Command]]
446 +* [[Upgrade Firmware>>path:#upgrade_image]]
649 649  
650 -= 3. Configure TrackerD via AT command or LoRaWAN downlink =
651 651  
652 652  
653 -User can configure TrackerD via AT Command or LoRaWAN Downlink.
654 654  
655 -LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
656 656  
452 += 3. Configure TrackerD via AT command or LoRaWAN downlink =
657 657  
658 658  
659 -== 3.1 Access AT Command ==
455 +User can configure TrackerD via AT Command or LoRaWAN Downlink.
660 660  
457 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
661 661  
662 -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.
663 663  
460 +== 3.1 Access AT Command ==
664 664  
665 -[[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. ...
666 666  
464 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
667 667  
668 -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:
669 669  
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:
670 670  
671 -[[image:1664503022490-662.png]]
672 672  
470 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
673 673  
674 -[[image:1664503035713-500.png]]
675 675  
676 676  
677 -[[image:1664503047675-651.png]]
474 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
678 678  
476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
679 679  
680 680  
681 681  == 3.2 Command Set ==
... ... @@ -683,150 +683,137 @@
683 683  
684 684  === 3.2.1 Set Transmit Interval ===
685 685  
686 -
687 687  Set device uplink interval.
688 688  
689 -* (% style="color:blue" %)**AT Command:**
486 +* AT Command:
690 690  
691 -(% style="color:#037691" %)**AT+TDC=xxx **
488 +AT+TDC=xxx
692 692  
693 -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)
694 694  
695 695  
696 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
493 +* Downlink Payload (prefix 0x01):
697 697  
698 -(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
495 +0x01 00 01 2C     ~/~/ Same as AT+TDC=300000
699 699  
700 700  
701 -
702 702  === 3.2.2 Set Alarm Packet transmission interval ===
703 703  
704 -
705 705  Set alarm packet transmit interval
706 706  
707 -* (% style="color:blue" %)**AT Command:**
502 +* AT Command:
708 708  
709 -(% style="color:#037691" %)**AT+ATDC=xx. **
504 +AT+ATDC=xx.
710 710  
711 -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
712 712  
713 713  
714 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
509 +* Downlink Payload (prefix 0xB1):
715 715  
716 -(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
511 +0xB1 00 00 3C    ~/~/Same as AT+ATDC=60000
717 717  
718 718  
514 +=== 3.3.3 Set Sports Mode Packet transmission interval ===
719 719  
720 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
516 +Set sports packet transmit interval
721 721  
518 +* AT Command:
722 722  
723 -Set Transport Mode packet transmit interval
520 +AT+MTDC=xx.
724 724  
725 -* (% 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
726 726  
727 -(% style="color:#037691" %)**AT+MTDC=xx. **
728 728  
729 -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):
730 730  
527 +0x03 00 01 2C    ~/~/Same as AT+ MTDC=3000000
731 731  
732 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
733 733  
734 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
735 735  
531 +=== 3.3.4 Exit Alarm ===
736 736  
737 -
738 -=== 3.2.4 Exit Alarm ===
739 -
740 -
741 741  Server send downlink command to exit Alarm mode
742 742  
743 -* (% style="color:blue" %)**AT Command: No AT Command**
535 +* AT Command:
744 744  
745 -* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
537 +No AT Command
746 746  
747 -(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
748 748  
540 +* Downlink Payload (prefix 0x02):
749 749  
542 +0x02 01     ~/~/ Exit Alarm Mode
750 750  
751 -=== 3.2.5 Disable/Enable LED flash ===
752 752  
545 +=== 3.3.5 Disable/Enable LED flash ===
753 753  
754 754  Disable/Enable LED for position, downlink and uplink
755 755  
756 -* (% style="color:blue" %)**AT Command:**
549 +* AT Command:
757 757  
758 -(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
551 +AT+LON=xx.  (Disable (0), Enable (1), default:1)
759 759  
760 -Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
553 + Example: AT+LON=0 à Disable LED for position, downlink and uplink.
761 761  
762 762  
763 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
556 +* Downlink Payload (prefix 0xAE):
764 764  
765 -(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
558 +0xAE 00    ~/~/Same as AT+LON=0
766 766  
767 767  
768 768  
769 -=== 3.2.6 Disable/Enable Transport Mode ===
770 770  
563 +=== 3.3.6 Disable/Enable movement detect (Debug Only) ===
771 771  
772 -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
773 773  
774 -* (% style="color:blue" %)**AT Command:**
567 +* AT Command:
775 775  
776 -(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
569 +AT+INTWK=xx.  (Disable (0), Enable (1), default:0)
777 777  
778 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
571 + Example: AT+ INTWK =1 à Enable detect movement.
779 779  
780 780  
781 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
574 +* Downlink Payload (prefix 0xAF):
782 782  
783 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
576 +0xAF 01    ~/~/Same as AT+ INTWK =1
784 784  
785 785  
786 786  
787 -=== 3.2.7 Set Positioning Mode ===
580 +=== 3.3.7 Set Positioning Mode ===
788 788  
582 +SMOD define the how TrackerD scan and uplink date.
789 789  
790 -SMOD define how TrackerD scan and uplink data:
584 +GPS室外定位模式：设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
791 791  
586 + BLE室内定位模式：设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
792 792  
793 -* (% style="color:blue" %)**AT Command:**
588 + GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
794 794  
795 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
590 +运动模式：设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
796 796  
797 -(% style="color:#037691" %)** aa:**
798 798  
799 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
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 -* (% 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.
802 802  
803 -(% style="color:#037691" %)**bb:**
804 804  
805 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
806 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
595 +* AT Command:
807 807  
808 -(% style="color:#037691" %)**cc:   **
597 +AT+SMOD=xx.
809 809  
810 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
811 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
599 + Example:
812 812  
813 -(% style="color:blue" %)**Example:**
601 + AT+ SMOD =1,0    à GPS+ BAT+ State+Tem&Hum
814 814  
815 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
816 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
817 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
818 - AT+ SMOD =2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
603 + AT+ SMOD =1,1    à GPS +BAT State
819 819  
605 + AT+ SMOD =2,3    à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
820 820  
821 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
822 822  
823 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
608 +* Downlink Payload (prefix 0xA5):
824 824  
610 +0xA5 01 00     ~/~/ Same as AT+ SMOD =1,0
825 825  
826 826  
827 -=== 3.2.8 Set MAX GPS position time ===
613 +=== 3.3.8 Set MAX GPS position time ===
828 828  
829 -
830 830  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.
831 831  
832 832  
... ... @@ -833,123 +833,63 @@
833 833  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.
834 834  
835 835  
836 -* (% style="color:blue" %)**AT Command:**
621 +* AT Command:
837 837  
838 -(% 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.
839 839  
840 -**Example:**  AT+FTIME=150
625 +Example: AT+FTIME=150
841 841  
842 842  
843 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
628 +* Downlink Payload (prefix 0xAA):
844 844  
845 -(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
630 +0xAA 00 96      ~/~/Set AT+FTIME=150
846 846  
847 847  
848 848  
849 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
850 850  
635 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
851 851  
852 -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.
853 853  
854 854  
855 855  A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
856 856  
857 857  
858 -* (% style="color:blue" %)**AT Command:**
643 +* AT Command:
859 859  
860 -(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
645 +AT+PDOP=2.5  à Set PDOP to 2.5
861 861  
862 862  
863 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
648 +* Downlink Payload (prefix 0xAD):
864 864  
865 -(% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
650 +0xAD 00 0A    ~/~/Set AT+PDOP=1    (0x0A / 10 =1)
866 866  
867 -(% 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)
868 868  
869 -(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
654 +0xAD 00 46    ~/~/Set AT+PDOP=7     (0x46 / 10 =7)
870 870  
871 -
872 -
873 873  Disable/Enable the confirmation mode
874 874  
875 -* (% style="color:blue" %)**AT Command:**
658 +* AT Command:
876 876  
877 -(% style="color:#037691" %)**AT+CFM=xx**
660 +AT+CFM=xx.
878 878  
662 + Example:
879 879  
880 -**~ Example:**
664 + AT+ CFM=0    à Disable confirmation
881 881  
882 - AT+ CFM=0    **~-~->   ** Disable confirmation
666 + AT+ CFM=1    à Enable confirmation
883 883  
884 - AT+ CFM=1    **~-~->  ** Enable confirmation
885 885  
669 +* Downlink Payload (prefix 0x05):
886 886  
887 -* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
671 +0x05 01      ~/~/ Same as AT+ SMOD =1
888 888  
889 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
890 890  
891 891  
892 892  
893 -=== 3.2.10  Auto Send None-ACK messages ===
894 894  
895 895  
896 -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.
897 -
898 -
899 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
900 -
901 -The default factory setting is 0.
902 -
903 -
904 -**Command Example Function Response:**
905 -
906 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
907 -
908 -
909 -* (% style="color:blue" %)**Downlink Command: 0x34**
910 -
911 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
912 -
913 -
914 -
915 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
916 -
917 -
918 -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.
919 -
920 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
921 -
922 -(% style="color:blue" %)**AT Command:**
923 -
924 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
925 -
926 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
927 -
928 -
929 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
930 -
931 -Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
932 -
933 -
934 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID ===
935 -
936 -
937 -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. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
938 -
939 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
940 -
941 -(% style="color:blue" %)**AT Command:**
942 -
943 - (% style="color:#037691" %)**AT+ WiFiMASK =123456**    (%%) ~/~/ Set WiFiMASK = 123456
944 -
945 - (% style="color:#037691" %)**AT+ WiFiMASK =0**       (%%) ~/~/ disable WiFiMASK
946 -
947 -
948 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
949 -
950 -Example: 0xA5010203040506    ~/~/ Set WiFiMASK to 123456
951 -
952 -
953 953  = 4. Setting for Different Scenarios =
954 954  
955 955  
... ... @@ -959,43 +959,38 @@
959 959  
960 960  == 5.1 Firmware Change Log ==
961 961  
962 -
963 963  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
964 964  
965 965  
966 -
967 967  == 5.2 How to upgrade firmware ==
968 968  
692 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
969 969  
970 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
971 971  
695 +**(% style="color:blue" %)Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
972 972  
973 -(% 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.
974 974  
975 -
976 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
977 -
978 978  After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
979 979  
980 980  
981 -(% 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:
982 982  
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]]
983 983  
984 -(% 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
985 985  
986 986  
987 -[[image:1664503563660-578.png]]
709 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]]
988 988  
711 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]]
989 989  
990 -[[image:1664503574618-659.png]]
991 991  
714 +**(% style="color:blue" %)Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
992 992  
716 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
993 993  
994 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
995 995  
996 -[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
997 -
998 -
999 999  Users need to use below files:
1000 1000  
1001 1001  boot_app0.bin @0e000
... ... @@ -1002,17 +1002,16 @@
1002 1002  
1003 1003  ESP_LORA-eeprom-class.bin @ 0x10000
1004 1004  
725 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]]
1005 1005  
1006 -[[image:1664503593459-435.png]]
727 +After upgrade finish, it will show finish as below:
1007 1007  
729 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]]
1008 1008  
1009 1009  
1010 -After upgrade finish, it will show finish as below:
1011 1011  
1012 -[[image:1664503611848-385.png]]
1013 1013  
1014 1014  
1015 -
1016 1016  = 6. Developer Guide =
1017 1017  
1018 1018  
... ... @@ -1022,59 +1022,49 @@
1022 1022  === 6.1.1 Set up ARDUINO compile environment ===
1023 1023  
1024 1024  
1025 -* **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
1026 1026  
1027 -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]]
1028 1028  
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]]
1029 1029  
1030 -[[image:1664503635019-941.png]]
750 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
1031 1031  
752 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it.
1032 1032  
754 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
1033 1033  
1034 -* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1035 1035  
1036 -[[image:1664503715811-892.png]]
757 +* Download the latest TrackerD from the dragino github
1037 1037  
759 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
1038 1038  
1039 -(% 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.
1040 1040  
1041 -[[image:image-20221024105643-1.png]]
762 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory
1042 1042  
1043 -**~ Figure1**
764 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1044 1044  
1045 1045  
1046 -[[image:image-20221024105643-2.png]]
1047 1047  
1048 - **Figure2**
1049 1049  
1050 -
1051 -* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1052 -
1053 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1054 -
1055 -
1056 -[[image:1664503752288-974.png]]
1057 -
1058 -
1059 -
1060 1060  == 6.2 Source Code ==
1061 1061  
1062 1062  
1063 -* (% 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:
1064 1064  
1065 -[[image:1664503794261-827.png]]
774 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1066 1066  
776 +* Click to upload
1067 1067  
778 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1068 1068  
1069 -* (% 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
1070 1070  
1071 -[[image:1664503808294-336.png]]
1072 1072  
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]]
1073 1073  
1074 1074  
1075 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1076 1076  
1077 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1078 1078  
1079 1079  
1080 1080  
... ... @@ -1081,10 +1081,11 @@
1081 1081  = 7.  FAQ =
1082 1082  
1083 1083  
793 +
1084 1084  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1085 1085  
1086 1086  
1087 -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.
1088 1088  
1089 1089  
1090 1090  
... ... @@ -1095,8 +1095,8 @@
1095 1095  
1096 1096  
1097 1097  
1098 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1099 -|=(% 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**
1100 1100  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1101 1101  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1102 1102  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
... ... @@ -1114,6 +1114,7 @@
1114 1114  (% style="color:blue" %)**XXX**(%%): The default frequency band
1115 1115  
1116 1116  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
827 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470
1117 1117  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1118 1118  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1119 1119  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
... ... @@ -1121,25 +1121,33 @@
1121 1121  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1122 1122  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1123 1123  
835 +
1124 1124  = 9.  Packing Info =
1125 1125  
1126 1126  
1127 -(% style="color:#037691" %)**Package Includes**:
839 +**Package Includes**:
1128 1128  
1129 -* TrackerD LoRaWAN GPS/BLE Tracker x 1
1130 -* USB recharge & program cable x 1
841 +* TrackerD x 1
842 +* Rechargeable cable x 1
843 +* Program Cable x 1
1131 1131  
1132 -(% style="color:#037691" %)**Dimensions and Weight**:
845 +**Dimensions and Weight**:
1133 1133  
1134 -* Device Size: 85 x 48 x 15 cm
1135 -* Weight: 50g
847 +* Device Size: 85 x 48 x 15 mm/pcs
848 +* Weight: 55g/pcs
1136 1136  
1137 -= 10. Support =
1138 1138  
1139 1139  
852 += 10. Support =
853 +
1140 1140  * 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.
1141 -* 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
1142 1142  
857 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
858 +
859 +
860 +
861 +
1143 1143  = 11.  Reference =
1144 1144  
1145 1145  
... ... @@ -1146,4 +1146,3 @@
1146 1146  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1147 1147  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1148 1148  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1149 -
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