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

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 34 added, 0 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.Edwin
	1	+XWiki.Xiaoling

Content

...	...	@@ -12,6 +12,7 @@
12	12
13	13
14	14
	15	+
15	15	= 1.  Introduction =
16	16
17	17	== 1.1  What is TrackerD ==
...	...	@@ -31,15 +31,12 @@
31	31	(((
32	32	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.
33	33	)))
34		-)))
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.
38		-
39		-
40	40	)))
41	41
42		-[[image:1664499921684-770.png||_mstalt="298194"]]
	40	+[[image:image-20230213110119-1.png||height="382" width="834"]]
43	43
44	44
45	45	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
...	...	@@ -95,6 +95,10 @@
95	95	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
96	96	* Tracking: max: 38mA
97	97
	96	+(% style="display:none" %)
	97	+
	98	+
	99	+
98	98	== 1.3  Features ==
99	99
100	100
...	...	@@ -113,6 +113,10 @@
113	113	* Tri-color LED, Alarm button
114	114	* Datalog
115	115
	118	+(% style="display:none" %)
	119	+
	120	+
	121	+
116	116	== 1.4  Applications ==
117	117
118	118
...	...	@@ -119,6 +119,10 @@
119	119	* Logistics and Supply Chain Management
120	120	* Human tracking
121	121
	128	+(% style="display:none" %)
	129	+
	130	+
	131	+
122	122	= 2.  Use TrackerD =
123	123
124	124	== 2.1 How it works? ==
...	...	@@ -133,10 +133,9 @@
133	133	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.
134	134
135	135
136		-[[image:1664501652064-326.png||_mstalt="293306"]]
	146	+[[image:image-20230213110214-2.png||height="388" width="847"]]
137	137
138	138
139		-
140	140	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:
141	141
142	142
...	...	@@ -145,7 +145,7 @@
145	145	Each TrackerD is shipped with a sticker with the default device EUI as below:
146	146
147	147
148		-[[image:1664501677253-891.png||_mstalt="296569"]]
	157	+[[image:image-20230426085815-1.png||height="259" width="558"]]
149	149
150	150
151	151	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -153,11 +153,9 @@
153	153
154	154	**__Add APP EUI in the application:__**
155	155
156		-
157	157	[[image:1664501711466-918.png||_mstalt="295828"]]
158	158
159	159
160		-
161	161	[[image:1664501721248-725.png||_mstalt="294450"]]
162	162
163	163
...	...	@@ -164,7 +164,6 @@
164	164	[[image:1664501734705-405.png||_mstalt="293306"]]
165	165
166	166
167		-
168	168	**__Add APP KEY and DEV EUI:__**
169	169
170	170
...	...	@@ -171,7 +171,6 @@
171	171	[[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"]]
172	172
173	173
174		-
175	175	(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
176	176
177	177	(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
...	...	@@ -199,15 +199,14 @@
199	199	=== 2.4.1 Uplink FPORT~=5, Device Status ===
200	200
201	201
202		-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.
	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.
203	203
204		-Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
	209	+Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
205	205
	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
206	206
207		-(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
208		-|=(% 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
209		-|=(% 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
210		-
211	211	[[image:1665301570342-765.png||_mstalt="294580"]]
212	212
213	213
...	...	@@ -219,31 +219,30 @@
219	219
220	220	(% style="color:#037691" %)**Frequency Band**:
221	221
222		-*0x01: EU868
	226	+0x01: EU868
223	223
224		-*0x02: US915
	228	+0x02: US915
225	225
226		-*0x03: IN865
	230	+0x03: IN865
227	227
228		-*0x04: AU915
	232	+0x04: AU915
229	229
230		-*0x05: KZ865
	234	+0x05: KZ865
231	231
232		-*0x06: RU864
	236	+0x06: RU864
233	233
234		-*0x07: AS923
	238	+0x07: AS923
235	235
236		-*0x08: AS923-1
	240	+0x08: AS923-1
237	237
238		-*0x09: AS923-2
	242	+0x09: AS923-2
239	239
240		-*0x0a: AS923-3
	244	+0x0a: AS923-3
241	241
242		-Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
	246	+(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
243	243
244	244	(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
245	245
246		-
247	247	(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
248	248
249	249	Use can also get the Device Status uplink through the downlink command:
...	...	@@ -251,54 +251,50 @@
251	251
252	252	(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
253	253
254		-(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
255		-|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
256		-|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
	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
257	257
258		-(% style="color:blue" %)** SMOD：**
	261	+(% style="color:blue" %)**SMOD：**
259	259
260		-(% style="color:red" %)** 1 :** (%%) GPS ONLY
	263	+(% style="color:red" %)**1 :** (%%) GPS ONLY
261	261
262		-(% style="color:red" %)** 2 :** (%%) BLE ONLY
	265	+(% style="color:red" %)**2 :** (%%) BLE ONLY
263	263
264		-(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
	267	+(% style="color:red" %)**3 :**  (%%) GPS/BLE Hybrid
265	265
266	266
267		-(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
	270	+(% style="color:blue" %)**GPS_MOD: Define how to send GPS payload**
268	268
269		-(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
	272	+(% style="color:red" %)**0 : ** (%%) Enable uploading on-board Temperature and humidity values
270	270
271		-(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
	274	+(% style="color:red" %)**1 :** (%%) Disable uploading on-board Temperature and humidity values
272	272
273	273
274		-(% style="color:blue" %)** BLE_Settings:**
	277	+(% style="color:blue" %)**BLE_Settings:**
275	275
276		-(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
	279	+(% style="color:red" %)**1: ** (%%) BLE Positioning with Strongest iBeacon
277	277
278		-(% _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)(%%)
	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)(%%)
279	279
280	280
281	281	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
282	282
283		-(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
284		-|=(% 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
285		-|=(% 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"]]
	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"]]
286	286
287		-=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
	290	+(% style="display:none" %)
288	288
289	289
290		-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,
	293	+=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
291	291
292	292
293		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
294		-|=(% scope="row" style="width: 60px;" %)(((
295		-**Size(bytes)**
296		-)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
297		-2
298		-)))|(% style="width:30px" %)(((
299		-2
300		-)))
301		-|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	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	+
	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" %)(((
302	302	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
303	303	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
304	304
...	...	@@ -307,15 +307,18 @@
307	307
308	308	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
309	309
310		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
311		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
312		-|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
	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:"]]
313	313
	313	+(% style="display:none" %)
	314	+
	315	+
314	314	==== (% style="color:blue" %)**FLAG:**(%%) ====
315	315
316		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
317		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
318		-|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
	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:"]]
319	319
320	320	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
321	321
...	...	@@ -340,7 +340,6 @@
340	340	[[image:1664502166010-515.png||_mstalt="291395"]]
341	341
342	342
343		-
344	344	==== (% style="color:blue" %)**Alarm:**(%%) ====
345	345
346	346	**Example: ** 0x4B & 0x40 >> 6 = 0x01
...	...	@@ -360,6 +360,8 @@
360	360	* 3.40v ~~ 3.69v:  20% ~~ 40%
361	361	* < 3.39v:  0~~20%
362	362
	364	+(% style="display:none" %) (%%)
	365	+
363	363	==== (% style="color:blue" %)**MOD:**(%%) ====
364	364
365	365	**Example: ** (0x60>>6) & 0x3f =1
...	...	@@ -403,14 +403,12 @@
403	403	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
404	404
405	405
406		-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)
	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)
407	407
408	408
409		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
410		-|=(% scope="row" style="width: 60px;" %)(((
411		-**Size(bytes)**
412		-)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
413		-|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	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" %)(((
414	414	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
415	415	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
416	416
...	...	@@ -421,7 +421,7 @@
421	421	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
422	422
423	423
424		-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.
	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.
425	425
426	426
427	427	(% style="color:red" %)**Note for this mode:**
...	...	@@ -432,11 +432,9 @@
432	432
433	433	The payload is 15 bytes, as below.
434	434
435		-(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
436		-|=(% scope="row" %)(((
437		-**Size(bytes)**
438		-)))|4|4|2|1|1|1|1|1
439		-|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
	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
440	440
441	441	[[image:image-20221009160309-2.png||_mstalt="429312"]]
442	442
...	...	@@ -449,11 +449,9 @@
449	449	User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
450	450
451	451
452		-(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
453		-|=(% scope="row" style="width: 60px;" %)(((
454		-**Size(bytes)**
455		-)))|(% 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
456		-|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
	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" %)(((
457	457	iBeacon MAJOR
458	458	)))|(% style="width:63px" %)(((
459	459	iBeacon MINOR
...	...	@@ -476,44 +476,85 @@
476	476	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
477	477	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
478	478
479		-=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
	476	+(% style="display:none" %) (%%)
480	480
	478	+=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
481	481
482		-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.
483	483
	481	+The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
484	484
485		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
486		-|=(% scope="row" style="width: 60px;" %)(((
	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	+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	+
	503	+(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
	504	+|(% style="width:65px" %)(((
487	487	**Size(bytes)**
488		-)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
489		-|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
	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" %)(((
490	490	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
491		-)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
	509	+)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
492	492
493	493	(% class="wikigeneratedid" %)
494	494	[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
495	495
496		-
497	497	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
498	498	* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
499	499	* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
500	500
501		-=== 2.4.7  Add Payload format in TTN V3 ===
	518	+(% style="display:none" %) (%%)
502	502
	520	+=== 2.4.8  Uplink FPORT~=9, BLE Positioning with Multiple iBeacon（Since firmware 1.4.7） ===
503	503
504		-In TTN V3, user can add a custom payload so it shows friendly.
	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.
505	505
506		-In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
	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.
507	507
	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:]]
508	508
509		-[[image:1664502649601-895.png||_mstalt="296985"]]
	530	+(% class="wikigeneratedid" id="H" %)
	531	+[[image:image-20231023103116-1.png||height="448" width="901"]]
510	510
	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.
511	511
	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
512	512
513		-Add the decoder from this link:
514	514
515		-[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	543	+=== 2.4.9  Add Payload format in TTN V3 ===
516	516
	545	+
	546	+In TTN V3, user can add a custom payload so it shows friendly.
	547	+
	548	+In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
	549	+
	550	+[[image:1664502649601-895.png||_mstalt="296985"]]
	551	+
	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	+
517	517	Save the change the uplink message will be parsed. As below:
518	518
519	519	[[image:1664502676891-606.png||_mstalt="296673"]]
...	...	@@ -526,7 +526,6 @@
526	526
527	527	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]]
528	528
529		-
530	530	[[image:1664502695771-538.png||_mstalt="297349"]]
531	531
532	532
...	...	@@ -537,16 +537,56 @@
537	537
538	538	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]]
539	539
540		-
541	541	[[image:1664502715371-321.png||_mstalt="292162"]]
542	542
543	543
544		-== 2.7  Datalog Feature ==
	580	+== 2.7  Integrate with Node-red ==
545	545
546	546
	583	+~1. Install node-red, please refer to the installation method in the link:
	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	+
	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	+
547	547	total 273 entries,by default,
548	548
549		-User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	626	+User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
550	550
551	551	Example use case.
552	552
...	...	@@ -556,11 +556,11 @@
556	556	[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
557	557
558	558
559		-== 2.8 Alarm Mode ==
	636	+== 2.9  Alarm Mode ==
560	560
561	561
562	562	(((
563		-User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
	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.
564	564	)))
565	565
566	566
...	...	@@ -581,21 +581,25 @@
581	581	)))
582	582
583	583
584		-== 2.9 Transport Mode ==
	661	+== 2.10  Transport Mode ==
585	585
586	586
587		-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.
	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"]]**.
588	588
	666	+When device is set in Transport Mode, it will uplink more frequenctly during moving.
	667	+
589	589	* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
590	590	* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
591		-* **[[PT>>||anchor="H3.2.1SetTransmitInterval"]]** defines the threldhold to detect a motion.
	670	+* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
592	592
	672	+(% style="display:none" %) (%%)
593	593
594		-== 2.10 LED Status ==
595	595
	675	+== 2.11  LED Status ==
596	596
597		-(% border="1.5" style="background-color:#ffffcc; width:500px" %)
598		-|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
	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**
599	599	|(% 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
600	600	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
601	601	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
...	...	@@ -608,9 +608,12 @@
608	608	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
609	609	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
610	610
611		-== 2.11 Button Function ==
	692	+(% style="display:none" %) (%%)
612	612
613	613
	695	+== 2.12  Button Function ==
	696	+
	697	+
614	614	(% style="color:blue" %)**RESET button:**
615	615
616	616	[[image:1664502835802-546.png||_mstalt="295061"]]
...	...	@@ -620,18 +620,22 @@
620	620
621	621	(% style="color:red" %)**RED button:**
622	622
623		-[[image:1664502854406-763.png||_mstalt="295568"]]
	707	+[[image:image-20230213110506-3.png]](% style="display:none" %)
624	624
	709	+(% style="display:none" %) (%%)
625	625
626		-(% border="1" style="background-color:#ffffcc; width:510px" %)
627		-|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
	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**
628	628	|(% 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"]]
629	629	|(% 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
630	630	|(% 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.
631	631
632		-== 2.12 USB Port Function ==
	717	+(% style="display:none" %) (%%)
633	633
634	634
	720	+== 2.13  USB Port Function ==
	721	+
	722	+
635	635	The USB interface of TrackerD has below functions:
636	636
637	637	* Power on the device
...	...	@@ -639,6 +639,19 @@
639	639	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
640	640	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
641	641
	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	+
642	642	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
643	643
644	644
...	...	@@ -652,7 +652,6 @@
652	652
653	653	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.
654	654
655		-
656	656	[[image:1664502999401-486.png||_mstalt="296985"]]
657	657
658	658
...	...	@@ -667,8 +667,8 @@
667	667
668	668	[[image:1664503047675-651.png||_mstalt="295386"]]
669	669
	770	+(% style="display:none" %) (%%)
670	670
671		-
672	672	== 3.2 Command Set ==
673	673
674	674	=== 3.2.1 Set Transmit Interval ===
...	...	@@ -734,7 +734,7 @@
734	734	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
735	735
736	736
737		-=== 3.2.5 Disable/Enable LED flash ===
	837	+=== 3.2.5 Disable/Enable LED flash and buzzer ===
738	738
739	739
740	740	Disable/Enable LED for position, downlink and uplink
...	...	@@ -773,7 +773,6 @@
773	773
774	774	SMOD define how TrackerD scan and uplink data:
775	775
776		-
777	777	* (% style="color:blue" %)**AT Command:**
778	778
779	779	(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
...	...	@@ -808,6 +808,7 @@
808	808
809	809	AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
810	810
	910	+ AT+SMOD=2,0,3  ~-~->  (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
811	811
812	812	* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
813	813
...	...	@@ -819,10 +819,8 @@
819	819
820	820	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.
821	821
822		-
823	823	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.
824	824
825		-
826	826	* (% style="color:blue" %)**AT Command:**
827	827
828	828	(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
...	...	@@ -840,10 +840,8 @@
840	840
841	841	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.
842	842
843		-
844	844	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
845	845
846		-
847	847	* (% style="color:blue" %)**AT Command:**
848	848
849	849	(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
...	...	@@ -858,8 +858,8 @@
858	858	(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
859	859
860	860
	957	+=== 3.2.10 Disable/Enable the confirmation mode ===
861	861
862		-=== 3.2.10 Disable/Enable the confirmation mode ===
863	863
864	864	* (% style="color:blue" %)**AT Command:**
865	865
...	...	@@ -866,11 +866,11 @@
866	866	(% style="color:#037691" %)**AT+CFM=xx**
867	867
868	868
869		-**~ Example:**
	965	+**Example:**
870	870
871		- AT+CFM=0    **~-~->   ** Disable confirmation
	967	+AT+CFM=0    **~-~->   ** Disable confirmation
872	872
873		- AT+CFM=1    **~-~->  ** Enable confirmation
	969	+AT+CFM=1    **~-~->  ** Enable confirmation
874	874
875	875
876	876	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
...	...	@@ -908,9 +908,9 @@
908	908
909	909	(% style="color:blue" %)**AT Command:**
910	910
911		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	1007	+(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
912	912
913		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	1009	+(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
914	914
915	915	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
916	916
...	...	@@ -926,9 +926,9 @@
926	926
927	927	(% style="color:blue" %)**AT Command:**
928	928
929		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	1025	+(% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
930	930
931		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	1027	+(% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
932	932
933	933	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
934	934
...	...	@@ -942,11 +942,11 @@
942	942
943	943	(% style="color:blue" %)**AT Command:**
944	944
945		-(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
	1041	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
946	946	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
947	947
948	948
949		-=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	1045	+=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
950	950
951	951
952	952	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
...	...	@@ -953,14 +953,131 @@
953	953
954	954	(% style="color:blue" %)**AT Command:**
955	955
956		-(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
	1052	+(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
957	957
958	958
959	959	(% style="color:blue" %)**Downlink Payload:0X24**
960	960
961		-Example: 0x24 01 ~/~/ Same as AT+CHE=1
	1057	+Example: 0x24 01  ~/~/ Same as AT+CHE=1
962	962
963	963
	1060	+=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
	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	+
964	964	= 4. Setting for Different Scenarios =
965	965
966	966
...	...	@@ -1012,16 +1012,15 @@
1012	1012	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1013	1013
1014	1014
1015		-[[image:image-20221118105220-2.png||_mstalt="426608"]]
	1228	+[[image:image-20221207120501-1.png]]
1016	1016
1017	1017
1018	1018
1019	1019	After upgrade finish, it will show finish as below:
1020	1020
1021		-[[image:image-20221118105402-4.png||_mstalt="427986"]]
	1234	+[[image:image-20221207133911-7.png]]
1022	1022
1023	1023
1024		-
1025	1025	= 6. Developer Guide =
1026	1026
1027	1027	== 6.1 Compile Source Code ==
...	...	@@ -1043,13 +1043,70 @@
1043	1043	[[image:1664503715811-892.png||_mstalt="295698"]]
1044	1044
1045	1045
	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	+
1046	1046	(% 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.
1047	1047
	1298	+[[image:image-20221213102311-5.png||height="582" width="711"]]
	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	+
1048	1048	[[image:image-20221024105643-1.png||_mstalt="428129"]]
1049	1049
1050	1050	**~ Figure1**
1051	1051
1052	1052
	1321	+
1053	1053	[[image:image-20221024105643-2.png||_mstalt="428493"]]
1054	1054
1055	1055	**Figure2**
...	...	@@ -1097,9 +1097,8 @@
1097	1097	[[image:1664499635206-262.png||_mstalt="295360"]]
1098	1098
1099	1099
1100		-
1101		-(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1102		-|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
	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**
1103	1103	|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1104	1104	|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1105	1105	|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
...	...	@@ -1109,6 +1109,9 @@
1109	1109	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1110	1110	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1111	1111
	1380	+(% style="display:none" %) (%%)
	1381	+
	1382	+
1112	1112	== 7.3 Notes on using different serial port tools for TrackerD ==
1113	1113
1114	1114	=== 7.3.1  Serial port utility ===
...	...	@@ -1122,7 +1122,6 @@
1122	1122	[[image:image-20221102140621-1.png||_mstalt="425672"]]
1123	1123
1124	1124
1125		-
1126	1126	When using AT commands, the data flow needs to be adjusted to XON/XOFF
1127	1127
1128	1128	[[image:image-20221102140638-2.png||_mstalt="428727"]]
...	...	@@ -1191,6 +1191,18 @@
1191	1191	[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1192	1192
1193	1193
	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	+
1194	1194	= 8  Trouble Shooting =
1195	1195
1196	1196	== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
...	...	@@ -1197,7 +1197,7 @@
1197	1197
1198	1198
1199	1199	(((
1200		-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
	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
1201	1201	)))
1202	1202
1203	1203
...	...	@@ -1211,25 +1211,31 @@
1211	1211
1212	1212	== 8.3  Problem after Upgrading Firmware ==
1213	1213
1214		-=== 8.3.1 Continue Restart after upgrading ===
	1496	+=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1215	1215
1216	1216
1217		-(((
1218		-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
1219		-)))
	1499	+**Error Output**
1220	1220
1221	1221
1222		-[[image:image-20221118105249-3.png||_mstalt="430664"]]
	1502	+[[image:image-20221122100004-4.png||_mstalt="424606"]]
1223	1223
1224	1224
1225		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1505	+(((
	1506	+Some partition is missed during upgrade, please upgrade below four files as example:
1226	1226
	1508	+[[image:image-20221207120524-2.png]]
	1509	+)))
1227	1227
	1511	+
	1512	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1513	+
	1514	+
1228	1228	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
1229	1229
1230	1230
1231		-=== 8.3.3 "flash read err" after upgrade firmware ===
	1518	+=== 8.3.3 "flash read err" after upgrade firmware ===
1232	1232
	1520	+
1233	1233	Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1234	1234
1235	1235	[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
...	...	@@ -1237,28 +1237,32 @@
1237	1237
1238	1238	User need to upgrade again with below four files to solve this issue.
1239	1239
1240		- [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
	1528	+ [[image:image-20221207120530-3.png]]
1241	1241
1242	1242	**Figure 2**
1243	1243
1244	1244
1245		-=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
	1533	+=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1246	1246
	1535	+
1247	1247	User might erase the entire flash include keys and default settings which cause this issue.
1248	1248
1249		-After the upgrade is completed, enter AT+CFG as shown in the figure below.
	1538	+After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1250	1250
	1540	+
1251	1251	[[image:image-20221122100004-3.png||_mstalt="424242"]]
1252	1252
1253		-Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1254	1254
	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	+
1255	1255	After AT+FDR. please set
1256	1256
1257		-* AT+PDOP=7
1258		-* AT+FTIME=180000
	1548	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1259	1259
1260		-Example:
	1550	+* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1261	1261
	1552	+**Example:**
	1553	+
1262	1262	AT+PDOP=7.00
1263	1263
1264	1264	AT+FTIME=180
...	...	@@ -1276,13 +1276,6 @@
1276	1276	AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1277	1277
1278	1278
1279		-
1280		-=== 8.3.4  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 ===
1281		-
1282		-
1283		-[[image:image-20221122100004-4.png||_mstalt="424606"]]
1284		-
1285		-
1286	1286	== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1287	1287
1288	1288
...	...	@@ -1305,6 +1305,59 @@
1305	1305	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
1306	1306
1307	1307
	1593	+== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1594	+
	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	+
1308	1308	= 9.  Order Info =
1309	1309
1310	1310
...	...	@@ -1326,6 +1326,9 @@
1326	1326
1327	1327	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1328	1328
	1667	+(% style="display:none" %) (%%)
	1668	+
	1669	+
1329	1329	= 10.  Packing Info =
1330	1330
1331	1331
...	...	@@ -1341,6 +1341,9 @@
1341	1341
1342	1342	* Weight: 50g
1343	1343
	1685	+(% style="display:none" %) (%%)
	1686	+
	1687	+
1344	1344	= 11. Support =
1345	1345
1346	1346
...	...	@@ -1348,6 +1348,10 @@
1348	1348
1349	1349	* 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]].
1350	1350
	1695	+(% style="display:none" %)
	1696	+
	1697	+
	1698	+
1351	1351	= 12.  Reference =
1352	1352
1353	1353
...	...	@@ -1356,3 +1356,6 @@
1356	1356	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1357	1357
1358	1358	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
	1707	+
	1708	+
	1709	+)))

image-20221128102938-1.png

Author

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

Size

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

Content

image-20221128103040-2.png

Author

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

Size

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

Content

image-20221128110503-3.png

Author

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

Size

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

Content

image-20221128111443-4.png

Author

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

Size

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

Content

image-20221128111850-5.png

Author

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

Size

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

Content

image-20221128111951-6.png

Author

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

Size

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

Content

image-20221128112035-7.png

Author

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

Size

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

Content

image-20221207120501-1.png

Author

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

Size

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

Content

image-20221207120524-2.png

Author

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

Size

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

Content

image-20221207120530-3.png

Author

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

Size

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

Content

image-20221207120536-4.png

Author

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

Size

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

Content

image-20221207120601-5.png

Author

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

Size

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

Content

image-20221207133836-6.png

Author

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

Size

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

Content

image-20221207133911-7.png

Author

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

Size

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

Content

image-20221207134028-8.png

Author

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

Size

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

Content

image-20221213100007-1.png

Author

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

Size

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

Content

image-20221213100626-2.png

Author

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

Size

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

Content

image-20221213100808-3.png

Author

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

Size

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

Content

image-20221213101040-4.png

Author

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

Size

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

Content

image-20221213102311-5.png

Author

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

Size

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

Content

image-20221213102334-6.png

Author

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

Size

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

Content

image-20221213102718-7.png

Author

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

Size

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

Content

image-20221213110952-8.png

Author

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

Size

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

Content

image-20230213110119-1.png

Author

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

Size

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

Content

image-20230213110214-2.png

Author

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

Size

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

Content

image-20230213110506-3.png

Author

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

Size

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

Content

image-20230302145315-1.png

Author

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

Size

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

Content

image-20230307135914-1.png

Author

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

Size

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

Content

image-20230307135932-2.png

Author

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

Size

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

Content

image-20230308115430-1.png

Author

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

Size

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

Content

image-20230308115616-2.png

Author

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

Size

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

Content

image-20230308115701-3.png

Author

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

Size

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

Content

image-20230426085815-1.png

Author

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

Size

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

Content

image-20231023103116-1.png

Author

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

Size

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

Content