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,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="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
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
	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
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,9 +258,9 @@
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" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
263		-|(% 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
264	264
265	265	(% style="color:blue" %)** SMOD：**
266	266
...	...	@@ -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
...	...	@@ -308,27 +308,24 @@
308	308	)))|(% style="width:30px" %)(((
309	309	2
310	310	)))
311		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	308	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
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" 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
429		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	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" %)(((
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		-|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
	448	+|=**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,11 +465,11 @@
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		-|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
	466	+|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
473	473	iBeacon MAJOR
474	474	)))|(% style="width:63px" %)(((
475	475	iBeacon MINOR
...	...	@@ -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,44 +492,22 @@
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		-=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
498	498
499		-
500		-The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
501		-
502		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
503		-|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
504		-|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
505		-
506		- [[image:image-20230302145315-1.png]]
507		-
508		-**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
509		-
510		-**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
511		-
512		-**mod** = bytes[2] & 0xC0;
513		-
514		-**Lon**=(bytes[2] & 0x20)
515		-
516		-
517		-=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
518		-
519		-
520	520	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.
521	521
522	522
523		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
524		-|(% style="width:65px" %)(((
	495	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	496	+|=(% scope="row" style="width: 60px;" %)(((
525	525	**Size(bytes)**
526		-)))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
527		-|(% 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" %)(((
528	528	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
529		-)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
	501	+)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
530	530
531	531	(% class="wikigeneratedid" %)
532		-[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	504	+[[image:1667288597595-714.png||height="212" width="1151"]]
533	533
534	534
535	535	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -536,27 +536,27 @@
536	536	* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
537	537	* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
538	538
539		-(% style="display:none" %) (%%)
	511	+=== 2.4.7  Add Payload format in TTN V3 ===
540	540
541		-=== 2.4.8  Add Payload format in TTN V3 ===
542	542
543		-
544	544	In TTN V3, user can add a custom payload so it shows friendly.
545	545
546	546	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
547	547
548	548
549		-[[image:1664502649601-895.png||_mstalt="296985"]]
	519	+[[image:1664502649601-895.png]]
550	550
551	551
	522	+Add the decoder from this link:
552	552
553		-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]]
554	554
555	555	Save the change the uplink message will be parsed. As below:
556	556
557		-[[image:1664502676891-606.png||_mstalt="296673"]]
	528	+[[image:1664502676891-606.png]]
558	558
559	559
	531	+
560	560	== 2.5 Integrate with Datacake ==
561	561
562	562
...	...	@@ -565,9 +565,10 @@
565	565	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]]
566	566
567	567
568		-[[image:1664502695771-538.png||_mstalt="297349"]]
	540	+[[image:1664502695771-538.png]]
569	569
570	570
	543	+
571	571	== 2.6 Integrate with Tago ==
572	572
573	573
...	...	@@ -576,70 +576,31 @@
576	576	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]]
577	577
578	578
579		-[[image:1664502715371-321.png||_mstalt="292162"]]
	552	+[[image:1664502715371-321.png]]
580	580
581	581
582		-== 2.7  Integrate with Node-red ==
583	583
	556	+== 2.7  Datalog Feature ==
584	584
585		-~1. Install node-red, please refer to the installation method in the link:
586	586
587		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
588		-
589		-
590		-2. Import the created flow template, please refer to the import method in the link:
591		-
592		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
593		-
594		-
595		-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]]
596		-
597		-(% 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.**
598		-
599		-[[image:image-20230307135914-1.png||height="527" width="1045"]]
600		-
601		-
602		-[[image:image-20230307135932-2.png||height="527" width="1044"]]
603		-
604		-
605		-3. Display the map
606		- Enter the link to the map:
607		-
608		- Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
609		-
610		-**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
611		-
612		-
613		- Hit all input in input stream
614		-
615		- [[image:image-20230308115616-2.png||height="563" width="1070"]]
616		-
617		-
618		- View map again
619		-
620		-[[image:image-20230308115701-3.png||height="571" width="1085"]]
621		-
622		-
623		-== 2.8  Datalog Feature ==
624		-
625		-
626	626	total 273 entries,by default,
627	627
628		-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.
629	629
630	630	Example use case.
631	631
632		-[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	565	+[[image:image-20221009234703-2.png||height="328" width="899"]]
633	633
634	634
635		-[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	568	+[[image:image-20221009234629-1.png||height="390" width="577"]]
636	636
637	637
638		-== 2.9  Alarm Mode ==
639	639
	572	+== 2.8 Alarm Mode ==
640	640
	574	+
641	641	(((
642		-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.
643	643	)))
644	644
645	645
...	...	@@ -649,7 +649,7 @@
649	649
650	650
651	651	(((
652		-**Two ways to exit alarm mode:**
	586	+Two ways to exit alarm mode:
653	653	)))
654	654
655	655	* Server sends a downlink command to exit.
...	...	@@ -660,24 +660,19 @@
660	660	)))
661	661
662	662
663		-== 2.10  Transport Mode ==
664	664
	598	+== 2.9 Transport Mode ==
665	665
666		-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"]]**.
667	667
668		-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.
669	669
670		-* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
671		-* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
672		-* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
673	673
674		-(% style="display:none" %) (%%)
675	675
676		-== 2.11  LED Status ==
	605	+== 2.10 LED Status ==
677	677
678	678
679		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
680		-|=(% 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**
681	681	|(% 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
682	682	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
683	683	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
...	...	@@ -690,14 +690,12 @@
690	690	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
691	691	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
692	692
693		-(% style="display:none" %) (%%)
	622	+== 2.11 Button Function ==
694	694
695		-== 2.12  Button Function ==
696	696
697		-
698	698	(% style="color:blue" %)**RESET button:**
699	699
700		-[[image:1664502835802-546.png||_mstalt="295061"]]
	627	+[[image:1664502835802-546.png]]
701	701
702	702	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
703	703
...	...	@@ -704,21 +704,18 @@
704	704
705	705	(% style="color:red" %)**RED button:**
706	706
707		-[[image:image-20230213110506-3.png]](% style="display:none" %)
	634	+[[image:1664502854406-763.png]]
708	708
709		-(% style="display:none" %) (%%)
710	710
711		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
712		-|=(% 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**
713	713	|(% 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"]]
714	714	|(% 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
715	715	|(% 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.
716	716
717		-(% style="display:none" %) (%%)
	643	+== 2.12 USB Port Function ==
718	718
719		-== 2.13  USB Port Function ==
720	720
721		-
722	722	The USB interface of TrackerD has below functions:
723	723
724	724	* Power on the device
...	...	@@ -726,18 +726,6 @@
726	726	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
727	727	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
728	728
729		-(% style="display:none" %) (%%)
730		-
731		-== 2.14  Sleep Mode ==
732		-
733		-
734		-(% 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.
735		-
736		-In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
737		-
738		-Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
739		-
740		-
741	741	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
742	742
743	743
...	...	@@ -746,6 +746,7 @@
746	746	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
747	747
748	748
	661	+
749	749	== 3.1 Access AT Command ==
750	750
751	751
...	...	@@ -752,24 +752,25 @@
752	752	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.
753	753
754	754
755		-[[image:1664502999401-486.png||_mstalt="296985"]]
	668	+[[image:1664502999401-486.png]]
756	756
757	757
758	758	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:
759	759
760	760
761		-[[image:1664503022490-662.png||_mstalt="293332"]]
	674	+[[image:1664503022490-662.png]]
762	762
763	763
764		-[[image:1664503035713-500.png||_mstalt="291096"]]
	677	+[[image:1664503035713-500.png]]
765	765
766	766
767		-[[image:1664503047675-651.png||_mstalt="295386"]]
	680	+[[image:1664503047675-651.png]]
768	768
769		-(% style="display:none" %) (%%)
770	770
	683	+
771	771	== 3.2 Command Set ==
772	772
	686	+
773	773	=== 3.2.1 Set Transmit Interval ===
774	774
775	775
...	...	@@ -787,6 +787,7 @@
787	787	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
788	788
789	789
	704	+
790	790	=== 3.2.2 Set Alarm Packet transmission interval ===
791	791
792	792
...	...	@@ -804,6 +804,7 @@
804	804	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
805	805
806	806
	722	+
807	807	=== 3.2.3 Set Transport Mode Packet transmission interval ===
808	808
809	809
...	...	@@ -821,6 +821,7 @@
821	821	(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
822	822
823	823
	740	+
824	824	=== 3.2.4 Exit Alarm ===
825	825
826	826
...	...	@@ -833,9 +833,10 @@
833	833	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
834	834
835	835
836		-=== 3.2.5 Disable/Enable LED flash and buzzer ===
837	837
	754	+=== 3.2.5 Disable/Enable LED flash ===
838	838
	756	+
839	839	Disable/Enable LED for position, downlink and uplink
840	840
841	841	* (% style="color:blue" %)**AT Command:**
...	...	@@ -850,6 +850,7 @@
850	850	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
851	851
852	852
	771	+
853	853	=== 3.2.6 Disable/Enable Transport Mode ===
854	854
855	855
...	...	@@ -867,6 +867,7 @@
867	867	(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
868	868
869	869
	789	+
870	870	=== 3.2.7 Set Positioning Mode ===
871	871
872	872
...	...	@@ -893,9 +893,9 @@
893	893
894	894	(% style="color:#037691" %)**cc:   **
895	895
896		-* (% _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
897	897
898		-* (% _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(%%))
899	899
900	900	(% style="color:blue" %)**Example:**
901	901
...	...	@@ -913,6 +913,7 @@
913	913	(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
914	914
915	915
	836	+
916	916	=== 3.2.8 Set MAX GPS position time ===
917	917
918	918
...	...	@@ -919,7 +919,7 @@
919	919	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.
920	920
921	921
922		-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.
923	923
924	924
925	925	* (% style="color:blue" %)**AT Command:**
...	...	@@ -934,6 +934,7 @@
934	934	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
935	935
936	936
	858	+
937	937	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
938	938
939	939
...	...	@@ -957,8 +957,8 @@
957	957	(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
958	958
959	959
960		-=== 3.2.10 Disable/Enable the confirmation mode ===
961	961
	883	+Disable/Enable the confirmation mode
962	962
963	963	* (% style="color:blue" %)**AT Command:**
964	964
...	...	@@ -977,9 +977,10 @@
977	977	(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
978	978
979	979
980		-=== 3.2.11  Auto Send None-ACK messages ===
981	981
	903	+=== 3.2.10  Auto Send None-ACK messages ===
982	982
	905	+
983	983	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.
984	984
985	985
...	...	@@ -995,12 +995,13 @@
995	995
996	996	* (% style="color:blue" %)**Downlink Command: 0x34**
997	997
998		-Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
	921	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
999	999
1000	1000
1001		-=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
1002	1002
	925	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
1003	1003
	927	+
1004	1004	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.
1005	1005
1006	1006	(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
...	...	@@ -1007,18 +1007,19 @@
1007	1007
1008	1008	(% style="color:blue" %)**AT Command:**
1009	1009
1010		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	934	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1011	1011
1012		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	936	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1013	1013
1014	1014	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1015	1015
1016		-Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
	940	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1017	1017
1018	1018
1019		-=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1020	1020
	944	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1021	1021
	946	+
1022	1022	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.
1023	1023
1024	1024	(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
...	...	@@ -1025,158 +1025,44 @@
1025	1025
1026	1026	(% style="color:blue" %)**AT Command:**
1027	1027
1028		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	953	+ (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1029	1029
1030		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	955	+ (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1031	1031
1032	1032	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1033	1033
1034		-Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
	959	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1035	1035
1036	1036
1037		-=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
1038	1038
	963	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1039	1039
	965	+
1040	1040	Users can use this feature to enable/disable Information printing.
1041	1041
1042	1042	(% style="color:blue" %)**AT Command:**
1043	1043
1044		-(% 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)
1045	1045	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1046	1046
1047	1047
1048		-=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1049	1049
	975	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1050	1050
	977	+
1051	1051	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
1052	1052
1053	1053	(% style="color:blue" %)**AT Command:**
1054	1054
1055		-(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
	982	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1056	1056
1057	1057
1058	1058	(% style="color:blue" %)**Downlink Payload:0X24**
1059	1059
1060		-Example: 0x24 01  ~/~/ Same as AT+CHE=1
	987	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
1061	1061
1062	1062
1063		-=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1064	1064
1065		-
1066		-User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1067		-
1068		-(% style="color:blue" %)**AT Command:**
1069		-
1070		-(% style="color:#037691" %)**AT+PT=xx**
1071		-
1072		- Example:
1073		-
1074		- AT+PT=14    ~-~->    Set to detect car motion.
1075		-
1076		- AT+PT=41  ~-~->    set to detect walk motion.
1077		-
1078		-
1079		-(% style="color:blue" %)**Downlink Payload:0xB4**
1080		-
1081		-0xB4 14          ~/~/  Same as AT+PT=14
1082		-
1083		-
1084		-=== 3.2.17  Set AT command window time（Since firmware 1.4.5） ===
1085		-
1086		-
1087		-AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1088		-
1089		-(% style="color:blue" %)**AT Command:**
1090		-
1091		-(% style="color:#037691" %)**AT+ATST=XX**
1092		-
1093		- Example:
1094		-
1095		- AT+ATST=15    ~-~-> Set the time to 15 seconds
1096		-
1097		-(% style="color:blue" %)**Downlink Payload:0XB5**
1098		-
1099		-0xB5 0F          ~/~/  Same as AT+ATST=15
1100		-
1101		-
1102		-=== 3.2.18  Set the stepmeter mode（Since firmware 1.4.5） ===
1103		-
1104		-
1105		-After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1106		-
1107		-(% style="color:blue" %)**AT Command:**
1108		-
1109		-(% style="color:#037691" %)**AT+PM=xx**
1110		-
1111		- Example:
1112		-
1113		- AT+PM=1    ~-~->  Turn on step counting mode
1114		-
1115		-AT+PM=0    ~-~->  Turn OFF step counting mode
1116		-
1117		-(% style="color:blue" %)**Downlink Payload:0XB6**
1118		-
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		-
1125		-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.
1126		-
1127		-(% style="color:blue" %)**AT Command:**
1128		-
1129		-(% style="color:#037691" %)**AT+FD=xx**
1130		-
1131		- Example:
1132		-
1133		- AT+FD=1    ~-~->  Turn on the Fall detection
1134		-
1135		-AT+FD=0    ~-~->  Turn OFF the Fall detection
1136		-
1137		-(% style="color:blue" %)**Downlink Payload:0XB7**
1138		-
1139		-0xB7 01          ~/~/  Same as AT+FD=1
1140		-
1141		-
1142		-=== 3.2.20 Disable/Enable buzzer（Since firmware 1.4.6） ===
1143		-
1144		-
1145		-Disable/Enable buzzer for Alarm, downlink and uplink
1146		-
1147		-(% style="color:blue" %)**AT Command:**
1148		-
1149		-(% style="color:#037691" %)**AT+BEEP=XX**
1150		-
1151		- Example:
1152		-
1153		-AT+BEEP=1 ~-~-> Turn on the buzzer
1154		-
1155		-AT+BEEP=0 ~-~-> Turn OFF the buzzer
1156		-
1157		-(% style="color:blue" %)**Downlink Payload:0XB9**
1158		-
1159		-0xB9 01 ~/~/ Same as AT+BEEP=1
1160		-
1161		-
1162		-=== 3.2.21 Set long press time（Since firmware 1.4.6） ===
1163		-
1164		-
1165		-When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
1166		-
1167		-(% style="color:blue" %)**AT Command:**
1168		-
1169		-(% style="color:#037691" %)**AT+EAT=XX**
1170		-
1171		- Example:
1172		-
1173		-AT+EAT=2 ~-~-> Set the long press time to 2s
1174		-
1175		-(% style="color:blue" %)**Downlink Payload:0XBA**
1176		-
1177		-0xBA 02 ~/~/ Same as AT+EAT=2
1178		-
1179		-
1180	1180	= 4. Setting for Different Scenarios =
1181	1181
1182	1182
...	...	@@ -1183,6 +1183,7 @@
1183	1183
1184	1184	= 5. Upload Firmware =
1185	1185
	997	+
1186	1186	== 5.1 Firmware Change Log ==
1187	1187
1188	1188
...	...	@@ -1189,6 +1189,7 @@
1189	1189	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
1190	1190
1191	1191
	1004	+
1192	1192	== 5.2 How to upgrade firmware ==
1193	1193
1194	1194
...	...	@@ -1209,10 +1209,10 @@
1209	1209	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1210	1210
1211	1211
1212		-[[image:1664503563660-578.png||_mstalt="296777"]]
	1025	+[[image:1664503563660-578.png]]
1213	1213
1214	1214
1215		-[[image:1664503574618-659.png||_mstalt="297986"]]
	1028	+[[image:1664503574618-659.png]]
1216	1216
1217	1217
1218	1218
...	...	@@ -1221,7 +1221,7 @@
1221	1221	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1222	1222
1223	1223
1224		-**Users need to use below files:**
	1037	+Users need to use below files:
1225	1225
1226	1226	boot_app0.bin @0e000
1227	1227
...	...	@@ -1228,19 +1228,22 @@
1228	1228	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1229	1229
1230	1230
1231		-[[image:image-20221207120501-1.png]]
	1044	+[[image:image-20221118105220-2.png]]
1232	1232
1233	1233
1234	1234
1235	1235	After upgrade finish, it will show finish as below:
1236	1236
1237		-[[image:image-20221207133911-7.png]]
	1050	+[[image:image-20221118105402-4.png]]
1238	1238
1239	1239
	1053	+
1240	1240	= 6. Developer Guide =
1241	1241
	1056	+
1242	1242	== 6.1 Compile Source Code ==
1243	1243
	1059	+
1244	1244	=== 6.1.1 Set up ARDUINO compile environment ===
1245	1245
1246	1246
...	...	@@ -1249,81 +1249,24 @@
1249	1249	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]]
1250	1250
1251	1251
1252		-[[image:1664503635019-941.png||_mstalt="294658"]]
	1068	+[[image:1664503635019-941.png]]
1253	1253
1254	1254
1255	1255
1256	1256	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1257	1257
1258		-[[image:1664503715811-892.png||_mstalt="295698"]]
	1074	+[[image:1664503715811-892.png]]
1259	1259
1260	1260
1261		-=== 6.1.2  Build the development environment ===
1262		-
1263		-
1264		-**~1. Download and install arduino IDE**
1265		-
1266		-[[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]]
1267		-
1268		-
1269		-**2. Download the ESP32 development package in the arduino IDE**
1270		-
1271		-[[image:image-20221213100007-1.png]]
1272		-
1273		-
1274		-Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1275		-
1276		-[[image:image-20221213100626-2.png]]
1277		-
1278		-
1279		-Restart the IDE after the addition is complete, then:
1280		-
1281		-[[image:image-20221213100808-3.png||height="679" width="649"]]
1282		-
1283		-
1284		-[[image:image-20221213101040-4.png]]
1285		-
1286		-
1287		-(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1288		-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)**
1289		-
1290		-
1291		-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:
1292		-
1293		-(% style="color:blue" %)**Methods as below:**
1294		-
1295		-~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1296		-
1297		-2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1298		-
1299	1299	(% 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.
1300	1300
1301		-[[image:image-20221213102311-5.png||height="582" width="711"]]
	1079	+[[image:image-20221024105643-1.png]]
1302	1302
1303		-
1304		-**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1305		-
1306		-[[image:image-20221213102334-6.png]]
1307		-
1308		-(% style="color:red" %)**Note: This step requires a python environment**
1309		-
1310		-
1311		-Either way, in the end:
1312		-
1313		-The final effect is to open the arduino and you can see the esp32
1314		-
1315		-[[image:image-20221213110952-8.png||height="866" width="711"]]
1316		-
1317		-
1318		-
1319		-[[image:image-20221024105643-1.png||_mstalt="428129"]]
1320		-
1321	1321	**~ Figure1**
1322	1322
1323	1323
	1084	+[[image:image-20221024105643-2.png]]
1324	1324
1325		-[[image:image-20221024105643-2.png||_mstalt="428493"]]
1326		-
1327	1327	**Figure2**
1328	1328
1329	1329
...	...	@@ -1332,31 +1332,34 @@
1332	1332	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1333	1333
1334	1334
1335		-[[image:1664503752288-974.png||_mstalt="298194"]]
	1094	+[[image:1664503752288-974.png]]
1336	1336
1337	1337
	1097	+
1338	1338	== 6.2 Source Code ==
1339	1339
1340	1340
1341	1341	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1342	1342
1343		-[[image:1664503794261-827.png||_mstalt="296387"]]
	1103	+[[image:1664503794261-827.png]]
1344	1344
1345	1345
1346	1346
1347	1347	* (% style="color:blue" %)**Click to upload**
1348	1348
1349		-[[image:1664503808294-336.png||_mstalt="295711"]]
	1109	+[[image:1664503808294-336.png]]
1350	1350
1351	1351
1352	1352
1353	1353	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1354	1354
1355		-[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
	1115	+[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1356	1356
1357	1357
	1118	+
1358	1358	= 7.  FAQ =
1359	1359
	1121	+
1360	1360	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1361	1361
1362	1362
...	...	@@ -1363,15 +1363,16 @@
1363	1363	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1364	1364
1365	1365
	1128	+
1366	1366	== 7.2 What is the pin mapping for the USB program cable? ==
1367	1367
1368	1368
1369		-[[image:1664499635206-262.png||_mstalt="295360"]]
	1132	+[[image:1664499635206-262.png]]
1370	1370
1371	1371
1372	1372
1373		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1374		-|=(% 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**
	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**
1375	1375	|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1376	1376	|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1377	1377	|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
...	...	@@ -1381,11 +1381,9 @@
1381	1381	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1382	1382	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1383	1383
1384		-(% style="display:none" %) (%%)
1385		-
1386		-
1387	1387	== 7.3 Notes on using different serial port tools for TrackerD ==
1388	1388
	1149	+
1389	1389	=== 7.3.1  Serial port utility ===
1390	1390
1391	1391
...	...	@@ -1393,16 +1393,18 @@
1393	1393
1394	1394	Need to adjust the data stream to RTS/CTS on physical restart.
1395	1395
	1157	+
1396	1396	(% class="wikigeneratedid" %)
1397		-[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1159	+[[image:image-20221102140621-1.png]]
1398	1398
1399	1399
1400		-
1401	1401	When using AT commands, the data flow needs to be adjusted to XON/XOFF
1402	1402
1403		-[[image:image-20221102140638-2.png||_mstalt="428727"]]
1404	1404
	1165	+[[image:image-20221102140638-2.png]]
1405	1405
	1167	+
	1168	+
1406	1406	=== 7.3.2  SecureCRT ===
1407	1407
1408	1408
...	...	@@ -1409,22 +1409,23 @@
1409	1409	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.
1410	1410
1411	1411
1412		-[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1175	+[[image:image-20221102140704-3.png]]
1413	1413
1414	1414
1415		-[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1178	+[[image:image-20221102140712-4.png]]
1416	1416
1417	1417
	1181	+
1418	1418	=== 7.3.3  PUTTY ===
1419	1419
1420	1420
1421		-[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1185	+[[image:image-20221102140748-5.png]]
1422	1422
1423	1423
1424	1424	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.
1425	1425
1426	1426
1427		-[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1191	+[[image:image-20221102140801-6.png]]
1428	1428
1429	1429
1430	1430	== 7.4 How to modify source code to compile different frequency band bin file? ==
...	...	@@ -1436,58 +1436,38 @@
1436	1436	See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1437	1437	)))
1438	1438
1439		-**~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.
1440	1440
	1205	+[[image:image-20221116111844-1.png||height="227" width="782"]]
1441	1441
1442		-[[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).
1443	1443
	1209	+[[image:image-20221116111844-2.png||height="262" width="781"]]
1444	1444
	1211	+3.Compile the AS923_JP band, please refer to the intention shown
1445	1445
1446		-**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"]]
1447	1447
	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.
1448	1448
1449		-[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1217	+[[image:image-20221116111844-4.png||height="641" width="739"]]
1450	1450
	1219	+[[image:image-20221116111844-5.png||height="551" width="708"]]
1451	1451
1452	1452
1453		-**3. Compile the AS923_JP band, please refer to the intention shown**
1454	1454
1455		-
1456		-[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1457		-
1458		-
1459		-
1460		-**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.**
1461		-
1462		-
1463		-[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1464		-
1465		-
1466		-[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1467		-
1468		-
1469		-== 7.5 Are there example python example for BLE Indoor Positioning? ==
1470		-
1471		-
1472		-[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1473		-
1474		-
1475		-== 7.6 Can alert mode and transport mode be used together? ==
1476		-
1477		-
1478		-Yes, you can also press the panic button to sound the alarm if set to transport mode
1479		-
1480		-
1481	1481	= 8  Trouble Shooting =
1482	1482
	1225	+
1483	1483	== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1484	1484
1485	1485
1486	1486	(((
1487		-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
1488	1488	)))
1489	1489
1490	1490
	1234	+
1491	1491	== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1492	1492
1493	1493
...	...	@@ -1496,152 +1496,85 @@
1496	1496	)))
1497	1497
1498	1498
	1243	+
1499	1499	== 8.3  Problem after Upgrading Firmware ==
1500	1500
1501		-=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
	1246	+=== 8.3.1 Continue Restart after upgrading ===
1502	1502
1503	1503
1504		-**Error Output**
1505		-
1506		-
1507		-[[image:image-20221122100004-4.png||_mstalt="424606"]]
1508		-
1509		-
1510	1510	(((
1511		-Some partition is missed during upgrade, please upgrade below four files as example:
1512		-
1513		-[[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
1514	1514	)))
1515	1515
1516	1516
1517		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1254	+[[image:image-20221118105249-3.png]]
1518	1518
1519	1519
	1257	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1258	+
1520	1520	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
1521	1521
1522	1522
1523		-=== 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 ====
1524	1524
	1264	+[[image:image-20221122100004-1.png||height="497" width="534"]]
1525	1525
1526		-Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
	1266	+ Figure 1
1527	1527
	1268	+ [[image:image-20221122100004-2.png||height="619" width="389"]]
1528	1528
1529		-[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
	1270	+ Figure 2
1530	1530
	1272	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
1531	1531
1532		-User need to upgrade again with below four files to solve this issue.
	1274	+[[image:image-20221122100004-3.png]]
1533	1533
1534		- [[image:image-20221207120530-3.png]]
	1276	+Please AT+FDR, and then enter the following instructions by the information on the label
1535	1535
1536		- **Figure 2**
	1278	+AT+DEUI=70B3D57ED0053981
1537	1537
1538		-
1539		-=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1540		-
1541		-
1542		-User might erase the entire flash include keys and default settings which cause this issue.
1543		-
1544		-After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1545		-
1546		-
1547		-[[image:image-20221122100004-3.png||_mstalt="424242"]]
1548		-
1549		-
1550		-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.
1551		-
1552		-After AT+FDR. please set
1553		-
1554		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1555		-
1556		-* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1557		-
1558		-**Example:**
1559		-
1560		-AT+PDOP=7.00
1561		-
1562		-AT+FTIME=180
1563		-
1564		-AT+DEUI=70B3D57ED0053981
1565		-
1566	1566	AT+APPEUI=D23345667BCBCCAF
1567	1567
1568	1568	AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1569	1569
1570		-AT+DADDR=260b4dce    ( no need for OTAA)
	1284	+AT+DADDR=260b4dce
1571	1571
1572		-AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
	1286	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1573	1573
1574		-AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
	1288	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1575	1575
1576	1576
1577		-== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1578	1578
	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 ====
1579	1579
1580		-Please download version 1.4.2 again
	1294	+[[image:image-20221122100004-4.png]]
1581	1581
	1296	+== ==
1582	1582
1583		-== 8.5  How to deal with unsuccessful GPS positioning? ==
	1298	+== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1584	1584
	1300	+Please download version 1.4.2 again
1585	1585
1586		-1） Make Sure the device is in Open Area where can see the sky.
1587	1587
	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.
1588	1588	2)  Set PDOP to a higher value.
1589	1589
1590		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1309	+ AT+PDOP=2(can be positioned precisely.）
1591	1591
1592		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1311	+ AT+PDOP=7(Quickly locate in open spaces）
1593	1593
1594		-* (% _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）
1595	1595
1596	1596	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	+)))
1597	1597
1598	1598
1599		-== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1319	+== ==
1600	1600
1601	1601
1602		-When upgrading, use the erase button to upgrade
1603		-
1604		-[[image:image-20221207120536-4.png]]
1605		-
1606		-
1607		-The parameters are displayed abnormally and cannot be fixed using AT+FDR
1608		-
1609		-[[image:image-20221128103040-2.png||height="431" width="525"]]
1610		-
1611		-
1612		-Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1613		-
1614		-[[image:image-20221207134028-8.png]]
1615		-
1616		-
1617		-Reboot information after upgrade
1618		-
1619		-[[image:image-20221128111443-4.png||height="432" width="546"]]
1620		-
1621		-
1622		-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
1623		-
1624		-[[image:image-20221128111850-5.png]]
1625		-
1626		-
1627		-After the parameters return to normal, upgrade to the version you need again
1628		-
1629		-[[image:image-20221207120601-5.png]]
1630		-
1631		-
1632		-At this point, the parameters return to normal after running AT+FDR again
1633		-
1634		-[[image:image-20221128112035-7.png]]
1635		-
1636		-
1637		-== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1638		-
1639		-
1640		-~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1641		-
1642		-2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1643		-
1644		-
1645	1645	= 9.  Order Info =
1646	1646
1647	1647
...	...	@@ -1650,21 +1650,13 @@
1650	1650	(% style="color:blue" %)**XXX**(%%): The default frequency band
1651	1651
1652	1652	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1653		-
1654	1654	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1655		-
1656	1656	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1657		-
1658	1658	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1659		-
1660	1660	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1661		-
1662	1662	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1663		-
1664	1664	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1665	1665
1666		-(% style="display:none" %) (%%)
1667		-
1668	1668	= 10.  Packing Info =
1669	1669
1670	1670
...	...	@@ -1671,35 +1671,22 @@
1671	1671	(% style="color:#037691" %)**Package Includes**:
1672	1672
1673	1673	* TrackerD LoRaWAN GPS/BLE Tracker x 1
1674		-
1675	1675	* USB recharge & program cable x 1
1676	1676
1677	1677	(% style="color:#037691" %)**Dimensions and Weight**:
1678	1678
1679	1679	* Device Size: 85 x 48 x 15 mm
1680		-
1681	1681	* Weight: 50g
1682	1682
1683		-(% style="display:none" %) (%%)
1684		-
1685	1685	= 11. Support =
1686	1686
1687	1687
1688	1688	* 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.
1689		-
1690	1690	* 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]].
1691	1691
1692		-(% style="display:none" %)
1693		-
1694		-
1695	1695	= 12.  Reference =
1696	1696
1697	1697
1698	1698	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1699		-
1700	1700	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1701		-
1702	1702	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1703		-
1704		-
1705		-)))

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