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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 33 removed)
  • image-20221128102938-1.png
  • image-20221128103040-2.png
  • image-20221128110503-3.png
  • image-20221128111443-4.png
  • image-20221128111850-5.png
  • image-20221128111951-6.png
  • image-20221128112035-7.png
  • image-20221207120501-1.png
  • image-20221207120524-2.png
  • image-20221207120530-3.png
  • image-20221207120536-4.png
  • image-20221207120601-5.png
  • image-20221207133836-6.png
  • image-20221207133911-7.png
  • image-20221207134028-8.png
  • image-20221213100007-1.png
  • image-20221213100626-2.png
  • image-20221213100808-3.png
  • image-20221213101040-4.png
  • image-20221213102311-5.png
  • image-20221213102334-6.png
  • image-20221213102718-7.png
  • image-20221213110952-8.png
  • image-20230213110119-1.png
  • image-20230213110214-2.png
  • image-20230213110506-3.png
  • image-20230302145315-1.png
  • image-20230307135914-1.png
  • image-20230307135932-2.png
  • image-20230308115430-1.png
  • image-20230308115616-2.png
  • image-20230308115701-3.png
  • image-20230426085815-1.png

Details

Page properties

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% style="text-align:center" %)
2		-[[image:1664505654417-133.png||_mstalt="293696"]]
	2	+[[image:1664505654417-133.png]]
3	3
4	4
5	5
...	...	@@ -12,9 +12,9 @@
12	12
13	13
14	14
15		-
16	16	= 1.  Introduction =
17	17
	17	+
18	18	== 1.1  What is TrackerD ==
19	19
20	20
...	...	@@ -32,17 +32,21 @@
32	32	(((
33	33	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.
34	34	)))
	35	+)))
35	35
36	36	(((
37	37	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.
	39	+
	40	+
38	38	)))
39	39
40		-[[image:image-20230213110119-1.png||height="382" width="834"]]
	43	+[[image:1664499921684-770.png]]
41	41
42	42
43	43	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
44	44
45	45
	49	+
46	46	== 1.2 Specifications ==
47	47
48	48
...	...	@@ -93,10 +93,6 @@
93	93	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94	94	* Tracking: max: 38mA
95	95
96		-(% style="display:none" %)
97		-
98		-
99		-
100	100	== 1.3  Features ==
101	101
102	102
...	...	@@ -115,10 +115,6 @@
115	115	* Tri-color LED, Alarm button
116	116	* Datalog
117	117
118		-(% style="display:none" %)
119		-
120		-
121		-
122	122	== 1.4  Applications ==
123	123
124	124
...	...	@@ -125,12 +125,9 @@
125	125	* Logistics and Supply Chain Management
126	126	* Human tracking
127	127
128		-(% style="display:none" %)
129		-
130		-
131		-
132	132	= 2.  Use TrackerD =
133	133
	126	+
134	134	== 2.1 How it works? ==
135	135
136	136
...	...	@@ -137,6 +137,7 @@
137	137	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.
138	138
139	139
	133	+
140	140	== 2.2 Quick guide to connect to LoRaWAN server ==
141	141
142	142
...	...	@@ -143,7 +143,7 @@
143	143	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.
144	144
145	145
146		-[[image:image-20230213110214-2.png||height="388" width="847"]]
	140	+[[image:1664501652064-326.png]]
147	147
148	148
149	149
...	...	@@ -155,7 +155,7 @@
155	155	Each TrackerD is shipped with a sticker with the default device EUI as below:
156	156
157	157
158		-[[image:image-20230426085815-1.png||height="259" width="558"]]
	152	+[[image:1664501677253-891.png]]
159	159
160	160
161	161	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -164,14 +164,14 @@
164	164	**__Add APP EUI in the application:__**
165	165
166	166
167		-[[image:1664501711466-918.png||_mstalt="295828"]]
	161	+[[image:1664501711466-918.png]]
168	168
169	169
170	170
171		-[[image:1664501721248-725.png||_mstalt="294450"]]
	165	+[[image:1664501721248-725.png]]
172	172
173	173
174		-[[image:1664501734705-405.png||_mstalt="293306"]]
	168	+[[image:1664501734705-405.png]]
175	175
176	176
177	177
...	...	@@ -178,20 +178,21 @@
178	178	**__Add APP KEY and DEV EUI:__**
179	179
180	180
181		-[[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"]]
	175	+[[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"]]
182	182
183	183
184	184
185	185	(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
186	186
187		-(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
	181	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
188	188
189		-[[image:1664502835802-546.png||_mstalt="295061"]]
	183	+[[image:1664502835802-546.png]]
190	190
191	191
192	192	(% 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.
193	193
194	194
	189	+
195	195	== 2.3  Positioning Mode(SMOD) ==
196	196
197	197
...	...	@@ -204,21 +204,23 @@
204	204	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
205	205
206	206
	202	+
207	207	== 2.4  Uplink Payload ==
208	208
	205	+
209	209	=== 2.4.1 Uplink FPORT~=5, Device Status ===
210	210
211	211
212		-Uplink the device configures with (% style="color:blue" %)**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.
	209	+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.
213	213
214		-Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
	211	+Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
215	215
216	216
217		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
218		-|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1
219		-|(% 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
	214	+(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
	215	+|=(% 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
	216	+|=(% 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
220	220
221		-[[image:1665301570342-765.png||_mstalt="294580"]]
	218	+[[image:1665301570342-765.png]]
222	222
223	223
224	224	(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
...	...	@@ -229,30 +229,31 @@
229	229
230	230	(% style="color:#037691" %)**Frequency Band**:
231	231
232		-0x01: EU868
	229	+*0x01: EU868
233	233
234		-0x02: US915
	231	+*0x02: US915
235	235
236		-0x03: IN865
	233	+*0x03: IN865
237	237
238		-0x04: AU915
	235	+*0x04: AU915
239	239
240		-0x05: KZ865
	237	+*0x05: KZ865
241	241
242		-0x06: RU864
	239	+*0x06: RU864
243	243
244		-0x07: AS923
	241	+*0x07: AS923
245	245
246		-0x08: AS923-1
	243	+*0x08: AS923-1
247	247
248		-0x09: AS923-2
	245	+*0x09: AS923-2
249	249
250		-0x0a: AS923-3
	247	+*0x0a: AS923-3
251	251
252		-(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
	249	+Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
253	253
254	254	(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
255	255
	253	+
256	256	(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
257	257
258	258	Use can also get the Device Status uplink through the downlink command:
...	...	@@ -260,9 +260,9 @@
260	260
261	261	(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
262	262
263		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
264		-|(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
265		-|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
	261	+(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
	262	+|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
	263	+|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
266	266
267	267	(% style="color:blue" %)** SMOD：**
268	268
...	...	@@ -284,48 +284,47 @@
284	284
285	285	(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
286	286
287		-(% _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)(%%)
	285	+(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)
288	288
289	289
290	290	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
291	291
292		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
293		-|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:88px" %)1 Bit|(% style="width:50px" %)1 Bit|(% style="width:128px" %)1 Bit
294		-|(% style="width:75px" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
	290	+(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	291	+|=(% 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
	292	+|=(% 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"]]
295	295
296		-(% style="display:none" %)
297		-
298		-
299		-
300	300	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
301	301
302	302
303		-Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
	297	+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,
304	304
305	305
306		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)
307		-|(% style="width:60px" %)**Size(bytes)**|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)2|(% style="width:30px" %)2
308		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	300	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	301	+|=(% scope="row" style="width: 60px;" %)(((
	302	+**Size(bytes)**
	303	+)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
	304	+2
	305	+)))|(% style="width:30px" %)(((
	306	+2
	307	+)))
	308	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
309	309	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
310	310	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
311	311
312		-[[image:1665301636888-168.png||_mstalt="298012"]]
	312	+[[image:1665301636888-168.png]]
313	313
314	314
315	315	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
316	316
317		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)
318		-|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits
319		-|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]]
	317	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	318	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
	319	+|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
320	320
321		-(% style="display:none" %)
322		-
323		-
324	324	==== (% style="color:blue" %)**FLAG:**(%%) ====
325	325
326		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
327		-|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit
328		-|(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
	323	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	324	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
	325	+|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
329	329
330	330	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
331	331
...	...	@@ -342,12 +342,12 @@
342	342	2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
343	343
344	344
345		-[[image:1664502116362-706.png||_mstalt="293306"]]
	342	+[[image:1664502116362-706.png]]
346	346
347	347
348	348	3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
349	349
350		-[[image:1664502166010-515.png||_mstalt="291395"]]
	347	+[[image:1664502166010-515.png]]
351	351
352	352
353	353
...	...	@@ -370,9 +370,6 @@
370	370	* 3.40v ~~ 3.69v:  20% ~~ 40%
371	371	* < 3.39v:  0~~20%
372	372
373		-(% style="display:none" %) (%%)
374		-
375		-
376	376	==== (% style="color:blue" %)**MOD:**(%%) ====
377	377
378	378	**Example: ** (0x60>>6) & 0x3f =1
...	...	@@ -413,26 +413,30 @@
413	413	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
414	414
415	415
	410	+
416	416	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
417	417
418	418
419		-The default uplink payload includes total 11 bytes ((% style="color:blue" %)**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)
	414	+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)
420	420
421	421
422		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
423		-|(% style="width:60px" %)**Size(bytes)**|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1
424		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	417	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
	418	+|=(% scope="row" style="width: 60px;" %)(((
	419	+**Size(bytes)**
	420	+)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
	421	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
425	425	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
426	426	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
427	427
428	428	(% class="wikigeneratedid" %)
429		-[[image:1665301687277-443.png||_mstalt="296140"]]
	426	+[[image:1665301687277-443.png]]
430	430
431	431
	429	+
432	432	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
433	433
434	434
435		-Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-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.
	433	+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.
436	436
437	437
438	438	(% style="color:red" %)**Note for this mode:**
...	...	@@ -443,13 +443,16 @@
443	443
444	444	The payload is 15 bytes, as below.
445	445
446		-(% border="1" style="background-color:#f2f2f2; width:500px" %)
447		-|**Size(bytes)**|4|4|2|1|1|1|1|1
448		-|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
	444	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	445	+|=(% scope="row" %)(((
	446	+**Size(bytes)**
	447	+)))|4|4|2|1|1|1|1|1
	448	+|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
449	449
450		-[[image:image-20221009160309-2.png||_mstalt="429312"]]
	450	+[[image:image-20221009160309-2.png]]
451	451
452	452
	453	+
453	453	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
454	454
455	455
...	...	@@ -458,9 +458,11 @@
458	458	User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
459	459
460	460
461		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
462		-|(% style="width:60px" %)**Size(bytes)**|(% 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
463		-|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
	462	+(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
	463	+|=(% scope="row" style="width: 60px;" %)(((
	464	+**Size(bytes)**
	465	+)))|(% 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
	466	+|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
464	464	iBeacon MAJOR
465	465	)))|(% style="width:63px" %)(((
466	466	iBeacon MINOR
...	...	@@ -472,7 +472,7 @@
472	472	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
473	473	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
474	474
475		-[[image:1664502425687-834.png||_mstalt="296738"]]
	478	+[[image:1664502425687-834.png]]
476	476
477	477
478	478	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -483,69 +483,49 @@
483	483	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
484	484	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
485	485
486		-(% style="display:none" %) (%%)
	489	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
487	487
488	488
489		-=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
490		-
491		-
492		-The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
493		-
494		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
495		-|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
496		-|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
497		-
498		- [[image:image-20230302145315-1.png]]
499		-
500		-**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
501		-
502		-**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
503		-
504		-**mod** = bytes[2] & 0xC0;
505		-
506		-**Lon**=(bytes[2] & 0x20)
507		-
508		-
509		-=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
510		-
511		-
512	512	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.
513	513
514		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
515		-|(% style="width:65px" %)(((
	494	+
	495	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	496	+|=(% scope="row" style="width: 60px;" %)(((
516	516	**Size(bytes)**
517		-)))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
518		-|(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
	498	+)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
	499	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
519	519	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
520		-)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
	501	+)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
521	521
522	522	(% class="wikigeneratedid" %)
523		-[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	504	+[[image:1667288597595-714.png||height="212" width="1151"]]
524	524
	506	+
525	525	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
526	526	* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
527	527	* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
528	528
529		-(% style="display:none" %) (%%)
	511	+=== 2.4.7  Add Payload format in TTN V3 ===
530	530
531	531
532		-=== 2.4.8  Add Payload format in TTN V3 ===
533		-
534		-
535	535	In TTN V3, user can add a custom payload so it shows friendly.
536	536
537	537	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
538	538
539		-[[image:1664502649601-895.png||_mstalt="296985"]]
540	540
	519	+[[image:1664502649601-895.png]]
541	541
542		-Add the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
543	543
	522	+Add the decoder from this link:
	523	+
	524	+[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	525	+
544	544	Save the change the uplink message will be parsed. As below:
545	545
546		-[[image:1664502676891-606.png||_mstalt="296673"]]
	528	+[[image:1664502676891-606.png]]
547	547
548	548
	531	+
549	549	== 2.5 Integrate with Datacake ==
550	550
551	551
...	...	@@ -553,9 +553,11 @@
553	553
554	554	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]]
555	555
556		-[[image:1664502695771-538.png||_mstalt="297349"]]
557	557
	540	+[[image:1664502695771-538.png]]
558	558
	542	+
	543	+
559	559	== 2.6 Integrate with Tago ==
560	560
561	561
...	...	@@ -563,70 +563,32 @@
563	563
564	564	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]]
565	565
566		-[[image:1664502715371-321.png||_mstalt="292162"]]
567	567
	552	+[[image:1664502715371-321.png]]
568	568
569		-== 2.7  Integrate with Node-red ==
570	570
571	571
572		-~1. Install node-red, please refer to the installation method in the link:
	556	+== 2.7  Datalog Feature ==
573	573
574		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
575	575
576		-
577		-2. Import the created flow template, please refer to the import method in the link:
578		-
579		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
580		-
581		-
582		-The address of the flow template: [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]
583		-
584		-(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**
585		-
586		-[[image:image-20230307135914-1.png||height="527" width="1045"]]
587		-
588		-
589		-[[image:image-20230307135932-2.png||height="527" width="1044"]]
590		-
591		-
592		-3. Display the map
593		- Enter the link to the map:
594		-
595		- Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
596		-
597		-**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
598		-
599		-
600		- Hit all input in input stream
601		-
602		- [[image:image-20230308115616-2.png||height="563" width="1070"]]
603		-
604		-
605		- View map again
606		-
607		-[[image:image-20230308115701-3.png||height="571" width="1085"]]
608		-
609		-
610		-== 2.8  Datalog Feature ==
611		-
612		-
613	613	total 273 entries,by default,
614	614
615		-User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	561	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
616	616
617	617	Example use case.
618	618
619		-[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	565	+[[image:image-20221009234703-2.png||height="328" width="899"]]
620	620
621	621
622		-[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	568	+[[image:image-20221009234629-1.png||height="390" width="577"]]
623	623
624	624
625		-== 2.9  Alarm Mode ==
626	626
	572	+== 2.8 Alarm Mode ==
627	627
	574	+
628	628	(((
629		-User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
	576	+User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
630	630	)))
631	631
632	632
...	...	@@ -636,7 +636,7 @@
636	636
637	637
638	638	(((
639		-**Two ways to exit alarm mode:**
	586	+Two ways to exit alarm mode:
640	640	)))
641	641
642	642	* Server sends a downlink command to exit.
...	...	@@ -647,25 +647,19 @@
647	647	)))
648	648
649	649
650		-== 2.10  Transport Mode ==
651	651
	598	+== 2.9 Transport Mode ==
652	652
653		-In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
654	654
655		-When device is set in Transport Mode, it will uplink more frequenctly during moving.
	601	+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.
656	656
657		-* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
658		-* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
659		-* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
660	660
661		-(% style="display:none" %) (%%)
662	662
	605	+== 2.10 LED Status ==
663	663
664		-== 2.11  LED Status ==
665	665
666		-
667		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
668		-|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**Event**|=(% style="width: 200px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**AT+LON to control on/off**
	608	+(% border="1.5" style="background-color:#ffffcc; width:500px" %)
	609	+|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
669	669	|(% 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
670	670	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
671	671	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
...	...	@@ -678,15 +678,12 @@
678	678	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
679	679	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
680	680
681		-(% style="display:none" %) (%%)
	622	+== 2.11 Button Function ==
682	682
683	683
684		-== 2.12  Button Function ==
685		-
686		-
687	687	(% style="color:blue" %)**RESET button:**
688	688
689		-[[image:1664502835802-546.png||_mstalt="295061"]]
	627	+[[image:1664502835802-546.png]]
690	690
691	691	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
692	692
...	...	@@ -693,22 +693,18 @@
693	693
694	694	(% style="color:red" %)**RED button:**
695	695
696		-[[image:image-20230213110506-3.png]](% style="display:none" %)
	634	+[[image:1664502854406-763.png]]
697	697
698		-(% style="display:none" %) (%%)
699	699
700		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
701		-|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Description**
	637	+(% border="1" style="background-color:#ffffcc; width:510px" %)
	638	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
702	702	|(% 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"]]
703	703	|(% 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
704	704	|(% 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.
705	705
706		-(% style="display:none" %) (%%)
	643	+== 2.12 USB Port Function ==
707	707
708	708
709		-== 2.13  USB Port Function ==
710		-
711		-
712	712	The USB interface of TrackerD has below functions:
713	713
714	714	* Power on the device
...	...	@@ -716,19 +716,6 @@
716	716	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
717	717	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
718	718
719		-(% style="display:none" %) (%%)
720		-
721		-
722		-== 2.14  Sleep Mode ==
723		-
724		-
725		-(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
726		-
727		-In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
728		-
729		-Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
730		-
731		-
732	732	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
733	733
734	734
...	...	@@ -737,29 +737,32 @@
737	737	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
738	738
739	739
	661	+
740	740	== 3.1 Access AT Command ==
741	741
742	742
743	743	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.
744	744
745		-[[image:1664502999401-486.png||_mstalt="296985"]]
746	746
	668	+[[image:1664502999401-486.png]]
747	747
	670	+
748	748	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:
749	749
750	750
751		-[[image:1664503022490-662.png||_mstalt="293332"]]
	674	+[[image:1664503022490-662.png]]
752	752
753	753
754		-[[image:1664503035713-500.png||_mstalt="291096"]]
	677	+[[image:1664503035713-500.png]]
755	755
756	756
757		-[[image:1664503047675-651.png||_mstalt="295386"]]
	680	+[[image:1664503047675-651.png]]
758	758
759		-(% style="display:none" %) (%%)
760	760
	683	+
761	761	== 3.2 Command Set ==
762	762
	686	+
763	763	=== 3.2.1 Set Transmit Interval ===
764	764
765	765
...	...	@@ -777,6 +777,7 @@
777	777	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
778	778
779	779
	704	+
780	780	=== 3.2.2 Set Alarm Packet transmission interval ===
781	781
782	782
...	...	@@ -794,6 +794,7 @@
794	794	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
795	795
796	796
	722	+
797	797	=== 3.2.3 Set Transport Mode Packet transmission interval ===
798	798
799	799
...	...	@@ -811,6 +811,7 @@
811	811	(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
812	812
813	813
	740	+
814	814	=== 3.2.4 Exit Alarm ===
815	815
816	816
...	...	@@ -823,9 +823,10 @@
823	823	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
824	824
825	825
826		-=== 3.2.5 Disable/Enable LED flash and buzzer ===
827	827
	754	+=== 3.2.5 Disable/Enable LED flash ===
828	828
	756	+
829	829	Disable/Enable LED for position, downlink and uplink
830	830
831	831	* (% style="color:blue" %)**AT Command:**
...	...	@@ -840,6 +840,7 @@
840	840	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
841	841
842	842
	771	+
843	843	=== 3.2.6 Disable/Enable Transport Mode ===
844	844
845	845
...	...	@@ -857,6 +857,7 @@
857	857	(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
858	858
859	859
	789	+
860	860	=== 3.2.7 Set Positioning Mode ===
861	861
862	862
...	...	@@ -883,9 +883,9 @@
883	883
884	884	(% style="color:#037691" %)**cc:   **
885	885
886		-* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	816	+* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
887	887
888		-* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
	818	+* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
889	889
890	890	(% style="color:blue" %)**Example:**
891	891
...	...	@@ -903,6 +903,7 @@
903	903	(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
904	904
905	905
	836	+
906	906	=== 3.2.8 Set MAX GPS position time ===
907	907
908	908
...	...	@@ -909,7 +909,7 @@
909	909	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.
910	910
911	911
912		-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.
	843	+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.
913	913
914	914
915	915	* (% style="color:blue" %)**AT Command:**
...	...	@@ -924,6 +924,7 @@
924	924	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
925	925
926	926
	858	+
927	927	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
928	928
929	929
...	...	@@ -947,8 +947,8 @@
947	947	(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
948	948
949	949
950		-=== 3.2.10 Disable/Enable the confirmation mode ===
951	951
	883	+Disable/Enable the confirmation mode
952	952
953	953	* (% style="color:blue" %)**AT Command:**
954	954
...	...	@@ -967,9 +967,10 @@
967	967	(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
968	968
969	969
970		-=== 3.2.11  Auto Send None-ACK messages ===
971	971
	903	+=== 3.2.10  Auto Send None-ACK messages ===
972	972
	905	+
973	973	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.
974	974
975	975
...	...	@@ -985,12 +985,13 @@
985	985
986	986	* (% style="color:blue" %)**Downlink Command: 0x34**
987	987
988		-Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
	921	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
989	989
990	990
991		-=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
992	992
	925	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
993	993
	927	+
994	994	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.
995	995
996	996	(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
...	...	@@ -997,18 +997,19 @@
997	997
998	998	(% style="color:blue" %)**AT Command:**
999	999
1000		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	934	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1001	1001
1002		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	936	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1003	1003
1004	1004	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1005	1005
1006		-Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
	940	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1007	1007
1008	1008
1009		-=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1010	1010
	944	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1011	1011
	946	+
1012	1012	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.
1013	1013
1014	1014	(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
...	...	@@ -1015,158 +1015,44 @@
1015	1015
1016	1016	(% style="color:blue" %)**AT Command:**
1017	1017
1018		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	953	+ (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1019	1019
1020		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	955	+ (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1021	1021
1022	1022	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1023	1023
1024		-Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
	959	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1025	1025
1026	1026
1027		-=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
1028	1028
	963	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1029	1029
	965	+
1030	1030	Users can use this feature to enable/disable Information printing.
1031	1031
1032	1032	(% style="color:blue" %)**AT Command:**
1033	1033
1034		-(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
	970	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1035	1035	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1036	1036
1037	1037
1038		-=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1039	1039
	975	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1040	1040
	977	+
1041	1041	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
1042	1042
1043	1043	(% style="color:blue" %)**AT Command:**
1044	1044
1045		-(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
	982	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1046	1046
1047	1047
1048	1048	(% style="color:blue" %)**Downlink Payload:0X24**
1049	1049
1050		-Example: 0x24 01  ~/~/ Same as AT+CHE=1
	987	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
1051	1051
1052	1052
1053		-=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1054	1054
1055		-
1056		-User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1057		-
1058		-(% style="color:blue" %)**AT Command:**
1059		-
1060		-(% style="color:#037691" %)**AT+PT=xx**
1061		-
1062		- Example:
1063		-
1064		- AT+PT=14    ~-~->    Set to detect car motion.
1065		-
1066		- AT+PT=41  ~-~->    set to detect walk motion.
1067		-
1068		-
1069		-(% style="color:blue" %)**Downlink Payload:0xB4**
1070		-
1071		-0xB4 14          ~/~/  Same as AT+PT=14
1072		-
1073		-
1074		-=== 3.2.17  Set AT command window time（Since firmware 1.4.5） ===
1075		-
1076		-
1077		-AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1078		-
1079		-(% style="color:blue" %)**AT Command:**
1080		-
1081		-(% style="color:#037691" %)**AT+ATST=XX**
1082		-
1083		- Example:
1084		-
1085		- AT+ATST=15    ~-~-> Set the time to 15 seconds
1086		-
1087		-(% style="color:blue" %)**Downlink Payload:0XB5**
1088		-
1089		-0xB5 0F          ~/~/  Same as AT+ATST=15
1090		-
1091		-
1092		-=== 3.2.18  Set the stepmeter mode（Since firmware 1.4.5） ===
1093		-
1094		-
1095		-After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1096		-
1097		-(% style="color:blue" %)**AT Command:**
1098		-
1099		-(% style="color:#037691" %)**AT+PM=xx**
1100		-
1101		- Example:
1102		-
1103		- AT+PM=1    ~-~->  Turn on step counting mode
1104		-
1105		-AT+PM=0    ~-~->  Turn OFF step counting mode
1106		-
1107		-(% style="color:blue" %)**Downlink Payload:0XB6**
1108		-
1109		-0xB6 01          ~/~/  Same as AT+PM=1
1110		-
1111		-
1112		-=== 3.2.19  Set down the decline detection mode（Since firmware 1.4.5） ===
1113		-
1114		-
1115		-This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.
1116		-
1117		-(% style="color:blue" %)**AT Command:**
1118		-
1119		-(% style="color:#037691" %)**AT+FD=xx**
1120		-
1121		-**Example:**
1122		-
1123		-AT+FD=1    ~-~->  Turn on the Fall detection
1124		-
1125		-AT+FD=0    ~-~->  Turn OFF the Fall detection
1126		-
1127		-(% style="color:blue" %)**Downlink Payload:0XB7**
1128		-
1129		-0xB7 01          ~/~/  Same as AT+FD=1
1130		-
1131		-
1132		-=== 3.2.20 Disable/Enable buzzer（Since firmware 1.4.6） ===
1133		-
1134		-
1135		-Disable/Enable buzzer for Alarm, downlink and uplink
1136		-
1137		-(% style="color:blue" %)**AT Command:**
1138		-
1139		-(% style="color:#037691" %)**AT+BEEP=XX**
1140		-
1141		- Example:
1142		-
1143		-AT+BEEP=1 ~-~-> Turn on the buzzer
1144		-
1145		-AT+BEEP=0 ~-~-> Turn OFF the buzzer
1146		-
1147		-(% style="color:blue" %)**Downlink Payload:0XB9**
1148		-
1149		-0xB9 01 ~/~/ Same as AT+BEEP=1
1150		-
1151		-
1152		-=== 3.2.21 Set long press time（Since firmware 1.4.6） ===
1153		-
1154		-
1155		-When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
1156		-
1157		-(% style="color:blue" %)**AT Command:**
1158		-
1159		-(% style="color:#037691" %)**AT+EAT=XX**
1160		-
1161		- Example:
1162		-
1163		-AT+EAT=2 ~-~-> Set the long press time to 2s
1164		-
1165		-(% style="color:blue" %)**Downlink Payload:0XBA**
1166		-
1167		-0xBA 02 ~/~/ Same as AT+EAT=2
1168		-
1169		-
1170	1170	= 4. Setting for Different Scenarios =
1171	1171
1172	1172
...	...	@@ -1173,6 +1173,7 @@
1173	1173
1174	1174	= 5. Upload Firmware =
1175	1175
	997	+
1176	1176	== 5.1 Firmware Change Log ==
1177	1177
1178	1178
...	...	@@ -1179,6 +1179,7 @@
1179	1179	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
1180	1180
1181	1181
	1004	+
1182	1182	== 5.2 How to upgrade firmware ==
1183	1183
1184	1184
...	...	@@ -1199,10 +1199,10 @@
1199	1199	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1200	1200
1201	1201
1202		-[[image:1664503563660-578.png||_mstalt="296777"]]
	1025	+[[image:1664503563660-578.png]]
1203	1203
1204	1204
1205		-[[image:1664503574618-659.png||_mstalt="297986"]]
	1028	+[[image:1664503574618-659.png]]
1206	1206
1207	1207
1208	1208
...	...	@@ -1211,7 +1211,7 @@
1211	1211	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1212	1212
1213	1213
1214		-**Users need to use below files:**
	1037	+Users need to use below files:
1215	1215
1216	1216	boot_app0.bin @0e000
1217	1217
...	...	@@ -1218,19 +1218,22 @@
1218	1218	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1219	1219
1220	1220
1221		-[[image:image-20221207120501-1.png]]
	1044	+[[image:image-20221118105220-2.png]]
1222	1222
1223	1223
1224	1224
1225	1225	After upgrade finish, it will show finish as below:
1226	1226
1227		-[[image:image-20221207133911-7.png]]
	1050	+[[image:image-20221118105402-4.png]]
1228	1228
1229	1229
	1053	+
1230	1230	= 6. Developer Guide =
1231	1231
	1056	+
1232	1232	== 6.1 Compile Source Code ==
1233	1233
	1059	+
1234	1234	=== 6.1.1 Set up ARDUINO compile environment ===
1235	1235
1236	1236
...	...	@@ -1239,81 +1239,24 @@
1239	1239	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]]
1240	1240
1241	1241
1242		-[[image:1664503635019-941.png||_mstalt="294658"]]
	1068	+[[image:1664503635019-941.png]]
1243	1243
1244	1244
1245	1245
1246	1246	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1247	1247
1248		-[[image:1664503715811-892.png||_mstalt="295698"]]
	1074	+[[image:1664503715811-892.png]]
1249	1249
1250	1250
1251		-=== 6.1.2  Build the development environment ===
1252		-
1253		-
1254		-**~1. Download and install arduino IDE**
1255		-
1256		-[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1257		-
1258		-
1259		-**2. Download the ESP32 development package in the arduino IDE**
1260		-
1261		-[[image:image-20221213100007-1.png]]
1262		-
1263		-
1264		-Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1265		-
1266		-[[image:image-20221213100626-2.png]]
1267		-
1268		-
1269		-Restart the IDE after the addition is complete, then:
1270		-
1271		-[[image:image-20221213100808-3.png||height="679" width="649"]]
1272		-
1273		-
1274		-[[image:image-20221213101040-4.png]]
1275		-
1276		-
1277		-(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1278		-Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1279		-
1280		-
1281		-Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1282		-
1283		-(% style="color:blue" %)**Methods as below:**
1284		-
1285		-~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1286		-
1287		-2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1288		-
1289	1289	(% 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.
1290	1290
1291		-[[image:image-20221213102311-5.png||height="582" width="711"]]
	1079	+[[image:image-20221024105643-1.png]]
1292	1292
1293		-
1294		-**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1295		-
1296		-[[image:image-20221213102334-6.png]]
1297		-
1298		-(% style="color:red" %)**Note: This step requires a python environment**
1299		-
1300		-
1301		-Either way, in the end:
1302		-
1303		-The final effect is to open the arduino and you can see the esp32
1304		-
1305		-[[image:image-20221213110952-8.png||height="866" width="711"]]
1306		-
1307		-
1308		-
1309		-[[image:image-20221024105643-1.png||_mstalt="428129"]]
1310		-
1311	1311	**~ Figure1**
1312	1312
1313	1313
	1084	+[[image:image-20221024105643-2.png]]
1314	1314
1315		-[[image:image-20221024105643-2.png||_mstalt="428493"]]
1316		-
1317	1317	**Figure2**
1318	1318
1319	1319
...	...	@@ -1322,31 +1322,34 @@
1322	1322	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1323	1323
1324	1324
1325		-[[image:1664503752288-974.png||_mstalt="298194"]]
	1094	+[[image:1664503752288-974.png]]
1326	1326
1327	1327
	1097	+
1328	1328	== 6.2 Source Code ==
1329	1329
1330	1330
1331	1331	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1332	1332
1333		-[[image:1664503794261-827.png||_mstalt="296387"]]
	1103	+[[image:1664503794261-827.png]]
1334	1334
1335	1335
1336	1336
1337	1337	* (% style="color:blue" %)**Click to upload**
1338	1338
1339		-[[image:1664503808294-336.png||_mstalt="295711"]]
	1109	+[[image:1664503808294-336.png]]
1340	1340
1341	1341
1342	1342
1343	1343	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1344	1344
1345		-[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
	1115	+[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1346	1346
1347	1347
	1118	+
1348	1348	= 7.  FAQ =
1349	1349
	1121	+
1350	1350	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1351	1351
1352	1352
...	...	@@ -1353,14 +1353,16 @@
1353	1353	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1354	1354
1355	1355
	1128	+
1356	1356	== 7.2 What is the pin mapping for the USB program cable? ==
1357	1357
1358	1358
1359		-[[image:1664499635206-262.png||_mstalt="295360"]]
	1132	+[[image:1664499635206-262.png]]
1360	1360
1361	1361
1362		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1363		-|=(% style="width: 120px;background-color:#D9E2F3;color:#0070C0" %)**Pin**|=(% style="width: 69px;background-color:#D9E2F3;color:#0070C0" %)**Color**|=(% style="width: 125px;background-color:#D9E2F3;color:#0070C0" %)**USB Pin**
	1135	+
	1136	+(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
	1137	+|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
1364	1364	|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1365	1365	|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1366	1366	|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
...	...	@@ -1370,11 +1370,9 @@
1370	1370	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1371	1371	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1372	1372
1373		-(% style="display:none" %) (%%)
1374		-
1375		-
1376	1376	== 7.3 Notes on using different serial port tools for TrackerD ==
1377	1377
	1149	+
1378	1378	=== 7.3.1  Serial port utility ===
1379	1379
1380	1380
...	...	@@ -1382,15 +1382,18 @@
1382	1382
1383	1383	Need to adjust the data stream to RTS/CTS on physical restart.
1384	1384
	1157	+
1385	1385	(% class="wikigeneratedid" %)
1386		-[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1159	+[[image:image-20221102140621-1.png]]
1387	1387
1388	1388
1389	1389	When using AT commands, the data flow needs to be adjusted to XON/XOFF
1390	1390
1391		-[[image:image-20221102140638-2.png||_mstalt="428727"]]
1392	1392
	1165	+[[image:image-20221102140638-2.png]]
1393	1393
	1167	+
	1168	+
1394	1394	=== 7.3.2  SecureCRT ===
1395	1395
1396	1396
...	...	@@ -1397,22 +1397,23 @@
1397	1397	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.
1398	1398
1399	1399
1400		-[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1175	+[[image:image-20221102140704-3.png]]
1401	1401
1402	1402
1403		-[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1178	+[[image:image-20221102140712-4.png]]
1404	1404
1405	1405
	1181	+
1406	1406	=== 7.3.3  PUTTY ===
1407	1407
1408	1408
1409		-[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1185	+[[image:image-20221102140748-5.png]]
1410	1410
1411	1411
1412	1412	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.
1413	1413
1414	1414
1415		-[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1191	+[[image:image-20221102140801-6.png]]
1416	1416
1417	1417
1418	1418	== 7.4 How to modify source code to compile different frequency band bin file? ==
...	...	@@ -1424,58 +1424,38 @@
1424	1424	See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1425	1425	)))
1426	1426
1427		-**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
	1203	+1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1428	1428
	1205	+[[image:image-20221116111844-1.png||height="227" width="782"]]
1429	1429
1430		-[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
	1207	+2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1431	1431
	1209	+[[image:image-20221116111844-2.png||height="262" width="781"]]
1432	1432
	1211	+3.Compile the AS923_JP band, please refer to the intention shown
1433	1433
1434		-**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
	1213	+[[image:image-20221116111844-3.png||height="338" width="746"]]
1435	1435
	1215	+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.
1436	1436
1437		-[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1217	+[[image:image-20221116111844-4.png||height="641" width="739"]]
1438	1438
	1219	+[[image:image-20221116111844-5.png||height="551" width="708"]]
1439	1439
1440	1440
1441		-**3. Compile the AS923_JP band, please refer to the intention shown**
1442	1442
1443		-
1444		-[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1445		-
1446		-
1447		-
1448		-**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.**
1449		-
1450		-
1451		-[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1452		-
1453		-
1454		-[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1455		-
1456		-
1457		-== 7.5 Are there example python example for BLE Indoor Positioning? ==
1458		-
1459		-
1460		-[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1461		-
1462		-
1463		-== 7.6 Can alert mode and transport mode be used together? ==
1464		-
1465		-
1466		-Yes, you can also press the panic button to sound the alarm if set to transport mode
1467		-
1468		-
1469	1469	= 8  Trouble Shooting =
1470	1470
	1225	+
1471	1471	== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1472	1472
1473	1473
1474	1474	(((
1475		-Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**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
	1230	+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
1476	1476	)))
1477	1477
1478	1478
	1234	+
1479	1479	== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1480	1480
1481	1481
...	...	@@ -1484,157 +1484,86 @@
1484	1484	)))
1485	1485
1486	1486
	1243	+
1487	1487	== 8.3  Problem after Upgrading Firmware ==
1488	1488
1489		-=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
	1246	+=== 8.3.1 Continue Restart after upgrading ===
1490	1490
1491	1491
1492		-**Error Output**
1493		-
1494		-
1495		-[[image:image-20221122100004-4.png||_mstalt="424606"]]
1496		-
1497		-
1498	1498	(((
1499		-Some partition is missed during upgrade, please upgrade below four files as example:
1500		-
1501		-[[image:image-20221207120524-2.png]]
	1250	+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
1502	1502	)))
1503	1503
1504	1504
1505		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1254	+[[image:image-20221118105249-3.png]]
1506	1506
1507	1507
	1257	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1258	+
1508	1508	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
1509	1509
1510	1510
1511		-=== 8.3.3 "flash read err" after upgrade firmware ===
	1262	+==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1512	1512
	1264	+[[image:image-20221122100004-1.png||height="497" width="534"]]
1513	1513
1514		-Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
	1266	+ Figure 1
1515	1515
	1268	+ [[image:image-20221122100004-2.png||height="619" width="389"]]
1516	1516
1517		-[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
	1270	+ Figure 2
1518	1518
	1272	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
1519	1519
1520		-User need to upgrade again with below four files to solve this issue.
	1274	+[[image:image-20221122100004-3.png]]
1521	1521
1522		- [[image:image-20221207120530-3.png]]
	1276	+Please at+FDR, and then enter the following instructions by the information on the label
1523	1523
1524		- **Figure 2**
	1278	+AT+DEUI=70B3D57ED0053981
1525	1525
1526		-
1527		-=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1528		-
1529		-
1530		-User might erase the entire flash include keys and default settings which cause this issue.
1531		-
1532		-After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1533		-
1534		-
1535		-[[image:image-20221122100004-3.png||_mstalt="424242"]]
1536		-
1537		-
1538		-Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1539		-
1540		-After AT+FDR. please set
1541		-
1542		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1543		-
1544		-* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1545		-
1546		-**Example:**
1547		-
1548		-AT+PDOP=7.00
1549		-
1550		-AT+FTIME=180
1551		-
1552		-AT+DEUI=70B3D57ED0053981
1553		-
1554	1554	AT+APPEUI=D23345667BCBCCAF
1555	1555
1556	1556	AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1557	1557
1558		-AT+DADDR=260b4dce    ( no need for OTAA)
	1284	+AT+DADDR=260b4dce
1559	1559
1560		-AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
	1286	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1561	1561
1562		-AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
	1288	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1563	1563
1564	1564
1565		-== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1566	1566
	1292	+==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1567	1567
1568		-Please download version 1.4.2 again
	1294	+[[image:image-20221122100004-4.png]]
1569	1569
	1296	+(% class="wikigeneratedid" %)
	1297	+== ==
1570	1570
1571		-== 8.5  How to deal with unsuccessful GPS positioning? ==
	1299	+== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1572	1572
	1301	+Please download version 1.4.2 again
1573	1573
1574		-1） Make Sure the device is in Open Area where can see the sky.
1575	1575
	1304	+(((
	1305	+== 8.5 How to deal with unsuccessful GPS positioning? ==
	1306	+
	1307	+1） Make Sure the device is in Open Area where can see the sky.
1576	1576	2)  Set PDOP to a higher value.
1577	1577
1578		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1310	+ AT+PDOP=2(can be positioned precisely.）
1579	1579
1580		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1312	+ AT+PDOP=7(Quickly locate in open spaces）
1581	1581
1582		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1314	+ AT+PDOP=14.7(Positioning can be acquired in complex environments）
1583	1583
1584	1584	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
	1317	+)))
1585	1585
1586	1586
1587		-== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1320	+== ==
1588	1588
1589	1589
1590		-When upgrading, use the erase button to upgrade
1591		-
1592		-[[image:image-20221207120536-4.png]]
1593		-
1594		-
1595		-The parameters are displayed abnormally and cannot be fixed using AT+FDR
1596		-
1597		-[[image:image-20221128103040-2.png||height="431" width="525"]]
1598		-
1599		-
1600		-Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1601		-
1602		-[[image:image-20221207134028-8.png]]
1603		-
1604		-
1605		-Reboot information after upgrade
1606		-
1607		-[[image:image-20221128111443-4.png||height="432" width="546"]]
1608		-
1609		-
1610		-Use (% style="color:blue" %)**AT+FDR**(%%) command to reset and then use (% style="color:blue" %)**AT+CFG**(%%) to check whether the configuration is back to normal
1611		-
1612		-[[image:image-20221128111850-5.png]]
1613		-
1614		-
1615		-After the parameters return to normal, upgrade to the version you need again
1616		-
1617		-[[image:image-20221207120601-5.png]]
1618		-
1619		-
1620		-At this point, the parameters return to normal after running AT+FDR again
1621		-
1622		-[[image:image-20221128112035-7.png]]
1623		-
1624		-
1625		-== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1626		-
1627		-
1628		-~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1629		-
1630		-2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1631		-
1632		-
1633		-== 8.8  Why when using some serial consoles, only inputting the first string port console will return "error"? ==
1634		-
1635		-You need to enter the entire command at once, not a single character
1636		-You can open a command window or copy the entire command to the serial console
1637		-
1638	1638	= 9.  Order Info =
1639	1639
1640	1640
...	...	@@ -1643,22 +1643,13 @@
1643	1643	(% style="color:blue" %)**XXX**(%%): The default frequency band
1644	1644
1645	1645	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1646		-
1647	1647	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1648		-
1649	1649	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1650		-
1651	1651	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1652		-
1653	1653	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1654		-
1655	1655	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1656		-
1657	1657	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1658	1658
1659		-(% style="display:none" %) (%%)
1660		-
1661		-
1662	1662	= 10.  Packing Info =
1663	1663
1664	1664
...	...	@@ -1665,37 +1665,22 @@
1665	1665	(% style="color:#037691" %)**Package Includes**:
1666	1666
1667	1667	* TrackerD LoRaWAN GPS/BLE Tracker x 1
1668		-
1669	1669	* USB recharge & program cable x 1
1670	1670
1671	1671	(% style="color:#037691" %)**Dimensions and Weight**:
1672	1672
1673	1673	* Device Size: 85 x 48 x 15 mm
1674		-
1675	1675	* Weight: 50g
1676	1676
1677		-(% style="display:none" %) (%%)
1678		-
1679		-
1680	1680	= 11. Support =
1681	1681
1682	1682
1683	1683	* 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.
1684		-
1685	1685	* 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]].
1686	1686
1687		-(% style="display:none" %)
1688		-
1689		-
1690		-
1691	1691	= 12.  Reference =
1692	1692
1693	1693
1694	1694	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1695		-
1696	1696	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1697		-
1698	1698	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1699		-
1700		-
1701		-)))

image-20221128102938-1.png

Author

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

Size

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

Content

image-20221128103040-2.png

Author

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

Size

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

Content

image-20221128110503-3.png

Author

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

Size

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

Content

image-20221128111443-4.png

Author

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

Size

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

Content

image-20221128111850-5.png

Author

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

Size

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

Content

image-20221128111951-6.png

Author

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

Size

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

Content

image-20221128112035-7.png

Author

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

Size

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

Content

image-20221207120501-1.png

Author

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

Size

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

Content

image-20221207120524-2.png

Author

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

Size

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

Content

image-20221207120530-3.png

Author

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

Size

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

Content

image-20221207120536-4.png

Author

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

Size

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

Content

image-20221207120601-5.png

Author

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

Size

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

Content

image-20221207133836-6.png

Author

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

Size

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

Content

image-20221207133911-7.png

Author

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

Size

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

Content

image-20221207134028-8.png

Author

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

Size

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

Content

image-20221213100007-1.png

Author

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

Size

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

Content

image-20221213100626-2.png

Author

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

Size

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

Content

image-20221213100808-3.png

Author

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

Size

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

Content

image-20221213101040-4.png

Author

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

Size

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

Content

image-20221213102311-5.png

Author

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

Size

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

Content

image-20221213102334-6.png

Author

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

Size

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

Content

image-20221213102718-7.png

Author

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

Size

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

Content

image-20221213110952-8.png

Author

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

Size

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

Content

image-20230213110119-1.png

Author

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

Size

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

Content

image-20230213110214-2.png

Author

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

Size

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

Content

image-20230213110506-3.png

Author

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

Size

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

Content

image-20230302145315-1.png

Author

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

Size

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

Content

image-20230307135914-1.png

Author

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

Size

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

Content

image-20230307135932-2.png

Author

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

Size

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

Content

image-20230308115430-1.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-2.4 MB

Content

image-20230308115616-2.png

Author

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

Size

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

Content

image-20230308115701-3.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-2.4 MB

Content

image-20230426085815-1.png

Author

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

Size

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

Content