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

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 21 removed)
  • 1667288597595-714.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.Xiaoling

Content

...	...	@@ -14,6 +14,7 @@
14	14
15	15	= 1.  Introduction =
16	16
	17	+
17	17	== 1.1  What is TrackerD ==
18	18
19	19
...	...	@@ -45,6 +45,7 @@
45	45	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
46	46
47	47
	49	+
48	48	== 1.2 Specifications ==
49	49
50	50
...	...	@@ -119,8 +119,9 @@
119	119	* Logistics and Supply Chain Management
120	120	* Human tracking
121	121
122		-= 2.  Use TrackerD =
	124	+= 2.1 Use TrackerD =
123	123
	126	+
124	124	== 2.1 How it works? ==
125	125
126	126
...	...	@@ -127,6 +127,7 @@
127	127	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.
128	128
129	129
	133	+
130	130	== 2.2 Quick guide to connect to LoRaWAN server ==
131	131
132	132
...	...	@@ -168,34 +168,34 @@
168	168	**__Add APP KEY and DEV EUI:__**
169	169
170	170
171		-[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
	175	+[[image:1664501784668-703.png]]
172	172
173	173
174	174
175		-(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
176	176
177		-(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
	180	+(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
178	178
179		-[[image:1664502835802-546.png]]
180	180
181		-
182	182	(% 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.
183	183
184	184
	186	+
185	185	== 2.3  Positioning Mode(SMOD) ==
186	186
187	187
188	188	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
189	189
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.
	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.
193	193
194	194	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
195	195
196	196
	199	+
197	197	== 2.4  Uplink Payload ==
198	198
	202	+
199	199	=== 2.4.1 Uplink FPORT~=5, Device Status ===
200	200
201	201
...	...	@@ -251,7 +251,7 @@
251	251
252	252	(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
253	253
254		-(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
	258	+(% border="1.5" style="background-color:#ffffcc; color:green; width:280px" %)
255	255	|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
256	256	|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
257	257
...	...	@@ -275,13 +275,11 @@
275	275
276	276	(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
277	277
278		-(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)
279	279
280		-
281	281	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
282	282
283		-(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
284		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
	285	+(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
	286	+|=(% scope="row" style="width: 77px;" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:92px" %)1 Bit|(% style="width:48px" %)1 Bit|(% style="width:126px" %)1 Bit
285	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	286
287	287	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
...	...	@@ -290,12 +290,12 @@
290	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	291
292	292
293		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
294		-|=(% scope="row" style="width: 60px;" %)(((
	295	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
	296	+|=(% scope="row" style="width: 50px;" %)(((
295	295	**Size(bytes)**
296		-)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
	298	+)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
297	297	2
298		-)))|(% style="width:30px" %)(((
	300	+)))|(% style="width:87px" %)(((
299	299	2
300	300	)))
301	301	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
...	...	@@ -313,8 +313,8 @@
313	313
314	314	==== (% style="color:blue" %)**FLAG:**(%%) ====
315	315
316		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
317		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
	318	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	319	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
318	318	|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
319	319
320	320	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
...	...	@@ -390,6 +390,7 @@
390	390	)))
391	391
392	392
	395	+
393	393	==== (% style="color:blue" %)**Hum:**(%%) ====
394	394
395	395	0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
...	...	@@ -400,6 +400,7 @@
400	400	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
401	401
402	402
	406	+
403	403	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
404	404
405	405
...	...	@@ -406,10 +406,10 @@
406	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)
407	407
408	408
409		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
410		-|=(% scope="row" style="width: 60px;" %)(((
	413	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
	414	+|=(% scope="row" style="width: 50px;" %)(((
411	411	**Size(bytes)**
412		-)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
	416	+)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
413	413	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
414	414	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
415	415	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
...	...	@@ -418,6 +418,7 @@
418	418	[[image:1665301687277-443.png]]
419	419
420	420
	425	+
421	421	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
422	422
423	423
...	...	@@ -427,12 +427,12 @@
427	427	(% style="color:red" %)**Note for this mode:**
428	428
429	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.
	435	+* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=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	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	432
433	433	The payload is 15 bytes, as below.
434	434
435		-(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	440	+(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
436	436	|=(% scope="row" %)(((
437	437	**Size(bytes)**
438	438	)))|4|4|2|1|1|1|1|1
...	...	@@ -441,6 +441,7 @@
441	441	[[image:image-20221009160309-2.png]]
442	442
443	443
	449	+
444	444	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
445	445
446	446
...	...	@@ -472,37 +472,15 @@
472	472	* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
473	473	* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
474	474	* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
475		-* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
	481	+* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
476	476	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
477	477	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
478	478
479		-=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
	485	+=== 2.4.6  Add Payload format in TTN V3 ===
480	480
481	481
482		-TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
	488	+In TTN V3, use can add a custom payload so it shows friendly.
483	483
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||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		-
506	506	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
507	507
508	508
...	...	@@ -509,7 +509,6 @@
509	509	[[image:1664502649601-895.png]]
510	510
511	511
512		-
513	513	Add the decoder from this link:
514	514
515	515	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
...	...	@@ -519,6 +519,7 @@
519	519	[[image:1664502676891-606.png]]
520	520
521	521
	505	+
522	522	== 2.5 Integrate with Datacake ==
523	523
524	524
...	...	@@ -526,10 +526,10 @@
526	526
527	527	Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
528	528
529		-
530	530	[[image:1664502695771-538.png]]
531	531
532	532
	516	+
533	533	== 2.6 Integrate with Tago ==
534	534
535	535
...	...	@@ -538,9 +538,11 @@
538	538	Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
539	539
540	540
	525	+
541	541	[[image:1664502715371-321.png]]
542	542
543	543
	529	+
544	544	== 2.7  Datalog Feature ==
545	545
546	546
...	...	@@ -556,6 +556,7 @@
556	556	[[image:image-20221009234629-1.png||height="390" width="577"]]
557	557
558	558
	545	+
559	559	== 2.8 Alarm Mode ==
560	560
561	561
...	...	@@ -570,7 +570,7 @@
570	570
571	571
572	572	(((
573		-**Two ways to exit alarm mode:**
	560	+Two ways to exit alarm mode:
574	574	)))
575	575
576	576	* Server sends a downlink command to exit.
...	...	@@ -581,6 +581,7 @@
581	581	)))
582	582
583	583
	571	+
584	584	== 2.9 Transport Mode ==
585	585
586	586
...	...	@@ -587,16 +587,17 @@
587	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.
588	588
589	589
	578	+
590	590	== 2.10 LED Status ==
591	591
592	592
593		-(% border="1.5" style="background-color:#ffffcc; width:500px" %)
	582	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
594	594	|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
595	595	|(% 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
596	596	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
597	597	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
598	598	|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% 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
	588	+|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
600	600	|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
601	601	|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
602	602	|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
...	...	@@ -619,9 +619,9 @@
619	619	[[image:1664502854406-763.png]]
620	620
621	621
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"]]
	611	+(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	612	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
	613	+|(% 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"]]
625	625	|(% 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
626	626	|(% 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.
627	627
...	...	@@ -643,6 +643,7 @@
643	643	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
644	644
645	645
	635	+
646	646	== 3.1 Access AT Command ==
647	647
648	648
...	...	@@ -667,6 +667,7 @@
667	667
668	668	== 3.2 Command Set ==
669	669
	660	+
670	670	=== 3.2.1 Set Transmit Interval ===
671	671
672	672
...	...	@@ -684,6 +684,7 @@
684	684	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
685	685
686	686
	678	+
687	687	=== 3.2.2 Set Alarm Packet transmission interval ===
688	688
689	689
...	...	@@ -701,6 +701,7 @@
701	701	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
702	702
703	703
	696	+
704	704	=== 3.2.3 Set Transport Mode Packet transmission interval ===
705	705
706	706
...	...	@@ -715,9 +715,10 @@
715	715
716	716	* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
717	717
718		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
	711	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
719	719
720	720
	714	+
721	721	=== 3.2.4 Exit Alarm ===
722	722
723	723
...	...	@@ -730,6 +730,7 @@
730	730	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
731	731
732	732
	727	+
733	733	=== 3.2.5 Disable/Enable LED flash ===
734	734
735	735
...	...	@@ -747,6 +747,7 @@
747	747	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
748	748
749	749
	745	+
750	750	=== 3.2.6 Disable/Enable Transport Mode ===
751	751
752	752
...	...	@@ -756,14 +756,15 @@
756	756
757	757	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
758	758
759		-Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
	755	+Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
760	760
761	761
762	762	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
763	763
764		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
	760	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
765	765
766	766
	763	+
767	767	=== 3.2.7 Set Positioning Mode ===
768	768
769	769
...	...	@@ -776,40 +776,32 @@
776	776
777	777	(% style="color:#037691" %)** aa:**
778	778
779		-* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
	776	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
	777	+* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
	778	+* (% 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.
780	780
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.
782		-
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.
784		-
785	785	(% style="color:#037691" %)**bb:**
786	786
787	787	* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
788		-
789	789	* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
790	790
791	791	(% style="color:#037691" %)**cc:   **
792	792
793		-* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
794		-
795		-* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
	787	+* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
796	796
797	797	(% style="color:blue" %)**Example:**
798	798
799		- AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
	791	+ AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
	792	+ AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
	793	+ AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
800	800
801		- AT+SMOD=1,1,0 ~-~->  GPS +BAT State
802	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	808	* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
809	809
810		-(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
	798	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
811	811
812	812
	801	+
813	813	=== 3.2.8 Set MAX GPS position time ===
814	814
815	815
...	...	@@ -816,7 +816,7 @@
816	816	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.
817	817
818	818
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.
	808	+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.
820	820
821	821
822	822	* (% style="color:blue" %)**AT Command:**
...	...	@@ -831,6 +831,7 @@
831	831	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
832	832
833	833
	823	+
834	834	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
835	835
836	836
...	...	@@ -855,7 +855,7 @@
855	855
856	856
857	857
858		-**Disable/Enable the confirmation mode**
	848	+Disable/Enable the confirmation mode
859	859
860	860	* (% style="color:blue" %)**AT Command:**
861	861
...	...	@@ -864,16 +864,17 @@
864	864
865	865	**~ Example:**
866	866
867		- AT+CFM=0    **~-~->   ** Disable confirmation
	857	+ AT+ CFM=0    **~-~->   ** Disable confirmation
868	868
869		- AT+CFM=1    **~-~->  ** Enable confirmation
	859	+ AT+ CFM=1    **~-~->  ** Enable confirmation
870	870
871	871
872	872	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
873	873
874		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
	864	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
875	875
876	876
	867	+
877	877	=== 3.2.10  Auto Send None-ACK messages ===
878	878
879	879
...	...	@@ -895,10 +895,11 @@
895	895	Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
896	896
897	897
	889	+
898	898	=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
899	899
900	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.
	893	+BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
902	902
903	903	(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
904	904
...	...	@@ -908,55 +908,13 @@
908	908
909	909	(% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
910	910
911		-(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
912	912
913		-Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
	904	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
914	914
	906	+Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
915	915
916		-=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
917	917
918	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		- (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
926		-
927		- (% 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: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
932		-
933		-
934		-=== 3.2.13 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.14 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		-
960	960	= 4. Setting for Different Scenarios =
961	961
962	962
...	...	@@ -963,6 +963,7 @@
963	963
964	964	= 5. Upload Firmware =
965	965
	916	+
966	966	== 5.1 Firmware Change Log ==
967	967
968	968
...	...	@@ -969,6 +969,7 @@
969	969	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
970	970
971	971
	923	+
972	972	== 5.2 How to upgrade firmware ==
973	973
974	974
...	...	@@ -1001,27 +1001,29 @@
1001	1001	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1002	1002
1003	1003
1004		-**Users need to use below files:**
	956	+Users need to use below files:
1005	1005
1006	1006	boot_app0.bin @0e000
1007	1007
1008		-US915.bin @ 0x10000(Select the bin file of the frequency band you need)
	960	+ESP_LORA-eeprom-class.bin @ 0x10000
1009	1009
1010	1010
1011		-[[image:image-20221118105220-2.png]]
	963	+[[image:1664503593459-435.png]]
1012	1012
1013	1013
1014	1014
1015	1015	After upgrade finish, it will show finish as below:
1016	1016
1017		-[[image:image-20221118105402-4.png]]
	969	+[[image:1664503611848-385.png]]
1018	1018
1019	1019
1020	1020
1021	1021	= 6. Developer Guide =
1022	1022
	975	+
1023	1023	== 6.1 Compile Source Code ==
1024	1024
	978	+
1025	1025	=== 6.1.1 Set up ARDUINO compile environment ===
1026	1026
1027	1027
...	...	@@ -1059,6 +1059,7 @@
1059	1059	[[image:1664503752288-974.png]]
1060	1060
1061	1061
	1016	+
1062	1062	== 6.2 Source Code ==
1063	1063
1064	1064
...	...	@@ -1079,8 +1079,10 @@
1079	1079	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1080	1080
1081	1081
	1037	+
1082	1082	= 7.  FAQ =
1083	1083
	1040	+
1084	1084	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1085	1085
1086	1086
...	...	@@ -1087,6 +1087,7 @@
1087	1087	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1088	1088
1089	1089
	1047	+
1090	1090	== 7.2 What is the pin mapping for the USB program cable? ==
1091	1091
1092	1092
...	...	@@ -1105,242 +1105,45 @@
1105	1105	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1106	1106	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1107	1107
1108		-== 7.3 Notes on using different serial port tools for TrackerD ==
	1066	+= 8.  Order Info =
1109	1109
1110		-=== 7.3.1  Serial port utility ===
1111	1111
1112		-
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]]
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]]
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]]
1134		-
1135		-
1136		-[[image:image-20221102140712-4.png]]
1137		-
1138		-
1139		-=== 7.3.3  PUTTY ===
1140		-
1141		-
1142		-[[image:image-20221102140748-5.png]]
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]]
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||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||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||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||height="641" width="739"]]
1185		-
1186		-
1187		-[[image:image-20221116111844-5.png||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]]
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||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||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]]
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		-
1252		-Example:
1253		-
1254		-AT+DEUI=70B3D57ED0053981
1255		-
1256		-AT+APPEUI=D23345667BCBCCAF
1257		-
1258		-AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1259		-
1260		-AT+DADDR=260b4dce    ( no need for OTAA)
1261		-
1262		-AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1263		-
1264		-AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1265		-
1266		-
1267		-
1268		-=== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===
1269		-
1270		-
1271		-[[image:image-20221122100004-4.png]]
1272		-
1273		-
1274		-== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1275		-
1276		-
1277		-Please download version 1.4.2 again
1278		-
1279		-
1280		-== 8.5  How to deal with unsuccessful GPS positioning? ==
1281		-
1282		-
1283		-1） Make Sure the device is in Open Area where can see the sky.
1284		-
1285		-2)  Set PDOP to a higher value.
1286		-
1287		-* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1288		-
1289		-* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1290		-
1291		-* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1292		-
1293		-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
1294		-
1295		-
1296		-= 9.  Order Info =
1297		-
1298		-
1299	1299	Part Number: (% style="color:blue" %)**TrackerD-XXX**
1300	1300
1301	1301	(% style="color:blue" %)**XXX**(%%): The default frequency band
1302	1302
1303	1303	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1304		-
1305	1305	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1306		-
1307	1307	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1308		-
1309	1309	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1310		-
1311	1311	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1312		-
1313	1313	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1314		-
1315	1315	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1316	1316
1317		-= 10.  Packing Info =
	1081	+= 9.  Packing Info =
1318	1318
1319	1319
1320	1320	(% style="color:#037691" %)**Package Includes**:
1321	1321
1322	1322	* TrackerD LoRaWAN GPS/BLE Tracker x 1
1323		-
1324	1324	* USB recharge & program cable x 1
1325	1325
1326	1326	(% style="color:#037691" %)**Dimensions and Weight**:
1327	1327
1328		-* Device Size: 85 x 48 x 15 mm
1329		-
	1091	+* Device Size: 85 x 48 x 15 cm
1330	1330	* Weight: 50g
1331	1331
1332		-= 11. Support =
	1094	+= 10. Support =
1333	1333
1334	1334
1335	1335	* 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.
1336		-
1337	1337	* 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]].
1338	1338
1339		-= 12.  Reference =
	1100	+= 11.  Reference =
1340	1340
1341	1341
1342	1342	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1343		-
1344	1344	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1345		-
1346	1346	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
	1106	+
	1107	+

1667288597595-714.png

Author

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

Size

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

Content

image-20221102140621-1.png

Author

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

Size

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

Content

image-20221102140638-2.png

Author

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

Size

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

Content

image-20221102140704-3.png

Author

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

Size

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

Content

image-20221102140712-4.png

Author

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

Size

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

Content

image-20221102140748-5.png

Author

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

Size

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

Content

image-20221102140801-6.png

Author

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

Size

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

Content

image-20221107145243-1.png

Author

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

Size

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

Content

image-20221116111844-1.png

Author

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

Size

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

Content

image-20221116111844-2.png

Author

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

Size

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

Content

image-20221116111844-3.png

Author

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

Size

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

Content

image-20221116111844-4.png

Author

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

Size

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

Content

image-20221116111844-5.png

Author

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

Size

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

Content

image-20221118104359-1.png

Author

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

Size

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

Content

image-20221118105220-2.png

Author

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

Size

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

Content

image-20221118105249-3.png

Author

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

Size

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

Content

image-20221118105402-4.png

Author

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

Size

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

Content

image-20221122100004-1.png

Author

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

Size

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

Content

image-20221122100004-2.png

Author

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

Size

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

Content

image-20221122100004-3.png

Author

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

Size

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

Content

image-20221122100004-4.png

Author

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

Size

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

Content