Changes for page TrackerD -- LoRaWAN Tracker User Manual

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 32 removed)
  • 1664501652064-326.png
  • 1664501677253-891.png
  • 1664501711466-918.png
  • 1664501721248-725.png
  • 1664501734705-405.png
  • 1664501784668-703.png
  • 1664501958445-288.png
  • 1664502116362-706.png
  • 1664502166010-515.png
  • 1664502425687-834.png
  • 1664502649601-895.png
  • 1664502676891-606.png
  • 1664502695771-538.png
  • 1664502715371-321.png
  • 1664502835802-546.png
  • 1664502854406-763.png
  • 1664502999401-486.png
  • 1664503022490-662.png
  • 1664503035713-500.png
  • 1664503047675-651.png
  • 1664503563660-578.png
  • 1664503574618-659.png
  • 1664503593459-435.png
  • 1664503611848-385.png
  • 1664503635019-941.png
  • 1664503715811-892.png
  • 1664503752288-974.png
  • 1664503794261-827.png
  • 1664503808294-336.png
  • 1664503824081-592.png
  • 1664503831430-500.png
  • 1664505654417-133.png

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
...	...	@@ -62,7 +62,6 @@
62	62	* Clock Speed: 32Mhz
63	63
64	64
65		-
66	66	(% style="color:blue" %)**Common DC Characteristics:**
67	67
68	68	* Supply Voltage: 5V via USB port or Internal li-on battery
...	...	@@ -69,7 +69,6 @@
69	69	* Operating Temperature: -40 ~~ 60°C
70	70
71	71
72		-
73	73	(% style="color:blue" %)**LoRa Spec:**
74	74
75	75	* Frequency Range,
...	...	@@ -92,13 +92,11 @@
92	92	* LoRaWAN 1.0.3 Specification
93	93
94	94
95		-
96	96	(% style="color:blue" %)**Battery:**
97	97
98	98	* 1000mA Li-on Battery power (for model TrackerD)
99	99
100	100
101		-
102	102	(% style="color:blue" %)**Power Consumption**
103	103
104	104	* Sleeping Mode: 200uA
...	...	@@ -114,7 +114,7 @@
114	114	* LoRaWAN 1.0.3 Class A
115	115	* ESP32 PICO D4
116	116	* SX1276/78 Wireless Chip
117		-** Arduino IDE Compatible
	100	+* Arduino IDE Compatible
118	118	* Open source hardware / software
119	119	* Regular/ Real-time GPS,BLE,WIFI tracking
120	120	* Built-in3 axis accelerometer (LIS3DH)
...	...	@@ -128,7 +128,6 @@
128	128
129	129
130	130
131		-
132	132	== 1.4  Applications ==
133	133
134	134
...	...	@@ -138,261 +138,261 @@
138	138
139	139
140	140
141		-= 2.1 Use TrackerD =
	123	+1. Use TrackerD
	124	+11. How it works?
142	142
143	143
144		-== 2.1 How it works? ==
145		-
146		-
147	147	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.
148	148
149	149
	130	+1.
	131	+11. Quick guide to connect to LoRaWAN server
150	150
151		-== 2.2 Quick guide to connect to LoRaWAN server ==
	133	+Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.
152	152
153	153
154		-Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.
	136	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
155	155
156	156
157		-[[image:1664501652064-326.png]]
158		-
159		-
160		-
161	161	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:
162	162
	141	+**Step 1**: Create a device in TTN V3 with the OTAA keys from TrackerD.
163	163
164		-(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
165		-
166	166	Each TrackerD is shipped with a sticker with the default device EUI as below:
167	167
	145	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
168	168
169		-[[image:1664501677253-891.png]]
170	170
171	171
	149	+
172	172	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
173	173
174	174
175		-**__Add APP EUI in the application:__**
	153	+Add APP EUI in the application
176	176
	155	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
177	177
178		-[[image:1664501711466-918.png]]
	157	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
179	179
180	180
	160	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
181	181
182		-[[image:1664501721248-725.png]]
183	183
184	184
185		-[[image:1664501734705-405.png]]
	164	+Add APP KEY and DEV EUI
186	186
	166	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
187	187
188	188
189		-**__Add APP KEY and DEV EUI:__**
190	190
191	191
192		-[[image:1664501784668-703.png]]
	171	+**Step 2**: Power on TrackerD by using the on board switch.
193	193
194	194
	174	+**Step 3:** TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
195	195
196	196
197		-(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
	177	+**Positioning Mode(SMOD):**
198	198
	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.
199	199
200		-(% 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]].
201	201
202	202
203		-(% style="color:blue" %)**Positioning Mode(SMOD):**
	186	+1.
	187	+11. Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~-
204	204
205		-* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
206		-* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
207		-* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
208	208
209		-User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
	190	+1.
	191	+11.
	192	+111. Uplink FPORT=5, Device Status
210	210
211	211
212	212
213		-== 2.3 Uplink Payload ==
	196	+1.
	197	+11.
	198	+111. Uplink FPORT= , Realtime GNSS Positioning
214	214
	200	+The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won’t work on DR0 on US915/AU915 frequency band. )
215	215
216		-=== 2.3.1 Uplink FPORT~=5, Device Status ===
217	217
	203	+|(((
	204	+**Size**
218	218
	206	+**(bytes)**
	207	+)))|4|4|2|1|(((
	208	+2
219	219
220		-=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
	210	+(optional )
	211	+)))|(((
	212	+2
221	221
222		-
223		-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. )
224		-
225		-
226		-(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:520px" %)
227		-|=(% scope="row" style="width: 80px;" %)(((
228		-**Size(bytes)**
229		-
230		-)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:80px" %)(((
231		-2(optional )
232		-)))|(% style="width:80px" %)(((
233		-2(optional)
	214	+(optional)
234	234	)))
235		-|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
236		-[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
237		-)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:83px" %)[[Tem>>||anchor="HTem:"]]
	216	+|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|(((
	217	+[[Alarm &>>path:#Alarm]]
238	238
239		-[[image:1664501958445-288.png]]
	219	+[[BAT>>path:#Alarm]]
	220	+)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]]
240	240
241	241
242		-==== (% style="color:blue" %)Alarm & BAT:(%%) ====
	223	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
243	243
244		-(% border="2" style="background-color:#ffffcc; color:green; width:329px" %)
245		-|(% style="width:72px" %)**Size(bit)**|(% style="width:67px" %)1 bit|(% style="width:118px" %)1bit|(% style="width:63px" %)14 bits
246		-|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
247	247
248		-==== (% style="color:blue" %)FLAG:(%%) ====
	226	+**Alarm & BAT:**
249	249
250		-(% border="2" style="background-color:#ffffcc; color:green; width:332px" %)
251		-|(% style="width:79px" %)**Size(bit)**|(% style="width:55px" %)2 bits|(% style="width:47px" %)1bit|(% style="width:140px" %)5 bits
252		-|(% style="width:79px" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H2.3.4BLEpositioningPayload28Fport229"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version
	228	+|**Size(bit)**|1 bit|1bit|14 bits
	229	+|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]]
253	253
254		-**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
	231	+**FLAG:**
255	255
	233	+|**Size(bit)**|2 bits|1bit|5 bits
	234	+|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version
256	256
257		-==== (% style="color:blue" %)Location info:(%%) ====
258	258
259		-* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
260		-* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
261	261
262		-(% style="color:red" %)**Important note:**
	238	+**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A **
263	263
264		-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.
265	265
266		-2.  In firmware version v1.5, Roll & Pitch is disabled by default.
	241	+**Location info:**
267	267
268		-3.  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:
	243	+* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~://
269	269
	245	+//value = 02863D68 /1000000 = 42.351976//
270	270
271		-[[image:1664502116362-706.png]]
	247	+* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://
272	272
	249	+//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
273	273
274	274
275		-4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
	252	+Important note:
276	276
277		-[[image:1664502166010-515.png]]
	254	+1. When power is low (<2.84v), GPS won’t be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
	255	+1. In firmware version v1.5, Roll & Pitch is disabled by default.
	256	+1. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
278	278
	258	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
279	279
280	280
281		-==== (% style="color:blue" %)Alarm:(%%) ====
	261	+1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
282	282
	263	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
283	283
284		-Example:  0x4B & 0x40 >> 6 = 0x01
	265	+* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01
	266	+* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV).
285	285
	268	+The battery info shows the current voltage, for **TrackerD** version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
286	286
287		-==== (% style="color:blue" %)BAT:(%%) ====
288	288
	271	+* > 4.0v : 80% ~~ 100%
	272	+* 3.85v ~~3.99v: 60% ~~ 80%
	273	+* 3.70v ~~ 3.84v: 40% ~~ 60%
	274	+* 3.40v ~~ 3.69v: 20% ~~ 40%
	275	+* < 3.39v: 0~~20%
289	289
290		-Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
291	291
292		-The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
	278	+* **LON: **Enable/Disable LED activity for uplink
293	293
	280	+0x00: Disable LED indicator.
294	294
295		-* > 4.0v :  80% ~~ 100%
296		-* 3.85v ~~3.99v:  60% ~~ 80%
297		-* 3.70v ~~ 3.84v:  40% ~~ 60%
298		-* 3.40v ~~ 3.69v:  20% ~~ 40%
299		-* < 3.39v:  0~~20%
	282	+0x01: Enable LED indicator (Default Value)
300	300
301		-==== (% style="color:blue" %)LON:(%%) ====
302	302
303		-
304		-Enable/Disable LED activity for uplink
	285	+* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
	286	+* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree
305	305
306		-0x00:  Disable LED indicator.
307	307
308		-0x01:  Enable LED indicator (Default Value)
309	309
	290	+1.
	291	+11.
	292	+111. Uplink FPORT= , History GNSS Positioning
310	310
311		-==== (% style="color:blue" %)Hum:(%%) ====
312	312
313		-0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
314	314
	296	+1.
	297	+11.
	298	+111. BLE positioning Payload(Fport=2)
315	315
316		-==== (% style="color:blue" %)Tem:(%%) ====
	300	+Different MODE has different payload:
317	317
318		-011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
	302	+**MODE=2**
319	319
	304	+|(((
	305	+**Size**
320	320
	307	+**(bytes)**
	308	+)))|16|4|4|2|4|2|1
	309	+|**Value**|[[UUID>>path:#Location]]|(((
	310	+iBeacon
321	321
	312	+MAJOR
	313	+)))|(((
	314	+iBeacon
322	322
323		-=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
	316	+MINOR
	317	+)))|(((
	318	+iBeacon Measured
324	324
	320	+Power
	321	+)))|(((
	322	+iBeacon
325	325
	324	+RSSI
	325	+)))|(((
	326	+[[Alarm &>>path:#Alarm]]
326	326
327		-=== 2.3.4 BLE positioning Payload(Fport2) ===
	328	+[[BAT>>path:#Alarm]]
	329	+)))|[[FLAG>>path:#Flag]]
328	328
329	329
330		-Different MODE has different payload:
	332	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
331	331
332		-**MODE=2**
333	333
334		-(% border="2" style="background-color:#ffffcc; color:green; width:491px" %)
335		-|(% style="width:70px" %)(((
336		-**Size**
	335	+* **BAT**: Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
	336	+* **MODE: **Define the payload format.
	337	+* **UUID: **The uuid from the strongest iBeacon.
	338	+* **MAJOR**: The MAJOR from the strongest iBeacon.
	339	+* **MINOR**: The MAJOR from the strongest iBeacon.
	340	+* **Measured** **Power**: The Measured Power from the strongest iBeacon.
	341	+* **RSSI**: The RSSI from the strongest iBeacon.
337	337
338		-**(bytes)**
339		-)))|(% style="width:44px" %)16|(% style="width:61px" %)4|(% style="width:63px" %)4|(% style="width:71px" %)2|(% style="width:50px" %)4|(% style="width:47px" %)2|(% style="width:15px" %)1
340		-|(% style="width:70px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
341		-iBeacon MAJOR
342		-)))|(% style="width:63px" %)(((
343		-iBeacon MINOR
344		-)))|(% style="width:71px" %)(((
345		-iBeacon Measured Power
346		-)))|(% style="width:50px" %)(((
347		-iBeacon RSSI
348		-)))|(% style="width:47px" %)(((
349		-[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
350		-)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
351	351
352		-[[image:1664502425687-834.png]]
	344	+1.
	345	+11.
	346	+111. Add Payload format in TTN V3
353	353
354		-
355		-* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
356		-* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
357		-* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
358		-* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
359		-* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
360		-* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
361		-* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
362		-
363		-=== 2.3.5 Add Payload format in TTN V3 ===
364		-
365		-
366	366	In TTN V3, use can add a custom payload so it shows friendly.
367	367
368		-In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
	350	+In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
369	369
	352	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
370	370
371		-[[image:1664502649601-895.png]]
372		-
373		-
374	374	Add the decoder from this link:
375	375
376	376
377	377	Save the change the uplink message will be parsed. As below:
378	378
379		-[[image:1664502676891-606.png]]
	359	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
380	380
381	381
382	382
383		-== 2.4 Integrate with Datacake ==
384	384
385	385
386		-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.
	365	+1.
	366	+11. Integrate with Datacake
387	387
388		-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]]
389	389
	369	+After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
390	390
391		-[[image:1664502695771-538.png]]
	371	+Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
392	392
	373	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
393	393
394	394
395		-== 2.5 Integrate with Tago ==
	376	+1.
	377	+11. Integrate with Tago
396	396
397	397
398	398	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.
...	...	@@ -399,18 +399,19 @@
399	399
400	400	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]]
401	401
	384	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
402	402
403		-[[image:1664502715371-321.png]]
404	404
405	405
406	406
407		-== 2.6 Alarm Mode ==
	389	+1.
	390	+11. Alarm Mode
408	408
409	409
410		-User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
	393	+User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
411	411
412	412
413		-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 exit alert mode.
	396	+Once enter Alarm mode, the **GREEN LED** will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
414	414
415	415
416	416	Two ways to exit alarm mode:
...	...	@@ -418,244 +418,252 @@
418	418	* Server send a downlink command to exit.
419	419	* User fast press the RED button 10 times.
420	420
421		-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.
	404	+When exit alarm mode, **RED LED** will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
422	422
423	423
	407	+1.
	408	+11. Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--
424	424
425		-== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
426	426
427	427
	412	+1.
	413	+11. LED Status
428	428
429		-== 2.8 LED Status ==
430	430
	416	+|**Event**|**Action**|**AT+LON to control on/off**
	417	+|**Power On**|**BLUE, RED , Green** flash once|N/A
	418	+|**Join request**|**Green** led fast blink once (200ms)|Yes
	419	+|**Join Success**|**Green** led on 5 second|N/A
	420	+|**Fixing Location**|**BLUE **blinks 200ms per second|Yes
	421	+|**Fixed and uplink**|**GREEN **blinks twice (200ms per blink)|Yes
	422	+|**Fail Fix and uplink**|**RED **blinks twice (200ms per blink)|Yes
	423	+|**Enter Alarm mode**|**RED **on for 3 seconds|Yes
	424	+|**Uplink under Alarm**|**RED **on for 1 second|Yes
	425	+|**Exit Alarm**|**BLUE **led on 5 second|Yes
	426	+|**Get Downlink**|**GREEN** led on 1 second|Yes
	427	+|**Movement Detect**|**RED **on 500ms|N/A
431	431
432		-(% border="2" style="background-color:#ffffcc; color:green; width:636px" %)
433		-|(% style="width:157px" %)**Event**|(% style="width:271px" %)**Action**|(% style="width:202px" %)**AT+LON to control on/off**
434		-|(% 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
435		-|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
436		-|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
437		-|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
438		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
439		-|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
440		-|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
441		-|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
442		-|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
443		-|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
444		-|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
445	445
446		-== 2.9 Button Function ==
447	447
448	448
449		-(% style="color:green" %)**RESET button:**
450	450
451		-[[image:1664502835802-546.png]]
	433	+1.
	434	+11. Button Function
452	452
453		-Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	436	+**RESET button:**
454	454
	438	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
455	455
456		-(% style="color:red" %)**RED button:**
	440	+Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
457	457
458		-[[image:1664502854406-763.png]]
459	459
	443	+**RED button:**
460	460
461		-(% border="2" style="background-color:#ffffcc; color:green; width:627px" %)
462		-|(% style="width:135px" %)**Function**|(% style="width:220px" %)**Action**|(% style="width:265px" %)**Description**
463		-|(% 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"]]
464		-|(% 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
465		-|(% 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.
	445	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
466	466
	447	+|**Function**|**Action**|**Description**
	448	+|Send Alarm|Keep Pressing **RED** button for more than 5 seconds|Enter Alarm Mode.  See [[Alarm Mode>>path:#Alarm_Mode]]
	449	+|Exit Alarm Mode|Fast press the **RED** button 10 times|Exit Alarm Mode
	450	+|Enter Deep Sleep Mode|Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy.
467	467
468	468
469		-== 2.10 USB Port Function ==
470	470
471	471
	455	+1.
	456	+11. USB Port Function
	457	+
472	472	The USB interface of TrackerD has below functions:
473	473
474	474	* Power on the device
475	475	* Recharge the battery
476		-* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
477		-* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
	462	+* [[Configure Device>>path:#AT_Command]]
	463	+* [[Upgrade Firmware>>path:#upgrade_image]]
478	478
479	479
480	480
481		-= 3. Configure TrackerD via AT command or LoRaWAN downlink =
482	482
483	483
484		-User can configure TrackerD via AT Command or LoRaWAN Downlink.
	469	+1. Configure TrackerD via AT command or LoRaWAN downlink
485	485
486		-LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
487	487
	472	+User can configure TrackerD via AT Command or LoRaWAN Downlink.
488	488
	474	+LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
489	489
490		-== 3.1 Access AT Command ==
491	491
	477	+1.
	478	+11. Access AT Command
492	492
493		-TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
	480	+TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below. ...
494	494
	482	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
495	495
496		-[[image:1664502999401-486.png]]
497	497
	485	+In PC, User needs to set serial tool baud rate to **115200** to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
498	498
499		-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:
500	500
	488	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
501	501
502		-[[image:1664503022490-662.png]]
503	503
504	504
	492	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
505	505
506		-[[image:1664503035713-500.png]]
	494	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
507	507
508	508
	497	+1.
	498	+11. Command Set
509	509
510		-[[image:1664503047675-651.png]]
511	511
	501	+1.
	502	+11.
	503	+111. Set Transmit Interval
512	512
513		-
514		-== 3.2 Command Set ==
515		-
516		-
517		-=== 3.2.1 Set Transmit Interval ===
518		-
519		-
520	520	Set device uplink interval.
521	521
522		-* (% style="color:blue" %)**AT Command:**
	507	+* AT Command:
523	523
524		-(% style="color:#037691" %)**AT+TDC=xxx **
	509	+AT+TDC=xxx
525	525
526		-Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
	511	+Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
527	527
528	528
529		-* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
	514	+* Downlink Payload (prefix 0x01):
530	530
531		-(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
	516	+0x01 00 01 2C     ~/~/ Same as AT+TDC=300000
532	532
533	533
	519	+1.
	520	+11.
	521	+111. Set Alarm Packet transmission interval
534	534
535		-=== 3.2.2 Set Alarm Packet transmission interval ===
536		-
537		-
538	538	Set alarm packet transmit interval
539	539
540		-* (% style="color:blue" %)**AT Command:**
	525	+* AT Command:
541	541
542		-(% style="color:#037691" %)**AT+ATDC=xx. **
	527	+AT+ATDC=xx.
543	543
544		-Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
	529	+Example: AT+ATDC=60000  à Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
545	545
546	546
547		-* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
	532	+* Downlink Payload (prefix 0xB1):
548	548
549		-(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
	534	+0xB1 00 00 3C    ~/~/Same as AT+ATDC=60000
550	550
551	551
	537	+1.
	538	+11.
	539	+111. Set Sports Mode Packet transmission interval
552	552
553		-=== 3.2.3 Set Sports Mode Packet transmission interval ===
554		-
555		-
556	556	Set sports packet transmit interval
557	557
558		-* (% style="color:blue" %)**AT Command:**
	543	+* AT Command:
559	559
560		-(% style="color:#037691" %)**AT+MTDC=xx. **
	545	+AT+MTDC=xx.
561	561
562		- Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
	547	+ Example: AT+MTDC=300000  à Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
563	563
564	564
565		-* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
	550	+* Downlink Payload (prefix 0x03):
566	566
567		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
	552	+0x03 00 01 2C    ~/~/Same as AT+ MTDC=3000000
568	568
569	569
570	570
571		-=== 3.2.4 Exit Alarm ===
	556	+1.
	557	+11.
	558	+111. Exit Alarm
572	572
573		-
574	574	Server send downlink command to exit Alarm mode
575	575
576		-* (% style="color:blue" %)**AT Command: No AT Command**
	562	+* AT Command:
577	577
	564	+No AT Command
578	578
579		-* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
580	580
581		-(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
	567	+* Downlink Payload (prefix 0x02):
582	582
	569	+0x02 01     ~/~/ Exit Alarm Mode
583	583
584	584
585		-=== 3.2.5 Disable/Enable LED flash ===
	572	+1.
	573	+11.
	574	+111. Disable/Enable LED flash
586	586
587		-
588	588	Disable/Enable LED for position, downlink and uplink
589	589
590		-* (% style="color:blue" %)**AT Command:**
	578	+* AT Command:
591	591
592		-(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
	580	+AT+LON=xx.  (Disable (0), Enable (1), default:1)
593	593
594		- Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
	582	+ Example: AT+LON=0 à Disable LED for position, downlink and uplink.
595	595
596	596
597		-* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
	585	+* Downlink Payload (prefix 0xAE):
598	598
599		-(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
	587	+0xAE 00    ~/~/Same as AT+LON=0
600	600
601	601
602	602
603		-=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
604	604
	592	+1.
	593	+11.
	594	+111. Disable/Enable movement detect (Debug Only)
605	605
606	606	User can use this feature to check and set thread hole of movement detect
607	607
608		-* (% style="color:blue" %)**AT Command:**
	598	+* AT Command:
609	609
610		-(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
	600	+AT+INTWK=xx.  (Disable (0), Enable (1), default:0)
611	611
612		- Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
	602	+ Example: AT+ INTWK =1 à Enable detect movement.
613	613
614	614
615		-* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
	605	+* Downlink Payload (prefix 0xAF):
616	616
617		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
	607	+0xAF 01    ~/~/Same as AT+ INTWK =1
618	618
619	619
620	620
621		-=== 3.2.7 Set Positioning Mode ===
	611	+1.
	612	+11.
	613	+111. Set Positioning Mode
622	622
623		-
624	624	SMOD define the how TrackerD scan and uplink date.
625	625
626		-GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
	617	+GPS室外定位模式：设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
627	627
628		-BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
	619	+ BLE室内定位模式：设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
629	629
630		-GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
	621	+ GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
631	631
632		-运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
	623	+运动模式：设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
633	633
634	634
635	635
636		-* (% style="color:blue" %)**AT Command:**
637	637
638		-(% style="color:#037691" %)**AT+SMOD=xx. **
	628	+* AT Command:
639	639
	630	+AT+SMOD=xx.
640	640
641		- **Example:**
	632	+ Example:
642	642
643		- AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
	634	+ AT+ SMOD =1,0    à GPS+ BAT+ State+Tem&Hum
644	644
645		- AT+ SMOD =1,1    **~-~->**  GPS +BAT State
	636	+ AT+ SMOD =1,1    à GPS +BAT State
646	646
647		- AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
	638	+ AT+ SMOD =2,3    à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
648	648
649	649
650		-* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	641	+* Downlink Payload (prefix 0xA5):
651	651
652		-(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
	643	+0xA5 01 00     ~/~/ Same as AT+ SMOD =1,0
653	653
654	654
	646	+1.
	647	+11.
	648	+111. Set MAX GPS position time
655	655
656		-=== 3.2.8 Set MAX GPS position time ===
657		-
658		-
659	659	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.
660	660
661	661
...	...	@@ -662,105 +662,102 @@
662	662	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.
663	663
664	664
665		-* (% style="color:blue" %)**AT Command:**
	656	+* AT Command:
666	666
667		-(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
	658	+AT+FTIME=xx  à Set to use xx as max fix time.
668	668
669		-Example:  AT+FTIME=150
	660	+Example: AT+FTIME=150
670	670
671	671
672		-* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
	663	+* Downlink Payload (prefix 0xAA):
673	673
674		-(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
	665	+0xAA 00 96      ~/~/Set AT+FTIME=150
675	675
676	676
677	677
678		-=== 3.3.9 Set PDOP value for GPS fix accuracy ===
679	679
	670	+1.
	671	+11.
	672	+111. Set PDOP value for GPS fix accuracy
680	680
681		-PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
	674	+PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can’t get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
682	682
683	683
684	684	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
685	685
686	686
687		-* (% style="color:blue" %)**AT Command:**
	680	+* AT Command:
688	688
689		-(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
	682	+AT+PDOP=2.5  à Set PDOP to 2.5
690	690
691	691
692		-* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
	685	+* Downlink Payload (prefix 0xAD):
693	693
694		-(% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
	687	+0xAD 00 0A    ~/~/Set AT+PDOP=1    (0x0A / 10 =1)
695	695
696		-(% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
	689	+0xAD 00 19    ~/~/Set AT+PDOP=2.5    (0x19 / 10 =2.5)
697	697
698		-(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
	691	+0xAD 00 46    ~/~/Set AT+PDOP=7     (0x46 / 10 =7)
699	699
700		-
701		-
702	702	Disable/Enable the confirmation mode
703	703
704		-* (% style="color:blue" %)**AT Command:**
	695	+* AT Command:
705	705
706		-(% style="color:#037691" %)**AT+CFM=xx. **
	697	+AT+CFM=xx.
707	707
	699	+ Example:
708	708
709		-**~ Example:**
	701	+ AT+ CFM=0    à Disable confirmation
710	710
711		- AT+ CFM=0    **~-~->   ** Disable confirmation
	703	+ AT+ CFM=1    à Enable confirmation
712	712
713		- AT+ CFM=1    **~-~->  ** Enable confirmation
714	714
	706	+* Downlink Payload (prefix 0x05):
715	715
716		-* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
	708	+0x05 01      ~/~/ Same as AT+ SMOD =1
717	717
718		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
719	719
720	720
721	721
722		-= 4. Setting for Different Scenarios =
723	723
724	724
	715	+1. Setting for Different Scenarios
725	725
726		-= 5. Upload Firmware =
727	727
728	728
729		-== 5.1 Firmware Change Log ==
	719	+1. Upload Firmware
	720	+11. Firmware Change Log
730	730
731		-
732	732	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
733	733
734	734
	725	+1.
	726	+11. How to upgrade firmware
735	735
736		-== 5.2 How to upgrade firmware ==
	728	+User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
737	737
738	738
739		-User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
	731	+**Step1:  **Connect TrackerD and PC via USB cable shipped with TrackerD.
740	740
	733	+**Step2:**  Install CH9102 driver in the PC.
741	741
742		-(% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
743		-
744		-
745		-(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
746		-
747	747	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
748	748
749	749
750		-(% style="color:blue" %)**Step3：**(%%) Download and Install Flash Tool:  [[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]
	738	+**Step3：** Download and Install Flash Tool:
751	751
	740	+[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]
752	752
753		-(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
	742	+**Step4:**  Run Flash Download Tool and configure chip type to ESP32
754	754
755	755
756		-[[image:1664503563660-578.png]]
	745	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]]
757	757
	747	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]]
758	758
759		-[[image:1664503574618-659.png]]
760	760
	750	+**Step5:**  Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
761	761
762		-(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
763		-
764	764	[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
765	765
766	766
...	...	@@ -770,77 +770,75 @@
770	770
771	771	ESP_LORA-eeprom-class.bin @ 0x10000
772	772
	761	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]]
773	773
774		-[[image:1664503593459-435.png]]
775		-
776		-
777		-
778	778	After upgrade finish, it will show finish as below:
779	779
780		-[[image:1664503611848-385.png]]
	765	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]]
781	781
782	782
783	783
784		-= 6. Developer Guide =
785	785
786	786
787		-== 6.1 Compile Source Code ==
	771	+1. Developer Guide
788	788
789	789
790		-=== 6.1.1 Set up ARDUINO compile environment ===
	774	+*
	775	+*1. Compile Source Code
	776	+*11. Set up ARDUINO compile environment
	777	+* Download the latest Arduino software (IDE) from the Arduino official website
791	791
	779	+[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]
792	792
793		-* Download the latest Arduino software (IDE) from the Arduino official website:  [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]
	781	+Install IDE on PC, open and click File ~-~-> Preference, add the following URL [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
794	794
795		-Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL:  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
	783	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
796	796
	785	+* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it.
797	797
798		-[[image:1664503635019-941.png]]
	787	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
799	799
800	800
801		-* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) find the esp32 information and install it.
	790	+* Download the latest TrackerD from the dragino github
802	802
803		-[[image:1664503715811-892.png]]
	792	+[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
804	804
805	805
	795	+Put the Library in the TrackerD directory into the libraries file in the Arduino directory
806	806
807		-* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
	797	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
808	808
809		-Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
810	810
811	811
812		-[[image:1664503752288-974.png]]
813	813
	802	+*
	803	+*1. Source Code
	804	+* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
814	814
	806	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
815	815
816		-== 6.2 Source Code ==
	808	+* Click to upload
817	817
	810	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
818	818
819		-* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
	812	+* Check the result, if the upload is successful, as shown below, open the serial port to view the data
820	820
821		-[[image:1664503794261-827.png]]
822	822
	815	+[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]]
823	823
824	824
825		-* (% style="color:blue" %)**Click to upload**
826	826
827		-[[image:1664503808294-336.png]]
828	828
829	829
830	830
831		-* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
832		-
833		-[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
834		-
835		-
836		-
837	837	= 7.  FAQ =
838	838
839	839
	825	+
840	840	== 7.1 How to change the LoRa Frequency Bands/Region? ==
841	841
842	842
843		-User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
	829	+User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
844	844
845	845
846	846
...	...	@@ -870,6 +870,7 @@
870	870	(% style="color:blue" %)**XXX**(%%): The default frequency band
871	871
872	872	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
	859	+* (% style="color:red" %)**CN470**(%%): Default frequency band CN470
873	873	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
874	874	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
875	875	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
...	...	@@ -877,25 +877,33 @@
877	877	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
878	878	* (% style="color:red" %)**US915**(%%): Default frequency band US915
879	879
	867	+
880	880	= 9.  Packing Info =
881	881
882	882
883	883	**Package Includes**:
884	884
885		-* TrackerD LoRaWAN GPS/BLE Tracker x 1
886		-* USB recharge & program cable x 1
	873	+* TrackerD x 1
	874	+* Rechargeable cable x 1
	875	+* Program Cable x 1
887	887
888	888	**Dimensions and Weight**:
889	889
890		-* Device Size: 85 x 48 x 15 cm
891		-* Weight: 50g
	879	+* Device Size: 85 x 48 x 15 mm/pcs
	880	+* Weight: 55g/pcs
892	892
893		-= 10. Support =
894	894
895	895
	884	+= 10. Support =
	885	+
896	896	* 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.
897		-* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
	887	+* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
898	898
	889	+[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
	890	+
	891	+
	892	+
	893	+
899	899	= 11.  Reference =
900	900
901	901

1664501652064-326.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-143.9 KB

Content

1664501677253-891.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-202.7 KB

Content

1664501711466-918.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-62.0 KB

Content

1664501721248-725.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-55.6 KB

Content

1664501734705-405.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-64.1 KB

Content

1664501784668-703.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-62.0 KB

Content

1664501958445-288.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-74.1 KB

Content

1664502116362-706.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-56.0 KB

Content

1664502166010-515.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-41.3 KB

Content

1664502425687-834.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-38.2 KB

Content

1664502649601-895.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-59.2 KB

Content

1664502676891-606.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-64.3 KB

Content

1664502695771-538.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-54.7 KB

Content

1664502715371-321.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-79.9 KB

Content

1664502835802-546.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-37.8 KB

Content

1664502854406-763.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-14.3 KB

Content

1664502999401-486.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-916.7 KB

Content

1664503022490-662.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-133.6 KB

Content

1664503035713-500.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-354.0 KB

Content

1664503047675-651.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-199.1 KB

Content

1664503563660-578.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-38.1 KB

Content

1664503574618-659.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-139.8 KB

Content

1664503593459-435.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-183.3 KB

Content

1664503611848-385.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-175.9 KB

Content

1664503635019-941.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-161.8 KB

Content

1664503715811-892.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-36.6 KB

Content

1664503752288-974.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-112.6 KB

Content

1664503794261-827.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-119.5 KB

Content

1664503808294-336.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-161.6 KB

Content

1664503824081-592.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-77.4 KB

Content

1664503831430-500.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-147.8 KB

Content

1664505654417-133.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-27.5 KB

Content