Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 15 removed)
  • image-20220601142354-2.png
  • image-20220601142452-3.png
  • image-20220601142607-4.png
  • image-20220601142805-5.png
  • image-20220601142936-6.png
  • image-20220601143046-7.png
  • image-20220601143115-8.png
  • image-20220601143201-9.png
  • image-20220601143257-10.png
  • image-20220601143519-1.png
  • image-20220601143642-2.png
  • image-20220601143803-3.png
  • image-20220601143921-4.png
  • image-20220601144053-5.png
  • image-20220601144149-6.png

Details

Page properties

Content

...	...	@@ -1,4 +1,5 @@
1		-**Table of Contents:**
	1	+(% class="wikigeneratedid" %)
	2	+ **Contents:**
2	2
3	3	{{toc/}}
4	4
...	...	@@ -9,13 +9,11 @@
9	9
10	10	= **1. Introduction** =
11	11
12		-
13	13	This article provide the examples for RS485-LN to connect to different type of RS485 sensors.
14	14
15	15
16	16	== **1.1 Example 1: Connect to Leak relay and VFD** ==
17	17
18		-
19	19	This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to Relay and VFD and communicate with Mobile. The structure is like below:
20	20
21	21	[[image:image-20220527091852-1.png]]
...	...	@@ -29,19 +29,18 @@
29	29	Connection
30	30
31	31
32		-(% style="color:blue" %)**Related documents:**
	31	+Related documents:
33	33
34		-* System Structure:  [[Solar Pump with Dragino>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/||style="background-color: rgb(255, 255, 255);"]]
35		-* Explanation on how to integrate to Node-red and to the Mobile Phone, and with link to the Github code:  [[Configure Manual>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/||style="background-color: rgb(255, 255, 255);"]]
	33	+* [[Solar Pump with Dragino>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/]] : System Structure
	34	+* [[Configure Manual>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/]] : Explanation on how to integrate to Node-red and to the Mobile Phone, and with link to the Github code.
36	36	* [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
37	37
38	38
	38	+
39	39	== **1.2 Example 2: Connect to Pulse Counter** ==
40	40
41		-
42	42	This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to Pulse Counter and communicate with Mobile. This example and example 2 compose the structure for a farm IoT solution. The structure is like below:
43	43
44		-
45	45	[[image:image-20220527092058-3.png]]
46	46
47	47	Connection
...	...	@@ -53,21 +53,17 @@
53	53	Connection
54	54
55	55
56		-(% style="color:blue" %)**Related documents:**
57		-
58		-* Configure Document:  [[Pickdata MIO40 water pulse counter to LoRa with Dragino RS485-LN>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Pulse-Counter/]]
	54	+* [[Pickdata MIO40 water pulse counter to LoRa with Dragino RS485-LN>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Pulse-Counter/]] : Configure Document
59	59	* [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
60	60
	57	+== ==
61	61
62		-
63	63	== **1.3 Example3: Use RS485-LN with energy meters** ==
64	64
65		-
66	66	=== **1.3.1 OverView** ===
67	67
68		-
69	69	(((
70		-(% style="color:red" %)**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
	64	+**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
71	71	)))
72	72
73	73	(((
...	...	@@ -81,9 +81,7 @@
81	81
82	82
83	83	(((
84		-(% style="color:blue" %)**How to connect with Energy Meter：**
85		-
86		-
	78	+How to connect with Energy Meter：
87	87	)))
88	88
89	89	(((
...	...	@@ -111,6 +111,7 @@
111	111	Connection2
112	112
113	113
	106	+
114	114	[[image:image-20220527092555-7.png]]
115	115
116	116	Connection3
...	...	@@ -118,13 +118,15 @@
118	118
119	119	=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
120	120
121		-
122	122	If the user needs to read the parameters of the electric energy meter and use the modbus command,please refer to the appendix of the MODBUS communication protocol in the user manual of the energy meter.
123	123
124		-[[image:image-20220601143257-10.png]]
	116	+[[image:image-20220527092629-8.png]]
125	125
126	126
127		-(% style="color:blue" %)**Example:**(%%)  AT+COMMAND1=01 03 00 00 00 01 84 0A
	119	+(% class="box infomessage" %)
	120	+(((
	121	+**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A
	122	+)))
128	128
129	129	* The first byte : slave address code (=001～247)
130	130	* The second byte : read register value function code
...	...	@@ -133,12 +133,12 @@
133	133	* 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
134	134
135	135	(((
136		-
137		-
138		-
139	139	How to parse the reading of the return command of the parameter：
	132	+)))
140	140
141		-(% style="color:blue" %)**Example:**(%%) RETURN1：01 03 02 08 FD 7E 05
	134	+(% class="box infomessage" %)
	135	+(((
	136	+**Example:** RETURN1：01 03 02 08 FD 7E 05
142	142	)))
143	143
144	144	* The first byte ARD: slave address code (=001～254)
...	...	@@ -151,27 +151,22 @@
151	151	(% class="wikigeneratedid" %)
152	152	(((
153	153
154		-
155		-
156		-
157	157	)))
158	158
159	159	=== **1.3.3 How to configure RS485-LN and parse output commands** ===
160	160
161		-
162	162	RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
163	163
164	164
165		-==== **1.3.3.1 via AT COMMAND** ====
	156	+==== **1.3.3.1 via AT COMMAND:** ====
166	166
	158	+First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
167	167
168		-First, we can use (% style="color:blue" %)**AT+CFGDEV**(%%) to get the return value, and we can also judge whether the input parameters are correct.
169		-
170	170	(((
171	171	If the configured parameters and commands are incorrect, the return value is not obtained.
172	172	)))
173	173
174		-[[image:image-20220601143201-9.png]]
	164	+[[image:image-20220527092748-9.png]]
175	175
176	176	AT COMMAND
177	177
...	...	@@ -178,7 +178,7 @@
178	178
179	179	(% class="box infomessage" %)
180	180	(((
181		- **AT+DATACUTx **:  This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
	171	+ AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
182	182	)))
183	183
184	184	a:  length for the return of AT+COMMAND
...	...	@@ -187,7 +187,7 @@
187	187
188	188	c:  define the position for valid value.
189	189
190		-[[image:image-20220601143115-8.png]]
	180	+[[image:image-20220527092936-10.png]]
191	191
192	192	AT COMMAND
193	193
...	...	@@ -196,7 +196,7 @@
196	196	PAYLOAD is available after the valid value is intercepted.
197	197
198	198
199		-[[image:image-20220601143046-7.png]]
	189	+[[image:image-20220527093059-11.png]]
200	200
201	201	AT COMMAND
202	202
...	...	@@ -204,7 +204,7 @@
204	204
205	205	You can get configured PAYLOAD on TTN.
206	206
207		-[[image:image-20220601143519-1.png]]
	197	+[[image:image-20220527093133-12.png]]
208	208
209	209	(((
210	210	AT COMMAND
...	...	@@ -215,52 +215,52 @@
215	215	)))
216	216
217	217	(((
218		-(% style="color:blue" %)**Example**:
	208	+(% style="color:#4f81bd" %)**Example**:
219	219
220		-**CMD1:** Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
	210	+CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
221	221	)))
222	222
223	223	(((
224		-RETURN1: 01 03 02 00 02 39 85 00 00(return data)
	214	+RETURN1:01 03 02 00 02 39 85 00 00(return data)
225	225	)))
226	226
227	227	(((
228		-AT+DATACUT1: 9,1,4+5+6+7 Take the return value 00 02 39 85 as the valid value of reading current data and used to splice payload.
	218	+AT+DATACUT1:9,1,4+5+6+7 Take the return value 00 02 39 85 as the valid value of reading current data and used to splice payload.
229	229
230	230
231	231	)))
232	232
233	233	(((
234		-**CMD2: **Read voltage data with MODBUS command. address: 0x00 AT+COMMAND2= 01 03 00 00 00 01,1
	224	+CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1
235	235	)))
236	236
237	237	(((
238		-RETURN2: 01 03 02 08 DC BE 1D(return data)
	228	+RETURN2:01 03 02 08 DC BE 1D(return data)
239	239	)))
240	240
241	241	(((
242		-AT+DATACUT2: 7,1,4+5 Take the return value 08 DC as the valid value of reading voltage data and used to splice payload.
	232	+AT+DATACUT2:7,1,4+5 Take the return value 08 DC as the valid value of reading voltage data and used to splice payload.
243	243
244	244
245	245	)))
246	246
247	247	(((
248		-**CMD3:** Read total active energy data with MODBUS command. address: 0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
	238	+CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
249	249	)))
250	250
251	251	(((
252		-RETURN3: 01 03 04 00 00 00 44 FA 00(return data)
	242	+RETURN3:01 03 04 00 00 00 44 FA 00(return data)
253	253	)))
254	254
255	255	(((
256		-AT+DATACUT3: 9,1,4+5+6+7 Take the return value 00 00 00 44 as the valid value of reading total active energy data and used to splice payload.
	246	+AT+DATACUT3:9,1,4+5+6+7 Take the return value 00 00 00 44 as the valid value of reading total active energy data and used to splice payload.
257	257	)))
258	258
259	259	(((
260		-Payload: 01 00 02 39 85 08 DC 00 00 00 44
	250	+Payload:01 00 02 39 85 08 DC 00 00 00 44
261	261	)))
262	262
263		-[[image:image-20220601142936-6.png]]
	253	+[[image:image-20220527093204-13.png]]
264	264
265	265	AT COMMAND
266	266
...	...	@@ -268,14 +268,14 @@
268	268	(% style="color:#4f81bd" %)**01 is device address,00 02 is the current, 08 DC is the voltage,00 00 00 44 is the total active energy.**
269	269
270	270
271		-[[image:image-20220601143642-2.png]]
272	272
	262	+[[image:image-20220527093251-14.png]]
	263	+
273	273	AT COMMAND
274	274
275	275
276	276	==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
277	277
278		-
279	279	[[image:image-20220527093358-15.png]]
280	280
281	281	(((
...	...	@@ -298,7 +298,7 @@
298	298	)))
299	299
300	300	(((
301		-(% style="color:red" %)Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
	291	+Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
302	302	)))
303	303
304	304	(((
...	...	@@ -336,7 +336,7 @@
336	336	(((
337	337
338	338
339		-(% style="color:blue" %)**Example:**
	329	+(% style="color:#4f81bd" %)**Example:**
340	340	)))
341	341
342	342	(((
...	...	@@ -343,31 +343,31 @@
343	343	**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
344	344	)))
345	345
346		-[[image:image-20220601144149-6.png]]
	336	+[[image:image-20220527093430-16.png]]
347	347
348	348	DOWNLINK
349	349
350	350
351	351
352		-[[image:image-20220601143803-3.png]]
	342	+[[image:image-20220527093508-17.png]]
353	353
354	354	DOWNLINK
355	355
356	356
357	357
358		-[[image:image-20220601144053-5.png]]
	348	+[[image:image-20220527093530-18.png]]
359	359
360	360	DOWNLINK
361	361
362	362
363	363
364		-[[image:image-20220601143921-4.png]]
	354	+[[image:image-20220527093607-19.png]]
365	365
366	366	DOWNLINK
367	367
368	368
369	369
370		-[[image:image-20220601142805-5.png]]
	360	+[[image:image-20220527093628-20.png]]
371	371
372	372	DOWNLINK
373	373
...	...	@@ -392,8 +392,6 @@
392	392
393	393	(((
394	394	check digit: Even
395		-
396		-
397	397	)))
398	398
399	399	[[image:image-20220527093708-21.png]]
...	...	@@ -410,18 +410,14 @@
410	410
411	411	(((
412	412	The configuration command is consistent with the AT command, input the hexadecimal command directly into the serial port, and the serial port will output the command.
413		-
414		-
415	415	)))
416	416
417	417	(((
418		-(% style="color:blue" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
	404	+(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
419	419	)))
420	420
421	421	(((
422	422	output：01 03 04 00 00 00 42 7A 02
423		-
424		-
425	425	)))
426	426
427	427	[[image:image-20220527093821-23.png]]
...	...	@@ -431,7 +431,6 @@
431	431
432	432	=== **1.3.5 How to configure multiple devices and modify device addresses** ===
433	433
434		-
435	435	If users need to read the parameters of multiple energy meters, they need to modify the device address, because the default device address of each energy meter is 01.
436	436
437	437	(((
...	...	@@ -443,14 +443,12 @@
443	443	[[image:image-20220601142044-1.png]]
444	444
445	445
446		-(% style="color:blue" %)**Example**(%%): These two meters are examples of setting parameters and device addresses.
	429	+**Example**:These two meters are examples of setting parameters and device addresses.
447	447
448	448	[[image:image-20220527093950-25.png]]
449	449
450		-
451	451	[[image:image-20220527094028-26.png]]
452	452
453		-
454	454	(((
455	455	(((
456	456	First of all, since the default device address of the energy meter is 01, the configuration of two energy meters will conflict, so we first connect an energy meter and configure the device address.
...	...	@@ -459,7 +459,7 @@
459	459
460	460	(((
461	461	(((
462		-We can use **AT+CFGDEV** to set the device address.
	443	+We can use AT+CFGDEV to set the device address.
463	463	)))
464	464	)))
465	465
...	...	@@ -469,9 +469,8 @@
469	469	)))
470	470	)))
471	471
472		-[[image:image-20220601142354-2.png]]
	453	+[[image:image-20220527094100-27.png]]
473	473
474		-
475	475	(% class="box infomessage" %)
476	476	(((
477	477	**AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
...	...	@@ -497,12 +497,11 @@
497	497
498	498	Its default device address is 01, and the following are the parameters for configuring two energy meters.
499	499
500		-[[image:image-20220601142452-3.png]]
	480	+[[image:image-20220527094150-28.png]]
501	501
502	502
503		-[[image:image-20220601142607-4.png]]
	483	+[[image:image-20220527094224-29.png]]
504	504
505		-
506	506	**PAYLOAD:01 08 DF 43 62**
507	507
508	508	* 08 DF is the valid value of the meter with device address 02.
...	...	@@ -511,42 +511,33 @@
511	511
512	512	== 1.4 Example 4: Circuit Breaker Remote Open Close ==
513	513
	493	+This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to SCHNEIDER SMART and Monitor and control your cabinet remotely with no wires and with Dragino RS485-LN LoRaWAN technology. The structure is like below:
514	514
515		-This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to SCHNEIDER SMART and Monitor and control your cabinet remotely with no wires and with Dragino RS485-LN LoRaWAN technology.
516		-
517		-The structure is like below:
518		-
519	519	[[image:image-20220527094330-30.png]]
520	520
521	521	Connection
522	522
	499	+* [[Circuit Breaker Remote Open Close>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Circuit_Breaker_Remote_Open_Close/]] : Configure Documen
523	523
524		-* Configure Documen:  [[Circuit Breaker Remote Open Close>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Circuit_Breaker_Remote_Open_Close/]]
525	525
526		-
527	527	== 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
528	528
529		-
530	530	This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-BL to connect to SEM Three Energy Meter and send the data to mobile phone for remote minitor. The structure is like below:
531	531
532		-* Configure Document For RS485-BL:  [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Application_Note/&file=Dragino%20RS485BL%20and%20pickdata%20SEM%20Three%20v1.pdf||style="background-color: rgb(255, 255, 255);"]]
533		-* Configure Document for RS485-LN:  [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/SEM_Three_Energy_Meter/&file=SEM%20three%20and%20Dragino%20RS485-LN%20v1.pdf]]
	506	+* [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Application_Note/&file=Dragino%20RS485BL%20and%20pickdata%20SEM%20Three%20v1.pdf]] : Configure Document For RS485-BL
534	534
	508	+* [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/SEM_Three_Energy_Meter/&file=SEM%20three%20and%20Dragino%20RS485-LN%20v1.pdf]] : Configure Document for RS485-LN
535	535
536		-== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN ==
	510	+== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
537	537
538		-
539	539	This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to CEM C31 485-T1-MID and send the data for remote minitor. The structure is like below:
540	540
541		-* Configure Document For RS485-LN:  [[CEM C31 485-T1-MID>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/ELECTRICAL%20CABINET/&file=ELECTRICAL%20CABINET%20READINGS.pdf||style="background-color: rgb(255, 255, 255);"]]
	514	+* [[CEM C31 485-T1-MID>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/ELECTRICAL%20CABINET/&file=ELECTRICAL%20CABINET%20READINGS.pdf]] : Configure Document For RS485-LN
542	542
	516	+== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
543	543
544		-== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
545		-
546		-
547	547	[[image:image-20220527094556-31.png]]
548	548
549	549	Network Structure
550	550
551		-
552	552	* [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]

image-20220601142354-2.png

Author

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

Size

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

Content

image-20220601142452-3.png

Author

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

Size

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

Content

image-20220601142607-4.png

Author

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

Size

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

Content

image-20220601142805-5.png

Author

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

Size

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

Content

image-20220601142936-6.png

Author

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

Size

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

Content

image-20220601143046-7.png

Author

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

Size

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

Content

image-20220601143115-8.png

Author

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

Size

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

Content

image-20220601143201-9.png

Author

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

Size

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

Content

image-20220601143257-10.png

Author

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

Size

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

Content

image-20220601143519-1.png

Author

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

Size

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

Content

image-20220601143642-2.png

Author

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

Size

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

Content

image-20220601143803-3.png

Author

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

Size

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

Content

image-20220601143921-4.png

Author

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

Size

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

Content

image-20220601144053-5.png

Author

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

Size

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

Content

image-20220601144149-6.png

Author

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

Size

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

Content