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

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,8 +127,8 @@
127 127  
128 128  
129 129  
130 -= 2.  Use TrackerD =
131 131  
123 += 2.1 Use TrackerD =
132 132  
133 133  == 2.1 How it works? ==
134 134  
... ... @@ -136,724 +136,490 @@
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  
139 -
140 140  == 2.2 Quick guide to connect to LoRaWAN server ==
141 141  
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.
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. 
144 144  
136 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
145 145  
146 -[[image:1664501652064-326.png]]
147 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 +**(% style="color:blue" %)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 +**(% style="color:blue" %)Step 2**:(%%) Power on TrackerD by using the on board switch.
182 182  
183 183  
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.
184 184  
185 185  
186 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
177 +**(% style="color:blue" %)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 +== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- ==
192 192  
193 -== 2.3  Positioning Mode(SMOD) ==
194 194  
189 +=== 2.3.1 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"]].
193 +=== 2.3.2 Uplink FPORT= , Realtime GNSS Positioning ===
203 203  
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. )
204 204  
205 205  
206 -== 2.4  Uplink Payload ==
198 +|(((
199 +**Size**
207 207  
201 +**(bytes)**
202 +)))|4|4|2|1|(((
203 +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" %)(((
205 +(optional )
206 +)))|(((
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 -
327 -
328 -==== (% style="color:blue" %)**FLAG:**(%%) ====
329 -
330 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
331 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
332 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
333 -
334 -**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
335 -
336 -
337 -==== (% style="color:blue" %)**Location info:**(%%) ====
338 -
339 -* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
340 -* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
341 -
342 -(% style="color:red" %)**Important note:**
343 -
344 -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.
345 -
346 -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:
347 -
348 -
349 -[[image:1664502116362-706.png]]
350 -
351 -
352 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
353 -
354 -[[image:1664502166010-515.png]]
355 -
356 -
357 -
358 -==== (% style="color:blue" %)**Alarm:**(%%) ====
359 -
360 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
361 -
362 -
363 -==== (% style="color:blue" %)**BAT:**(%%) ====
364 -
365 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
366 -
367 -(((
368 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
209 +(optional)
369 369  )))
211 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|(((
212 +[[Alarm &>>path:#Alarm]]
370 370  
371 -* > 4.0v :  80% ~~ 100%
372 -* 3.85v ~~3.99v:  60% ~~ 80%
373 -* 3.70v ~~ 3.84v:  40% ~~ 60%
374 -* 3.40v ~~ 3.69v:  20% ~~ 40%
375 -* < 3.39v:  0~~20%
214 +[[BAT>>path:#Alarm]]
215 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]]
376 376  
377 377  
218 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
378 378  
379 -==== (% style="color:blue" %)**MOD:**(%%) ====
380 380  
381 -**Example: ** (0x60>>6) & 0x3f =1
221 +**Alarm & BAT:**
382 382  
383 -**Set the format of GPS data uplink link：**
223 +|**Size(bit)**|1 bit|1bit|14 bits
224 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]]
384 384  
385 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
386 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
226 +**FLAG:**
387 387  
228 +|**Size(bit)**|2 bits|1bit|5 bits
229 +|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version
388 388  
389 -**Set the format of BLE data uplink link：**
390 390  
391 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
392 392  
233 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A **
393 393  
394 -==== (% style="color:blue" %)**LON:**(%%) ====
395 395  
396 -**Example:** (0x60>>5) & 0x01=1.
236 +**Location info:**
397 397  
398 -Enable/Disable LED activity for uplink
238 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~://
399 399  
400 -(((
401 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
402 -)))
240 +//value = 02863D68 /1000000 = 42.351976//
403 403  
404 -(((
405 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
406 -)))
242 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://
407 407  
244 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
408 408  
409 -==== (% style="color:blue" %)**Hum:**(%%) ====
410 410  
411 -0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
247 +Important note:
412 412  
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:
413 413  
414 -==== (% style="color:blue" %)**Tem:**(%%) ====
253 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
415 415  
416 -011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
417 417  
256 +1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
418 418  
258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
419 419  
420 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
260 +* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01
261 +* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV).
421 421  
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: \
422 422  
423 -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)
424 424  
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%
425 425  
426 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
427 -|=(% scope="row" style="width: 60px;" %)(((
428 -**Size(bytes)**
429 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
430 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
431 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
432 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
433 433  
434 -(% class="wikigeneratedid" %)
435 -[[image:1665301687277-443.png]]
273 +* **LON: **Enable/Disable LED activity for uplink
436 436  
275 +0x00: Disable LED indicator.
437 437  
277 +0x01: Enable LED indicator (Default Value)
438 438  
439 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
440 440  
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
441 441  
442 -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.
443 443  
444 444  
445 -(% style="color:red" %)**Note for this mode:**
285 +=== 2.3.3 Uplink FPORT= , History GNSS Positioning ===
446 446  
447 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
448 -* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
449 -* 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
450 450  
451 -The payload is 15 bytes, as below.
452 452  
453 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
454 -|=(% scope="row" %)(((
455 -**Size(bytes)**
456 -)))|4|4|2|1|1|1|1|1
457 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
289 +=== 2.3.4 BLE positioning Payload(Fport=2) ===
458 458  
459 -[[image:image-20221009160309-2.png]]
291 +Different MODE has different payload:
460 460  
293 +**MODE=2**
461 461  
295 +|(((
296 +**Size**
462 462  
463 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
298 +**(bytes)**
299 +)))|16|4|4|2|4|2|1
300 +|**Value**|[[UUID>>path:#Location]]|(((
301 +iBeacon
464 464  
303 +MAJOR
304 +)))|(((
305 +iBeacon
465 465  
466 -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.
307 +MINOR
308 +)))|(((
309 +iBeacon Measured
467 467  
468 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
311 +Power
312 +)))|(((
313 +iBeacon
469 469  
315 +RSSI
316 +)))|(((
317 +[[Alarm &>>path:#Alarm]]
470 470  
471 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
472 -|=(% scope="row" style="width: 60px;" %)(((
473 -**Size(bytes)**
474 -)))|(% 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
475 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
476 -iBeacon MAJOR
477 -)))|(% style="width:63px" %)(((
478 -iBeacon MINOR
479 -)))|(% style="width:71px" %)(((
480 -iBeacon Measured Power
481 -)))|(% style="width:50px" %)(((
482 -iBeacon RSSI
483 -)))|(% style="width:47px" %)(((
484 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
485 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
319 +[[BAT>>path:#Alarm]]
320 +)))|[[FLAG>>path:#Flag]]
486 486  
487 -[[image:1664502425687-834.png]]
488 488  
323 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
489 489  
490 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
491 -* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
492 -* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
493 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
494 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
495 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
496 -* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
497 497  
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.
498 498  
499 499  
500 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
501 501  
336 +=== 2.3.5 Add Payload format in TTN V3 ===
502 502  
503 -TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
338 +In TTN V3, use can add a custom payload so it shows friendly.
504 504  
340 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
505 505  
506 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
507 -|=(% scope="row" style="width: 60px;" %)(((
508 -**Size(bytes)**
509 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
510 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
511 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
512 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
342 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
513 513  
514 -(% class="wikigeneratedid" %)
515 -[[image:1667288597595-714.png||height="212" width="1151"]]
344 +Add the decoder from this link:
516 516  
517 517  
518 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
519 -* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
520 -* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
347 +Save the change the uplink message will be parsed. As below:
521 521  
349 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
522 522  
523 523  
524 -=== 2.4.7  Add Payload format in TTN V3 ===
525 525  
526 526  
527 -In TTN V3, user can add a custom payload so it shows friendly.
528 528  
529 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
355 +== 2.4 Integrate with Datacake ==
530 530  
531 531  
532 -[[image:1664502649601-895.png]]
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.
533 533  
360 +Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
534 534  
535 -Add the decoder from this link: 
362 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
536 536  
537 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
538 538  
539 -Save the change the uplink message will be parsed. As below:
365 +== 2.5 Integrate with Tago ==
540 540  
541 -[[image:1664502676891-606.png]]
542 542  
543 -
544 -
545 -== 2.5 Integrate with Datacake ==
546 -
547 -
548 548  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.
549 549  
550 -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]]
551 -
552 -[[image:1664502695771-538.png]]
553 -
554 -
555 -
556 -== 2.6 Integrate with Tago ==
557 -
558 -
559 -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.
560 -
561 561  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]]
562 562  
372 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
563 563  
564 564  
565 -[[image:1664502715371-321.png]]
566 566  
567 567  
377 +== 2.6 Alarm Mode ==
568 568  
569 -== 2.7  Datalog Feature ==
570 570  
380 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
571 571  
572 -total 273 entries,by default,
573 573  
574 -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.
575 575  
576 -Example use case.
577 577  
578 -[[image:image-20221009234703-2.png||height="328" width="899"]]
579 -
580 -
581 -[[image:image-20221009234629-1.png||height="390" width="577"]]
582 -
583 -
584 -
585 -== 2.8 Alarm Mode ==
586 -
587 -
588 -(((
589 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
590 -)))
591 -
592 -
593 -(((
594 -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.
595 -)))
596 -
597 -
598 -(((
599 599  Two ways to exit alarm mode:
600 -)))
601 601  
602 -* Server sends a downlink command to exit.
388 +* Server send a downlink command to exit.
603 603  * User fast press the RED button 10 times.
604 604  
605 -(((
606 -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.
607 -)))
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.
608 608  
609 609  
394 +== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
610 610  
611 -== 2.9 Transport Mode ==
612 612  
613 613  
614 -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 ==
615 615  
616 616  
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
617 617  
618 -== 2.10 LED Status ==
619 619  
620 620  
621 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
622 -|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
623 -|(% 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
624 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
625 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
626 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
627 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
628 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
629 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
630 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
631 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
632 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
633 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
634 634  
635 635  
418 +== 2.9 Button Function ==
636 636  
637 -== 2.11 Button Function ==
420 +**RESET button:**
638 638  
422 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
639 639  
640 -(% style="color:blue" %)**RESET button:**
641 -
642 -[[image:1664502835802-546.png]]
643 -
644 644  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
645 645  
646 646  
647 -(% style="color:red" %)**RED button:**
427 +**RED button:**
648 648  
649 -[[image:1664502854406-763.png]]
429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
650 650  
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.
651 651  
652 -(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
653 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
654 -|(% 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"]]
655 -|(% 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
656 -|(% 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.
657 657  
658 658  
659 659  
660 -== 2.12 USB Port Function ==
439 +== 2.10 USB Port Function ==
661 661  
662 -
663 663  The USB interface of TrackerD has below functions:
664 664  
665 665  * Power on the device
666 666  * Recharge the battery
667 -* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
668 -* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
445 +* [[Configure Device>>path:#AT_Command]]
446 +* [[Upgrade Firmware>>path:#upgrade_image]]
669 669  
670 670  
671 671  
450 +
451 +
672 672  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
673 673  
674 674  
675 675  User can configure TrackerD via AT Command or LoRaWAN Downlink.
676 676  
677 -LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
457 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
678 678  
679 679  
680 -
681 681  == 3.1 Access AT Command ==
682 682  
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. ...
683 683  
684 -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.
464 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
685 685  
686 686  
687 -[[image:1664502999401-486.png]]
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:
688 688  
689 689  
690 -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:
470 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
691 691  
692 692  
693 -[[image:1664503022490-662.png]]
694 694  
474 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
695 695  
696 -[[image:1664503035713-500.png]]
476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
697 697  
698 698  
699 -[[image:1664503047675-651.png]]
700 -
701 -
702 -
703 703  == 3.2 Command Set ==
704 704  
705 705  
706 706  === 3.2.1 Set Transmit Interval ===
707 707  
708 -
709 709  Set device uplink interval.
710 710  
711 -* (% style="color:blue" %)**AT Command:**
486 +* AT Command:
712 712  
713 -(% style="color:#037691" %)**AT+TDC=xxx **
488 +AT+TDC=xxx
714 714  
715 -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)
716 716  
717 717  
718 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
493 +* Downlink Payload (prefix 0x01):
719 719  
720 -(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
495 +0x01 00 01 2C     ~/~/ Same as AT+TDC=300000
721 721  
722 722  
723 -
724 724  === 3.2.2 Set Alarm Packet transmission interval ===
725 725  
726 -
727 727  Set alarm packet transmit interval
728 728  
729 -* (% style="color:blue" %)**AT Command:**
502 +* AT Command:
730 730  
731 -(% style="color:#037691" %)**AT+ATDC=xx. **
504 +AT+ATDC=xx.
732 732  
733 -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
734 734  
735 735  
736 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
509 +* Downlink Payload (prefix 0xB1):
737 737  
738 -(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
511 +0xB1 00 00 3C    ~/~/Same as AT+ATDC=60000
739 739  
740 740  
514 +=== 3.3.3 Set Sports Mode Packet transmission interval ===
741 741  
742 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
516 +Set sports packet transmit interval
743 743  
518 +* AT Command:
744 744  
745 -Set Transport Mode packet transmit interval
520 +AT+MTDC=xx.
746 746  
747 -* (% 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
748 748  
749 -(% style="color:#037691" %)**AT+MTDC=xx. **
750 750  
751 -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):
752 752  
527 +0x03 00 01 2C    ~/~/Same as AT+ MTDC=3000000
753 753  
754 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
755 755  
756 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
757 757  
531 +=== 3.3.4 Exit Alarm ===
758 758  
759 -
760 -=== 3.2.4 Exit Alarm ===
761 -
762 -
763 763  Server send downlink command to exit Alarm mode
764 764  
765 -* (% style="color:blue" %)**AT Command: No AT Command**
535 +* AT Command:
766 766  
767 -* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
537 +No AT Command
768 768  
769 -(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
770 770  
540 +* Downlink Payload (prefix 0x02):
771 771  
542 +0x02 01     ~/~/ Exit Alarm Mode
772 772  
773 -=== 3.2.5 Disable/Enable LED flash ===
774 774  
545 +=== 3.3.5 Disable/Enable LED flash ===
775 775  
776 776  Disable/Enable LED for position, downlink and uplink
777 777  
778 -* (% style="color:blue" %)**AT Command:**
549 +* AT Command:
779 779  
780 -(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
551 +AT+LON=xx.  (Disable (0), Enable (1), default:1)
781 781  
782 -Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
553 + Example: AT+LON=0 à Disable LED for position, downlink and uplink.
783 783  
784 784  
785 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
556 +* Downlink Payload (prefix 0xAE):
786 786  
787 -(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
558 +0xAE 00    ~/~/Same as AT+LON=0
788 788  
789 789  
790 790  
791 -=== 3.2.6 Disable/Enable Transport Mode ===
792 792  
563 +=== 3.3.6 Disable/Enable movement detect (Debug Only) ===
793 793  
794 -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
795 795  
796 -* (% style="color:blue" %)**AT Command:**
567 +* AT Command:
797 797  
798 -(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
569 +AT+INTWK=xx.  (Disable (0), Enable (1), default:0)
799 799  
800 -Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
571 + Example: AT+ INTWK =1 à Enable detect movement.
801 801  
802 802  
803 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
574 +* Downlink Payload (prefix 0xAF):
804 804  
805 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
576 +0xAF 01    ~/~/Same as AT+ INTWK =1
806 806  
807 807  
808 808  
809 -=== 3.2.7 Set Positioning Mode ===
580 +=== 3.3.7 Set Positioning Mode ===
810 810  
582 +SMOD define the how TrackerD scan and uplink date.
811 811  
812 -SMOD define how TrackerD scan and uplink data:
584 +GPS室外定位模式：设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
813 813  
586 + BLE室内定位模式：设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
814 814  
815 -* (% style="color:blue" %)**AT Command:**
588 + GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
816 816  
817 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
590 +运动模式：设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
818 818  
819 -(% style="color:#037691" %)** aa:**
820 820  
821 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
822 -* (% 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.
823 -* (% 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.
824 824  
825 -(% style="color:#037691" %)**bb:**
826 826  
827 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
595 +* AT Command:
828 828  
829 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
597 +AT+SMOD=xx.
830 830  
831 -(% style="color:#037691" %)**cc:   **
599 + Example:
832 832  
833 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
834 -
835 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
601 + AT+ SMOD =1,0    à GPS+ BAT+ State+Tem&Hum
836 836  
837 -(% style="color:blue" %)**Example:**
603 + AT+ SMOD =1,1    à GPS +BAT State
838 838  
839 - AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
605 + AT+ SMOD =2,3    à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
840 840  
841 - AT+SMOD=1,1,0 ~-~->  GPS +BAT State
842 842  
843 - AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
608 +* Downlink Payload (prefix 0xA5):
844 844  
845 - AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
610 +0xA5 01 00     ~/~/ Same as AT+ SMOD =1,0
846 846  
847 847  
848 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
613 +=== 3.3.8 Set MAX GPS position time ===
849 849  
850 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
851 -
852 -
853 -
854 -=== 3.2.8 Set MAX GPS position time ===
855 -
856 -
857 857  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.
858 858  
859 859  
... ... @@ -860,151 +860,63 @@
860 860  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.
861 861  
862 862  
863 -* (% style="color:blue" %)**AT Command:**
621 +* AT Command:
864 864  
865 -(% 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.
866 866  
867 -**Example:**  AT+FTIME=150
625 +Example: AT+FTIME=150
868 868  
869 869  
870 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
628 +* Downlink Payload (prefix 0xAA):
871 871  
872 -(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
630 +0xAA 00 96      ~/~/Set AT+FTIME=150
873 873  
874 874  
875 875  
876 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
877 877  
635 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
878 878  
879 -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.
880 880  
881 881  
882 882  A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
883 883  
884 884  
885 -* (% style="color:blue" %)**AT Command:**
643 +* AT Command:
886 886  
887 -(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
645 +AT+PDOP=2.5  à Set PDOP to 2.5
888 888  
889 889  
890 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
648 +* Downlink Payload (prefix 0xAD):
891 891  
892 -(% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
650 +0xAD 00 0A    ~/~/Set AT+PDOP=1    (0x0A / 10 =1)
893 893  
894 -(% 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)
895 895  
896 -(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
654 +0xAD 00 46    ~/~/Set AT+PDOP=7     (0x46 / 10 =7)
897 897  
898 -
899 -
900 900  Disable/Enable the confirmation mode
901 901  
902 -* (% style="color:blue" %)**AT Command:**
658 +* AT Command:
903 903  
904 -(% style="color:#037691" %)**AT+CFM=xx**
660 +AT+CFM=xx.
905 905  
662 + Example:
906 906  
907 -**~ Example:**
664 + AT+ CFM=0    à Disable confirmation
908 908  
909 - AT+CFM=0    **~-~->   ** Disable confirmation
666 + AT+ CFM=1    à Enable confirmation
910 910  
911 - AT+CFM=1    **~-~->  ** Enable confirmation
912 912  
669 +* Downlink Payload (prefix 0x05):
913 913  
914 -* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
671 +0x05 01      ~/~/ Same as AT+ SMOD =1
915 915  
916 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
917 917  
918 918  
919 919  
920 -=== 3.2.10  Auto Send None-ACK messages ===
921 921  
922 922  
923 -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.
924 -
925 -
926 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
927 -
928 -The default factory setting is 0.
929 -
930 -
931 -**Command Example Function Response:**
932 -
933 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
934 -
935 -
936 -* (% style="color:blue" %)**Downlink Command: 0x34**
937 -
938 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
939 -
940 -
941 -
942 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
943 -
944 -
945 -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.
946 -
947 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
948 -
949 -(% style="color:blue" %)**AT Command:**
950 -
951 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
952 -
953 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
954 -
955 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
956 -
957 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
958 -
959 -
960 -
961 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
962 -
963 -
964 -WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
965 -
966 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
967 -
968 -(% style="color:blue" %)**AT Command:**
969 -
970 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
971 -
972 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
973 -
974 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
975 -
976 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
977 -
978 -
979 -
980 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
981 -
982 -
983 -Users can use this feature to enable/disable Information printing.
984 -
985 -(% style="color:blue" %)**AT Command:**
986 -
987 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
988 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
989 -
990 -
991 -
992 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
993 -
994 -
995 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
996 -
997 -(% style="color:blue" %)**AT Command:**
998 -
999 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1000 -
1001 -
1002 -(% style="color:blue" %)**Downlink Payload:0X24**(%%)
1003 -
1004 -Example: 0x24 01 ~/~/ Same as AT+CHE=1
1005 -
1006 -
1007 -
1008 1008  = 4. Setting for Different Scenarios =
1009 1009  
1010 1010  
... ... @@ -1014,43 +1014,38 @@
1014 1014  
1015 1015  == 5.1 Firmware Change Log ==
1016 1016  
1017 -
1018 1018  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1019 1019  
1020 1020  
1021 -
1022 1022  == 5.2 How to upgrade firmware ==
1023 1023  
692 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
1024 1024  
1025 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
1026 1026  
695 +**(% style="color:blue" %)Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
1027 1027  
1028 -(% 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.
1029 1029  
1030 -
1031 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
1032 -
1033 1033  After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
1034 1034  
1035 1035  
1036 -(% 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:
1037 1037  
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]]
1038 1038  
1039 -(% 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
1040 1040  
1041 1041  
1042 -[[image:1664503563660-578.png]]
709 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]]
1043 1043  
711 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]]
1044 1044  
1045 -[[image:1664503574618-659.png]]
1046 1046  
714 +**(% style="color:blue" %)Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1047 1047  
716 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1048 1048  
1049 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1050 1050  
1051 -[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1052 -
1053 -
1054 1054  Users need to use below files:
1055 1055  
1056 1056  boot_app0.bin @0e000
... ... @@ -1057,17 +1057,16 @@
1057 1057  
1058 1058  ESP_LORA-eeprom-class.bin @ 0x10000
1059 1059  
725 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]]
1060 1060  
1061 -[[image:1664503593459-435.png]]
727 +After upgrade finish, it will show finish as below:
1062 1062  
729 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]]
1063 1063  
1064 1064  
1065 -After upgrade finish, it will show finish as below:
1066 1066  
1067 -[[image:1664503611848-385.png]]
1068 1068  
1069 1069  
1070 -
1071 1071  = 6. Developer Guide =
1072 1072  
1073 1073  
... ... @@ -1077,59 +1077,49 @@
1077 1077  === 6.1.1 Set up ARDUINO compile environment ===
1078 1078  
1079 1079  
1080 -* **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
1081 1081  
1082 -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]]
1083 1083  
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]]
1084 1084  
1085 -[[image:1664503635019-941.png]]
750 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
1086 1086  
752 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it.
1087 1087  
754 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
1088 1088  
1089 -* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1090 1090  
1091 -[[image:1664503715811-892.png]]
757 +* Download the latest TrackerD from the dragino github
1092 1092  
759 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
1093 1093  
1094 -(% 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.
1095 1095  
1096 -[[image:image-20221024105643-1.png]]
762 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory
1097 1097  
1098 -**~ Figure1**
764 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1099 1099  
1100 1100  
1101 -[[image:image-20221024105643-2.png]]
1102 1102  
1103 - **Figure2**
1104 1104  
1105 -
1106 -* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1107 -
1108 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1109 -
1110 -
1111 -[[image:1664503752288-974.png]]
1112 -
1113 -
1114 -
1115 1115  == 6.2 Source Code ==
1116 1116  
1117 1117  
1118 -* (% 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:
1119 1119  
1120 -[[image:1664503794261-827.png]]
774 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1121 1121  
776 +* Click to upload
1122 1122  
778 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1123 1123  
1124 -* (% 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
1125 1125  
1126 -[[image:1664503808294-336.png]]
1127 1127  
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]]
1128 1128  
1129 1129  
1130 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1131 1131  
1132 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1133 1133  
1134 1134  
1135 1135  
... ... @@ -1136,10 +1136,11 @@
1136 1136  = 7.  FAQ =
1137 1137  
1138 1138  
793 +
1139 1139  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1140 1140  
1141 1141  
1142 -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.
1143 1143  
1144 1144  
1145 1145  
... ... @@ -1150,8 +1150,8 @@
1150 1150  
1151 1151  
1152 1152  
1153 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1154 -|=(% 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**
1155 1155  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1156 1156  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1157 1157  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
... ... @@ -1161,80 +1161,15 @@
1161 1161  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1162 1162  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1163 1163  
1164 -== 7.3 Notes on using different serial port tools for TrackerD ==
819 += 8.  Order Info =
1165 1165  
1166 1166  
1167 -=== **Serial port utility** ===
1168 -
1169 -
1170 -Serial port utility requires you to automatically add data streams.
1171 -
1172 -Need to adjust the data stream to RTS/CTS on physical restart.
1173 -
1174 -
1175 -(% class="wikigeneratedid" %)
1176 -[[image:image-20221102140621-1.png]]
1177 -
1178 -
1179 -When using AT commands, the data flow needs to be adjusted to XON/XOFF
1180 -
1181 -
1182 -[[image:image-20221102140638-2.png]]
1183 -
1184 -
1185 -
1186 -=== **SecureCRT** ===
1187 -
1188 -
1189 -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.
1190 -
1191 -
1192 -[[image:image-20221102140704-3.png]]
1193 -
1194 -
1195 -[[image:image-20221102140712-4.png]]
1196 -
1197 -
1198 -
1199 -=== **PUTTY** ===
1200 -
1201 -
1202 -[[image:image-20221102140748-5.png]]
1203 -
1204 -
1205 -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.
1206 -
1207 -
1208 -[[image:image-20221102140801-6.png]]
1209 -
1210 -
1211 -= 8  Trouble Shooting =
1212 -
1213 -== 8.1 TDC is changed to 4294947296 and cause no uplink. ==
1214 -
1215 -Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1216 -
1217 -
1218 -== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==
1219 -
1220 -ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1221 -
1222 -
1223 -== 8.3 The reason why it has been restarted after upgrading（V.1.4.1） ==
1224 -
1225 -If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1226 -
1227 -[[image:image-20221107145243-1.png||height="695" width="443"]]
1228 -
1229 -
1230 -= 9.  Order Info =
1231 -
1232 -
1233 1233  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1234 1234  
1235 1235  (% style="color:blue" %)**XXX**(%%): The default frequency band
1236 1236  
1237 1237  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
827 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470
1238 1238  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1239 1239  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1240 1240  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
... ... @@ -1242,30 +1242,36 @@
1242 1242  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1243 1243  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1244 1244  
1245 -= 10.  Packing Info =
1246 1246  
836 += 9.  Packing Info =
1247 1247  
1248 -(% style="color:#037691" %)**Package Includes**:
1249 1249  
1250 -* TrackerD LoRaWAN GPS/BLE Tracker x 1
1251 -* USB recharge & program cable x 1
839 +**Package Includes**:
1252 1252  
1253 -(% style="color:#037691" %)**Dimensions and Weight**:
841 +* TrackerD x 1
842 +* Rechargeable cable x 1
843 +* Program Cable x 1
1254 1254  
1255 -* Device Size: 85 x 48 x 15 mm
1256 -* Weight: 50g
845 +**Dimensions and Weight**:
1257 1257  
1258 -= 11. Support =
847 +* Device Size: 85 x 48 x 15 mm/pcs
848 +* Weight: 55g/pcs
1259 1259  
1260 1260  
851 +
852 += 10. Support =
853 +
1261 1261  * 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.
1262 -* 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
1263 1263  
1264 -= 12.  Reference =
857 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1265 1265  
1266 1266  
860 +
861 +
862 += 11.  Reference =
863 +
864 +
1267 1267  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1268 1268  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1269 1269  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1270 -
1271 -
1664505654417-133.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.5 KB
Content
1665301570342-765.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1665301636888-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.6 KB
Content
1665301687277-443.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1665301786397-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1667288597595-714.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20221006181316-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.7 KB
Content
image-20221006181357-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -88.0 KB
Content
image-20221009160220-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.4 KB
Content
image-20221009160309-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -57.2 KB
Content
image-20221009234629-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -222.9 KB
Content
image-20221009234703-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -136.4 KB
Content
image-20221024105643-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.3 KB
Content
image-20221024105643-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.5 KB
Content
image-20221102140621-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content
image-20221102140638-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -40.8 KB
Content
image-20221102140704-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -15.5 KB
Content
image-20221102140712-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -73.2 KB
Content
image-20221102140748-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20221102140801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -21.0 KB
Content
image-20221107145243-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -107.3 KB
Content