Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)

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
...	...	@@ -40,13 +40,12 @@
40	40
41	41	)))
42	42
43		-[[image:1664499921684-770.png]]
	42	+[[image:1664499921684-770.png||_mstalt="298194"]]
44	44
45	45
46	46	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47	47
48	48
49		-
50	50	== 1.2 Specifications ==
51	51
52	52
...	...	@@ -61,13 +61,11 @@
61	61	* EEPROM: 520 KB
62	62	* Clock Speed: 32Mhz
63	63
64		-
65	65	(% style="color:blue" %)**Common DC Characteristics:**
66	66
67	67	* Supply Voltage: 5V via USB port or Internal li-on battery
68	68	* Operating Temperature: -40 ~~ 60°C
69	69
70		-
71	71	(% style="color:blue" %)**LoRa Spec:**
72	72
73	73	* Frequency Range,
...	...	@@ -89,12 +89,10 @@
89	89	* Packet engine up to 256 bytes with CRC.
90	90	* LoRaWAN 1.0.3 Specification
91	91
92		-
93	93	(% style="color:blue" %)**Battery:**
94	94
95	95	* 1000mA Li-on Battery power (for model TrackerD)
96	96
97		-
98	98	(% style="color:blue" %)**Power Consumption**
99	99
100	100	* Sleeping Mode: 200uA
...	...	@@ -101,8 +101,6 @@
101	101	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
102	102	* Tracking: max: 38mA
103	103
104		-
105		-
106	106	== 1.3  Features ==
107	107
108	108
...	...	@@ -109,7 +109,7 @@
109	109	* LoRaWAN 1.0.3 Class A
110	110	* ESP32 PICO D4
111	111	* SX1276/78 Wireless Chip
112		-** Arduino IDE Compatible
	104	+* Arduino IDE Compatible
113	113	* Open source hardware / software
114	114	* Regular/ Real-time GPS,BLE,WIFI tracking
115	115	* Built-in3 axis accelerometer (LIS3DH)
...	...	@@ -121,8 +121,6 @@
121	121	* Tri-color LED, Alarm button
122	122	* Datalog
123	123
124		-
125		-
126	126	== 1.4  Applications ==
127	127
128	128
...	...	@@ -129,11 +129,8 @@
129	129	* Logistics and Supply Chain Management
130	130	* Human tracking
131	131
	122	+= 2.  Use TrackerD =
132	132
133		-
134		-= 2.1 Use TrackerD =
135		-
136		-
137	137	== 2.1 How it works? ==
138	138
139	139
...	...	@@ -140,7 +140,6 @@
140	140	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.
141	141
142	142
143		-
144	144	== 2.2 Quick guide to connect to LoRaWAN server ==
145	145
146	146
...	...	@@ -147,7 +147,7 @@
147	147	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.
148	148
149	149
150		-[[image:1664501652064-326.png]]
	136	+[[image:1664501652064-326.png||_mstalt="293306"]]
151	151
152	152
153	153
...	...	@@ -159,7 +159,7 @@
159	159	Each TrackerD is shipped with a sticker with the default device EUI as below:
160	160
161	161
162		-[[image:1664501677253-891.png]]
	148	+[[image:1664501677253-891.png||_mstalt="296569"]]
163	163
164	164
165	165	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -168,14 +168,14 @@
168	168	**__Add APP EUI in the application:__**
169	169
170	170
171		-[[image:1664501711466-918.png]]
	157	+[[image:1664501711466-918.png||_mstalt="295828"]]
172	172
173	173
174	174
175		-[[image:1664501721248-725.png]]
	161	+[[image:1664501721248-725.png||_mstalt="294450"]]
176	176
177	177
178		-[[image:1664501734705-405.png]]
	164	+[[image:1664501734705-405.png||_mstalt="293306"]]
179	179
180	180
181	181
...	...	@@ -182,71 +182,159 @@
182	182	**__Add APP KEY and DEV EUI:__**
183	183
184	184
185		-[[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"]]
186	186
187	187
188	188
	175	+(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
189	189
190		-(% 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"]]
191	191
	179	+[[image:1664502835802-546.png||_mstalt="295061"]]
192	192
	181	+
193	193	(% 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.
194	194
195	195
196		-(% style="color:blue" %)**Positioning Mode(SMOD):**
	185	+== 2.3  Positioning Mode(SMOD) ==
197	197
198		-* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
199		-* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
200		-* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
201	201
202		-User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
	188	+Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
203	203
	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.
204	204
	194	+Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
205	205
206		-== 2.3 Uplink Payload ==
207	207
	197	+== 2.4  Uplink Payload ==
208	208
209		-=== 2.3.1 Uplink FPORT~=5, Device Status ===
	199	+=== 2.4.1 Uplink FPORT~=5, Device Status ===
210	210
211	211
	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.
212	212
213		-=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
	204	+Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
214	214
215	215
216		-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
217	217
	211	+[[image:1665301570342-765.png||_mstalt="294580"]]
218	218
219		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:500px" %)
220		-|=(% scope="row" style="width: 50px;" %)(((
	213	+
	214	+(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
	215	+
	216	+(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
	217	+
	218	+(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
	219	+
	220	+(% style="color:#037691" %)**Frequency Band**:
	221	+
	222	+*0x01: EU868
	223	+
	224	+*0x02: US915
	225	+
	226	+*0x03: IN865
	227	+
	228	+*0x04: AU915
	229	+
	230	+*0x05: KZ865
	231	+
	232	+*0x06: RU864
	233	+
	234	+*0x07: AS923
	235	+
	236	+*0x08: AS923-1
	237	+
	238	+*0x09: AS923-2
	239	+
	240	+*0x0a: AS923-3
	241	+
	242	+Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
	243	+
	244	+(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
	245	+
	246	+
	247	+(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
	248	+
	249	+Use can also get the Device Status uplink through the downlink command:
	250	+
	251	+
	252	+(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
	253	+
	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;" %)(((
221	221	**Size(bytes)**
222		-)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:80px" %)(((
223		-2(optional )
224		-)))|(% style="width:80px" %)(((
225		-2(optional)
	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
226	226	)))
227	227	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
228	228	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
229		-)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:83px" %)[[Tem>>||anchor="HTem:"]]
	303	+)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
230	230
231		-[[image:1664501958445-288.png]]
	305	+[[image:1665301636888-168.png||_mstalt="298012"]]
232	232
233	233
234		-==== (% style="color:blue" %)Alarm & BAT:(%%) ====
	308	+==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
235	235
236		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:280px" %)
237		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14 bits
	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
238	238	|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
239	239
240		-==== (% style="color:blue" %)FLAG:(%%) ====
	314	+==== (% style="color:blue" %)**FLAG:**(%%) ====
241	241
242		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:280px" %)
243		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2 bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
244		-|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H2.3.4BLEpositioningPayload28Fport229"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version
	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:"]]
245	245
246	246	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
247	247
248	248
249		-==== (% style="color:blue" %)Location info:(%%) ====
	323	+==== (% style="color:blue" %)**Location info:**(%%) ====
250	250
251	251	* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
252	252	* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
...	...	@@ -255,35 +255,31 @@
255	255
256	256	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.
257	257
258		-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:
259	259
260		-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:
261	261
	335	+[[image:1664502116362-706.png||_mstalt="293306"]]
262	262
263		-[[image:1664502116362-706.png]]
264	264
	338	+3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
265	265
	340	+[[image:1664502166010-515.png||_mstalt="291395"]]
266	266
267		-4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
268	268
269		-[[image:1664502166010-515.png]]
270	270
	344	+==== (% style="color:blue" %)**Alarm:**(%%) ====
271	271
	346	+**Example: ** 0x4B & 0x40 >> 6 = 0x01
272	272
273		-==== (% style="color:blue" %)Alarm:(%%) ====
274	274
	349	+==== (% style="color:blue" %)**BAT:**(%%) ====
275	275
276		-Example:  0x4B & 0x40 >> 6 = 0x01
	351	+**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
277	277
	353	+(((
	354	+The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
	355	+)))
278	278
279		-==== (% style="color:blue" %)BAT:(%%) ====
280		-
281		-
282		-Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
283		-
284		-The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
285		-
286		-
287	287	* > 4.0v :  80% ~~ 100%
288	288	* 3.85v ~~3.99v:  60% ~~ 80%
289	289	* 3.70v ~~ 3.84v:  40% ~~ 60%
...	...	@@ -290,46 +290,100 @@
290	290	* 3.40v ~~ 3.69v:  20% ~~ 40%
291	291	* < 3.39v:  0~~20%
292	292
293		-==== (% style="color:blue" %)LON:(%%) ====
	363	+==== (% style="color:blue" %)**MOD:**(%%) ====
294	294
295		-
	365	+**Example: ** (0x60>>6) & 0x3f =1
	366	+
	367	+**Set the format of GPS data uplink link：**
	368	+
	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
	371	+
	372	+
	373	+**Set the format of BLE data uplink link：**
	374	+
	375	+(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
	376	+
	377	+
	378	+==== (% style="color:blue" %)**LON:**(%%) ====
	379	+
	380	+**Example:** (0x60>>5) & 0x01=1.
	381	+
296	296	Enable/Disable LED activity for uplink
297	297
298		-0x00:  Disable LED indicator.
	384	+(((
	385	+(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
	386	+)))
299	299
300		-0x01:  Enable LED indicator (Default Value)
	388	+(((
	389	+(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
	390	+)))
301	301
302	302
303		-==== (% style="color:blue" %)Hum:(%%) ====
	393	+==== (% style="color:blue" %)**Hum:**(%%) ====
304	304
305	305	0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
306	306
307	307
308		-==== (% style="color:blue" %)Tem:(%%) ====
	398	+==== (% style="color:blue" %)**Tem:**(%%) ====
309	309
310	310	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
311	311
312	312
	403	+=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
313	313
314	314
315		-=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
	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)
316	316
317	317
	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:"]]
318	318
319		-=== 2.3.4 BLE positioning Payload(Fport2) ===
	417	+(% class="wikigeneratedid" %)
	418	+[[image:1665301687277-443.png||_mstalt="296140"]]
320	320
321	321
322		-Different MODE has different payload:
	421	+=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
323	323
324		-**MODE=2**
325	325
326		-(% border="2" style="background-color:#ffffcc; color:green; width:491px" %)
327		-|(% style="width:70px" %)(((
328		-**Size**
	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.
329	329
330		-**(bytes)**
331		-)))|(% style="width:44px" %)16|(% style="width:61px" %)4|(% style="width:63px" %)4|(% style="width:71px" %)2|(% style="width:50px" %)4|(% style="width:47px" %)2|(% style="width:15px" %)1
332		-|(% style="width:70px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
	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" %)(((
333	333	iBeacon MAJOR
334	334	)))|(% style="width:63px" %)(((
335	335	iBeacon MINOR
...	...	@@ -341,93 +341,138 @@
341	341	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
342	342	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
343	343
344		-[[image:1664502425687-834.png]]
	468	+[[image:1664502425687-834.png||_mstalt="296738"]]
345	345
346	346
347		-* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
	471	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
348	348	* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
349	349	* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
350	350	* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
351		-* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
	475	+* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
352	352	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
353	353	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
354	354
355		-=== 2.3.5 Add Payload format in TTN V3 ===
	479	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
356	356
357	357
358		-In TTN V3, use can add a custom payload so it shows friendly.
	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.
359	359
	484	+
	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:"]]
	492	+
	493	+(% class="wikigeneratedid" %)
	494	+[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	495	+
	496	+
	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.
	500	+
	501	+=== 2.4.7  Add Payload format in TTN V3 ===
	502	+
	503	+
	504	+In TTN V3, user can add a custom payload so it shows friendly.
	505	+
360	360	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
361	361
362	362
363		-[[image:1664502649601-895.png]]
	509	+[[image:1664502649601-895.png||_mstalt="296985"]]
364	364
365	365
366		-Add the decoder from this link:
367	367
	513	+Add the decoder from this link:
368	368
	515	+[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	516	+
369	369	Save the change the uplink message will be parsed. As below:
370	370
371		-[[image:1664502676891-606.png]]
	519	+[[image:1664502676891-606.png||_mstalt="296673"]]
372	372
373	373
	522	+== 2.5 Integrate with Datacake ==
374	374
375		-== 2.4 Integrate with Datacake ==
376	376
377		-
378	378	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.
379	379
380	380	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	381
382	382
383		-[[image:1664502695771-538.png]]
	530	+[[image:1664502695771-538.png||_mstalt="297349"]]
384	384
385	385
	533	+== 2.6 Integrate with Tago ==
386	386
387		-== 2.5 Integrate with Tago ==
388	388
	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.
389	389
390		-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.
391		-
392	392	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]]
393	393
394	394
395		-[[image:1664502715371-321.png]]
	541	+[[image:1664502715371-321.png||_mstalt="292162"]]
396	396
397	397
	544	+== 2.7  Datalog Feature ==
398	398
399		-== 2.6 Alarm Mode ==
400	400
	547	+total 273 entries,by default,
401	401
	549	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	550	+
	551	+Example use case.
	552	+
	553	+[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	554	+
	555	+
	556	+[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	557	+
	558	+
	559	+== 2.8 Alarm Mode ==
	560	+
	561	+
	562	+(((
402	402	User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
	564	+)))
403	403
404	404
405		-Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
	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	+)))
406	406
407	407
408		-Two ways to exit alarm mode:
	572	+(((
	573	+**Two ways to exit alarm mode:**
	574	+)))
409	409
410		-* Server send a downlink command to exit.
	576	+* Server sends a downlink command to exit.
411	411	* User fast press the RED button 10 times.
412	412
	579	+(((
413	413	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	+)))
414	414
415	415
	584	+== 2.9 Transport Mode ==
416	416
417		-== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
418	418
	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.
419	419
420	420
421		-== 2.8 LED Status ==
	590	+== 2.10 LED Status ==
422	422
423	423
424		-(% border="2" style="background-color:#ffffcc; color:green; width:636px" %)
425		-|(% style="width:157px" %)**Event**|(% style="width:271px" %)**Action**|(% style="width:202px" %)**AT+LON to control on/off**
	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**
426	426	|(% 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
427	427	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
428	428	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
429	429	|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
430		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% 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
431	431	|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
432	432	|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
433	433	|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
...	...	@@ -435,12 +435,12 @@
435	435	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
436	436	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
437	437
438		-== 2.9 Button Function ==
	607	+== 2.11 Button Function ==
439	439
440	440
441		-(% style="color:green" %)**RESET button:**
	610	+(% style="color:blue" %)**RESET button:**
442	442
443		-[[image:1664502835802-546.png]]
	612	+[[image:1664502835802-546.png||_mstalt="295061"]]
444	444
445	445	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
446	446
...	...	@@ -447,19 +447,18 @@
447	447
448	448	(% style="color:red" %)**RED button:**
449	449
450		-[[image:1664502854406-763.png]]
	619	+[[image:1664502854406-763.png||_mstalt="295568"]]
451	451
452	452
453		-(% border="2" style="background-color:#ffffcc; color:green; width:627px" %)
454		-|(% style="width:135px" %)**Function**|(% style="width:220px" %)**Action**|(% style="width:265px" %)**Description**
455		-|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
	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"]]
456	456	|(% 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
457	457	|(% 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.
458	458
	628	+== 2.12 USB Port Function ==
459	459
460		-== 2.10 USB Port Function ==
461	461
462		-
463	463	The USB interface of TrackerD has below functions:
464	464
465	465	* Power on the device
...	...	@@ -467,7 +467,6 @@
467	467	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
468	468	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
469	469
470		-
471	471	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
472	472
473	473
...	...	@@ -476,7 +476,6 @@
476	476	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
477	477
478	478
479		-
480	480	== 3.1 Access AT Command ==
481	481
482	482
...	...	@@ -483,27 +483,24 @@
483	483	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.
484	484
485	485
486		-[[image:1664502999401-486.png]]
	652	+[[image:1664502999401-486.png||_mstalt="296985"]]
487	487
488	488
489	489	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:
490	490
491	491
492		-[[image:1664503022490-662.png]]
	658	+[[image:1664503022490-662.png||_mstalt="293332"]]
493	493
494	494
	661	+[[image:1664503035713-500.png||_mstalt="291096"]]
495	495
496		-[[image:1664503035713-500.png]]
497	497
	664	+[[image:1664503047675-651.png||_mstalt="295386"]]
498	498
499	499
500		-[[image:1664503047675-651.png]]
501	501
502		-
503		-
504	504	== 3.2 Command Set ==
505	505
506		-
507	507	=== 3.2.1 Set Transmit Interval ===
508	508
509	509
...	...	@@ -521,7 +521,6 @@
521	521	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
522	522
523	523
524		-
525	525	=== 3.2.2 Set Alarm Packet transmission interval ===
526	526
527	527
...	...	@@ -539,25 +539,23 @@
539	539	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
540	540
541	541
	704	+=== 3.2.3 Set Transport Mode Packet transmission interval ===
542	542
543		-=== 3.2.3 Set Sports Mode Packet transmission interval ===
544	544
	707	+Set Transport Mode packet transmit interval
545	545
546		-Set sports packet transmit interval
547		-
548	548	* (% style="color:blue" %)**AT Command:**
549	549
550	550	(% style="color:#037691" %)**AT+MTDC=xx. **
551	551
552		- Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
	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
553	553
554	554
555	555	* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
556	556
557		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
	718	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
558	558
559	559
560		-
561	561	=== 3.2.4 Exit Alarm ===
562	562
563	563
...	...	@@ -570,7 +570,6 @@
570	570	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
571	571
572	572
573		-
574	574	=== 3.2.5 Disable/Enable LED flash ===
575	575
576	576
...	...	@@ -580,7 +580,7 @@
580	580
581	581	(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
582	582
583		- Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
	742	+Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
584	584
585	585
586	586	* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
...	...	@@ -588,60 +588,69 @@
588	588	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
589	589
590	590
	750	+=== 3.2.6 Disable/Enable Transport Mode ===
591	591
592		-=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
593	593
	753	+Users can use this feature to enable/disable Transport Mode.
594	594
595		-User can use this feature to check and set thread hole of movement detect
596		-
597	597	* (% style="color:blue" %)**AT Command:**
598	598
599	599	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
600	600
601		- Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
	759	+Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
602	602
603	603
604	604	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
605	605
606		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
	764	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
607	607
608	608
609		-
610	610	=== 3.2.7 Set Positioning Mode ===
611	611
612	612
613		-SMOD define the how TrackerD scan and uplink date.
	770	+SMOD define how TrackerD scan and uplink data:
614	614
615		-GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
616	616
617		-BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
	773	+* (% style="color:blue" %)**AT Command:**
618	618
619		-GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
	775	+(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
620	620
621		-运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
	777	+(% style="color:#037691" %)** aa:**
622	622
	779	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
623	623
	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.
624	624
625		-* (% style="color:blue" %)**AT Command:**
	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.
626	626
627		-(% style="color:#037691" %)**AT+SMOD=xx. **
	785	+(% style="color:#037691" %)**bb:**
628	628
	787	+* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
629	629
630		- **Example:**
	789	+* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
631	631
632		- AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
	791	+(% style="color:#037691" %)**cc:   **
633	633
634		- AT+ SMOD =1,1    **~-~->**  GPS +BAT State
	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(%%))
635	635
636		- AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
	797	+(% style="color:blue" %)**Example:**
637	637
	799	+ AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
638	638
639		-* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	801	+ AT+SMOD=1,1,0 ~-~->  GPS +BAT State
640	640
641		-(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
	803	+ AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
642	642
	805	+ AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
643	643
644	644
	808	+* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	809	+
	810	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
	811	+
	812	+
645	645	=== 3.2.8 Set MAX GPS position time ===
646	646
647	647
...	...	@@ -648,7 +648,7 @@
648	648	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.
649	649
650	650
651		-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.
652	652
653	653
654	654	* (% style="color:blue" %)**AT Command:**
...	...	@@ -655,7 +655,7 @@
655	655
656	656	(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
657	657
658		-Example:  AT+FTIME=150
	826	+**Example:**  AT+FTIME=150
659	659
660	660
661	661	* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
...	...	@@ -663,10 +663,9 @@
663	663	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
664	664
665	665
	834	+=== 3.2.9 Set PDOP value for GPS fix accuracy ===
666	666
667		-=== 3.3.9 Set PDOP value for GPS fix accuracy ===
668	668
669		-
670	670	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.
671	671
672	672
...	...	@@ -688,26 +688,108 @@
688	688
689	689
690	690
691		-Disable/Enable the confirmation mode
	858	+**Disable/Enable the confirmation mode**
692	692
693	693	* (% style="color:blue" %)**AT Command:**
694	694
695		-(% style="color:#037691" %)**AT+CFM=xx. **
	862	+(% style="color:#037691" %)**AT+CFM=xx**
696	696
697	697
698	698	**~ Example:**
699	699
700		- AT+ CFM=0    **~-~->   ** Disable confirmation
	867	+ AT+CFM=0    **~-~->   ** Disable confirmation
701	701
702		- AT+ CFM=1    **~-~->  ** Enable confirmation
	869	+ AT+CFM=1    **~-~->  ** Enable confirmation
703	703
704	704
705	705	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
706	706
707		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
	874	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
708	708
709	709
	877	+=== 3.2.10  Auto Send None-ACK messages ===
710	710
	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	+
711	711	= 4. Setting for Different Scenarios =
712	712
713	713
...	...	@@ -714,7 +714,6 @@
714	714
715	715	= 5. Upload Firmware =
716	716
717		-
718	718	== 5.1 Firmware Change Log ==
719	719
720	720
...	...	@@ -721,7 +721,6 @@
721	721	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
722	722
723	723
724		-
725	725	== 5.2 How to upgrade firmware ==
726	726
727	727
...	...	@@ -736,96 +736,104 @@
736	736	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
737	737
738	738
739		-(% 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]]
	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]]
740	740
741	741
742	742	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
743	743
744	744
745		-[[image:1664503563660-578.png]]
	992	+[[image:1664503563660-578.png||_mstalt="296777"]]
746	746
747	747
748		-[[image:1664503574618-659.png]]
	995	+[[image:1664503574618-659.png||_mstalt="297986"]]
749	749
750	750
	998	+
751	751	(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
752	752
753		-[[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]]
754	754
755	755
756		-Users need to use below files:
	1004	+**Users need to use below files:**
757	757
758	758	boot_app0.bin @0e000
759	759
760		-ESP_LORA-eeprom-class.bin @ 0x10000
	1008	+US915.bin @ 0x10000(Select the bin file of the frequency band you need)
761	761
762	762
763		-[[image:1664503593459-435.png]]
	1011	+[[image:image-20221118105220-2.png||_mstalt="426608"]]
764	764
765	765
766	766
767	767	After upgrade finish, it will show finish as below:
768	768
769		-[[image:1664503611848-385.png]]
	1017	+[[image:image-20221118105402-4.png||_mstalt="427986"]]
770	770
771	771
772	772
773	773	= 6. Developer Guide =
774	774
775		-
776	776	== 6.1 Compile Source Code ==
777	777
778		-
779	779	=== 6.1.1 Set up ARDUINO compile environment ===
780	780
781	781
782		-* 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]]**
783	783
784	784	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]]
785	785
786	786
787		-[[image:1664503635019-941.png]]
	1033	+[[image:1664503635019-941.png||_mstalt="294658"]]
788	788
789	789
790		-* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) find the esp32 information and install it.
791	791
792		-[[image:1664503715811-892.png]]
	1037	+* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
793	793
	1039	+[[image:1664503715811-892.png||_mstalt="295698"]]
794	794
795	795
796		-* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
	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.
797	797
798		-Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
	1044	+[[image:image-20221024105643-1.png||_mstalt="428129"]]
799	799
	1046	+**~ Figure1**
800	800
801		-[[image:1664503752288-974.png]]
802	802
	1049	+[[image:image-20221024105643-2.png||_mstalt="428493"]]
803	803
	1051	+ **Figure2**
804	804
	1053	+
	1054	+* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
	1055	+
	1056	+Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
	1057	+
	1058	+
	1059	+[[image:1664503752288-974.png||_mstalt="298194"]]
	1060	+
	1061	+
805	805	== 6.2 Source Code ==
806	806
807	807
808	808	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
809	809
810		-[[image:1664503794261-827.png]]
	1067	+[[image:1664503794261-827.png||_mstalt="296387"]]
811	811
812	812
813	813
814	814	* (% style="color:blue" %)**Click to upload**
815	815
816		-[[image:1664503808294-336.png]]
	1073	+[[image:1664503808294-336.png||_mstalt="295711"]]
817	817
818	818
819	819
820	820	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
821	821
822		-[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
	1079	+[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
823	823
824	824
825		-
826	826	= 7.  FAQ =
827	827
828		-
829	829	== 7.1 How to change the LoRa Frequency Bands/Region? ==
830	830
831	831
...	...	@@ -832,16 +832,15 @@
832	832	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
833	833
834	834
835		-
836	836	== 7.2 What is the pin mapping for the USB program cable? ==
837	837
838	838
839		-[[image:1664499635206-262.png]]
	1093	+[[image:1664499635206-262.png||_mstalt="295360"]]
840	840
841	841
842	842
843		-(% border="2" style="background-color:#ffffcc; color:green; width:314px" %)
844		-|(% 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**
845	845	|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
846	846	|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
847	847	|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
...	...	@@ -851,43 +851,246 @@
851	851	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
852	852	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
853	853
854		-= 8.  Order Info =
	1108	+== 7.3 Notes on using different serial port tools for TrackerD ==
855	855
	1110	+=== 7.3.1  Serial port utility ===
856	856
	1112	+
	1113	+Serial port utility requires you to automatically add data streams.
	1114	+
	1115	+Need to adjust the data stream to RTS/CTS on physical restart.
	1116	+
	1117	+(% class="wikigeneratedid" %)
	1118	+[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1119	+
	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	+
857	857	Part Number: (% style="color:blue" %)**TrackerD-XXX**
858	858
859	859	(% style="color:blue" %)**XXX**(%%): The default frequency band
860	860
861	861	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
	1308	+
862	862	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
	1310	+
863	863	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
	1312	+
864	864	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
	1314	+
865	865	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
	1316	+
866	866	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
	1318	+
867	867	* (% style="color:red" %)**US915**(%%): Default frequency band US915
868	868
869		-= 9.  Packing Info =
	1321	+= 10.  Packing Info =
870	870
871	871
872		-**Package Includes**:
	1324	+(% style="color:#037691" %)**Package Includes**:
873	873
874	874	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1327	+
875	875	* USB recharge & program cable x 1
876	876
877		-**Dimensions and Weight**:
	1330	+(% style="color:#037691" %)**Dimensions and Weight**:
878	878
879		-* Device Size: 85 x 48 x 15 cm
	1332	+* Device Size: 85 x 48 x 15 mm
	1333	+
880	880	* Weight: 50g
881	881
882		-= 10. Support =
	1336	+= 11. Support =
883	883
884	884
885	885	* 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.
886		-* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
887	887
888		-= 11.  Reference =
	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]].
889	889
	1343	+= 12.  Reference =
890	890
	1345	+
891	891	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1347	+
892	892	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
	1349	+
893	893	* [[**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