Chapter 2. programming interface, Overview, Modbus master requirements – Comtrol Modbus TCP User Guide User Manual

Page 17: Programming interface

Advertising
background image

DeviceMaster UP Modbus/TCP User Guide: 2000447 Rev. I

Chapter 2. Programming Interface - 17

Chapter 2. Programming Interface

2.1. Overview

The DeviceMaster UP provides highly flexible Modbus connectivity.

Modbus masters supported include Modbus/TCP and Modbus/RTU and Modbus/ASCII serial masters.

Both serial Modbus/RTU and Modbus/ASCII slave devices are supported.

All Modbus masters can communicate with all Modbus slave devices.

The Modbus/RTU and Modbus/ASCII Protocol Interface is defined in (

2.4. Modbus/RTU and Modbus/

ASCII To-Slaves Protocol Interface

on Page 29).

The DeviceMaster UP provides highly advanced raw/ASCII device functionality:

Both serial and Ethernet TCP/IP devices are supported.

Modbus interfaces include Modbus/TCP masters, Modbus/TCP slaves, and both Modbus/RTU and
Modbus/ASCII serial masters.

Up to six Ethernet TCP/IP Application connections per serial or Ethernet TCP/IP device.

The raw/ASCII interface is defined in (

2.2. Raw Data Interface

on Page 19).

You must configure the DeviceMaster UP through its embedded web pages defined in

Chapter 3. Embedded

Configuration Pages

on Page 33.

The DeviceMaster UP uses normal Modbus addressing conventions and provides receive, transmit, and
statistical data.

Appendix A. Programming the PLC via Concept

on Page 85 describes the Concept

PLC programming

examples provided with the DeviceMaster UP. It describes how to configure the DeviceMaster UP for raw
serial data and start running the example programs using the embedded web pages and the example PLC
program code.

Note: While the Concept PLC example programs directly apply only to the Schneider Electric Momentum,

Quantum, and Compact PLCs, they can be used as a guide for programming other PLCs.

2.1.1. Modbus Master Requirements

Modbus Masters (Modbus/TCP, Modbus/RTU serial, and Modbus/ASCII) must meet these requirements:

The Modbus Master must support the corresponding protocol.

For raw/ASCII data, the Modbus Master must support the Read Holding Registers and Write Multiple
Registers commands or, alternatively, the Read/Write Multiple Registers command.

The Modbus Master must be able to write enough data in one message to handle the maximum sized
messages required for the serial or Ethernet device.

Advertising