Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 13 removed)
  • 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,10 +29,10 @@
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
...	...	@@ -39,10 +39,8 @@
39	39
40	40	== **1.2 Example 2: Connect to Pulse Counter** ==
41	41
42		-
43	43	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:
44	44
45		-
46	46	[[image:image-20220527092058-3.png]]
47	47
48	48	Connection
...	...	@@ -54,22 +54,17 @@
54	54	Connection
55	55
56	56
57		-(% style="color:blue" %)**Related documents:**
58		-
59		-* 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
60	60	* [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
61	61
	57	+== ==
62	62
63		-
64		-
65	65	== **1.3 Example3: Use RS485-LN with energy meters** ==
66	66
67		-
68	68	=== **1.3.1 OverView** ===
69	69
70		-
71	71	(((
72		-(% 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.
73	73	)))
74	74
75	75	(((
...	...	@@ -83,9 +83,7 @@
83	83
84	84
85	85	(((
86		-(% style="color:blue" %)**How to connect with Energy Meter：**
87		-
88		-
	78	+How to connect with Energy Meter：
89	89	)))
90	90
91	91	(((
...	...	@@ -121,13 +121,15 @@
121	121
122	122	=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
123	123
124		-
125	125	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.
126	126
127		-[[image:image-20220601143257-10.png]]
	116	+[[image:image-20220527092629-8.png]]
128	128
129	129
130		-(% 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	+)))
131	131
132	132	* The first byte : slave address code (=001～247)
133	133	* The second byte : read register value function code
...	...	@@ -136,12 +136,12 @@
136	136	* 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
137	137
138	138	(((
139		-
140		-
141		-
142	142	How to parse the reading of the return command of the parameter：
	132	+)))
143	143
144		-(% 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
145	145	)))
146	146
147	147	* The first byte ARD: slave address code (=001～254)
...	...	@@ -154,27 +154,22 @@
154	154	(% class="wikigeneratedid" %)
155	155	(((
156	156
157		-
158		-
159		-
160	160	)))
161	161
162	162	=== **1.3.3 How to configure RS485-LN and parse output commands** ===
163	163
164		-
165	165	RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
166	166
167	167
168		-==== **1.3.3.1 via AT COMMAND** ====
	156	+==== **1.3.3.1 via AT COMMAND:** ====
169	169
	158	+First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
170	170
171		-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.
172		-
173	173	(((
174	174	If the configured parameters and commands are incorrect, the return value is not obtained.
175	175	)))
176	176
177		-[[image:image-20220601143201-9.png]]
	164	+[[image:image-20220527092748-9.png]]
178	178
179	179	AT COMMAND
180	180
...	...	@@ -181,7 +181,7 @@
181	181
182	182	(% class="box infomessage" %)
183	183	(((
184		- **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
185	185	)))
186	186
187	187	a:  length for the return of AT+COMMAND
...	...	@@ -190,7 +190,7 @@
190	190
191	191	c:  define the position for valid value.
192	192
193		-[[image:image-20220601143115-8.png]]
	180	+[[image:image-20220527092936-10.png]]
194	194
195	195	AT COMMAND
196	196
...	...	@@ -199,7 +199,7 @@
199	199	PAYLOAD is available after the valid value is intercepted.
200	200
201	201
202		-[[image:image-20220601143046-7.png]]
	189	+[[image:image-20220527093059-11.png]]
203	203
204	204	AT COMMAND
205	205
...	...	@@ -207,7 +207,7 @@
207	207
208	208	You can get configured PAYLOAD on TTN.
209	209
210		-[[image:image-20220601143519-1.png]]
	197	+[[image:image-20220527093133-12.png]]
211	211
212	212	(((
213	213	AT COMMAND
...	...	@@ -218,52 +218,52 @@
218	218	)))
219	219
220	220	(((
221		-(% style="color:blue" %)**Example**:
	208	+(% style="color:#4f81bd" %)**Example**:
222	222
223		-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
224	224	)))
225	225
226	226	(((
227		-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)
228	228	)))
229	229
230	230	(((
231		-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.
232	232
233	233
234	234	)))
235	235
236	236	(((
237		-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
238	238	)))
239	239
240	240	(((
241		-RETURN2: 01 03 02 08 DC BE 1D(return data)
	228	+RETURN2:01 03 02 08 DC BE 1D(return data)
242	242	)))
243	243
244	244	(((
245		-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.
246	246
247	247
248	248	)))
249	249
250	250	(((
251		-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
252	252	)))
253	253
254	254	(((
255		-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)
256	256	)))
257	257
258	258	(((
259		-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.
260	260	)))
261	261
262	262	(((
263		-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
264	264	)))
265	265
266		-[[image:image-20220601142936-6.png]]
	253	+[[image:image-20220527093204-13.png]]
267	267
268	268	AT COMMAND
269	269
...	...	@@ -271,14 +271,14 @@
271	271	(% 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.**
272	272
273	273
274		-[[image:image-20220601143642-2.png]]
275	275
	262	+[[image:image-20220527093251-14.png]]
	263	+
276	276	AT COMMAND
277	277
278	278
279	279	==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
280	280
281		-
282	282	[[image:image-20220527093358-15.png]]
283	283
284	284	(((
...	...	@@ -301,7 +301,7 @@
301	301	)))
302	302
303	303	(((
304		-(% 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.
305	305	)))
306	306
307	307	(((
...	...	@@ -339,7 +339,7 @@
339	339	(((
340	340
341	341
342		-(% style="color:blue" %)**Example:**
	329	+(% style="color:#4f81bd" %)**Example:**
343	343	)))
344	344
345	345	(((
...	...	@@ -346,31 +346,31 @@
346	346	**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
347	347	)))
348	348
349		-[[image:image-20220601144149-6.png]]
	336	+[[image:image-20220527093430-16.png]]
350	350
351	351	DOWNLINK
352	352
353	353
354	354
355		-[[image:image-20220601143803-3.png]]
	342	+[[image:image-20220527093508-17.png]]
356	356
357	357	DOWNLINK
358	358
359	359
360	360
361		-[[image:image-20220601144053-5.png]]
	348	+[[image:image-20220527093530-18.png]]
362	362
363	363	DOWNLINK
364	364
365	365
366	366
367		-[[image:image-20220601143921-4.png]]
	354	+[[image:image-20220527093607-19.png]]
368	368
369	369	DOWNLINK
370	370
371	371
372	372
373		-[[image:image-20220601142805-5.png]]
	360	+[[image:image-20220527093628-20.png]]
374	374
375	375	DOWNLINK
376	376
...	...	@@ -395,8 +395,6 @@
395	395
396	396	(((
397	397	check digit: Even
398		-
399		-
400	400	)))
401	401
402	402	[[image:image-20220527093708-21.png]]
...	...	@@ -413,18 +413,14 @@
413	413
414	414	(((
415	415	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.
416		-
417		-
418	418	)))
419	419
420	420	(((
421		-(% 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
422	422	)))
423	423
424	424	(((
425	425	output：01 03 04 00 00 00 42 7A 02
426		-
427		-
428	428	)))
429	429
430	430	[[image:image-20220527093821-23.png]]
...	...	@@ -434,7 +434,6 @@
434	434
435	435	=== **1.3.5 How to configure multiple devices and modify device addresses** ===
436	436
437		-
438	438	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.
439	439
440	440	(((
...	...	@@ -446,14 +446,12 @@
446	446	[[image:image-20220601142044-1.png]]
447	447
448	448
449		-(% 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.
450	450
451	451	[[image:image-20220527093950-25.png]]
452	452
453		-
454	454	[[image:image-20220527094028-26.png]]
455	455
456		-
457	457	(((
458	458	(((
459	459	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.
...	...	@@ -462,7 +462,7 @@
462	462
463	463	(((
464	464	(((
465		-We can use **AT+CFGDEV** to set the device address.
	443	+We can use AT+CFGDEV to set the device address.
466	466	)))
467	467	)))
468	468
...	...	@@ -474,7 +474,6 @@
474	474
475	475	[[image:image-20220601142354-2.png]]
476	476
477		-
478	478	(% class="box infomessage" %)
479	479	(((
480	480	**AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
...	...	@@ -503,9 +503,8 @@
503	503	[[image:image-20220601142452-3.png]]
504	504
505	505
506		-[[image:image-20220601142607-4.png]]
	483	+[[image:image-20220527094224-29.png]]
507	507
508		-
509	509	**PAYLOAD:01 08 DF 43 62**
510	510
511	511	* 08 DF is the valid value of the meter with device address 02.
...	...	@@ -512,48 +512,35 @@
512	512	* 43 62 is the valid value of the meter with device address 01.
513	513
514	514
515		-
516	516	== 1.4 Example 4: Circuit Breaker Remote Open Close ==
517	517
	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:
518	518
519		-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.
520		-
521		-The structure is like below:
522		-
523	523	[[image:image-20220527094330-30.png]]
524	524
525	525	Connection
526	526
	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
527	527
528		-* 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/]]
529	529
530		-
531		-
532	532	== 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
533	533
534		-
535	535	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:
536	536
537		-* 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);"]]
538		-* 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
539	539
	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
540	540
	510	+== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
541	541
542		-== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN ==
543		-
544		-
545	545	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:
546	546
547		-* 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
548	548
	516	+== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
549	549
550		-
551		-== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
552		-
553		-
554	554	[[image:image-20220527094556-31.png]]
555	555
556	556	Network Structure
557	557
558		-
559	559	* [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]

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