Changes for page TrackerD -- LoRaWAN Tracker User Manual

Summary

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

Details

Page properties

Author

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

Content

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