Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 10 removed)
  • 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,6 +1,5 @@
1	1	(% class="wikigeneratedid" %)
2		-*
3		-** Table of** **Contents:
	2	+ **Contents:**
4	4
5	5	{{toc/}}
6	6
...	...	@@ -11,13 +11,11 @@
11	11
12	12	= **1. Introduction** =
13	13
14		-
15	15	This article provide the examples for RS485-LN to connect to different type of RS485 sensors.
16	16
17	17
18	18	== **1.1 Example 1: Connect to Leak relay and VFD** ==
19	19
20		-
21	21	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:
22	22
23	23	[[image:image-20220527091852-1.png]]
...	...	@@ -37,12 +37,12 @@
37	37	* [[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.
38	38	* [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
39	39
40		-== **1.2 Example 2: Connect to Pulse Counter** ==
41	41
42	42
	39	+== **1.2 Example 2: Connect to Pulse Counter** ==
	40	+
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,16 +54,17 @@
54	54	Connection
55	55
56	56
57		-* 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
58	58	* [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
59	59
	57	+== ==
	58	+
60	60	== **1.3 Example3: Use RS485-LN with energy meters** ==
61	61
62	62	=== **1.3.1 OverView** ===
63	63
64		-
65	65	(((
66		-(% 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.
67	67	)))
68	68
69	69	(((
...	...	@@ -77,9 +77,7 @@
77	77
78	78
79	79	(((
80		-**How to connect with Energy Meter：**
81		-
82		-
	78	+How to connect with Energy Meter：
83	83	)))
84	84
85	85	(((
...	...	@@ -115,13 +115,15 @@
115	115
116	116	=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
117	117
118		-
119	119	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.
120	120
121		-[[image:image-20220601143257-10.png]]
	116	+[[image:image-20220527092629-8.png]]
122	122
123	123
124		-(% 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	+)))
125	125
126	126	* The first byte : slave address code (=001～247)
127	127	* The second byte : read register value function code
...	...	@@ -130,12 +130,12 @@
130	130	* 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
131	131
132	132	(((
133		-
134		-
135		-
136	136	How to parse the reading of the return command of the parameter：
	132	+)))
137	137
138		-(% 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
139	139	)))
140	140
141	141	* The first byte ARD: slave address code (=001～254)
...	...	@@ -148,27 +148,22 @@
148	148	(% class="wikigeneratedid" %)
149	149	(((
150	150
151		-
152		-
153		-
154	154	)))
155	155
156	156	=== **1.3.3 How to configure RS485-LN and parse output commands** ===
157	157
158		-
159	159	RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
160	160
161	161
162		-==== **1.3.3.1 via AT COMMAND** ====
	156	+==== **1.3.3.1 via AT COMMAND:** ====
163	163
	158	+First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
164	164
165		-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.
166		-
167	167	(((
168	168	If the configured parameters and commands are incorrect, the return value is not obtained.
169	169	)))
170	170
171		-[[image:image-20220601143201-9.png]]
	164	+[[image:image-20220527092748-9.png]]
172	172
173	173	AT COMMAND
174	174
...	...	@@ -175,7 +175,7 @@
175	175
176	176	(% class="box infomessage" %)
177	177	(((
178		- **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
179	179	)))
180	180
181	181	a:  length for the return of AT+COMMAND
...	...	@@ -184,7 +184,7 @@
184	184
185	185	c:  define the position for valid value.
186	186
187		-[[image:image-20220601143115-8.png]]
	180	+[[image:image-20220527092936-10.png]]
188	188
189	189	AT COMMAND
190	190
...	...	@@ -193,7 +193,7 @@
193	193	PAYLOAD is available after the valid value is intercepted.
194	194
195	195
196		-[[image:image-20220601143046-7.png]]
	189	+[[image:image-20220527093059-11.png]]
197	197
198	198	AT COMMAND
199	199
...	...	@@ -201,7 +201,7 @@
201	201
202	202	You can get configured PAYLOAD on TTN.
203	203
204		-[[image:image-20220601143519-1.png]]
	197	+[[image:image-20220527093133-12.png]]
205	205
206	206	(((
207	207	AT COMMAND
...	...	@@ -212,49 +212,49 @@
212	212	)))
213	213
214	214	(((
215		-(% style="color:blue" %)**Example**:
	208	+(% style="color:#4f81bd" %)**Example**:
216	216
217		-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
218	218	)))
219	219
220	220	(((
221		-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)
222	222	)))
223	223
224	224	(((
225		-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.
226	226
227	227
228	228	)))
229	229
230	230	(((
231		-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
232	232	)))
233	233
234	234	(((
235		-RETURN2: 01 03 02 08 DC BE 1D(return data)
	228	+RETURN2:01 03 02 08 DC BE 1D(return data)
236	236	)))
237	237
238	238	(((
239		-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.
240	240
241	241
242	242	)))
243	243
244	244	(((
245		-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
246	246	)))
247	247
248	248	(((
249		-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)
250	250	)))
251	251
252	252	(((
253		-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.
254	254	)))
255	255
256	256	(((
257		-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
258	258	)))
259	259
260	260	[[image:image-20220601142936-6.png]]
...	...	@@ -265,14 +265,14 @@
265	265	(% 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.**
266	266
267	267
268		-[[image:image-20220601143642-2.png]]
269	269
	262	+[[image:image-20220527093251-14.png]]
	263	+
270	270	AT COMMAND
271	271
272	272
273	273	==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
274	274
275		-
276	276	[[image:image-20220527093358-15.png]]
277	277
278	278	(((
...	...	@@ -295,7 +295,7 @@
295	295	)))
296	296
297	297	(((
298		-(% 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.
299	299	)))
300	300
301	301	(((
...	...	@@ -333,7 +333,7 @@
333	333	(((
334	334
335	335
336		-(% style="color:blue" %)**Example:**
	329	+(% style="color:#4f81bd" %)**Example:**
337	337	)))
338	338
339	339	(((
...	...	@@ -340,25 +340,25 @@
340	340	**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
341	341	)))
342	342
343		-[[image:image-20220601144149-6.png]]
	336	+[[image:image-20220527093430-16.png]]
344	344
345	345	DOWNLINK
346	346
347	347
348	348
349		-[[image:image-20220601143803-3.png]]
	342	+[[image:image-20220527093508-17.png]]
350	350
351	351	DOWNLINK
352	352
353	353
354	354
355		-[[image:image-20220601144053-5.png]]
	348	+[[image:image-20220527093530-18.png]]
356	356
357	357	DOWNLINK
358	358
359	359
360	360
361		-[[image:image-20220601143921-4.png]]
	354	+[[image:image-20220527093607-19.png]]
362	362
363	363	DOWNLINK
364	364
...	...	@@ -389,8 +389,6 @@
389	389
390	390	(((
391	391	check digit: Even
392		-
393		-
394	394	)))
395	395
396	396	[[image:image-20220527093708-21.png]]
...	...	@@ -407,18 +407,14 @@
407	407
408	408	(((
409	409	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.
410		-
411		-
412	412	)))
413	413
414	414	(((
415		-(% 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
416	416	)))
417	417
418	418	(((
419	419	output：01 03 04 00 00 00 42 7A 02
420		-
421		-
422	422	)))
423	423
424	424	[[image:image-20220527093821-23.png]]
...	...	@@ -428,7 +428,6 @@
428	428
429	429	=== **1.3.5 How to configure multiple devices and modify device addresses** ===
430	430
431		-
432	432	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.
433	433
434	434	(((
...	...	@@ -440,11 +440,10 @@
440	440	[[image:image-20220601142044-1.png]]
441	441
442	442
443		-(% 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.
444	444
445	445	[[image:image-20220527093950-25.png]]
446	446
447		-
448	448	[[image:image-20220527094028-26.png]]
449	449
450	450	(((
...	...	@@ -502,6 +502,7 @@
502	502	* 08 DF is the valid value of the meter with device address 02.
503	503	* 43 62 is the valid value of the meter with device address 01.
504	504
	490	+
505	505	== 1.4 Example 4: Circuit Breaker Remote Open Close ==
506	506
507	507	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:
...	...	@@ -512,6 +512,7 @@
512	512
513	513	* [[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
514	514
	501	+
515	515	== 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
516	516
517	517	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:
...	...	@@ -520,6 +520,8 @@
520	520
521	521	* [[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
522	522
	510	+
	511	+
523	523	== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
524	524
525	525	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:
...	...	@@ -526,6 +526,8 @@
526	526
527	527	* [[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
528	528
	518	+
	519	+
529	529	== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
530	530
531	531	[[image:image-20220527094556-31.png]]

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