Reference manual
DOC.RM.QC31.E Rev: A7
March, 2010
FieldQ Valve Actuator
QC31, DeviceNet™ Control Module
TM
www.FieldQ.com
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
Contents
AESSENTIAL INSTRUCTIONS
3
A1
A2
A3
A4
Before you start .............................................. 3
Orientation (see fig. A1).................................. 3
Applicable control modules............................. 3
Installation, operation and maintenance reference documents.............................................. 3
A5 Operating medium........................................... 3
A6 Product integrety............................................. 3
A7 Hazardous areas............................................. 4
A8 Warning ; Moving parts................................... 4
A9 Prevent moisture entering the actuator........... 4
A10 Warning ; Magnetic material............................ 4
A11 Warning ; Temperature range.......................... 4
1
Module Description
1.1
1.2
1.3
1.4
1.5
1.6
FieldQ™ DeviceNet™ Control Module.............. 5
DeviceNet™ Communication........................... 6
Device Description and Methods.................... 6
Node Address.................................................. 6
Related Information......................................... 6
Specifications, DeviceNet™ Hardware........... 6
2
Installation
2.1
2.2
2.3
2.4
2.5
Introduction..................................................... 7
Applicable control modules............................. 7
Before starting................................................. 7
Pneumatic connections................................... 7
Electric connections........................................ 8
Page 2
5
7
3
Commisioning
10
3.1
3.2
3.4
Implementation of the EDS file in the host system................................................................ 10
Intialization.................................................... 10
Troubleshooting............................................. 13
4
Detailed Configuration
15
4.1
4.2
4.3
4.4
4.5
4.6
4.7
FieldQ DeviceNet Objects Details................. 15
Identity Object, Class ID 1 (01hex).................. 17
Message Router Object, Class ID 2 (02hex)... 18
DeviceNet Object, Class ID 3 (03hex)............. 19
Assembly Object, Class ID 4 (04hex).............. 20
Connection Object, Class ID 5 (05hex)........... 21
Discrete Input Point Object,
Class ID 8 (08hex)........................................... 22
4.8 Discrete Output Point Object,
Class ID 9 (09hex)........................................... 23
4.9 Analog Input Point Object,
Class ID 10 (0Ahex)......................................... 24
4.10 Acknowledge Handler Object,
Class ID 43 (2Bhex)......................................... 25
4.11 Controller Object, Class ID 100 (64hex).......... 26
4.12 Monitor Object, Class ID 101 (65hex).............. 29
5.0 Basic DeviceNet l/O Operation
5.1
5.2
31
Polled I/O...................................................... 31
Cyclic and Change-Of State I/O.................... 31
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
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 116 psig
• This manual does not provide instructions for
installations in hazardous areas. See applicable
sections of Installation Guide DOC.IG. QC31.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
QC31 -DeviceNet™ Weatherproof Module
QC31 -DeviceNet™ Non-Incendive
or Non Sparking Module
Check the module label for the right execution.
Installation, operation and
maintenance reference
documents
Before mounting, installing, commisioning 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 availabel from www.FieldQ.com or
through your local Valve Automation representative).
A5Operating medium
•
•
•
•
Air or inert gasses.
Air filtered at 50 micron.
Dew point 10 K bellow operating temperature.
For subzero applications take appropriate measures.
A6
Product integrety
• Assembly or disassembly is only allowed for replacing sealings and guide bands (softparts).
• Under the European Pressure Equipement Directive, conversion of actuators may only be performed by companies or personel, authorized by
Emerson Process Management .
1
2
3
OK!
Fig A.1Orientation
Control Module Type Label =
QC31... = DeviceNet™
Fig A.2 Module check
Page 3
TM
Reference manual DeviceNet™ Control module
DOC.RM.QC31.E Rev: A7
March, 2010
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.QC31.1.
This can cause damage or malfunction.
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
1
Module Description
1.1
FieldQ™ DeviceNet™ Control Module
This manual contains installation, operating, and
maintenance information for the FieldQ™
DeviceNet™ 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 DeviceNet™ 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 fieldbus 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 DeviceNet™ 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 DeviceNet™ 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
Automatic initialization:
Push 4 seconds
Closed reassignment button
Closed LED
1 2 3 4 5
DeviceNet™
status LEDs
- Module
- Network
Main Status LED
Open LED
Open reassignment
button
Main Status LED
on
off
LED = Flashing
on
off
LED = Blinking
Time
Fig 1.1 FieldQ DeviceNet™ Module
Fig 1.2 Customer interface of the QC31
DeviceNet™ Control Module
Page 5
TM
Reference manual DeviceNet™ Control module
DOC.RM.QC31.E Rev: A7
March, 2010
1.2
DeviceNet™ Communication
The FieldQ QC31 module uses the DeviceNet™ protocol to communicate with other field devices and the
host system. DeviceNet™ is an all-digital, serial, twoway communication system, which interconnects field
equipment such as transmitters, valve controllers,
and process controllers. DeviceNet™ 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 DeviceNet™ environment is the base level group
of digital networks in the hierarchy of plant networks.
The DeviceNet™ retains the desirable features of
analog systems such as:
 A standardized physical interface to the wire
In addition, use of DeviceNet™ 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
1.3
Device Description and Methods
This manual describes device setup using the
Electronic Data Sheet (EDS) specified by the DeviceNet™ protocol. Parameter access and methods
are also described in this manual.
1.4
Node Address
The default node address of the FieldQ QC31 DeviceNet™ module is 63.
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.
Page 6
1.5
Related Information
1.5.1
DeviceNet™ Installation and wiring
guidelines
DeviceNet™ Technical Overview (available from the
Fieldbus Foundation)
1.5.2Other Related Information
Other documents containing information related to
the FieldQ Control module include:
1.604.09
Control Module data sheet
DOC.IG.QC31.1 Installation Guide QC31 Control
odule with DeviceNet™
DOC.IOM.Q.E Installation Operation & Maintenance Manual.
These documents are free available for download
from www.FieldQ.com or contact your local FieldQ
representative.
1.6
Specifications, DeviceNet™
Hardware
Electrical Entry
2 x M20 or 1/2” NPT
Electrical Input, Fieldbus Interface
Voltage Level
:11 to 25 volts
Nominal Current
:75mA (@ 24V, pilot valve =
on)
Operating Ambient Temperature Limits
-20°C to +80 C (-4° F to 176° F)
Electrical connections
Terminal Block
Optional quick connectors
Housing
Material :Aluminum Alloy
Finish
:Polyester non-TGIC based powder
coating
Enclosure :IP65 / NEMA 4X
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
2
Installation
2.1
Introduction
The FieldQ DeviceNet™ Control module is a 4-wire
device with seperate connections for power and communication.
For various application guides like installation and
wiring guidelines please check:
www.ODVA.org
The following sections provide instructions on pneumatic and electric installations. For instructions on
commisioning, see chapter 3.
2.2
Applicable control modules
QC31
QC31
- DeviceNet™
- DeviceNet™ Non-Incendive
or Non Sparking
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
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.1Operating media
*
*
*
*
Air or inert gases.
Air filtered at 50 micron.
Dew point 10 K bellow operating temperature.
For subzero applications take appropriate measures.
2.4.2
OK
OK
Pneumatic connections
Single acting (spring return) or
Double acting actuator
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
Control
Module cover
Double
acting
Ps : 1/4”BSP or 1/4”NPT
Control Module Type Label =
OK QC31... = DeviceNet™
Ra
OK Actuator Type Label =
Rb
QS xxxx = Single acting (Spring Return)
QD xxxx = Double acting
Fig. 2.2 Identification
Ps : 1/4”BSP or 1/4”NPT
Fig. 2.3: Pneumatic connections
Page 7
TM
Reference manual DeviceNet™ Control module
DOC.RM.QC31.E Rev: A7
March, 2010
2.5Electric connections
Table 2.1Electrical Input, Fieldbus Interface
DeviceNet
5 pole terminal, or quick connector
Connection
Voltage isolation None
120mA @ 11VDC
Nominal power
75mA @ 25VDC
Maximum power 2.0 W
Environmental conditions :
-20°C to +80°C
Temperature *
(-4°F to +176°F)
0 to 85% at 25°C(+77°F) derate to 50%
Humidity
above 40°C (104°F) (non-condensing).
Operating full power available up to 2000
Altitude
meter (6000 feet).
Use
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.
Page 8
2.5.1Electrical data of the hazardous area
executions
Please check the following Chapters of Installation
Guide (DOC.IG.QC31.1) for electrical data in case
the control module is used in a Hazardous location:
Non incendive/Non Sparking
- QC31 DeviceNet™ Chapter 10
2.5.2
Wiring dimensions
Solid wire
Stranded wire
2.5.3
2.5mm2 max.
0.2-2.5mm2 or 30-12 AWG
Tools (Screw driver)
Terminals
Cover screws
Cross slotted Phillips screws nr. 0
Cross slotted Phillips screws nr. 2
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
WARNING:
* 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.
Control Module
Type Label
Terminals
* 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.4
Fig. 2.5.1Installing wiring
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 DeviceNet™ 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.1.
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.5
Main Status LED
DeviceNet™ installation and wiring
guidelines
For various application guides like installation and
wiring guidelines please check:
www.ODVA.org
Fig.2.5.2 Earth wire connection
DeviceNet™ terminal wiring connections:
-V
CAN_L
Shield
CAN_H
+V
1
2 QC31
3 DeviceNet™
4 control module
5
Quick connector pinouts:
(male chassis part)
3
2
4
5
1
7/8" UNC
4
1
3
2
5
3
5
1
4
2
M12
Quick
connector
Black
Blue
Grey
White
Red
1
2
3
4
5
Terminal
Fig. 2.5.3Terminal connections and Quick connector
pinouts
Page 9
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
3
Commisioning
In order to commision the QC31 module just two
steps need to be done in advance:
1 Implementation of the EDS file in the host system.
2 Initialization of the FieldQ QC31 module.
3.1
Implementation of the EDS file in
the host system.
These EDS file 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
3.2.1
Initialization using local buttons
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, meaning the initialization was successful.
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.
Remarks:
Intialization
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).
- If the Status LED is flashing, the auto initialization
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.
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.
Automatic initialization:
Push 4 seconds
Closed reassignment button
Closed LED
"Close"
end position
End stop
offsets
End stop
offsets
10˚max
1 2 3 4 5
DeviceNet™
status LEDs
- Module
Main Status
LED
Open LED
Open reassignment button
- Network
Main Status LED
±40˚
±40˚
10˚max
on
off
LED = Flashing
on
off
LED = Blinking
"Open"
end position
Factory settings
Setting after initialization
Fig 3.1 Feedback characteristics
Page 10
Time
The default setting of the reassignment buttons is:
Enabled
Fig. 3.2 FieldQ Button board and wiring compartment
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
Table 3.1
Main status LED indications (see figure 3.2)
Status
Status LED action
Open/Close LED action
OK (Init successful)
Constant on
Normal operation (position indicated by LED which is constant on)
Initializing
Blinking
Normal operation
Init error
Flashing
Normal operation
Init default
Waiting for reassignment confirm
Identification
Flashing
Activated LED (depending on position) blinking
Activated by push button LED Flashing, other LED is off
Table 3.2
Constant on
Flashing for 300 sec
Button board functionality (see figure 3.2)
Action
Set to factory default
Initialize
Reassignment “Open” end position
Reassignment “Close” end position
Table 3.3
Normal operation
Reassignment buttons
Push both buttons before power up, and than hold until Status LED is constant on. Release and observe LEDs to indicate default
While powered up push both buttons until Status LED starts blinking
Push “Open” button until “Open” LED starts flashing, release button and
push again until LED is constant on, Status LED indicates “init successful”.
Push “Close” button until “Close” LED starts flashing, release button and
push again until LED is constant on, Status LED indicates “init successful”.
DeviceNet™ Module status LED (see figure 3.2)
For this state:
LED is:
To indicate:
No Power
Off
There is no power applied to the device
Operational
Green
Standby (The Device
Flashing Green
Needs Commissioning)
Minor Fault
Flashing Red
The device is operating in a normal condition.
The device needs commissioning due to configuration missing, incomplete
or incorrect.
Recoverable Fault
Unrecoverable Fault
Red
The device has an unrecoverable fault; may need replacing
Device Self Testing
Flashing Red-Green
The Device is in Self Test.
Table 3.4
DeviceNet™ Network status LED (see figure 3.2)
For this state:
Not Powered / Not
On-line
LED is:
To indicate:
Device is not on-line.
Off
- The device has not completed the Dup_MAC_ID test yet.
- The device may not be powered, look at Module Status LED.
Device is on-line but has no connections in the established state.
On-line, Not Connected
- The device has passed the Dup_MAC_ID test, is on-line, bus has no
established connections to other nodes.
Flashing Green
- For a Group 2 Only device it means that this device is not allocated to a
master.
- For a UCMM capable device it means that the device has no established
connections.
The device is on-line and has connections in the established state.
Link OK
On-line, Connected
Green
Connection Time-Out
Flashing Red
Critical Link Failure
Red
Communication Faulted
and Received an IdenFlashing Red & Green
tify Comm Fault Request- Long Protocol.
- For a Group 2 Only device it means that the device is allocated to a Master.
- For a UCMM capable device it means that the devise has one or more
established connections.
One or more I/O Connections are in the Timed-Out state.
Failed communication device. The device has detected an error that has
rendered it incapable of communicating on the network (Duplicate MAC ID,
or Bus-off).
A specific Communication Faulted device. Te device has detected a Network Access error and is in the Communication Faulted state. The device
has subsequently received and accepted an Identify Communication
Faulted Request. Long Protocol message.
Page 11
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
3.2.2
Initialization using Bus Command
1 Go to the Controller object Vendor Specific Services.
2 To start the initialization procedure;
Activate Service code 32 as per table 3.5.
3 When the initialization is running, the "Device
Status" parameter of the Monitor object is set to
"init-running" (bit 9) and the Status LED will blink.
4 Actuator will cycle two or three times.
5 When the initialization is successful, the "Device
Status" parameter of the Monitor object is set to
"init-OK" (bit 14) and the Status LED is on.
Remark:
- If the auto initialization has failed, the status LED
on the module is flashing and the status of parameter AUTO INITIALIZATION will indicate a posible
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 posible to finish the auto-initialization routine, the switch points can be set, according §3.4.3
Table 3.5
Controller Vendor Specific Common Services
Service Code (hex)
Page 12
Service Name
32
Start auto init (Valve will Move)
33
Stop auto init
34
Open end pos
35
Close end pos
36
Restart processor
37
Restart with default
38
Buttonboard enable
39
Buttonboard disable
40
Shutdown reset status
3.3.1
Check functioning
Before function test:
- The unit must be connected to a host system and
power must be connected (see chapter 3).
- The unit must be successfully initialized ("Device
Status" parameter of the Monitor object must be
"init-OK" (bit 14).
1 Set Instance ID 100 of "Discrete Output Point Object" to “Open”.
2 Actuator moves to "Open" position.
3 Set Instance ID 100 of "Discrete Output Point Object" to “Close”.
4 Actuator moves to "Closed" position.
3.3.2
Recognizing LED
To recognize a particular FieldQ actuator in the plant
“Recognizing LED” function can be activated in the
Monitor Object . When this function is activated, the
status LED will blink for 5 minutes. To start the LED:
1 Activate the Monitor Object Instance Attribute ID 3
2 Status LED on the unit will blink for 5 minutes.
3 After 5 minutes Instance Attribute ID 3 will change
back "not active".
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
3.4Troubleshooting
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 2.5 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.1.1 “Factory default settings”, using a
bus command.
To set the control module to its factory default settings, do the following;
1 Go to the Controller object Vendor Specific Services.
2 To set the "Factory default settings" position;
Activate Service code 37 as per table 4.11.4.
3.4.2
If auto initialization procedure has
failed
If the auto initialization has failed, the status LED on
the module will flash. The "Device Status" parameter
of the Monitor object will indicate a posible cause:
Table 3.6
Device Status attribute of the initialization diagnostics:
Bit
9
Error
Undetermined bad
repeatability
Running
Solution
Check air-pressure at the actuator and/or actuator sizing.
10
Aborted
12
Time Out
11
Range Error
14
Successful
Operator: restart
It takes too long before endpositions are found.Check airpressure at the actuator and/or
actuator sizing.
Difference between open
andclosed end position is too
small. Check air-pressure,
check proper valve rotation.
15
No Valid Data
8
To solve this:
1 Check table 3.6 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 procedure (see §3.2).
4 When the actuator does not move within 10 seconds, the auto initialization will fail.
To solve this either;
- perform the “default setting” procedure (see
§3.4.1) and repeat the initialization procedure
(see §3.2), or
- set the limit switch points individually by the bus
see (see §3.4.4)
3.4.3
If the position feedback is reversed.
1 Go to the Controller object Vendor Specific Services.
2 To set the "Open" position;
Activate Service code 34 as per table 4.11.4
The "Closed" position will change automatically.
3 To set the "Closed" position;
Activate Service code 35 as per table 4.11.4
The "Closed" position will change automatically.
The "Open" position will change automatically.
Note:
- If "Shutdown" is activate (see 4.11.1), check if "Action" is still "OK".
Not initialized, start initialization
Page 13
TM
Reference manual DeviceNet™ Control module
DOC.RM.QC31.E Rev: A7
March, 2010
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:
1Go to the Controller object Vendor Specific Services.
2To set the "Open" position;
Activate Service code 34 as per table 3.5.
The "Closed" position will change automatically.
3To set the "Closed" position;
Activate Service code 35 as per table 3.5.
The "Closed" position will change automatically.
The "Open" position will change automatically.
Note:
- If the problem is persistent, increase the endstop
offset (see 4.2.3.2).
3.4.5
If the initialization can not be started
via the push buttons.
1 Go to Controller object Vendor Specific Services.
2 Activate Service code 38 (Buttonboard enable) as
per table 3.5
Remark:
Setting the device to default will always enable the
push buttons (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 14
3.4.6
If the device is in Shutdown
When the device is in Shutdown an internal failure
has occured. Check the Device Status attribute of the
Monitor object (bit 6) is set, meaning that shutdown is
active.
If the internal failure is re-solved, the actuator shutdown status can be manually reset.
1 Go to "Controller Object Instance Attributes" and
set the parameter "Shutdown status" to "normal
operation"
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.
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4
Detailed Configuration
4.1
FieldQ DeviceNet Objects Details
General purpose discrete I/O, Class 7 with objects
Table 4.1
Protocol details and specifications
Common and DeviceNet
specific Objects
Identity Object
Class
ID
1
Message Router Object
2
1
DeviceNet Object
3
1
Assembly Object
4
100, 101
Connection Object
5
1, 2, 4, 5, 6, 7
Discrete Input Point Object
Discrete Output Point
Object
Analog Input Point Object
8
100, 101
9
100
10
100
Controller Object
100
1
Monitor Object
101
1
ODVA DeviceNet Spec Vol.I
Rev 3.7 & Vol. III Rev 1.8
Prefined Master/Slave Connection Set, Group 2 Server.
Polled I/O, Change of State
(COS), Cyclic, Explicit and
Dynamic Explicit connection
objects.
400 ms (2.5 kHz) minimum
5 pole terminal, or quick connector
Device Conformance
Comminications
I/O Protocols
Refresh rate
DeviceNet Connection
4.1.1
Instance ID(s)
1
Device configuration.
The following five parameter are available to configure the QC31 module for normal operation:
1 Auto initialization
2 Shutdown configuration
3 Reassign Open en Close end positions
4 Zero power condition
5 Button board enable/disable
6 Temperature units setting
4.1.1.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.1.1.2 Shutdown configuration
Shutdown configuration is part tof the Controller
Object. The behaviour, settings and default setting
of Shutdown configuration are decribed in chapter
4.11.1
4.1.1.3 Reassign Open en Close end positions
The FieldQ™ QC31 Control module will be shipped
with the default feedback characteristic, as per figure
4.1. This feedback characteristic is operational after
initialization (see chapter 3) and is suitable for most
applications.
If the default configuration is not suficient for your application, the switch points can be configured.
For the QC31 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.
2 "Open" and "Closed" end positions.
There are two procedures to re-configure the end
positions:
1If it is safe to cycle the actuator, perform the
initialization procedure (see §3.2).
2If it is not safe to cycle the actuator, perform the
following re-assignment procedure:
1Go to Vendor Specific Services in the Vendor
Specific Application Object (see also chapter
4.11, table 4.11.4)
2In case the "Open" position needs an update:
Set parameter Open End Pos.
3In case the "Closed" position needs an update:
Set parameter Close End Pos.
Default setting
after initialization
End stop
offsets
10˚max
Adjustable
range
End
position
30˚
5˚
30˚
10˚max
5˚
End
position
Fig. 4.1 Feedback characteristic
Page 15
TM
Reference manual DeviceNet™ Control module
DOC.RM.QC31.E Rev: A7
March, 2010
3 "Open" and "Closed" stop offset.
The "Open" or "Closed" limit stop 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
Parameters Open Switch Pos and Close Switch
Pos in the Controller Object Instance Attributes
(see chapter 4.11, table 4.11.2) can be used to
change the end stop offsets and can be set per °
(degree)
4.1.1.4 Zero power condition
(See chapter 4.12, table 4.12.2, attribute ID 2)
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
Fail-to-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.
Page 16
4.1.1.5 Buttonboard enable
(See chapter 4.11, table 4.11.4)
The button bord can be set to:
Service Code Description of Service
38
Enabled
39
Disabled
4.1.1.6Temperature units setting
(See chapter 4.9, table 4.9.3)
The device temperature can be read out in degree
Celcius (°C) or degree Fahrenheit (°F)
Attribute ID Semantics of Value
0 = Degree Celsius
100
1 = Degree Fahrenheit
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.2
Identity Object, Class ID 1 (01hex)
The Identity Object provides identification and general information about the FieldQ DeviceNet Module.
Table 4.2.1
Identity Object Class Attributes
Attribute
Access Rule Name
ID
1
Get (NV-RO) Revision
2
Get (NV-RO)
Table 4.2.2
Data
Type
UINT
Max Instance
UINT
2
Get (NV-RO)
Device Type
3
Get (V-RO)
Product Code
Data Type Description of Attribute
Get (NV-RO)
UINT
Identification of each vendor by number
UINT
Indication of general type of product
Semantics of
Value
903
0
(Generic Device)
Major Revision
1
Minor Revision
USINT
#
Minor Revision of FieldQ DeviceNet
5
Get (V-RO)
Status
WORD
Summary status of device
6
Get (NV-RO)
Serial Number
UDINT
Serial number of device
7
Get (NV-RO)
Product Name
SHORT
Human readable identification
8
Get (V-RO)
State
USINT
Present state of the device as represented by
the state transition diagram
10
Get/Set (NVRW)
Heartbeat Interval
USINT
The nominal interval between heartbeat messages in seconds
Table 4.2.3
1
Identification of a particular product of an individual vendor
STRUCT Revision of the item the Identity Object repreof
sents
USINT
Major Revision of FieldQ DeviceNet
UINT
Revision
4
Revision of the Identity Object Class Definition
Maximum instance number of an object currently
created in this class level of the device
Identity Object Instance Attributes
Attribute
Access Rule Name
ID
1
Get (NV-RO) Vendor ID
Semantics of
Value
1
Description of Attribute
41665
FieldQ Pneumatic
Valve Actuator
See [1] Chapter 5-2
Default = 0
Zero disables
transmission of
the heartbeat
message.
Identity Object Common Services
Service Code Class
Instance
Service Name
Description of Service
05(hex)
n/a
yes
Reset
Invokes the Reset-Service for the device
0E(hex)
yes
yes
Get Attribute Single
Used to read the specified attribute value
10(hex)
n/a
yes
Set Attribute Single
Used to write the specified attribute value
The instance service 05hex is used to reset the whole FieldQ DeviceNet. For this, three Reset Types are provided:
Reset Type = 0: Emulate as closely as possible cycling power. This value is the default, if this parameter is
omitted.
Reset Type = 1: Return as closely as possible to the out-of-the-box or default configuration (the “factory default
settings”), then emulate cycling power as closely as possible.
Reset Type = 2: Return as closely as possible to the out-of-box configuration with the exception of communication link parameters and emulate cycling power as closely as possible. The communication link
parameters that are to be preserved are defined by each network type. See the Reset service
of the network specific link object(s) for complete information.
Page 17
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
Table 4.2.4
Events defined for Identity Object Class
Event
Power Applied
Passed Tests
FailedTests
Source
DeviceNet interface
board
DeviceNet interface
board
DeviceNet interface
board
Activated
Controller card
Deactivated
n/a
Minor Recoverable
Fault
Controller card
Minor Unrecoverable
Fault
Description
Connect DeviceNet bus power
No errors detected during internal selftest
True, if one or more of the following errors have been detected during selftest of the FieldQ DeviceNet:
- EEPROM Checksum Error
True, if one of the following bits of the Monitor Object Instance Attribute 1
(Device status) is set and none of the bits listed in Major Recoverable Fault
is set:
- Bit 9 (Init running)
- Bit 14 (Init ok)
Not implemented
True, if one of the following bits of the Monitor Object Instance Attribute 1
(Device status) is set and none of the bits listed in Major Recoverable Fault
is set:
- Bit 15 (Init default)
n/a
Not implemented
True, if one of the following bits of the Monitor Object Instance Attribute 1
(Device Status) is set:
- Bit 1 (GMR error)
- Bit 2 (Temp sensor error)
Major Recoverable
Fault
- Bit 3 (System temp exceeded)
Controller card
- Bit 4 (Software error)
- Bit 7 (Unknown error)
- Bit 8 (Init bad repeatability)
- Bit 10 (Init stopped)
- Bit 11 (Init range error)
Major Unrecoverable
Fault
DeviceNet interface
board
- Bit 12 (Init timed out)
True if one or more of the following internal diagnostic Faults have been
detected:
- Receive Queue Overrun
- Transmit Queue Overrun
- CAN Controller Overrun
4.3
Message Router Object, Class ID 2 (02hex)
The Message Router Object provides a messaging connection point through which a client may address a service
to any object class or instance residing in the FieldQ DeviceNet Module.
Page 18
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.4
DeviceNet Object, Class ID 3 (03hex)
The DeviceNet Object is used to provide the configuration and status of physical attachment of the FieldQ DeviceNet module to DeviceNet network.
Table 4.4.1
DeviceNet Object Class Attributes
Attribute
Access Rule Name
ID
1
Get (NV-RO)
Table 4.4.2
Revision
3
4
Get (V-RO)
Get/Set (VRW)
Get/Set (VRW)
Baud Rate
BOI
USINT
Node Address
USINT
Baud Rate
Bus-Off Counter USINT
Get (V-RO)
BYTE
(NV-RW)
Table 4.4.3
Service
Code
0E(hex)
Number of times CAN went to the bus-off state
USINT
Enable Auto
Baud
BOOL
Semantics of
Value
2
Semantics of
Value
Range 0 – 63
Range 0 – 2
0 = 125 kBaud
1 = 250 kBaud
2 = 500 kBaud
See [2] Chapter 5-3
See [2] Chapter 5-3
See [2] Chapter 3-5
See [2] Chapter 5-3
MAC ID of Master
See [2] Chapter 5-3
Choice Byte
MAC ID
Get/Set
Bus-Off Interrupt
Allocation Infor- STRUCT
mation
of
Master’s
100
Revision of the DeviceNet Object Class Definition
Data Type Description of Attribute
BOOL
Allocation
5
UINT
DeviceNet Object Instance Attributes
Attribute
Access Rule Name
ID
1
Get (V-RO)
MAC ID
2
Data Type Description of Attribute
MAC ID
AutoBaud, Enable(Default);
Disable when manual setting the Baud Rate
Parameter
0 = Disable
1 = Enable (default)
DeviceNet Object Common Services
Class
Instance Service Name
yes
yes
Get Attribute Single
10(hex)
n/a
yes
4B(hex)
n/a
yes
Set Attribute Single
Allocate Master/Slave
Connection Set
4C(hex)
n/a
yes
Description of Service
Used to read the specified attribute value
Used to write the specified attribute value
Requests the use of the Predefined Master/Slave Connection
Set
Indicates that the specified Connections within the Predefined
Release Group 2 IdentiMaster/Slave Connection Set are no longer desired. These Confier Set
nections are to be released (Deleted)
Page 19
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.5
Assembly Object, Class ID 4 (04hex)
The Assembly Object binds attributes of multiple objects, which allows diagnostic data from the Monitor object to
be sent or received over a single connection.
Table 4.5.1
Implemented Instances of the Assembly Object
Instance ID
Type
Data Component Name
Size in bytes
100
Input
Input data (Monitor Object data)
26
Table 4.5.2
Assembly Object Class Attributes
Attribute
Access Rule
ID
1
Get (NV-RO)
3
Get (NV-RO)
Table 4.5.3
2
3
4
Data Type Description of Attribute
Revision
Number of
Instances
UINT
UINT
Assembly Object Instance Attributes
Attribute
Access Rule
ID
1
Semantics of
Value
Revision of the Assembly Object Class Definition 2
Number of object instances currently created at
1
this class level of the device
Name
Name
Data Type Description of Attribute
Number of
UINT
Members in List
ARRAY of
Member List
The member list is an array of DeviceNet paths
STRUCT
Member Data
UINT
Size of member
Description
Get (NV-RO)
Member Path
UINT
Size of Member Path
Size
See [1] Appendix C-1 for the format of these
Member Path
EPATH
fields.
ARRAY of
Get/Set (V-RW) Member Data
BYTE
Get (NV-RO)
Size
UINT
Number of bytes in Attribute 3
Semantics of
Value
Get (NV-RO)
Table 4.5.4
Size in bits
Size in bytes
Assembly Object Common Services
Service
Code
0E(hex)
Class
Instance
Service Name
Description of Service
yes
yes
Get Attribute Single
Used to read the specified attribute value
10(hex)
n/a
yes
Set Attribute Single
Used to write the specified attribute value
Table 4.5.5
FieldQ Input Assembly Instance 100
Assembly
Data
Class
Object
Component
ID Name
Instance ID
Name
101 Monitor
Instance Attribute
ID
ID Name
1
101 Monitor
10
Analog Input Point
Page 20
Input data
1
Device Status
UINT
3
Recognize unit status
USINT
3
Value
INT
8
Discrete Input Point
100
3
Value
BOOL1
8
Discrete Input Point
101
3
Value
BOOL1
101 Monitor
100
100
Data Type
1
4
Unscaled pos
UINT
100
3
Value
BOOL1
101 Monitor
1
8
Cycle Counter
UDINT
101 Monitor
1
5
Time in position
UDINT
101 Monitor
1
6
Open travel timer
UINT
101 Monitor
1
7
Close travel timer
UINT
101 Monitor
1
9
Average Open travel timer
UINT
101 Monitor
1
10 Average Close travel timer
UINT
9
Discrete Output Point
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.6
Connection Object, Class ID 5 (05hex)
The Connection Object Class allocates and manages the internal resources associated with both I/O and Explicit
Messaging Connections.
Table 4.6.1
Default Values of the Poll Connection
Attribute
Access Rule
ID
7
Get (NV-RO)
8
Get (NV-RO)
14
Get (NV-RW)
16
Get (NV-RW)
Table 4.6.2
Produced Connection Size
Consumed
Connection
Size
Produced Connection Path
Consumed
Connection
Path
Data Type Description of Attribute
7
Get (NV-RO)
8
Get (NV-RO)
14
Get (NV-RW)
16
Get (NV-RW)
Name
Produced Connection Size
Consumed
Connection
Size
Produced Connection Path
Consumed
Connection
Path
Semantics of
Value
UINT
Maximum number of bytes transmitted via this
Connection
Default = 26
UINT
Maximum number of bytes transmitted via this
Connection
Default = 1
EPATH
Specifies the Application Object(s) whose data is Default = {20 04
to be produced by this Connection Object
24 64 30 03}hex
EPATH
Specifies the Application Object(s) whose data is Default = {20 04
to be consumed by this Connection Object
24 65 30 03}hex
Default Values of the COS/Cyclic Connection
Attribute
Access Rule
ID
4.6.1
Name
Data Type Description of Attribute
Semantics of
Value
UINT
Maximum number of bytes transmitted via this
Connection
Default = 26
UINT
Maximum number of bytes transmitted via this
Connection
Default = 1
EPATH
Specifies the Application Object(s) whose data is Default = {20 04
to be produced by this Connection Object
24 64 30 03}hex
EPATH
Specifies the Application Object(s) whose data is Default = {20 04
to be consumed by this Connection Object
24 65 30 03}hex
Dynamic Explicit Message Connection Object Instances
Connection Object Instance ID ≥ 5 (05hex)
The FieldQ DeviceNet module is a Group-2-Server and does support the UCMM-Port to establish further Explicit
Messaging Connection with Connection Object Instance ID = 5 and ID = 6. It furthermore supports the establishment of one dynamic I/O Messaging Connection with Connection Instance ID 7.
Table 4.6.3
Connection Object Common Services
Service Code Class
Instance
Service Name
Description of Service
0E(hex)
yes
yes
Get Attribute Single
Used to read the specified attribute value
10(hex)
yes
yes
Set Attribute Single
Used to write the specified attribute value
05(hex)
yes
yes
Reset
Used to reset a connection.
09(hex)
yes
yes
Delete
Used to reset a connection.
Page 21
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.7
Discrete Input Point Object, Class ID 8 (08hex)
The Discrete Input Point Object is used to provide an interface to the "Open" and "Closed" feedback switches.
Table 4.7.1
Discrete Input Point Object Instances
Instance ID
Name
Source
1
Open State
Open status; 1=True; 0= False
2
Close State
Close status; 1=True; 0= False
Table 4.7.2
Discrete Input Point Object Class Attributes
Attribute ID Access Rule Name
Data Type
1
Get (NV-RO) Revision
3
Get (NV-RO)
Table 4.7.3
Number of
Instances
UINT
UINT
Description of Attribute
Revision of the Discrete Input Point Object Class
2
Definition
Number of object instances currently created at
2
this class level of the device
Discrete Input Point Object Instance Attributes
Attribute ID Access Rule Name
Data Type
Semantics of
Value
Description of Attribute
Semantics of
Value
Number of attributes supported in this product
3
2
Number of
USINT
Attributes
Get (NV-RO) Attribute List ARRAY of
List of attributes supported in this product
3
Get (NV-RO) Value
Input Point Value
1, 2, 3
0 = closed
1 = open
1
Table 4.7.4
Get (NV-RO)
BOOL
Discrete Input Point Object Common Services
Service Code Class
Instance
Service Name
Description of Service
0E(hex)
yes
yes
Get Attribute Single
Used to read the specified attribute value
10(hex)
n/a
yes
Set Attribute Single
Used to write the specified attribute value
Page 22
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.8
Discrete Output Point Object, Class ID 9 (09hex)
The Discrete Output Point Object is used to provide an interface to the pilot valve of the module.
Table 4.8.1
Discrete Output Point Object Instances
Instance ID
Name
Source
100
Open_Close_Cmd
FieldQ Command to open and close)
Table 4.8 2
Discrete Output Point Object Class Attributes
Attribute ID Access Rule Name
Data Type
1
Get (NV-RO) Revision
UINT
3
Number of
Get (NV-RO)
Instances
UINT
Table 4.8 3
Revision of the Discrete Output Point Object
Class Definition
Number of object instances currently created at
this class level of the device
Discrete Output Point Object Instance Attributes
Attribute ID Access Rule Name
Number of
Attributes
1
Get (NV-RO)
2
Get (NV-RO) Attribute List
3
Get/Set (NVValue
RW)
Table 4.8 4
Description of Attribute
Semantics of
Value
1
2
Data Type
Description of Attribute
Semantics of
Value
USINT
Number of attributes supported in this product
3
ARRAY of
USINT
List of attributes supported in this product
1, 2, 3
BOOL
Output Point Value
0 = Deactivate
Pilotvale
1 = Activate Pilotvalve
Discrete Output Point Object Common Services
Service Code Class
Instance
Service Name
Description of Service
0E(hex)
yes
yes
Get Attribute Single
Used to read the specified attribute value
10(hex)
n/a
yes
Set Attribute Single
Used to write the specified attribute value
Page 23
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.9
Analog Input Point Object, Class ID 10 (0Ahex)
Table 4.9 1
Analog Input Point Object Instances in case of FieldQ
Instance ID
Channel Interface Object
Source
100
Instrument Temp
Internal temperature of the Module
Table 4.9 2
Analog Input Point Object Class Attributes
Attribute ID Access Rule Name
Data Type
1
Get (NV-RO) Revision
3
Get (NV-RO)
Table 4.9 3
Number of
Instances
3
100
Table 4.9 4
UINT
Analog Input Point Object Instance Attributes
Attribute ID Access Rule Name
Number of
1
Get (NV-RO)
Attributes
2
UINT
Description of Attribute
Semantics of Value
Revision of the Analog Input Point Object
2
Class Definition
Number of object instances currently created
1
at this class level of the device
Data Type
USINT
ARRAY of
Get (NV-RO) Attribute List
USINT
Get (NV-RO) Value
INT
Temperature
Get (V-RO)
USINT
Unit
Description of Attribute
Number of attributes supported in this
product
List of attributes supported in this product
Semantics of Value
3
1, 2, 3
Analog Input Value
Range -128 to +127
Switch Between degree Celsius and degree 0 = Degree Celsius
Fahrenheit
1 = Degree Fahrenheit
Discrete Output Point Object Common Services
Service Code Class
Instance
Service Name
Description of Service
0E(hex)
yes
yes
Get Attribute Single
Used to read the specified attribute value
10(hex)
n/a
yes
Set Attribute Single
Used to write the specified attribute value
Table 4.9 5
Analog Input Point Object Instance Services
Service Code Class
Instance
Service Name
32(hex)
n/a
yes
Switch Celsius
33(hex)
n/a
yes
Switch Fahrenheit
Page 24
Description of Service
Used to set unit of the Value attribute to degrees Celsius
Used to set unit of the Value attribute to degrees Fahrenheit
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.10
Acknowledge Handler Object, Class ID 43 (2Bhex)
Table 4.10 1
Acknowledge Handler Object Class Attributes
Attribute ID Access Rule Name
Data Type
1
Get (NV-RO) Revision
2
Get (NV-RO) Max Instance UINT
Table 4.10 2
UINT
Description of Attribute
Revision of the Acknowledge Handler Object
1
Class Definition
Maximum instance number of an object currently
1
created in this class level of the device
Acknowledge Handler Object Instance Attributes
Attribute ID Access Rule Name
Data Type
Description of Attribute
1
Get/Set (VRW)
Acknowledge
UINT
Timer
Time to wait for acknowledge before resending
2
Get/Set (VRW)
Retry Limit
Number of Ack Timeouts to wait before informing the producing application of a RetryLimit
Reached event.
3
Get/Set (VRW)
COS Producing Connec- UINT
tion Instance
4
Get (V-RO)
5
Get (V-RO)
6
Get (V-RO)
7
Get (V-RO)
Table 4.10 3
USINT
Ack List Size BYTE
BYTE
Ack List
ARRAY of
UINT
Data with
Ack Path List BYTE
Size
BYTE
Semantics of
Value
Semantics of
Value
Range 1-65535
ms
(0 invalid)
Default = 16
Range 0-255
Default = 1
Connection Instance which contains the path of Default = 4
the producing I/O application object which will be (COS/Cyclic
notified of AckHandler events.
I/O Connection)
Maximum number of members in Ack List
Default = 1
List of active connection instances which are
receiving Acks.
Default = {01 04
00} hex
Maximum number of members in Data with Ack
Path List
Default = 1
List of connection instance/consuming applica- Default = {01 04
ARRAY of
Data with
tion object pairs. This attribute is used to forward 00 06 20 04 24 67
UINT
USINT
Ack Path List
data received with acknowledgment.
30 03 }hex
Padded
EPATH
Acknowledge Handler Object Common Services
Service Code Class
Instance
Service Name
Description of Service
0E(hex)
yes
yes
Get Attribute Single
Used to read the specified attribute value
10(hex)
n/a
yes
Set Attribute Single
Used to write the specified attribute value
Page 25
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.11
Controller Object, Class ID 100 (64hex)
Table 4.11.1
Controller Object Class Attributes
Attribute ID Access Rule Name
1
Data Type
Get (NV-RO) Revision
Table 4.11.2
Attribute ID
UINT
Semantics of
Value
Revision of the Controller Object Class Definition 1
Description of Attribute
Controller Object Instance Attributes
Access Rule
Name
OxA2C1 (ON/OFF
FieldQ)
Data Type
1
Get (V-RO)
2
Get/Set (V-RW) Open Switch Pos
USINT
3
Get/Set (V-RW) Close Switch Pos
USINT
4
Get (V-RO)
Open End Pos
UINT
5
Get (V-RO)
Close End Pos
UINT
6
Get (V-RO)
Software Action
USINT
8
Get (V-RO)
Production serial
number
ARRAY of
USINT
9
Get (V-RO)
Ctrl Firmware Rev
UDINT
10
Get (V-RO)
Shutdown Status
USINT
11
Get/Set (V-RW) Shutdown Setting
USINT
Semantics of Value
UINT
Range 5 - 30
Sets Offset to Open End Position
Range 5 - 30
Sets Offset to Close End Position
Range 0 - 1023
Initialized Open End Position
Range 0 - 1023
Initialized Close End Position
1 = Run (Normal)
3 = Restart with Defaults
4 = Restart Processor
Range 0 - 65535
Firmware Revision Level of Controller Card
0 = normal operation
1 = shutdown
0 = Enable auto recover
1 = Enable Manual recover
2 = Disable
Action on Internal Communication Loss
12
13
14
Get/Set (V-RW) Shutdown Action
Get/Set (V-RW) Shutdown Delay
Get/Set (V-RW)
Shutdown on DeviceNet
Communication Loss
USINT
USINT
BOOL
0 = close (default)
1 = open
2 = hold
Delay after Communication Loss before Shutdown Action
Range 0 – 255
Unit: seconds (Default 5 seconds)
Specifies whether DeviceNet communication
loss is mapped on internal communication loss
TRUE = shutdown
FALSE = no shutdown (default)
Page 26
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.11.1 Shutdown configuration
Internal communication loss is sensed on both the
Controller card and the DeviceNet interface board.
After Internal communication loss is sensed on the
DeviceNet interface board, the FieldQ behaves like
the Controller card does. This means:
1.Wait for a specific amount of time after Internal
communication loss occurred, specified in Shutdown delay.
2.If Shutdown setting is of value 0 (enable auto
recovery), auto recovery of Internal communication loss is done. If Shutdown setting is of value 1
(enable manual recovery), the FieldQ DeviceNet
waits for manual recovery. However, if Shutdown
setting is of value 3 (disable), no shutdown shall be
initiated.
Additionally, to indicate an internal communication
loss to the DeviceNet bus, bit 0 of Monitor Object
Instance Attribute 100 (Device status) is set.
DeviceNet communication loss is mapped on the
internal communication loss. The FieldQ DeviceNet
forces an internal communication loss event on both
the Controller card and the DeviceNet interface board
by stopping internal messaging.
4.11.3 Factory default Shutdown
configuration
Shutdown setting Enable, Manual Recovery
Shutdown action Close
Shutdown delay
5 seconds
4.11.4 Restart Processor Service
The Restart Processor Service resets both the processor on the Controller card and the processor on
the DeviceNet interface board.
Additionally, the Reset Service of the Identity Object
with Reset Type 0 is invoked.
4.11.5 Restart with default Service
The Restart with default Service resets both the
processor on the Controller card and the processor
on the DeviceNet interface board.
Additionally, the Reset Service of the Identity Object
with Reset Type 1 is invoked.
4.11.6 Buttonboard enable Service
The Buttonboard enable Service enables the Button
board.
4.11.7 Buttonboard disable Service
The Buttonboard disable Service disables the Button board.
4.11.8Shutdown reset status
The Shutdown reset status Service must be used
for a manual recovery. Manual recovery is required
when the Controller Object Instance Attribute 10
(Shutdown setting) is set to 1 (enable manual recovery). The Shutdown reset status Service will return
an Object State Conflict error when requested and
currently no manual recovery is required.
Default shutdown configuration
* Means that 5 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.
Page 27
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
Table 4.11.3
Service
Code
0E(hex)
10(hex)
Table 4.11.4
Service
Code
Controller Object Common Services
Class
Instance
Service Name
Description of Service
yes
n/a
yes
yes
Get Attribute Single
Set Attribute Single
Used to read the specified attribute value
Used to write the specified attribute value
Controller Vendor Specific Common Services
Class
Instance
Service Name
32
n/a
yes
Start auto init
33
34
35
36
37
38
39
40
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
yes
yes
yes
yes
yes
yes
yes
yes
Stop auto init
Open end position
Close end position
Restart processor
Restart with default
Buttonboard enable
Buttonboard disable
Shutdown reset status
Page 28
Description of Service
Start the auto initialization (Valve will
Move)
Stop the auto initialization
Initialized open end position
Initialized close end position
Restart the processor
Restart the processor with default
Enable the buttonboard
Disable the uttonboard
Status of Shutdown configuration
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
4.12
Monitor Object, Class ID 101 (65hex)
Table 4.12.1
Monitor Object Class Attributes
Attribute ID Access Rule Name
Data Type
Description of Attribute
1
UINT
Revision of the Monitor Object Class Definition
Get (NV-RO) Revision
Table 4.12.2
Semantics of
Value
1
Monitor Object Instance Attributes
Attribute ID Access Rule Name
Device
Status
Zero Pwr
Cond
Data Type
Description of Attribute
Semantics of
Value
WORD
Bit values for the Device status
See table 4.12.3
USINT
Position after power loss (Single Pilot Valve
Module)
1 = Open
0 = Close
1 = active (flashing)
0 = not active
1
Get (V-RO)
2
Get (V-RO)
3
Get/Set (VRW)
Flash Status
USINT
LED
4
Get (V-RO)
Unscaled
Pos
UINT
5
Get (V-RO)
Time in posiUDINT
tion
6
Get (V-RO)
Open travel
timer
UINT
7
Get (V-RO)
Close travel
timer
UINT
8
Get (V-RO)
9
Get (V-RO)
10
Get (V-RO)
11
Get (V-RO)
Cycle counter
Average
Open travel
timer
Average
Close travel
timer
Readback of
Command
to open and
close
Flash status LED of Device to identify module.
Feedback Value for Diagnostics
Range 0 to 1023
"Time in position (in seconds)
Holds the time in current position. Reset to zero Range 0 to 232-1
when power switched off"
"Open travel timer (in 10ms Ticks)
Indicates time between:
Range 0 to 216-1
- Pilot position change commanded and
- Open trip position reached."
"Close travel timer (in 10ms Ticks)
Indicates time between:
Range 0 to 216-1
- Pilot position change commanded and
- Open trip position reached."
UDINT
Number of Actuation Cycles Completed
Range 0 to 232-1
UINT
Average of 30 strokes of Open travel timer
(in 10ms Ticks)
Range 0 to 216-1
UINT
Average of 30 strokes of Close travel timer
(in 10ms Ticks)
Range 0 to 216-1
USINT
1 = Activate pilot
Readback of Command to open and close of the
0 = De-activate
selected FieldQ
pilot
4.12.1 Cycle Counter and Timers
Cycle Counter and Timers are available to set alarms
in the host system. For using these parameters and
setting the alarms, please refer to the documentation
of the host system.
Cycle Counter
A counter parameter is available for counting the
cycles of the control module.
Timers
There are 3 kind timers available in this device:
1 Time in position (ID5):
Records the time since the last movement.
It is reset to zero when the power is switched off.
2 Open travel time (ID6 & ID9)
- Indicates the time between:
When pilot valve position is changed and when
the Open trip position reached.
- Parameter Average Open travel timer calculates the average stroke time of the last 30
strokes.
Page 29
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
3 Close travel time (ID7 & ID10)
- Indicates the time between:
When pilot valve position is changed and when the Closed trip position reached.
- Parameter Average Close travel timer calculates the average stroke time of the last 30 strokes.
Average Open travel timer and Average Close travel timer Attributes
The Average Open travel timer and Average Close travel timer Attributes are processed on the DeviceNet interface board by means of building the arithmetic average of the Open travel timer and Close travel timer Attributes
over the last 30 movements. Until 30 movements occurred since the last power up, the average is built on all last
movements. If no movement has taken place, 0 (zero) is returned.
4.12.2 Device Status Attribute
The Device status Attribute is provided by a 16-bit word that contains the fields listed in Table 4.12.3.
Table 4.12.3 Bit values for the Device status Attribute
Bit
Description
0
Internal communications lost (set by DeviceNet firmware)
1
GMR error (= position feedback sensor error)
2
Temp sensor error
3
System temp exceeded
4
Software error
5
travel deviation
6
Shutdown set
7
Unknown error
8
Init bad repeatability
9
Init running
10
Init stopped
11
Init range error
12
Init timed out
13
n/a
14
Init ok
15
Init default
Furthermore, the general status of the device can be retrieved over the Identity Object Instance Attribute 5 (Status) and 8 (State).
Table 4.12.4 Monitor Object Common Services
Service
Code
0E(hex)
Page 30
Class
Instance
Service Name
Description of Service
yes
yes
Get Attribute Single
Used to read the specified attribute value
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
5.0
Basic DeviceNet l/O Operation
The FieldQ DeviceNet Control Module, QC31, operates as acombined discrete input and output device
on the DeviceNet network. It is a slave (server) device that can be allocated by the system implementer
to one specific master (client).
There are several parameters that may be modified
by the user. They may be left as defaulted, depending
on your requirements.
The Polled I/O feature follows the conventional method of a client requesting data from and/or sending
data to one server. This requires both a command
message from the client and a response message
from each server for every set of I/O.
To improve throughput on the network Change-ofState and Cyclic I/O functions have been defined by
the DeviceNet protocol. These functions are supported by the DeviceNet Control Module.
The discrete data returned in the poll response to the
client will contain both valve confact input and valve
command output status data.
5.1
Polled I/O
The client (master) can poll (read) the input and command the output status from the DeviceNet Control
Module and can energize or de-energize the discrete
outputs (operate the pilot valve) on the DeviceNet
Control Module.
5.2
Cyclic and Change-Of State I/O
The Cyclic connection initiates a transmission every
time the connection timer expires. The cyclic connection can only send data from the DeviceNet Control
Module or to it's assigned client.
The polled and cyclic connections are not exclusive,
so both can exist at the same time. The manner in
which cyclic connection reports its data is the same
as the polled connection.
The Change of State (COS) connection is the same
as the cyclic connection except that as well as triggering communications on the expiration of the timer,
the COS connection also initiates a transfer on a
change of the valve's status.
The COS connection:
- is mutually exclusive with the cyclic connection, but
can coexist with the polled connection.
- operation is very useful in conserving bandwidth,
and provides the client with the most current data
as fast or faster than apoll connection.
- automatically turns on the CDS mechanism when
the connection is created.
Page 31
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
Table 5.1 Poll Response (Input Data) Assembly Instance 100
Name
BYTE
7
2
Recognize unit
status
AI_Value
DI_Value
DI_Value
Position
DO_Value
Cycle Counter
Time in position
Open travel
timer
Close travel
timer
Average open
travel timer
Average close
travel timer
5
4
Bit Position
3
2
1
0
UnSoftSystem_
Internal communicaShutTravel_
Tem_sen- GMR_erknown_
ware_er- temp_extions lost (set by Devidown_set deviation
sor_error
ror
error
ror
ceeded
ceNet firmware)
Init_
Init_deInit_
Init_
Init_runInit_ok
n/a
range_erInit_bad_repeatability
fault
timed_out
stopped
ing
ror
1
Device Status
6
3
Active/not Active
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
LSB of Temperature
MSB of Temperature
Open State
Close State
LSB of Position
MSB of Position
Open_Close_Cmd
LSB of Cycle Counter
MLSB of Cycle Counter
MMSB of Cycle Counter
MSB of Cycle Counter
LSB of Time in position
MLSB of Time in position
MMSB of Time in position
MSB of Time in position
LSB of Open travel timer
MSB of Open travel timer
LSB of Close travel timer
MSB of Close travel timer
LSB of Average open travel timer
MSB of Average open travel timer
LSB of Average close travel timer
MSB of Average close travel timer
Table 5.2 Poll Request (Output Data) Assembly Instance 101
byte
1
Page 32
7
0
6
0
5
0
4
0
3
0
Bit position
2
Flash Status LED
1
start auto init
0
FieldQ command to open and close
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
Page 33
TM
Reference manual DeviceNet™ Control module
DOC.RM.QC31.E Rev: A7
March, 2010
Page 34
Reference manual DeviceNet™ Control module
TM
DOC.RM.QC31.E Rev: A7
March, 2010
Page 35
Contact Us: Emerson Process Management, Valve Automation facilities at your nearest location:
North & South America
18703 GH Circle
PO Box 508
Waller, Texas 77484
USA
T +1 281 727 5300
F +1 281 727 5353
2500 Park Avenue West
Mansfield, Ohio 44906
USA
T +1 419 529 4311
F +1 419 529 3688
9009 King Palm Drive
Tampa , Florida 33619
USA
T +1 813 630 2255
F +1 813 630 9449
4112-91A Street
Edmonton, Alberta T6E5V2
Canada
T +1 780 450 3600
F +1 780 450 1400
Av. Hollingsworth,325
Iporanga
Sorocaba, SP 18087-105
Brazil
T +55 15 3238 3788
F +55 15 3228 3300
Europe
Asveldweg 11
7556 BT Hengelo(O)
The Netherlands
T +31 74 256 1010
F +31 74 291 0938
30/36 Allee du Plateau
93250 Villemomble
France
T +331 48 122610
F +331 48 122619
6 Bracken Hill
South West Industrial Estate
Peterlee, Co Durham
SR82LS, United Kingdom
T +44 191 518 0020
F +44 191 518 0032
3 Furze Court
114 Wickham Road
Fareham, Hampshire
PO167SH ,United Kingdom
T +44 132 984 8900
F +44 132 984 8901
Via Montello 71/73
20038 Seregno
Italy
T +39 0362 2285207
Selska cesta 93
10000 Zagreb
Croatia
T +385 913654292
ul. Konstruktorska str 11A
02-673 Warsaw
Poland
T +48 22 4589237
Hungári körút 166-168
H-1146 Budapest
Hungary
T +36 14624034
Siemensring 112
D-47877 Willich
Germany
T +49 2154 499 660
F +49 2154 499 6613
Hajkova 2747/22
130 00 Praha 3
Czech Republic
T +42 2 81002666
Zelezniciarska 13
811 04 Bratislava
Slovakia
T +42 1252442071
Blegistrasse 21,
P.O. Box 1046
CH 6341 Baar
Switzerland
T +41 (41) 7686215
2-4, Gara Herastrau St.
District 2, Nova Building,
5th floor 020334 Bucharest
Romania
T +40 212062506
Icerenkoy MAh. Topcu Ibrahim
Sk.
No:13 K:4 Icerenkoy
Istanbul, Turkey
T +90 2165739848408
Middle East & Africa
2 Monteer Road, Isando
Kempton Park, 1600
South Africa
T +27 11 974 3336
F +27 11 974 7005
PO Box 17033
Jebel Ali Free Zone
Dubai,
United Arab Emirates
T +971 4883 5235
F +971 4883 5312
Asia Pacific
19, Kian Teck Crescent,
Singapore 628885
T +65 6501 4600
F +65 6268 0028
9/F Gateway Building
No.10 Ya Bao Road
Chaoyang District
Beijing, 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 400076
India
T +91 22 6662 0566
F +91 22 6662 0500
NOF Shinagawa Konan Building
1-2-5, Higashi-shinagawa
Shinagawa-Ku, Tokyo
140-0002 Japan
T +81 3 5769 6873
F +81 3 5769 6902
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.
©2011 Emerson Electric Co.
TM
www.FieldQ.com