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