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

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 33 removed)
  • image-20221128102938-1.png
  • image-20221128103040-2.png
  • image-20221128110503-3.png
  • image-20221128111443-4.png
  • image-20221128111850-5.png
  • image-20221128111951-6.png
  • image-20221128112035-7.png
  • image-20221207120501-1.png
  • image-20221207120524-2.png
  • image-20221207120530-3.png
  • image-20221207120536-4.png
  • image-20221207120601-5.png
  • image-20221207133836-6.png
  • image-20221207133911-7.png
  • image-20221207134028-8.png
  • image-20221213100007-1.png
  • image-20221213100626-2.png
  • image-20221213100808-3.png
  • image-20221213101040-4.png
  • image-20221213102311-5.png
  • image-20221213102334-6.png
  • image-20221213102718-7.png
  • image-20221213110952-8.png
  • image-20230213110119-1.png
  • image-20230213110214-2.png
  • image-20230213110506-3.png
  • image-20230302145315-1.png
  • image-20230307135914-1.png
  • image-20230307135932-2.png
  • image-20230308115430-1.png
  • image-20230308115616-2.png
  • image-20230308115701-3.png
  • image-20230426085815-1.png

Details

Page properties

Author

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

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,7 +12,6 @@
12	12
13	13
14	14
15		-
16	16	= 1.  Introduction =
17	17
18	18	== 1.1  What is TrackerD ==
...	...	@@ -32,12 +32,15 @@
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	)))
	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	+
38	38	)))
39	39
40		-[[image:image-20230213110119-1.png||height="382" width="834"]]
	42	+[[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.**
...	...	@@ -93,9 +93,6 @@
93	93	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94	94	* Tracking: max: 38mA
95	95
96		-(% style="display:none" %)
97		-
98		-
99	99	== 1.3  Features ==
100	100
101	101
...	...	@@ -114,9 +114,6 @@
114	114	* Tri-color LED, Alarm button
115	115	* Datalog
116	116
117		-(% style="display:none" %)
118		-
119		-
120	120	== 1.4  Applications ==
121	121
122	122
...	...	@@ -123,9 +123,6 @@
123	123	* Logistics and Supply Chain Management
124	124	* Human tracking
125	125
126		-(% style="display:none" %)
127		-
128		-
129	129	= 2.  Use TrackerD =
130	130
131	131	== 2.1 How it works? ==
...	...	@@ -140,7 +140,7 @@
140	140	Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.
141	141
142	142
143		-[[image:image-20230213110214-2.png||height="388" width="847"]]
	136	+[[image:1664501652064-326.png]]
144	144
145	145
146	146
...	...	@@ -152,7 +152,7 @@
152	152	Each TrackerD is shipped with a sticker with the default device EUI as below:
153	153
154	154
155		-[[image:image-20230426085815-1.png||height="259" width="558"]]
	148	+[[image:1664501677253-891.png]]
156	156
157	157
158	158	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -161,14 +161,14 @@
161	161	**__Add APP EUI in the application:__**
162	162
163	163
164		-[[image:1664501711466-918.png||_mstalt="295828"]]
	157	+[[image:1664501711466-918.png]]
165	165
166	166
167	167
168		-[[image:1664501721248-725.png||_mstalt="294450"]]
	161	+[[image:1664501721248-725.png]]
169	169
170	170
171		-[[image:1664501734705-405.png||_mstalt="293306"]]
	164	+[[image:1664501734705-405.png]]
172	172
173	173
174	174
...	...	@@ -175,15 +175,15 @@
175	175	**__Add APP KEY and DEV EUI:__**
176	176
177	177
178		-[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
	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||alt="1654671889112-678.png"]]
179	179
180	180
181	181
182	182	(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
183	183
184		-(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
	177	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
185	185
186		-[[image:1664502835802-546.png||_mstalt="295061"]]
	179	+[[image:1664502835802-546.png]]
187	187
188	188
189	189	(% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
...	...	@@ -206,16 +206,16 @@
206	206	=== 2.4.1 Uplink FPORT~=5, Device Status ===
207	207
208	208
209		-Uplink the device configures with (% style="color:blue" %)**FPORT=5**(%%). Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
	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.
210	210
211		-Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
	204	+Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
212	212
213	213
214		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
215		-|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1
216		-|(% style="width:108px" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
	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
217	217
218		-[[image:1665301570342-765.png||_mstalt="294580"]]
	211	+[[image:1665301570342-765.png]]
219	219
220	220
221	221	(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
...	...	@@ -258,9 +258,9 @@
258	258
259	259	(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
260	260
261		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
262		-|(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
263		-|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
	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
264	264
265	265	(% style="color:blue" %)** SMOD：**
266	266
...	...	@@ -282,26 +282,23 @@
282	282
283	283	(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
284	284
285		-(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)
	278	+(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)
286	286
287	287
288	288	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
289	289
290		-(% border="1" style="background-color:#f2f2f2; width:413px" %)
291		-|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:88px" %)1 Bit|(% style="width:50px" %)1 Bit|(% style="width:128px" %)1 Bit
292		-|(% style="width:75px" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
	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"]]
293	293
294		-(% style="display:none" %)
295		-
296		-
297	297	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
298	298
299	299
300		-Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
	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,
301	301
302	302
303		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)
304		-|(% style="width:60px" %)(((
	293	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	294	+|=(% scope="row" style="width: 60px;" %)(((
305	305	**Size(bytes)**
306	306	)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
307	307	2
...	...	@@ -308,27 +308,24 @@
308	308	)))|(% style="width:30px" %)(((
309	309	2
310	310	)))
311		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	301	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
312	312	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
313	313	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
314	314
315		-[[image:1665301636888-168.png||_mstalt="298012"]]
	305	+[[image:1665301636888-168.png]]
316	316
317	317
318	318	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
319	319
320		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)
321		-|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits
322		-|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]]
	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:"]]
323	323
324		-(% style="display:none" %)
325		-
326		-
327	327	==== (% style="color:blue" %)**FLAG:**(%%) ====
328	328
329		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
330		-|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit
331		-|(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
	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:"]]
332	332
333	333	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
334	334
...	...	@@ -345,12 +345,12 @@
345	345	2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
346	346
347	347
348		-[[image:1664502116362-706.png||_mstalt="293306"]]
	335	+[[image:1664502116362-706.png]]
349	349
350	350
351	351	3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
352	352
353		-[[image:1664502166010-515.png||_mstalt="291395"]]
	340	+[[image:1664502166010-515.png]]
354	354
355	355
356	356
...	...	@@ -373,9 +373,6 @@
373	373	* 3.40v ~~ 3.69v:  20% ~~ 40%
374	374	* < 3.39v:  0~~20%
375	375
376		-(% style="display:none" %) (%%)
377		-
378		-
379	379	==== (% style="color:blue" %)**MOD:**(%%) ====
380	380
381	381	**Example: ** (0x60>>6) & 0x3f =1
...	...	@@ -419,25 +419,25 @@
419	419	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
420	420
421	421
422		-The default uplink payload includes total 11 bytes ((% style="color:blue" %)**AT+SMOD=1,1,0**(%%)). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
	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)
423	423
424	424
425		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
426		-|(% style="width:60px" %)(((
	409	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
	410	+|=(% scope="row" style="width: 60px;" %)(((
427	427	**Size(bytes)**
428		-)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1
429		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	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" %)(((
430	430	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
431	431	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
432	432
433	433	(% class="wikigeneratedid" %)
434		-[[image:1665301687277-443.png||_mstalt="296140"]]
	418	+[[image:1665301687277-443.png]]
435	435
436	436
437	437	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
438	438
439	439
440		-Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
	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.
441	441
442	442
443	443	(% style="color:red" %)**Note for this mode:**
...	...	@@ -448,13 +448,13 @@
448	448
449	449	The payload is 15 bytes, as below.
450	450
451		-(% border="1" style="background-color:#f2f2f2; width:500px" %)
452		-|(((
	435	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	436	+|=(% scope="row" %)(((
453	453	**Size(bytes)**
454	454	)))|4|4|2|1|1|1|1|1
455		-|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
	439	+|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
456	456
457		-[[image:image-20221009160309-2.png||_mstalt="429312"]]
	441	+[[image:image-20221009160309-2.png]]
458	458
459	459
460	460	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
...	...	@@ -465,11 +465,11 @@
465	465	User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
466	466
467	467
468		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
469		-|(% style="width:60px" %)(((
	452	+(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
	453	+|=(% scope="row" style="width: 60px;" %)(((
470	470	**Size(bytes)**
471	471	)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
472		-|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
	456	+|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
473	473	iBeacon MAJOR
474	474	)))|(% style="width:63px" %)(((
475	475	iBeacon MINOR
...	...	@@ -481,7 +481,7 @@
481	481	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
482	482	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
483	483
484		-[[image:1664502425687-834.png||_mstalt="296738"]]
	468	+[[image:1664502425687-834.png]]
485	485
486	486
487	487	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -492,45 +492,22 @@
492	492	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
493	493	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
494	494
495		-(% style="display:none" %) (%%)
	479	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
496	496
497	497
498		-=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
499		-
500		-
501		-The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
502		-
503		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
504		-|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
505		-|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
506		-
507		- [[image:image-20230302145315-1.png]]
508		-
509		-**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
510		-
511		-**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
512		-
513		-**mod** = bytes[2] & 0xC0;
514		-
515		-**Lon**=(bytes[2] & 0x20)
516		-
517		-
518		-=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
519		-
520		-
521	521	TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
522	522
523	523
524		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
525		-|(% style="width:65px" %)(((
	485	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	486	+|=(% scope="row" style="width: 60px;" %)(((
526	526	**Size(bytes)**
527		-)))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
528		-|(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
	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" %)(((
529	529	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
530		-)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
	491	+)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
531	531
532	532	(% class="wikigeneratedid" %)
533		-[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	494	+[[image:1667288597595-714.png||height="212" width="1151"]]
534	534
535	535
536	536	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -537,26 +537,25 @@
537	537	* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
538	538	* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
539	539
540		-(% style="display:none" %) (%%)
	501	+=== 2.4.7  Add Payload format in TTN V3 ===
541	541
542	542
543		-=== 2.4.8  Add Payload format in TTN V3 ===
544		-
545		-
546	546	In TTN V3, user can add a custom payload so it shows friendly.
547	547
548	548	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
549	549
550	550
551		-[[image:1664502649601-895.png||_mstalt="296985"]]
	509	+[[image:1664502649601-895.png]]
552	552
553	553
554	554
555		-Add the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	513	+Add the decoder from this link:
556	556
	515	+[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	516	+
557	557	Save the change the uplink message will be parsed. As below:
558	558
559		-[[image:1664502676891-606.png||_mstalt="296673"]]
	519	+[[image:1664502676891-606.png]]
560	560
561	561
562	562	== 2.5 Integrate with Datacake ==
...	...	@@ -567,7 +567,7 @@
567	567	Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
568	568
569	569
570		-[[image:1664502695771-538.png||_mstalt="297349"]]
	530	+[[image:1664502695771-538.png]]
571	571
572	572
573	573	== 2.6 Integrate with Tago ==
...	...	@@ -578,70 +578,29 @@
578	578	Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
579	579
580	580
581		-[[image:1664502715371-321.png||_mstalt="292162"]]
	541	+[[image:1664502715371-321.png]]
582	582
583	583
584		-== 2.7  Integrate with Node-red ==
	544	+== 2.7  Datalog Feature ==
585	585
586	586
587		-~1. Install node-red, please refer to the installation method in the link:
588		-
589		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
590		-
591		-
592		-2. Import the created flow template, please refer to the import method in the link:
593		-
594		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
595		-
596		-
597		-The address of the flow template: [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]
598		-
599		-(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**
600		-
601		-[[image:image-20230307135914-1.png||height="527" width="1045"]]
602		-
603		-
604		-[[image:image-20230307135932-2.png||height="527" width="1044"]]
605		-
606		-
607		-3. Display the map
608		- Enter the link to the map:
609		-
610		- Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
611		-
612		-**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
613		-
614		-
615		- Hit all input in input stream
616		-
617		- [[image:image-20230308115616-2.png||height="563" width="1070"]]
618		-
619		-
620		- View map again
621		-
622		-[[image:image-20230308115701-3.png||height="571" width="1085"]]
623		-
624		-
625		-== 2.8  Datalog Feature ==
626		-
627		-
628	628	total 273 entries,by default,
629	629
630		-User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	549	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
631	631
632	632	Example use case.
633	633
634		-[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	553	+[[image:image-20221009234703-2.png||height="328" width="899"]]
635	635
636	636
637		-[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	556	+[[image:image-20221009234629-1.png||height="390" width="577"]]
638	638
639	639
640		-== 2.9  Alarm Mode ==
	559	+== 2.8 Alarm Mode ==
641	641
642	642
643	643	(((
644		-User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
	563	+User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
645	645	)))
646	646
647	647
...	...	@@ -662,22 +662,15 @@
662	662	)))
663	663
664	664
665		-== 2.10  Transport Mode ==
	584	+== 2.9 Transport Mode ==
666	666
667	667
668		-In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
	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.
669	669
670		-When device is set in Transport Mode, it will uplink more frequenctly during moving.
671	671
672		-* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
673		-* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
674		-* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
	590	+== 2.10 LED Status ==
675	675
676		-(% style="display:none" %) (%%)
677	677
678		-== 2.11  LED Status ==
679		-
680		-
681	681	(% border="1.5" style="background-color:#ffffcc; width:500px" %)
682	682	|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
683	683	|(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A
...	...	@@ -692,14 +692,12 @@
692	692	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
693	693	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
694	694
695		-(% style="display:none" %) (%%)
	607	+== 2.11 Button Function ==
696	696
697		-== 2.12  Button Function ==
698	698
699		-
700	700	(% style="color:blue" %)**RESET button:**
701	701
702		-[[image:1664502835802-546.png||_mstalt="295061"]]
	612	+[[image:1664502835802-546.png]]
703	703
704	704	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
705	705
...	...	@@ -706,9 +706,8 @@
706	706
707	707	(% style="color:red" %)**RED button:**
708	708
709		-[[image:image-20230213110506-3.png]](% style="display:none" %)
	619	+[[image:1664502854406-763.png]]
710	710
711		-(% style="display:none" %) (%%)
712	712
713	713	(% border="1" style="background-color:#ffffcc; width:510px" %)
714	714	|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
...	...	@@ -716,12 +716,9 @@
716	716	|(% 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
717	717	|(% 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.
718	718
719		-(% style="display:none" %) (%%)
	628	+== 2.12 USB Port Function ==
720	720
721	721
722		-== 2.13  USB Port Function ==
723		-
724		-
725	725	The USB interface of TrackerD has below functions:
726	726
727	727	* Power on the device
...	...	@@ -729,19 +729,6 @@
729	729	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
730	730	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
731	731
732		-(% style="display:none" %) (%%)
733		-
734		-
735		-== 2.14  Sleep Mode ==
736		-
737		-
738		-(% 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.
739		-
740		-In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
741		-
742		-Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
743		-
744		-
745	745	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
746	746
747	747
...	...	@@ -756,22 +756,22 @@
756	756	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.
757	757
758	758
759		-[[image:1664502999401-486.png||_mstalt="296985"]]
	652	+[[image:1664502999401-486.png]]
760	760
761	761
762	762	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:
763	763
764	764
765		-[[image:1664503022490-662.png||_mstalt="293332"]]
	658	+[[image:1664503022490-662.png]]
766	766
767	767
768		-[[image:1664503035713-500.png||_mstalt="291096"]]
	661	+[[image:1664503035713-500.png]]
769	769
770	770
771		-[[image:1664503047675-651.png||_mstalt="295386"]]
	664	+[[image:1664503047675-651.png]]
772	772
773		-(% style="display:none" %) (%%)
774	774
	667	+
775	775	== 3.2 Command Set ==
776	776
777	777	=== 3.2.1 Set Transmit Interval ===
...	...	@@ -837,7 +837,7 @@
837	837	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
838	838
839	839
840		-=== 3.2.5 Disable/Enable LED flash and buzzer ===
	733	+=== 3.2.5 Disable/Enable LED flash ===
841	841
842	842
843	843	Disable/Enable LED for position, downlink and uplink
...	...	@@ -897,9 +897,9 @@
897	897
898	898	(% style="color:#037691" %)**cc:   **
899	899
900		-* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	793	+* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
901	901
902		-* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
	795	+* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
903	903
904	904	(% style="color:blue" %)**Example:**
905	905
...	...	@@ -961,8 +961,8 @@
961	961	(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
962	962
963	963
964		-=== 3.2.10 Disable/Enable the confirmation mode ===
965	965
	858	+**Disable/Enable the confirmation mode**
966	966
967	967	* (% style="color:blue" %)**AT Command:**
968	968
...	...	@@ -981,7 +981,7 @@
981	981	(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
982	982
983	983
984		-=== 3.2.11  Auto Send None-ACK messages ===
	877	+=== 3.2.10  Auto Send None-ACK messages ===
985	985
986	986
987	987	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.
...	...	@@ -999,10 +999,10 @@
999	999
1000	1000	* (% style="color:blue" %)**Downlink Command: 0x34**
1001	1001
1002		-Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
	895	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
1003	1003
1004	1004
1005		-=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
	898	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
1006	1006
1007	1007
1008	1008	BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
...	...	@@ -1011,16 +1011,16 @@
1011	1011
1012	1012	(% style="color:blue" %)**AT Command:**
1013	1013
1014		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	907	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1015	1015
1016		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	909	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1017	1017
1018	1018	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1019	1019
1020		-Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
	913	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1021	1021
1022	1022
1023		-=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
	916	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1024	1024
1025	1025
1026	1026	WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
...	...	@@ -1029,16 +1029,16 @@
1029	1029
1030	1030	(% style="color:blue" %)**AT Command:**
1031	1031
1032		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	925	+ (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1033	1033
1034		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	927	+ (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1035	1035
1036	1036	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1037	1037
1038		-Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
	931	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1039	1039
1040	1040
1041		-=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
	934	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1042	1042
1043	1043
1044	1044	Users can use this feature to enable/disable Information printing.
...	...	@@ -1045,11 +1045,11 @@
1045	1045
1046	1046	(% style="color:blue" %)**AT Command:**
1047	1047
1048		-(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
	941	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1049	1049	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1050	1050
1051	1051
1052		-=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	945	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1053	1053
1054	1054
1055	1055	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
...	...	@@ -1056,92 +1056,14 @@
1056	1056
1057	1057	(% style="color:blue" %)**AT Command:**
1058	1058
1059		-(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
	952	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1060	1060
1061	1061
1062	1062	(% style="color:blue" %)**Downlink Payload:0X24**
1063	1063
1064		-Example: 0x24 01  ~/~/ Same as AT+CHE=1
	957	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
1065	1065
1066	1066
1067		-=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1068		-
1069		-
1070		-User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1071		-
1072		-(% style="color:blue" %)**AT Command:**
1073		-
1074		-(% style="color:#037691" %)**AT+PT=xx**
1075		-
1076		- Example:
1077		-
1078		- AT+PT=14    ~-~->    Set to detect car motion.
1079		-
1080		- AT+PT=41  ~-~->    set to detect walk motion.
1081		-
1082		-
1083		-(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1084		-
1085		-0xB4 14          ~/~/  Same as AT+PT=14
1086		-
1087		-
1088		-=== 3.2.17  Set AT command window time（Since firmware 1.4.5） ===
1089		-
1090		-
1091		-AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1092		-
1093		-(% style="color:blue" %)**AT Command:**
1094		-
1095		-(% style="color:#037691" %)**AT+ATST=XX**
1096		-
1097		- Example:
1098		-
1099		- AT+ATST=15    ~-~-> Set the time to 15 seconds
1100		-
1101		-(% style="color:blue" %)**Downlink Payload:0XB5**(%%)
1102		-
1103		-0xB5 0F          ~/~/  Same as AT+ATST=15
1104		-
1105		-=== 3.2.18  Set the stepmeter mode（Since firmware 1.4.5） ===
1106		-
1107		-
1108		-After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1109		-
1110		-(% style="color:blue" %)**AT Command:**
1111		-
1112		-(% style="color:#037691" %)**AT+PM=xx**
1113		-
1114		- Example:
1115		-
1116		- AT+PM=1    ~-~->  Turn on step counting mode
1117		-
1118		-AT+PM=0    ~-~->  Turn OFF step counting mode
1119		-
1120		-(% style="color:blue" %)**Downlink Payload:0XB6**(%%)
1121		-
1122		-0xB6 01          ~/~/  Same as AT+PM=1
1123		-
1124		-
1125		-=== 3.2.19  Set down the decline detection mode（Since firmware 1.4.5） ===
1126		-
1127		-
1128		-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.
1129		-
1130		-(% style="color:blue" %)**AT Command:**
1131		-
1132		-(% style="color:#037691" %)**AT+FD=xx**
1133		-
1134		- Example:
1135		-
1136		- AT+FD=1    ~-~->  Turn on the Fall detection
1137		-
1138		-AT+FD=0    ~-~->  Turn OFF the Fall detection
1139		-
1140		-(% style="color:blue" %)**Downlink Payload:0XB7**(%%)
1141		-
1142		-0xB7 01          ~/~/  Same as AT+FD=1
1143		-
1144		-
1145	1145	= 4. Setting for Different Scenarios =
1146	1146
1147	1147
...	...	@@ -1174,10 +1174,10 @@
1174	1174	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1175	1175
1176	1176
1177		-[[image:1664503563660-578.png||_mstalt="296777"]]
	992	+[[image:1664503563660-578.png]]
1178	1178
1179	1179
1180		-[[image:1664503574618-659.png||_mstalt="297986"]]
	995	+[[image:1664503574618-659.png]]
1181	1181
1182	1182
1183	1183
...	...	@@ -1193,15 +1193,16 @@
1193	1193	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1194	1194
1195	1195
1196		-[[image:image-20221207120501-1.png]]
	1011	+[[image:image-20221118105220-2.png]]
1197	1197
1198	1198
1199	1199
1200	1200	After upgrade finish, it will show finish as below:
1201	1201
1202		-[[image:image-20221207133911-7.png]]
	1017	+[[image:image-20221118105402-4.png]]
1203	1203
1204	1204
	1020	+
1205	1205	= 6. Developer Guide =
1206	1206
1207	1207	== 6.1 Compile Source Code ==
...	...	@@ -1214,81 +1214,24 @@
1214	1214	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]]
1215	1215
1216	1216
1217		-[[image:1664503635019-941.png||_mstalt="294658"]]
	1033	+[[image:1664503635019-941.png]]
1218	1218
1219	1219
1220	1220
1221	1221	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1222	1222
1223		-[[image:1664503715811-892.png||_mstalt="295698"]]
	1039	+[[image:1664503715811-892.png]]
1224	1224
1225	1225
1226		-=== 6.1.2  Build the development environment ===
1227		-
1228		-
1229		-**~1. Download and install arduino IDE**
1230		-
1231		-[[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]]
1232		-
1233		-
1234		-**2. Download the ESP32 development package in the arduino IDE**
1235		-
1236		-[[image:image-20221213100007-1.png]]
1237		-
1238		-
1239		-Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1240		-
1241		-[[image:image-20221213100626-2.png]]
1242		-
1243		-
1244		-Restart the IDE after the addition is complete, then:
1245		-
1246		-[[image:image-20221213100808-3.png||height="679" width="649"]]
1247		-
1248		-
1249		-[[image:image-20221213101040-4.png]]
1250		-
1251		-
1252		-(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1253		-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)**
1254		-
1255		-
1256		-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:
1257		-
1258		-(% style="color:blue" %)**Methods as below:**
1259		-
1260		-~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1261		-
1262		-2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1263		-
1264	1264	(% 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.
1265	1265
1266		-[[image:image-20221213102311-5.png||height="582" width="711"]]
	1044	+[[image:image-20221024105643-1.png]]
1267	1267
1268		-
1269		-**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1270		-
1271		-[[image:image-20221213102334-6.png]]
1272		-
1273		-(% style="color:red" %)**Note: This step requires a python environment**
1274		-
1275		-
1276		-Either way, in the end:
1277		-
1278		-The final effect is to open the arduino and you can see the esp32
1279		-
1280		-[[image:image-20221213110952-8.png||height="866" width="711"]]
1281		-
1282		-
1283		-
1284		-[[image:image-20221024105643-1.png||_mstalt="428129"]]
1285		-
1286	1286	**~ Figure1**
1287	1287
1288	1288
	1049	+[[image:image-20221024105643-2.png]]
1289	1289
1290		-[[image:image-20221024105643-2.png||_mstalt="428493"]]
1291		-
1292	1292	**Figure2**
1293	1293
1294	1294
...	...	@@ -1297,7 +1297,7 @@
1297	1297	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1298	1298
1299	1299
1300		-[[image:1664503752288-974.png||_mstalt="298194"]]
	1059	+[[image:1664503752288-974.png]]
1301	1301
1302	1302
1303	1303	== 6.2 Source Code ==
...	...	@@ -1305,19 +1305,19 @@
1305	1305
1306	1306	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1307	1307
1308		-[[image:1664503794261-827.png||_mstalt="296387"]]
	1067	+[[image:1664503794261-827.png]]
1309	1309
1310	1310
1311	1311
1312	1312	* (% style="color:blue" %)**Click to upload**
1313	1313
1314		-[[image:1664503808294-336.png||_mstalt="295711"]]
	1073	+[[image:1664503808294-336.png]]
1315	1315
1316	1316
1317	1317
1318	1318	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1319	1319
1320		-[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
	1079	+[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1321	1321
1322	1322
1323	1323	= 7.  FAQ =
...	...	@@ -1331,12 +1331,12 @@
1331	1331	== 7.2 What is the pin mapping for the USB program cable? ==
1332	1332
1333	1333
1334		-[[image:1664499635206-262.png||_mstalt="295360"]]
	1093	+[[image:1664499635206-262.png]]
1335	1335
1336	1336
1337	1337
1338		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1339		-|=(% 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**
	1097	+(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
	1098	+|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
1340	1340	|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1341	1341	|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1342	1342	|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
...	...	@@ -1346,9 +1346,6 @@
1346	1346	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1347	1347	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1348	1348
1349		-(% style="display:none" %) (%%)
1350		-
1351		-
1352	1352	== 7.3 Notes on using different serial port tools for TrackerD ==
1353	1353
1354	1354	=== 7.3.1  Serial port utility ===
...	...	@@ -1359,13 +1359,13 @@
1359	1359	Need to adjust the data stream to RTS/CTS on physical restart.
1360	1360
1361	1361	(% class="wikigeneratedid" %)
1362		-[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1118	+[[image:image-20221102140621-1.png]]
1363	1363
1364	1364
1365	1365
1366	1366	When using AT commands, the data flow needs to be adjusted to XON/XOFF
1367	1367
1368		-[[image:image-20221102140638-2.png||_mstalt="428727"]]
	1124	+[[image:image-20221102140638-2.png]]
1369	1369
1370	1370
1371	1371	=== 7.3.2  SecureCRT ===
...	...	@@ -1374,22 +1374,22 @@
1374	1374	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.
1375	1375
1376	1376
1377		-[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1133	+[[image:image-20221102140704-3.png]]
1378	1378
1379	1379
1380		-[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1136	+[[image:image-20221102140712-4.png]]
1381	1381
1382	1382
1383	1383	=== 7.3.3  PUTTY ===
1384	1384
1385	1385
1386		-[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1142	+[[image:image-20221102140748-5.png]]
1387	1387
1388	1388
1389	1389	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.
1390	1390
1391	1391
1392		-[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1148	+[[image:image-20221102140801-6.png]]
1393	1393
1394	1394
1395	1395	== 7.4 How to modify source code to compile different frequency band bin file? ==
...	...	@@ -1404,7 +1404,7 @@
1404	1404	**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1405	1405
1406	1406
1407		-[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
	1163	+[[image:image-20221116111844-1.png||height="227" width="782"]]
1408	1408
1409	1409
1410	1410
...	...	@@ -1411,7 +1411,7 @@
1411	1411	**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1412	1412
1413	1413
1414		-[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1170	+[[image:image-20221116111844-2.png||height="262" width="781"]]
1415	1415
1416	1416
1417	1417
...	...	@@ -1418,7 +1418,7 @@
1418	1418	**3. Compile the AS923_JP band, please refer to the intention shown**
1419	1419
1420	1420
1421		-[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
	1177	+[[image:image-20221116111844-3.png||height="338" width="746"]]
1422	1422
1423	1423
1424	1424
...	...	@@ -1425,24 +1425,12 @@
1425	1425	**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.**
1426	1426
1427	1427
1428		-[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
	1184	+[[image:image-20221116111844-4.png||height="641" width="739"]]
1429	1429
1430	1430
1431		-[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
	1187	+[[image:image-20221116111844-5.png||height="551" width="708"]]
1432	1432
1433	1433
1434		-== 7.5 Are there example python example for BLE Indoor Positioning? ==
1435		-
1436		-
1437		-[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1438		-
1439		-
1440		-== 7.6 Can alert mode and transport mode be used together? ==
1441		-
1442		-
1443		-Yes, you can also press the panic button to sound the alarm if set to transport mode
1444		-
1445		-
1446	1446	= 8  Trouble Shooting =
1447	1447
1448	1448	== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
...	...	@@ -1449,7 +1449,7 @@
1449	1449
1450	1450
1451	1451	(((
1452		-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
	1196	+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
1453	1453	)))
1454	1454
1455	1455
...	...	@@ -1463,69 +1463,50 @@
1463	1463
1464	1464	== 8.3  Problem after Upgrading Firmware ==
1465	1465
1466		-=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
	1210	+=== 8.3.1 Continue Restart after upgrading ===
1467	1467
1468	1468
1469		-**Error Output**
1470		-
1471		-
1472		-[[image:image-20221122100004-4.png||_mstalt="424606"]]
1473		-
1474		-
1475	1475	(((
1476		-Some partition is missed during upgrade, please upgrade below four files as example:
1477		-
1478		-[[image:image-20221207120524-2.png]]
	1214	+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
1479	1479	)))
1480	1480
1481	1481
1482		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1218	+[[image:image-20221118105249-3.png]]
1483	1483
1484	1484
1485		-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
	1221	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1486	1486
1487	1487
1488		-=== 8.3.3 "flash read err" after upgrade firmware ===
	1224	+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
1489	1489
1490	1490
	1227	+=== 8.3.3 "flash read err" after upgrade firmware ===
	1228	+
1491	1491	Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1492	1492
	1231	+[[image:image-20221122100004-1.png||height="497" width="534"]]
1493	1493
1494		-[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1495	1495
1496		-
1497	1497	User need to upgrade again with below four files to solve this issue.
1498	1498
1499		- [[image:image-20221207120530-3.png]]
	1236	+ [[image:image-20221122100004-2.png||height="619" width="389"]]
1500	1500
1501	1501	**Figure 2**
1502	1502
1503	1503
1504		-=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
	1241	+=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1505	1505
1506		-
1507	1507	User might erase the entire flash include keys and default settings which cause this issue.
1508	1508
1509		-After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
	1245	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
1510	1510
	1247	+[[image:image-20221122100004-3.png]]
1511	1511
1512		-[[image:image-20221122100004-3.png||_mstalt="424242"]]
	1249	+Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1513	1513
1514	1514
1515		-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.
	1252	+Example:
1516	1516
1517		-After AT+FDR. please set
1518		-
1519		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1520		-
1521		-* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1522		-
1523		-**Example:**
1524		-
1525		-AT+PDOP=7.00
1526		-
1527		-AT+FTIME=180
1528		-
1529	1529	AT+DEUI=70B3D57ED0053981
1530	1530
1531	1531	AT+APPEUI=D23345667BCBCCAF
...	...	@@ -1539,6 +1539,13 @@
1539	1539	AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1540	1540
1541	1541
	1267	+
	1268	+=== 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 ===
	1269	+
	1270	+
	1271	+[[image:image-20221122100004-4.png]]
	1272	+
	1273	+
1542	1542	== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1543	1543
1544	1544
...	...	@@ -1552,61 +1552,15 @@
1552	1552
1553	1553	2)  Set PDOP to a higher value.
1554	1554
1555		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1287	+* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1556	1556
1557		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1289	+* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1558	1558
1559		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1291	+* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1560	1560
1561	1561	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
1562	1562
1563	1563
1564		-== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1565		-
1566		-
1567		-When upgrading, use the erase button to upgrade
1568		-
1569		-[[image:image-20221207120536-4.png]]
1570		-
1571		-
1572		-The parameters are displayed abnormally and cannot be fixed using AT+FDR
1573		-
1574		-[[image:image-20221128103040-2.png||height="431" width="525"]]
1575		-
1576		-
1577		-Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1578		-
1579		-[[image:image-20221207134028-8.png]]
1580		-
1581		-
1582		-Reboot information after upgrade
1583		-
1584		-[[image:image-20221128111443-4.png||height="432" width="546"]]
1585		-
1586		-
1587		-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
1588		-
1589		-[[image:image-20221128111850-5.png]]
1590		-
1591		-
1592		-After the parameters return to normal, upgrade to the version you need again
1593		-
1594		-[[image:image-20221207120601-5.png]]
1595		-
1596		-
1597		-At this point, the parameters return to normal after running AT+FDR again
1598		-
1599		-[[image:image-20221128112035-7.png]]
1600		-
1601		-
1602		-== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1603		-
1604		-
1605		-~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1606		-
1607		-2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1608		-
1609		-
1610	1610	= 9.  Order Info =
1611	1611
1612	1612
...	...	@@ -1628,8 +1628,6 @@
1628	1628
1629	1629	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1630	1630
1631		-(% style="display:none" %) (%%)
1632		-
1633	1633	= 10.  Packing Info =
1634	1634
1635	1635
...	...	@@ -1645,8 +1645,6 @@
1645	1645
1646	1646	* Weight: 50g
1647	1647
1648		-(% style="display:none" %) (%%)
1649		-
1650	1650	= 11. Support =
1651	1651
1652	1652
...	...	@@ -1654,7 +1654,6 @@
1654	1654
1655	1655	* 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]].
1656	1656
1657		-
1658	1658	= 12.  Reference =
1659	1659
1660	1660
...	...	@@ -1663,6 +1663,3 @@
1663	1663	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1664	1664
1665	1665	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1666		-
1667		-
1668		-)))

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