Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 46.2 >
edited by Xiaoling
on 2022/06/01 14:28
To version < 61.1 >
edited by Bei Jinggeng
on 2023/08/08 15:16
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,5 +1,4 @@
1 -(% class="wikigeneratedid" %)
2 - **Contents:**
1 +**Table of Contents:**
3 3  
4 4  {{toc/}}
5 5  
... ... @@ -8,74 +8,87 @@
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  
27 +
26 26  [[image:image-20220527091942-2.png]](% style="display:none" %)
27 27  
28 -Connection
30 +**Connection**
29 29  
30 30  
31 -Related documents:
33 +(% 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.
35 +* 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);"]]
36 +
37 +* 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);"]]
38 +
35 35  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
36 36  
37 37  
42 +== 1.2 Example 2: Connect to Pulse Counter ==
38 38  
39 -== **1.2 Example 2: Connect to Pulse Counter** ==
40 40  
41 41  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:
42 42  
43 -[[image:image-20220527092058-3.png]]
44 44  
45 -Connection
48 +[[image:image-20220527092058-3.png||height="552" width="905"]]
46 46  
50 +**Connection**
47 47  
48 48  
49 -[[image:image-20220527092146-4.png]]
50 50  
51 -Connection
54 +[[image:image-20220527092146-4.png||height="507" width="906"]]
52 52  
56 +**Connection**
53 53  
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 +
59 +(% style="color:blue" %)**Related documents:**
60 +
61 +* 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"]]
62 +
55 55  * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
56 56  
57 -== ==
58 58  
59 -== **1.3 Example3: Use RS485-LN with energy meters** ==
66 +== 1.3 Example 3: Use RS485-LN with energy meters ==
60 60  
61 -=== **1.3.1 OverView** ===
68 +=== 1.3.1 OverView ===
62 62  
70 +
63 63  (((
64 -**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
72 +(% style="color:red" %)**Note**：**The specifications of each energy meter are different, please refer to your own energy meter specifications.**
65 65  )))
66 66  
67 67  (((
68 68  This example describes a single-phase meter.This is the connection between the RS485-LN and the energy meter.
77 +
78 +
69 69  )))
70 70  
71 71  [[image:image-20220527092419-5.png]]
72 72  
73 -Connection1
83 +**Connection1**
74 74  
75 75  
76 76  
77 77  (((
78 -How to connect with Energy Meter：
88 +(% style="color:blue" %)**How to connect with Energy Meter：**
89 +
90 +
79 79  )))
80 80  
81 81  (((
... ... @@ -87,88 +87,97 @@
87 87  )))
88 88  
89 89  (((
90 -Power Source VIN to RS485-LN VIN+
102 +Power Source **VIN** to RS485-LN **VIN+**
91 91  )))
92 92  
93 93  (((
94 -Power Source GND to RS485-LN VIN-
106 +Power Source **GND** to RS485-LN **VIN-**
95 95  )))
96 96  
97 97  (((
98 98  Once there is power, the RS485-LN will be on.
111 +
112 +
99 99  )))
100 100  
101 101  [[image:image-20220527092514-6.png]]
102 102  
103 -Connection2
117 +**Connection2**
104 104  
105 105  
106 106  
107 107  [[image:image-20220527092555-7.png]]
108 108  
109 -Connection3
123 +**Connection3**
110 110  
111 111  
112 -=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
126 +=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands ===
113 113  
128 +
114 114  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.
115 115  
116 -[[image:image-20220527092629-8.png]]
131 +[[image:image-20220601143257-10.png]]
117 117  
118 118  
119 -(% class="box infomessage" %)
120 -(((
121 -**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A
122 -)))
134 +(% style="color:blue" %)**Example:**(%%)  AT+COMMAND1=01 03 00 00 00 01 84 0A
123 123  
124 124  * The first byte : slave address code (=001～247)
137 +
125 125  * The second byte : read register value function code
139 +
126 126  * 3rd and 4th bytes: start address of register to be read
141 +
127 127  * 5th and 6th bytes: Number of registers to read
143 +
128 128  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
129 129  
130 130  (((
147 +
148 +
149 +
131 131  How to parse the reading of the return command of the parameter：
132 -)))
133 133  
134 -(% class="box infomessage" %)
135 -(((
136 -**Example:** RETURN1：01 03 02 08 FD 7E 05
152 +(% style="color:blue" %)**Example:**(%%) RETURN1：01 03 02 08 FD 7E 05
137 137  )))
138 138  
139 139  * The first byte ARD: slave address code (=001～254)
156 +
140 140  * The second byte: Return to read function code
158 +
141 141  * 3rd byte: total number of bytes
160 +
142 142  * 4th～5th bytes: register data
162 +
143 143  * The 6th and 7th bytes: CRC16 checksum
164 +
144 144  * 08 FD is register data. Use short integer 16 bits to convert to decimal, get 2301, then 230.1V is the voltage.
145 145  
146 -(% class="wikigeneratedid" %)
147 -(((
148 -
149 -)))
150 150  
151 -=== **1.3.3 How to configure RS485-LN and parse output commands** ===
168 +=== 1.3.3 How to configure RS485-LN and parse output commands ===
152 152  
170 +
153 153  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
154 154  
155 155  
156 -==== **1.3.3.1 via AT COMMAND:** ====
174 +==== **1.3.3.1 via AT COMMAND** ====
157 157  
158 -First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
159 159  
177 +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.
178 +
160 160  (((
161 161  If the configured parameters and commands are incorrect, the return value is not obtained.
181 +
182 +
162 162  )))
163 163  
164 -[[image:image-20220527092748-9.png]]
185 +[[image:image-20220601143201-9.png]]
165 165  
166 -AT COMMAND
187 +**AT COMMAND**
167 167  
168 168  
169 169  (% class="box infomessage" %)
170 170  (((
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
192 + (% _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
172 172  )))
173 173  
174 174  a:  length for the return of AT+COMMAND
... ... @@ -177,27 +177,26 @@
177 177  
178 178  c:  define the position for valid value.
179 179  
180 -[[image:image-20220527092936-10.png]]
201 +[[image:image-20220601143115-8.png]]
181 181  
182 -AT COMMAND
203 +**AT COMMAND**
183 183  
184 184  
185 185  
186 186  PAYLOAD is available after the valid value is intercepted.
187 187  
209 +[[image:image-20220601143046-7.png]]
188 188  
189 -[[image:image-20220527093059-11.png]]
211 +**AT COMMAND**
190 190  
191 -AT COMMAND
192 192  
193 193  
194 -
195 195  You can get configured PAYLOAD on TTN.
196 196  
197 -[[image:image-20220527093133-12.png]]
217 +[[image:image-20220601143519-1.png]]
198 198  
199 199  (((
200 -AT COMMAND
220 +**AT COMMAND**
201 201  )))
202 202  
203 203  (((
... ... @@ -205,79 +205,79 @@
205 205  )))
206 206  
207 207  (((
208 -(% style="color:#4f81bd" %)**Example**:
228 +(% style="color:blue" %)**Example**:
209 209  
210 -CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
230 +(% style="color:red" %)**CMD1:**(%%) Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
211 211  )))
212 212  
213 213  (((
214 -RETURN1:01 03 02 00 02 39 85 00 00(return data)
234 +RETURN1: 01 03 02 00 02 39 85 00 00(return data)
215 215  )))
216 216  
217 217  (((
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.
238 +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.
219 219  
220 220  
221 221  )))
222 222  
223 223  (((
224 -CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1
244 +(% style="color:red" %)**CMD2: **(%%)Read voltage data with MODBUS command. address: 0x00 AT+COMMAND2= 01 03 00 00 00 01,1
225 225  )))
226 226  
227 227  (((
228 -RETURN2:01 03 02 08 DC BE 1D(return data)
248 +RETURN2: 01 03 02 08 DC BE 1D(return data)
229 229  )))
230 230  
231 231  (((
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.
252 +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.
233 233  
234 234  
235 235  )))
236 236  
237 237  (((
238 -CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
258 +(% style="color:red" %)**CMD3:**(%%) Read total active energy data with MODBUS command. address: 0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
239 239  )))
240 240  
241 241  (((
242 -RETURN3:01 03 04 00 00 00 44 FA 00(return data)
262 +RETURN3: 01 03 04 00 00 00 44 FA 00(return data)
243 243  )))
244 244  
245 245  (((
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.
266 +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.
247 247  )))
248 248  
249 249  (((
250 -Payload:01 00 02 39 85 08 DC 00 00 00 44
270 +Payload: 01 00 02 39 85 08 DC 00 00 00 44
251 251  )))
252 252  
253 -[[image:image-20220527093204-13.png]]
273 +[[image:image-20220601142936-6.png]]
254 254  
255 255  AT COMMAND
256 256  
257 257  
258 -(% 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.**
259 259  
279 +(% 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.**
260 260  
261 261  
262 -[[image:image-20220527093251-14.png]]
282 +[[image:image-20220601143642-2.png]]
263 263  
264 264  AT COMMAND
265 265  
266 266  
287 +
267 267  ==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
268 268  
290 +
269 269  [[image:image-20220527093358-15.png]]
270 270  
271 271  (((
272 -DOWNLINK
294 +**DOWNLINK**
273 273  )))
274 274  
275 -(((
276 -
277 -)))
278 278  
298 +
279 279  (((
280 -(% style="color:#4f81bd" %)**Type Code 0xAF**
300 +(% style="color:blue" %)**Type Code 0xAF**
281 281  )))
282 282  
283 283  (((
... ... @@ -288,7 +288,7 @@
288 288  )))
289 289  
290 290  (((
291 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
311 +(% style="color:red" %)**Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.**
292 292  )))
293 293  
294 294  (((
... ... @@ -323,10 +323,9 @@
323 323  will execute an uplink after got this command.
324 324  )))
325 325  
326 -(((
327 -
328 328  
329 -(% style="color:#4f81bd" %)**Example:**
347 +(((
348 +(% style="color:blue" %)**Example:**
330 330  )))
331 331  
332 332  (((
... ... @@ -333,37 +333,38 @@
333 333  **AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
334 334  )))
335 335  
336 -[[image:image-20220527093430-16.png]]
355 +[[image:image-20220601144149-6.png]]
337 337  
338 -DOWNLINK
357 +**DOWNLINK**
339 339  
340 340  
341 341  
342 -[[image:image-20220527093508-17.png]]
361 +[[image:image-20220601143803-3.png]]
343 343  
344 -DOWNLINK
363 +**DOWNLINK**
345 345  
346 346  
347 347  
348 -[[image:image-20220527093530-18.png]]
367 +[[image:image-20220601144053-5.png]]
349 349  
350 -DOWNLINK
369 +**DOWNLINK**
351 351  
352 352  
353 353  
354 -[[image:image-20220527093607-19.png]]
373 +[[image:image-20220601143921-4.png]]
355 355  
356 -DOWNLINK
375 +**DOWNLINK**
357 357  
358 358  
359 359  
360 360  [[image:image-20220601142805-5.png]]
361 361  
362 -DOWNLINK
363 -
381 +**DOWNLINK**
364 364  
365 -=== **1.3.4 How to configure and output commands for RS485 to USB** ===
366 366  
384 +=== 1.3.4 How to configure and output commands for RS485 to USB ===
385 +
386 +
367 367  (((
368 368  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.
369 369  )))
... ... @@ -382,17 +382,19 @@
382 382  
383 383  (((
384 384  check digit: Even
405 +
406 +
385 385  )))
386 386  
387 387  [[image:image-20220527093708-21.png]]
388 388  
389 -USB
411 +**USB**
390 390  
391 391  
392 392  
393 393  [[image:image-20220527093747-22.png]]
394 394  
395 -USB
417 +**USB**
396 396  
397 397  
398 398  
... ... @@ -401,20 +401,24 @@
401 401  )))
402 402  
403 403  (((
404 -(% style="color:#4f81bd" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
426 +(% style="color:blue" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
405 405  )))
406 406  
407 407  (((
408 408   output：01 03 04 00 00 00 42 7A 02
431 +
432 +
409 409  )))
410 410  
411 411  [[image:image-20220527093821-23.png]]
412 412  
413 -USB
437 +**USB**
414 414  
415 415  
416 -=== **1.3.5 How to configure multiple devices and modify device addresses** ===
417 417  
441 +=== 1.3.5 How to configure multiple devices and modify device addresses ===
442 +
443 +
418 418  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.
419 419  
420 420  (((
... ... @@ -426,12 +426,15 @@
426 426  [[image:image-20220601142044-1.png]]
427 427  
428 428  
429 -**Example**:These two meters are examples of setting parameters and device addresses.
455 +(% style="color:blue" %)**Example**(%%): These two meters are examples of setting parameters and device addresses.
430 430  
457 +
431 431  [[image:image-20220527093950-25.png]]
432 432  
460 +
433 433  [[image:image-20220527094028-26.png]]
434 434  
463 +
435 435  (((
436 436  (((
437 437  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.
... ... @@ -440,7 +440,7 @@
440 440  
441 441  (((
442 442  (((
443 -We can use AT+CFGDEV to set the device address.
472 +We can use (% style="color:blue" %)**AT+CFGDEV**(%%) to set the device address.
444 444  )))
445 445  )))
446 446  
... ... @@ -452,14 +452,15 @@
452 452  
453 453  [[image:image-20220601142354-2.png]]
454 454  
484 +
455 455  (% class="box infomessage" %)
456 456  (((
457 457  **AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
458 458  )))
459 459  
460 -* 01:device adaress
490 +* 01: device adaress
461 461  
462 -* 10:function code
492 +* 10: function code
463 463  
464 464  * 00 61：Register address
465 465  
... ... @@ -482,45 +482,68 @@
482 482  
483 483  [[image:image-20220601142607-4.png]]
484 484  
485 -**PAYLOAD:01 08 DF 43 62**
486 486  
516 +(% style="color:blue" %)**PAYLOAD: 01 08 DF 43 62**
517 +
487 487  * 08 DF is the valid value of the meter with device address 02.
488 488  * 43 62 is the valid value of the meter with device address 01.
489 489  
521 +(% style="display:none" %) (%%)
490 490  
523 +
491 491  == 1.4 Example 4: Circuit Breaker Remote Open Close ==
492 492  
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:
494 494  
527 +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.
528 +
529 +The structure is like below:
530 +
495 495  [[image:image-20220527094330-30.png]]
496 496  
497 -Connection
533 +**Connection**
498 498  
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
500 500  
536 +* 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"]]
501 501  
538 +
502 502  == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
503 503  
541 +
504 504  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:
505 505  
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
544 +* 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);"]]
507 507  
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
546 +* 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"]]
509 509  
510 510  
549 +== 1.6 Example 6: CEM C31 485-T1-MID Energy Meter with RS485-LN ==
511 511  
512 -== 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
513 513  
514 514  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:
515 515  
516 -* [[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
554 +* 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);"]]
517 517  
518 518  
557 +== 1.7 Example 7: Schneider Electric PLC M221 with RS485-BL ==
519 519  
520 -== 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
521 521  
522 522  [[image:image-20220527094556-31.png]]
523 523  
562 +
524 524  Network Structure
525 525  
526 526  * [[Reference Instruction>>url:https://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Schneider%20Electric%20PLC/]]
566 +
567 +== ==
568 +
569 +== 1.8  Example 8: This sketch is supposed to test Dragino RS485-BL (Modbus master), using an Arduino UNO as a Modbus slave. ==
570 +
571 +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.
572 +
573 +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.
574 +
575 +This is released the code under GNU LGPL licence on Github:
576 +
577 +[[https:~~/~~/github.com/zorbaproject/ArduinoModbusForDraginoRS485>>url:https://github.com/zorbaproject/ArduinoModbusForDraginoRS485]]
578 +
579 +
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