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

Summary

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

Author

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

Content

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

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