Catalogs >
Comtrol Corporation >
Device Master UP-Modbus Solution Examples

Device Master UP-Modbus Solution Examples
1 / 15Pages

Catalog excerpts

Device Master UP-Modbus Solution Examples - 1

DeviceMaster UP Modbus Solution Examples UP T This document includes a number of Modbus connectivity examples which are intended to help the system e integrator or plant engineer determine how to set up i installations. These examples include information such i as the recommended chassis and Modbus firmware for a each configuration. Information on how to configure the e functionality for each particular DeviceMaster is left to the f User Guide Manuals. U Due to flexibility of the DeviceMaster UP Modbus firmware D applications, it is not possible to show every possible a Modbus solution. The Modbus Router and Modbus/TCP firmware applications provide the ability to create either very simple or very complex Modbus installations. For instance, you can combine more than one of these connectivity solutions onto one gateway or use several gateways to build a Modbus network. (A Modbus network typically involves multiple gateways providing communication between Modbus controller(s) and device(s) on a network.) When setting up your Modbus installation, please keep the following in mind: • When using either Modbus Router or Modbus/TCP firmware, all Modbus masters can communicate to all slave devices. For example, you can have multiple serial and Modbus/TCP masters communicating to the same or different slave(s) at one time. • When using Modbus/TCP firmware, both Modbus controllers and applications can communicate to a single raw/ASCII device at the same time. • Modbus messages are automatically converted from one format to another. For instance, you can connect Modbus/RTU masters to Modbus/TCP or Modbus/ASCII slaves and the gateway automatically performs all conversions and message verification. • Each serial port or Ethernet TCP/IP device interface is individually configurable. That allows: o For Modbus/TCP and Modbus Router firmware, multiple serial master or slave devices of either the same or different Modbus type can be attached to the same gateway. o For Modbus/TCP firmware, each raw/ASCII serial port or Ethernet TCP/IP device interface can operate in different receive and transmit modes. (i.e. One can operate in master mode while others operate in slave or master/slave mode.) If you have an installation that is not covered by these examples or if you are not certain how to set up your environment, please call the Comtrol customer support staff for more information. To find the Modbus Solution for your installation, please follow the solution outline: Call or email for more information: 1.800.926.6876 | 763.957.6000 | IADSales@comtro

Open the catalog to page 1

Device Master UP-Modbus Solution Examples - 3

1. You have a Modbus/TCP Master Controller This typically includes such controllers as PLCs, OPC Servers, SCADA Systems, HMIs and applications that communicate as a master via Modbus/TCP. a. And you have Serial Modbus/RTU Slave(s) b. And you have Serial Modbus/ASCII Slave(s)

Open the catalog to page 3

Device Master UP-Modbus Solution Examples - 4

c. And you have Serial Raw/ASCH Device(s) Raw; ASCII Device * Barcode Scanner, Prnter, Weigh Scale. Vision System. Display, elc,

Open the catalog to page 4

Device Master UP-Modbus Solution Examples - 5

This typically includes such controllers as PLCs, OPC Servers, SCADA Systems, HMIs and applications that communicate as a slave via Modbus/TCP Due to the nature of master/slave connectivity, the functionality for Modbus/TCP slave controllers is limited to communicating to raw/ASCII devices. a. And you have Raw/ASCII Serial Device(s) Barcode Scanner, Pnnter, Weigh Scale, Vision System, Display, etc. Modbus/TCP Slave to Serial Raw/ASCII Device(s)

Open the catalog to page 5

Device Master UP-Modbus Solution Examples - 6

3. You have a Modbus/TCP Master/Slave Controller This typically includes full-featured controllers such as PLCs, OPC Servers, SCADA Systems, HMIs and applications that can communicate simulataneously as a master and a slave via Modbus/TCP. Utilizing Master/Slave functionality allows the controller and the DeviceMaster UP to operate as peers. Due to the nature of master/slave connectivity, the functionality for Modbus/TCP master/slave controllers is limited to communicating to raw/ASCII devices. a. And you have Raw/ASCII Serial Device(s) b. And you have Raw/ASCII Ethernet Device(s)

Open the catalog to page 6

Device Master UP-Modbus Solution Examples - 7

4. You have a Modbus/RTU or Modbus/ASCII Serial Master Controller This typically includes such controllers as PLCs, SCADA Systems, HMIs and applications that communicate as a master via Modbus/RTU or Modbus/ASCII over a serial or COM port. a. And you have Serial Modbus/RTU Slave(s) b. And you have Serial Modbus/ASCII Slave(s)

Open the catalog to page 7

Device Master UP-Modbus Solution Examples - 8

Firmware: Modbus Router Ethernet Network DeviceMaster UP Modbus^RTU or ModbusfTCP Modbu s/TCP -► 4-► PLC, HMI, SCADA, OPC Serve', Various devinns DevieeM aster UP Device Master UP Modbus Serial Master to Modbus/TCP Slave(s)

Open the catalog to page 8

Device Master UP-Modbus Solution Examples - 9

e. And you have Raw/ASCII Ethernet Device(s) f. And you have Remote Serial Modbus/RTU Slave(s)

Open the catalog to page 9

Device Master UP-Modbus Solution Examples - 10

g. And you have Remote Modbus/ASCII Slave(s) h. And you have Remote Raw/ASCII Serial Device(s)

Open the catalog to page 10

Device Master UP-Modbus Solution Examples - 11

5. You have a Modbus/RTU or Modbus/ASCII Serial Slave Controller This typcially includes such controllers as PLCs, SCADA Systems, HMIs and applications that communicate only as a slave via Modbus/RTU or Modbus/ASCII over a serial or COM port. Due to the nature of master/slave connectivity, the functionality for Modbus serial slave controllers is limited to communicating to raw/ASCII devices. a. And you have Raw/ASCII Serial Device(s) b. And you have Raw/ASCII Ethernet Device(s)

Open the catalog to page 11

Device Master UP-Modbus Solution Examples - 12

Firmware: Modbus-TCP Remote RHW/ASCH Devica- Modbus Serial Stave to Remote Raw/ASCll S ave{s) 12

Open the catalog to page 12

Device Master UP-Modbus Solution Examples - 13

6. You have a Modbus/RTU or Modbus/ASCII over Ethernet TCP/IP Master This typically includes such controllers as some OPC Servers, SCADA Systems, and applications that communicate as a master via an Ethernet TCP/IP connection or, with the use of a serial port redirector, a COM port. a. And you have Modbus/RTU Serial Slave(s) b. And you have Modbus/ASCII Serial Slave(s)

Open the catalog to page 13

Device Master UP-Modbus Solution Examples - 14

c. And you have Modbus/TCP Slaves

Open the catalog to page 14

Device Master UP-Modbus Solution Examples - 15

7. You have an Application that Communicates via Raw/ASCII over Ethernet TCP/IP Connection(s) This typcially includes control or data-base management applications that receive and/or transmit raw/ ASCII data over an Ethernet TCP/IP connection or, with the use of a serial port redirector, a COM port. a. And you have Raw/ASCII Serial Device(s) b. And you have Raw/ASCII Ethernet Device(s)

Open the catalog to page 15