AUMA AUMATIC AC 01.2 User manual

Actuator controls
AUMATIC AC 01.2/ACExC 01.2
Foundation Fieldbus
Device integration FieldbusManual

Read operation instructions first.
●Observe safety instructions.
Purpose of the document:
This document contains information for the commissioning staff of the distributed control system and DCS software
engineers.This document is intended to support the actuator integration into the DCS via fieldbus interface.
Reference documents:
●Operation instructions (Assembly, operation, commissioning) for actuator
●Manual (Operation and setting) AUMATIC AC 01.2 Foundation Fieldbus
Reference documents can be downloaded from the Internet (www.auma.com) or ordered directly from AUMA
(refer to <Addresses>).
Table of contents Page
41. Safety instructions................................................................................................................. 41.1. Basic information on safety 41.2. Range of application 51.3. Warnings and notes 51.4. References and symbols
62. General information regarding Foundation Fieldbus......................................................... 62.1. Performance features 72.2. Layered communications model 82.3. Physical layer 82.3.1. H1 bus 92.3.2. High Speed Ethernet (HSE) 92.3.3. Connection between H1 and HSE 92.3.4. Data transmission and power supply 92.4. Communication stack 102.4.1. Link Active Scheduler - LAS 102.4.2. Communication control 102.4.3. Services 112.5. Application layer 112.5.1. Block model 122.5.2. Device descriptions 122.5.3. System management 132.5.4. System configuration 132.6. Topology
163. Commissioning...................................................................................................................... 163.1. Introduction 163.2. Network configuration 163.2.1. Tag and device address 183.2.2. Link master parameter setting 183.2.3. Scheduling parameter setting 183.3. Function blocks 193.3.1. Operation commands 223.3.2. Feedback signals from AUMATIC actuator controls 233.3.3. Function block parameter setting
2
Actuator controls
Table of contents AC 01.2/ACExC 01.2 Foundation Fieldbus

444. Corrective action.................................................................................................................... 444.1. Troubleshooting
455. Technical data......................................................................................................................... 455.1. Foundation Fieldbus interface
486. Appendix................................................................................................................................. 486.1. Status signals of the transducer blocks including XD_ERROR und XD_ERREXT error variable
coding 496.2. Selection for RESTART parameter of Resource Block 496.3. Block operation modes 506.4. IO_OPTS, availability and description 516.5. CONTROL_OPTS, availability and description 516.6. STATUS_OPTS, availability and description 536.7. Proposed wiring diagram for external sensors, 2-wire technology 546.8. Proposed wiring diagram for external sensors, 3-wire technology 556.9. Proposed wiring diagram for external sensors, 4-wire technology
56Index........................................................................................................................................
58Addresses...............................................................................................................................
3
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus Table of contents

1. Safety instructions
1.1. Basic information on safety
Standards/directives AUMA products are designed and manufactured in compliance with recognised
standards and directives.This is certified in a Declaration of Incorporation and a EC
Declaration of Conformity.
The end user or the contractor must ensure that all legal requirements, directives,
guidelines, national regulations and recommendations with respect to assembly,
electrical connection, commissioning and operation are met at the place of installation.
They include among others applicable configuration guidelines for fieldbus
applications.
Safetyinstructions/warn-
ings All personnel working with this device must be familiar with the safety and warning
instructions in this manual and observe the instructions given. Safety instructions
and warning signs on the device must be observed to avoid personal injury or property
damage.
Qualification of staff Assembly, electrical connection, commissioning, operation, and maintenance must
be carried out exclusively by suitably qualified personnel having been authorised by
the end user or contractor of the plant only.
Prior to working on this product, the staff must have thoroughly read and understood
these instructions and, furthermore, know and observe officially recognised rules
regarding occupational health and safety.
Commissioning Prior to commissioning, it is important to check that all settings meet the requirements
of the application. Incorrect settings might present a danger to the application, e.g.
cause damage to the valve or the installation.The manufacturer will not be held
liable for any consequential damage. Such risk lies entirely with the user.
Operation Prerequisites for safe and smooth operation:
●Correct transport, proper storage, mounting and installation, as well as careful
commissioning.
●Only operate the device if it is in perfect condition while observing these instruc-
tions.
●Immediately report any faults and damage and allow for corrective measures.
●Observe recognised rules for occupational health and safety.
●Observe the national regulations.
●During operation,thehousing warms upandsurface temperatures>60°Cmay
occur.To prevent possible burns, we recommend to the check surface temper-
ature with an appropriate thermometer prior to working with device and to wear
protective gloves, if required.
Protective measures The end user or the contractor are responsible for implementing required protective
measures on site, such as enclosures, barriers, or personal protective equipment
for the staff.
Maintenance Any device modification requires the consent of the manufacturer.
1.2. Range of application
AUMA actuator controls are exclusively designed for the operation of AUMA actuators.
Other applications require explicit (written) confirmation by the manufacturer.The
following applications are not permitted, e.g.:
●motor control
●pump control
No liability can be assumed for inappropriate or unintended use.
Observance of these operation instructions is considered as part of the device's
designated use.
4
Actuator controls
Safety instructions AC 01.2/ACExC 01.2 Foundation Fieldbus

1.3. Warnings and notes
The following warnings draw special attention to safety-relevant procedures in these
operation instructions, each marked by the appropriate signal word (DANGER,
WARNING, CAUTION, NOTICE).
Indicates an imminently hazardous situation with a high level of risk. Failure
to observe this warning could result in death or serious injury.
Indicates a potentially hazardous situation with a medium level of risk.Failure
to observe this warning could result in death or serious injury.
Indicates a potentially hazardous situation with a low level of risk. Failure to
observe this warning may result in minor or moderate injury.May also be used
with property damage.
Potentially hazardous situation. Failure to observe this warning may result in
property damage. Is not used for personal injury.
Arrangement and typographic structure of the warnings
Type of hazard and respective source!
Potential consequence(s) in case of non-observance (option)
→Measures to avoid the danger
→Further measure(s)
Safety alert symbol warns of a potential personal injury hazard.
The signal word (here: DANGER) indicates the level of hazard.
1.4. References and symbols
The following references and symbols are used in these instructions:
Information The term Information preceding the text indicates important notes and information.
Symbol for CLOSED (valve closed)
Symbol for OPEN (valve open)
Important information before the next step.This symbol indicates what is required
for the next step or what has to be prepared or observed.
Via the menu to parameter
Describes the path within the menu to the parameter. By using the push buttons of
the local controls you may quickly find the desired parameter in the display.
< > Reference to other sections
Terms in brackets shown above refer to other sections of the document which provide
further information on this topic.These terms are either listed in the index, a heading
or in the table of contents and may quickly be found.
5
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus Safety instructions

2. General information regarding Foundation Fieldbus
For theexchangeof information amongautomation systemsand betweenautomation
systems and the connected distributed field devices, the use of serial fieldbus systems
as communication system is state-of-the-art.Thousands of applications have proved
impressively that, in comparison with conventional technology, cost savings of up to
40 % in wiring, commissioning, and maintenance are achieved by using fieldbus
technology.While in the past the fieldbus systems used were often manufacturer
specific and incompatible with other bus systems, the systems employed today are
almost exclusively open and standardized.This means that the user does not depend
on individual suppliers and can choose within a large product range the best product
at the most competitive price.
Historical development In 1992, an international group, the ISP (Interoperable Systems Project) was founded
with the intention to create an internationally uniform fieldbus standard for use in
hazardous environments. At the same time, the manufacturers and users of the
French FIP (Flux Information Process;previously:Factory Instrumentation Protocol)
establishedtheinternational userorganisationWorldFIP.Togetherwith theFIP North
America, they were a strong counterweight to the ISP consortium. In 1994, for
technical, economic, and political reasons, the ISP and the WorldFIP merged to form
the Fieldbus Foundation.The aim of the Fieldbus Foundation was and is to create
a single, international fieldbus standard for hazardous environments which will find
widespread use as IEC standardised fieldbus.
User organisation The Fieldbus Foundation is an independent non-profit organisation.The mission is
to develop and support a global, uniform fieldbus infrastructure for automation tasks
–the Foundation Fieldbus.Members include users and manufacturers of field devices
and automation systems.The Fieldbus Foundation contains various workshops
which are responsible, among others, for technical support, marketing, and support
of the members.Website of the Fieldbus Foundation: www.fieldbus.org.
Certification of the
devices This fieldbus is an open fieldbus standard which enables devices of different
manufacturers to be integrated in one system and, if required,ensures their
interchangeability (interoperability).This is only feasible when all devices exactly
meet the specification. If the devices are approved by Fieldbus Foundation, this
implies a guarantee for the user and manufacturer that those devices comply with
the specification.
2.1. Performance features
The Foundation Fieldbus provides a broad spectrum of services and functions
compared to other fieldbus systems:
●Bus-powered field devices
●Line or tree topology
●Deterministic (predictable) dynamic behaviour
●Distributed data transfer (DDT)
●Standardised block model for uniform device interfaces (interoperability, inter-
changeability)
●Trend functions and alarm treatment
●Flexible extension options based on device descriptions
●Intrinsic safety for use in hazardous areas (option)
Decentralised process
data processing The distributed data transmission within the Foundation Fieldbus network enables
individual field devices to independently perform automation tasks via standardised
function blocks.If a field device contains e.g.the PID function block, it is able to
independently control a process variable.This automation decentralisation from the
automation to the field level relieves the central process control.
6
Actuator controls
General information regarding Foundation Fieldbus AC 01.2/ACExC 01.2 Foundation Fieldbus

Figure 1:Typical Foundation Fieldbus structure
HSE FF bus based on high speed Ethernet
H1 FF bus based on H1
LD Linking device
PC Power Conditioner (FF H1 power supply)
Actuator controls with function blocks:
PID Process controller
AO Analogue output (valve setpoint)
AI Analog Input (e.g.flow rate measured by sensor)
2.2. Layered communications model
The structure of Foundation Fieldbus is based on the ISO/OSI reference model
(International Standards Organisation - Open Systems Interconnection).This model
consists of 7 layers.Foundation Fieldbus just uses three layers:
●Layer 1: Physical layer
●Layer 2: Data link layer
●Layer 7: Application layer
As is the case for many other bus systems, layers three to six are not used. Layer
7 is subdivided into a Fieldbus Access Sublayer (FAS) and a Fieldbus Message
Specification (FMS).The Communication Stack covers the tasks of layers 2 and 7.
The special feature of Foundation Fieldbus is the device-dependent application layer,
placed above the 7th layer.Whereas the actual application process is not determined
for the ISO/OSI model, the Fieldbus Foundation defines a special application layer.
This layer contains a block model with function block and a device description (DD).
Depending on which blocks are implemented in the block model of a device, users
can access a variety of services.
Thus, the Foundation Fieldbus specification consists of 3 main function elements:
●Physical layer
●Communication stack
●Application layer
7
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus General information regarding Foundation Fieldbus

Figure 2:
2.3. Physical layer
The lowest bus level, the physical layer, is based on IEC standard 61158-2.This
layer defines how the physical connection to the fieldbus network as well as the data
transmission are to be performed.
Foundation Fieldbus uses two systems for the communication.The low H1 version
for communication and direct connection of the field devices, the fast HSE version
based on Industrial Ethernet within the DCS and for connecting Remote Operations
Management (ROM) systems.
2.3.1. H1 bus
The following summary gives a brief overview of the features and functions of the
H1 bus. For detailed information, refer to the various Application Guides of the
Fieldbus Foundation (e.g. AG-140, AG-163, AG-181, FD-043).
●Data transfer: Manchester coding
●Data transfer rate 31.25 kbit/s (default setting, cannot be modified).
●Requirements for perfect communication: Sufficient power supply for the field
devices, i.e.minimum 9 volts for each device. Software tools are available for
network planning, calculating the resulting currents and terminal voltages on
the basis of network topology, the cable resistance, and the supply voltage.
E.g. DesignMATETM, available via www.fieldbus.org.
●Field device connection via H1 version.The Foundation Fieldbus Power Condi-
tioner is connected to the bus line in the same way (parallel) as a field device.
Field devices supplied by additional supply sources have to be connected to
these sources as well.
●The maximum power consumption of current consuming devices within H1
networks must be lower than the electric power supplied by the Foundation
Fieldbus Power Conditioner.
●Network topologies: Line topology;when using junction boxes or segment bar-
riers, also star, tree or a combination of these topologies.
●Device connections:Typically via short spurs to enable connection/disconnection
of the devices without impairing communication to other users.
●Maximum length of a spur: 120 m, depending on the number of spurs used as
well as the number of devices per spur.
8
Actuator controls
General information regarding Foundation Fieldbus AC 01.2/ACExC 01.2 Foundation Fieldbus

●Maximum cable length of an H1 segment without repeater: 1,900 m.
●Maximum cable length of an H1 segment using maximum 4 repeaters:5 x 1,900
m = 9.5 km.
All spurs from the field devices to the junction boxes have to be included in the
total length calculation.
●Number of field devices per segment: In non-intrinsically safe areas: Max. 32,
in explosion-hazardous areas, this number is reduced to significantly fewer
devices (due to power supply limitations).Based on the available H1 bandwidth,
the typical number of devices per segment is, however, max. 10 –14 devices
per segment.
●Fieldbus cable:Type A (recommended), only this type is specified for the
maximum segment length of 1,900 m.
●Termination:Two terminators per bus segment, typically one at each end of
the longest fieldbus cable.
●Bus cable shielding:If shielded cables are used (recommended), the shield is
typically only earthed at one single point within the segment (typically near the
Foundation Fieldbus power supply).Apart from this, other earthing philosophies
are available (refer to AG-181).
2.3.2. High Speed Ethernet (HSE)
HSEis basedon standardEthernet technology.The requiredcomponentsare widely
used and are available at comparatively low costs.The HSE data transfer speed
runs at 100 Mbit/s and can be equipped with both copper cables and optical fibre
cables.The Ethernet operates by using random (not deterministic) CSMA bus access.
This method cannot be applied to all automation applications, as for some parts,
real-time requirements have to be met.The extremely high transmission rate enables
the HSE to respond sufficiently fast when the bus load is low and only few devices
are connected.With respect to process automation demands, real-time requirements
are nevertheless met in any case.
If the bus load must be reduced due to the multitude of connected devices, or if
several HSE sub networks are to be combined to create a larger network, Ethernet
switches must be used. A switch reads the target address of the data packets that
must be forwarded and then passes the packets on to the associated sub network.
This way, the bus load and the resulting bus access time can be controlled to best
adapt it to the respective requirements.
2.3.3. Connection between H1 and HSE
To connect the comparatively slow H1 segments to the HSE network, linking devices
(connecting devices) are required (refer to figure "Typical Foundation Fieldbus
structure" in chapter "Performance features").
The linking device adapts the data transfer rates and the data telegrams of both
networks while considering the direction of transmission.This way, powerful and
widely branched networks can be installed in larger plants.
2.3.4. Data transmission and power supply
Within the Foundation Fieldbus network, a device transmitting data typically varies
the power consumption by ±10 mA at 31.25 kbit/s to generate a typical ±0.5 V
voltage change for power supply with a 50 Ohm impedance.This voltage variation
is modulated onto the 9 –32 V DC H1 power supply.
2.4. Communication stack
The field devices used with Foundation Fieldbus are capable of independently
assuming automation tasks, i.e.:
●Each field device can directly exchange data with other devices (e.g.reading
measuring values, forwarding control values).
●All field devices send and receive data at pre-defined points in time.
●Specific mechanism ensure that never two or more devices simultaneously
access the bus.
9
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus General information regarding Foundation Fieldbus

To meet these requirements, the Foundation Fieldbus needs a central communication
control system (Link Active Scheduler = LAS).
2.4.1. Link Active Scheduler - LAS
A field device performing the Link Active Scheduler (LAS) function controls and
schedules the bus communication. It controls all bus activities by means of specific
data telegrams that it sends to the available devices.Since the LAS also continuously
polls unassigned device addresses, it is possible to connect devices during operation
and to integrate them in the bus communication.
Devices which can be used as LAS are called Link Master Devices (LM).Basic
devices (BD) do not have LAS capacity.
In a redundant system containing several link master devices, only one link master
takes over the LAS task.If the active LAS device fails, another link master device
will take over (fail-operational design).
The LAS ensures both updating and continuous transmission of the Live List to all
other Link Master Devices. If a device is removed from or added to the list, the LAS
transmits this change to all link master devices (broadcast message).This way, all
link masters have access to the current live list so that they can become the LAS
without any loss of information, if required.
2.4.2. Communication control
The communication services of the FF specification define both scheduled and
unscheduled data transmission.Time-critical tasks, such as the control of process
variables, are exclusively performed by scheduled services, whereas programming
and diagnostic functions are carried out using unscheduled communication services.
Scheduleddata transmis-
sion To solve communication tasks in time and without access conflicts, all time-critical
tasks are based on a defined transmission schedule.The pertaining definitions are
created by the Foundation Fieldbus system operator during the configuration of the
FF system.
The LAS periodically broadcasts a time synchronisation signal (TD:Time Distribution)
on the fieldbus so that all devices have exactly the same data link time.In scheduled
transmission, the point in time and the sequence of data telegrams are defined in
detail.
For this reason, the FF H1 system is also called deterministic fieldbus system.
For each action to be performed (e.g. execution of a function block or transmission
of a process value), a defined period is added to the schedule.Based on this
schedule, a transmission list is generated which defines when a specific field device
is prompted to send its data.Upon receipt of a special trigger telegram (CD:Compel
Data), the respective device (publisher) broadcasts the data in the reception buffer
of all devices which are configured to receive this data (subscriber).
This type of transmission is therefore called the “publisher-subscriber”method.
Unscheduled data trans-
mission Device parameters and diagnostic data are typically only transmitted when needed,
i.e.on request.The transmission of this data is not time-critical. For such
communication tasks, the Foundation Fieldbus offers unscheduled data transmission.
Permission for a certain device to use the fieldbus for unscheduled communication
tasks is granted by the LAS device, provided that no scheduled data transmission
is active.
Every device may use the bus as long as required until it either returns the bus
access right (token), or until the maximum granted time to use the token has elapsed.
Unscheduled transmission offers two data transmission methods:“Client Server”to
adapt device settings, configuration upload/download of diagnostic data as well as
"Report Distribution" to send alarms.
2.4.3. Services
The Fieldbus Access Sublayer (FAS) and the Fieldbus Message Specification (FMS)
layer form the interface between the data link layer and the user application (refer
to figure 2).The services provided by both FAS and FMS are invisible for the user.
10
Actuator controls
General information regarding Foundation Fieldbus AC 01.2/ACExC 01.2 Foundation Fieldbus

However, performance and functionality of the communication system considerably
depend on these services.
Fieldbus Access Sublay-
er (FAS) The FAS services createVirtual Communication Relationships (VCR) which are used
by the higher-level FMS layer to execute its tasks.VCRs describe different types of
communication processes and enable faster processing of the associated activities.
Foundation Fieldbus communication uses the three different VCR types as follows
(refer to table).
Publisher/SubscriberReport DistributionClient/server Process data transmissionEvents, alarms, trendsUser communication Transfer process values of
sensors and other devices
Send process alarms to user
consoles, transmitting trend
data for long term data logging
Setpoint changes, operating
dataand devicedata changes,
upload/download, alarm value
adaptation, remote dia-
gnostics. ScheduledUnscheduledUnscheduled
The Publisher/Subscriber VCR type is used to transmit the input and output data of
function blocks.As described above, scheduled data transmission is based on this
type of VCR.
The Client/ServerVCR type is the basis for operator initiated requests, such as
setpoint changes, adaptations and change of control parameters, diagnostics, device
upload, and download, etc.
Report Distribution is used to send alarms or event notifications to the user console
or similar devices. Client/Server and Report Distribution data transmission is
unscheduled, due to the fact that the time of transmission cannot be foreseen and
therefore not be scheduled.
Fieldbus Message Spe-
cification (FMS) The FMS provides the services for standardised communication.Data types that are
communicated via the fieldbus are assigned to certain communication services.For
uniform and clear assignment, object descriptions are used. Object descriptions
contain definitions of all standard transmission message formats as well as
application-specific data. Special, predefined communication services are available
for each object type.
Object descriptions are collected together in a structure called an object dictionary.
2.5. Application layer
An important criterion for a fieldbus system to be accepted by the market is the
interoperability of the devices.Interoperability characterises the capability of devices
of different manufacturers to communicate with each other. In addition, it must be
ensured that a device from one manufacturer can be substituted with that of another.
This requires an open protocol specification which defines uniform device functions
and application interfaces. Other network users and application programs can use
these interfaces to access the functions and parameters of the field devices.The
Foundation Fieldbus meets these requirements by means of standardised function
blocks and device descriptions.
2.5.1. Block model
Foundation Fieldbus assigns all functions and device data to three different types of
blocks:
●Resource block
●One or several function blocks
●Several transducer blocks
Resource block The resource block describes characteristics of a fieldbus device, e.g.device name,
manufacturer, serial number, hardware and firmware version, etc.
Function blocks Function blocks describe the device functions and define how these can be accessed.
The charts of scheduled data transmission are based on these function blocks.Each
11
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus General information regarding Foundation Fieldbus

block (including the pertaining inputs and outputs) has a definite task.Each FF device
is equipped with at least one function block.
The FF specification provides defined function blocks which can be used to describe
the typical functions.They are listed below:
Analog InputAI Analog OutputAO Discrete InputDI Discrete OutputDO Proportional/integral/derivativePID Signal CharacteriserSC Input SelectorIS
Transducer blocks Transducer blocks enhance the application options of a device.Their data enables
the input and/or output parameters of a function block to be influenced. Measuring
and positioning data can be calibrated and reset, characteristics can be linearised
or physical units can be reset using additional process data.
Further objects Besides the three block types, the following additional objects are defined within the
block model:
Link objects define the connections between different function blocks, both internal
to the field device as well as across the fieldbus network.
Alert objects allow reporting alarms and events on the fieldbus.
Trend objects allow trending function block data for access and analysis from
higher-level systems.
View objects are predefined groupings of data and block parameter sets that can be
used to group and display the parameters according to their tasks: Process control,
configuration, maintenance and additional information.
2.5.2. Device descriptions
During start-up and maintenance as well as when performing diagnostic functions,
an open communication system must ensure that higher-level control computers or
control systems can access all field devices and that respective controls are available.
The device descriptions (DDs) contain the necessary information to fulfill these
requirements.They provide all information needed to understand the meaning of the
device data and display them correctly on the operator console.
2.5.3. System management
The system management of each device has the following tasks:
●Synchronisation of device activities in compliance with the predefined transmis-
sion schedule
●Cyclical processing of transmission list (LAS only) within the predefined
schedule.
Further tasks performed by the system management:
●Automatic assignment of LAS function to another Link Master if the active LAS
fails.
●Synchronisation of clock information
●Automatic address assignment for new devices within the communication net-
work
The automatic assignment of a provisional device address allows the assignment of
a clear and unambiguous device address at the commissioning during active
communication.For this address assignment procedure, special default addresses
are reserved allowing to access the new devices which are not yet configured.A
new device is integrated in the communication network after assigning a device tag
as well as a new, clear, unambiguous node address.The default address used is
then available again for the assignment of further devices, still due to be configured.
12
Actuator controls
General information regarding Foundation Fieldbus AC 01.2/ACExC 01.2 Foundation Fieldbus

2.5.4. System configuration
Scheduled communication as well as all fieldbus devices must be configured before
their first start-up (refer to figure below).This requires a configuration tool, e.g. the
NI-FBUS Configurator by National Instruments.
Figure 3:
1 Configuration device
2 Configurating basic devices
3 Configurating LAS and link master
Prior to the actual commissioning, the Device Descriptions (DD) for all devices to be
configured must be entered using configuration tools.The configuration software
must either be able to access the device descriptions in the available libraries, or
the device descriptions must be loaded via external data storage devices.
The configuration software helps to determine how and with which devices the
measurement and control tasks of a plant are processed by connecting the function
blocks of the field devices.This task can be performed using a graphical user
interface.For this, just connect inputs and outputs of the corresponding block symbols
and define the block behaviour.
The figure below shows an example of a filling level control.The sensor output value
is connected to a PID function block.This block can be provided e.g. by actuator
controls.The subsequent analogue output acts on the actuator positioner for filling
level control by means of the valve.
Figure 4:
2.6. Topology
Several structures are available for Foundation Fieldbus:
Point-to-point topology, whereby only one device is connected to each line.
13
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus General information regarding Foundation Fieldbus

Bus with spurs; for this structure, the fieldbus devices are connected to the bus
segment via spurs.
Line topology; for this structure, the fieldbus cable of a segment is led from device
to device and connected to the terminals of each fieldbus user. Due to the AUMA
plug/socket connector, installationswith AUMA actuatorsimplementing thistopology
can easily and individually be disconnected from the network without impairing the
availability of the remaining segment.
Tree topology;for this structure, the devices of one fieldbus segment are connected
to a common junction box via separate fieldbus cables.The maximum spur length
must be observed when implementing this topology. It is furthermore possible to
combine the topology options mentioned.
Die genannten Topologieoptionen können auch kombiniert werden.
Figure 5:
1 DCS
2 Trunk
3 Spurs
JB Junction Box
Spurs or tee connectors are possible for Foundation Fieldbus.The possible fieldbus
line length is determined by the type of cable, the cross section, and the type of the
bus supply.
Cable length = trunk length + total spur length
Maximum length = 1,900 metres with cable type A
By using up to four repeaters, a maximum of 5 x 1,900 m = 9,500 m can be achieved.
A terminator is to be installed at both ends of the main trunk.
Permissible spur lengthNumber of devices Permissible spur length for one device per
spur - any further device reduces the permiss-
ible spur length by 30 metres
The number of devices possible on a fieldbus
depends on the power consumption of
devices, the type of cable used, the use of re-
peaters, etc.For details please refer to Phys-
ical Layer Standard. 1 m25 –32 30 m19 –24 60 m15 –18 90 m13 –14 120 m1 –12
14
Actuator controls
General information regarding Foundation Fieldbus AC 01.2/ACExC 01.2 Foundation Fieldbus

For details regarding the different topology options, please refer to the Application
Guides published by Fieldbus Foundation:
AG-140 31.25 kbit/s Wiring and Installation
AG-163 31.25 kbit/s Intrinsically Safe Systems
AG-170 Function Block Capabilities in Hybrid/Batch Applications
AG-181 System Engineering Guidelines
Bus cables Various types of fieldbus cables can be applied for Foundation Fieldbus.The following
tableliststhe cable typesspecified bytheIEC/ISA61158-2 PhysicalLayer Standard.
Type A is the preferred fieldbus cable.This cable should be used in new installations.
However, other cable types may be used for the fieldbus wiring (e.g type B, C, and
D).Their disadvantage is the reduced cable length; therefore, their use is not
recommended.
Table 1:Bus cables
Type DType CType BType A
(Reference) Multiple twis-
ted pairs, not
shielded
Multiple twis-
ted pairs, not
shielded
One or mul-
tiple twisted
conductor
pairs, overall
shield
Twisted con-
ductor pair
Cable design
1.25 mm2
(AWG 16)
0.13 mm2
(AWG 26)
0.32 mm2
(AWG 22)
0.8mm2(AWG
18)
Cross section
(nominal) 40 Ω/km264 Ω/km112 Ω/km44 Ω/km
Loop resistance
(DC current) Not specifiedNot specified
100 Ω
±30 %
100 Ω
±20 %
Impedance
at 31.25 kHz 8 dB/km8 dB/km5 dB/km3 dB/kmWave attenuation
at 39 kHz Not specifiedNot specified2 nF/km2 nF/kmCapacitive asymmetry Not specifiedNot specifiedNot specified
1.7 μs/km
Group delay distortion (7.9 –
39 kHz) Not specifiedNot specifiedNot specified90 %Degree of shield coverage 200 m400 m1,200 m1,900 m.Recommended network ex-
pansion (incl. spur lines)
15
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus General information regarding Foundation Fieldbus

3. Commissioning
3.1. Introduction
AUMATIC controls with Foundation Fieldbus are commissioned via the fieldbus
network.This includes both PD tag and device address setting as well as configuration
of the function block application.
3.2. Network configuration
This section contains information on how to adapt AUMATIC actuator controls to
fieldbus network requirements.
3.2.1. Tag and device address
Before connecting devices with Foundation Fieldbus, PD Tag (Physical Device Tag)
and device addresses must be assigned.
The PDTag is an identifier used for the device.Up to 32 alpha-numerical characters
can be used for data entry.
Address ranges
The device address is used to identify devices during communication.The valid
address range is between 16 and 247 (0x10hex and 0xF7hex).Link master devices
are assigned lower addresses, basic devices higher addresses. An appropriate
address range is available for each of these device types.
The AUMATIC can be placed within both ranges: within the basic device range or
within the link master device range.The factory setting for the AUMATIC is to start
with address 247 (0xF7hex) and as basic device. If the AUMATIC is to be operated
as link master device, the MIB parameter BOOT_OPERAT_FUNCTIONAL_CLASS
has to be changed from 0x01 (BASIC) to 0x02 (LM). After this, the AUMATIC has
to be rebooted.
Information The device with the lowest address within the link master devices range adopts the
LAS function.
The following parameters for address range setting should be adapted:
DescriptionParameters First unpolled node;the highest address which can be assigned to a link master
device is V(FUN) –1.
V(FUN)
Number of unpolled nodes; here, the gap of unused consecutive addresses is
defined.The first address which can be assigned to basic devices is V(VUN)
+ V(NUN).
V(NUN)
Devices within the ‘Unused’address range are excluded from communicating via
Foundation Fieldbus, because the LAS does not periodically check this range for
new devices.V(FUN) and V(NUN) parameters have to be adapted according to the
addresses assigned within the Foundation Fieldbus network, the "unused" range
should be selected in a way to ensure that the LAS does not unnecessarily poll the
addresses of devices, not being connected.
16
Actuator controls
Commissioning AC 01.2/ACExC 01.2 Foundation Fieldbus

Figure 6:
Tag and device address setting
A Foundation Fieldbus Device can take on three states.If the state does not
correspond to the SM_OPERATIONAL state, no function block will be executed
Figure 7:
AUMATIC default setting:
PD tag: AUMA AC 01.2
Address: 247 (0xF7hex).
If two AUMATIC actuator controls are connected to the same address within the
same Foundation Fieldbus network, one of the controls keeps the address assigned,
whereas the other device uses a default address (from 248 [or 0xF8hex] to 251 [or
0xFBhex]).
Change the device ad-
dress: 1. Delete the address (CLEAR_ADDRESS).
2. Assign new, unused address (SET_ADDRESS).
Change the PD tag: 1. Delete address and PD tag.
2. Then, assign again PD tag and address.
Devices for which the address has been deleted will wait within the default address
range for a new setting (randomly chosen from a range of 248 (or 0xF8hex) to 251
(or 0xFBhex).At the same time, the device ID must be known to clearly identify the
device.The worldwide unique device ID for the AUMATIC is
0A01FF0001WorksNoxSerialNo.
17
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus Commissioning

3.2.2. Link master parameter setting
To ensure stable communication, different parameters must be observed and adapted
to the connected link master devices.When setting the parameters in compliance
with table 16, the largest value of all devices connected to the same Foundation
Fieldbus network must be used.
Link master parameters of the AUMATIC:
DescriptionParametersSymbol Time necessary for an immediate device response (unit:
1/256 µs). For the AUMATIC, set value ≥8.
Slot TimeV(ST)
Minimum time between two data telegrams (unit:1/256 µs).
For the AUMATIC, set value ≥6.
Minimum Inter
PDU Delay
V(MID)
Maximum time permissible for a response (unit: slot time
(V(ST));
For the AUMATIC, set value ≥5.
Maximum Re-
sponse Delay
V(MRD)
3.2.3. Scheduling parameter setting
The process application is assembled using and combining function blocks.The
scheduling of the connected function blocks is precisely defined during configuration
of the function block application.
The combined blocks have to be executed simultaneously with other blocks within
the communication schedule.Communication synchronisation is performed via the
LAS.
The MACROCYCLE_DURATION parameter is used to define the cycle time of the
devices connected to the network.
MACROCYCLE_DURATION specifies the macrocycle duration.The unit of this
parameter is 1/32 ms and the default value for the AUMATIC is 32000 (0x7D00hex
= 1 s).This value can be optimised, if required.
3.3. Function blocks
Input and output parameter of function blocks can be connected to perform the
automation task via Foundation Fieldbus.
The AUMATIC contains the following function blocks:
DescriptionCodeUnits Resource BlockRB21 Analog Input function blockAI4 Discrete Input function blockDI10 Analog Output function blockAO2 Discrete Output function blockDO8 Process Controller function blockPID1 Signal Characteriser function blockSC1 Input Selector function blockIS1 Analog Input transducer blockAITB1 Discrete Input transducer blockDITB1 Discrete Output transducer blockDOTB1 Analog Output transducer blockAOTB1 Positioner Transducer Block (transducer block for controlling the ac-
tuator)
PTB1
AUMA Commissioning Transducer Block (transducer block for com-
missioning and parameter setting)
AUMACTB1
AUMA DiagnosisTransducer Block (Transducer Block for diagnostics)AUMADTB1
Each Discrete Input function block is connected to a common Discrete Input
transducer block.
Each Analog Input function block is connected to a common Analog Input transducer
block.
18
Actuator controls
Commissioning AC 01.2/ACExC 01.2 Foundation Fieldbus

Depending on the channel configuration, the Discrete Output function block and the
Analog Output function block are either connected to the Positioner Transducer
Block, the Analog Output transducer block or the Discrete Output transducer block.
For the PID function block, the IS function block, the SC function block and the RB2
function block, no transducer blocks are required.
Figure 8: Function blocks
3.3.1. Operation commands
Operation of AUMA actuators with AUMATIC controls via Foundation Fieldbus can
be performed via the Analog Output function block (AO) for setpoint operation
commands or, alternatively, via the Discrete Output function block (DO) for OPEN -
STOP - CLOSE commands.
Typically, actuators are either exclusively operated via an analog setpoint operation
command of the Analog Output function block (AO) or, as an alternative, via binary
OPEN - CLOSE operation commands of the Discrete Output function blocks (DO).
Depending on the selected channel of the function block (CHANNEL parameter),
received operation commands will either be processed by the PositionerTransducer
Block (PTB), the Discrete OutputTransducer Block (DOTB) or the Analog Output
Transducer Block (AOTB), allowing for further settingssuch asdynamic change-over
between an analog setpoint command and binary OPEN - CLOSE operation
commands.
Information As the actuator may be controlled via different channels (CHANNEL parameter),
certain restrictionsapply for CHANNELparametersetting irrespectiveof thefunction
block used.They will be described in detail for commissioning of the respective
function blocks.
Operation commands via Analog Output function block
The AO function block accepts setpoints between 0 and 100 %.
A setpoint of 0 % signifies that the actuator fully closes, a setpoint of 100 % signifies,
that the actuator fully opens.
The integral PID function block can be used as controller function block to reduce
the number of required externalVCRs.This is not imperative.The PID function block
can be integrated within another external device, e.g.the DCS;however, an additional
VCR is then required for feedback from the AO to the PID.
For setpoint control via an Analog Output function block (AO), the setpoint signal is
typically forwarded to the Positioner Transducer Block.In this case, the AO can
provide additional information on the actual position and the actuator status and
therefore on the availability of the AO, when using the backward path (BKCAL_OUT).
19
Actuator controls
AC 01.2/ACExC 01.2 Foundation Fieldbus Commissioning

Figure 9:Typical control via Analog Output function block
As an alternative, the setpoint signal can also be sent via the Analog Output
transducer block. An additional Discrete Output function block then controls the
change-over between setpoint operation command and binary OPEN - CLOSE
commands.When using the above configuration, the AO will only provide the received
setpoint via its backward path (BKCAL_OUT), but no further feedback on actuator
position or actuator status.
Figure 10: Alternative control via Analog Output function block with operation com-
mand change-over via Discrete Output function block
Operation commands via Discrete Output function block
For binary control using a Discrete Output function block (DO), binary 8-bit operation
commands are typically also forwarded to the Positioner Transducer Block. In this
case, the DO provides the received operation commands via its backward path
(BKCAL_OUT_D), but also additional feedback on the actuator status and therefore
on the availability of the DO.
20
Actuator controls
Commissioning AC 01.2/ACExC 01.2 Foundation Fieldbus