4.4.2 Software Control Modules (C++ or Visual Basic Program) 38
4.4.3 Personal Computer with a Graphical User-Interface 39
5 Interfacing Hardware for the DDC-100 Network 41
5.1 RS-232 to RS-485 Converters 41
5.1.1 RS-232/RS-485 Control Line Steered Converter (P/N 61-825-0966-4) 43
5.1.2 RS-232/RS-485 Converter with RS-485 Self-Steering (P/N 61-825-1032-4) 45
5.2 RS-485 Connection Direct to the DDC-100 Field Unit 48
6 Programming Recommendations 49
6.1 Monitoring Field Unit Status 49
6.2 Issuing Control Commands 50
A Typical DDC-100 Network Installation Assignments 53
Project supplier responsibilities 53
FCD LMAIM4019-00 DDC-100 Direct-to-Host Programming Guide i
Figures
Figure 4.1 – DDC-100 Redundant Loop Network 30
Figure 4.2 – DDC-100 Single-Ended Loop Network 31
Figure 4.3 – DDC-100 Single-Line Multi-Drop Network 33
Figure 5.1 – RS-232/RS-485 Converter Dimensions and Rack Mount Kit 43
Figure 5.2 – RS-232/RS-485 Cable Diagram 43
Figure 5.3 – Front and Back Panels of Steered Converter 44
Figure 5.4 – Front and Back Panels of Self-Steering Converter 46
Tables
Table 3.1 – Field Unit Communication Parameters 5
Table 3.2 – Modbus Function Codes Supported 7
Table 3.3 – DDC-100 Coil Assignments, Modbus Function Code 01 Usage for Digital Outputs 8
Table 3.4 – Status Bit Definitions 8
Table 3.4 – Status Bit Definitions (continued) 9
Table 3.5 – Field Unit Register Definitions 12
Table 3.6 – DDC-100 Coil Assignments Modbus Function Code 05 Usage for Digital Outputs 19
Table 3.7 – Modbus 06 Command and Field Unit Holding Register 40001 20
Table 3.8 – Diagnostic Codes Supported by the DDC-100 Field Unit 23
Table 4.1 – Average Field Unit Response Time 34
Table 4.2 – Average Network Scan Time (seconds) 35
Table 5.1 – RS-232/RS-485 Converter Specifications 42
Table 5.2 – Steered Converter Assembly (P/N 22300-7591) 42
Table 5.3 – Self-Steering Converter Assembly (P/N 22300-7601) 42
Table 5.4 – RS-232/RS-485 Converter (P/N 61-825-0966-4) DIP Switch Functions 44
Table 5.5 – RS-232/RS-485 Converter (P/N 61-825-0966-4) RS-232 Connector 44
Table 5.6 – RS-232/RS-485 Converter (P/N 61-825-0966-4) RS-485 Connector 45
Table 5.7 – RS-232/RS-485 Converter (P/N 61-825-0966-4) Jumpers 45
Table 5.8 – RS-232/RS-485 Converter (P/N 61-825-1032-4) RS-232 Connector 46
Table 5.9 – RS-232/RS-485 Converter (P/N 61-825-1032-4) RS-485 Connector 46
Table 5.10 – RS-232/RS-485 Converter (P/N 61-825-1032-4) Jumpers
Table 6.1 – Sample Tag Table for Direct-to-Host applications 51
1 47
Introduction
1
1.1 Premise
This Programming Guide was written for the user who is connecting Flowserve Limitorque
DDC-100 Network-compatible valve actuators directly to a control system Host computer. These
guidelines provide the information that is necessary to control and monitor the valve actuators
through a serial data communications network.
Your safety and satisfaction are very important to Flowserve. Please follow all instructions carefully
and pay special attention to safety.
1.2 Emphasis
The following methods will be used to emphasize text throughout this manual:
WARNING: Refers to personal safety. This alerts the reader to potential danger or harm.
c
Failure to follow the advice in warning notices could result in personal injury or death.
CAUTION: Directs attention to general precautions, which, if not followed, could result in
a
personal injury and/or equipment damage.
NOTE: Highlights information critical to the understanding or use of these products.
Bold text highlights other important information that is critical to system components.
CAPITALIZED text stresses attention to the details of the procedure.
Underlined text emphasizes crucial words in sentences that could be misunderstood if the word is
not recognized.
The purpose of these emphasized blocks of text is to alert the reader to possible hazards associated
with the equipment and the precautions that can be taken to reduce the risk of personal injury and
damage to the equipment.
Read and become familiar with the material in these guidelines before attempting installation,
operation, or maintenance of the equipment. Failure to observe precautions could result in serious
bodily injury, damage to the equipment, or operational difficulty.
These guidelines were written to help you successfully connect Limitorque valve actuators directly
to a control system Host computer. You do not have to be an expert in electronics or digital controls
to utilize this manual. However, this manual assumes that you have a working understanding of
valve actuators and a fundamental understanding of control system programming.
The following manuals should be available before attempting to connect the valve actuators to the
control system:
1) Accutronix Installation and Operation for MX-DDC Field Unit Manual
Bulletin LMAIM1329
2) DDC-100 UEC Field Unit (Modbus®) Installation and Operation Manual
Bulletin LMAIM4029
3) DDC-100 UEC Field Unit Wiring and Startup Guidelines
Bulletin LMAIM4022
4) DDC-100 UEC Field Unit Installation and Commissioning Manual
Bulletin LMAIM4030
5) Modicon Modbus Protocol Reference Guide PI-MODBUS-300 Rev. G
available from Modicon
6) Valve actuator installation manual for the specific model(s) to be installed.
An understanding of valve actuators and digital control systems is beneficial to all system users.
Flowserve assistance and training is available to help you operate your system at top efficiency. It
is recommended that you read this entire manual before attempting to install the valve actuators in
your control system.
Direct-to-Host Valve
2
In this document, Direct-to-Host valve control is defined as the use of a customer-supplied
(possibly pre-existing) Host control system (PLC, DCS, PC, etc.) to directly control the actuation of
valves that are equipped with DDC-100 Network-compatible field units. The field units are microprocessor-based devices that can communicate with the Host and respond to Host commands for
valve motion and status. The DDC-100 Network uses the EIA RS-485 standard for the physical layer
and the A.E.G. Modicon Modbus protocol for the command structure.
The Direct-to-Host solution to valve actuation systems provides distinct advantages for many
users. These benefits range from maximizing system design flexibility to utilizing existing plant
equipment for valve actuator control. The customer can emphasize selecting the best equipment
and software that closely matches the application’s requirements. This solution allows the user to
add valve control while avoiding the need to incorporate new control equipment into the facility.
Direct-to-Host functionality is accomplished through the use of open architecture control and
communications in the valve actuator controls that economically accommodate widely available
interfaces for existing SCADA, PLC, or personal computers.
Control
2.1 Advantages of Direct-to-Host Control
• Freedom to design a valve actuator system to interface directly with customer-preferred supervisory equipment with open-market availability and off-the-shelf components.
• Maximizes valve actuator system exibility by utilizing the industry standard protocol of Modbus,
complemented with the EIA RS-485 electrical standard.
• Increases control room equipment utilization while incorporating a cost savings to the customer
through the elimination of unnecessary hardware.
• Supports the use of control system components familiar to the user and eliminates the requirement to learn third-party interfaces.
• Strengthens control system architecture with components readily available on the open market.
• Encourages parts replacement and support programs favorable to the user.
• Promotes direct downloading of valve actuator data to the supervisory control system without
• Provides a safe and reliable communications path between the supervisory control system and
valve actuator network. This eliminates an unnecessary single point of failure that would exist if
the valve control network required a gateway device.
• Enhances the operational relationship between the customer and the customer’s preferred system
integrator.
2.2 Deliverables for Successful
Direct-to-Host Implementations
Each Direct-to-Host installation requires coordination to ensure that every supplier understands
their deliverable responsibilities. When suppliers understand particular obligations and perform
the tasks in an orderly and timely fashion, the DDC-100 Network installation process will progress
very smoothly. Appendix A outlines a “typical” chart detailing areas of responsibility or supplier
deliverables for installing a DDC-100 system. This appendix is a guideline and may vary from
project to project.
Field Unit
3
Monitoring and
Control
Flowserve Limitorque valve actuators that are DDC-100 Network compatible can be controlled and
monitored by sending queries and receiving responses over a serial data network. The DDC-100
Network uses the non-proprietary Modbus message protocol and EIA RS-485 standard for the
physical communication link.
Field Unit Address Range 1–250ConfigurableConfigurable
3.1 Use of Coils and Registers
for Monitoring and Control
The material in this section is a brief tutorial and general discussion of the use of Modbus queries
and responses to control valve actuators. The detailed discussion of the commands will be given in
Section 3.2.
The Modbus communications protocol allows for working with two types of information—coils
(or bits) and registers (or 16-bit words). Coils are either ON (1) or OFF (0) and are used in direct
relation to relays (that have coils). For example, in a typical actuator, Coil 1 is energized to CLOSE
the actuator and Coil 2 is energized to OPEN the actuator. Register information is used for control
functions that do not involve coils. An example would be to write a command value to energize the
open or close coil or move the actuator to a position of 0 to 100% of open.
Queries are used to send requests from the Modbus master (Host) to the Modbus slave (DDC-100
Field Unit), and the slave must respond with an appropriate response or an error message.
The Modbus function codes that are supported in the DDC-100 Network are a subset of the
complete Modbus function codes and are listed below:
01 Read Coil Status Reads the ON/OFF status of discrete outputs (coils) in the field units.
02 Read Input Status Reads the ON/OFF status of discrete inputs in the field units.
03 Read Holding Registers Reads the binary contents of holding registers in the field units.
04 Read Input Registers Reads the binary contents of the input registers in the field units.
05 Force Single Coil Forces a single coil to either the ON or OFF state.
06 Preset Single Register Presets a value into a single-holding register.
08 Diagnostics Provides communication tests and checks for internal error conditions in the
field units.
Table 3.2 – Modbus Function Codes Supported
Function
Code
Note: MX-DDC does not support Modbus function code 02.
Modbus function codes 15 and 16 are supported in:
UEC-3-DDC Modbus Firmware 2.00 and greater
MX-DDC Firmware 02/01.00 and greater
Bit/Register
Addressing
Extended
Addressing Range
15 Force Multiple Coils Forces multiple coils to either the ON or OFF state.
16 Preset Multiple Registers Presets a value into multiple holding registers.
NOTE: All data in Modbus messages are referenced to zero. The first occurrence of a data item is
addressed as item number zero. This includes Coils, Inputs, and Registers. For example, coils 1-8
would be addressed as 0-7, inputs 1-16 would be addressed as 0-15, and registers 1-16 would be
addressed as 0-15.
3.2 Modbus
The Modbus protocol was developed by A.E.G. Modicon for communicating to various networked
devices. The relationship between these devices and a central controller is called a master-slave
relationship in which the master (Host device) initiates all communications. The slave devices (field
units in the actuators) respond to the queries from the master. Modbus only permits one master to
communicate at any given time (simultaneous communication is prohibited) for assuring process
control integrity.
The controlling device (master) must conform to the Modbus protocol as defined in the Modicon
Modbus Protocol Reference Guide PI-MODBUS-300 Rev. G and support Modbus function codes
01 through 06, 08, 15 and 16. These function codes are a subset of the complete protocol and are
defined in Table 3.2.
The choice of which query to use in a particular situation can significantly affect the efficiency of the
network. As an example, consider the situation where the Host requires the status of the coils, the
status of the digital inputs, the status of the faults, and the status of the timers and analog channels. This information can be obtained by using the 01 - Read Coil Status query, the 02 - Read Input
Status query, and 04 - Read Input Register query. To obtain this information, the Host would have
to send three separate queries, and the field unit would have to respond to each query separately.
A more efficient way to accomplish this same request for information would be through the use of
the 03 - Read Holding Register query. The Host would issue the 03 query (specifying the registers
to read), and the field unit would respond with one response that would contain all of the requested
information. The latter approach would generate considerably less network traffic than the former
approach, improving network capacity and response times.
In the strict sense, all transmissions from the Modbus master are called commands. In this manual,
a request for information, however, may be referred to as a query. Usually the term query will only
be used in conjunction with function codes (01), (02), (03), (04), and (08), which typically request
data. Commands are used in conjunction with function codes (05), (06), (15) and (16), which
typically initiate field unit action.
Examples
• The coil known as “coil 1” in the eld unit is addressed as coil 0000 in the data address eld of a
Modbus message.
• Digital input 129 decimal is addressed as digital input 0080 hex (128 decimal).
• Holding register 40001 is addressed as register 0000 in the data address eld of the message.
The function code field already specifies “holding register” operation. Therefore the reference
“4XXXX” is implicit.
• Holding register 40009 is addressed as register 0008 hex (8 decimal).
3.2.1 Modbus Function Code 01 (Read Coil Status)
This function code is used to read the coil status in the DDC-100 Field Unit. There are nine coils
available to be read on DDC-100 Field Units as shown in Table 3.3. For the MX/DDC or UEC-3-DDC
Field Unit, Coil 1 indicates CLOSE contactor and is interlocked with Coil 2, Coil 2 indicates OPEN
contactor and is interlocked with Coil 1. When the I/O Module is used in non-MOV (motor-operated
valve) mode, relays 1 through 6 or coils 3 through 8 are available for user configuration.
Table 3.3 – DDC-100 Coil Assignments, Modbus Function Code 01 Usage for Digital Outputs
Coil
Number
100Close / StopClose / StopClose / StopDo Not Use
201Open / StopOpen / StopClose / StopDo Not Use
302AS-1Lockout or Relay #3Lockout or Relay #3Relay #3
403AS-2Do Not UseRelay #4Relay #4
504AS-3Do Not UseRelay #5Relay #5
605AS-4Relay #6Relay #6Relay #6
706AR-1 (Opt)Do Not UseDo Not UseRelay #21
807AR-2 (Opt)Do Not UseDo Not UseRelay #12
908AR-3 (Opt)Do Not UseDo Not UseDo Not Use
Note 1: Relay #2 is physical Relay K2.
Note 2: Relay #1 is physical Relay K1.
Bit
Number
MX/DDCUEC-3-DDCDDC-100 ClamshellI/O Module
Example
Poll field unit number 3 for 8 coils starting at coil 1.
Query 0301000000083C2E
Response 03010118503A
Message Breakdown
QueryResponse
03Slave (Field Unit) Address03
01Function01Function
00Starting Address Hi01Byte Count
00Starting Address Lo18 1Data (Coils 8 - 1)
00No. of Points Hi503AError Check (CRC)
08No. of Points Lo
3C2EError Check (CRC)
Note 1: 18h equals 00011000 or coils 4 and 5 are ON.
Slave (Field Unit)
Address
3.2.2 Modbus Function Code 02 (Read Input Status)
This function code is used to read the discrete input status bits in the DDC-100 Field Unit. The use
of this function code will provide the user with the input status bits that are used to develop holding
registers 9 through 13. The status bit inputs are contained in locations 10129-10208 for each
DDC-100 Field Unit and are defined in Table 3.4.
Note 1: 01h equals 0000 0001 (actuator open input bit is ON).
Note 2: 08h equals 0000 1000 (actuator Channel B Fail bit is ON).
Data (Inputs 10136 - 10129)
2
Data (Inputs 10144 - 10137)
3.2.3 Modbus Function Code 03 (Read Holding Register)
This function code is used to read the binary contents of holding registers in the DDC-100 Field
Unit. This function code is typically used during the network polling cycle. A network poll should
consist of field unit registers 9 (Status) and 10 (Fault) as a minimum. Holding register 8 should
also be polled when the actuator is configured for the analog feedback option or position control.
See Table 3.5 for a complete listing of the holding registers.