Changes for page TrackerD -- LoRaWAN Tracker User Manual

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 34 added, 0 removed)
  • 1664505654417-133.png
  • 1665301570342-765.png
  • 1665301636888-168.png
  • 1665301687277-443.png
  • 1665301786397-168.png
  • 1667288597595-714.png
  • image-20221006181316-1.png
  • image-20221006181357-2.png
  • image-20221009160220-1.png
  • image-20221009160309-2.png
  • image-20221009234629-1.png
  • image-20221009234703-2.png
  • image-20221024105643-1.png
  • image-20221024105643-2.png
  • image-20221102140621-1.png
  • image-20221102140638-2.png
  • image-20221102140704-3.png
  • image-20221102140712-4.png
  • image-20221102140748-5.png
  • image-20221102140801-6.png
  • image-20221107145243-1.png
  • image-20221116111844-1.png
  • image-20221116111844-2.png
  • image-20221116111844-3.png
  • image-20221116111844-4.png
  • image-20221116111844-5.png
  • image-20221118104359-1.png
  • image-20221118105220-2.png
  • image-20221118105249-3.png
  • image-20221118105402-4.png
  • image-20221122100004-1.png
  • image-20221122100004-2.png
  • image-20221122100004-3.png
  • image-20221122100004-4.png

Details

Page properties

Content

...	...	@@ -1,6 +1,13 @@
	1	+(% style="text-align:center" %)
	2	+[[image:1664505654417-133.png]]
	3	+
	4	+
	5	+
	6	+
1	1	(% class="wikigeneratedid" %)
2	2	**Table of Contents:**
3	3
	10	+{{toc/}}
4	4
5	5
6	6
...	...	@@ -7,7 +7,6 @@
7	7
8	8	= 1.  Introduction =
9	9
10		-
11	11	== 1.1  What is TrackerD ==
12	12
13	13
...	...	@@ -18,10 +18,14 @@
18	18	(((
19	19	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.
20	20
	27	+(((
21	21	TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
	29	+)))
22	22
	31	+(((
23	23	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.
24	24	)))
	34	+)))
25	25
26	26	(((
27	27	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.
...	...	@@ -35,7 +35,6 @@
35	35	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
36	36
37	37
38		-
39	39	== 1.2 Specifications ==
40	40
41	41
...	...	@@ -94,7 +94,7 @@
94	94	* LoRaWAN 1.0.3 Class A
95	95	* ESP32 PICO D4
96	96	* SX1276/78 Wireless Chip
97		-* Arduino IDE Compatible
	106	+* Arduino IDE Compatible
98	98	* Open source hardware / software
99	99	* Regular/ Real-time GPS,BLE,WIFI tracking
100	100	* Built-in3 axis accelerometer (LIS3DH)
...	...	@@ -107,6 +107,7 @@
107	107	* Datalog
108	108
109	109
	119	+
110	110	== 1.4  Applications ==
111	111
112	112
...	...	@@ -115,9 +115,8 @@
115	115
116	116
117	117
118		-= 2.1 Use TrackerD =
	128	+= 2.  Use TrackerD =
119	119
120		-
121	121	== 2.1 How it works? ==
122	122
123	123
...	...	@@ -124,7 +124,6 @@
124	124	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.
125	125
126	126
127		-
128	128	== 2.2 Quick guide to connect to LoRaWAN server ==
129	129
130	130
...	...	@@ -142,11 +142,10 @@
142	142
143	143	Each TrackerD is shipped with a sticker with the default device EUI as below:
144	144
	153	+
145	145	[[image:1664501677253-891.png]]
146	146
147	147
148		-
149		-
150	150	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
151	151
152	152
...	...	@@ -167,114 +167,196 @@
167	167	**__Add APP KEY and DEV EUI:__**
168	168
169	169
170		-[[image:1664501784668-703.png]]
	177	+[[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	171
172	172
173	173
	181	+(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
174	174
175		-(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
	183	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
176	176
	185	+[[image:1664502835802-546.png]]
177	177
	187	+
178	178	(% 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.
179	179
180	180
181		-(% style="color:blue" %)**Positioning Mode(SMOD):**
	191	+== 2.3  Positioning Mode(SMOD) ==
182	182
183		-* **GPS ONLY(Factory Settings): **only get GPS location info.
184		-* **BLE ONLY: **Only obtain iBeacon info via BLE. Design for Indoor tracking.
185		-* **GPS/BLE Hybrid: **Combination for Indoor and Outdoor tracking.
186	186
187		-User can switch modes by [[changing SMOD>>path:#Positioning_Mode]].
	194	+Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
188	188
	196	+* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
	197	+* (% 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.
	198	+* (% 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.
189	189
	200	+Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
190	190
191		-== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- ==
192	192
	203	+== 2.4  Uplink Payload ==
193	193
194		-=== 2.3.1 Uplink FPORT~=5, Device Status ===
	205	+=== 2.4.1 Uplink FPORT~=5, Device Status ===
195	195
196	196
	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.
197	197
198		-=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
	210	+Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
199	199
200	200
201		-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. )
	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
202	202
	217	+[[image:1665301570342-765.png]]
203	203
204		-(% border="2" style="background-color:#ffffcc; color:green; width:537px" %)
205		-|(% style="width:69px" %)(((
206		-**Size**
207	207
208		-**(bytes)**
209		-)))|(% style="width:76px" %)4|(% style="width:87px" %)4|(% style="width:76px" %)2|(% style="width:52px" %)1|(% style="width:88px" %)(((
210		-2
	220	+(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
211	211
212		-(optional )
213		-)))|(% style="width:83px" %)(((
214		-2
	222	+(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
215	215
216		-(optional)
217		-)))
218		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>path:#Location]]|(% style="width:87px" %)[[Longitude>>path:#Location]]|(% style="width:76px" %)(((
219		-[[Alarm &>>path:#Alarm]]
	224	+(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
220	220
221		-[[BAT>>path:#Alarm]]
222		-)))|(% style="width:52px" %)[[FLAG>>path:#Flag]]|(% style="width:88px" %)Hum|(% style="width:83px" %)[[Tem>>path:#Pitch]]
	226	+(% style="color:#037691" %)**Frequency Band**:
223	223
	228	+*0x01: EU868
224	224
	230	+*0x02: US915
225	225
226		-[[image:1664501958445-288.png]]
	232	+*0x03: IN865
227	227
	234	+*0x04: AU915
228	228
229		-**Alarm & BAT:**
	236	+*0x05: KZ865
230	230
231		-(% border="2" style="background-color:#ffffcc; color:green; width:329px" %)
232		-|(% style="width:72px" %)**Size(bit)**|(% style="width:67px" %)1 bit|(% style="width:118px" %)1bit|(% style="width:63px" %)14 bits
233		-|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>path:#BAT]]
	238	+*0x06: RU864
234	234
	240	+*0x07: AS923
235	235
	242	+*0x08: AS923-1
236	236
237		-**FLAG:**
	244	+*0x09: AS923-2
238	238
239		-(% border="2" style="background-color:#ffffcc; color:green; width:332px" %)
240		-|(% style="width:79px" %)**Size(bit)**|(% style="width:55px" %)2 bits|(% style="width:47px" %)1bit|(% style="width:140px" %)5 bits
241		-|(% style="width:79px" %)**Value**|(% style="width:55px" %)[[MOD>>path:#MD]]|(% style="width:47px" %)[[LON>>path:#LON]]|(% style="width:140px" %)Firmware version
	246	+*0x0a: AS923-3
242	242
	248	+Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
243	243
244		-**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A  **
	250	+(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
245	245
246	246
247		-**Location info:**
	253	+(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
248	248
249		-* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
250		-* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
	255	+Use can also get the Device Status uplink through the downlink command:
251	251
252	252
253		-**Important note:**
	258	+(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
254	254
255		-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.
	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
256	256
257		-2.  In firmware version v1.5, Roll & Pitch is disabled by default.
	264	+(% style="color:blue" %)** SMOD：**
258	258
259		-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:
	266	+(% style="color:red" %)** 1 :** (%%) GPS ONLY
260	260
	268	+(% style="color:red" %)** 2 :** (%%) BLE ONLY
261	261
262		-[[image:1664502116362-706.png]]
	270	+(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
263	263
264	264
	273	+(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
265	265
266		-4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
	275	+(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
267	267
	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	+
	294	+
	295	+=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
	296	+
	297	+
	298	+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,
	299	+
	300	+
	301	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	302	+|=(% scope="row" style="width: 60px;" %)(((
	303	+**Size(bytes)**
	304	+)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
	305	+2
	306	+)))|(% style="width:30px" %)(((
	307	+2
	308	+)))
	309	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	310	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	311	+)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
	312	+
	313	+[[image:1665301636888-168.png]]
	314	+
	315	+
	316	+==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
	317	+
	318	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	319	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
	320	+|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
	321	+
	322	+
	323	+
	324	+==== (% style="color:blue" %)**FLAG:**(%%) ====
	325	+
	326	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	327	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
	328	+|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
	329	+
	330	+**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
	331	+
	332	+
	333	+==== (% style="color:blue" %)**Location info:**(%%) ====
	334	+
	335	+* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
	336	+* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
	337	+
	338	+(% style="color:red" %)**Important note:**
	339	+
	340	+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.
	341	+
	342	+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:
	343	+
	344	+
	345	+[[image:1664502116362-706.png]]
	346	+
	347	+
	348	+3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
	349	+
268	268	[[image:1664502166010-515.png]]
269	269
270	270
271	271
272		-* **Alarm**:  Example:  0x4B & 0x40 >> 6 = 0x01
273		-* **BAT**:  Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
	354	+==== (% style="color:blue" %)**Alarm:**(%%) ====
274	274
275		-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: \
	356	+**Example: ** 0x4B & 0x40 >> 6 = 0x01
276	276
277	277
	359	+==== (% style="color:blue" %)**BAT:**(%%) ====
	360	+
	361	+**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
	362	+
	363	+(((
	364	+The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
	365	+)))
	366	+
278	278	* > 4.0v :  80% ~~ 100%
279	279	* 3.85v ~~3.99v:  60% ~~ 80%
280	280	* 3.70v ~~ 3.84v:  40% ~~ 60%
...	...	@@ -283,96 +283,172 @@
283	283
284	284
285	285
286		-* **LON: **Enable/Disable LED activity for uplink
	375	+==== (% style="color:blue" %)**MOD:**(%%) ====
287	287
288		-0x00:  Disable LED indicator.
	377	+**Example: ** (0x60>>6) & 0x3f =1
289	289
290		-0x01:  Enable LED indicator (Default Value)
	379	+**Set the format of GPS data uplink link：**
291	291
	381	+(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
	382	+(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
292	292
293		-* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
294		-* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree
295	295
	385	+**Set the format of BLE data uplink link：**
296	296
	387	+(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
297	297
298	298
	390	+==== (% style="color:blue" %)**LON:**(%%) ====
299	299
300		-=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
	392	+**Example:** (0x60>>5) & 0x01=1.
301	301
	394	+Enable/Disable LED activity for uplink
302	302
	396	+(((
	397	+(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
	398	+)))
303	303
304		-=== 2.3.4 BLE positioning Payload(Fport2) ===
	400	+(((
	401	+(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
	402	+)))
305	305
306	306
307		-Different MODE has different payload:
	405	+==== (% style="color:blue" %)**Hum:**(%%) ====
308	308
309		-**MODE=2**
	407	+0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
310	310
311		-(% border="2" style="background-color:#ffffcc; color:green; width:620px" %)
312		-|(% style="width:70px" %)(((
313		-**Size**
314	314
315		-**(bytes)**
316		-)))|(% style="width:54px" %)16|(% style="width:72px" %)4|(% style="width:71px" %)4|(% style="width:145px" %)2|(% style="width:72px" %)4|(% style="width:76px" %)2|(% style="width:54px" %)1
317		-|(% style="width:70px" %)**Value**|(% style="width:54px" %)[[UUID>>path:#Location]]|(% style="width:72px" %)(((
318		-iBeacon
	410	+==== (% style="color:blue" %)**Tem:**(%%) ====
319	319
320		-MAJOR
321		-)))|(% style="width:71px" %)(((
322		-iBeacon
	412	+011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
323	323
324		-MINOR
325		-)))|(% style="width:145px" %)(((
326		-iBeacon Measured
327	327
328		-Power
329		-)))|(% style="width:72px" %)(((
330		-iBeacon
	415	+=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
331	331
332		-RSSI
333		-)))|(% style="width:76px" %)(((
334		-[[Alarm &>>path:#Alarm]]
335	335
336		-[[BAT>>path:#Alarm]]
337		-)))|(% style="width:54px" %)[[FLAG>>path:#Flag]]
	418	+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)
338	338
	420	+
	421	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
	422	+|=(% scope="row" style="width: 60px;" %)(((
	423	+**Size(bytes)**
	424	+)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
	425	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	426	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	427	+)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
	428	+
	429	+(% class="wikigeneratedid" %)
	430	+[[image:1665301687277-443.png]]
	431	+
	432	+
	433	+=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
	434	+
	435	+
	436	+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.
	437	+
	438	+
	439	+(% style="color:red" %)**Note for this mode:**
	440	+
	441	+* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
	442	+* 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.
	443	+* 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
	444	+
	445	+The payload is 15 bytes, as below.
	446	+
	447	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	448	+|=(% scope="row" %)(((
	449	+**Size(bytes)**
	450	+)))|4|4|2|1|1|1|1|1
	451	+|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
	452	+
	453	+[[image:image-20221009160309-2.png]]
	454	+
	455	+
	456	+=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
	457	+
	458	+
	459	+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.
	460	+
	461	+User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
	462	+
	463	+
	464	+(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
	465	+|=(% scope="row" style="width: 60px;" %)(((
	466	+**Size(bytes)**
	467	+)))|(% 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
	468	+|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
	469	+iBeacon MAJOR
	470	+)))|(% style="width:63px" %)(((
	471	+iBeacon MINOR
	472	+)))|(% style="width:71px" %)(((
	473	+iBeacon Measured Power
	474	+)))|(% style="width:50px" %)(((
	475	+iBeacon RSSI
	476	+)))|(% style="width:47px" %)(((
	477	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	478	+)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
	479	+
339	339	[[image:1664502425687-834.png]]
340	340
341	341
342		-* **BAT**:  Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
343		-* **MODE:  **Define the payload format.
344		-* **UUID:  **The uuid from the strongest iBeacon.
345		-* **MAJOR**:  The MAJOR from the strongest iBeacon.
346		-* **MINOR**:  The MAJOR from the strongest iBeacon.
347		-* **Measured** **Power**:  The Measured Power from the strongest iBeacon.
348		-* **RSSI**:  The RSSI from the strongest iBeacon.
	483	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	484	+* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
	485	+* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
	486	+* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
	487	+* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
	488	+* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
	489	+* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
349	349
350	350
351	351
	493	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
352	352
353	353
354		-=== 2.3.5 Add Payload format in TTN V3 ===
	496	+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.
355	355
356	356
357		-In TTN V3, use can add a custom payload so it shows friendly.
	499	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	500	+|=(% scope="row" style="width: 60px;" %)(((
	501	+**Size(bytes)**
	502	+)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
	503	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
	504	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	505	+)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
358	358
359		-In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
	507	+(% class="wikigeneratedid" %)
	508	+[[image:1667288597595-714.png||height="212" width="1151"]]
360	360
361	361
	511	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	512	+* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
	513	+* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
	514	+
	515	+
	516	+
	517	+=== 2.4.7  Add Payload format in TTN V3 ===
	518	+
	519	+
	520	+In TTN V3, user can add a custom payload so it shows friendly.
	521	+
	522	+In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
	523	+
	524	+
362	362	[[image:1664502649601-895.png]]
363	363
364		-Add the decoder from this link:
365	365
366	366
	529	+Add the decoder from this link:
	530	+
	531	+[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	532	+
367	367	Save the change the uplink message will be parsed. As below:
368	368
369	369	[[image:1664502676891-606.png]]
370	370
371	371
	538	+== 2.5 Integrate with Datacake ==
372	372
373		-== 2.4 Integrate with Datacake ==
374	374
375		-
376	376	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.
377	377
378	378	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]]
...	...	@@ -381,12 +381,11 @@
381	381	[[image:1664502695771-538.png]]
382	382
383	383
	549	+== 2.6 Integrate with Tago ==
384	384
385		-== 2.5 Integrate with Tago ==
386	386
	552	+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.
387	387
388		-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.
389		-
390	390	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]]
391	391
392	392
...	...	@@ -393,73 +393,95 @@
393	393	[[image:1664502715371-321.png]]
394	394
395	395
	560	+== 2.7  Datalog Feature ==
396	396
397		-== 2.6 Alarm Mode ==
398	398
	563	+total 273 entries,by default,
399	399
400		-User can push the **RED button** by more than 5 seconds to enter Alarm Mode.
	565	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
401	401
	567	+Example use case.
402	402
403		-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.
	569	+[[image:image-20221009234703-2.png||height="328" width="899"]]
404	404
405	405
406		-Two ways to exit alarm mode:
	572	+[[image:image-20221009234629-1.png||height="390" width="577"]]
407	407
408		-* Server send a downlink command to exit.
409		-* User fast press the RED button 10 times.
410	410
411		-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.
	575	+== 2.8 Alarm Mode ==
412	412
413	413
	578	+(((
	579	+User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
	580	+)))
414	414
415		-== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
416	416
	583	+(((
	584	+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.
	585	+)))
417	417
418	418
419		-== 2.8 LED Status ==
	588	+(((
	589	+**Two ways to exit alarm mode:**
	590	+)))
420	420
	592	+* Server sends a downlink command to exit.
	593	+* User fast press the RED button 10 times.
421	421
422		-(% border="2" style="background-color:#ffffcc; color:green; width:636px" %)
423		-|(% style="width:157px" %)**Event**|(% style="width:271px" %)**Action**|(% style="width:202px" %)**AT+LON to control on/off**
424		-|(% style="width:157px" %)**Power On**|(% style="width:271px" %)**BLUE, RED , Green** flash once|(% style="width:202px" %)N/A
425		-|(% style="width:157px" %)**Join request**|(% style="width:271px" %)**Green** led fast blink once (200ms)|(% style="width:202px" %)Yes
426		-|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)**Green** led on 5 second|(% style="width:202px" %)N/A
427		-|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)**BLUE **blinks 200ms per second|(% style="width:202px" %)Yes
428		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)**GREEN **blinks twice (200ms per blink)|(% style="width:202px" %)Yes
429		-|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)**RED **blinks twice (200ms per blink)|(% style="width:202px" %)Yes
430		-|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)**RED **on for 3 seconds|(% style="width:202px" %)Yes
431		-|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)**RED **on for 1 second|(% style="width:202px" %)Yes
432		-|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)**BLUE **led on 5 second|(% style="width:202px" %)Yes
433		-|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)**GREEN** led on 1 second|(% style="width:202px" %)Yes
434		-|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)**RED **on 500ms|(% style="width:202px" %)N/A
	595	+(((
	596	+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.
	597	+)))
435	435
436	436
	600	+== 2.9 Transport Mode ==
437	437
438	438
439		-== 2.9 Button Function ==
	603	+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.
440	440
441	441
442		-**RESET button:**
	606	+== 2.10 LED Status ==
443	443
	608	+
	609	+(% border="1.5" style="background-color:#ffffcc; width:500px" %)
	610	+|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
	611	+|(% 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
	612	+|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
	613	+|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
	614	+|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
	615	+|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
	616	+|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
	617	+|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
	618	+|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
	619	+|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
	620	+|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
	621	+|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
	622	+
	623	+
	624	+
	625	+== 2.11 Button Function ==
	626	+
	627	+
	628	+(% style="color:blue" %)**RESET button:**
	629	+
444	444	[[image:1664502835802-546.png]]
445	445
446	446	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
447	447
448	448
449		-**RED button:**
	635	+(% style="color:red" %)**RED button:**
450	450
451	451	[[image:1664502854406-763.png]]
452	452
453	453
454		-(% border="2" style="background-color:#ffffcc; color:green; width:627px" %)
455		-|(% style="width:135px" %)**Function**|(% style="width:220px" %)**Action**|(% style="width:265px" %)**Description**
456		-|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing **RED** button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>path:#Alarm_Mode]]
457		-|(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the **RED** button 10 times|(% style="width:265px" %)Exit Alarm Mode
	640	+(% border="1" style="background-color:#ffffcc; width:510px" %)
	641	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
	642	+|(% 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"]]
	643	+|(% 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
458	458	|(% 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.
459	459
460	460
461	461
462		-== 2.10 USB Port Function ==
	648	+== 2.12 USB Port Function ==
463	463
464	464
465	465	The USB interface of TrackerD has below functions:
...	...	@@ -466,21 +466,19 @@
466	466
467	467	* Power on the device
468	468	* Recharge the battery
469		-* [[Configure Device>>path:#AT_Command]]
470		-* [[Upgrade Firmware>>path:#upgrade_image]]
	655	+* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	656	+* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
471	471
472	472
473	473
474		-
475	475	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
476	476
477	477
478	478	User can configure TrackerD via AT Command or LoRaWAN Downlink.
479	479
480		-LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]]
	665	+LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
481	481
482	482
483		-
484	484	== 3.1 Access AT Command ==
485	485
486	486
...	...	@@ -490,17 +490,15 @@
490	490	[[image:1664502999401-486.png]]
491	491
492	492
493		-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:
	677	+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:
494	494
495	495
496	496	[[image:1664503022490-662.png]]
497	497
498	498
499		-
500	500	[[image:1664503035713-500.png]]
501	501
502	502
503		-
504	504	[[image:1664503047675-651.png]]
505	505
506	506
...	...	@@ -507,148 +507,149 @@
507	507
508	508	== 3.2 Command Set ==
509	509
510		-
511	511	=== 3.2.1 Set Transmit Interval ===
512	512
513	513
514	514	Set device uplink interval.
515	515
516		-* AT Command:
	697	+* (% style="color:blue" %)**AT Command:**
517	517
518		-AT+TDC=xxx
	699	+(% style="color:#037691" %)**AT+TDC=xxx **
519	519
520	520	Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
521	521
522	522
523		-* Downlink Payload (prefix 0x01):
	704	+* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
524	524
525		-0x01 00 01 2C     ~/~/  Same as AT+TDC=300000
	706	+(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
526	526
527	527
528		-
529	529	=== 3.2.2 Set Alarm Packet transmission interval ===
530	530
531	531
532	532	Set alarm packet transmit interval
533	533
534		-* AT Command:
	714	+* (% style="color:blue" %)**AT Command:**
535	535
536		-AT+ATDC=xx.
	716	+(% style="color:#037691" %)**AT+ATDC=xx. **
537	537
538		-Example:  AT+ATDC=60000  **~-~->  ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
	718	+Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
539	539
540	540
541		-* Downlink Payload (prefix 0xB1):
	721	+* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
542	542
543		-0xB1 00 00 3C  ~/~/  Same as AT+ATDC=60000
	723	+(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
544	544
545	545
	726	+=== 3.2.3 Set Transport Mode Packet transmission interval ===
546	546
547		-=== 3.2.3 Set Sports Mode Packet transmission interval ===
548	548
	729	+Set Transport Mode packet transmit interval
549	549
550		-Set sports packet transmit interval
	731	+* (% style="color:blue" %)**AT Command:**
551	551
552		-* AT Command:
	733	+(% style="color:#037691" %)**AT+MTDC=xx. **
553	553
554		-AT+MTDC=xx.
	735	+Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
555	555
556		- Example:  AT+MTDC=300000  **~-~->  ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
557	557
	738	+* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
558	558
559		-* Downlink Payload (prefix 0x03):
	740	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
560	560
561		-0x03 00 01 2C  ~/~/  Same as AT+ MTDC=3000000
562	562
563		-
564		-
565	565	=== 3.2.4 Exit Alarm ===
566	566
567	567
568	568	Server send downlink command to exit Alarm mode
569	569
570		-* AT Command:
	748	+* (% style="color:blue" %)**AT Command: No AT Command**
571	571
572		-No AT Command
	750	+* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
573	573
	752	+(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
574	574
575		-* Downlink Payload (prefix 0x02):
576	576
577		-0x02 01  ~/~/  Exit Alarm Mode
578		-
579		-
580		-
581	581	=== 3.2.5 Disable/Enable LED flash ===
582	582
583	583
584	584	Disable/Enable LED for position, downlink and uplink
585	585
586		-* AT Command:
	760	+* (% style="color:blue" %)**AT Command:**
587	587
588		-AT+LON=xx.  (Disable (0), Enable (1), default:1)
	762	+(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
589	589
590		- Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
	764	+Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
591	591
592	592
593		-* Downlink Payload (prefix 0xAE):
	767	+* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
594	594
595		-0xAE 00  ~/~/  Same as AT+LON=0
	769	+(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
596	596
597	597
	772	+=== 3.2.6 Disable/Enable Transport Mode ===
598	598
599		-=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
600	600
	775	+Users can use this feature to enable/disable Transport Mode.
601	601
602		-User can use this feature to check and set thread hole of movement detect
	777	+* (% style="color:blue" %)**AT Command:**
603	603
604		-* AT Command:
	779	+(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
605	605
606		-AT+INTWK=xx.  (Disable (0), Enable (1), default:0)
	781	+Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
607	607
608		- Example:  AT+ INTWK =1  **~-~->  ** Enable detect movement.
609	609
	784	+* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
610	610
611		-* Downlink Payload (prefix 0xAF):
	786	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
612	612
613		-0xAF 01  ~/~/  Same as AT+ INTWK =1
614	614
	789	+=== 3.2.7 Set Positioning Mode ===
615	615
616	616
617		-=== 3.2.7 Set Positioning Mode ===
	792	+SMOD define how TrackerD scan and uplink data:
618	618
619	619
620		-SMOD define the how TrackerD scan and uplink date.
	795	+* (% style="color:blue" %)**AT Command:**
621	621
622		-GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
	797	+(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
623	623
624		-BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
	799	+(% style="color:#037691" %)** aa:**
625	625
626		-GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
	801	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
627	627
628		-运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
	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.
629	629
	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.
630	630
	807	+(% style="color:#037691" %)**bb:**
631	631
632		-* AT Command:
	809	+* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
633	633
634		-AT+SMOD=xx.
	811	+* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
635	635
	813	+(% style="color:#037691" %)**cc:   **
636	636
637		- **Example:**
	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(%%))
638	638
639		- AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
	819	+(% style="color:blue" %)**Example:**
640	640
641		- AT+ SMOD =1,1    **~-~->**  GPS +BAT State
	821	+ AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
642	642
643		- AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
	823	+ AT+SMOD=1,1,0 ~-~->  GPS +BAT State
644	644
	825	+ AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
645	645
646		-* Downlink Payload (prefix 0xA5):
	827	+ AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
647	647
648		-0xA5 01 00  ~/~/  Same as AT+ SMOD =1,0
649	649
	830	+* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
650	650
	832	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
651	651
	834	+
652	652	=== 3.2.8 Set MAX GPS position time ===
653	653
654	654
...	...	@@ -655,25 +655,24 @@
655	655	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.
656	656
657	657
658		-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.
	841	+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.
659	659
660	660
661		-* AT Command:
	844	+* (% style="color:blue" %)**AT Command:**
662	662
663		-AT+FTIME=xx  **~-~-> ** Set to use xx as max fix time.
	846	+(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
664	664
665		-Example:  AT+FTIME=150
	848	+**Example:**  AT+FTIME=150
666	666
667	667
668		-* Downlink Payload (prefix 0xAA):
	851	+* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
669	669
670		-0xAA 00 96  ~/~/  Set AT+FTIME=150
	853	+(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
671	671
672	672
	856	+=== 3.2.9 Set PDOP value for GPS fix accuracy ===
673	673
674		-=== 3.3.9 Set PDOP value for GPS fix accuracy ===
675	675
676		-
677	677	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.
678	678
679	679
...	...	@@ -680,40 +680,123 @@
680	680	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
681	681
682	682
683		-* AT Command:
	865	+* (% style="color:blue" %)**AT Command:**
684	684
685		-AT+PDOP=2.5  **~-~->  ** Set PDOP to 2.5
	867	+(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
686	686
687	687
688		-* Downlink Payload (prefix 0xAD):
	870	+* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
689	689
690		-0xAD 00 0A  ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
	872	+(% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
691	691
692		-0xAD 00 19  ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
	874	+(% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
693	693
694		-0xAD 00 46  ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
	876	+(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
695	695
696	696
697		-Disable/Enable the confirmation mode
698	698
699		-* AT Command:
	880	+**Disable/Enable the confirmation mode**
700	700
701		-AT+CFM=xx.
	882	+* (% style="color:blue" %)**AT Command:**
702	702
	884	+(% style="color:#037691" %)**AT+CFM=xx**
703	703
	886	+
704	704	**~ Example:**
705	705
706		- AT+ CFM=0    **~-~->  ** Disable confirmation
	889	+ AT+CFM=0    **~-~->   ** Disable confirmation
707	707
708		- AT+ CFM=1    **~-~->  ** Enable confirmation
	891	+ AT+CFM=1    **~-~->  ** Enable confirmation
709	709
710	710
711		-* Downlink Payload (prefix 0x05):
	894	+* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
712	712
713		-0x05 01  ~/~/  Same as AT+ SMOD =1
	896	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
714	714
715	715
	899	+=== 3.2.10  Auto Send None-ACK messages ===
716	716
	901	+
	902	+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.
	903	+
	904	+
	905	+* (% style="color:blue" %)**AT Command: AT+PNACKMD**
	906	+
	907	+The default factory setting is 0.
	908	+
	909	+
	910	+**Command Example Function Response:**
	911	+
	912	+(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
	913	+
	914	+
	915	+* (% style="color:blue" %)**Downlink Command: 0x34**
	916	+
	917	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
	918	+
	919	+
	920	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
	921	+
	922	+
	923	+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.
	924	+
	925	+(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
	926	+
	927	+(% style="color:blue" %)**AT Command:**
	928	+
	929	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	930	+
	931	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	932	+
	933	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
	934	+
	935	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
	936	+
	937	+
	938	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
	939	+
	940	+
	941	+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.
	942	+
	943	+(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
	944	+
	945	+(% style="color:blue" %)**AT Command:**
	946	+
	947	+ (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	948	+
	949	+ (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	950	+
	951	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
	952	+
	953	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
	954	+
	955	+
	956	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
	957	+
	958	+
	959	+Users can use this feature to enable/disable Information printing.
	960	+
	961	+(% style="color:blue" %)**AT Command:**
	962	+
	963	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
	964	+\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
	965	+
	966	+
	967	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	968	+
	969	+
	970	+The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	971	+
	972	+(% style="color:blue" %)**AT Command:**
	973	+
	974	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
	975	+
	976	+
	977	+(% style="color:blue" %)**Downlink Payload:0X24**
	978	+
	979	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
	980	+
	981	+
717	717	= 4. Setting for Different Scenarios =
718	718
719	719
...	...	@@ -720,7 +720,6 @@
720	720
721	721	= 5. Upload Firmware =
722	722
723		-
724	724	== 5.1 Firmware Change Log ==
725	725
726	726
...	...	@@ -727,7 +727,6 @@
727	727	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
728	728
729	729
730		-
731	731	== 5.2 How to upgrade firmware ==
732	732
733	733
...	...	@@ -742,11 +742,9 @@
742	742	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
743	743
744	744
745		-(% style="color:blue" %)**Step3：**(%%) Download and Install Flash Tool:
	1008	+(% 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]]
746	746
747		-[[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]]
748	748
749		-
750	750	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
751	751
752	752
...	...	@@ -756,56 +756,64 @@
756	756	[[image:1664503574618-659.png]]
757	757
758	758
	1020	+
759	759	(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
760	760
761		-[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1023	+[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
762	762
763	763
764		-Users need to use below files:
	1026	+**Users need to use below files:**
765	765
766	766	boot_app0.bin @0e000
767	767
768		-ESP_LORA-eeprom-class.bin @ 0x10000
	1030	+US915.bin @ 0x10000(Select the bin file of the frequency band you need)
769	769
770	770
771		-[[image:1664503593459-435.png]]
	1033	+[[image:image-20221118105220-2.png]]
772	772
773	773
774	774
775	775	After upgrade finish, it will show finish as below:
776	776
777		-[[image:1664503611848-385.png]]
	1039	+[[image:image-20221118105402-4.png]]
778	778
779	779
780	780
781	781	= 6. Developer Guide =
782	782
783		-
784	784	== 6.1 Compile Source Code ==
785	785
786		-
787	787	=== 6.1.1 Set up ARDUINO compile environment ===
788	788
789	789
790		-* 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]]
	1050	+* **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]]**
791	791
792		-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]]
	1052	+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]]
793	793
794	794
795	795	[[image:1664503635019-941.png]]
796	796
797	797
798		-* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it.
799	799
	1059	+* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
800	800
801		-
802	802	[[image:1664503715811-892.png]]
803	803
804	804
	1064	+(% 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.
805	805
806		-* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
	1066	+[[image:image-20221024105643-1.png]]
807	807
	1068	+**~ Figure1**
808	808
	1070	+
	1071	+[[image:image-20221024105643-2.png]]
	1072	+
	1073	+ **Figure2**
	1074	+
	1075	+
	1076	+* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
	1077	+
809	809	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
810	810
811	811
...	...	@@ -812,38 +812,34 @@
812	812	[[image:1664503752288-974.png]]
813	813
814	814
815		-
816	816	== 6.2 Source Code ==
817	817
818	818
819		-* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
	1087	+* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
820	820
821	821	[[image:1664503794261-827.png]]
822	822
823	823
824	824
825		-* Click to upload
	1093	+* (% style="color:blue" %)**Click to upload**
826	826
827	827	[[image:1664503808294-336.png]]
828	828
829	829
830	830
831		-* Check the result, if the upload is successful, as shown below, open the serial port to view the data
	1099	+* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
832	832
833	833	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
834	834
835	835
836		-
837	837	= 7.  FAQ =
838	838
839		-
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>>path:#upgrade_image]]. When download the images, choose the required image file for download.
	1109	+User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
844	844
845	845
846		-
847	847	== 7.2 What is the pin mapping for the USB program cable? ==
848	848
849	849
...	...	@@ -851,8 +851,8 @@
851	851
852	852
853	853
854		-(% border="2" style="background-color:#ffffcc; color:green; width:314px" %)
855		-|(% style="width:118px" %)**Pin**|(% style="width:67px" %)**Color**|(% style="width:123px" %)**USB Pin**
	1119	+(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
	1120	+|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
856	856	|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
857	857	|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
858	858	|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
...	...	@@ -864,55 +864,243 @@
864	864
865	865
866	866
	1132	+== 7.3 Notes on using different serial port tools for TrackerD ==
867	867
	1134	+=== 7.3.1  Serial port utility ===
868	868
869		-= 8.  Order Info =
870	870
	1137	+Serial port utility requires you to automatically add data streams.
871	871
	1139	+Need to adjust the data stream to RTS/CTS on physical restart.
	1140	+
	1141	+(% class="wikigeneratedid" %)
	1142	+[[image:image-20221102140621-1.png]]
	1143	+
	1144	+
	1145	+
	1146	+When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1147	+
	1148	+[[image:image-20221102140638-2.png]]
	1149	+
	1150	+
	1151	+=== 7.3.2  SecureCRT ===
	1152	+
	1153	+
	1154	+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.
	1155	+
	1156	+
	1157	+[[image:image-20221102140704-3.png]]
	1158	+
	1159	+
	1160	+[[image:image-20221102140712-4.png]]
	1161	+
	1162	+
	1163	+=== 7.3.3  PUTTY ===
	1164	+
	1165	+
	1166	+[[image:image-20221102140748-5.png]]
	1167	+
	1168	+
	1169	+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.
	1170	+
	1171	+
	1172	+[[image:image-20221102140801-6.png]]
	1173	+
	1174	+
	1175	+== 7.4 How to modify source code to compile different frequency band bin file? ==
	1176	+
	1177	+
	1178	+(% class="box infomessage" %)
	1179	+(((
	1180	+(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
	1181	+See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
	1182	+)))
	1183	+
	1184	+**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
	1185	+
	1186	+
	1187	+[[image:image-20221116111844-1.png||height="227" width="782"]]
	1188	+
	1189	+
	1190	+
	1191	+**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
	1192	+
	1193	+
	1194	+[[image:image-20221116111844-2.png||height="262" width="781"]]
	1195	+
	1196	+
	1197	+
	1198	+**3. Compile the AS923_JP band, please refer to the intention shown**
	1199	+
	1200	+
	1201	+[[image:image-20221116111844-3.png||height="338" width="746"]]
	1202	+
	1203	+
	1204	+
	1205	+**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.**
	1206	+
	1207	+
	1208	+[[image:image-20221116111844-4.png||height="641" width="739"]]
	1209	+
	1210	+
	1211	+[[image:image-20221116111844-5.png||height="551" width="708"]]
	1212	+
	1213	+
	1214	+= 8  Trouble Shooting =
	1215	+
	1216	+== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
	1217	+
	1218	+
	1219	+(((
	1220	+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
	1221	+)))
	1222	+
	1223	+
	1224	+== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
	1225	+
	1226	+
	1227	+(((
	1228	+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.
	1229	+)))
	1230	+
	1231	+
	1232	+== 8.3  Problem after Upgrading Firmware ==
	1233	+
	1234	+=== 8.3.1 Continue Restart after upgrading ===
	1235	+
	1236	+
	1237	+(((
	1238	+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
	1239	+)))
	1240	+
	1241	+
	1242	+[[image:image-20221118105249-3.png]]
	1243	+
	1244	+
	1245	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1246	+
	1247	+
	1248	+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.1
	1249	+
	1250	+
	1251	+
	1252	+==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
	1253	+
	1254	+
	1255	+[[image:image-20221122100004-1.png||height="497" width="534"]]
	1256	+
	1257	+ ** Figure 1  **
	1258	+
	1259	+
	1260	+ [[image:image-20221122100004-2.png||height="619" width="389"]]
	1261	+
	1262	+ **Figure 2**
	1263	+
	1264	+
	1265	+
	1266	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
	1267	+
	1268	+
	1269	+[[image:image-20221122100004-3.png]]
	1270	+
	1271	+Please AT+FDR, and then enter the following instructions by the information on the label
	1272	+
	1273	+AT+DEUI=70B3D57ED0053981
	1274	+
	1275	+AT+APPEUI=D23345667BCBCCAF
	1276	+
	1277	+AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1278	+
	1279	+AT+DADDR=260b4dce
	1280	+
	1281	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
	1282	+
	1283	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
	1284	+
	1285	+
	1286	+
	1287	+==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
	1288	+
	1289	+
	1290	+[[image:image-20221122100004-4.png]]
	1291	+
	1292	+
	1293	+== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
	1294	+
	1295	+
	1296	+Please download version 1.4.2 again
	1297	+
	1298	+
	1299	+== 8.5  How to deal with unsuccessful GPS positioning? ==
	1300	+
	1301	+
	1302	+1） Make Sure the device is in Open Area where can see the sky.
	1303	+
	1304	+2)  Set PDOP to a higher value.
	1305	+
	1306	+* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1307	+
	1308	+* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1309	+
	1310	+* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1311	+
	1312	+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
	1313	+
	1314	+
	1315	+= 9.  Order Info =
	1316	+
	1317	+
872	872	Part Number: (% style="color:blue" %)**TrackerD-XXX**
873	873
874	874	(% style="color:blue" %)**XXX**(%%): The default frequency band
875	875
876	876	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
	1323	+
877	877	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
	1325	+
878	878	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
	1327	+
879	879	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
	1329	+
880	880	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
	1331	+
881	881	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
	1333	+
882	882	* (% style="color:red" %)**US915**(%%): Default frequency band US915
883	883
884	884
885	885
	1338	+= 10.  Packing Info =
886	886
887	887
888		-= 9.  Packing Info =
	1341	+(% style="color:#037691" %)**Package Includes**:
889	889
890		-
891		-**Package Includes**:
892		-
893	893	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1344	+
894	894	* USB recharge & program cable x 1
895	895
896		-**Dimensions and Weight**:
	1347	+(% style="color:#037691" %)**Dimensions and Weight**:
897	897
898		-* Device Size: 85 x 48 x 15 cm
	1349	+* Device Size: 85 x 48 x 15 mm
	1350	+
899	899	* Weight: 50g
900	900
901	901
902	902
	1355	+= 11. Support =
903	903
904		-= 10. Support =
905	905
906		-
907	907	* 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.
908		-* 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]]
909	909
	1360	+* 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]].
910	910
911	911
912	912
913		-= 11.  Reference =
	1364	+= 12.  Reference =
914	914
915	915
916	916	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1368	+
917	917	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
	1370	+
918	918	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]

1664505654417-133.png

Author

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

Size

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

Content

1665301570342-765.png

Author

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

Size

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

Content

1665301636888-168.png

Author

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

Size

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

Content

1665301687277-443.png

Author

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

Size

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

Content

1665301786397-168.png

Author

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

Size

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

Content

1667288597595-714.png

Author

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

Size

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

Content

image-20221006181316-1.png

Author

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

Size

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

Content

image-20221006181357-2.png

Author

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

Size

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

Content

image-20221009160220-1.png

Author

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

Size

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

Content

image-20221009160309-2.png

Author

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

Size

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

Content

image-20221009234629-1.png

Author

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

Size

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

Content

image-20221009234703-2.png

Author

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

Size

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

Content

image-20221024105643-1.png

Author

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

Size

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

Content

image-20221024105643-2.png

Author

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

Size

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

Content

image-20221102140621-1.png

Author

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

Size

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

Content

image-20221102140638-2.png

Author

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

Size

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

Content

image-20221102140704-3.png

Author

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

Size

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

Content

image-20221102140712-4.png

Author

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

Size

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

Content

image-20221102140748-5.png

Author

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

Size

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

Content

image-20221102140801-6.png

Author

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

Size

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

Content

image-20221107145243-1.png

Author

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

Size

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

Content

image-20221116111844-1.png

Author

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

Size

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

Content

image-20221116111844-2.png

Author

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

Size

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

Content

image-20221116111844-3.png

Author

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

Size

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

Content

image-20221116111844-4.png

Author

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

Size

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

Content

image-20221116111844-5.png

Author

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

Size

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

Content

image-20221118104359-1.png

Author

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

Size

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

Content

image-20221118105220-2.png

Author

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

Size

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

Content

image-20221118105249-3.png

Author

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

Size

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

Content

image-20221118105402-4.png

Author

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

Size

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

Content

image-20221122100004-1.png

Author

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

Size

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

Content

image-20221122100004-2.png

Author

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

Size

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

Content

image-20221122100004-3.png

Author

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

Size

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

Content

image-20221122100004-4.png

Author

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

Size

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

Content