Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 16 added, 0 removed)
  • image-20220601142044-1.png
  • 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,5 +1,6 @@
1	1	(% class="wikigeneratedid" %)
2		- **Contents:**
	2	+*
	3	+** Table of** **Contents:
3	3
4	4	{{toc/}}
5	5
...	...	@@ -10,11 +10,13 @@
10	10
11	11	= **1. Introduction** =
12	12
	14	+
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
	20	+
18	18	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:
19	19
20	20	[[image:image-20220527091852-1.png]]
...	...	@@ -34,31 +34,33 @@
34	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.
35	35	* [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
36	36
37		-
38	38	== **1.2 Example 2: Connect to Pulse Counter** ==
39	39
	42	+
40	40	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:
41	41
	45	+
42	42	[[image:image-20220527092058-3.png]]
43	43
44	44	Connection
45	45
46	46
	51	+
47	47	[[image:image-20220527092146-4.png]]
48	48
49	49	Connection
50	50
51		-* [[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
	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/]]
52	52	* [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
53	53
54		-== ==
55		-
56	56	== **1.3 Example3: Use RS485-LN with energy meters** ==
57	57
58	58	=== **1.3.1 OverView** ===
59	59
	64	+
60	60	(((
61		-**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
	66	+(% style="color:red" %)**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
62	62	)))
63	63
64	64	(((
...	...	@@ -70,8 +70,11 @@
70	70	Connection1
71	71
72	72
	78	+
73	73	(((
74		-How to connect with Energy Meter：
	80	+**How to connect with Energy Meter：**
	81	+
	82	+
75	75	)))
76	76
77	77	(((
...	...	@@ -99,6 +99,7 @@
99	99	Connection2
100	100
101	101
	110	+
102	102	[[image:image-20220527092555-7.png]]
103	103
104	104	Connection3
...	...	@@ -106,15 +106,13 @@
106	106
107	107	=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
108	108
	118	+
109	109	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.
110	110
111		-[[image:image-20220527092629-8.png]]
	121	+[[image:image-20220601143257-10.png]]
112	112
113	113
114		-(% class="box infomessage" %)
115		-(((
116		-**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A
117		-)))
	124	+(% style="color:blue" %)**Example:**(%%)  AT+COMMAND1=01 03 00 00 00 01 84 0A
118	118
119	119	* The first byte : slave address code (=001～247)
120	120	* The second byte : read register value function code
...	...	@@ -123,12 +123,12 @@
123	123	* 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
124	124
125	125	(((
	133	+
	134	+
	135	+
126	126	How to parse the reading of the return command of the parameter：
127		-)))
128	128
129		-(% class="box infomessage" %)
130		-(((
131		-**Example:** RETURN1：01 03 02 08 FD 7E 05
	138	+(% style="color:blue" %)**Example:**(%%) RETURN1：01 03 02 08 FD 7E 05
132	132	)))
133	133
134	134	* The first byte ARD: slave address code (=001～254)
...	...	@@ -141,22 +141,27 @@
141	141	(% class="wikigeneratedid" %)
142	142	(((
143	143
	151	+
	152	+
	153	+
144	144	)))
145	145
146	146	=== **1.3.3 How to configure RS485-LN and parse output commands** ===
147	147
	158	+
148	148	RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
149	149
150	150
151		-==== **1.3.3.1 via AT COMMAND:** ====
	162	+==== **1.3.3.1 via AT COMMAND** ====
152	152
153		-First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
154	154
	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	+
155	155	(((
156	156	If the configured parameters and commands are incorrect, the return value is not obtained.
157	157	)))
158	158
159		-[[image:image-20220527092748-9.png]]
	171	+[[image:image-20220601143201-9.png]]
160	160
161	161	AT COMMAND
162	162
...	...	@@ -163,31 +163,33 @@
163	163
164	164	(% class="box infomessage" %)
165	165	(((
166		- AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
	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
167	167	)))
168	168
169		-a: length for the return of AT+COMMAND
	181	+a:  length for the return of AT+COMMAND
170	170
171		-b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
	183	+b: 1: grab valid value by byte, max 6 bytes;  2: grab valid value by bytes section, max 3 sections.
172	172
173		-c: define the position for valid value.
	185	+c:  define the position for valid value.
174	174
175		-[[image:image-20220527092936-10.png]]
	187	+[[image:image-20220601143115-8.png]]
176	176
177	177	AT COMMAND
178	178
179	179
	192	+
180	180	PAYLOAD is available after the valid value is intercepted.
181	181
182	182
183		-[[image:image-20220527093059-11.png]]
	196	+[[image:image-20220601143046-7.png]]
184	184
185	185	AT COMMAND
186	186
187	187
	201	+
188	188	You can get configured PAYLOAD on TTN.
189	189
190		-[[image:image-20220527093133-12.png]]
	204	+[[image:image-20220601143519-1.png]]
191	191
192	192	(((
193	193	AT COMMAND
...	...	@@ -198,52 +198,52 @@
198	198	)))
199	199
200	200	(((
201		-(% style="color:#4f81bd" %)**Example**:
	215	+(% style="color:blue" %)**Example**:
202	202
203		-CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
	217	+CMD1: Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
204	204	)))
205	205
206	206	(((
207		-RETURN1:01 03 02 00 02 39 85 00 00(return data)
	221	+RETURN1: 01 03 02 00 02 39 85 00 00(return data)
208	208	)))
209	209
210	210	(((
211		-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.
	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.
212	212
213	213
214	214	)))
215	215
216	216	(((
217		-CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1
	231	+CMD2: Read voltage data with MODBUS command. address: 0x00 AT+COMMAND2= 01 03 00 00 00 01,1
218	218	)))
219	219
220	220	(((
221		-RETURN2:01 03 02 08 DC BE 1D(return data)
	235	+RETURN2: 01 03 02 08 DC BE 1D(return data)
222	222	)))
223	223
224	224	(((
225		-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.
	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.
226	226
227	227
228	228	)))
229	229
230	230	(((
231		-CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
	245	+CMD3: Read total active energy data with MODBUS command. address: 0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
232	232	)))
233	233
234	234	(((
235		-RETURN3:01 03 04 00 00 00 44 FA 00(return data)
	249	+RETURN3: 01 03 04 00 00 00 44 FA 00(return data)
236	236	)))
237	237
238	238	(((
239		-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.
	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.
240	240	)))
241	241
242	242	(((
243		-Payload:01 00 02 39 85 08 DC 00 00 00 44
	257	+Payload: 01 00 02 39 85 08 DC 00 00 00 44
244	244	)))
245	245
246		-[[image:image-20220527093204-13.png]]
	260	+[[image:image-20220601142936-6.png]]
247	247
248	248	AT COMMAND
249	249
...	...	@@ -250,13 +250,15 @@
250	250
251	251	(% 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.**
252	252
253		-[[image:image-20220527093251-14.png]]
254	254
	268	+[[image:image-20220601143642-2.png]]
	269	+
255	255	AT COMMAND
256	256
257	257
258	258	==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
259	259
	275	+
260	260	[[image:image-20220527093358-15.png]]
261	261
262	262	(((
...	...	@@ -279,7 +279,7 @@
279	279	)))
280	280
281	281	(((
282		-Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
	298	+(% style="color:red" %)Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
283	283	)))
284	284
285	285	(((
...	...	@@ -315,7 +315,9 @@
315	315	)))
316	316
317	317	(((
318		-(% style="color:#4f81bd" %)**Example:**
	334	+
	335	+
	336	+(% style="color:blue" %)**Example:**
319	319	)))
320	320
321	321	(((
...	...	@@ -322,28 +322,32 @@
322	322	**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
323	323	)))
324	324
325		-[[image:image-20220527093430-16.png]]
	343	+[[image:image-20220601144149-6.png]]
326	326
327	327	DOWNLINK
328	328
329	329
330		-[[image:image-20220527093508-17.png]]
331	331
	349	+[[image:image-20220601143803-3.png]]
	350	+
332	332	DOWNLINK
333	333
334	334
335		-[[image:image-20220527093530-18.png]]
336	336
	355	+[[image:image-20220601144053-5.png]]
	356	+
337	337	DOWNLINK
338	338
339	339
340		-[[image:image-20220527093607-19.png]]
341	341
	361	+[[image:image-20220601143921-4.png]]
	362	+
342	342	DOWNLINK
343	343
344	344
345		-[[image:image-20220527093628-20.png]]
346	346
	367	+[[image:image-20220601142805-5.png]]
	368	+
347	347	DOWNLINK
348	348
349	349
...	...	@@ -367,6 +367,8 @@
367	367
368	368	(((
369	369	check digit: Even
	392	+
	393	+
370	370	)))
371	371
372	372	[[image:image-20220527093708-21.png]]
...	...	@@ -374,21 +374,27 @@
374	374	USB
375	375
376	376
	401	+
377	377	[[image:image-20220527093747-22.png]]
378	378
379	379	USB
380	380
381	381
	407	+
382	382	(((
383	383	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	+
384	384	)))
385	385
386	386	(((
387		-(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
	415	+(% style="color:blue" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
388	388	)))
389	389
390	390	(((
391	391	output：01 03 04 00 00 00 42 7A 02
	420	+
	421	+
392	392	)))
393	393
394	394	[[image:image-20220527093821-23.png]]
...	...	@@ -398,6 +398,7 @@
398	398
399	399	=== **1.3.5 How to configure multiple devices and modify device addresses** ===
400	400
	431	+
401	401	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.
402	402
403	403	(((
...	...	@@ -406,13 +406,14 @@
406	406	)))
407	407	)))
408	408
409		-[[image:image-20220527093849-24.png]]
	440	+[[image:image-20220601142044-1.png]]
410	410
411	411
412		-**Example**:These two meters are examples of setting parameters and device addresses.
	443	+(% style="color:blue" %)**Example**(%%): These two meters are examples of setting parameters and device addresses.
413	413
414	414	[[image:image-20220527093950-25.png]]
415	415
	447	+
416	416	[[image:image-20220527094028-26.png]]
417	417
418	418	(((
...	...	@@ -433,7 +433,7 @@
433	433	)))
434	434	)))
435	435
436		-[[image:image-20220527094100-27.png]]
	468	+[[image:image-20220601142354-2.png]]
437	437
438	438	(% class="box infomessage" %)
439	439	(((
...	...	@@ -460,10 +460,10 @@
460	460
461	461	Its default device address is 01, and the following are the parameters for configuring two energy meters.
462	462
463		-[[image:image-20220527094150-28.png]]
	495	+[[image:image-20220601142452-3.png]]
464	464
465	465
466		-[[image:image-20220527094224-29.png]]
	498	+[[image:image-20220601142607-4.png]]
467	467
468	468	**PAYLOAD:01 08 DF 43 62**
469	469
...	...	@@ -470,8 +470,6 @@
470	470	* 08 DF is the valid value of the meter with device address 02.
471	471	* 43 62 is the valid value of the meter with device address 01.
472	472
473		-
474		-
475	475	== 1.4 Example 4: Circuit Breaker Remote Open Close ==
476	476
477	477	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:

image-20220601142044-1.png

Author

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

Size

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

Content

image-20220601142354-2.png

Author

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

Size

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

Content

image-20220601142452-3.png

Author

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

Size

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

Content

image-20220601142607-4.png

Author

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

Size

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

Content

image-20220601142805-5.png

Author

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

Size

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

Content

image-20220601142936-6.png

Author

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

Size

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

Content

image-20220601143046-7.png

Author

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

Size

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

Content

image-20220601143115-8.png

Author

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

Size

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

Content

image-20220601143201-9.png

Author

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

Size

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

Content

image-20220601143257-10.png

Author

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

Size

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

Content

image-20220601143519-1.png

Author

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

Size

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

Content

image-20220601143642-2.png

Author

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

Size

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

Content

image-20220601143803-3.png

Author

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

Size

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

Content

image-20220601143921-4.png

Author

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

Size

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

Content

image-20220601144053-5.png

Author

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

Size

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

Content

image-20220601144149-6.png

Author

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

Size

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

Content