Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 98.2
edited by Xiaoling
on 2022/11/02 15:52
Change comment: There is no comment for this version
To version 19.2
edited by Xiaoling
on 2022/09/30 09:12
Change comment: There is no comment for this version

Summary

Details

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