This document is meant for use with the Limitorque MX Installation and Operation Manual for MX-05
through MX-40. Information in this document is also applicable to MX-85, MX-140, and MX-150. No
part of this book shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise without the written permission of Limitorque.
While every precaution has been taken in the preparation of this book, the publisher assumes no
responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the
use of the information contained herein.
This document is the proprietary information of Flowserve, furnished for customer use ONLY. No other
uses are authorized without written permission from Limitorque.
Limitorque reserves the right to make changes, without notice, to this document and the products it
describes. Limitorque shall not be liable for technical or editorial errors or omissions made herein;
nor for incidental or consequential damages resulting from the furnishing, performance or use of this
document.
The choice of system components is the responsibility of the buyer, and how they are used cannot be
the liability of Limitorque. However, Flowserve Limitorque’s sales team and application engineers are
always available to assist you in making your decision.
This manual contains information that is correct to the best of Flowserve’s knowledge. It is intended
to be a guide and should not be considered as a sole source of technical instruction, replacing good
technical judgment, since all possible situations cannot be anticipated. If there is any doubt as to exact
installation, configuration, and/or use, call Flowserve Limitorque at (434) 528-4400. The latest revisions
to this document are available online at http://www.limitorque.com
2
3
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
ODVA hereby issues this Declaration of Conformity to the DeviceNet™ Specification for the product(s) described below. The Vendor
listed below (the "Vendor") has holds a valid the Terms of Usage Agreement for the DeviceNet Technology from ODVA, which is
incorporated herein by reference, thereby agreeing that it is the Vendor’s ultimate responsibility to assure that its DeviceNet
Compliant Products conform to the DeviceNet Specifications and that the DeviceNet Specifications are provided by ODVA to the
vendor on an AS IS basis without warranty. NO WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ARE BEING PROVIDED BY ODVA.
In recognition of the below DeviceNet Compliant Product(s) having been DeviceNet Conformance Tested at ODVA-authorized Test
Service Provider and having received a passing result from ODVA at the Composite Test Revision Level specified below, this
Declaration of Conformity authorizes the Vendor to use the DeviceNet Certification Marks in conjunction with the specific DeviceNet
Compliant Product(s) described below, for so long as the Vendor's Terms of Usage Agreement for the DeviceNet Technology remains
valid.
DeviceNet CONFORMANCE TESTED ™
Certification Logo MarkCertification Word Mark
This Declaration of Conformity is issued on 27 February 2006
on behalf of ODVA by:
Katherine Voss
Executive Director
Vendor Information
Vendor Name Flowserve Corporation
Vendor Address 5114 Woodall Road
Lynchburg, VA 24506
USA
Test Information
Test Date 16-17 February 2006
Composite Test Revision 18
ODVA File Number 10331
Product Information
Identity Object Instance 1
Device(s) Under Test Value
Vendor ID (Identity Object Attribute 1) 966
Network Category Node
Device Type (Identity Object Attribute 2) 0
Device Profile Name Generic Device
Product Revision (Identity Object Attribute 4) 1.002
Products Covered Under This Declaration of Conformity
No. Product Code (Identity Object Attribute 3) Product Name (Identity Object Attribute 7) SOC File Name
119800 Flowserve MX DLI.stc
Declaration of DeviceNet Conformance –
ODVA Certification
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
Abbreviations
CIP Common Industrial Protocol
CAN Controller Area Network
COS Change of State
ODVA Open DeviceNet Vendor Association
UCMM Unconnected Message Manager
NV-RO Non-Volatile Read Only. Data is stored in non-volatile memory and can only be read. Data is
stored during Power-Off. For DeviceNet Limitorque Interface this storage area is FLASH
NV-RW Non-Volatile Read Write. Data is stored in non-volatile memory and can be read and write.
Data is stored during Power-Off. For DeviceNet Limitorque Interface this storage area is EEPROM
V-RO Volatile Read Only. Data is stored in volatile memory and can only be read (e.g. Status). Data is
lost during Power-Off. For DeviceNet Limitorque Interface this storage area is RAM
V-RW Volatile Read Write. Data is stored in volatile memory and can be read and write data is lost
during Power-Off, for DeviceNet Limitorque Interface this storage area is RAM.
DNFU DeviceNet Field Unit (PCB w/in actuator control compartment)
SPI Synchronous Peripheral Interface
PCB Printed Circuit Board
6
7
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
flowserve.com
1 Introduction
1.1 Purpose
This manual explains how to install and operate the Limitorque MX™/DeviceNet field unit (DNFU) and is
to be used as an addendum to Bulletin LMENIM2306, Limitorque MX Installation and Operation Manual.
Up to 63 actuators, each containing a DeviceNet field unit, may be connected by a single 5 strand,
twisted-pair cable to form a DeviceNet network, two wires for connection to the data highway and two
wires for connection to the DC power lines of the network highway, plus a screen connection. A suitable
power supply and termination resistors on the highway are required in order for the FU to function
correctly. This network permits the actuators to be operated by various control room devices such as a
distributed control system (DCS), a programmable logic controller (PLC), or a personal computer (PC).
The DeviceNet system communicates status and alarm data from each MX actuator.
1.2 How to Use this Manual
Each section provides the MX user with information on installing and operating the MX DNFU.
Section 1, Introduction: Details user safety and knowledge requirements, system capabilities, and
features.
Section 2, System Components: Focuses on the description of the DeviceNet system hardware and
software components.
Section 3, Installation and Configuration: Provides details for installing and configuring a DNFU.
Section 4, Object Model Diagram: Provides a list of inputs and outputs supported through the Assembly
Object system information.
Section 5, View DeviceNet Status
Section 6, Associated Documents
Section 7, Troubleshooting
Section 8, How to Order Parts
Section 9, Regulatory Information
Section 10, Wiring Diagram
1.3 User Safety
Safety notices in this manual detail precautions the user must take to reduce the risk of personal injury
and damage to the equipment. The user must read and be familiar with these instructions before
attempting installation, operation, or maintenance. Failure to observe these precautions could result
in serious bodily injury, damage to the equipment, warranty void, or operational difficulty. User must
follow local and state safety regulations.
Safety notices are presented in this manual in three forms:
WARNING:
c Refers to personal safety. Alerts the user to potential danger. Failure to follow
warning notices could result in personal injury or death.
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
CAUTION:a Directs the user’s attention to general precautions that, if not followed, could result in
personal injury and/or equipment damage.
NOTE: Highlights information critical to the user’s understanding of the actuator’s installation and
operation.
1.4 User Knowledge
It is recommended that the user read this manual in its entirety before the DeviceNet equipped actuator
is installed and operated.
The user needs to have a fundamental knowledge of electronics and microprocessor concepts. An
understanding of valve actuators and digital control systems is also of benefit to the DNFU user.
1.5 DeviceNet System Capabilities and Features
DeviceNet is a low cost communications protocol which permits up to 64 nodes (devices) to be
installed over a single network and is based upon CAN (Controller Area Network), a broadcast protocol
developed for the automotive industry. DeviceNet™ protocol is defined as an open network standard and
Limitorque’s device is certified for use by the ODVA, Open Device Standard Association. DeviceNet is
usually PLC input controlled and the Limitorque MX electronic actuator is well suited for this communication system. A typical network is seen in Figure 1.1.
Figure 1.1 – Typical Network
1.5.1 General Specifications
1.5.1.1 Network Specifications
DeviceNet is a digital, trunk/drop network that connects and serves as a communication network
between industrial controllers and I/O devices.
DeviceNet follows the Open Systems Interconnection (OSI) model, an ISO standard for network
communications that is hierarchical in nature. Networks that follow this model define all necessary functions from the physical implementation up to the protocol and methodology to communicate control
and information data within and across networks.
8
9
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
flowserve.com
Table 1.1 – Network specifications
Network SizeUp to 63 Nodes
Network LengthSelectable end-to-end network distance varies with speed
Bus TopologyLinear (trunkline/dropline); power and signal on the same network cable
Bus AddressingMulti-Master and Master/Slave special case; polled of change-of-state
System FeaturesSelectable end-to-end network distance varies with speed
Termination resistor (121 ohms) must be used at each end of the network
1.5.1.2 MX Field Unit Specifications
CIP Generic Device Profile (Device Type = 00hex) extended to DNFU requirements•
Group 2 Server•
UCMM capable device•
Predefined Master/Slave Connection Set supporting•
Explicit Connection•
Polled I/O Connection•
Bit-Strobed I/O Connection•
Change of State / Cyclic I/O Connection•
Full support of fragmentation protocol•
Device Heartbeat Message•
Device Shutdown Message•
Offline Connection Set•
Galvanical Isolation: The isolation voltage for the DNFU is up to 1,500 VRMS for 1 minute (1,800 •
VRMS for 1 second
Power Supply: The DNFU Interface will be powered from the DeviceNet bus. A switching regulator is •
used to generate the internal supply voltage: VCC nominal 5.0 V ± 5 %
Surge Suppression: The DNFU Interface is equipped with surge suppression for the DeviceNet •
network data and power lines. Surge suppression is compliant with IEC 61000-6-2:2001.
125 Kbps 500 m (1,640 ft)
250 Kbps 250 m (820 ft)
500 Kbps 100 m (328 ft)
(exception-based)
Environmental conditions
The DNFU environmental parameters are within the same environmental constraints as the actuator.
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
2
1
2
3
7
8
4
5
11
12
10
6
9
2 System Components
2.1 Introduction
This section gives an overview of the components used in the DeviceNet system. The field unit is
installed in each MX actuator. The network cable connects the field unit to the network via the actuator
terminal block. The network cable is connected to a host controller, typically a PLC.
2.2 Hardware
NOTE: Recommended storage procedures are detailed in Bulletin LMENIM2314 Limitorque MX
Maintenance and Spare Parts Manual. Failure to comply with recommended procedures will void the
warranty. For longer-term storage, contact Limitorque for procedures and recommendations.
Figure 2.1 – MX-05 Actuator
10
Table 2.1 – MX-05 Actuator
1 Handwheel
2 Declutch Lever
3 Oil Fills (dotted arrow depicts fill on declutch side)
4 Controls Compartment (field unit location)
5LCD Display
6Control Knobs
7Ground Lug
8Thrust/Torque Base
9Conduit Entries
10Terminal Compartment
11Motor
12Nameplate
2.2.1 Limitorque MX
The MX is a multi-turn valve actuator designed for operation of ON-OFF and modulating valve applications. This actuator controls the opening and closing of valves. See Figure 2.1.
11
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
flowserve.com
The MX features include:
Non-intrusive setup •
Separately sealed terminal chamber •
Absolute encoder for valve position sensing (no battery required) •
32-character LCD for indication and calibration with configuration permitted in six languages. •
Sophisticated electronic control, monitoring, and diagnostic capabilities with LimiGard™ •
technology
2.2.2 DeviceNet Field Unit
The DeviceNet field unit is installed in the MX controls compartment. This unit permits the actuator to
be controlled by a host controller, typically a PLC, via the DeviceNet network. The DNFU includes two
high-level, surge-protected, and isolated network communication channels, configurable digital I/O, and
configuration via LCD screen. The following commands and information may be transmitted over the
DeviceNet network:
“OPEN,” “STOP,” and “CLOSE” commands •
“ESD” and “MOVE–TO” position commands •
Actuator status and alarm messages •
Six digital inputs and two analog inputs for user •
A surge-protected and isolated communication channels •MX control panel configuration•
Torque output (for reference only) and position feedback •
Four digital outputs (standard) •
Figure 2.2 – DeviceNet Field Unit
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
2.2.3 Hardware interface
The DeviceNet Limitorque Interface is comprised of a minimum of one PCB with two interfaces - One
for the DeviceNet Terminal Block connector and one for the SMT Main Board.
Figure 2.3 gives an overview about the hardware. The microcontroller on the DeviceNet Limitorque
Interface handles the DeviceNet protocol, stores the DeviceNet parameters in an EEPROM, and communicates with the SMT Main Board via SPI.
Figure 2.3 – DeviceNet Limitorque Interface
12
2.2.4 Network Cable
DeviceNet is a CAN - based protocol that uses 5 wires including a shield. Two of the conductors are
used for 24V DC power & up to 8 amps (4 amps for NEC Class 2) may be passed along the hi-way from
a suitable power source. Two conductors are used for the CAN bus signals, CAN_H and CAN_L, which
are usually smaller in diameter. Limitorque recommends Belden cable for connecting to a DeviceNet
network. The specifications for thick and thin cable (per site requirements) are as follows:
Table 2.2 – Belden Cable Specifications
Belden
Part No.
3082A
3084A
AWG
(Stranding)
dia. Inches
Nom. DCR
2 – 15 AWG
(19 x 28)
3.6 ohm/1000 ft
11.8 ohm/km
2 – 18 AWG
(19 x 30)
6.9 ohm/1000 ft
22.7 ohm/km
2 – 22 AWG
(19 x 34)
17.5 ohm/1000 ft
57.4 ohm/km
2 – 18 AWG
(19 x 36)
28.0 ohm/1000 ft
91.9 ohm/km
Insulation
material
(color code)
Power pair
(Black/Red)
Data pair
(Blue/White)
Power pair
(Black/Red)
Data pair
(Blue/White)
Nominal
O.D.
12.2 mm 120 12.0 pF/ft
7.2 mm12012.0 pF/ft
Nom
Impedance
(ohms)
Nominal
Capacitance
Test
Frequency
(MHz)
0.125
0.5
1
0.125
0.5
1
Maximum
Attenuation
dB/100ft
0.13
0.25
1.36
0.29
0.50
1.70
13
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
flowserve.com
Table 2.3 – Total cable length between repeaters or nodes:
Network Size125 KBPS 250 KBPS500 KBPS
Thick Trunk Length500 m (1,640 ft) 250 m (1,640 ft)100 m (1,640 ft)
Thin Trunk Length100 m (328 ft)100 m (328 ft)100 m (328 ft)
Flat Trunk Length380 m (1,250 ft)200 m (656 ft)75 m (246 ft)
Maximum Drop Length6 m (20 ft)6 m (20 ft)6 m (20 ft)
Cumulative Drop Length156 m (512 ft)78 m (256 ft)39 m (128 ft)
Note: Each actuator includes 0.60 meters of internal drop length.
3 Installation and Configuration
3.1 Site and Network Cable Preparation
3.1.1 Site Preparation
Prepare the site and associated equipment for operation of the DeviceNet controlled MX actuators as
follows:
1. Prepare a detailed site plan consisting of the following:
Actuator locations, tag numbers, DeviceNet addresses •
Junction boxes, terminal strip locations, and tag numbers •
2. Provide free access to the MX control panel and terminal block for setup, configuration, and
troubleshooting.
3. Prepare cable and label all wires. See Section 3.1.2, Network Cable Preparation.
4. Install power and control wires in separate conduits. Shielding is not sufficient to prevent induction
of stray voltages onto signal leads from the power lines.
5. Install and verify earth grounds.
NOTE: Limitorque defines an effective local earth ground as a low impedance (less than 5 ohms) path
to:
A ground electrode placed in close vicinity of the actuator that is free of ground loop currents. OR •
A safety ground that is free of ground loop currents running from the actuator back to the system •
ground electrode. If the signal wiring is run on aerial cable where it may be exposed to highenergy electrostatic discharge (such as lightning), a low impedance path to ground that is capable
of high current must be provided a short distance from the actuator as described above. OR
A power distribution grid identifying the impact of power isolation to a particular actuator or •
group of actuators should be provided.
3.1.2 Network Cable Preparation
3.1.2.1 Network Cable Connection to the Field Unit
The DeviceNet field unit is connected to the network via the MX terminal block. The network cable is
connected to the terminal block as shown in Figure 3.1.
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
NOTE: Recommended DeviceNet cable is Belden 3084A or equal. 121 ohm, ¼ W +/-1% termination
resistors must be connected at each segment end. Customer is required to connect wire between
terminal 30 and chassis ground for surge protection. Preferred network wiring is to connect shield to
terminal 48 for only one unit on each segment. Connect remaining individual network cable shields
together to ensure proper shielding of entire network. Consult wiring diagram for exact terminal connection points as they may change.
Prepare the network cable for connection to the MX terminal block as follows.
CAUTION:
a Strip stranded conductors carefully; do not damage the strands. This will weaken the
conductor. Do not nick conductors or conductor insulation when stripping away the insulation.
Nicking stresses the conductor and can cause the conductor to break. This type of damage may
not be apparent and failure can occur later without warning.
NOTE: Excess cable should be cut, not coiled or looped, to prevent noise induction into the network and
to reduce signal loss through unnecessarily long cable runs.
Cable Preparation
1. Remove two to three inches (5 to 8 cm) of the outer plastic jacket.
2. Separate the cable parts. Unbraid the shield and peel back the foil shield to the same point where
the outer jacket was removed. Cut away the braided shield and the foil shield. Strip the insulation
from the conductors approximately 0.4 inch (1 cm).
3. Apply heat shrink tubing to insulate the drain wire and to provide stress relief to the cable.
CAUTION:a Do not melt the insulation. NOTE: Ungrounded drain wires should be cut even with
the cable sheath. The brand foil and drain wire should have heat shrink tubing applied.
4. Install ring tongue connectors. Flowserve recommends the use of Thomas & Betts #RZ22-6 for
optimum results.
5. Connect the network cables to the MX terminal block as shown in Wiring Diagram #18-499-0181-3.
Table 3.1
3Shield
14 (Blue) DATA (-)
13 (White) DATA (+)
4 (Black) Network 0 V
5 (Red) Network 24V
EGND Earth ground for surge protection circuit
14
NOTE: Ground each segment of the cabling at only one point to prevent ground loops, which can affect system
performance. Verify the actuator is properly grounded.
6. Install jumper cable from terminal block pin 30 to earth ground or ground lug.
Loading...
+ 30 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.