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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 34 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
  • image-20231023103116-1.png

Details

Page properties

Content

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

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

image-20231023103116-1.png

Author

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

Size

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

Content