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

Summary

• Page properties (2 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

Author

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

Content

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

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