Reference Manual Smart Control Module

Reference Manual Smart Control Module
Reference manual
DOC.RM.QC34.E Rev: 0
January, 2013
FieldQ Valve Actuator
QC34, Foundation Fieldbus Control Module
www.FieldQ.com
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Contents
AESSENTIAL INSTRUCTIONS
A1
A2
A3
A4
A5
A6
A7
A8
A9
A10
A11
Before you start . ......................................... 3
Orientation (see fig. A1)............................... 3
Applicable control modules.......................... 3
Installation, operation and maintenance
reference documents................................... 3
Operating medium........................................ 3
Product integrity........................................... 3
Hazardous areas.......................................... 4
Warning ; Moving parts................................ 4
Prevent moisture entering the actuator........ 4
Warning ; Magnetic material......................... 4
Warning ; Temperature range....................... 4
1 Module Description
1.1
1.2
1.3
1.4
1.5
1.6
1.7
Page 2
3
5
FieldQ™ Foundation Fieldbus™ Control
Module......................................................... 5
Foundation Fieldbus™ Communication......... 6
Device Description and Methods................. 6
Node Address............................................... 6
Foundation Fieldbus™ function blocks......... 6
Related Information...................................... 7
Specifications, Foundation Fieldbus™ Hardware............................................................. 7
2 Installation
2.1
2.2
2.3
2.4
2.5
Introduction.................................................. 8
Applicable control modules.......................... 8
Before starting.............................................. 8
Pneumatic connections................................ 8
Electric connections..................................... 9
3 Commissioning
3.1
3.2
3.3
3.4
16
Resource block.......................................... 16
Transducer block........................................ 25
5 Operations and Maintenance
5.1
5.2
5.3
11
Implementation of the device driver in the
host system................................................ 11
Initialization................................................ 11
Function block assignments....................... 13
Troubleshooting.......................................... 14
4 Detailed Configuration
4.1
4.2
8
38
Fault state.................................................. 38
Restart method........................................... 38
Restarting the module................................ 38
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
AESSENTIAL INSTRUCTIONS
READ THIS SECTION BEFORE PROCEEDING!
A1
Before you start
A4
• FieldQ pneumatic actuators must be isolated both
pneumatically and electrically before any (dis)assembly is begun.
• It is not permitted to connect a pressure vessel
with unreduced media to the FieldQ pneumatic
actuator.
• FieldQ actuators must not be connected to an air
supply greater than 8 bar g or 120 psig
• This manual does not provide instructions for
installations in hazardous areas. See applicable
sections of Installation Guide DOC.IG. QC34.1 or
installations in hazardous areas.
• Installation, adjustment, putting into service, use,
assembly, disassembly and maintenance of the
pneumatic actuator must be done by qualified personnel.
A2
Orientation (see fig. A1)
The FieldQ actuator is an integrated concept for the
automation of quarter turn valves, dampers or other
quarter turn applications. It consists of three basic
parts:
1.Pneumatic actuator
2.Pneumatic Module
3.Control Module
A3
Applicable control modules
Installation, operation and
maintenance reference documents
Before mounting, installing, commissioning or (dis)
assembling the actuator consult the following documents:
- All chapters of this Reference manual and
- Installation Guide of the supplied Control Module.
- For installation in hazardous area’s:
Hazardous Area Control Drawing installation instructions, as shipped with the Control module.
All these items are available from www.FieldQ.com or
through your local Valve Automation representative).
A5
•
•
•
•
Operating medium
Air or inert gasses.
Air filtered at 5 micron.
Dew point 10 K bellow operating temperature.
For subzero applications take appropriate measures.
A6
Product integrity
• Assembly or disassembly is only allowed for replacing seals and guide bands (soft parts).
• Under the European Pressure Equipment Directive, conversion of actuators may only be performed by companies or personnel, authorized by
Emerson Process Management .
QC34 -Foundation Fieldbus™
QC34 -Foundation Fieldbus™ Non-Incendive
or Non Sparking
QC34 -Foundation Fieldbus™ Intrinsically safe
Check the module label for the right execution.
1
2
3
OK!
Fig A.1Orientation
Control Module Type Label =
QC34... = Foundation Fieldbus™
Fig A.2 Module check
Page 3
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
A7
Hazardous areas
Improper installation in a hazardous area can cause
an explosion.
• Assembly, disassembly and maintenance
must be done outside potentially explosive
area’s
• For information about installation in a hazardous area, refer to the appropriate sections of the Installation Guide, as shipped
with the control module.
A8
Warning ; Moving parts
• Applying pressure to the actuator or
• Applying a control signal to the Control
module, may cause the actuator/valve assembly to operate.
A9
Prevent moisture entering the
actuator
Condensation or moisture that enters the actuator,
the pneumatic module or the control module can
damage these components and can result in failures.
Therefore:
• Try not to mount the actuator with the
conduit openings or the air entries, pointing
upward.
• Ensure integrity of gaskets and o-rings.
• Install drip loops in conduit or cable.
• Seal all conduit openings whether used or
not.
Page 4
A10
Warning ; Magnetic material
• Do not put the FieldQ in direct contact with
magnetic material. This can cause damage
or malfunction.
A11
Warning ; Temperature range
• Do not exceed the temperature limits of the
module as specified in this manual or in the
Installation Guide DOC.IG.QC34.1.
This can cause damage or malfunction.
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
1
Module Description
1.1
FieldQ™ FOUNDATION Fieldbus™ Control Module
This manual contains installation, operating, and
maintenance information for the FieldQ™
FOUNDATION Fieldbus™ module (Figure 1).
Only qualified personnel should install, operate, and
maintain this module. If you have any questions
concerning these instructions or for information not
contained in this instruction manual, contact your local Valve Automation sales office or sales representative for more information.
The FieldQ module is an interoperable, processcontrolling, communicating, microprocessor-based,
module. In addition to its primary function of controlling the position of the valve, the FieldQ module, using FOUNDATION Fieldbus™ communications protocol,
gives easy access to information critical to process
operation, as well as process control. You can gain
information from the principal component of the
process, the control valve itself, by using a personal
computer or operator’s console within the control
room.
Using a compatible field bus configuration device,
you can obtain information about the health of the
module and the actuator and valve control elements.
You can also obtain asset information about the module. You can set input and output configuration parameters. Using the FOUNDATION Fieldbus™ protocol,
information from the module can be readily integrated
into a control system.
The FieldQ module is an assembly in an IP65 /
NEMA4X enclosure that provides input and output
signals to control and monitor the FieldQ actuator.
The module is self-contained providing control and
position feedback via the Field bus interface.
Figure 1.2 provides a cutaway view of the module
with key connection points labeled. Connect to the
module by removing the cover, inserting the wiring
through the electrical entries and connecting each
wire to the proper location on the terminal board.
More information about connecting a module can be
found in §2.5.
After connecting the module, set the limit switches
for the module by running the initialization procedure
described in section §3.2
Wiring
Terminals
Status
LED
Reassignment
buttons
Fig 1.1 FieldQ FOUNDATION Fieldbus™ Module
Fig 1.2 Cutaway of the QC34 Control Module
Page 5
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
1.2
Foundation Fieldbus™
Communication
The FieldQ QC34 module uses the Foundation Fieldbus™ protocol to communicate with other field devices and the host system. Foundation Fieldbus™ is
an all-digital, serial, two-way communication system,
which interconnects field equipment such as transmitters, valve controllers, and process controllers. Field
bus is a local-area network (LAN) for devices used
in both process and manufacturing automation with
built-in capability to distribute the control application
across the network.
The field bus environment is the base level group of
digital networks in the hierarchy of plant networks.
The field bus retains the desirable features of analog
systems such as:
 A standardized physical interface to the wire
 Bus-powered devices on a single wire pair
 Intrinsic safety options
In addition, use of FOUNDATION Fieldbus™ enables:
 Increased capabilities due to full digital communications
 Reduced wiring and wire terminations due to multiple devices on a single pair of wires
 Increased selection of suppliers due to interoperability
 Reduced loading on control room equipment available by distributing control and input/output functions to field devices
 Speed options for process control and manufacturing applications
For more information on the operation of the FOUNDATION Fieldbus™, refer to your DeltaV documentation
and the FOUNDATION Fieldbus™ specifications.
1.3
Device Description and Methods
This manual describes device setup using the Device
Descriptions (DD) specified by the FOUNDATION Fieldbus™ protocol. Parameter access and methods are
also described in this manual. FOUNDATION Fieldbus™
uses the DD, Function Blocks, and a Capabilities
File to achieve interoperability between the module
and field bus components from other manufacturers in the control systems including hosts and other
devices. The DD provides information to describe
the data interface to the device while the Capabilities
File provides information about the device to enable
the creation of a control strategy without a physical
device (off-line configuration).
Page 6
For field bus devices, in addition to providing parameter definitions and other information required by the
control system to communicate with the device, the
DD may also include methods. Methods can be used
for a variety of functions including remote restarting
of the control module. Methods are a predetermined
sequence of steps using a structured programming
language and the interface definition for the module.
How the method prompts and how messages appear
is determined by the host system. For information on
using methods on the host system, see Appendix E
and the appropriate host system documentation.
1.4
Node Address
The default node address of the FieldQ QC34 module is 247 (status = standby).
Use the host system to commission the module and
assign it a working address. For information on using
the host system for device commissioning and assigning addresses, see the appropriate host system
documentation.
1.5
Foundation Fieldbus™ function
blocks
Function blocks, within a field bus device, perform the
various functions required for process control, such
as process variable input, output, and control functions such as Proportional/Integral/Derivative (PID)
functions. The standard function blocks provide a
common structure for defining function block inputs,
outputs, control parameters, events, alarms, and
modes. Then, function blocks can be combined into
a process that can be implemented within a single
device or in multiple devices via the field bus network.
The following function blocks are implemented in the
FieldQ module.
 Resource Block (RB)
 Transducer Block (TB)
 Analog Input (AI) Function Block
 Discrete Output (DO) Function Block
 2x Discrete Input (DI) Function Block
 PID Function Block
Function Block parameters and usage is described in
the host system documentation. Please refer to this
documentation for detailed information on function
blocks.
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
1.5.1
Resource Block
The Resource Block contains hardware and electronics information. There are no linkable inputs or
outputs to the Resource Block.
1.5.2
Transducer Block
The Transducer Block is the primary interface to the
control function of the device. This Transducer Block
contains all the parameters necessary to configure
the device and set diagnostics parameters.
1.5.3
Analog Input (AI) Block
The Analog Input (AI) function block processes field
device measurements and makes this data available
to other function blocks.
The AI block supports alarming, signal scaling, signal
filtering, signal status calculation, mode control, and
simulation. The AI block is widely used for scaling
functionality.
1.5.4
Discrete Output (DO) Block
The Discrete Output (DO) function block processes a
discrete setpoint then outputs the setpoint to a specified I/O channel to produce an output signal. The DO
function block supports mode control, output tracking,
and simulation. There is no process alarm detection in the block. In operation, the DO function block
determines its setpoint, sets the output, and, as an
option, checks a readback signal from the field device
to confirm the physical output operation.
1.5.5
Discrete Input (DI) Block
The Discrete Input (DI) function block processes a
single discrete input from a field device and makes
it available to other function blocks. The DI function
block supports mode control, signal status propagation, and simulation.
1.6
Related Information
1.6.1
Foundation Fieldbus™ Installation
and wiring guidelines
Foundation Fieldbus™ Technical Overview (available
from the Fieldbus Foundation)
1.6.2
Other Related Information
Other documents containing information related to
the FieldQ Control module include:
1.604.02
Control Module data sheet
DOC.IG.QC34.1 Installation Guide QC34 Control
Module with Foundation Fieldbus™
These documents are free available for download
from www.FieldQ.com or contact your local FieldQ
representative.
1.7Specifications, Foundation Fieldbus™
Hardware
Electrical Entry
2 x M20 or 1/2” NPT
Electrical Input, Field bus Interface
Voltage Level
:9 to 32 volts
Nominal Current
:18 mA, maximum
Reverse Polarity :Unit is not polarity sensitive
Protection
Required external :Restrict the power supply
protection current to <600mA.
Function Blocks Available
Analog Input (AI)
Discrete Input (DI)
Discrete Output (DO)
PID to Proportional/Integral/Derivative
Digital Communication Protocol
Manchester-encoded digital signal that conforms to
IEC 1158-2 and ISA 50.02
Operating Ambient Temperature Limits
-20°C to +50° C (-4° F to 122° F)
Electrical connections
Terminal Block
Optional quick connectors
Housing
Material :Aluminum Alloy
Finish
:Polyester non-TGIC based powder
coating
Enclosure :IP65 / NEMA 4X
Page 7
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
2
Installation
2.1
Introduction
The FieldQ Foundation Fieldbus™ Control module is
a two-wire device powered by the bus.
For various application guides like installation and
wiring guidelines please check:
www.fieldbus.org/About/FoundationTech/Resources/
The following sections provide instructions on pneumatic and electric installations. For instructions on
commisioning, see chapter 3.
2.2
Applicable control modules
QC34 -Foundation Fieldbus™
QC34 -Foundation Fieldbus™ Non-Incendive
or Non Sparking
QC34 -Foundation Fieldbus™ Intrinsically safe
2.3
Before starting
* Be sure that the actuator is correctly mounted on
the valve before connecting air supply and electrical wiring (see Installation & Operation Manual
FieldQ Valve Actuator, DOC.IOM.Q.E)
* Check the module label for the right execution (see
fig. 2.2)
* Check the type of actuator: single or double acting
(see fig. 2.2)
2.4
Pneumatic connections
IMPORTANT
* The actuator/valve combination can move after connecting
the air supply.
*Ensure that the pneumatic module and the control module
are mounted properly to the actuator to achieve a degree of
ingress protection rated IP65/NEMA4X, before connecting
the air supply.
* Check the maximum pressure Pmax = 8bar/116Psi
* Be sure that the minimum required supply pressure for the
application is available at the actuator.
* Condensation or moisture that enters the actuator, the
pneumatic module or the control module can damage
these components and can result in failures.
* The venting ports on the pneumatic module (see fig. 3)
are equipped as standard with silencers/filters rated IP65/
NEMA4X.
* In case IP65/NEMA4X ingress protection is required, the
exhaust ports Ra and Rb and the electrical entries must be
fitted with devices rated IP65/NEMA4X or higher.
2.4.1
*
*
*
*
Operating media
Air or inert gases.
Air filtered at 5 micron.
Dew point 10 K bellow operating temperature.
For subzero applications take appropriate measures.
2.4.2Single acting (spring return) or
Double acting actuator
OK
OK
1 Remove the plug from the air supply (Ps).
2 Connect air supply to port (Ps).
Single
acting
Venting ports
Fig. 2.1: Check proper mounting before connecting
air supply and electrical wiring.
Rb
Module cover
Ps : 1/4”BSP or 1/4”NPT
Double
acting
Control Module Type Label =
Control
OK QC34... = Foundation Fieldbus™
Ra
OK Actuator Type Label =
Rb
QS xxxx = Single acting (Spring Return)
QD xxxx = Double acting
Fig. 2.2 Identification
Page 8
Ps : 1/4”BSP or 1/4”NPT
Fig. 2.3: Pneumatic connections
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
2.5Electric connections
2.5.1Electrical Input, Field bus Interface
Voltage range *
9 to 32 volts
2.5.2Electrical data of the hazardous area
executions
Reverse polarity
protection
Unit is not polarity sensitive.
Please check the following Chapters of Installation
Guide (DOC.IG.QC34.1) for electrical data in case
the control module is used in a Hazardous location:
Required external protection
Restrict the power supply
current to <600mA
Non incendive/Non Sparking
- QC34 FF (FNICO) Chapter 10
Maximum current 18 mA
Environmental conditions :
Temperature *
-20°C to +50°C
(-4°F to +122°F)
Humidity
0 to 85% at 25°C(+77°F)
derate to 50% above 40°C
(104°F) (non-condensing).
Altitude
Use
Operating full power available up to 2000 meter (6000
feet).
In- and outdoor.
* In case the Control module is used in Hazardous
locations, check the Control Drawings as per chapter 4.2 for the applicable temperature or voltage
range.
Intrinsically safe
- QC34 FF
- QC34 FF (FISCO)
2.5.3
Wiring dimensions
Solid wire :
Stranded wire :
2.5.4
Chapter 11
Chapter 12
2.5mm2 max.
0.2-3.3mm2 or 24-12 AWG
Tools
Tool for terminals
:Screw driver 0.6 x 3.5
Tool for cover screws :Screw driver for cross
slotted Phillips screws nr. 2
Page 9
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
WARNING:
Control Module
Type Label
* Do not put the Control module and the Pneumatic module
in direct contact with magnetic material. This can cause
damage or malfunction of the position feedback.
* If the Control module is used in a manner not specified by
the manufacturer, the protection provided by the equipment may be impaired.
* If required, mount earth wire (1) between top (2) and bottom (3) ring of earth wire connection (see figure 2.5.2).
2.5.5
Procedure
1 Remove control module cover (see figure 2.5.1)
2 Guide the cable(s) through the electrical entry(ies).
- Use and mount cable glands as required by national or local legislation.
- When IP65/NEMA4X ingress protection is required, the electrical entries must be fitted with
glands rated IP65/NEMA4X or higher.
3 Connect the Foundation Fieldbus™ signal to the
applicable terminals (see figure 2.53).
- For 7/8” or M12 quick connector pinout, see fig 6.
- For hazardous area connections, see the control
drawings as indicated in chapter 2.5.2.
4 Mount the control module cover to the housing (see figure 2.5.1) or continue with chapter 3.
Take care that the cover seal is in place to comply to dust and water tightness according IP65 /
NEMA4X.
2.5.6
Terminals
Status LED
Fig. 2.5.1Installing wiring
Fig.2.5.2 Earth wire connection
Field wiring
Foundation Fieldbus™ installation
and wiring guidelines
For various application guides like installation and
wiring guidelines please check:
www.fieldbus.org/About/FoundationTech/Resources/
Actuator wiring
FF
+
Power
supply
-
1
2
3
Fig. 2.5.3Terminal and quick connector connections
Quick connector pinouts:
(male chassis part)
1
2
7/8" UNC
3
4
4
1
3
2
2
4
1
Brown
1
Green/Yellow 2
Blue
M12
Quick connector
Fig. 2.5.4Quick connector pinouts
Page 10
3
Terminal
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
3
Commissioning
In order to commission the QC34 module three steps
need to be done in advance:
1 Implementation of the device driver in the host
system.
2 Initialization of the FieldQ QC34 module.
3 Function block assignment to channels.
3.1
Implementation of the device driver
in the host system.
Two versions of the DD-drivers are available for the
QC34 module:
- QC34 Standard DD Rev 3 - DD files for use with
other Foundation FieldBus host systems and tools
- QC34 PlantWeb DD Rev 3 - DD files tailored specifically for use with Emerson PlantWeb Systems
(DeltaV).
These DD drivers are available for download from
www.FieldQ.com.
Please, see the documentation of your host system,
how to implement these device drivers in your host
system.
3.2
Initialization
Initialization finds the end positions of the actuator.
Switching will then occur within the end stop offsets
from these end positions. This process is done automatically, by the module, however, the user must start
it and the unit must be wired according
chapter 2. The initialization process can be started in
two ways:
1.Initialization using the local buttons (see §3.2.1).
2.Initialization using a bus command (see §3.2.2).
WARNING:
* During the initialization routine the actuator /valve combination will cycle several times.
* Before initialization check whether the actuator and valve
have the same “Open” and “Closed” positions.
*Ensure that the valve stroke is not obstructed before the
initialization routine is started.
"Close"
End stop
offsets
End stop
offsets
end position
10˚max
±40˚
±40˚
10˚max
"Open"
end position
Factory settings
Setting after initialization
Fig 3.1 Feedback characteristics
Page 11
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
3.2.1
Initialization using local buttons
For "Initialization using the local buttons" digital communication is not required, power supply is necessary
(9V to 32V DC).
1 Push "Open" and "Closed" reassignment buttons
at the same time for 4 seconds.
2 Status LED will blink.
3 Actuator will cycle 2 or 3 times.
4 At the end of the routine the Status LED switches
to constant on, indicating that the initialization was
successful.
Table 3.1Status LED indications
Status
Status LED action
OK (init successful) Constant on
Initializing
Blinking (see fig 3.2)
Init error
Flashing (see fig 3.2)
Init default
Flashing (see fig 3.2)
Identification
Flashing for 5 minutes
Table 3.2Button board functionality
Action
Set to factory
default
Initialize
Reassignment buttons
Push both buttons and hold
while powering up. Release buttons when Status LED is solid.
While powered up push both
buttons until Status LED starts
blinking
Remarks:
- If the Status LED is flashing, the auto initialization
(calibration) routine has failed, see §3.4.2.
- If the read out in the PLC or DCS is reversed,
see §3.4.3.
- If the device is in operation and after a while the
"Open" or "Closed" feedback is lost, see §3.4.4.
- If the initialization can not be started via the push
buttons, see §3.4.5.
Page 12
Closed
reassignment
button
Status LED
Push
4 sec.
Open reassignment
button
on
LED = Flashing
off
on
off
LED = Blinking
Time
* The default setting of the reassignment buttons is:
enabled when the unit is in “Out of Service”.
* ”Open” and “Closed” LED are disabled.
Fig. 3.2 Reassignment buttons (located behind front
cover of module).
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
3.2.2
Initialization using Bus Command
1 Set the Transducer Block to “Out of Service”.
2 Set sub-parameter “AUTO_INIT_COMMAND”
(Auto Calibration Command) of parameter AUTO_
INITIALIZATION (Auto Calibration) to start auto
init.
3 When the initialization is running, AUTO_INIT_
STATUS (Calibration Status) will indicate running
and the Status LED will blink.
4 Actuator will cycle two or three times.
5 When the initialization is successful, AUTO_INIT_
STATUS (Calibration Status) will indicate successful and the Status LED is on.
6 Set the Transducer Block to “Auto”.
Remark:
- If the auto initialization has failed, the status LED
on the module is flashing and the status of parameter AUTO_INITIALIZATION (Auto Calibration) will
indicate a possible cause, see §3.4.2
- After initializing check if the feedback matches the
actual valve position. If the position feedback in the
PLC or DCS is reversed, see §3.4.3.
- If readjustment of the positions is needed, without
cycling the actuator, see §3.4.4
- If it is not possible to finish the auto-initialization
routine, the switch points can be set, according
§3.4.3
3.3
Function block assignments
1 Set the required Function Block(s) to “Out of Service”.
2 Set the required channel number(s). The following
are the basic channel assignments that should be
used when using the FF QC34 Control Module:
3 Assign Channels and signals to the appropriate
function blocks (see table 3.3)
4 Download the Function Block(s) to the “system”.
5 Set the Function Block(s) to “Auto”.
3.3.1
Check functioning
Before function test:
- Check or set “Resource Block” to “Auto”.
- The unit must be connected to a host system and
power must be connected (see chapter 3).
- The unit must be successfully initialized (Status of
Transducer Block AUTO_INITIALIZATION (Auto
Calibration) must be successful.
1 Set the Transducer Block to “Out of Service”.
2 Set the DO Function Block to “Out of Service”.
3 Set channel number of the DO Function Block
block to 1 ("Output Command").
4 Download the settings to the system.
4 Set the Function Block to the “Auto” mode.
6 Set parameter "SP_D" to “ open”.
7 Actuator moves to "Open" position.
8 Set parameter "SP_D" to “ closed”.
9 Actuator moves to "Closed" position.
10Set the Transducer Block to “Auto”.
3.3.2
Recognizing LED
To recognize a particular FieldQ actuator in the plant
“Recognizing LED” function can be activated in the
Transducer Block . When this function is activated,
the status LED will blink for 5 minutes. To start the
LED:
1 Set “FLASH_LED”-parameter to start.
2 Status LED on the unit will blink for 5 minutes.
3 After 5 minutes the “FLASH_LED”-parameter will
change back to finished.
Table 3.3Function block assignments
Function Signal
block
DO
Command to the actuator to
open or close
DI
Feedback from the actuator
indicating open, close, opening or closing
Switch 2 (Open) state from
the actuator indicate active or
inactive
Switch 1 (Closed) state from
the actuator indicate active or
inactive
AI
Temperature of the electronics (default in°C).
Channel
1
2
3
4
5
Page 13
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
3.4
Troubleshooting
3.4.1
“Factory default settings”, using the
button board.
To set the control module to its factory default settings, do the following;
1 Connect power according chapter 4 and observe
that the Status LED is either on or flashing.
2 Disconnect the power.
3 Press both reassignment buttons.
4 Reconnect power.
5 Status LED goes on.
6 Release the reassignment buttons.
7 Observe that the Status LED indicates that the unit
is in its “Init Default” state (flashing)
3.4.2
If auto initialization (Auto Calibration)
procedure has failed
If the auto initialization (Auto Calibration) has failed,
the status LED on the module will flash and the status
of the AUTO_INITIALIZATION parameter will indicate
a possible error:
Table 3.4Status of the initialization procedure:
Error
Solution
Undetermined bad
repeatability
Check air-pressure at the actuator and/or actuator sizing.
Running,
Aborted
Operator: restart
Undetermined
Difference between open
and close position too small.
Check proper stroking of the
actuator/valve unit.
Time Out
It takes too long before endpositions are found. Check
air-pressure at the actuator
and/or actuator sizing.
Range Error
Difference between open and
closed end position is too
small. Check air-pressure,
check proper valve rotation.
Successful
No Valid Data
Page 14
Not initialized, start initialization
To solve this:
1 Check table 3.4 and try the suggested solution to
solve the problem.
2 Check Actuator assembly code (see Installation
& Operation Manual FieldQ Valve Actuator, DOC.
IOM.Q.E)
3 Repeat the initialization (calibration) procedure
(see §3.2).
4 When the actuator does not move within 10 seconds, the auto initialization (calibration) will fail.
To solve this either;
- Perform the “default setting” procedure (see
§3.4.1) and repeat the initialization procedure
(calibration; see §3.2), or
- Set the limit switch points individually by the
bus (see §3.4.4)
3.4.3
If the position feedback is reversed.
1 Go to Transducer block.
2 To set the "Open" position;
Set sub parameter OPEN_END_POSITION of
parameter CFG_SWITCH_POINTS to:
"set to current position".
The "Closed" position will change automatically.
3 To set the "Closed" position;
Set sub parameter OPEN_END_POSITION of
parameter CFG_SWITCH_POINTS to:
"set to current position".
The "Open" position will change automatically.
Note:
- If "Shutdown" is activate (see 4.2.3.3), check if
"Action" is still "OK".
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
3.4.4
If the "Open" or "Closed" feedback is
lost.
1 Check if the actuator/valve unit is working correctly.
2 If it is safe to cycle the actuator, perform the initialization procedure (see §3.2).
3 If it is not safe to cycle the actuator, perform the following procedure:
1 Go to Transducer block.
2 In case the "Open" position is lost:
Set sub parameter OPEN_END_POSITION of
parameter CFG_SWITCH_POINTS to:
"set to current position".
3 In case the "Closed" position is lost:
Set sub parameter CLOSE_END_POSITION of
parameter CFG_SWITCH_POINTS to:
"set to current position".
Note:
- If the problem is persistent, increase the endstop
offset (see 4.2.3.2).
3.4.5
3.4.6
If the device is in Shutdown
When the device is in Shutdown an internal failure
has occurred.
If the internal failure is re-solved, the actuator shutdown status can be manually reset (Transducer
block, parameter SHUTDOWN_CFG).
1 Normally the SHUTDOWN_RESET parameter is
inactive. For reseting the shutdown status parameter SHUTDOWN_RESET must be set to Reset.
2 When this reset is completed succesfully, the
SHUTDOWN_STATUS parameter will be FieldQ
operational and SHUTDOWN_RESET parameter
will return to inactive.
If you do not want to manually reset the device, you
can set the device to Auto-Recovery as described in
4.2.3.3.
If the problem persists, please contact your local
FieldQ representative.
If the initialization can not be started
via the push buttons.
1 Ensure the device is "Out Of Service".
2 Ensure that the buttons are enabled in the transducer block (parameter BUTTONBOARD_ENABLE, index 34).
Remark:
Setting the device to default will always enable the
push buttons as long as the device is in "Out Of
Service" (see §3.4.1).
3 Ensure that the unit is not in Shutdown. See Transducer block parameter SHUTDOWN_STATUS,
index 32. If the device is in Shutdown see 3.4.6
Page 15
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
4
Detailed Configuration
The FieldQ QC34 Module contains the following function blocks:
Block
Index
Resource
1000
Transducer
1100
Discrete Input (DI)
1200
Discrete Input (DI)
1300
Discrete Output (DO)
1400
Analog Input (AI)
1500
PID
1600
4.1.1
See chapter 3, table 3.3, which channel should be
assigned to which function block.
4.1.2
This section contains more detailed information for
configuring the Resource and Transducer Block
parameters to setup the module. Access to each parameter depends upon the host system software. For
information on using the host system to modify block
parameters, see the appropriate appendix and host
system documentation.
- For reading or writing identification parameters
open the resource block.
- For reading or writing configuration parameters
and alerts open the transducer block.
4.1
Resource block
The Resource Block describes the characteristics of
the field bus device such as device name and type,
manufacturer, serial number, amount of free memory,
and free time. There is only one Resource Block in
the module.
The parameters for configuring the Resource Block
are referenced by group within the following sections.
4.1.1
General Resource Block parameters according Foundation Fieldbus™ Protocol
4.1.2
FieldQ™ specific parameters for Instrument Description
4.1.3
FieldQ™ specific parameters which have no
influence on the function of the device.
4.1.4
PlantWeb™ Alerts.
4.1.5
NAMUR NE- 107 Alarms
- For complete details of the parameters listed, see
table 4.1.
- Refer to the applicable host documentation for
procedures to access the referenced parameters.
Page 16
General Resource Block parameters
according Foundation FieldBus™
Protocol
The resource block parameters with index number 1
to 41, are setup according to Foundation Fieldbus™
protocol.
- For their default setting and adjustable range, see
table 4.1.
- For use of the RESTART parameter see chapter 5.
FieldQ™ specific parameters for
Instrument Description
The following parameters are setup specific for the
FieldQ™ with FOUNDATION FieldBus™ communication:
Distributor [DISTRIBUTOR],
Index 93
Private Label Distributor. Identifies the company that
is responsible for the distribution of this Field Device
to customers
Software Revisions [SOFTWARE_REV]:
Index 69
States the software revisions of the controller card
and the FF interface card
Hardware Revision [HARDWARE_REVISION],
Index 68
Hardware revision of that hardware in which the Resource Block resides.
Electronics serial number [ELECTRONICS_SN]:
Index 94
Not used on QC34 Module.
Factory serial number [FACTORY_SN]:
Index 95
Serial number of the QC34 Module.
Field serial number [FIELD_SN]:
Index 96
Serial number for the QC34 Module.which can be set
by the customer.
4.1.3
FieldQ™ specific parameters which
have no influence on the function of
the device.
The following Resource block parameter have no
direct influence on the operation of the device.
Index No Name
71
DEV_STRING
97
DIAG_OPTIONS
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
4.1.4
Alerts
The FieldQ™ QC34 Control module with Foundation
Fieldbus™ communication features diagnostic capabilities combined with PlantWeb™ Alerts.
The FieldQ™ QC34 Control module generates a
recommended action after an internal error has
occurred, timer or counter limits have exceeded or
when the initialization has failed
A full list of Alerts and Recommended Actions, combined with the Alert Default Setting is shown in table
4.3.
4.1.4.1 Alert handling
The Resource Block will act as a coordinator/collector for (PlantWeb™) alerts (see resource block index
numbers 77 to 92).
Although the alerts have default settings (see table
4.3), these levels can be set by the customer to
match their requirements.
There are three levels of alerts available:
1 Failed Alerts
A Failure Alert indicates a failure within a device
that will make the device or some part of the device non-operational.
This implies that the device is in need of repair
and must be fixed immediately.
This alert has the following five parameters:
1FAILED_ENABLE:Enable the indication and
reporting
2FAILED_MASK :Suppress reporting
3FAILED_PRI
:Designates the priority
4FAILED_ACTIVE :Displays which of the conditions within the alert is active.
5FAILED_ALM
:To report the particular failed
condition to the host system.
Level 1
Alert
Priorities
Advisory
Alerts
the device has
detected a condition
within the device that
is not critical
2 Maintenance Alerts
A Maintenance Alert indicates a condition within
a device that, if not attended to in the near future
(the type of alert defines the time period for “Near
Future”) will make the device or some part of the
device non-operational.
This implies that the device is in need of repair
and must be fixed as soon as possible.
This alert has the following five parameters:
1MAINT_ENABLE:Enable the indication and
reporting
2MAINT_MASK :Suppress reporting
3MAINT_PRI
:Designates the priority
4MAINT_ACTIVE :Displays which of the conditions within the alert is active.
5MAINT_ALM
:To report the particular failed
condition to the host system.
3 Advisory Alerts
An Advisory Alert indicates a condition within a
device that is informational in nature. The alert is
used to notify the host that the device has detected a condition within the device that is not
critical, will not cause a failure if left unattended
but should be reported to the host for awareness
and possible action.
This alert has the following five parameters:
1ADVISE_ENABLE:Enable the indication and
reporting
2ADVISE_MASK :Suppress reporting
3ADVISE_PRI
:Designates the priority
4ADVISE_ACTIVE:Displays which of the conditions within the alert is active.
5ADVISE_ALM :To report the particular failed
condition to the host system.
Level 2
Alert
Priorities
Maintenance
Alerts
the device is in need
of repair and must
be fixed as soon as
possible.
Level 3
Alert
Priorities
Failed
Alerts
device is in need of
repair and must be
fixed immediately.
Fig 4.1 Alert levels and priorities
Page 17
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
4.1.4.2 Alert parameter describtion.
1 Alerts - Enabled
These parameters are used to enable the indication and reporting of each corresponding alert.
When a alert is disabled, the device shall not
detect that particular alert, it shall not be indicated
in the (FAILED_ACTIVE, MAINT_ACTIVE or
ADVISE_ACTIVE parameters or be reported via
respectively Failed Alerts, Maintenance Alerts or
Advisory Alerts.
If an alert enable parameter is changed to ‘disabled’ while the alert is active, it shall clear the
alert and re-evaluate the alert. (Writable, only
affects the applicable condition modified. When set
the condition will not be indicated or reported).
2 Alerts - masked:
These parameters will mask any of the failed conditions listed in respectively Failed Alerts, Maintenance Alerts or Advisory Alerts.
Setting a bit to true, will cause the corresponding alert to be indicated in the (FAILED_ACTIVE,
MAINT_ACTIVE or ADVISE_ACTIVE parameters
but it will not be reported to the host via Failed
Alerts, Maintenance Alerts or Advisory Alerts.
If an alert mask is changed while the alert is active, the alert is cleared and all the conditions are
reevaluated. (Writable, only affects the applicable
condition modified. When set the condition will be
indicated however, it will not be reported).
3 Alerts - Priority:
Designates the priority of the Failed, Maintenance
or Advisory Alerts. The default is 2 and the recommended value is between 10 and 15. (Writable,
changes the priority of the applicable alert).
4 Alerts - Active:
These parameters displays which of the conditions within the Failed, Maintenance or Advisory
Alerts is active. When a device detects a condition
has become active, it shall set the corresponding
bit in the Failed, Maintenance or Advisory Alerts
- Active parameters. If it is not suppressed, it will
be reported using the associated alert parameter.
(Read Only)
5 Alert Alarm:
These parameter are used to report the particular failed condition to the host. (Read Only). For
parameter structure see table 4.2.
Page 18
4.1.5
NAMUR NE- 107 Alarms
This section describes the parameter interaction to
implement a FieldQ™ QC34 Control module to the
NAMUR NE-107 requirements as a parameter group
in the Resource Block. There are four alarm categories defined as per the NE-107 specification, Failed,
Off Specification, Maintenance, and Check function.
Maintenance
Although the output signal is valid,
the wear reserve is nearly exhausted or a functions will soon be
restricted due to operational conditions e.g. build-up of deposits
Off
Specification
Off-spec means that the device is
operating outside its specified range
or an internal diagnostic indicates
deviations from measured or set
values due to internal problems in
the device or process characteristics (e.g. bubble formation in flow
metering or valve sticking).
Check Function
Output signal temporarily invalid
(e.g. frozen) due to on-going work
on the device.
Failed
Output signal invalid due to malfunction in the field device or its
peripherals.
Each of these categories share 32 conditions that can
be defined by the device manufacturer.
Each condition may be mapped or not mapped for
each category. If a condition is mapped then it is
indicated in the* ACTIVE parameter. If the condition in the * ACTIVE parameter is not masked by the
corresponding bit in the *_MASK parameter then the
condition will be queued for broadcast using the corresponding *ALM parameter at the associated priority
indicated by *PRI parameter. The 4 categories are
defined below.
The conditions are not expected to identify explicitly
the root cause of the condition, but rather to identify it
in terms of:
• Replace the device
• Replace a part of the device
• Correct a configuration problem
• Fix something outside of the device
The above list is all that the operator needs to know
to restore his process functionality and if there are
more than 31 device conditions they should be
grouped by definition into these bits.
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Then using the EXTENDED parameters in the resource block, more detailed information can be made
available about the conditions for a maintenance
person to get to the root of the problem.
The Common Practice Parameters named FD_EXTENDED_ACTIVE_n which are similar to the
BLOCK_ERR_DESC_n parameter in function, are
used to describe what lower level conditions are
causing the condition in the FD_FAIL_ACTIVE,
FD_MAINT_ACTIVE, FD_OFFSPEC_ACTIVE, or FD
CHECKACTIVE to be true.
ALARM
BROADCAST
RECORD
FD_ FAIL_ ALM
FD_ OFFSPEC_ ALM
ALARM
BROADCAST
ENABLE
FD_ FAIL_ MASK
FD_ OFFSPEC_ MASK
ALARM
INDICATION
( POLLING)
FD_ FAIL_ ACTIVE
FD_ OFFSPEC_ ACTIVE
ALARM
DETECTION
ENABLE
FD_FAIL_MAP
Additional Common Practice Parameters named
FD_EXTENDED_MAP_n may be used to map
multiple sensors or conditions into a single condition
bit, Both FD_EXTENDED_ACTIVE_n and FD_EXTENDED_MAP_n parameters if present must follow
the FD_RECOMMEN_ACT parameter.
Any number of bits in the extended parameters may
be or’ed together to trigger a single condition bit in
the standard Fail, Maint, OffSpec, and Check 32
bits, There is also no restriction on which bits out of
the standard 32 that may be used for the Fail, Maint,
OffSpec, or Check categories.
FD_ MAINT_ ALM
FD_ CHECK_ ALM
DS87
FD_ FAIL_PRI
FD_ OFFSPEC_PRI
FD_OFFSPEC_MAP
Manufacturer
FD_ MAINT_PRI
FD_ CHECK_PRI
FD_ MAINT_ MASK
FD_ CHECK_ MASK
FD_ MAINT_ ACTIVE
FD_ CHECK_ ACTIVE
FD_MAINT_MAP
FD_CHECK_MAP
Bitstring
32 bits
Bitstring
32 bits
Bitstring
32 bits
Specific Conditions
3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
Increasing Priority at device level
32 bit Bitstring
C
H
E
C
K
3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
Optional FD_EXTENDED_ACTIVE_n
and FD_EXTENDED_MAP_n
Fig 4.2 Field Diagnostics Alarm Schematic
Page 19
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.1 FieldQ™ Resource Block
Index
No.
1
Name
Description
Valid Range
Initial Value
Permission
ST_REV
Static data revision. Updated when static data is changed
0 to 65535
0
Read only
2
TAG_DESC
spaces
Read / Write
3
STRATEGY
7 bit ASCII
0
Read / Write
4
ALERT_KEY
Unique description for the resource block within a system, writable by
the host system operator.
Used by host system administrator to group blocks foe easy
identification of location.
Plant unit ID, for host system operator for sorting alarms
1 to 255
0
Read / Write
5
MODE_BLK
The target, actual and permitted modes for the block
OOS, AUTO
TARGET
OOS
Read / Write
ACTUAL
N/A
Read Only
PERMITTED
OOS, AUTO
Read / Write
NORMAL
AUTO
Read / Write
0 to F
N/A
Read Only
1 to 6
5
Read only
Not applicable
Not applicable
Not applicable
spaces
Read only
6
BLOCK_ERR
7
RS_STATE
8
TEST_RW
Error status associated with the hardware or software of the resource
block
0: Other
1: Block config error (not used)
2: Link configuration error
3: Simulate Active: Based on switch
4: Local override (not used)
5: Device Fail safe set
6: Device needs Maintenance Soon
7: Input failure (not used)
8: Output failure (not used)
9: Memory Failure (FF card)
10: Lost static data (FF card)
11:Lost NV data (FF card)
12: Readback check failed (not used)
13: Device needs Maintenance Now
14: Power-up (not used)
15: Out-of-Service
State of the resource
1: Start restart
2: Initialization, actual mode = IMAN
3: Online linking
4: Online, actual mode = Auto
5: Standby
6: Failure
Read write test parameter for interoperability testing
9
DD_RESOURCE
Tag ID string identifying DD resource for info only
10
MANUFAC_ID
0x564144
0x564144
Read only
11
DEV_TYPE
0xD3A0
0xD3A0
Read only
12
DEV_REV
Manufacturing identification number, used by an interface device to
locate DD file for resurce. Should show up as Valve automation
Manufacturers model number 0xD3A0 = FieldQ – Pneumatic Valve
Actuator
Device Revision; Used to locate DD file set to: 3
3
3
Read only
13
DD_REV
Minimum compatible DD revision number associated with this device
1
1
Read only
14
GRANT_DENY
Access control to host computer.
GRANT
DENY
15
HARD_TYPES
The types of hardware available as channel numbers on this resource
16
RESTART
Shows current status and allows a manual restart to be initiated,
implemented as method with warnings!
1 Run - Normal operation
2 Resource - Restart FF resource keep settings.
3 Defaults - Restart FF resource with default.
4 Processor - Restart FF Resource.
5 Actuator defaults - Restart control module with factory settings
6 Actuator processor - Restart control module, keep settings.
Valid settings: 0x00
0 Program,
1 Tune,
2 Alarm,
3 Local
0 Scalar Input,
1 Scalar output,
2 Discrete
Input,
3 Discrete
Output
1 to 6
1
Page 20
Read / Write
Read only
Read only
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.1 FieldQ™ Resource Block (Continued)
Index Name
Description
No.
17
FEATURES
Shows the supported resource block options
0: Unicode strings
1: Reports
2: Faultstate
3: Soft W Lock
4: Out readback
5. Multi-bit Alarm (Bit-Alarm) Support
6. Restart/Relink after FB Action
18
FEATURE_SEL
Shows the selected “Features” from the availible options listed in the
above “FEATURES” parameter.
0: Unicode strings N/A
1: Reports
2: Faultstate
3: Soft W Lock
4: Out readback
19
CYCLE_TYPE
Indicates available function block execution routines
0: Scheduled
1: Completion of Block Execution N/A
2 : Manufacturer specific N/A
20
CYCLE_SEL
Indicates selected function block execution routines
0: Scheduled
1: Completion of Block Execution N/A
2 : Manufacturer specific N/A
21
MIN_CYCLE_T
Indicates shortest cycle of which the resource is capable
22
MEMORY_SIZE
Available memory in empty resource (Mcore).
23
NV_CYCLE_T
Minimum time interval required to write internal parameters to nonvolatile memory. 0 means only external writes
24
FREE_SPACE
Memory available for further configuration in FF card
25
FREE_TIME
Block processing time available to additional blocks
26
SHED_RCAS
Time duration at which to give up on computer writes to function block
RCas locations.
27
SHED_ROUT
Time duration at which to give up on computer writes to function block
ROut locations
28
FAULT_STATE
Forces output function blocks to the FAULT_STATE condition if active.
1: clear, 2: active
29
SET_FSTATE
Writing a set to this parameter will force FAULT_STATE to be manually
initiated
1: off
2: set
30
CLR_FSTATE
Writing a set to this parameter will force FAULT_STATE to be cleared
1: off
2: clear
31
32
MAX_NOTIFY
LIM_NOTIFY
33
34
CONFIRM_TIME
WRITE_LOCK
35
UPDATE_EVT
Absolute Maximum number of unconfirmed notify messages possible.
Selected Maximum number of unconfirmed alert notify messages
possible
Wait time before re-try. 0 = no retry
If set no writes accept to clear write lock will be allowed
1: not locked
2: locked
Alert generated by any change to the static data
UNACKNOWLEDGED: 0 undefined, 1 acknowledged,
2 unacknowledged
UPDATE STATE: 0 undefined, 1 Update reported,
2 Update not reported
TIME STAMP
STATIC REVISION
RELATIVE INDEX
Valid Range
Initial Value
Permission
1 to 6
See
Description
Read only
1 to 4
0x1E (ALL)
Read / Write
0 to 2
0
Read only
0 to 2
0
Read only
Set by FCS
Set by FCS
>=0
3200
0
Read only
Read only
Read only
0 to 100%
0 to 100%
>=0
0
0
640000
Read only
Read only
Read only
>=0
640000
Read only
1 to 2
1
Read only
1 to 2
1
1 to 2
5
0 to MAX_
NOTIFY
>=0
1 to 2
Read / Write,
access
controled by
operator
1
Read / Write,
access
controled by
operator
5
Read only
MAX_NOTIFY Read / Write
640000
1
Read / Write
Read / Write,
access
controled by
operator
0 to 2
0
Read / Write
0 to 2
0
Read only
time
N/A
N/A
0:00:00
0
0
Read only
Read only
Read only
Page 21
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.1 FieldQ™ Resource Block (Continued)
Index Name
Description
No.
36
BLOCK_ALM
The block alarm is used for all configurations, hardware connection
failures and system problems in the block. The cause of the alert is
entered in the sub-code.
UNACKNOWLEDGED: 0 undefined, 1 acknowledged, 2
unacknowledged
ALARM_STATE 0:Undefined 0 1:Clear- Reported 2:Clear- Not reported
3:Active- Reported 4:Active- Not reported
TIME_STAMP
SUB_CODE = BLOCK_ERR
VALUE- A value can be added by the customer for configuring alarms
37
ALARM_SUM
Status and states of the alarms associated with the block
38
ACK_OPTION
39
40
WRITE_PRI
WRITE_ALM
41
ITK_VER
42
FD_VER
43
44
45
46
47
FD_FAIL_ACTIVE
FD_OFFSPEC_ACTIVE
FD_MAINT_ACTIVE
FD_CHECK_ACTIVE
FD_FAIL_MAP
48
FD_OFFSPEC_MAP
49
FD_MAINT_MAP
50
51
52
53
54
FD_CHECK_MAP
FD_FAIL_MASK
FD_OFFSPEC_MASK
FD_MAINT_MASK
FD_CHECK_MASK
55
56
57
58
FD_FAIL_ALM
FD_OFFSPEC_ALM
FD_MAINT_ALM
FD_CHECK_ALM
Page 22
CURRENT- current status
UNACKNOWLEDGED - states unacknowledged alarms
UNREPORTED - states unreported alarms
DISABLED - states disabled alarms
When enabled, the device automatically acknowledges alerts sent to
the host
1 : Auto Acknowledge Disabled
2 : Auto Acknowledge Enabled
Priority of the alarm generated by clearing the Write Lock
Generated if the writelock is cleared
UNACKNOWLEDGED: 0 undefined, 1 acknowledged, 2
unacknowledged
ALARM_STATE 0:Undefined 0 1:Clear- Reported 2:Clear- Not reported
3:Active- Reported 4:Active- Not reported
TIME_STAMP
SUB_CODE - indicates what alarm
VALUE- A value can be added by the customer for configuring alarms
Indicates the major revision number of the interoperability test case
used in certifying this device as interoperable
NAMUR NE107 Alarm parameters
A parameter equal to the value of the major version of the Field
Diagnostics specification that this device was designed to.
This parameter reflects the error conditions that are being detected as
active as selected for this category. It is a bit string, so that multiple
conditions may be shown.
This parameter maps conditions to be detected as active for this alarm
category. Thus the same condition may be active in all, some, or none
of the 4 alarm categories.
This parameter allows the user to suppress any single or multiple
conditions that are active, in this category, from being broadcast to the
host through the alarm parameter. A bit equal to ‘1’ will mask i.e. inhibit
the broadcast of a condition, and a bit equal to ‘0’ will unmask i.e. allow
broadcast of a condition.
This parameter is used primarily to broadcast a change in the
associated active conditions, which are not masked, for this alarm
category to a Host System.
Valid Range
Initial Value
Permission
0 to 2
Read / Write
0 to 4
Read only
time
Read only
Read only
Read only
Read only
0: Discrete
0
alarm set when
write lock is
turned off 7:
Block alarm
1 to 2
1
Read / Write
0 to 15
0
Read / Write
0 to 2
0
Read / Write
0 to 4
0
Read only
time
set by FF
0
0
0
6
Read only
Read only
Read only
Read only
1
1
Read only
Read only
Read only
Read only
Read only
ALARM
NV Memory
Failure,
Electronics
Failure,
Bad
Temperature
Sensor,
Software Error,
Travel
Deviation,
Shutdown
is Set,
Buttonboard
Failure,
Internal IO
Failure
Instrument
ALARM
Temperature
Exceeded
Bad Position
ALARM
Sensor
Check
ALARM
ALARM
ALARM
ALARM
ALARM
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.1 FieldQ™ Resource Block (Continued)
Index Name
Description
No.
59
FD_FAIL_PRI
This parameter allows the user to specify the priority of this alarm
60
FD_OFFSPEC_PRI
category.
61
FD_MAINT_PRI
62
FD_CHECK_PRI
63
FD_SIMULATE
This parameter allows the conditions to be manually supplied when
simulation is enabled. When simulation is disabled both the diagnostic
simulate value and the diagnostic value track the actual conditions. The
simulation is enabled/disabled through a method and while simulation is
enabled the recommended action will show that simulation is active.
64
FD_RECOMMEN_ACT
This parameter is a device enumerated summarization of the most
severe condition or conditions detected.
The DD help should describe by enumerated action, what should
be done to alleviate the condition or conditions. 0 is defined as Not
Initialized, 1 is defined as No Action Required, all others defined by
manuf.
65
FD_EXTENDED_ACTIVE
An optional parameter or parameters to allow the user finer detail on
conditions causing an active condition in
the FD_*_ACTIVE parameters.
66
FD_EXTENDED_MAP
An optional parameter or parameters to allow the user finer control
on enabling conditions contributing to the conditions in FD_*_ACTIVE
parameters.
67
COMPATIBILITY_REV
Compatibility Revision: This is used for device replacement and
indicates whether a previous rev can be replaced by the current device.
This is a new Foundation feature so previous revisions of the FieldQ will
not comply with the new device replacement rules.
68
HARDWARE_REVISION
Revision of hardware
69
SOFTWARE_REV
Software revisions of FF card
Rev: xx-yy-zz (xx=major, yy= middle, zz=minor) Rev. date: dd-monthyyyy
70
PD_TAG
This parameter is the physical device tag of the field device.
71
DEV_STRING
72
DEV_OPTIONS
73
OUTPUT_BOARD_SN
74
FINAL_ASSY_NUM
75
DOWNLOAD_MODE
76
HEALTH_INDEX
Valid Range
Initial Value
Permission
0 to 15
0 to 15
0 to 15
0 to 15
0
0
0
0
disabled
ALARM
ALARM
ALARM
ALARM
Read / Write
0
ALARM
Read only
3
Read only
0 to 255
N/A
Read only
N/A
N/A
Read only
Read only
Resource Block. Used to load new licensing into the device. The value
can be written but will always be read back with a value of 0
This parameter allows the operator access to the base record. When
the base record option is enabled, operator can write/read parameters
to/from the sensor board that are not available via the FF parameter list.
A method is used to enable/disable the parameter and a direct write is
not necessary.
Output Board Serial number is a unigue 4 byte number of the FF card
for each device.
Final Assembly Number is a 4 byte static value that can be set by the
operator
Indicates whether the device is in run or download mode
Parameter representing the overall health of the device.
100 being perfect and 1 being non-functioning.
no alerts -> 100
ADVISE_ACTIVE -> -10 per advice
MAINT_ACTIVE -> - 40 per advise
FAIL_ACTIVE -> = 10 (10 also lowest value)
Read / Write
0
Read / Write
Read only
0
Read / Write
Read only
10 to 100
100
Read only
Page 23
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.1 FieldQ™ Resource Block (Continued)
Index
No.
77
PlantWeb Alert parameters
Name
Description
FAILED_PRI
Designates the alarming priority of the FAILED_ALM. Handling defined
by FF.
0: All FAILED alerts disabled
Valid Range
Initial Value
Permission
0 to 15
2
Read / Write
0
Read only
1: All failed alerts supressed
2: Higher process failed alerts
78
RECOMMENDED_ACTION
Enumerated list of recommended actions of the device, displayed with a N/A
device alert (can be multiple, see table below)
see table
79
FAILED_ALM
Alarm indicating a failure within a device which makes the device nonoperational.
UNACKNOWLEDGED:
Read only
0: Undefined, 1: Acknowledged, 2: Unacknowledged
ALARM_STATE
Read only
0:Undefined 0
1:Clear- Reported
2:Clear- Not reported
3:Active- Reported
4:Active- Not reported
TIME_STAMP
Read only
SUBCODE value should match alert as stated under FAILED_ENABLE
Read only
VALUE
Read only
80
MAINT_ALM
See index 79 FAILED_ALM
81
ADVISE_ALM
See index 79 FAILED_ALM
82
FAILED_ENABLE
see alert table
83
FAILED_MASK
see alert table
84
FAILED_ACTIVE
see alert table
85
MAINT_PRI
See index 77 FAILED_PRI
0 to 15
86
MAINT_ENABLE
see alert table
N/A
87
MAINT_MASK
see alert table
88
MAINT_ACTIVE
see alert table
89
ADVISE_PRI
See index 77 FAILED_PRI
0 to 15
90
ADVISE_ENABLE
see alert table
N/A
91
ADVISE_MASK
see alert table
92
ADVISE_ACTIVE
see alert table
93
DISTRIBUTOR
94
ELECTRONICS_SN
Private Label Distributor. Identifies the company that is responsible for
the distribution of this Field Device to customers
Set by factory
95
FACTORY_SN
Set by factory
96
FIELD_SN
Set by customer
97
DIAG_OPTIONS
Currently not used
98
CONTROL_CARD_SW_REV CTRL_CRD_SWARE_REV interpret MSB.LSB
Page 24
N/A
N/A
Read only
2
Read / Write
Read only
2
Read / Write
Read / write
Read / write
Read only
0x564144
Read only
0 to 255
N/A
Read only
N/A
N/A
Read only
N/A
All spaces
Read / Write
0 to 255
N/A
Read only
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
4.2
Transducer block
The Transducer Block manages data that moves
between a function block and the device input/output (I/O) such as sensors and position switches that
provide process data for automated process control.
Transducer blocks control access to I/O devices
through a device independent interface and manufacturer specific parameters defined for use by function
blocks. Transducer blocks also perform functions,
such as calibration and linearization, on I/O data to
convert it to a device independent representation.
The transducer block to function blocks interface is
defined as one or more implementation independent
channels.
The parameters for configuring the Transducer Block
are referenced by group within the following sections.
- For complete details of the parameters listed, see
table 4.1.
- Refer to the applicable host documentation for
procedures to access the referenced parameters.
4.2.3
Device configuration.
The following five parameter are available to configure the QC34 module for normal operation:
Index No
Name
28
AUTO_INITIALIZATION
29
CFG_SWITCH_POINTS
32
SHUTDOWN-CFG
33
ZERO_PWR_COND
34
BUTTONBOARD_ENABLE
4.2.3.1 AUTO_INITIALIZATION
Initialization sets the end positions for the position
feedback of the actuator. The initialization procedures
are decribed in detail in chaper 3. For the default setting and adjustable range, see table 4.2. index 28.
4.2.1 General Transducer Block parameters according FOUNDATION FieldBus™ Protocol
4.2.2 Device position status parameters
4.2.3 Device configuration (Switch points and Shutdown).
4.2.4 Diagnostic configuration (Timers, Counters).
4.2.1
General Transducer Block
parameters according Foundation
FieldBus™ Protocol
The Transducer Blocks parameters with index
number 1 to 24, are setup according the Foundation
Fieldbus™ protocol. For their default setting and
adjustable range, see table 4.2.
4.2.2
Device position status parameters
There are 3 parameter which give information on the
position status of the device.
Index No
Name
25
DISCRETE_POSITION
26
OPEN_STATE
27
CLOSE_STATE
For their default setting and adjustable range, see
table 4.2.
Page 25
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
4.2.3.2 CFG_SWITCH_POINTS
The FieldQ™ QC34 Control module will be shipped
with the default feedback characteristic, as per figure
4.3. This feedback characteristic is operational after
initialization (see chapter 3) and is suitable for most
applications.
Default setting
after initialization
End stop
offsets
10˚max
Adjustable
range
End
position
30˚
5˚
30˚
10˚max
5˚
End
position
Fig. 4.3 Feedback characteristic
If the default configuration is not suficient for your application, the switch points can be configured.
For the QC34 Module, there are three topics concerning the configuration of the switch points.
1 Mechanical limit stops.
Normally the mechanical limit stops limit the stroke
of the actuator. (To adjust the mechanical limit
stops see DOC.IOM.Q.1 chapter 3).
If the mechanical limit stop setting is changed, or
the valve does not reach the fully open or closed
positions (due to wear in the valve), the Open and
Closed end positions have to be re-configured to
assure position feedback.
Page 26
2 "Open" and "Closed" end positions.
There are two procedures to re-configure the end
positions:
1 If it is safe to cycle the actuator, perform the initialization procedure (see §3.2).
2 If it is not safe to cycle the actuator, perform the
following re-assignment procedure:
1 Go to Transducer block.
2 In case the "Open" position needs an update:
Set sub parameter OPEN_END_POSITION of
parameter CFG_SWITCH_POINTS to:
"set to current position".
3 In case the "Closed" position needs an update:
Set sub parameter CLOSED_END_POSITION
of parameter CFG_SWITCH_POINTS to:
"set to current position".
3 "Open" and "Closed" stop offset.
The "Open" or "Closed" offset value is the number
of degrees before the end of stroke within which
the switches will be activated or deactivated. Default values for both positions are (see figure 4.1):
- Default offset 10° before end of stroke.
- Adjustable range 5° to 30° before end of
stroke
Sub parameters OPEN_STOP_OFFSET and
CLOSED_STOP_OFFSET can be used to change
the end stop offsets and can be set per ° (degree)
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
4.2.3.3SHUTDOWN-CFG
Shutdown configuration controls the behaviour of the
FieldQ™ actuator in case of an internal communications failure in the QC34 module. This is independent
of the FF communication on the bus line.
This set of parameters can overrule the Failure
modes of the basic actuator, as described in the
FieldQ™ IOM manual, chapter 2.2 (DOC.IOM.Q1).
1 General working of Shutdown configuration.
Shutdown configuration can work in three configurations, as set by the SHUTDOWN_ENABLE parameter:
- enable, auto recovery
- enable, manual recovery
- disable.
Enable : After an internal failure, the setting of parameter SHUTDOWN_ACTION will be executed.
Auto Recovery : When the internal failure is solved,
the actuator will automatically go to its current setpoint position.
Manual Recovery : When the internal failure is
solved, the actuator shutdown status must be manually reset.
Normally the SHUTDOWN_RESET parameter is
inactive. For reseting the shutdown status this parameter must be set to Reset. When this reset is completed succesfully, the SHUTDOWN_STATUS parameter
will be FieldQ operational and SHUTDOWN_RESET
parameter will return to inactive.
Disable : Shutdown functionality is not operational,
the actuator will stay in its last position after an internal failure.
Parameter SHUTDOWN_DELAY_TIME defines a
delay time (up to 4 minutes and 15 seconds) between
the time the internal failure is detected by transducer
block parameter XD_ERROR (I/O Failure) and the
time that the unit will go in "Shutdown".
The sequence of events for 2 shutdown configurations is shown in figures 4.4 and 4.5.
2 Factory default Shutdown configuration setting
(see figure 4.5):
SHUTD-ENABLE
:Enable, Manual Recovery
SHUTDOWN_ACTION
:Close
SHUTDOWN_DELAY_TIME :5 seconds
I/O Failure
XD_ERROR = “I/O Failure”
Delay time as set in
SHUTDOWN_STATUS
SHUTDOWN_DELAY_TIME
Changes to
FieldQ shutdown
SHUTD-ENABLE =
SHUTDOWN_ACTION =
- open
- close
- hold
‘Enable, Auto recovery'
After internal communications
are re-estabished, the actuator/valve unit will automatically
go to its current setpoint
position.
Fig 4.4 Shutdown configuration, Enable,
Auto recovery
I/O Failure
XD_ERROR = “I/O Failure”
SHUTDOWN_STATUS
Changes to
FieldQ shutdown
Delay time as set in
SHUTDOWN_DELAY_TIME
SHUTD-ENABLE =
‘Enable, Manual recover'
SHUTDOWN_ACTION =
- open
- close
- hold
SHUTDOWN_RESET
After internal communications
are re-established, the shutdown status must be manually
reset using the SHUTDOWN_
RESET parameter.
Fig. 4.5 Shutdown configuration, Enable,
Manual recovery
Default shutdown configuration
* Means that 4 seconds after an internal failure is detected,
DOUBLE ACTING AND SPRING RETURN (Single acting)
actuators will go to the closed position, when pressure is
available at the actuator,
and
* After the internal communications are re-established, the
shutdown status must be reset.
Important
* If feedback is reversed, the default position in "SHUTDOWN_ACTION" is not automatically reversed
Page 27
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
4.2.3.4 ZERO_PWR_COND
This parameter helps identifying whether the device
setup matches the actual mechanical configuration of
the actuator ;
- Fail-to-Close or Fail-to-Open for single acting actuators.
This parameter indicates the position where the
actuator/valve unit will move to, when no power is
present (air pressure should be present for DA).
- The value is set during initialization and position
re-assignment and is valid for valve applications
which close after a clockwise (CW) rotation and the
operation of the valve may be Fail-to-Close or Failto-Open.
- For applications which close after a counter clock
wise (CCW) rotation, the indication will be reversed
after initialization. This can be corrected by reassigning the end positions as decribed in §3.4.3.
4.2.3.5 BUTTONBOARD_ENABLE
The button bord can be set to:
- Enabled when in OOS (factory default)
- Never active
4.2.4
Diagnostic configuration
This section describes the counter and timer parameters. The description how to set alerts and generate
the recommended actions can be found in §4.1.4.
4.2.4.1 Counters
Four counter parameters are available for counting
the cycles of the :
1 Control module
2 Actuator 3 Pneumatic module
4 Valve.
The Control (function) Module counter is the master
counter and is read only. The other three counters
can each be reset independently when required (e.g.
replacement).
These counter parameters have :
- a sub parameter which records the cycles.
- a sub parameter to set a limit value.
When one of the set limits is exceeded an alert and a
recommended action message will be generated as
per table 4.3 and as per alert setting ( see §4.2.5).
For the default setting and adjustable range, see
table 4.2. index 36, 37, 38 and 39.
Page 28
4.2.4.2 Timers
There are 3 timers available in this device:
1 Time in position (TIME_IN_POSITION)
- Records the time since the last movement.
It is reset to zero when the power is switched off.
- In sub parameter TIME_IN_POSITION_HI_LIM, a
limit can be set.
2 Open travel time (OPEN_TRAVEL_TIME)
- Indicates the time between:
When pilot valve position is changed and when the
Open trip position reached.
- In parameters OPEN_TRAVEL_TIME_HI_LIM and
OPEN_TRAVEL_TIME_LO_LIM, high en low limits
can be set.
- Parameter OPEN_TRAVEL_TIME_AVG calculates
the average stroke time of the last 30 strokes.
- In parameters OPEN_TRAVEL_AVG_HI_LIM and
OPEN_TRAVEL_AVG_LO_LIM, high en low limits
can be set.
3 Close travel time (CLOSE_TRAVEL_TIME)
- Indicates the time between:
When pilot valve position is changed and when the
Closed trip position reached.
- In sub parameter CLOSE_TRAVEL_TIME_HI_LIM
and CLOSE_TRAVEL_TIME_LO_LIM, high en low
limits can be set.
- Parameter CLOSE_TRAVEL_TIME_AVG calculates the average stroke time of the last 30 strokes.
- In parameters CLOSE_TRAVEL_AVG_HI_LIM and
CLOSE_TRAVEL_AVG_LO_LIM, high en low limits
can be set.
When the limits of the above timers are exceeded,
and the alerts are enabled, alerts and recommended
action messages will be generated as per table 4.3
and as per alert setting (see §4.1.4).
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Page 29
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.2 FieldQ™ Transducer Block
"Index Name
No."
Description
1
ST_REV
Static data revision. Updated when static data is changed
2
TAG_DESC
3
STRATEGY
4
ALERT_KEY
Unique description for the transducer block within a system, writable by
the host system operator.
Used by host system administrator to group blocks for easy
7 bit ASCII
identification of location.
Plant unit ID, for host system operator for sorting alarms
1 to 255
5
MODE_BLK
The target, actual and permitted modes for the block
ACTUAL
BLOCK_ERR
7
UPDATE_EVT
8
BLOCK_ALM
Initial Value
Permission
0 to 65535
0
Read only
spaces
Read / write
0
Read / write
0
Read / write
OOS
Read / write
General Transducer Block parameters
TARGET
6
Valid Range
7: OOS, 3:
AUTO
N/A
Read Only
PERMITTED
ALL
Read / write
NORMAL
AUTO
Read / write
N/A
Read Only
Error status associated with the hardware or software of the resource
block (enumeration)
0: Other
1: Block config error (not used)
2: Link configuration error
3: Simulate Active: Based on switch
4: Local override (not used)
5: Device Fail safe set
6: Device needs Maintenance Soon
7: Input failure (not used)
8: Output failure (not used)
9: Memory Failure (FF card)
10: Lost static data (FF card)
11:Lost NV data (FF card)
12: Readback check failed (not used)
13: Device needs Maintenance Now
14: Power-up (not used)
15: Out-of-Service
Alert generated by a change to static data.
UNACKNOWLEDGED:
0 undefined, 1 acknowledged, 2 unacknowledged
ALARM_STATE
0:Undefined 0
1:Clear- Reported
2:Clear- Not reported
3:Active- Reported
4:Active- Not reported
TIME_STAMP
SUB_CODE
RELATIVE INDEX
The block alarm is used for all configurations, hardware connection
failures and system problems in the block. The cause of the alert is
entered in the sub-code.
UNACKNOWLEDGED:
0 to 15
Read only
0 to 2
Read / Write
0 to 4
Read only
time
Read only
0 undefined, 1 acknowledged, 2 unacknowledged
ALARM_STATE
0:Undefined 0
1:Clear- Reported
2:Clear- Not reported
3:Active- Reported
4:Active- Not reported
TIME_STAMP
SUB_CODE The alarm is stated here(only Device fail -safe set and
OOS)
VALUE- A value can be added by the customer for configuring alarms
Page 30
Read only
Read only
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.2 FieldQ™ Transducer Block (continued)
"Index Name
No."
Description
Valid Range
Initial Value
Permission
General Transducer Block parameters (continued)
9
TRANSDUCER_DIRECTORY Array containing the transducer definitions (empty)
0,0
0,0
Read only
10
TRANSDUCER_TYPE
Identifies the type of Transducer Block.
XD_ERROR
Extensions to Block Error indicated by the “Other” bit 0 being set
(enumaration)
16: unspecified error
17: General error (not used)
18: Calibration error
19: configuration error (not used)
20: Electronics failure
21: Mechanical failure (not used)
22: I/O Failure
23: Data Integrety error (not used)
24: Software error
25: Algorithm error (not used)
Standard
discrete
positioner
0 = no error
Read only
11
Standard
discrete
positioner
0 = no error
12
COLLECTION_DIRECTORY A directory that specifies the number, starting indices, and DD Item IDs
of the data collections in each transducer within a Transducer Block.
FINAL_VALUE_D
States the requested valve position and status written by a discrete
function block (set point)
STATUS
0
0
Read only
2
Read only
13
14
ACT_FAIL_ACTION
15
ACT_MAN_ID
16
ACT_MODEL_NUM
17
ACT_SN
18
VALVE_MAN_ID
19
VALVE_MODEL_NUM
20
VALVE_SN
21
VALVE_TYPE
22
XD_CAL_LOC
23
XD_CAL_DATE
24
XD_CAL_WHO
Read only
Read only
VALUE requested position 0: close, 1: open
0 to 1
0
Read only
Defined by Foundation Fieldbus, has no effect on our device!
0: undefined (DA), 1 Self-closing(SA), 2 Self opening(SA)
Actuator manufacturer ID in Foundation Mfg id units.
Is: Emerson Process Management Valve Automation Division
Actuator model number. Depends where it is mounted.
Can be set by customer.
Seriel number of actuator.
Can be set by customer.
Valve manufacturer ID in Foundation Mfg id units.
Can be set by customer.
Indicates available function block execution routines
0 to 3
0
Read / Write
0x564144
0x564144
Read only
all spaces
Read / Write
all spaces
Read / Write
0
Read / Write
all spaces
Read / Write
all spaces
Read / Write
2
Read / Write
all spaces
Read / Write
Seriel number of valve.
Can be set by customer.
Type of valve. Can be set by customer, but it is not used by the device.
0: undefined, 1: Sliding stem, 2: Rotary
The location where device was last initialized.
Can be set by customer,
The date the unit was calibrated/initialized.
Can be set by customer.
Person who did the calibration.
Can be set by customer.
0 to 2
Read / Write
all spaces
Read / Write
Page 31
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.2 FieldQ™ Transducer Block (continued)
Index
No.
Name
Description
25
DISCRETE_POSITION
Single signal indicating the current discrete position
Valid Range
Initial Value
0 to 3
0
true/false
FALSE
Device position status parameters
STATUS
26
27
Permission
OPEN_STATE
CLOSE_STATE
Read only
VALUE
0 = closed,
1 = open,
2 = Closing (based on not being 0 or 1 and the current position request)
3 = opening (based on not being 0 or 1 and the current position
request)
Discrete position feedback
0: false, 1: true
STATUS (bad when loose IO board comms block err, uncertain sensor
error)
VALUE
0 false, 1: true
Discrete position feedback
Read only
Read only
0 to 1
0
true/false
FALSE
Read only
0: false, 1: true
STATUS (bad when loose IO board comms - block err, uncertain when
sensor bad)
VALUE
Read only
0 to 1
0
Read only
0 false, 1: true
Device configuration
28
29
AUTO_INITIALIZATION
Controls the procedure for finding the end positions
0 to 2
CFG_SWITCH_POINTS
AUTO_INIT_COMMAND 0: no action,
1: start auto init
2: start Zero point adjustment,
3: stop auto init
Status of the initialization procedure
- Undetermined, bad repeatability -> increase limit stop offset
- Running,
- Aborted, -> stopped, by user.
- Undetermined, difference between open and close too small
- Time Out, -> too long before end-positions are found -> check airpressure and actuator sizing
- Range Error -> Difference between open and closed end position is
too small. -> check air-pressure, check proper valve rotation.
- Successful
- No Valid Data. -> value after default (not initialized)
Set trippoints from endposition
OPEN_END_POSITION use current position as open end position
0: normal, 1: set
CLOSED_END_POSITION use current position as close end position
0: normal, 1: set
OPEN_STOP_OFFSET - distance to endposition
(in ° before end position) Can be set per ° (degree)
CLOSE_STOP_OFFSET - distance to endposition
(in ° before end position) Can be set per ° (degree)
For identification blink status led (5 min.)
0: finished
1:start
Indicates the internal temperature of the instrument
STATUS
VALUE Indicates the internal temperature of the device in degrees
Celcius
Configures what actions to take after internal communications are lost.
SHUTDOWN_ENABLE - 0: enable auto recovery,
1: enable manual recovery, 2: disable
SHUTDOWN_ACTION 0: close, 1: open, 2: hold
SHUTDOWN_DELAY_TIME - Time (in sec.) before action will be taken
after event has occurred
SHUTDOWN_RESET - Normally 0, unless SHUTDOWN_STATUS is 1
and SHUTDOWN_ENABLE set to manual recovery. Manual recovery
will then require this bit to be set to 0
SHUTDOWN_STATUS - Set to 1 when the system is shutdown, else 0
30
FLASH_LED
31
INSTRUMENT_TEMP
32
SHUTDOWN_CFG
Page 32
Read / Write
0
Read only
0 to 1
0
Read / Write
0 to 1
0
Read / Write
5° to 30°
10°
Read / Write
5° to 30°
10°
Read / Write
0 to 1
N/A
Read / Write
N/A
N/A
Read only
0 to 2
1
Read / Write
0 to 2
0
Read / Write
1 to 255
4
Read / Write
0 to 1
0
Read / Write
0 to 1
N/A
Read only
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.2 FieldQ™ Transducer Block (continued)
Index
No.
Name
33
ZERO_POWER_CONDITION The position where the valve will move to when nopower is present
(airpressure should be present for DA)closed, open
BUTTONBOARD_ENABLE
Enables and disables the buttonboard for initialization. Set to default
will always be possible. Can only be enable when in OOS. When not in
OOS it automatcally returns to false, to come back to its original setting
when in OOS. FF card must change this setting on the sensorboard.
INTERNAL_ALERTS
Bad position sensor
Bad temperature sensor
System temperature exceeded
Software error IO card
Travel deviation alert
Device shutdown
Unknown error
34
35
Description
Valid Range
Initial Value
Permission
closed, open
closed
Read only
Device configuration (continued)
"- enable when enable when in Read / Write
in OOS
OOS
- Never in
OOS"
N/A
Read only
Diagnostic configuration
36
FUNCTION_MODULE_
COUNTER
Counts the end position cycles performed by the control module.
FM_CNT_VALUE (read only)
FM_CNT_LIMIT
37
PNEUMATIC_MODULE_
COUNTER
Counts the end position cycles performed by the pneumatic module
PM_CNT_VALUE
PM_CNT_LIMIT
38
ACTUATOR_MODULE_
COUNTER
Counts the end position cycles performed by the actuator
ACT_CNT_VALUE
ACT_CNT_LIMIT
39
VALVE_MODULE_COUNTER Counts the end position cycles performed by the valve
VLV_CNT_VALUE
VLV_CNT_LIMIT
40
41
TIMERS (units are seconds). TIME_IN_POSITION - Holds the time in current positionReset to zero
when power switched off
TIME_IN_POSITION_HI_LIM - Sets a limit for an alert for the time in
position
OPEN_TIMERAVEL_TIME Indicates time between: - Pilot position
change commanded and - Open trip position reached.
OPEN_TRAVEL_TIME_HI_LIM
FF_COMM_STAT
04294967295
[2] 0 4294967295
N/A
Read only
1,000,000
Read / Write
04294967295
[2] 0 4294967295
N/A
Read / Write
1,000,000
Read / Write
04294967295
[2] 0 4294967295
N/A
Read / Write
1,000,000
Read / Write
04294967295
[2] 0 4294967295
0 to
4294967295
[2] 0 to
4294967295
0 to 65536
N/A
Read / Write
1,000,000
Read / Write
0
Read only
0
read.write
0
Read only
[2] 0 to 65536
0
Read / Write
OPEN_TRAVEL_TIME_LO_LIM
[2] 0 to 65536
0
Read / Write
OPEN_TRAVEL_TIME_AVG (average of 30 strokes)
0 to 65536
0
Read only
OPEN_TRAVEL_AVG_HI_LIM
[2] 0 to 65536
0
Read / Write
OPEN_TRAVEL_AVG_LO_LIM
[2] 0 to 65536
0
Read / Write
CLOSE_TRAVEL_T Indicates time between: - Pilot position change
commanded and - Close trip position reached.
CLOSE_TRAVEL_TIME_HI_LIM
0 to 65536
0
Read only
[2] 0 to 65536
0
Read / Write
CLOSE_TRAVEL_TIME_LO_LIM
[2] 0 to 65536
0
Read / Write
CLOSE_TRAVEL_TIME_AVG (average of 30 strokes)
0 to 65536
0
Read only
CLOSE_TRAVEL_AVG_HI_LIM
[2] 0 to 65536
0
Read / Write
CLOSE_TRAVEL_AVG_LO_LIM
[2] 0 to 65536
0
Read / Write
0 to 65535
0
Read only
FF_COMM_TIME_OUT - States how manny of the attempts were timed 0 to 65535
out
When the base record option is enabled, operator can write/read
parameters to/from the sensor board that are not available via the FF
parameter list. A method is used to enable/disable the parameter and a
direct write is not necessary.
0
Read only
Indicates quality of FF communications
FF_COMM_ATTEMPTS - States the number of attempts.
When at max, reset to 0 for timed out messages also!
42
BASE_RECORD
Page 33
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.2 FieldQ™ Transducer Block (continued)
Index
No.
Name
Description
35
INTERNAL_ALERTS
Bad position sensor
Valid Range
Initial Value Permission
Alerts
N/A
Read only
Bad temperature sensor
System temperature exceeded
Software error IO card
Travel deviation alert
Device shutdown
Unknown error
41
RECOMMENDED_ACTION
Enumerated list of recommended actions of the device, displayed with a N/A
device alert (can be multiple, see table below)
see table
0
Read only
42
FAILED_PRI
2
Read / Write
43
FAILED_ENABLE
Designates the alarming priority of the FAILED_ALM. Handling defined
by FF.
0: All FAILED alerts disabled
1: All failed alerts supressed
2: Higher process failed alerts
see alert table
44
FAILED_MASK
see alert table
45
FAILED_ACTIVE
see alert table
N/A
Read only
46
FAILED_ALM
Alarm indicating a failure within a device which makes the device nonoperational.
UNACKNOWLEDGED:
0: Undefined, 1: Acknowledged, 2: Unacknowledged
ALARM_STATE
0:Undefined 0
1:Clear- Reported
2:Clear- Not reported
3:Active- Reported
4:Active- Not reported
TIME_STAMP
0 to 15
N/A
Read only
Read only
Read only
SUBCODE value should match alert as stated under FAILED_ENABLE
Read only
VALUE
Read only
47
MAINT_PRI
See index 42 FAILED_PRI
0 to 15
2
48
MAINT_ENABLE
see alert table
N/A
Read / Write
49
MAINT_MASK
see alert table
50
MAINT_ACTIVE
see alert table
51
MAINT_ALM
See index 46 FAILED_ALM
52
ADVISE_PRI
See index 42 FAILED_PRI
0 to 15
53
ADVISE_ENABLE
see alert table
N/A
54
ADVISE_MASK
see alert table
Read / write
55
ADVISE_ACTIVE
see alert table
Read only
56
ADVISE_ALM
See index 46 FAILED_ALM
31
INSTRUMENT_TEMP
Indicates the internal temperature of the instrument
Read only
2
Read / Write
Read / write
N/A
N/A
Read only
10 to 100
100
Read only
0 to 1
N/A
Read / Write
0
Read only
0
Read only
1
Read / Write
STATUS
57
HEALTH_INDEX
VALUE Indicates the internal temperature of the device in degrees
Celcius
Parameter representing the overall health of the device.
100 being perfect and 1 being non-functioning.
no alerts -> 100
ADVISE_ACTIVE -> -10 per advice
MAINT_ACTIVE -> - 40 per advise
FAIL_ACTIVE -> = 10 (10 also lowest value)
Others
30
FLASH_LED
58
FF_COMM_STAT
59
PWA_SIMULATE
Page 34
For identification blink status led (5 min.)
0: finished
1:start
Indicates quality of FF communications
FF_COMM_ATTEMPTS - States the number of attempts.
0 to 65535
When at max, reset to 0 for timed out messages also!
FF_COMM_TIME_OUT - States how manny of the attempts were timed 0 to 65535
out
Password protected and off when powercycled! If this is set to 2 then all 1 and 2
the alert parameters are writable 1: sumulate off, 2 simulate enabled
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.3 FieldQ™ Alerts & recommended actions
Alert default setting
Alerts
Parameter name
DeltaV text
Recommended actions
enable
mask
(show)
enable
mask
(show)
Fail
mask
(show)
Maintenance
enable
Advisory
bad_position_sensor
Bad Position Sensor
Feedback problem, replace Control module when
possible
n
n
y
y
n
n
bad_temperature_sensor
Bad Temperature
Sensor
Temperature sensor problem, replace Control
module when possible
n
n
y
y
n
n
system_temperature_exceeded
System Temperature
Exceeded
Take corrective actions to bring temperature
within specified range.
n
n
y
y
n
n
software_error
Software Error
Software error has been detected, replace
control module when possible.
n
n
y
n
n
n
travel_deviation
Travel Deviation
Lost position, Check air pressure
y
y
n
n
n
n
shutdown_is_set
Shutdown Is Set
Internal communications problem, check
shutdown configuration for restart, Replace
Control module.
Error is undefined, replace control module when
possible
n
n
n
n
y
y
n
n
y
n
n
n
n
n
y
y
n
n
Internal alerts
undefined_error
Undefined Error
Counter alerts
cm_life_exceeded
Control Module Life
Cycle Exceeded
Control module life cycle exceeded, replace
control module
pm_life_exceeded
Pneumatic Module Life Pneumatic module life cycle exceeded, replace
Cycle Exceeded
pneumatic module.
n
n
n
n
n
n
act_life_exceeded
Actuator Life Cycle
Exceeded
Actuator life cycle exceeded, replace actuator.
n
n
n
n
n
n
valve_life_exceeded
Valve Life Cycle
Exceeded
Valve life cycle exceeded,valve requires
maintenance.
n
n
n
n
n
n
time_in_position_exceeded
Time in position
exceeded
Time in position exceeded, take appropriate
action.
n
n
n
n
n
n
open_travel_time_exceeded
Open travel timer
exceeded
Open travel timer exceeded, check valve system.
n
n
n
n
n
n
close_travel_time_exceeded
Close travel timer
exceeded
Close travel timer exceeded, check valve system.
n
n
n
n
n
n
y
y
n
n
n
n
Timer alerts
Initialization alert
initialization_failed
Initialization Failure
Device failed initialization; Check airpressure,
check actuator sizing, check valve system
Page 35
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.3 FieldQ™ Alerts & recommended actions (continued)
Alert default setting
Alerts
Internal communications are lost, device will act
according to shutdown configuration.
rb_NV_write_deferred
Output Board NV
Memory Failure
NV Write Deferred:
A high number of writes has been detected to
non-volatile memory. To prevent premature failure
of the memory, the write operations have been
deferred. The data will be saved about every 3
hours.
This condition usually exists because a program
has been written that writes to control block
parameters not normally expected to be written
to on a cyclic basis. Any such automated write
sequence should be modified to write the the
parameter(s) only when needed.
It is recommended that you limit the number
of periodic writes to all static or non-volatile
parameters such as HI_HI_LIM, LOW_CUT, SP,
TRACK_IN_D, OUT, IO_OPTS, BIAS, STATUS_
OPTS, SP_HI_LIM, and so on.
If PWA simulate mode has been activated.
The PWA active parameters can now be
written as well as the resource block detailed
status parameters and the internal alerts in the
Transducer Block where the PWA active alarms
originate from.
Output Board NV Memory Failure:
"Non-volatile EEPROM data corruption was
detected on the Fieldbus Electronics Board.
Default values were loaded into the faulty block.
1. Check the device configuration for changes in
the block parameter values.
2. Reset the device to clear the error.
3. Download a Device Configuration.
NOTE: If the failure reoccurs it may indicate a
faulty EEPROM memory chip.
Output Board Electronics Failure:
The Device has detected a fault with an electrical
component on the Fieldbus Electronics Module
Assembly. Replace the Device.
mask
(show)
Internal Io Failure
enable
io_failure
mask
(show)
Recommended actions
enable
DeltaV text
Fail
mask
(show)
Parameter name
Maintenance
enable
Advisory
y
y
n
n
n
n
n
n
n
n
y
y
n
n
n
n
y
y
y
y
n
n
n
n
y
y
n
n
n
n
Internal IO failure alert
PWA_simulate_active
rb_nv_memory_failure
rb_nv_electronics_failure
PWA Simulate Active
Output Board NV
Memory Failure
Output Board
Electronics Failure
diag_opt_PWA_simulate
PWA Simulate
func_opt_simulate
Simulate Switch
misc_opt_base_record
Base Record
Page 36
Since the hardware simulate switch may be
impractical to access, a software option is being
provided.
When the base record option is enabled, operator
can write/read parameters to/from the sensor
board that are not available via the FF parameter
list.
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Table 4.4 FieldQ™ NAMUR NE- 107 Alarms
Parameter
Mnemonic
FD_CHECK_ACTIVE
Obj
Type
S
Data Type/
Structure
Bit String
Use/Model
Store
Size
C/FD Active
D
4
FD_CHECK_ALM
R
DS-87
C/Alarm
D
15
FD_CHECK_MAP
S
Bit String
C/Contained
S
4
FD_CHECK_MASK
S
Bit String
C/Contained
S
4
FD_CHECK_PRI
S
Unsigned8
C/Alert Priority
S
1
FD_EXTENDED_ACTIVE_n
S
Bit String
C/Contained
D
4
FD_EXTENDED_MAP_n
S
Bit String
C/Contained
S
4
FD_FAIL_ACTIVE
S
Bit String
C/FD Active
D
4
FD_FAIL_ALM
R
DS-87
C/Alarm
D
15
FD_FAIL_MAP
S
Bit String
C/Contained
S
4
FD_FAIL_MASK
S
Bit String
C/Contained
S
4
FD_FAIL_PRI
S
Unsigned8
C/Alert Priority
S
1
FD_MAINT_ACTIVE
S
Bit String
C/FD Active
D
4
FD_MAINT_ALM
R
DS-87
C/Alarm
D
15
FD_MAINT_MAP
S
Bit String
C/Contained
S
4
FD_MAINT_MASK
S
Bit String
C/Contained
S
4
FD_MAINT_PRI
S
Unsigned8
C/Alert Priority
S
1
FD_OFFSPEC_ACTIVE
S
Bit String
C/FD Active
D
4
Valid
Range
Initial
Value
Permission
Other
Read only
Range
Check
ALARM
ALARM
0 - 15
0
ALARM
Yes
Read only
Read only
ALARM
ALARM
0 - 15
0
ALARM
Yes
Read only
ALARM
ALARM
0 - 15
0
ALARM
Yes
Read only
FD_OFFSPEC_ALM
R
DS-87
C/Alarm
D
15
FD_OFFSPEC_MAP
S
Bit String
C/Contained
S
4
FD_OFFSPEC_MASK
S
Bit String
C/Contained
S
4
FD_OFFSPEC_PRI
S
Unsigned8
C/Alert Priority
S
1
0 - 15
0
FD_RECOMMEN_ACT
S
Unsigned16
C/Contained
D
2
0
FD_SIMULATE
R
DS-89
C/FD Simulate
D
9
1 – manf
spec
FD_VER
S
Unsigned16
C/Contained
S
2
ALARM
ALARM
ALARM
Yes
Read only
disabled
Read only
Page 37
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
5
Operations and Maintenance
5.1
Fault state
The fault state parameter, when active, indicates
a loss of communication to an output block, a fault
promoted to an output block, or loss of a physical
contact. If the fault state is active, the output function
blocks perform their Fault State actions. Selecting
the feature Fault State enables the ability to manually set and clear the fault state of the device. Setting the Set Fault State parameter to “Set” manually
places the instrument in the fault state. Setting the
Clear Fault State parameter to “Clear” clears the
device fault state if no faults are currently active. You
can test the actions the output blocks will perform by
manually setting the fault state active.
5.2
Restart method
The following method is provided with the FieldQ
Module Device Description:
 Restart
Method Description:
 Master Reset - Available via the Resource Block,
the Master Reset method is required for restarting
the switchbox without removing power. It also allows the user to set data within the switchbox to its
default state. In addition to restarting the switchbox, this method also performs switchbox integrity
tests to verify that it is acceptable to restart the
switchbox. This method is only available via the
Resource Block and is described in detail in the
detailed setup section (section 4.1).
5.3
Restarting the module
You can restart the module via different mechanisms. Depending on which restart option is used;
the communication links, static parameters, etc. may
be affected. However, due to the effect that a restart
can have on the module, and therefore the process,
restarting the module should be used cautiously.
WARNING
Restarting the FieldQ may cause
loss of control of the process.
Page 38
5.3.1Software restart
There are several Restart options as described
bellow. This can be done via parameter RESTART
(index 16) in the Resource block. The following is a
brief description for each of the restart options:
 Resource - Performing a “Resource”-restart has
no observable effect on the module resetting the
dynamic variables in the Function Blocks. However, the dynamic variable within the module are reset and this could cause a “bump” in your process.
 Processor - Performing a “Restart Processor” has
the same effect as removing power from the module and re-applying power. This is typically used
to restart the Foundation Fieldbus Interface card
should the Interface Card and the Module I/O card
get out of sync due to incorrect power application.
 Defaults - Performing a “Restart with Defaults”
should be done with care. This restart sets the
static parameters of the function blocks in the
module to their default state. It also disconnects all
links within the module. After performing a “Restart
with Defaults”, a “Restart Processor” should be
performed. Within the FieldQ Series of modules,
the “Restart with Defaults” option is the only option
that will read certain data from the FieldQ Communications board.
 Actuator Processor - Performing a “Actuator
Processor”-Restart has the same effect as removing power from the control part of the module and
re-applying power. This is typically used to restart
the control part of the module.
 Actuator Defaults - Performing a "Actuator
Defaults”-restart should be done with care. This
restart sets the switch point to default (see §3.2).
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.QC34.E Rev: 0
January, 2013
Page 39
North & South America
19200 Northwest Freeway
Houston Texas 77065
USA
T +1 281 477 4100
F +1 281 477 2801
2500 Park Avenue West
Mansfield, OH 44906
USA
T +1 419 529 4311
F +1 419 529 3688
9009 King Palm Drive
Tampa, FL 33619
USA
T +1 813 630 2255
F +1 813 630 9449
13840 Pike Road
Missouri City, Texas 77489
USA
T +1 281 499 1561
F +1 281 499 8445
Av. Hollingsworth
325, Iporanga Sorocaba
SP 18087-105
Brazil
T +55 15 3238 3788
F +55 15 3228 3300
Middle Eas t & Africa
P. O. Box 17033
Dubai
United Arab Emirates
T +971 4 811 8100
F +971 4 886 5465
P. O. Box 105958
Abu Dhabi
United Arab Emirates
T +971 2 697 2000
F +971 2 555 0364
P. O. Box 3911
Al Khobar 31952
Saudi Arabia
T +966 3 814 7560
F +966 3 814 7570
Via Montello 71/73
20038 Seregno (Milan)
Italy
T +39 0362 2285 207
F +39 0362 2436 55
P.O. Box 10305
Jubail 31961
Saudi Arabia
T +966 3 340 8650
F +966 3 340 8790
6 Bracken Hill
South West Industrial Estate
Peterlee SR8 2LS
United Kingdom
T +44 191 518 0020
F +44 191 518 0032
P. O. Box 32281
Doha
Qatar
T +974 4 576777
F +974 4 315448
24 Angus Crescent
Longmeadow Business Estate
East
P.O. Box 6908; Greenstone; 1616
Modderfontein, Extension 5
South Africa
T +27 11 451 3700
F +27 11 451 3800
Europe
Asveldweg 11
7556 BR Hengelo (O)
The Netherlands
T +31 74 256 1010
F +31 74 291 0938
Siemensring 112
47877 Willich
Germany
T +49 2154 499 660
F +49 2154 499 6613
25, Rue de Villeneuve
Silic – BP 40434
94583 Rungis
France
T +33 1 49 79 73 00
F +33 1 49 79 73 99
2A Szturmowa Str
02-678 Warsaw
Poland
T +48 22 4589237
F +48 22 45 89 231
C/ Francisco Gervás, 1
28108 Alcobendas – Madrid
Spain
T +34 0913 586 000
F +34 0913 589 145
Letnikovskaya Str. 10-2
115114 Moscow|
Russia and FSU
T +7 495 981 98 11
F +7 495 981 98 10
Hungári körút 166-168
H-1146 Budapest
Hungary
T +36 1 462 4000
F +36 1 462 0505
Asia Pa cific
No. 9 Gul Road
#01-02 Singapore 629361
T +65 6501 4600
F +65 6268 0028
9/F Gateway Building
No. 10 Ya Bao Road
Chaoyang District
Beijing 100020
P.R.China
T +86 10 5821 1188
F +86 10 5821 1100
No.15 Xing Wang Road
Wuqing Development Area
Tianjin 301700
P.R.China
T +86 22 8212 3300
F +86 22 8212 3308
Lot 13112, Mukim Labu
Kawasan Perindustrian Nilai
71807 Nilai, Negeri Sembilan
Malaysia
T +60 6 799 2323
F +60 6 799 9942
471 Mountain Highway
Bayswater, Victoria 3153
Australia
T +61 3 9721 0200
F +61 3 9720 0588
Delphi B Wing, 601 & 602
6th Floor, Central Avenue
Powai, Mumbai – 400 076
India
T +91 22 6662 0566
F +91 22 6662 0500
NOF, Shinagawa Konan Bldg
1-2-5, Higashi-shinagawa
Shinagawa-ku, Tokyo
140-0002 Japan
T +81 3 5769 6873
F +81 3 5769 6902
Please visit our web site for up to date product data. www.FieldQ.com
All Rights Reserved.
We reserve the right to modify or improve the designs or specifications of the products mentioned in this manual at any time without notice.
Emerson Process Management does not assume responsibility for the selection, use or maintenance of any product. Responsibility for proper
selection, use and maintenance of any Emerson Process Management product remains solely with the purchaser.
©2013 Emerson Electric Co.
www.FieldQ.com
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement