Changes for page TrackerD -- LoRaWAN Tracker User Manual

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 33 added, 0 removed)
  • 1665301570342-765.png
  • 1665301636888-168.png
  • 1665301687277-443.png
  • 1665301786397-168.png
  • 1667288597595-714.png
  • image-20221006181316-1.png
  • image-20221006181357-2.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.Xiaoling
	1	+XWiki.Edwin

Content

...	...	@@ -14,7 +14,6 @@
14	14
15	15	= 1.  Introduction =
16	16
17		-
18	18	== 1.1  What is TrackerD ==
19	19
20	20
...	...	@@ -46,7 +46,6 @@
46	46	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47	47
48	48
49		-
50	50	== 1.2 Specifications ==
51	51
52	52
...	...	@@ -61,13 +61,11 @@
61	61	* EEPROM: 520 KB
62	62	* Clock Speed: 32Mhz
63	63
64		-
65	65	(% style="color:blue" %)**Common DC Characteristics:**
66	66
67	67	* Supply Voltage: 5V via USB port or Internal li-on battery
68	68	* Operating Temperature: -40 ~~ 60°C
69	69
70		-
71	71	(% style="color:blue" %)**LoRa Spec:**
72	72
73	73	* Frequency Range,
...	...	@@ -89,12 +89,10 @@
89	89	* Packet engine up to 256 bytes with CRC.
90	90	* LoRaWAN 1.0.3 Specification
91	91
92		-
93	93	(% style="color:blue" %)**Battery:**
94	94
95	95	* 1000mA Li-on Battery power (for model TrackerD)
96	96
97		-
98	98	(% style="color:blue" %)**Power Consumption**
99	99
100	100	* Sleeping Mode: 200uA
...	...	@@ -102,7 +102,6 @@
102	102	* Tracking: max: 38mA
103	103
104	104
105		-
106	106	== 1.3  Features ==
107	107
108	108
...	...	@@ -109,7 +109,7 @@
109	109	* LoRaWAN 1.0.3 Class A
110	110	* ESP32 PICO D4
111	111	* SX1276/78 Wireless Chip
112		-** Arduino IDE Compatible
	105	+* Arduino IDE Compatible
113	113	* Open source hardware / software
114	114	* Regular/ Real-time GPS,BLE,WIFI tracking
115	115	* Built-in3 axis accelerometer (LIS3DH)
...	...	@@ -122,7 +122,6 @@
122	122	* Datalog
123	123
124	124
125		-
126	126	== 1.4  Applications ==
127	127
128	128
...	...	@@ -130,10 +130,8 @@
130	130	* Human tracking
131	131
132	132
	125	+= 2.  Use TrackerD =
133	133
134		-= 2.1 Use TrackerD =
135		-
136		-
137	137	== 2.1 How it works? ==
138	138
139	139
...	...	@@ -140,7 +140,6 @@
140	140	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.
141	141
142	142
143		-
144	144	== 2.2 Quick guide to connect to LoRaWAN server ==
145	145
146	146
...	...	@@ -182,53 +182,142 @@
182	182	**__Add APP KEY and DEV EUI:__**
183	183
184	184
185		-[[image:1664501784668-703.png]]
	174	+[[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"]]
186	186
187	187
188	188
	178	+(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
189	189
190		-(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
	180	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
191	191
	182	+[[image:1664502835802-546.png]]
192	192
	184	+
193	193	(% 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.
194	194
195	195
196		-(% style="color:blue" %)**Positioning Mode(SMOD):**
	188	+== 2.3  Positioning Mode(SMOD) ==
197	197
198		-* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
199		-* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
200		-* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
201	201
202		-User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
	191	+Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
203	203
	193	+* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
	194	+* (% 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.
	195	+* (% 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.
204	204
	197	+Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
205	205
206		-== 2.3 Uplink Payload ==
207	207
	200	+== 2.4  Uplink Payload ==
208	208
209		-=== 2.3.1 Uplink FPORT~=5, Device Status ===
	202	+=== 2.4.1 Uplink FPORT~=5, Device Status ===
210	210
211	211
	205	+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.
212	212
213		-=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
	207	+Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
214	214
215	215
216		-The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
	210	+(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
	211	+|=(% 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
	212	+|=(% 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
	214	+[[image:1665301570342-765.png]]
218	218
219		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
220		-|=(% scope="row" style="width: 50px;" %)(((
	216	+
	217	+(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
	218	+
	219	+(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
	220	+
	221	+(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
	222	+
	223	+(% style="color:#037691" %)**Frequency Band**:
	224	+
	225	+*0x01: EU868
	226	+
	227	+*0x02: US915
	228	+
	229	+*0x03: IN865
	230	+
	231	+*0x04: AU915
	232	+
	233	+*0x05: KZ865
	234	+
	235	+*0x06: RU864
	236	+
	237	+*0x07: AS923
	238	+
	239	+*0x08: AS923-1
	240	+
	241	+*0x09: AS923-2
	242	+
	243	+*0x0a: AS923-3
	244	+
	245	+Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
	246	+
	247	+(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
	248	+
	249	+
	250	+(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
	251	+
	252	+Use can also get the Device Status uplink through the downlink command:
	253	+
	254	+
	255	+(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
	256	+
	257	+(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
	258	+|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
	259	+|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
	260	+
	261	+(% style="color:blue" %)** SMOD：**
	262	+
	263	+(% style="color:red" %)** 1 :** (%%) GPS ONLY
	264	+
	265	+(% style="color:red" %)** 2 :** (%%) BLE ONLY
	266	+
	267	+(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
	268	+
	269	+
	270	+(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
	271	+
	272	+(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
	273	+
	274	+(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
	275	+
	276	+
	277	+(% style="color:blue" %)** BLE_Settings:**
	278	+
	279	+(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
	280	+
	281	+(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)
	282	+
	283	+
	284	+(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
	285	+
	286	+(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	287	+|=(% 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
	288	+|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
	289	+
	290	+
	291	+=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
	292	+
	293	+
	294	+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,
	295	+
	296	+
	297	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	298	+|=(% scope="row" style="width: 60px;" %)(((
221	221	**Size(bytes)**
222		-)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
223		-2(optional)
224		-)))|(% style="width:87px" %)(((
225		-2(optional)
	300	+)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
	301	+2
	302	+)))|(% style="width:30px" %)(((
	303	+2
226	226	)))
227	227	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
228	228	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
229		-)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
	307	+)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
230	230
231		-[[image:1664501958445-288.png]]
	309	+[[image:1665301636888-168.png]]
232	232
233	233
234	234	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
...	...	@@ -240,9 +240,9 @@
240	240
241	241	==== (% style="color:blue" %)**FLAG:**(%%) ====
242	242
243		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
244		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
245		-|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version
	321	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	322	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
	323	+|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
246	246
247	247	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
248	248
...	...	@@ -252,23 +252,18 @@
252	252	* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
253	253	* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
254	254
255		-
256		-
257	257	(% style="color:red" %)**Important note:**
258	258
259	259	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.
260	260
261		-2.  In firmware version v1.5, Roll & Pitch is disabled by default.
	337	+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:
262	262
263		-3.  When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
264	264
265		-
266	266	[[image:1664502116362-706.png]]
267	267
268	268
	343	+3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
269	269
270		-4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
271		-
272	272	[[image:1664502166010-515.png]]
273	273
274	274
...	...	@@ -275,18 +275,17 @@
275	275
276	276	==== (% style="color:blue" %)**Alarm:**(%%) ====
277	277
278		-Example:  0x4B & 0x40 >> 6 = 0x01
	351	+**Example: ** 0x4B & 0x40 >> 6 = 0x01
279	279
280	280
281	281	==== (% style="color:blue" %)**BAT:**(%%) ====
282	282
283		-Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
	356	+**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
284	284
285	285	(((
286		-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: \
	359	+The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
287	287	)))
288	288
289		-
290	290	* > 4.0v :  80% ~~ 100%
291	291	* 3.85v ~~3.99v:  60% ~~ 80%
292	292	* 3.70v ~~ 3.84v:  40% ~~ 60%
...	...	@@ -294,17 +294,33 @@
294	294	* < 3.39v:  0~~20%
295	295
296	296
	369	+==== (% style="color:blue" %)**MOD:**(%%) ====
	370	+
	371	+**Example: ** (0x60>>6) & 0x3f =1
	372	+
	373	+**Set the format of GPS data uplink link：**
	374	+
	375	+(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
	376	+(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
	377	+
	378	+
	379	+**Set the format of BLE data uplink link：**
	380	+
	381	+(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
	382	+
	383	+
297	297	==== (% style="color:blue" %)**LON:**(%%) ====
298	298
299		-
	386	+**Example:** (0x60>>5) & 0x01=1.
	387	+
300	300	Enable/Disable LED activity for uplink
301	301
302	302	(((
303		-0x00:  Disable LED indicator.
	391	+(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
304	304	)))
305	305
306	306	(((
307		-0x01:  Enable LED indicator (Default Value)
	395	+(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
308	308	)))
309	309
310	310
...	...	@@ -318,16 +318,55 @@
318	318	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
319	319
320	320
	409	+=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
321	321
322		-=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
323	323
	412	+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)
324	324
325	325
326		-=== 2.3.4 BLE positioning Payload(Fport2) ===
	415	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
	416	+|=(% scope="row" style="width: 60px;" %)(((
	417	+**Size(bytes)**
	418	+)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
	419	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	420	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	421	+)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
327	327
	423	+(% class="wikigeneratedid" %)
	424	+[[image:1665301687277-443.png]]
328	328
329		-Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
330	330
	427	+=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
	428	+
	429	+
	430	+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.
	431	+
	432	+
	433	+(% style="color:red" %)**Note for this mode:**
	434	+
	435	+* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
	436	+* 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.
	437	+* 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
	438	+
	439	+The payload is 15 bytes, as below.
	440	+
	441	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	442	+|=(% scope="row" %)(((
	443	+**Size(bytes)**
	444	+)))|4|4|2|1|1|1|1|1
	445	+|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
	446	+
	447	+[[image:image-20221009160309-2.png]]
	448	+
	449	+
	450	+=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
	451	+
	452	+
	453	+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.
	454	+
	455	+User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
	456	+
	457	+
331	331	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
332	332	|=(% scope="row" style="width: 60px;" %)(((
333	333	**Size(bytes)**
...	...	@@ -344,25 +344,46 @@
344	344	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
345	345	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
346	346
347		-
348	348	[[image:1664502425687-834.png]]
349	349
350	350
351		-* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
	477	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
352	352	* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
353	353	* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
354	354	* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
355		-* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
	481	+* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
356	356	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
357	357	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
358	358
359	359
	486	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
360	360
361		-=== 2.3.5 Add Payload format in TTN V3 ===
362	362
	489	+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.
363	363
364		-In TTN V3, use can add a custom payload so it shows friendly.
365	365
	492	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	493	+|=(% scope="row" style="width: 60px;" %)(((
	494	+**Size(bytes)**
	495	+)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
	496	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
	497	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	498	+)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
	499	+
	500	+(% class="wikigeneratedid" %)
	501	+[[image:1667288597595-714.png||height="212" width="1151"]]
	502	+
	503	+
	504	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	505	+* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
	506	+* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
	507	+
	508	+
	509	+=== 2.4.7  Add Payload format in TTN V3 ===
	510	+
	511	+
	512	+In TTN V3, user can add a custom payload so it shows friendly.
	513	+
366	366	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
367	367
368	368
...	...	@@ -369,50 +369,56 @@
369	369	[[image:1664502649601-895.png]]
370	370
371	371
372		-Add the decoder from this link:
373	373
	521	+Add the decoder from this link:
374	374
	523	+[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	524	+
375	375	Save the change the uplink message will be parsed. As below:
376	376
377	377	[[image:1664502676891-606.png]]
378	378
379	379
	530	+== 2.5 Integrate with Datacake ==
380	380
381		-== 2.4 Integrate with Datacake ==
382	382
383		-
384		-(((
385	385	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.
386		-)))
387	387
388		-(((
389	389	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]]
390		-)))
391	391
392	392
393	393	[[image:1664502695771-538.png]]
394	394
395	395
	541	+== 2.6 Integrate with Tago ==
396	396
397		-== 2.5 Integrate with Tago ==
398	398
	544	+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.
399	399
400		-(((
401		-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.
402		-)))
403		-
404		-(((
405	405	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]]
406		-)))
407	407
408	408
409	409	[[image:1664502715371-321.png]]
410	410
411	411
	552	+== 2.7  Datalog Feature ==
412	412
413		-== 2.6 Alarm Mode ==
414	414
	555	+total 273 entries,by default,
415	415
	557	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	558	+
	559	+Example use case.
	560	+
	561	+[[image:image-20221009234703-2.png||height="328" width="899"]]
	562	+
	563	+
	564	+[[image:image-20221009234629-1.png||height="390" width="577"]]
	565	+
	566	+
	567	+== 2.8 Alarm Mode ==
	568	+
	569	+
416	416	(((
417	417	User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
418	418	)))
...	...	@@ -419,38 +419,38 @@
419	419
420	420
421	421	(((
422		-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.
	576	+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.
423	423	)))
424	424
425	425
426	426	(((
427		-Two ways to exit alarm mode:
	581	+**Two ways to exit alarm mode:**
428	428	)))
429	429
430		-* Server send a downlink command to exit.
	584	+* Server sends a downlink command to exit.
431	431	* User fast press the RED button 10 times.
432	432
433		-
434	434	(((
435	435	When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
436	436	)))
437	437
438	438
	592	+== 2.9 Transport Mode ==
439	439
440		-== 2.7 Sports Mode ==
441	441
	595	+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.
442	442
443	443
444		-== 2.8 LED Status ==
	598	+== 2.10 LED Status ==
445	445
446	446
447		-(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	601	+(% border="1.5" style="background-color:#ffffcc; width:500px" %)
448	448	|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
449	449	|(% 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
450	450	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
451	451	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
452	452	|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
453		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
	607	+|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
454	454	|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
455	455	|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
456	456	|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
...	...	@@ -459,10 +459,9 @@
459	459	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
460	460
461	461
	616	+== 2.11 Button Function ==
462	462
463		-== 2.9 Button Function ==
464	464
465		-
466	466	(% style="color:blue" %)**RESET button:**
467	467
468	468	[[image:1664502835802-546.png]]
...	...	@@ -475,17 +475,16 @@
475	475	[[image:1664502854406-763.png]]
476	476
477	477
478		-(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
479		-|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
480		-|(% 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"]]
	631	+(% border="1" style="background-color:#ffffcc; width:510px" %)
	632	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
	633	+|(% 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"]]
481	481	|(% 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
482	482	|(% 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.
483	483
484	484
	638	+== 2.12 USB Port Function ==
485	485
486		-== 2.10 USB Port Function ==
487	487
488		-
489	489	The USB interface of TrackerD has below functions:
490	490
491	491	* Power on the device
...	...	@@ -494,8 +494,6 @@
494	494	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
495	495
496	496
497		-
498		-
499	499	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
500	500
501	501
...	...	@@ -504,7 +504,6 @@
504	504	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
505	505
506	506
507		-
508	508	== 3.1 Access AT Command ==
509	509
510	510
...	...	@@ -520,11 +520,9 @@
520	520	[[image:1664503022490-662.png]]
521	521
522	522
523		-
524	524	[[image:1664503035713-500.png]]
525	525
526	526
527		-
528	528	[[image:1664503047675-651.png]]
529	529
530	530
...	...	@@ -531,7 +531,6 @@
531	531
532	532	== 3.2 Command Set ==
533	533
534		-
535	535	=== 3.2.1 Set Transmit Interval ===
536	536
537	537
...	...	@@ -549,7 +549,6 @@
549	549	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
550	550
551	551
552		-
553	553	=== 3.2.2 Set Alarm Packet transmission interval ===
554	554
555	555
...	...	@@ -567,25 +567,23 @@
567	567	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
568	568
569	569
	715	+=== 3.2.3 Set Transport Mode Packet transmission interval ===
570	570
571		-=== 3.2.3 Set Sports Mode Packet transmission interval ===
572	572
	718	+Set Transport Mode packet transmit interval
573	573
574		-Set sports packet transmit interval
575		-
576	576	* (% style="color:blue" %)**AT Command:**
577	577
578	578	(% style="color:#037691" %)**AT+MTDC=xx. **
579	579
580		-Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
	724	+Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
581	581
582	582
583	583	* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
584	584
585		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
	729	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
586	586
587	587
588		-
589	589	=== 3.2.4 Exit Alarm ===
590	590
591	591
...	...	@@ -598,7 +598,6 @@
598	598	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
599	599
600	600
601		-
602	602	=== 3.2.5 Disable/Enable LED flash ===
603	603
604	604
...	...	@@ -616,60 +616,69 @@
616	616	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
617	617
618	618
	761	+=== 3.2.6 Disable/Enable Transport Mode ===
619	619
620		-=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
621	621
	764	+Users can use this feature to enable/disable Transport Mode.
622	622
623		-User can use this feature to check and set thread hole of movement detect
624		-
625	625	* (% style="color:blue" %)**AT Command:**
626	626
627	627	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
628	628
629		-Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
	770	+Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
630	630
631	631
632	632	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
633	633
634		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
	775	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
635	635
636	636
637		-
638	638	=== 3.2.7 Set Positioning Mode ===
639	639
640	640
641		-SMOD define the how TrackerD scan and uplink date.
	781	+SMOD define how TrackerD scan and uplink data:
642	642
643		-GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
644	644
645		-BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
	784	+* (% style="color:blue" %)**AT Command:**
646	646
647		-GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
	786	+(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
648	648
649		-运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
	788	+(% style="color:#037691" %)** aa:**
650	650
	790	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
651	651
	792	+* (% 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.
652	652
653		-* (% style="color:blue" %)**AT Command:**
	794	+* (% 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.
654	654
655		-(% style="color:#037691" %)**AT+SMOD=xx. **
	796	+(% style="color:#037691" %)**bb:**
656	656
	798	+* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
657	657
658		- **Example:**
	800	+* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
659	659
660		- AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
	802	+(% style="color:#037691" %)**cc:   **
661	661
662		- AT+ SMOD =1,1    **~-~->**  GPS +BAT State
	804	+* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	805	+
	806	+* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
663	663
664		- AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
	808	+(% style="color:blue" %)**Example:**
665	665
	810	+ AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
666	666
667		-* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	812	+ AT+SMOD=1,1,0 ~-~->  GPS +BAT State
668	668
669		-(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
	814	+ AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
670	670
	816	+ AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
671	671
672	672
	819	+* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	820	+
	821	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
	822	+
	823	+
673	673	=== 3.2.8 Set MAX GPS position time ===
674	674
675	675
...	...	@@ -676,7 +676,7 @@
676	676	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.
677	677
678	678
679		-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.
	830	+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.
680	680
681	681
682	682	* (% style="color:blue" %)**AT Command:**
...	...	@@ -683,7 +683,7 @@
683	683
684	684	(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
685	685
686		-Example:  AT+FTIME=150
	837	+**Example:**  AT+FTIME=150
687	687
688	688
689	689	* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
...	...	@@ -691,10 +691,9 @@
691	691	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
692	692
693	693
	845	+=== 3.2.9 Set PDOP value for GPS fix accuracy ===
694	694
695		-=== 3.3.9 Set PDOP value for GPS fix accuracy ===
696	696
697		-
698	698	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.
699	699
700	700
...	...	@@ -716,26 +716,108 @@
716	716
717	717
718	718
719		-Disable/Enable the confirmation mode
	869	+**Disable/Enable the confirmation mode**
720	720
721	721	* (% style="color:blue" %)**AT Command:**
722	722
723		-(% style="color:#037691" %)**AT+CFM=xx. **
	873	+(% style="color:#037691" %)**AT+CFM=xx**
724	724
725	725
726	726	**~ Example:**
727	727
728		- AT+ CFM=0    **~-~->   ** Disable confirmation
	878	+ AT+CFM=0    **~-~->   ** Disable confirmation
729	729
730		- AT+ CFM=1    **~-~->  ** Enable confirmation
	880	+ AT+CFM=1    **~-~->  ** Enable confirmation
731	731
732	732
733	733	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
734	734
735		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
	885	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
736	736
737	737
	888	+=== 3.2.10  Auto Send None-ACK messages ===
738	738
	890	+
	891	+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.
	892	+
	893	+
	894	+* (% style="color:blue" %)**AT Command: AT+PNACKMD**
	895	+
	896	+The default factory setting is 0.
	897	+
	898	+
	899	+**Command Example Function Response:**
	900	+
	901	+(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
	902	+
	903	+
	904	+* (% style="color:blue" %)**Downlink Command: 0x34**
	905	+
	906	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
	907	+
	908	+
	909	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
	910	+
	911	+
	912	+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.
	913	+
	914	+(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
	915	+
	916	+(% style="color:blue" %)**AT Command:**
	917	+
	918	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	919	+
	920	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	921	+
	922	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
	923	+
	924	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
	925	+
	926	+
	927	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
	928	+
	929	+
	930	+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.
	931	+
	932	+(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
	933	+
	934	+(% style="color:blue" %)**AT Command:**
	935	+
	936	+ (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	937	+
	938	+ (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	939	+
	940	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
	941	+
	942	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
	943	+
	944	+
	945	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
	946	+
	947	+
	948	+Users can use this feature to enable/disable Information printing.
	949	+
	950	+(% style="color:blue" %)**AT Command:**
	951	+
	952	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
	953	+\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
	954	+
	955	+
	956	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	957	+
	958	+
	959	+The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	960	+
	961	+(% style="color:blue" %)**AT Command:**
	962	+
	963	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
	964	+
	965	+
	966	+(% style="color:blue" %)**Downlink Payload:0X24**
	967	+
	968	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
	969	+
	970	+
739	739	= 4. Setting for Different Scenarios =
740	740
741	741
...	...	@@ -742,7 +742,6 @@
742	742
743	743	= 5. Upload Firmware =
744	744
745		-
746	746	== 5.1 Firmware Change Log ==
747	747
748	748
...	...	@@ -749,7 +749,6 @@
749	749	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
750	750
751	751
752		-
753	753	== 5.2 How to upgrade firmware ==
754	754
755	755
...	...	@@ -776,34 +776,33 @@
776	776	[[image:1664503574618-659.png]]
777	777
778	778
	1009	+
779	779	(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
780	780
781		-[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1012	+[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
782	782
783	783
784		-Users need to use below files:
	1015	+**Users need to use below files:**
785	785
786	786	boot_app0.bin @0e000
787	787
788		-ESP_LORA-eeprom-class.bin @ 0x10000
	1019	+US915.bin @ 0x10000(Select the bin file of the frequency band you need)
789	789
790	790
791		-[[image:1664503593459-435.png]]
	1022	+[[image:image-20221118105220-2.png]]
792	792
793	793
794	794
795	795	After upgrade finish, it will show finish as below:
796	796
797		-[[image:1664503611848-385.png]]
	1028	+[[image:image-20221118105402-4.png]]
798	798
799	799
800	800
801	801	= 6. Developer Guide =
802	802
803		-
804	804	== 6.1 Compile Source Code ==
805	805
806		-
807	807	=== 6.1.1 Set up ARDUINO compile environment ===
808	808
809	809
...	...	@@ -815,12 +815,24 @@
815	815	[[image:1664503635019-941.png]]
816	816
817	817
	1047	+
818	818	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
819	819
820	820	[[image:1664503715811-892.png]]
821	821
822	822
	1053	+(% 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.
823	823
	1055	+[[image:image-20221024105643-1.png]]
	1056	+
	1057	+**~ Figure1**
	1058	+
	1059	+
	1060	+[[image:image-20221024105643-2.png]]
	1061	+
	1062	+ **Figure2**
	1063	+
	1064	+
824	824	* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
825	825
826	826	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
...	...	@@ -829,7 +829,6 @@
829	829	[[image:1664503752288-974.png]]
830	830
831	831
832		-
833	833	== 6.2 Source Code ==
834	834
835	835
...	...	@@ -850,10 +850,8 @@
850	850	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
851	851
852	852
853		-
854	854	= 7.  FAQ =
855	855
856		-
857	857	== 7.1 How to change the LoRa Frequency Bands/Region? ==
858	858
859	859
...	...	@@ -860,7 +860,6 @@
860	860	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
861	861
862	862
863		-
864	864	== 7.2 What is the pin mapping for the USB program cable? ==
865	865
866	866
...	...	@@ -880,56 +880,245 @@
880	880	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
881	881
882	882
	1120	+== 7.3 Notes on using different serial port tools for TrackerD ==
883	883
884		-= 8.  Order Info =
	1122	+=== 7.3.1  Serial port utility ===
885	885
886	886
	1125	+Serial port utility requires you to automatically add data streams.
	1126	+
	1127	+Need to adjust the data stream to RTS/CTS on physical restart.
	1128	+
	1129	+(% class="wikigeneratedid" %)
	1130	+[[image:image-20221102140621-1.png]]
	1131	+
	1132	+
	1133	+
	1134	+When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1135	+
	1136	+[[image:image-20221102140638-2.png]]
	1137	+
	1138	+
	1139	+=== 7.3.2  SecureCRT ===
	1140	+
	1141	+
	1142	+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.
	1143	+
	1144	+
	1145	+[[image:image-20221102140704-3.png]]
	1146	+
	1147	+
	1148	+[[image:image-20221102140712-4.png]]
	1149	+
	1150	+
	1151	+=== 7.3.3  PUTTY ===
	1152	+
	1153	+
	1154	+[[image:image-20221102140748-5.png]]
	1155	+
	1156	+
	1157	+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.
	1158	+
	1159	+
	1160	+[[image:image-20221102140801-6.png]]
	1161	+
	1162	+
	1163	+== 7.4 How to modify source code to compile different frequency band bin file? ==
	1164	+
	1165	+
	1166	+(% class="box infomessage" %)
	1167	+(((
	1168	+(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
	1169	+See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
	1170	+)))
	1171	+
	1172	+**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
	1173	+
	1174	+
	1175	+[[image:image-20221116111844-1.png||height="227" width="782"]]
	1176	+
	1177	+
	1178	+
	1179	+**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
	1180	+
	1181	+
	1182	+[[image:image-20221116111844-2.png||height="262" width="781"]]
	1183	+
	1184	+
	1185	+
	1186	+**3. Compile the AS923_JP band, please refer to the intention shown**
	1187	+
	1188	+
	1189	+[[image:image-20221116111844-3.png||height="338" width="746"]]
	1190	+
	1191	+
	1192	+
	1193	+**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.**
	1194	+
	1195	+
	1196	+[[image:image-20221116111844-4.png||height="641" width="739"]]
	1197	+
	1198	+
	1199	+[[image:image-20221116111844-5.png||height="551" width="708"]]
	1200	+
	1201	+
	1202	+= 8  Trouble Shooting =
	1203	+
	1204	+== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
	1205	+
	1206	+
	1207	+(((
	1208	+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
	1209	+)))
	1210	+
	1211	+
	1212	+== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
	1213	+
	1214	+
	1215	+(((
	1216	+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.
	1217	+)))
	1218	+
	1219	+
	1220	+== 8.3  Problem after Upgrading Firmware ==
	1221	+
	1222	+=== 8.3.1 Continue Restart after upgrading ===
	1223	+
	1224	+
	1225	+(((
	1226	+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
	1227	+)))
	1228	+
	1229	+
	1230	+[[image:image-20221118105249-3.png]]
	1231	+
	1232	+
	1233	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1234	+
	1235	+
	1236	+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
	1237	+
	1238	+
	1239	+=== 8.3.3 "flash read err" after upgrade firmware ===
	1240	+
	1241	+Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
	1242	+
	1243	+[[image:image-20221122100004-1.png||height="497" width="534"]]
	1244	+
	1245	+
	1246	+User need to upgrade again with below four files to solve this issue.
	1247	+
	1248	+ [[image:image-20221122100004-2.png||height="619" width="389"]]
	1249	+
	1250	+ **Figure 2**
	1251	+
	1252	+
	1253	+=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
	1254	+
	1255	+User might erase the entire flash include keys and default settings which cause this issue.
	1256	+
	1257	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
	1258	+
	1259	+[[image:image-20221122100004-3.png]]
	1260	+
	1261	+Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
	1262	+
	1263	+
	1264	+Example:
	1265	+
	1266	+AT+DEUI=70B3D57ED0053981
	1267	+
	1268	+AT+APPEUI=D23345667BCBCCAF
	1269	+
	1270	+AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1271	+
	1272	+AT+DADDR=260b4dce    ( no need for OTAA)
	1273	+
	1274	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
	1275	+
	1276	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
	1277	+
	1278	+
	1279	+
	1280	+==== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
	1281	+
	1282	+
	1283	+[[image:image-20221122100004-4.png]]
	1284	+
	1285	+
	1286	+== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
	1287	+
	1288	+
	1289	+Please download version 1.4.2 again
	1290	+
	1291	+
	1292	+== 8.5  How to deal with unsuccessful GPS positioning? ==
	1293	+
	1294	+
	1295	+1） Make Sure the device is in Open Area where can see the sky.
	1296	+
	1297	+2)  Set PDOP to a higher value.
	1298	+
	1299	+* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1300	+
	1301	+* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1302	+
	1303	+* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1304	+
	1305	+Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
	1306	+
	1307	+
	1308	+= 9.  Order Info =
	1309	+
	1310	+
887	887	Part Number: (% style="color:blue" %)**TrackerD-XXX**
888	888
889	889	(% style="color:blue" %)**XXX**(%%): The default frequency band
890	890
891	891	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
	1316	+
892	892	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
	1318	+
893	893	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
	1320	+
894	894	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
	1322	+
895	895	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
	1324	+
896	896	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
	1326	+
897	897	* (% style="color:red" %)**US915**(%%): Default frequency band US915
898	898
899	899
	1330	+= 10.  Packing Info =
900	900
901	901
902		-= 9.  Packing Info =
	1333	+(% style="color:#037691" %)**Package Includes**:
903	903
904		-
905		-**(% style="color:#037691" %)Package Includes**:
906		-
907	907	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1336	+
908	908	* USB recharge & program cable x 1
909	909
910		-**(% style="color:#037691" %)Dimensions and Weight**:
	1339	+(% style="color:#037691" %)**Dimensions and Weight**:
911	911
912		-* Device Size: 85 x 48 x 15 cm
	1341	+* Device Size: 85 x 48 x 15 mm
	1342	+
913	913	* Weight: 50g
914	914
915	915
	1346	+= 11. Support =
916	916
917	917
918		-= 10. Support =
919		-
920		-
921	921	* 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.
	1350	+
922	922	* 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]].
923	923
924	924
	1354	+= 12.  Reference =
925	925
926	926
927		-= 11.  Reference =
928		-
929		-
930	930	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1358	+
931	931	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
932		-* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
933	933
934		-
935		-
	1361	+* [[**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-20221006181316-1.png

Author

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

Size

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

Content

image-20221006181357-2.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+88.0 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