Changes for page TrackerD -- LoRaWAN Tracker User Manual

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 33 added, 0 removed)
  • 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

Author

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

Content

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

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