Changes for page TrackerD -- LoRaWAN Tracker User Manual

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 31 added, 0 removed)
  • 1665301570342-765.png
  • 1665301636888-168.png
  • 1665301687277-443.png
  • 1665301786397-168.png
  • 1667288597595-714.png
  • image-20221009160220-1.png
  • image-20221009160309-2.png
  • image-20221009234629-1.png
  • image-20221009234703-2.png
  • image-20221024105643-1.png
  • image-20221024105643-2.png
  • image-20221102140621-1.png
  • image-20221102140638-2.png
  • image-20221102140704-3.png
  • image-20221102140712-4.png
  • image-20221102140748-5.png
  • image-20221102140801-6.png
  • image-20221107145243-1.png
  • image-20221116111844-1.png
  • image-20221116111844-2.png
  • image-20221116111844-3.png
  • image-20221116111844-4.png
  • image-20221116111844-5.png
  • image-20221118104359-1.png
  • image-20221118105220-2.png
  • image-20221118105249-3.png
  • image-20221118105402-4.png
  • image-20221122100004-1.png
  • image-20221122100004-2.png
  • image-20221122100004-3.png
  • image-20221122100004-4.png

Details

Page properties

Author

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

Content

...	...	@@ -1,7 +3,5 @@
1		-== ==
2		-
3	3	(% style="text-align:center" %)
4		-[[image:1664505654417-133.png]]
	2	+[[image:1664505654417-133.png||_mstalt="293696"]]
5	5
6	6
7	7
...	...	@@ -16,7 +16,6 @@
16	16
17	17	= 1.  Introduction =
18	18
19		-
20	20	== 1.1  What is TrackerD ==
21	21
22	22
...	...	@@ -42,13 +42,12 @@
42	42
43	43	)))
44	44
45		-[[image:1664499921684-770.png]]
	42	+[[image:1664499921684-770.png||_mstalt="298194"]]
46	46
47	47
48	48	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
49	49
50	50
51		-
52	52	== 1.2 Specifications ==
53	53
54	54
...	...	@@ -123,9 +123,8 @@
123	123	* Logistics and Supply Chain Management
124	124	* Human tracking
125	125
126		-= 2.1 Use TrackerD =
	122	+= 2.  Use TrackerD =
127	127
128		-
129	129	== 2.1 How it works? ==
130	130
131	131
...	...	@@ -132,7 +132,6 @@
132	132	TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
133	133
134	134
135		-
136	136	== 2.2 Quick guide to connect to LoRaWAN server ==
137	137
138	138
...	...	@@ -139,7 +139,7 @@
139	139	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.
140	140
141	141
142		-[[image:1664501652064-326.png]]
	136	+[[image:1664501652064-326.png||_mstalt="293306"]]
143	143
144	144
145	145
...	...	@@ -151,7 +151,7 @@
151	151	Each TrackerD is shipped with a sticker with the default device EUI as below:
152	152
153	153
154		-[[image:1664501677253-891.png]]
	148	+[[image:1664501677253-891.png||_mstalt="296569"]]
155	155
156	156
157	157	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -160,14 +160,14 @@
160	160	**__Add APP EUI in the application:__**
161	161
162	162
163		-[[image:1664501711466-918.png]]
	157	+[[image:1664501711466-918.png||_mstalt="295828"]]
164	164
165	165
166	166
167		-[[image:1664501721248-725.png]]
	161	+[[image:1664501721248-725.png||_mstalt="294450"]]
168	168
169	169
170		-[[image:1664501734705-405.png]]
	164	+[[image:1664501734705-405.png||_mstalt="293306"]]
171	171
172	172
173	173
...	...	@@ -174,48 +174,57 @@
174	174	**__Add APP KEY and DEV EUI:__**
175	175
176	176
177		-[[image:1664501784668-703.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||_mstalt="298233" alt="1654671889112-678.png"]]
178	178
179	179
180	180
	175	+(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
181	181
182		-(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
	177	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
183	183
	179	+[[image:1664502835802-546.png||_mstalt="295061"]]
184	184
	181	+
185	185	(% 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.
186	186
187	187
188		-== 2.3 Positioning Mode(SMOD) ==
	185	+== 2.3  Positioning Mode(SMOD) ==
189	189
	187	+
190	190	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191	191
192		-* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
193		-* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
194		-* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
	190	+* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
	191	+* (% style="color:#037691" %)**BLE or WiFi ONLY:            **(%%)** **Only obtain iBeacon info via BLE and uplink  or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking.
	192	+* (% style="color:#037691" %)**GPS/BLE Hybrid:                        **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
195	195
196	196	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197	197
198	198
199		-== 2.3 Uplink Payload ==
	197	+== 2.4  Uplink Payload ==
200	200
	199	+=== 2.4.1 Uplink FPORT~=5, Device Status ===
201	201
202		-=== 2.3.1 Uplink FPORT~=5, Device Status ===
203	203
204		-Uplink the device configures with FPORT=5. Once LHT52 Joined the network, it will uplink this message to the server. After first uplink, LHT52 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.
205	205
206		-|=**Size (bytes)**|=**1**|=**2**|=**1**|=**1**|=**2**
207		-|**Value**|Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT
	204	+Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
208	208
209		-[[image:image-20221006181357-2.png]]
210	210
211		-Example Payload (FPort=5):  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]]
	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
212	212
213		-**Sensor Model**: For TrackerD, this value is 0x13.
	211	+[[image:1665301570342-765.png||_mstalt="294580"]]
214	214
215		-**Firmware Version**: 0x0100, Means: v1.0.0 version.
216	216
217		-**Frequency Band**:
	214	+(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
218	218
	216	+(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
	217	+
	218	+(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
	219	+
	220	+(% style="color:#037691" %)**Frequency Band**:
	221	+
219	219	*0x01: EU868
220	220
221	221	*0x02: US915
...	...	@@ -236,34 +236,70 @@
236	236
237	237	*0x0a: AS923-3
238	238
239		-**Sub-Band**: value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
	242	+Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
240	240
241		-**BAT**: shows the battery voltage for TrackerD.
	244	+(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
242	242
243		-Ex1: 0x0B3A = 2874mV
244	244
	247	+(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
	248	+
245	245	Use can also get the Device Status uplink through the downlink command:
246	246
247	247
248		-=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning ===
	252	+(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
249	249
	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
250	250
251		-The default uplink payload includes totally 11 bytes. (User can use AT+SMOD=1,0 to enable uploading on-board Temperature and humidity value, and total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
	258	+(% style="color:blue" %)** SMOD：**
252	252
	260	+(% style="color:red" %)** 1 :** (%%) GPS ONLY
253	253
254		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
255		-|=(% scope="row" style="width: 50px;" %)(((
	262	+(% style="color:red" %)** 2 :** (%%) BLE ONLY
	263	+
	264	+(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
	265	+
	266	+
	267	+(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
	268	+
	269	+(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
	270	+
	271	+(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
	272	+
	273	+
	274	+(% style="color:blue" %)** BLE_Settings:**
	275	+
	276	+(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
	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)(%%)
	279	+
	280	+
	281	+(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
	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	+
	287	+=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
	288	+
	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,
	291	+
	292	+
	293	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	294	+|=(% scope="row" style="width: 60px;" %)(((
256	256	**Size(bytes)**
257		-)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
258		-2(optional)
259		-)))|(% style="width:87px" %)(((
260		-2(optional)
	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
261	261	)))
262	262	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
263	263	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
264		-)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
	303	+)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
265	265
266		-[[image:1664501958445-288.png]]
	305	+[[image:1665301636888-168.png||_mstalt="298012"]]
267	267
268	268
269	269	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
...	...	@@ -274,9 +274,9 @@
274	274
275	275	==== (% style="color:blue" %)**FLAG:**(%%) ====
276	276
277		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
278		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
279		-|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version
	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:"]]
280	280
281	281	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
282	282
...	...	@@ -290,30 +290,29 @@
290	290
291	291	1.  When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
292	292
293		-2.  When enable 9-axis motion sensor, 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:
	332	+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:
294	294
295	295
296		-[[image:1664502116362-706.png]]
	335	+[[image:1664502116362-706.png||_mstalt="293306"]]
297	297
298	298
	338	+3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
299	299
300		-4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
	340	+[[image:1664502166010-515.png||_mstalt="291395"]]
301	301
302		-[[image:1664502166010-515.png]]
303	303
304	304
305		-
306	306	==== (% style="color:blue" %)**Alarm:**(%%) ====
307	307
308		-Example:  0x4B & 0x40 >> 6 = 0x01
	346	+**Example: ** 0x4B & 0x40 >> 6 = 0x01
309	309
310	310
311	311	==== (% style="color:blue" %)**BAT:**(%%) ====
312	312
313		-Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
	351	+**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
314	314
315	315	(((
316		-The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
	354	+The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
317	317	)))
318	318
319	319	* > 4.0v :  80% ~~ 100%
...	...	@@ -322,17 +322,33 @@
322	322	* 3.40v ~~ 3.69v:  20% ~~ 40%
323	323	* < 3.39v:  0~~20%
324	324
	363	+==== (% style="color:blue" %)**MOD:**(%%) ====
325	325
	365	+**Example: ** (0x60>>6) & 0x3f =1
	366	+
	367	+**Set the format of GPS data uplink link：**
	368	+
	369	+(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
	370	+(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
	371	+
	372	+
	373	+**Set the format of BLE data uplink link：**
	374	+
	375	+(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
	376	+
	377	+
326	326	==== (% style="color:blue" %)**LON:**(%%) ====
327	327
	380	+**Example:** (0x60>>5) & 0x01=1.
	381	+
328	328	Enable/Disable LED activity for uplink
329	329
330	330	(((
331		-0x00:  Disable LED indicator.
	385	+(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
332	332	)))
333	333
334	334	(((
335		-0x01:  Enable LED indicator (Default Value)
	389	+(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
336	336	)))
337	337
338	338
...	...	@@ -346,16 +346,55 @@
346	346	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
347	347
348	348
	403	+=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
349	349
350		-=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
351	351
	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)
352	352
353	353
354		-=== 2.3.4 BLE positioning Payload(Fport2) ===
	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" %)(((
	414	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	415	+)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
355	355
	417	+(% class="wikigeneratedid" %)
	418	+[[image:1665301687277-443.png||_mstalt="296140"]]
356	356
357		-Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
358	358
	421	+=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
	422	+
	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	+
	426	+
	427	+(% style="color:red" %)**Note for this mode:**
	428	+
	429	+* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
	430	+* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
	431	+* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
	432	+
	433	+The payload is 15 bytes, as below.
	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
	440	+
	441	+[[image:image-20221009160309-2.png||_mstalt="429312"]]
	442	+
	443	+
	444	+=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
	445	+
	446	+
	447	+TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink.
	448	+
	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	+
	451	+
359	359	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
360	360	|=(% scope="row" style="width: 60px;" %)(((
361	361	**Size(bytes)**
...	...	@@ -372,72 +372,100 @@
372	372	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
373	373	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
374	374
375		-[[image:1664502425687-834.png]]
	468	+[[image:1664502425687-834.png||_mstalt="296738"]]
376	376
377	377
378		-* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
	471	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
379	379	* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
380	380	* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
381	381	* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
382		-* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
	475	+* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
383	383	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
384	384	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
385	385
386		-=== 2.3.5 Add Payload format in TTN V3 ===
	479	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
387	387
388	388
389		-In TTN V3, use can add a custom payload so it shows friendly.
	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.
390	390
	484	+
	485	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	486	+|=(% scope="row" style="width: 60px;" %)(((
	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" %)(((
	490	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	491	+)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
	492	+
	493	+(% class="wikigeneratedid" %)
	494	+[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	495	+
	496	+
	497	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	498	+* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
	499	+* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
	500	+
	501	+=== 2.4.7  Add Payload format in TTN V3 ===
	502	+
	503	+
	504	+In TTN V3, user can add a custom payload so it shows friendly.
	505	+
391	391	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
392	392
393	393
394		-[[image:1664502649601-895.png]]
	509	+[[image:1664502649601-895.png||_mstalt="296985"]]
395	395
396	396
397		-Add the decoder from this link:
398	398
	513	+Add the decoder from this link:
399	399
	515	+[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	516	+
400	400	Save the change the uplink message will be parsed. As below:
401	401
402		-[[image:1664502676891-606.png]]
	519	+[[image:1664502676891-606.png||_mstalt="296673"]]
403	403
404	404
	522	+== 2.5 Integrate with Datacake ==
405	405
406		-== 2.4 Integrate with Datacake ==
407	407
408		-
409		-(((
410	410	After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
411		-)))
412	412
413		-(((
414	414	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]]
415		-)))
416	416
417	417
418		-[[image:1664502695771-538.png]]
	530	+[[image:1664502695771-538.png||_mstalt="297349"]]
419	419
420	420
	533	+== 2.6 Integrate with Tago ==
421	421
422		-== 2.5 Integrate with Tago ==
423	423
	536	+After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot.
424	424
425		-(((
426		-After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
427		-)))
428		-
429		-(((
430	430	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]]
431		-)))
432	432
433	433
434		-[[image:1664502715371-321.png]]
	541	+[[image:1664502715371-321.png||_mstalt="292162"]]
435	435
436	436
	544	+== 2.7  Datalog Feature ==
437	437
438		-== 2.6 Alarm Mode ==
439	439
	547	+total 273 entries,by default,
440	440
	549	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	550	+
	551	+Example use case.
	552	+
	553	+[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	554	+
	555	+
	556	+[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	557	+
	558	+
	559	+== 2.8 Alarm Mode ==
	560	+
	561	+
441	441	(((
442	442	User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
443	443	)))
...	...	@@ -444,15 +444,15 @@
444	444
445	445
446	446	(((
447		-Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
	568	+Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode.
448	448	)))
449	449
450	450
451	451	(((
452		-Two ways to exit alarm mode:
	573	+**Two ways to exit alarm mode:**
453	453	)))
454	454
455		-* Server send a downlink command to exit.
	576	+* Server sends a downlink command to exit.
456	456	* User fast press the RED button 10 times.
457	457
458	458	(((
...	...	@@ -460,23 +460,22 @@
460	460	)))
461	461
462	462
	584	+== 2.9 Transport Mode ==
463	463
464		-== 2.7 Sports Mode ==
465	465
	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.
466	466
467		-In Sports 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.
468	468
	590	+== 2.10 LED Status ==
469	469
470		-== 2.8 LED Status ==
471	471
472		-
473		-(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	593	+(% border="1.5" style="background-color:#ffffcc; width:500px" %)
474	474	|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
475	475	|(% 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
476	476	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
477	477	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
478	478	|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
479		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
	599	+|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
480	480	|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
481	481	|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
482	482	|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
...	...	@@ -484,12 +484,12 @@
484	484	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
485	485	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
486	486
487		-== 2.9 Button Function ==
	607	+== 2.11 Button Function ==
488	488
489	489
490	490	(% style="color:blue" %)**RESET button:**
491	491
492		-[[image:1664502835802-546.png]]
	612	+[[image:1664502835802-546.png||_mstalt="295061"]]
493	493
494	494	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
495	495
...	...	@@ -496,16 +496,16 @@
496	496
497	497	(% style="color:red" %)**RED button:**
498	498
499		-[[image:1664502854406-763.png]]
	619	+[[image:1664502854406-763.png||_mstalt="295568"]]
500	500
501	501
502		-(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
503		-|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
504		-|(% 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.6AlarmMode"]]
	622	+(% border="1" style="background-color:#ffffcc; width:510px" %)
	623	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
	624	+|(% 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"]]
505	505	|(% 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
506	506	|(% 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.
507	507
508		-== 2.10 USB Port Function ==
	628	+== 2.12 USB Port Function ==
509	509
510	510
511	511	The USB interface of TrackerD has below functions:
...	...	@@ -523,7 +523,6 @@
523	523	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
524	524
525	525
526		-
527	527	== 3.1 Access AT Command ==
528	528
529	529
...	...	@@ -530,27 +530,24 @@
530	530	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.
531	531
532	532
533		-[[image:1664502999401-486.png]]
	652	+[[image:1664502999401-486.png||_mstalt="296985"]]
534	534
535	535
536	536	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:
537	537
538	538
539		-[[image:1664503022490-662.png]]
	658	+[[image:1664503022490-662.png||_mstalt="293332"]]
540	540
541	541
	661	+[[image:1664503035713-500.png||_mstalt="291096"]]
542	542
543		-[[image:1664503035713-500.png]]
544	544
	664	+[[image:1664503047675-651.png||_mstalt="295386"]]
545	545
546	546
547		-[[image:1664503047675-651.png]]
548	548
549		-
550		-
551	551	== 3.2 Command Set ==
552	552
553		-
554	554	=== 3.2.1 Set Transmit Interval ===
555	555
556	556
...	...	@@ -568,7 +568,6 @@
568	568	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
569	569
570	570
571		-
572	572	=== 3.2.2 Set Alarm Packet transmission interval ===
573	573
574	574
...	...	@@ -586,25 +586,23 @@
586	586	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
587	587
588	588
	704	+=== 3.2.3 Set Transport Mode Packet transmission interval ===
589	589
590		-=== 3.2.3 Set Sports Mode Packet transmission interval ===
591	591
	707	+Set Transport Mode packet transmit interval
592	592
593		-Set sports packet transmit interval
594		-
595	595	* (% style="color:blue" %)**AT Command:**
596	596
597	597	(% style="color:#037691" %)**AT+MTDC=xx. **
598	598
599		-Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
	713	+Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
600	600
601	601
602	602	* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
603	603
604		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
	718	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
605	605
606	606
607		-
608	608	=== 3.2.4 Exit Alarm ===
609	609
610	610
...	...	@@ -617,7 +617,6 @@
617	617	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
618	618
619	619
620		-
621	621	=== 3.2.5 Disable/Enable LED flash ===
622	622
623	623
...	...	@@ -635,51 +635,69 @@
635	635	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
636	636
637	637
	750	+=== 3.2.6 Disable/Enable Transport Mode ===
638	638
639		-=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
640	640
	753	+Users can use this feature to enable/disable Transport Mode.
641	641
642		-User can use this feature to check and set thread hole of movement detect
643		-
644	644	* (% style="color:blue" %)**AT Command:**
645	645
646	646	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
647	647
648		-Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
	759	+Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
649	649
650	650
651	651	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
652	652
653		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
	764	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
654	654
655	655
656		-
657	657	=== 3.2.7 Set Positioning Mode ===
658	658
659	659
660		-SMOD define the how TrackerD scan and uplink data:
	770	+SMOD define how TrackerD scan and uplink data:
661	661
662	662
663	663	* (% style="color:blue" %)**AT Command:**
664	664
665		-(% style="color:#037691" %)**AT+SMOD=xx. **
	775	+(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
666	666
	777	+(% style="color:#037691" %)** aa:**
667	667
668		- **Example:**
	779	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
669	669
670		- AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
	781	+* (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
671	671
672		- AT+ SMOD =1,1    **~-~->**  GPS +BAT State
	783	+* (% style="color:red" %)**3: GPS/BLE Hybrid:                       **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
673	673
674		- AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
	785	+(% style="color:#037691" %)**bb:**
675	675
	787	+* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
676	676
677		-* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	789	+* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
678	678
679		-(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
	791	+(% style="color:#037691" %)**cc:   **
680	680
	793	+* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	794	+
	795	+* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
681	681
	797	+(% style="color:blue" %)**Example:**
682	682
	799	+ AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
	800	+
	801	+ AT+SMOD=1,1,0 ~-~->  GPS +BAT State
	802	+
	803	+ AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	804	+
	805	+ AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
	806	+
	807	+
	808	+* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	809	+
	810	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
	811	+
	812	+
683	683	=== 3.2.8 Set MAX GPS position time ===
684	684
685	685
...	...	@@ -686,7 +686,7 @@
686	686	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.
687	687
688	688
689		-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.
	819	+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.
690	690
691	691
692	692	* (% style="color:blue" %)**AT Command:**
...	...	@@ -693,7 +693,7 @@
693	693
694	694	(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
695	695
696		-Example:  AT+FTIME=150
	826	+**Example:**  AT+FTIME=150
697	697
698	698
699	699	* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
...	...	@@ -701,10 +701,9 @@
701	701	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
702	702
703	703
	834	+=== 3.2.9 Set PDOP value for GPS fix accuracy ===
704	704
705		-=== 3.3.9 Set PDOP value for GPS fix accuracy ===
706	706
707		-
708	708	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.
709	709
710	710
...	...	@@ -726,26 +726,108 @@
726	726
727	727
728	728
729		-Disable/Enable the confirmation mode
	858	+=== 3.2.10 Disable/Enable the confirmation mode ===
730	730
731	731	* (% style="color:blue" %)**AT Command:**
732	732
733		-(% style="color:#037691" %)**AT+CFM=xx. **
	862	+(% style="color:#037691" %)**AT+CFM=xx**
734	734
735	735
736	736	**~ Example:**
737	737
738		- AT+ CFM=0    **~-~->   ** Disable confirmation
	867	+ AT+CFM=0    **~-~->   ** Disable confirmation
739	739
740		- AT+ CFM=1    **~-~->  ** Enable confirmation
	869	+ AT+CFM=1    **~-~->  ** Enable confirmation
741	741
742	742
743	743	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
744	744
745		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
	874	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
746	746
747	747
	877	+=== 3.2.11  Auto Send None-ACK messages ===
748	748
	879	+
	880	+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.
	881	+
	882	+
	883	+* (% style="color:blue" %)**AT Command: AT+PNACKMD**
	884	+
	885	+The default factory setting is 0.
	886	+
	887	+
	888	+**Command Example Function Response:**
	889	+
	890	+(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
	891	+
	892	+
	893	+* (% style="color:blue" %)**Downlink Command: 0x34**
	894	+
	895	+Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
	896	+
	897	+
	898	+=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
	899	+
	900	+
	901	+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.
	902	+
	903	+(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
	904	+
	905	+(% style="color:blue" %)**AT Command:**
	906	+
	907	+ (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	908	+
	909	+ (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	910	+
	911	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
	912	+
	913	+Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
	914	+
	915	+
	916	+=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
	917	+
	918	+
	919	+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.
	920	+
	921	+(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
	922	+
	923	+(% style="color:blue" %)**AT Command:**
	924	+
	925	+ (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	926	+
	927	+ (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	928	+
	929	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
	930	+
	931	+Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
	932	+
	933	+
	934	+=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
	935	+
	936	+
	937	+Users can use this feature to enable/disable Information printing.
	938	+
	939	+(% style="color:blue" %)**AT Command:**
	940	+
	941	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
	942	+\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
	943	+
	944	+
	945	+=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	946	+
	947	+
	948	+The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	949	+
	950	+(% style="color:blue" %)**AT Command:**
	951	+
	952	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
	953	+
	954	+
	955	+(% style="color:blue" %)**Downlink Payload:0X24**
	956	+
	957	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
	958	+
	959	+
749	749	= 4. Setting for Different Scenarios =
750	750
751	751
...	...	@@ -752,7 +752,6 @@
752	752
753	753	= 5. Upload Firmware =
754	754
755		-
756	756	== 5.1 Firmware Change Log ==
757	757
758	758
...	...	@@ -759,7 +759,6 @@
759	759	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
760	760
761	761
762		-
763	763	== 5.2 How to upgrade firmware ==
764	764
765	765
...	...	@@ -780,40 +780,39 @@
780	780	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
781	781
782	782
783		-[[image:1664503563660-578.png]]
	992	+[[image:1664503563660-578.png||_mstalt="296777"]]
784	784
785	785
786		-[[image:1664503574618-659.png]]
	995	+[[image:1664503574618-659.png||_mstalt="297986"]]
787	787
788	788
	998	+
789	789	(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
790	790
791		-[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1001	+[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
792	792
793	793
794		-Users need to use below files:
	1004	+**Users need to use below files:**
795	795
796	796	boot_app0.bin @0e000
797	797
798		-ESP_LORA-eeprom-class.bin @ 0x10000
	1008	+US915.bin @ 0x10000(Select the bin file of the frequency band you need)
799	799
800	800
801		-[[image:1664503593459-435.png]]
	1011	+[[image:image-20221118105220-2.png||_mstalt="426608"]]
802	802
803	803
804	804
805	805	After upgrade finish, it will show finish as below:
806	806
807		-[[image:1664503611848-385.png]]
	1017	+[[image:image-20221118105402-4.png||_mstalt="427986"]]
808	808
809	809
810	810
811	811	= 6. Developer Guide =
812	812
813		-
814	814	== 6.1 Compile Source Code ==
815	815
816		-
817	817	=== 6.1.1 Set up ARDUINO compile environment ===
818	818
819	819
...	...	@@ -822,48 +822,57 @@
822	822	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]]
823	823
824	824
825		-[[image:1664503635019-941.png]]
	1033	+[[image:1664503635019-941.png||_mstalt="294658"]]
826	826
827	827
	1036	+
828	828	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
829	829
830		-[[image:1664503715811-892.png]]
	1039	+[[image:1664503715811-892.png||_mstalt="295698"]]
831	831
832	832
	1042	+(% 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.
833	833
	1044	+[[image:image-20221024105643-1.png||_mstalt="428129"]]
	1045	+
	1046	+**~ Figure1**
	1047	+
	1048	+
	1049	+[[image:image-20221024105643-2.png||_mstalt="428493"]]
	1050	+
	1051	+ **Figure2**
	1052	+
	1053	+
834	834	* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
835	835
836	836	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
837	837
838	838
839		-[[image:1664503752288-974.png]]
	1059	+[[image:1664503752288-974.png||_mstalt="298194"]]
840	840
841	841
842		-
843	843	== 6.2 Source Code ==
844	844
845	845
846	846	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
847	847
848		-[[image:1664503794261-827.png]]
	1067	+[[image:1664503794261-827.png||_mstalt="296387"]]
849	849
850	850
851	851
852	852	* (% style="color:blue" %)**Click to upload**
853	853
854		-[[image:1664503808294-336.png]]
	1073	+[[image:1664503808294-336.png||_mstalt="295711"]]
855	855
856	856
857	857
858	858	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
859	859
860		-[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
	1079	+[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
861	861
862	862
863		-
864	864	= 7.  FAQ =
865	865
866		-
867	867	== 7.1 How to change the LoRa Frequency Bands/Region? ==
868	868
869	869
...	...	@@ -870,11 +870,10 @@
870	870	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
871	871
872	872
873		-
874	874	== 7.2 What is the pin mapping for the USB program cable? ==
875	875
876	876
877		-[[image:1664499635206-262.png]]
	1093	+[[image:1664499635206-262.png||_mstalt="295360"]]
878	878
879	879
880	880
...	...	@@ -889,46 +889,250 @@
889	889	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
890	890	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
891	891
	1108	+== 7.3 Notes on using different serial port tools for TrackerD ==
892	892
893		-= 8.  Order Info =
	1110	+=== 7.3.1  Serial port utility ===
894	894
895	895
	1113	+Serial port utility requires you to automatically add data streams.
	1114	+
	1115	+Need to adjust the data stream to RTS/CTS on physical restart.
	1116	+
	1117	+(% class="wikigeneratedid" %)
	1118	+[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1119	+
	1120	+
	1121	+
	1122	+When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1123	+
	1124	+[[image:image-20221102140638-2.png||_mstalt="428727"]]
	1125	+
	1126	+
	1127	+=== 7.3.2  SecureCRT ===
	1128	+
	1129	+
	1130	+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.
	1131	+
	1132	+
	1133	+[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1134	+
	1135	+
	1136	+[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1137	+
	1138	+
	1139	+=== 7.3.3  PUTTY ===
	1140	+
	1141	+
	1142	+[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1143	+
	1144	+
	1145	+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.
	1146	+
	1147	+
	1148	+[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1149	+
	1150	+
	1151	+== 7.4 How to modify source code to compile different frequency band bin file? ==
	1152	+
	1153	+
	1154	+(% class="box infomessage" %)
	1155	+(((
	1156	+(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
	1157	+See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
	1158	+)))
	1159	+
	1160	+**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
	1161	+
	1162	+
	1163	+[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
	1164	+
	1165	+
	1166	+
	1167	+**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
	1168	+
	1169	+
	1170	+[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1171	+
	1172	+
	1173	+
	1174	+**3. Compile the AS923_JP band, please refer to the intention shown**
	1175	+
	1176	+
	1177	+[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
	1178	+
	1179	+
	1180	+
	1181	+**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.**
	1182	+
	1183	+
	1184	+[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
	1185	+
	1186	+
	1187	+[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
	1188	+
	1189	+
	1190	+= 8  Trouble Shooting =
	1191	+
	1192	+== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
	1193	+
	1194	+
	1195	+(((
	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
	1197	+)))
	1198	+
	1199	+
	1200	+== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
	1201	+
	1202	+
	1203	+(((
	1204	+ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
	1205	+)))
	1206	+
	1207	+
	1208	+== 8.3  Problem after Upgrading Firmware ==
	1209	+
	1210	+=== 8.3.1 Continue Restart after upgrading ===
	1211	+
	1212	+
	1213	+(((
	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
	1215	+)))
	1216	+
	1217	+
	1218	+[[image:image-20221118105249-3.png||_mstalt="430664"]]
	1219	+
	1220	+
	1221	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1222	+
	1223	+
	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
	1225	+
	1226	+
	1227	+=== 8.3.3 "flash read err" after upgrade firmware ===
	1228	+
	1229	+Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
	1230	+
	1231	+[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
	1232	+
	1233	+
	1234	+User need to upgrade again with below four files to solve this issue.
	1235	+
	1236	+ [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
	1237	+
	1238	+ **Figure 2**
	1239	+
	1240	+
	1241	+=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
	1242	+
	1243	+User might erase the entire flash include keys and default settings which cause this issue.
	1244	+
	1245	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
	1246	+
	1247	+[[image:image-20221122100004-3.png||_mstalt="424242"]]
	1248	+
	1249	+Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
	1250	+
	1251	+After AT+FDR. please set
	1252	+
	1253	+* AT+PDOP=7
	1254	+* AT+FTIME=180000
	1255	+
	1256	+Example:
	1257	+
	1258	+AT+PDOP=7.00
	1259	+
	1260	+AT+FTIME=180
	1261	+
	1262	+AT+DEUI=70B3D57ED0053981
	1263	+
	1264	+AT+APPEUI=D23345667BCBCCAF
	1265	+
	1266	+AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1267	+
	1268	+AT+DADDR=260b4dce    ( no need for OTAA)
	1269	+
	1270	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
	1271	+
	1272	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
	1273	+
	1274	+
	1275	+
	1276	+=== 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 ===
	1277	+
	1278	+
	1279	+[[image:image-20221122100004-4.png||_mstalt="424606"]]
	1280	+
	1281	+
	1282	+== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
	1283	+
	1284	+
	1285	+Please download version 1.4.2 again
	1286	+
	1287	+
	1288	+== 8.5  How to deal with unsuccessful GPS positioning? ==
	1289	+
	1290	+
	1291	+1） Make Sure the device is in Open Area where can see the sky.
	1292	+
	1293	+2)  Set PDOP to a higher value.
	1294	+
	1295	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1296	+
	1297	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1298	+
	1299	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1300	+
	1301	+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
	1302	+
	1303	+
	1304	+= 9.  Order Info =
	1305	+
	1306	+
896	896	Part Number: (% style="color:blue" %)**TrackerD-XXX**
897	897
898	898	(% style="color:blue" %)**XXX**(%%): The default frequency band
899	899
900	900	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
	1312	+
901	901	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
	1314	+
902	902	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
	1316	+
903	903	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
	1318	+
904	904	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
	1320	+
905	905	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
	1322	+
906	906	* (% style="color:red" %)**US915**(%%): Default frequency band US915
907	907
908		-= 9.  Packing Info =
	1325	+= 10.  Packing Info =
909	909
910	910
911	911	(% style="color:#037691" %)**Package Includes**:
912	912
913	913	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1331	+
914	914	* USB recharge & program cable x 1
915	915
916	916	(% style="color:#037691" %)**Dimensions and Weight**:
917	917
918		-* Device Size: 85 x 48 x 15 cm
	1336	+* Device Size: 85 x 48 x 15 mm
	1337	+
919	919	* Weight: 50g
920	920
921		-= 10. Support =
	1340	+= 11. Support =
922	922
923	923
924	924	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
	1344	+
925	925	* 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]].
926	926
927		-= 11.  Reference =
	1347	+= 12.  Reference =
928	928
929	929
930	930	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1351	+
931	931	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
932		-* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
933	933
934		-
	1354	+* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]

1665301570342-765.png

Author

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

Size

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

Content

1665301636888-168.png

Author

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

Size

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

Content

1665301687277-443.png

Author

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

Size

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

Content

1665301786397-168.png

Author

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

Size

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

Content

1667288597595-714.png

Author

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

Size

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

Content

image-20221009160220-1.png

Author

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

Size

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

Content

image-20221009160309-2.png

Author

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

Size

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

Content

image-20221009234629-1.png

Author

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

Size

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

Content

image-20221009234703-2.png

Author

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

Size

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

Content

image-20221024105643-1.png

Author

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

Size

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

Content

image-20221024105643-2.png

Author

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

Size

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

Content

image-20221102140621-1.png

Author

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

Size

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

Content

image-20221102140638-2.png

Author

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

Size

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

Content

image-20221102140704-3.png

Author

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

Size

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

Content

image-20221102140712-4.png

Author

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

Size

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

Content

image-20221102140748-5.png

Author

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

Size

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

Content

image-20221102140801-6.png

Author

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

Size

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

Content

image-20221107145243-1.png

Author

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

Size

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

Content

image-20221116111844-1.png

Author

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

Size

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

Content

image-20221116111844-2.png

Author

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

Size

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

Content

image-20221116111844-3.png

Author

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

Size

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

Content

image-20221116111844-4.png

Author

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

Size

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

Content

image-20221116111844-5.png

Author

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

Size

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

Content

image-20221118104359-1.png

Author

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

Size

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

Content

image-20221118105220-2.png

Author

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

Size

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

Content

image-20221118105249-3.png

Author

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

Size

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

Content

image-20221118105402-4.png

Author

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

Size

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

Content

image-20221122100004-1.png

Author

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

Size

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

Content

image-20221122100004-2.png

Author

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

Size

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

Content

image-20221122100004-3.png

Author

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

Size

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

Content

image-20221122100004-4.png

Author

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

Size

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

Content