Template:Networking rut955 manual modbus serial: Difference between revisions
No edit summary |
m Protected "Template:Networking rut955 manual modbus serial" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== | ==Summary== | ||
'''Modbus''' is a serial communications protocol originally published by Modicon (now Schneider Electric) in 1979 for use with its programmable logic controllers (PLCs). Modbus has become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices. The main reasons for the use of Modbus in the industrial environment are: | '''Modbus''' is a serial communications protocol originally published by Modicon (now Schneider Electric) in 1979 for use with its programmable logic controllers (PLCs). Modbus has become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices. The main reasons for the use of Modbus in the industrial environment are: | ||
| Line 10: | Line 10: | ||
Modbus enables communication among many devices connected to the same network, for example, a system that measures temperature and humidity and communicates the results to a computer. Modbus is often used to connect a supervisory computer with a remote terminal unit (RTU) in supervisory control and data acquisition (SCADA) systems. Many of the data types are named from its use in driving relays: a single-bit physical output is called a coil, and a single-bit physical input is called a discrete input or a contact. | Modbus enables communication among many devices connected to the same network, for example, a system that measures temperature and humidity and communicates the results to a computer. Modbus is often used to connect a supervisory computer with a remote terminal unit (RTU) in supervisory control and data acquisition (SCADA) systems. Many of the data types are named from its use in driving relays: a single-bit physical output is called a coil, and a single-bit physical input is called a discrete input or a contact. | ||
This article provides | This article provides a brief example on how to use Modbus serial to monitor a slave device, send data to server and how to configure slave alarms. To find more information about this feature visit [[RUT955 Modbus]] and [[RUT955 RS232/RS485]] pages. | ||
==Prerequisites== | ==Prerequisites== | ||
| Line 21: | Line 21: | ||
==Topology== | ==Topology== | ||
[[File: | [[File:Networking_rut955_configuration_modbus_serial_topology_2_v1.png|border|class=tlt-border|700x700px]] | ||
==Configuring Modbus serial slave device== | ==Configuring Modbus serial slave device== | ||
| Line 83: | Line 83: | ||
---- | ---- | ||
In order to test the functionality you will need to | In order to test the functionality, you will need to set up a server (you can run a server on the same computer you use as a slave simulator). | ||
There are many ways how you can create a server to which Modbus will send data to. In this example we are going to be using Windows 10 computer and Hercules app, which you can download [https://www.hw-group.com/product-version/hercules here], to create a test server. Download, install the app and apply the configuration below: | There are many ways how you can create a server to which Modbus will send data to. In this example we are going to be using Windows 10 computer and Hercules app, which you can download [https://www.hw-group.com/product-version/hercules here], to create a test server. Download, install the app and apply the configuration below: | ||
| Line 160: | Line 156: | ||
Change the value to anything below 5, you should not receive messages. Then change the value to anything above 5, you should start receiving messages. | Change the value to anything below 5, you should not receive messages. Then change the value to anything above 5, you should start receiving messages. | ||