Changes for page LMDS200 -- LoRaWAN Microwave Radar Distance Sensor User Manual

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 31 removed)
  • 1654852175653-550.png
  • 1654852253176-749.png
  • 1655254599445-662.png
  • 1655255122126-327.png
  • 1655256160324-178.png
  • 1655257026882-201.png
  • 1655257698953-697.png
  • image-20220610172003-1.png
  • image-20220610172003-2.png
  • image-20220610172400-3.png
  • image-20220610172924-4.png
  • image-20220610172924-5.png
  • image-20220610172924-6.png
  • image-20220610173409-7.png
  • image-20220610174836-8.png
  • image-20220610174917-9.png
  • image-20220615090910-1.png
  • image-20220615090910-2.png
  • image-20220615091045-3.png
  • image-20220615091045-4.png
  • image-20220615091045-5.png
  • image-20220615091045-6.png
  • image-20220615091045-7.png
  • image-20220615091045-8.png
  • image-20220615091045-9.png
  • image-20220615091929-10.png
  • image-20220615092010-11.png
  • image-20220615092044-12.png
  • image-20220615092327-13.png
  • image-20220615095102-14.png
  • image-20220615100930-15.png

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-LDDS20 - LoRaWAN Ultrasonic Liquid Level Sensor User Manual
	1	+LDDS75 - LoRaWAN Distance Detection Sensor User Manual

Content

...	...	@@ -1,578 +1,828 @@
1	1	(% style="text-align:center" %)
2		-[[image:1655254599445-662.png]]
	2	+[[image:1654846127817-788.png]]
3	3
	4	+**Contents:**
4	4
5	5
6	6
7		-**Table of Contents:**
8	8
9	9
10	10
11	11
12	12
13		-
14		-
15		-
16	16	= 1.  Introduction =
17	17
18		-== 1.1 ​ What is LoRaWAN Ultrasonic liquid level Sensor ==
	15	+== 1.1 ​ What is LoRaWAN Distance Detection Sensor ==
19	19
20	20	(((
21	21
22	22
23	23	(((
24		-(((
25		-(((
26		-The Dragino LDDS20 is a (% style="color:#4472c4" %)**LoRaWAN Ultrasonic liquid level sensor**(%%) for Internet of Things solution. It uses (% style="color:#4472c4" %)**none-contact method **(%%)to measure the height of liquid in a container without opening the container, and send the value via LoRaWAN network to IoT Server
27		-)))
	21	+The Dragino LDDS75 is a (% style="color:#4472c4" %)** LoRaWAN Distance Detection Sensor**(%%) for Internet of Things solution. It is used to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses (% style="color:#4472c4" %)** ultrasonic sensing** (%%)technology for distance measurement, and (% style="color:#4472c4" %)** temperature compensation**(%%) is performed internally to improve the reliability of data. The LDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc.
28	28
29		-(((
30		-
	23	+
	24	+It detects the distance** (% style="color:#4472c4" %) between the measured object and the sensor(%%)**, and uploads the value via wireless to LoRaWAN IoT Server.
	25	+
	26	+
	27	+The LoRa wireless technology used in LDDS75 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
	28	+
	29	+
	30	+LDDS75 is powered by (% style="color:#4472c4" %)** 4000mA or 8500mAh Li-SOCI2 battery**(%%); It is designed for long term use up to 10 years*.
	31	+
	32	+
	33	+Each LDDS75 pre-loads with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect if there is network coverage, after power on.
	34	+
	35	+
	36	+(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors
31	31	)))
	38	+)))
32	32
	40	+
	41	+[[image:1654847051249-359.png]]
	42	+
	43	+
	44	+
	45	+== ​1.2  Features ==
	46	+
	47	+* LoRaWAN 1.0.3 Class A
	48	+* Ultra low power consumption
	49	+* Distance Detection by Ultrasonic technology
	50	+* Flat object range 280mm - 7500mm
	51	+* Accuracy: ±(1cm+S*0.3%) (S: Distance)
	52	+* Cable Length : 25cm
	53	+* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
	54	+* AT Commands to change parameters
	55	+* Uplink on periodically
	56	+* Downlink to change configure
	57	+* IP66 Waterproof Enclosure
	58	+* 4000mAh or 8500mAh Battery for long term use
	59	+
	60	+== 1.3  Specification ==
	61	+
	62	+=== 1.3.1  Rated environmental conditions ===
	63	+
	64	+[[image:image-20220610154839-1.png]]
	65	+
	66	+**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);**
	67	+
	68	+**b. When the ambient temperature is 40-50 ℃, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation)**
	69	+
	70	+
	71	+
	72	+=== 1.3.2  Effective measurement range Reference beam pattern ===
	73	+
	74	+**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**[[image:image-20220610155021-2.png||height="440" width="1189"]]
	75	+
	76	+
	77	+
	78	+**(2)** The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.[[image:image-20220610155021-3.png||height="437" width="1192"]]
	79	+
	80	+(% style="display:none" %) (%%)
	81	+
	82	+
	83	+== 1.5 ​ Applications ==
	84	+
	85	+* Horizontal distance measurement
	86	+* Liquid level measurement
	87	+* Parking management system
	88	+* Object proximity and presence detection
	89	+* Intelligent trash can management system
	90	+* Robot obstacle avoidance
	91	+* Automatic control
	92	+* Sewer
	93	+* Bottom water level monitoring
	94	+
	95	+== 1.6  Pin mapping and power on ==
	96	+
	97	+
	98	+[[image:1654847583902-256.png]]
	99	+
	100	+
	101	+= 2.  Configure LDDS75 to connect to LoRaWAN network =
	102	+
	103	+== 2.1  How it works ==
	104	+
33	33	(((
34		-The LDDS20 sensor is installed directly below the container to detect the height of the liquid level. User doesn’t need to open a hole on the container to be tested. The (% style="color:#4472c4" %)**none-contact measurement makes the measurement safety, easier and possible for some strict situation**.
	106	+The LDDS75 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS75. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value
35	35	)))
36	36
37	37	(((
38		-
	110	+In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.A0ConfigureLDDS75viaATCommandorLoRaWANDownlink"]]to set the keys in the LDDS75.
39	39	)))
40	40
	113	+
	114	+== 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
	115	+
41	41	(((
42		-LDDS20 uses ultrasonic sensing technology for distance measurement. LDDS20 is of high accuracy to measure various liquid such as: (% style="color:#4472c4" %)**toxic substances**(%%), (% style="color:#4472c4" %)**strong acids**(%%), (% style="color:#4472c4" %)**strong alkalis**(%%) and (% style="color:#4472c4" %)**various pure liquids**(%%) in high-temperature and high-pressure airtight containers.
	117	+Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.
43	43	)))
44	44
45	45	(((
46		-
	121	+[[image:1654848616367-242.png]]
47	47	)))
48	48
49	49	(((
50		-The LoRa wireless technology used in LDDS20 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
	125	+The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
51	51	)))
52	52
53	53	(((
54		-
	129	+(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
55	55	)))
56	56
57	57	(((
58		-LDDS20 is powered by (% style="color:#4472c4" %)**8500mA Li-SOCI2 battery**(%%); It is designed for long term use up to 10 years*.
	133	+Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
59	59	)))
60	60
	136	+[[image:image-20220607170145-1.jpeg]]
	137	+
	138	+
	139	+For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
	140	+
	141	+Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
	142	+
	143	+**Add APP EUI in the application**
	144	+
	145	+[[image:image-20220610161353-4.png]]
	146	+
	147	+[[image:image-20220610161353-5.png]]
	148	+
	149	+[[image:image-20220610161353-6.png]]
	150	+
	151	+
	152	+[[image:image-20220610161353-7.png]]
	153	+
	154	+
	155	+You can also choose to create the device manually.
	156	+
	157	+ [[image:image-20220610161538-8.png]]
	158	+
	159	+
	160	+
	161	+**Add APP KEY and DEV EUI**
	162	+
	163	+[[image:image-20220610161538-9.png]]
	164	+
	165	+
	166	+
	167	+(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
	168	+
	169	+
	170	+Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
	171	+
	172	+[[image:image-20220610161724-10.png]]
	173	+
	174	+
61	61	(((
62		-
	176	+(% style="color:blue" %)**Step 3**(%%)**:** The LDDS75 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
63	63	)))
64	64
	179	+[[image:1654849068701-275.png]]
	180	+
	181	+
	182	+
	183	+== 2.3  ​Uplink Payload ==
	184	+
65	65	(((
66		-Each LDDS20 pre-loads with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect if there is network coverage, after power on.
	186	+LDDS75 will uplink payload via LoRaWAN with below payload format:
	187	+
	188	+Uplink payload includes in total 4 bytes.
	189	+Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
67	67	)))
68	68
69	69	(((
70	70
71	71	)))
72		-)))
73	73
74		-(((
75		-(((
76		-(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors.
77		-)))
78		-)))
79		-)))
80		-)))
	196	+(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
	197	+|=(% style="width: 62.5px;" %)(((
	198	+**Size (bytes)**
	199	+)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
	200	+|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
	201	+[[Distance>>||anchor="H2.3.3A0Distance"]]
81	81
	203	+(unit: mm)
	204	+)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
	205	+[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
	206	+)))|[[Sensor Flag>>path:#Sensor_Flag]]
82	82
83		-[[image:1655255122126-327.png]]
	208	+[[image:1654850511545-399.png]]
84	84
85	85
86	86
87		-== ​1.2  Features ==
	212	+=== 2.3.1  Battery Info ===
88	88
89		-* LoRaWAN 1.0.3 Class A
90		-* Ultra low power consumption
91		-* Liquid Level Measurement by Ultrasonic technology
92		-* Measure through container, No need to contact Liquid.
93		-* Valid level range 20mm - 2000mm
94		-* Accuracy: ±(5mm+S*0.5%) (S: Measure Value)
95		-* Cable Length : 25cm
96		-* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
97		-* AT Commands to change parameters
98		-* Uplink on periodically
99		-* Downlink to change configure
100		-* IP66 Waterproof Enclosure
101		-* 8500mAh Battery for long term use
102	102
103		-== 1.3  Suitable Container & Liquid ==
	215	+Check the battery voltage for LDDS75.
104	104
105		-* Solid Wall container such as: steel, iron, glass, ceramics, non-foaming plastics etc.
106		-* Container shape is regular, and surface is smooth.
107		-* Container Thickness:
108		-** Pure metal material.  2~~8mm, best is 3~~5mm
109		-** Pure non metal material: <10 mm
110		-* Pure liquid without irregular deposition.
	217	+Ex1: 0x0B45 = 2885mV
111	111
112		-== 1.4  Mechanical ==
	219	+Ex2: 0x0B49 = 2889mV
113	113
114		-[[image:image-20220615090910-1.png]]
115	115
116	116
117		-[[image:image-20220615090910-2.png]]
	223	+=== 2.3.2  Distance ===
118	118
	225	+Get the distance. Flat object range 280mm - 7500mm.
119	119
	227	+For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0B05(H) = 2821 (D) = 2821 mm.**
120	120
121		-== 1.5  Install LDDS20 ==
122	122
	230	+* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
	231	+* If the sensor value lower than 0x0118 (280mm), the sensor value will be invalid. Since v1.1.4, all value lower than 280mm will be set to 0x0014(20mm) which means the value is invalid.
123	123
124		-(% style="color:blue" %)**Step 1**(%%):  Choose the installation point.
125	125
126		-LDDS20 (% style="color:red" %)**MUST**(%%) be installed on the container bottom middle position.
127	127
128		-[[image:image-20220615091045-3.png]]
	235	+=== 2.3.3  Interrupt Pin ===
129	129
	237	+This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H4.2A0SetInterruptMode"]] for the hardware and software set up.
130	130
	239	+**Example:**
131	131
132		-(% style="color:blue" %)**Step 2**(%%):  Polish the installation point.
	241	+0x00: Normal uplink packet.
133	133
134		-For Metal Surface with paint, it is important to polish the surface, first use crude sand paper to polish the paint level , then use exquisite sand paper to polish the metal level to make it shine & smooth.
	243	+0x01: Interrupt Uplink Packet.
135	135
136		-[[image:image-20220615092010-11.png]]
137	137
	246	+=== 2.3.4  DS18B20 Temperature sensor ===
138	138
139		-No polish needed if the container is shine metal surface without paint or non-metal container.
	248	+This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
140	140
141		-[[image:image-20220615092044-12.png]]
	250	+**Example**:
142	142
	252	+If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
143	143
	254	+If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
144	144
145		-(% style="color:blue" %)**Step3:   **(%%)Test the installation point.
	256	+(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
146	146
147		-Power on LDDS75, check if the blue LED is on, If the blue LED is on, means the sensor works. Then put ultrasonic coupling paste on the sensor and put it tightly on the installation point.
148	148
149	149
150		-It is necessary to put the coupling paste between the sensor and the container, otherwise LDDS20 won’t detect the liquid level.
	260	+=== 2.3.5  Sensor Flag ===
151	151
152		-[[image:1655256160324-178.png]][[image:image-20220615092327-13.png]]
	262	+0x01: Detect Ultrasonic Sensor
153	153
	264	+0x00: No Ultrasonic Sensor
154	154
155		-After paste the LDDS20 well, power on LDDS20. In the first 30 seconds of booting, device will check the sensors status and BLUE LED will show the status as below. After 30 seconds, BLUE LED will be off to save battery life.
156	156
	267	+===
	268	+(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
157	157
158		-(% style="color:red" %)**LED Status:**
	270	+While using TTN network, you can add the payload format to decode the payload.
159	159
160		-* Onboard LED: When power on device, the onboard LED will fast blink 4 times which means detect the sensor well.
161	161
162		-* (% style="color:blue" %)BLUE LED(% style="color:red" %) always ON(%%): Sensor is power on but doesn’t detect liquid. There is problem in installation point.
163		-* (% style="color:blue" %)BLUE LED(% style="color:red" %) slowly blinking(%%): Sensor detects Liquid Level, The installation point is good.
	273	+[[image:1654850829385-439.png]]
164	164
165		-LDDS20 will enter into low power mode at 30 seconds after system reset or power on, Blue LED will be off after that.
	275	+The payload decoder function for TTN V3 is here:
166	166
	277	+LDDS75 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS75/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
167	167
168		-(% style="color:red" %)**Note 2:**
169	169
170		-(% style="color:red" %)Ultrasonic coupling paste (%%) is subjected in most shipping way. So the default package doesn’t include it and user needs to purchase locally.
171	171
	281	+== 2.4  Uplink Interval ==
172	172
	283	+The LDDS75 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
173	173
174		-(% style="color:blue" %)**Step4:   **(%%)Install use Epoxy ab glue.
175	175
176		-Prepare Eproxy AB glue.
177	177
178		-Put Eproxy AB glue in the sensor and press it hard on the container installation point.
	287	+== 2.5  ​Show Data in DataCake IoT Server ==
179	179
180		-Reset LDDS20 and see if the BLUE LED is slowly blinking.
	289	+(((
	290	+[[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps:
	291	+)))
181	181
182		-[[image:image-20220615091045-8.png||height="226" width="380"]] [[image:image-20220615091045-9.png||height="239" width="339"]]
	293	+(((
	294	+
	295	+)))
183	183
	297	+(((
	298	+(% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.**
	299	+)))
184	184
185		-(% style="color:red" %)**Note 1:**
	301	+(((
	302	+(% style="color:blue" %)**Step 2**(%%)**: To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:**
	303	+)))
186	186
187		-Eproxy AB glue needs 3~~ 5 minutes to stable attached. we can use other glue material to keep it in the position.
188	188
	306	+[[image:1654592790040-760.png]]
189	189
190		-(% style="color:red" %)**Note 2:**
191	191
192		-(% style="color:red" %)Eproxy AB glue(%%) is subjected in most shipping way. So the default package doesn’t include it and user needs to purchase locally.
	309	+[[image:1654592800389-571.png]]
193	193
194	194
	312	+(% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
195	195
196		-== 1.6 ​ Applications ==
	314	+(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
197	197
198		-* Smart liquid control solution.
199		-* Smart liquefied gas solution.
	316	+[[image:1654851029373-510.png]]
200	200
201		-== 1.7  Precautions ==
202	202
203		-* At room temperature, containers of different materials, such as steel, glass, iron, ceramics, non-foamed plastics and other dense materials, have different detection blind areas and detection limit heights.
204		-* For containers of the same material at room temperature, the detection blind zone and detection limit height are also different for the thickness of the container.
205		-* When the detected liquid level exceeds the effective detection value of the sensor, and the liquid level of the liquid to be measured shakes or tilts, the detected liquid height is unstable.
	319	+After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
206	206
207		-== 1.8  Pin mapping and power on ==
	321	+[[image:image-20220610165129-11.png||height="595" width="1088"]]
208	208
209	209
210		-[[image:1655257026882-201.png]]
211	211
	325	+== 2.6  Frequency Plans ==
212	212
	327	+(((
	328	+The LLDS12 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
	329	+)))
213	213
214		-= 2.  Configure LDDS20 to connect to LoRaWAN network =
215	215
	332	+=== 2.6.1  EU863-870 (EU868) ===
216	216
217		-== 2.1  How it works ==
218		-
219	219	(((
220		-The LDDS20 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS20. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value.
	335	+(% style="color:blue" %)**Uplink:**
221	221	)))
222	222
223	223	(((
224		-In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.A0UsingtheATCommands"]]to set the keys in the LDDS20.
	339	+868.1 - SF7BW125 to SF12BW125
225	225	)))
226	226
227		-
228		-
229		-== 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
230		-
231	231	(((
232		-Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.
	343	+868.3 - SF7BW125 to SF12BW125 and SF7BW250
233	233	)))
234	234
235	235	(((
236		-[[image:1655257698953-697.png]]
	347	+868.5 - SF7BW125 to SF12BW125
237	237	)))
238	238
239	239	(((
240		-The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
	351	+867.1 - SF7BW125 to SF12BW125
241	241	)))
242	242
243	243	(((
244		-
	355	+867.3 - SF7BW125 to SF12BW125
	356	+)))
245	245
246		-(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS20.
	358	+(((
	359	+867.5 - SF7BW125 to SF12BW125
247	247	)))
248	248
249	249	(((
250		-Each LDDS20 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
	363	+867.7 - SF7BW125 to SF12BW125
251	251	)))
252	252
253		-[[image:image-20220607170145-1.jpeg]]
254		-
255		-
256	256	(((
257		-For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
	367	+867.9 - SF7BW125 to SF12BW125
258	258	)))
259	259
260	260	(((
261		-Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
	371	+868.8 - FSK
262	262	)))
263	263
264	264	(((
265	265
	376	+)))
266	266
267		-**Add APP EUI in the application**
	378	+(((
	379	+(% style="color:blue" %)**Downlink:**
268	268	)))
269	269
270		-[[image:image-20220610161353-4.png]]
	382	+(((
	383	+Uplink channels 1-9 (RX1)
	384	+)))
271	271
272		-[[image:image-20220610161353-5.png]]
	386	+(((
	387	+869.525 - SF9BW125 (RX2 downlink only)
	388	+)))
273	273
274		-[[image:image-20220610161353-6.png]]
275	275
276	276
277		-[[image:image-20220610161353-7.png]]
	392	+=== 2.6.2  US902-928(US915) ===
278	278
	394	+(((
	395	+Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	396	+)))
279	279
	398	+(((
	399	+To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
	400	+)))
280	280
281		-You can also choose to create the device manually.
	402	+(((
	403	+After Join success, the end node will switch to the correct sub band by:
	404	+)))
282	282
283		- [[image:image-20220610161538-8.png]]
	406	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	407	+* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
284	284
	409	+=== 2.6.3  CN470-510 (CN470) ===
285	285
	411	+(((
	412	+Used in China, Default use CHE=1
	413	+)))
286	286
287		-**Add APP KEY and DEV EUI**
	415	+(((
	416	+(% style="color:blue" %)**Uplink:**
	417	+)))
288	288
289		-[[image:image-20220610161538-9.png]]
	419	+(((
	420	+486.3 - SF7BW125 to SF12BW125
	421	+)))
290	290
	423	+(((
	424	+486.5 - SF7BW125 to SF12BW125
	425	+)))
291	291
	427	+(((
	428	+486.7 - SF7BW125 to SF12BW125
	429	+)))
292	292
293		-(% style="color:blue" %)**Step 2**(%%):  Power on LDDS20
	431	+(((
	432	+486.9 - SF7BW125 to SF12BW125
	433	+)))
294	294
	435	+(((
	436	+487.1 - SF7BW125 to SF12BW125
	437	+)))
295	295
296		-Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
	439	+(((
	440	+487.3 - SF7BW125 to SF12BW125
	441	+)))
297	297
298		-[[image:image-20220615095102-14.png]]
	443	+(((
	444	+487.5 - SF7BW125 to SF12BW125
	445	+)))
299	299
	447	+(((
	448	+487.7 - SF7BW125 to SF12BW125
	449	+)))
300	300
	451	+(((
	452	+
	453	+)))
301	301
302	302	(((
303		-(% style="color:blue" %)**Step 3**(%%)**:**  The LDDS20 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
	456	+(% style="color:blue" %)**Downlink:**
304	304	)))
305	305
306		-[[image:1654849068701-275.png]]
	459	+(((
	460	+506.7 - SF7BW125 to SF12BW125
	461	+)))
307	307
	463	+(((
	464	+506.9 - SF7BW125 to SF12BW125
	465	+)))
308	308
	467	+(((
	468	+507.1 - SF7BW125 to SF12BW125
	469	+)))
309	309
310		-== 2.3  ​Uplink Payload ==
	471	+(((
	472	+507.3 - SF7BW125 to SF12BW125
	473	+)))
311	311
312	312	(((
	476	+507.5 - SF7BW125 to SF12BW125
	477	+)))
	478	+
313	313	(((
314		-LDDS20 will uplink payload via LoRaWAN with below payload format:
	480	+507.7 - SF7BW125 to SF12BW125
	481	+)))
315	315
316		-Uplink payload includes in total 8 bytes.
317		-Payload for firmware version v1.1.4. . Before v1.1.3, there is only 5 bytes: BAT and Distance(Please check manual v1.2.0 if you have 5 bytes payload).
	483	+(((
	484	+507.9 - SF7BW125 to SF12BW125
318	318	)))
	486	+
	487	+(((
	488	+508.1 - SF7BW125 to SF12BW125
319	319	)))
320	320
321	321	(((
322		-
	492	+505.3 - SF12BW125 (RX2 downlink only)
323	323	)))
324	324
325		-(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
326		-|=(% style="width: 62.5px;" %)(((
327		-**Size (bytes)**
328		-)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
329		-|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
330		-[[Distance>>||anchor="H2.3.2A0Distance"]]
331	331
332		-(unit: mm)
333		-)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.3A0InterruptPin"]]|(((
334		-[[Temperature (Optional )>>||anchor="H2.3.4A0DS18B20Temperaturesensor"]]
335		-)))|[[Sensor Flag>>||anchor="H2.3.5A0SensorFlag"]]
336	336
337		-[[image:1654850511545-399.png]]
338	338
	498	+=== 2.6.4  AU915-928(AU915) ===
339	339
	500	+(((
	501	+Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	502	+)))
340	340
341		-=== 2.3.1  Battery Info ===
	504	+(((
	505	+To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
	506	+)))
342	342
	508	+(((
	509	+
	510	+)))
343	343
344		-Check the battery voltage for LDDS20.
	512	+(((
	513	+After Join success, the end node will switch to the correct sub band by:
	514	+)))
345	345
346		-Ex1: 0x0B45 = 2885mV
	516	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	517	+* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
347	347
348		-Ex2: 0x0B49 = 2889mV
	519	+=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
349	349
	521	+(((
	522	+(% style="color:blue" %)**Default Uplink channel:**
	523	+)))
350	350
	525	+(((
	526	+923.2 - SF7BW125 to SF10BW125
	527	+)))
351	351
352		-=== 2.3.2  Distance ===
	529	+(((
	530	+923.4 - SF7BW125 to SF10BW125
	531	+)))
353	353
354	354	(((
355		-Get the distance. Flat object range 20mm - 2000mm.
	534	+
356	356	)))
357	357
358	358	(((
359		-For example, if the data you get from the register is __0x06 0x05__, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0605(H) = 1541 (D) = 1541 mm.**
	538	+(% style="color:blue" %)**Additional Uplink Channel**:
360	360	)))
361	361
362		-* If the sensor value is 0x0000, it means system doesn't detect ultrasonic sensor.
363		-* If the sensor value lower than 0x0014 (20mm), the sensor value will be invalid.
	541	+(((
	542	+(OTAA mode, channel added by JoinAccept message)
	543	+)))
364	364
365		-=== 2.3.3  Interrupt Pin ===
	545	+(((
	546	+
	547	+)))
366	366
367		-This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.2A0SetInterruptMode"]] for the hardware and software set up.
	549	+(((
	550	+(% style="color:blue" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
	551	+)))
368	368
369		-**Example:**
	553	+(((
	554	+922.2 - SF7BW125 to SF10BW125
	555	+)))
370	370
371		-0x00: Normal uplink packet.
	557	+(((
	558	+922.4 - SF7BW125 to SF10BW125
	559	+)))
372	372
373		-0x01: Interrupt Uplink Packet.
	561	+(((
	562	+922.6 - SF7BW125 to SF10BW125
	563	+)))
374	374
	565	+(((
	566	+922.8 - SF7BW125 to SF10BW125
	567	+)))
375	375
	569	+(((
	570	+923.0 - SF7BW125 to SF10BW125
	571	+)))
376	376
377		-=== 2.3.4  DS18B20 Temperature sensor ===
	573	+(((
	574	+922.0 - SF7BW125 to SF10BW125
	575	+)))
378	378
379		-This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
	577	+(((
	578	+
	579	+)))
380	380
381		-**Example**:
	581	+(((
	582	+(% style="color:blue" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
	583	+)))
382	382
383		-If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
	585	+(((
	586	+923.6 - SF7BW125 to SF10BW125
	587	+)))
384	384
385		-If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
	589	+(((
	590	+923.8 - SF7BW125 to SF10BW125
	591	+)))
386	386
387		-(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
	593	+(((
	594	+924.0 - SF7BW125 to SF10BW125
	595	+)))
388	388
	597	+(((
	598	+924.2 - SF7BW125 to SF10BW125
	599	+)))
389	389
	601	+(((
	602	+924.4 - SF7BW125 to SF10BW125
	603	+)))
390	390
391		-=== 2.3.5  Sensor Flag ===
	605	+(((
	606	+924.6 - SF7BW125 to SF10BW125
	607	+)))
392	392
393	393	(((
394		-0x01: Detect Ultrasonic Sensor
	610	+
395	395	)))
396	396
397	397	(((
398		-0x00: No Ultrasonic Sensor
	614	+(% style="color:blue" %)**Downlink:**
399	399	)))
400	400
	617	+(((
	618	+Uplink channels 1-8 (RX1)
	619	+)))
401	401
	621	+(((
	622	+923.2 - SF10BW125 (RX2)
	623	+)))
402	402
403		-=== 2.3.6  Decode payload in The Things Network ===
404	404
405		-While using TTN network, you can add the payload format to decode the payload.
406	406
407	407
408		-[[image:1654850829385-439.png]]
	628	+=== 2.6.6  KR920-923 (KR920) ===
409	409
410		-The payload decoder function for TTN V3 is here:
	630	+(((
	631	+(% style="color:blue" %)**Default channel:**
	632	+)))
411	411
412	412	(((
413		-LDDS20 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS20/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
	635	+922.1 - SF7BW125 to SF12BW125
414	414	)))
415	415
	638	+(((
	639	+922.3 - SF7BW125 to SF12BW125
	640	+)))
416	416
	642	+(((
	643	+922.5 - SF7BW125 to SF12BW125
	644	+)))
417	417
418		-== 2.4  Downlink Payload ==
	646	+(((
	647	+
	648	+)))
419	419
420		-By default, LDDS20 prints the downlink payload to console port.
	650	+(((
	651	+(% style="color:blue" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
	652	+)))
421	421
422		-[[image:image-20220615100930-15.png]]
	654	+(((
	655	+922.1 - SF7BW125 to SF12BW125
	656	+)))
423	423
	658	+(((
	659	+922.3 - SF7BW125 to SF12BW125
	660	+)))
424	424
425		-**Examples:**
	662	+(((
	663	+922.5 - SF7BW125 to SF12BW125
	664	+)))
426	426
	666	+(((
	667	+922.7 - SF7BW125 to SF12BW125
	668	+)))
427	427
428		-* (% style="color:blue" %)**Set TDC**
	670	+(((
	671	+922.9 - SF7BW125 to SF12BW125
	672	+)))
429	429
430		-If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
	674	+(((
	675	+923.1 - SF7BW125 to SF12BW125
	676	+)))
431	431
432		-Payload:    01 00 00 1E    TDC=30S
	678	+(((
	679	+923.3 - SF7BW125 to SF12BW125
	680	+)))
433	433
434		-Payload:    01 00 00 3C    TDC=60S
	682	+(((
	683	+
	684	+)))
435	435
	686	+(((
	687	+(% style="color:blue" %)**Downlink:**
	688	+)))
436	436
437		-* (% style="color:blue" %)**Reset**
	690	+(((
	691	+Uplink channels 1-7(RX1)
	692	+)))
438	438
439		-If payload = 0x04FF, it will reset the LDDS20
	694	+(((
	695	+921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
	696	+)))
440	440
441	441
442		-* (% style="color:blue" %)**CFM**
443	443
444		-Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
445	445
	701	+=== 2.6.7  IN865-867 (IN865) ===
446	446
	703	+(((
	704	+(% style="color:blue" %)**Uplink:**
	705	+)))
447	447
448		-== 2.5  ​Show Data in DataCake IoT Server ==
	707	+(((
	708	+865.0625 - SF7BW125 to SF12BW125
	709	+)))
449	449
450	450	(((
451		-[[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps:
	712	+865.4025 - SF7BW125 to SF12BW125
452	452	)))
453	453
454	454	(((
	716	+865.9850 - SF7BW125 to SF12BW125
	717	+)))
	718	+
	719	+(((
455	455
456	456	)))
457	457
458	458	(((
459		-(% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.**
	724	+(% style="color:blue" %)**Downlink:**
460	460	)))
461	461
462	462	(((
463		-(% style="color:blue" %)**Step 2**(%%)**: To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:**
	728	+Uplink channels 1-3 (RX1)
464	464	)))
465	465
	731	+(((
	732	+866.550 - SF10BW125 (RX2)
	733	+)))
466	466
467		-[[image:1654592790040-760.png]]
468	468
469	469
470		-[[image:1654592800389-571.png]]
471	471
	738	+== 2.7  LED Indicator ==
472	472
473		-(% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
	740	+The LLDS12 has an internal LED which is to show the status of different state.
474	474
475		-(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.(% style="color:red" %)(Note: LDDS20 use same payload as LDDS75)(%%)**
	742	+* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
	743	+* Blink once when device transmit a packet.
476	476
477		-[[image:1654851029373-510.png]]
	745	+== 2.8  ​Firmware Change Log ==
478	478
479	479
480		-After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
	748	+**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Firmware/]]
481	481
482		-[[image:image-20220610165129-11.png||height="595" width="1088"]]
483	483
	751	+**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
484	484
485	485
486		-== 2.6  LED Indicator ==
487	487
488		-The LDDS20 has an internal LED which is to show the status of different state.
	755	+= 3.  LiDAR ToF Measurement =
489	489
	757	+== 3.1 Principle of Distance Measurement ==
490	490
491		-* Blink once when device power on.
492		-* The device detects the sensor and flashes 5 times.
493		-* Solid ON for 5 seconds once device successful Join the network.
	759	+The LiDAR probe is based on TOF, namely, Time of Flight principle. To be specific, the product emits modulation wave of near infrared ray on a periodic basis, which will be reflected after contacting object. The product obtains the time of flight by measuring round-trip phase difference and then calculates relative range between the product and the detection object, as shown below.
494	494
495		-Blink once when device transmit a packet.
	761	+[[image:1654831757579-263.png]]
496	496
497	497
498	498
499		-== 2.8  ​Firmware Change Log ==
	765	+== 3.2 Distance Measurement Characteristics ==
500	500
	767	+With optimization of light path and algorithm, The LiDAR probe has minimized influence from external environment on distance measurement performance. Despite that, the range of distance measurement may still be affected by the environment illumination intensity and the reflectivity of detection object. As shown in below:
501	501
	769	+[[image:1654831774373-275.png]]
	770	+
	771	+
502	502	(((
503		-**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
	773	+(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
504	504	)))
505	505
506	506	(((
507		-
	777	+(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
508	508	)))
509	509
510	510	(((
511		-**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
	781	+(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
512	512	)))
513	513
514	514
	785	+(((
	786	+Vertical Coordinates: Represents the radius of light spot for The LiDAR probe at the different distances. The diameter of light spot depends on the FOV of The LiDAR probe (the term of FOV generally refers to the smaller value between the receiving angle and the transmitting angle), which is calculated as follows:
	787	+)))
515	515
516		-== 2.9  Mechanical ==
517	517
	790	+[[image:1654831797521-720.png]]
518	518
519		-[[image:image-20220610172003-1.png]]
520	520
521		-
522		-[[image:image-20220610172003-2.png]]
523		-
524		-
525		-
526		-== 2.10  Battery Analysis ==
527		-
528		-=== 2.10.1  Battery Type ===
529		-
530		-The LDDS75 battery is a combination of a 4000mAh or 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
531		-
532		-
533		-The battery related documents as below:
534		-
535		-* (((
536		-[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
	793	+(((
	794	+In the formula above, d is the diameter of light spot; D is detecting range; β is the value of the receiving angle of The LiDAR probe, 3.6°. Correspondence between the diameter of light spot and detecting range is given in Table below.
537	537	)))
538		-* (((
539		-[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
540		-)))
541		-* (((
542		-[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
543		-)))
544	544
545		- [[image:image-20220610172400-3.png]]
	797	+[[image:1654831810009-716.png]]
546	546
547	547
548		-
549		-=== 2.10.2  Replace the battery ===
550		-
551	551	(((
552		-You can change the battery in the LDDS75.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
	801	+If the light spot reaches two objects with different distances, as shown in Figure 3, the output distance value will be a value between the actual distance values of the two objects. For a high accuracy requirement in practice, the above situation should be noticed to avoid the measurement error.
553	553	)))
554	554
555		-(((
556		-
557		-)))
558	558
559		-(((
560		-The default battery pack of LDDS75 includes a ER18505 plus super capacitor. If user can't find this pack locally, they can find ER18505 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
561		-)))
562	562
	806	+== 3.3 Notice of usage: ==
563	563
	808	+Possible invalid /wrong reading for LiDAR ToF tech:
564	564
565		-= 3.  Configure LDDS75 via AT Command or LoRaWAN Downlink =
	810	+* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
	811	+* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
	812	+* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
	813	+* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
566	566
	815	+= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
	816	+
567	567	(((
568	568	(((
569		-Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
	819	+Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
570	570	)))
571	571	)))
572	572
573	573	* (((
574	574	(((
575		-AT Command Connection: See [[FAQ>>||anchor="H4.A0FAQ"]].
	825	+AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]].
576	576	)))
577	577	)))
578	578	* (((
...	...	@@ -587,7 +587,7 @@
587	587	)))
588	588
589	589	(((
590		-There are two kinds of commands to configure LDDS75, they are:
	840	+There are two kinds of commands to configure LLDS12, they are:
591	591	)))
592	592	)))
593	593
...	...	@@ -628,155 +628,351 @@
628	628
629	629	* (((
630	630	(((
631		-(% style="color:#4f81bd" %)** Commands special design for LDDS75**
	881	+(% style="color:#4f81bd" %)** Commands special design for LLDS12**
632	632	)))
633	633	)))
634	634
635	635	(((
636	636	(((
637		-These commands only valid for LDDS75, as below:
	887	+These commands only valid for LLDS12, as below:
638	638	)))
639	639	)))
640	640
641	641
642	642
643		-== 3.1  Access AT Commands ==
	893	+== 4.1  Set Transmit Interval Time ==
644	644
645		-LDDS75 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LDDS75 for using AT command, as below.
	895	+Feature: Change LoRaWAN End Node Transmit Interval.
646	646
647		-[[image:image-20220610172924-4.png||height="483" width="988"]]
	897	+(% style="color:#037691" %)**AT Command: AT+TDC**
648	648
	899	+[[image:image-20220607171554-8.png]]
649	649
650		-Or if you have below board, use below connection:
651	651
	902	+(((
	903	+(% style="color:#037691" %)**Downlink Command: 0x01**
	904	+)))
652	652
653		-[[image:image-20220610172924-5.png]]
	906	+(((
	907	+Format: Command Code (0x01) followed by 3 bytes time value.
	908	+)))
654	654
	910	+(((
	911	+If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
	912	+)))
655	655
	914	+* (((
	915	+Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	916	+)))
	917	+* (((
	918	+Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	919	+)))
	920	+
	921	+== 4.2  Set Interrupt Mode ==
	922	+
	923	+Feature, Set Interrupt mode for GPIO_EXIT.
	924	+
	925	+(% style="color:#037691" %)**AT Command: AT+INTMOD**
	926	+
	927	+[[image:image-20220610105806-2.png]]
	928	+
	929	+
656	656	(((
657		-In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LDDS75. LDDS75 will output system info once power on as below:
	931	+(% style="color:#037691" %)**Downlink Command: 0x06**
658	658	)))
659	659
	934	+(((
	935	+Format: Command Code (0x06) followed by 3 bytes.
	936	+)))
660	660
661		- [[image:image-20220610172924-6.png||height="601" width="860"]]
	938	+(((
	939	+This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	940	+)))
662	662
	942	+* (((
	943	+Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	944	+)))
	945	+* (((
	946	+Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	947	+)))
663	663
	949	+== 4.3  Get Firmware Version Info ==
664	664
665		-== 3.2  Set Transmit Interval Time ==
	951	+Feature: use downlink to get firmware version.
666	666
667		-Feature: Change LoRaWAN End Node Transmit Interval.
	953	+(% style="color:#037691" %)**Downlink Command: 0x26**
668	668
669		-(% style="color:#037691" %)**AT Command: AT+TDC**
	955	+[[image:image-20220607171917-10.png]]
670	670
671		-[[image:image-20220610173409-7.png]]
	957	+* Reply to the confirmation package: 26 01
	958	+* Reply to non-confirmed packet: 26 00
672	672
	960	+Device will send an uplink after got this downlink command. With below payload:
673	673
	962	+Configures info payload:
	963	+
	964	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
	965	+|=(((
	966	+**Size(bytes)**
	967	+)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
	968	+|**Value**|Software Type|(((
	969	+Frequency
	970	+
	971	+Band
	972	+)))|Sub-band|(((
	973	+Firmware
	974	+
	975	+Version
	976	+)))|Sensor Type|Reserve|(((
	977	+[[Message Type>>||anchor="H2.3.7A0MessageType"]]
	978	+Always 0x02
	979	+)))
	980	+
	981	+**Software Type**: Always 0x03 for LLDS12
	982	+
	983	+
	984	+**Frequency Band**:
	985	+
	986	+*0x01: EU868
	987	+
	988	+*0x02: US915
	989	+
	990	+*0x03: IN865
	991	+
	992	+*0x04: AU915
	993	+
	994	+*0x05: KZ865
	995	+
	996	+*0x06: RU864
	997	+
	998	+*0x07: AS923
	999	+
	1000	+*0x08: AS923-1
	1001	+
	1002	+*0x09: AS923-2
	1003	+
	1004	+*0xa0: AS923-3
	1005	+
	1006	+
	1007	+**Sub-Band**: value 0x00 ~~ 0x08
	1008	+
	1009	+
	1010	+**Firmware Version**: 0x0100, Means: v1.0.0 version
	1011	+
	1012	+
	1013	+**Sensor Type**:
	1014	+
	1015	+0x01: LSE01
	1016	+
	1017	+0x02: LDDS75
	1018	+
	1019	+0x03: LDDS20
	1020	+
	1021	+0x04: LLMS01
	1022	+
	1023	+0x05: LSPH01
	1024	+
	1025	+0x06: LSNPK01
	1026	+
	1027	+0x07: LLDS12
	1028	+
	1029	+
	1030	+
	1031	+= 5.  Battery & How to replace =
	1032	+
	1033	+== 5.1  Battery Type ==
	1034	+
674	674	(((
675		-(% style="color:#037691" %)**Downlink Command: 0x01**
	1036	+LLDS12 is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.
676	676	)))
677	677
678	678	(((
	1040	+The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
	1041	+)))
	1042	+
	1043	+[[image:1654593587246-335.png]]
	1044	+
	1045	+
	1046	+Minimum Working Voltage for the LLDS12:
	1047	+
	1048	+LLDS12:  2.45v ~~ 3.6v
	1049	+
	1050	+
	1051	+
	1052	+== 5.2  Replace Battery ==
	1053	+
679	679	(((
680		-Format: Command Code (0x01) followed by 3 bytes time value.
	1055	+Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
	1056	+)))
681	681
682	682	(((
683		-If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
	1059	+And make sure the positive and negative pins match.
684	684	)))
685	685
686		-* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
687		-* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	1062	+
	1063	+
	1064	+== 5.3  Power Consumption Analyze ==
	1065	+
	1066	+(((
	1067	+Dragino Battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
688	688	)))
	1069	+
	1070	+(((
	1071	+Instruction to use as below:
689	689	)))
690	690
691	691
	1075	+**Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
692	692
	1077	+[[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
693	693
694	694
695		-== 3.3  Set Interrupt Mode ==
	1080	+**Step 2**: Open it and choose
696	696
697		-Feature, Set Interrupt mode for GPIO_EXIT.
	1082	+* Product Model
	1083	+* Uplink Interval
	1084	+* Working Mode
698	698
699		-(% style="color:#037691" %)**Downlink Command: AT+INTMOD**
	1086	+And the Life expectation in difference case will be shown on the right.
700	700
701		-[[image:image-20220610174917-9.png]]
	1088	+[[image:1654593605679-189.png]]
702	702
703	703
704		-(% style="color:#037691" %)**Downlink Command: 0x06**
	1091	+The battery related documents as below:
705	705
706		-Format: Command Code (0x06) followed by 3 bytes.
	1093	+* (((
	1094	+[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
	1095	+)))
	1096	+* (((
	1097	+[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
	1098	+)))
	1099	+* (((
	1100	+[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
	1101	+)))
707	707
	1103	+[[image:image-20220607172042-11.png]]
	1104	+
	1105	+
	1106	+
	1107	+=== 5.3.1  ​Battery Note ===
	1108	+
708	708	(((
709		-This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	1110	+The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
710	710	)))
711	711
712		-* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
713		-* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
714	714
715		-= 4.  FAQ =
716	716
717		-== 4.1  What is the frequency plan for LDDS75? ==
	1115	+=== ​5.3.2  Replace the battery ===
718	718
719		-LDDS75 use the same frequency as other Dragino products. User can see the detail from this link:  [[Introduction>>doc:Main.End Device Frequency Band.WebHome||anchor="H1.Introduction"]]
	1117	+(((
	1118	+You can change the battery in the LLDS12.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
	1119	+)))
720	720
	1121	+(((
	1122	+The default battery pack of LLDS12 includes a ER26500 plus super capacitor. If user can’t find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
	1123	+)))
721	721
722	722
723		-== 4.2  How to change the LoRa Frequency Bands/Region ==
724	724
725		-You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
726		-When downloading the images, choose the required image file for download. ​
	1127	+= 6.  Use AT Command =
727	727
	1129	+== 6.1  Access AT Commands ==
728	728
	1131	+LLDS12 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LLDS12 for using AT command, as below.
729	729
730		-== 4.3  Can I use LDDS75 in condensation environment? ==
	1133	+[[image:1654593668970-604.png]]
731	731
732		-LDDS75 is not suitable to be used in condensation environment. Condensation on the LDDS75 probe will affect the reading and always got 0.
	1135	+**Connection:**
733	733
	1137	+(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
734	734
	1139	+(% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
735	735
736		-= 5.  Trouble Shooting =
	1141	+(% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
737	737
738		-== 5.1  Why I can’t join TTN V3 in US915 / AU915 bands? ==
739	739
740		-It is due to channel mapping. Please see below link:  [[Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
	1144	+(((
	1145	+(((
	1146	+In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
	1147	+)))
741	741
	1149	+(((
	1150	+LLDS12 will output system info once power on as below:
	1151	+)))
	1152	+)))
742	742
743		-== 5.2  AT Command input doesn't work ==
744	744
	1155	+ [[image:1654593712276-618.png]]
	1156	+
	1157	+Valid AT Command please check [[Configure Device>>||anchor="H4.A0ConfigureLLDS12viaATCommandorLoRaWANDownlink"]].
	1158	+
	1159	+
	1160	+= 7.  FAQ =
	1161	+
	1162	+== 7.1  How to change the LoRa Frequency Bands/Region ==
	1163	+
	1164	+You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
	1165	+When downloading the images, choose the required image file for download. ​
	1166	+
	1167	+
	1168	+= 8.  Trouble Shooting =
	1169	+
	1170	+== 8.1  AT Commands input doesn’t work ==
	1171	+
	1172	+
	1173	+(((
745	745	In the case if user can see the console output but can’t type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn’t send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
	1175	+)))
746	746
	1177	+
	1178	+== 8.2  Significant error between the output distant value of LiDAR and actual distance ==
	1179	+
	1180	+
747	747	(((
	1182	+(% style="color:blue" %)**Cause ①**(%%)**：**Due to the physical principles of The LiDAR probe, the above phenomenon is likely to occur if the detection object is the material with high reflectivity (such as mirror, smooth floor tile, etc.) or transparent substance (such as glass and water, etc.)
	1183	+)))
	1184	+
	1185	+(((
	1186	+Troubleshooting: Please avoid use of this product under such circumstance in practice.
	1187	+)))
	1188	+
	1189	+(((
748	748
749	749	)))
750	750
	1193	+(((
	1194	+(% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.
	1195	+)))
751	751
752		-= 6.  Order Info =
	1197	+(((
	1198	+Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
	1199	+)))
753	753
754	754
755		-Part Number **:** (% style="color:blue" %)**LDDS75-XX-YY**
756	756
	1203	+= 9.  Order Info =
757	757
758		-(% style="color:blue" %)**XX**(%%)**: **The default frequency band
759	759
760		-* (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band
761		-* (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band
762		-* (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band
763		-* (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band
764		-* (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band
765		-* (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band
766		-* (% style="color:red" %)**IN865 **(%%)**:**  LoRaWAN IN865 band
767		-* (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band
	1206	+Part Number: (% style="color:blue" %)**LLDS12-XX**
768	768
769		-(% style="color:blue" %)**YY**(%%): Battery Option
770	770
771		-* (% style="color:red" %)**4 **(%%)**: **4000mAh battery
772		-* (% style="color:red" %)**8 **(%%)**:** 8500mAh battery
	1209	+(% style="color:blue" %)**XX**(%%): The default frequency band
773	773
774		-= 7. ​ Packing Info =
	1211	+* (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
	1212	+* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
	1213	+* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
	1214	+* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
	1215	+* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
	1216	+* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
	1217	+* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
	1218	+* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
775	775
	1220	+= 10. ​ Packing Info =
776	776
	1222	+
777	777	**Package Includes**:
778	778
779		-* LDDS75 LoRaWAN Distance Detection Sensor x 1
	1225	+* LLDS12 LoRaWAN LiDAR Distance Sensor x 1
780	780
781	781	**Dimension and weight**:
782	782
...	...	@@ -785,7 +785,7 @@
785	785	* Package Size / pcs : cm
786	786	* Weight / pcs : g
787	787
788		-= 8.  ​Support =
	1234	+= 11.  ​Support =
789	789
790	790	* 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.
791	791	* 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:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]].

1654852175653-550.png

Author

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

Size

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

Content

1654852253176-749.png

Author

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

Size

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

Content

1655254599445-662.png

Author

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

Size

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

Content

1655255122126-327.png

Author

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

Size

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

Content

1655256160324-178.png

Author

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

Size

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

Content

1655257026882-201.png

Author

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

Size

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

Content

1655257698953-697.png

Author

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

Size

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

Content

image-20220610172003-1.png

Author

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

Size

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

Content

image-20220610172003-2.png

Author

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

Size

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

Content

image-20220610172400-3.png

Author

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

Size

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

Content

image-20220610172924-4.png

Author

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

Size

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

Content

image-20220610172924-5.png

Author

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

Size

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

Content

image-20220610172924-6.png

Author

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

Size

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

Content

image-20220610173409-7.png

Author

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

Size

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

Content

image-20220610174836-8.png

Author

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

Size

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

Content

image-20220610174917-9.png

Author

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

Size

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

Content

image-20220615090910-1.png

Author

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

Size

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

Content

image-20220615090910-2.png

Author

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

Size

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

Content

image-20220615091045-3.png

Author

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

Size

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

Content

image-20220615091045-4.png

Author

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

Size

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

Content

image-20220615091045-5.png

Author

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

Size

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

Content

image-20220615091045-6.png

Author

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

Size

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

Content

image-20220615091045-7.png

Author

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

Size

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

Content

image-20220615091045-8.png

Author

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

Size

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

Content

image-20220615091045-9.png

Author

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

Size

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

Content

image-20220615091929-10.png

Author

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

Size

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

Content

image-20220615092010-11.png

Author

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

Size

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

Content

image-20220615092044-12.png

Author

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

Size

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

Content

image-20220615092327-13.png

Author

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

Size

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

Content

image-20220615095102-14.png

Author

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

Size

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

Content

image-20220615100930-15.png

Author

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

Size

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

Content