Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 41.9 >
edited by Xiaoling
on 2022/05/31 09:39
To version < 74.1 >
edited by Karry Zhuang
on 2024/07/11 11:54
>
Change comment: Uploaded new attachment "1720670079781-764.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.karry
Content
... ... @@ -1,5 +1,4 @@
1 -(% class="wikigeneratedid" %)
2 - **Contents:**
1 +**Table of Contents:**
3 3  
4 4  {{toc/}}
5 5  
... ... @@ -8,57 +8,67 @@
8 8  
9 9  
10 10  
11 -= **1. Introduction** =
10 += 1. Introduction =
12 12  
12 +
13 13  This article provide the examples for RS485-LN to connect to different type of RS485 sensors.
14 14  
15 15  
16 -== **1.1 Example 1: Connect to Leak relay and VFD** ==
16 +== 1.1 Example 1: Connect to Leak relay and VFD ==
17 17  
18 +
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 -[[image:image-20220527091852-1.png]]
21 21  
22 -Connection
22 +[[image:image-20220527091852-1.png||height="547" width="994"]]
23 23  
24 +**Connection**
24 24  
25 25  
26 26  [[image:image-20220527091942-2.png]](% style="display:none" %)
27 27  
28 -Connection
29 +**Connection**
29 29  
30 30  
31 -Related documents:
32 +(% style="color:blue" %)**Related documents:**
32 32  
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.
34 +* System Structure:  [[Solar Pump with Dragino>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
35 +
36 +* 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/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
37 +
35 35  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
36 36  
37 37  
38 -== **1.2 Example 2: Connect to Pulse Counter** ==
41 +== 1.2 Example 2: Connect to Pulse Counter ==
39 39  
43 +
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  
42 -[[image:image-20220527092058-3.png]]
43 43  
44 -Connection
47 +[[image:image-20220527092058-3.png||height="552" width="905"]]
45 45  
49 +**Connection**
46 46  
47 -[[image:image-20220527092146-4.png]]
48 48  
49 -Connection
52 +[[image:image-20220527092146-4.png||height="507" width="906"]]
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
54 +**Connection**
55 +
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/||_mstmutation="1"]]
60 +
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 55  
56 -== **1.3 Example3: Use RS485-LN with energy meters** ==
64 +== 1.3 Example 3: Use RS485-LN with energy meters ==
57 57  
58 -=== **1.3.1 OverView** ===
66 +=== 1.3.1 OverView ===
59 59  
68 +
60 60  (((
61 -**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
70 +(% 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  (((
... ... @@ -67,11 +67,13 @@
67 67  
68 68  [[image:image-20220527092419-5.png]]
69 69  
70 -Connection1
79 +**Connection1**
71 71  
72 72  
73 73  (((
74 -How to connect with Energy Meter：
83 +(% style="color:blue" %)**How to connect with Energy Meter：**
84 +
85 +
75 75  )))
76 76  
77 77  (((
... ... @@ -83,11 +83,11 @@
83 83  )))
84 84  
85 85  (((
86 -Power Source VIN to RS485-LN VIN+
97 +Power Source **VIN** to RS485-LN **VIN+**
87 87  )))
88 88  
89 89  (((
90 -Power Source GND to RS485-LN VIN-
101 +Power Source **GND** to RS485-LN **VIN-**
91 91  )))
92 92  
93 93  (((
... ... @@ -96,101 +96,107 @@
96 96  
97 97  [[image:image-20220527092514-6.png]]
98 98  
99 -Connection2
110 +**Connection2**
100 100  
101 101  
102 102  [[image:image-20220527092555-7.png]]
103 103  
104 -Connection3
115 +**Connection3**
105 105  
106 106  
107 -=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
118 +=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands ===
108 108  
120 +
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]]
123 +[[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 -)))
126 +(% 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)
129 +
120 120  * The second byte : read register value function code
131 +
121 121  * 3rd and 4th bytes: start address of register to be read
133 +
122 122  * 5th and 6th bytes: Number of registers to read
135 +
123 123  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
124 124  
125 125  (((
139 +
140 +
141 +
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
144 +(% 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)
148 +
135 135  * The second byte: Return to read function code
150 +
136 136  * 3rd byte: total number of bytes
152 +
137 137  * 4th～5th bytes: register data
154 +
138 138  * The 6th and 7th bytes: CRC16 checksum
156 +
139 139  * 08 FD is register data. Use short integer 16 bits to convert to decimal, get 2301, then 230.1V is the voltage.
140 140  
141 -(% class="wikigeneratedid" %)
142 -(((
143 -
144 -)))
145 145  
146 -=== **1.3.3 How to configure RS485-LN and parse output commands** ===
160 +=== 1.3.3 How to configure RS485-LN and parse output commands ===
147 147  
162 +
148 148  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
149 149  
150 150  
151 -==== **1.3.3.1 via AT COMMAND:** ====
166 +==== **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  
169 +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.
170 +
155 155  (((
156 156  If the configured parameters and commands are incorrect, the return value is not obtained.
173 +
174 +
157 157  )))
158 158  
159 -[[image:image-20220527092748-9.png]]
177 +[[image:image-20220601143201-9.png]]
160 160  
161 -AT COMMAND
179 +**AT COMMAND**
162 162  
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
184 + (% _mstmutation="1" %)**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
187 +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.
189 +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.
191 +c:  define the position for valid value.
174 174  
175 -[[image:image-20220527092936-10.png]]
193 +[[image:image-20220601143115-8.png]]
176 176  
177 -AT COMMAND
195 +**AT COMMAND**
178 178  
179 179  
180 180  PAYLOAD is available after the valid value is intercepted.
181 181  
200 +[[image:image-20220601143046-7.png]]
182 182  
183 -[[image:image-20220527093059-11.png]]
202 +**AT COMMAND**
184 184  
185 -AT COMMAND
186 186  
187 -
188 188  You can get configured PAYLOAD on TTN.
189 189  
190 -[[image:image-20220527093133-12.png]]
207 +[[image:image-20220601143519-1.png]]
191 191  
192 192  (((
193 -AT COMMAND
210 +**AT COMMAND**
194 194  )))
195 195  
196 196  (((
... ... @@ -198,77 +198,76 @@
198 198  )))
199 199  
200 200  (((
201 -(% style="color:#4f81bd" %)**Example**:
218 +(% 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
220 +(% style="color:red" %)**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)
224 +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.
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.
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
234 +(% style="color:red" %)**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)
238 +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.
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.
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
248 +(% style="color:red" %)**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)
252 +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.
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.
240 240  )))
241 241  
242 242  (((
243 -Payload:01 00 02 39 85 08 DC 00 00 00 44
260 +Payload: 01 00 02 39 85 08 DC 00 00 00 44
244 244  )))
245 245  
246 -[[image:image-20220527093204-13.png]]
263 +[[image:image-20220601142936-6.png]]
247 247  
248 248  AT COMMAND
249 249  
250 250  
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.**
268 +(% style="color:blue" %)**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  
271 +[[image:image-20220601143642-2.png]]
272 +
255 255  AT COMMAND
256 256  
257 257  
258 258  ==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
259 259  
278 +
260 260  [[image:image-20220527093358-15.png]]
261 261  
262 262  (((
263 -DOWNLINK
282 +**DOWNLINK**
264 264  )))
265 265  
266 -(((
267 -
268 -)))
269 269  
270 270  (((
271 -(% style="color:#4f81bd" %)**Type Code 0xAF**
287 +(% style="color:blue" %)**Type Code 0xAF**
272 272  )))
273 273  
274 274  (((
... ... @@ -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  (((
... ... @@ -314,8 +314,9 @@
314 314  will execute an uplink after got this command.
315 315  )))
316 316  
333 +
317 317  (((
318 -(% style="color:#4f81bd" %)**Example:**
335 +(% style="color:blue" %)**Example:**
319 319  )))
320 320  
321 321  (((
... ... @@ -322,33 +322,34 @@
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]]
342 +[[image:image-20220601144149-6.png]]
326 326  
327 -DOWNLINK
344 +**DOWNLINK**
328 328  
329 329  
330 -[[image:image-20220527093508-17.png]]
347 +[[image:image-20220601143803-3.png]]
331 331  
332 -DOWNLINK
349 +**DOWNLINK**
333 333  
334 334  
335 -[[image:image-20220527093530-18.png]]
352 +[[image:image-20220601144053-5.png]]
336 336  
337 -DOWNLINK
354 +**DOWNLINK**
338 338  
339 339  
340 -[[image:image-20220527093607-19.png]]
357 +[[image:image-20220601143921-4.png]]
341 341  
342 -DOWNLINK
359 +**DOWNLINK**
343 343  
344 344  
345 -[[image:image-20220527093628-20.png]]
362 +[[image:image-20220601142805-5.png]]
346 346  
347 -DOWNLINK
348 -
364 +**DOWNLINK**
349 349  
350 -=== **1.3.4 How to configure and output commands for RS485 to USB** ===
351 351  
367 +=== 1.3.4 How to configure and output commands for RS485 to USB ===
368 +
369 +
352 352  (((
353 353  This step is not necessary, it is just to show how to use a normal RS485 to USB adapter to connect to the meter to check the input and output. This can be used to test the connection and RS485 command of the meter without RS485-LN.
354 354  )))
... ... @@ -371,33 +371,37 @@
371 371  
372 372  [[image:image-20220527093708-21.png]]
373 373  
374 -USB
392 +**USB**
375 375  
376 376  
377 377  [[image:image-20220527093747-22.png]]
378 378  
379 -USB
397 +**USB**
380 380  
381 381  
400 +
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.
384 384  )))
385 385  
386 386  (((
387 -(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
406 +(% 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
411 +
412 +
392 392  )))
393 393  
394 394  [[image:image-20220527093821-23.png]]
395 395  
396 -USB
417 +**USB**
397 397  
398 398  
399 -=== **1.3.5 How to configure multiple devices and modify device addresses** ===
420 +=== 1.3.5 How to configure multiple devices and modify device addresses ===
400 400  
422 +
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,15 +406,18 @@
406 406  )))
407 407  )))
408 408  
409 -[[image:image-20220527093849-24.png]]
431 +[[image:image-20220601142044-1.png]]
410 410  
411 411  
412 -**Example**:These two meters are examples of setting parameters and device addresses.
434 +(% style="color:blue" %)**Example**(%%): These two meters are examples of setting parameters and device addresses.
413 413  
436 +
414 414  [[image:image-20220527093950-25.png]]
415 415  
439 +
416 416  [[image:image-20220527094028-26.png]]
417 417  
442 +
418 418  (((
419 419  (((
420 420  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.
... ... @@ -423,7 +423,7 @@
423 423  
424 424  (((
425 425  (((
426 -We can use AT+CFGDEV to set the device address.
451 +We can use (% style="color:blue" %)**AT+CFGDEV**(%%) to set the device address.
427 427  )))
428 428  )))
429 429  
... ... @@ -433,16 +433,17 @@
433 433  )))
434 434  )))
435 435  
436 -[[image:image-20220527094100-27.png]]
461 +[[image:image-20220601142354-2.png]]
437 437  
463 +
438 438  (% class="box infomessage" %)
439 439  (((
440 440  **AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
441 441  )))
442 442  
443 -* 01:device adaress
469 +* 01: device adaress
444 444  
445 -* 10:function code
471 +* 10: function code
446 446  
447 447  * 00 61：Register address
448 448  
... ... @@ -460,48 +460,82 @@
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]]
489 +[[image:image-20220601142452-3.png]]
464 464  
465 465  
466 -[[image:image-20220527094224-29.png]]
492 +[[image:image-20220601142607-4.png]]
467 467  
468 -**PAYLOAD:01 08 DF 43 62**
469 469  
495 +(% style="color:blue" %)**PAYLOAD: 01 08 DF 43 62**
496 +
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  
500 +(% style="display:none" %) (%%)
473 473  
474 474  
475 475  == 1.4 Example 4: Circuit Breaker Remote Open Close ==
476 476  
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:
478 478  
506 +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.
507 +
508 +The structure is like below:
509 +
479 479  [[image:image-20220527094330-30.png]]
480 480  
481 -Connection
512 +**Connection**
482 482  
483 -* [[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
484 484  
515 +* 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/||_mstmutation="1"]]
485 485  
486 486  
487 487  == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
488 488  
520 +
489 489  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:
490 490  
491 -* [[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
523 +* 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||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
492 492  
493 -* [[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
525 +* 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||_mstmutation="1"]]
494 494  
495 -== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
496 496  
528 +== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN ==
529 +
530 +
497 497  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:
498 498  
499 -* [[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
533 +* 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||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
500 500  
501 -== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
502 502  
536 +== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
537 +
538 +
503 503  [[image:image-20220527094556-31.png]]
504 504  
541 +
505 505  Network Structure
506 506  
507 507  * [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]
545 +
546 +
547 +== 1.8 Example 8: This sketch is supposed to test Dragino RS485-BL (Modbus master), using an Arduino UNO as a Modbus slave. ==
548 +
549 +
550 +This sketch uses 4 registers: some of them can be set by Dragino with a command, another is used to store value from a DS18B20 temperature sensor, or a random generated number. All data is 16bit uint, but the sketch shows also how to represent booleans and negative numbers.
551 +
552 +In the next days I will be adding more documentation, but I think it already explains users how to build their own modbus sensor to pair with Dragino RS485-BL.
553 +
554 +This is released the code under GNU LGPL licence on Github:
555 +
556 +[[https:~~/~~/github.com/zorbaproject/ArduinoModbusForDraginoRS485>>url:https://github.com/zorbaproject/ArduinoModbusForDraginoRS485]]
557 +
558 +
559 +== 1.9 Example 9: RS485-LN and ultrasonic flow meter transmission data ==
560 +
561 +
562 +It shows how to use RS485-LN to connect to an ultrasonic flow meter and read the data from the ultrasonic flow meter.
563 +
564 +
565 +
566 +* **Specific steps**:  RS485-LN with ultrasonic flow meter
567 +*
1720669739434-926.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +489.9 KB
Content
1720669744315-613.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +476.9 KB
Content
1720669933691-331.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +395.1 KB
Content
1720669944339-942.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +341.8 KB
Content
1720669981767-254.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +341.8 KB
Content
1720670003601-544.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +385.3 KB
Content
1720670016539-422.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +503.5 KB
Content
1720670019136-658.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +592.6 KB
Content
1720670035661-234.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +316.5 KB
Content
1720670038725-366.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +571.9 KB
Content
1720670041974-372.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +571.9 KB
Content
1720670079781-764.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.karry
Size
... ... @@ -1,0 +1,1 @@
1 +614.7 KB
Content
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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0