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