1
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Lars MickanSofting AG
Fieldbus Foundation – India Marketing Committee
Fieldbus FoundationParadigm Change in Instrumentation Technology
FF Software / Hardware device integration
Date : 26th of September, 2008 (Friday) Time : from 09:00 am to 06:00 pm. Venue : Automation 2008 Conference Hall.
: Conference Hall, Bombay Exhibition Centre (NSE), Goregaon (East), Mumbai INDIA
2
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Structure
- Introduction – Motivation
- Requirements on Field Devices Integration
- Hardware Solutions for FF Interface
- Software Solution MODBUS/HART mapping
- Ready-made Example of FF Interface
- Summary
3
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Structure
- Introduction – Motivation
- Requirements on Field Devices Integration
- Hardware Solutions for FF Interface
- Software Solution MODBUS/HART mapping
- Ready-made Example of FF Interface
- Summary
4
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Introduction – Motivation
- Foundation Fieldbus Technology is a Standard in Process Automation
- Still other „old“ fashion technology's (4..20mA or HART) available in the market
- How will it possible to use current field device hardware with advantages of FF ?
5
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Structure
- Introduction – Motivation
- Requirements on Field Devices Integration
- Hardware Solutions for FF Interface
- Software Solution MODBUS/HART mapping
- Ready-made Example of FF Interface
- Summary
6
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Requirements on Field Devices Integration
- Hardware development of FF interface
- Adaptation of communication stack to new hardware
- Integration of application software
- Electrical conformance test (EMC, Ex, Physical layer)
- CTK, ITK and host conformance tests
7
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Step 1:License hardware schematics and develop fieldbus Interface hardware including ex requirements
Step 2:Produce Prototypes and submit them to stack supplierStack supplier implements stack and function blocks
Step 3:Integration of device application and connection to devicePre-certification
Step 4:Final tests and product launchCertification
today
4-6 months
6-9 months
App.12 months
Project Schedule –„Traditional way“
8
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Required Test of new Fieldbus Hardware
Physical Layer Test- Test of fieldbus hardware based on requirements of physical layer of
Foundation fieldbus- A successful test is necessary to get a device certification
CTK Conformance Test - Based on FOUNDATION fieldbus conformance test kit- Will be done by test lab of Frauenhofer ITB in Karlsruhe
ITK Interoperability Test - Test of interoperability to other FOUNDATION fieldbus devices- Will be done by test lab of FOUNDATION fieldbus in Austin
Proven application with to major host systems
9
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Project Schedule –„Rapid way“
Today: Step 1:
1-2. month Step 2:
3-4. month Step 3:
Submit specification of service application (e.g. HART-Commands)
Hardware integrationCustomizing of software and templatesConfiguration files generation
Precertification (only ITK necessary)DeliveryCertification to follow
10
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Comparison of different Approaches
-++++RapridApproach
++----Traditional Approach
Device CostSystem Performance
Development Time
Development Cost
11
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Structure
- Introduction – Motivation
- Requirements on Field Devices Integration
- Hardware Solutions for FF Interface
- Software Solution MODBUS/HART mapping
- Ready-made Example of FF Interface
- Summary
12
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
FF Interface Solution - Scenario #1
Sensor / ActuatorBoard
HARTInterface
Existing Field DeviceNew Field Device
Sensor / Actuatorand FF Module
one board – one processor
„Traditional“ way of Field Device Integration
- One Processor System- Design of new PCB (Schematics)- Re-run of all certification test
13
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
FF Interface Solution - Scenario #2
Sensor / ActuatorBoard
HARTInterface
Existing Field Device
Sensor / ActuatorBoard
New Field Device
FF Interface Module
„Rapid“ way of Field Device Integration by using serial interface
- Using of Actor / Sensor board- Serial communication MODBUS RTU- Only ITK certification test necessary
14
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
FF Interface Solution - Scenario #3
Sensor / ActuatorBoard
HARTInterface
Existing Field Device
Sensor / ActuatorBoard
HARTInterface
New Field Device
FF Interface Module
„Rapid“ way of Field Device Integration by using HART interface
- Using of Actor / Sensor board- Mapping of HART commands to FF- Only ITK certification test necessary
15
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Summary of the Scenarios
--+++Scenario #3Rapid wayHART Interface
-++-Scenario #2Rapid waySerial Interface
+++----Scenario #1Traditional way
Device CostSystem Performance
Development Time
Development Cost
16
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Structure
- Introduction – Motivation
- Requirements on Field Devices Integration
- Hardware Solutions for FF Interface
- Software Solution MODBUS/HART mapping
- Ready-made Example of FF Interface
- Summary
17
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
FF Interface Solution – MODBUS/HART
The FF interface module has to have a built in MODBUS rsp. HART Master-Slave communication module
Modbus / HART handling supports the following communication strategies:
- cyclic read, cyclic write- acyclic read, acyclic write
To do:- Define Modbus locations / HART commands- Define access pattern (cyclic / regular / acyclic) for
transactions
18
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Modbus / HART Scheduler
Acyclic command Cyclic commands Regular commands
Request List
read process value read parameter Aread parameter Bread parameter D
write parameter C
read process valueread parameter A
read process value
write parameter Cread process valueread parameter B
FF Interface Solution – MODBUS/HART
19
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Structure
- Introduction – Motivation
- Requirements on Field Devices Integration
- Hardware Solutions for FF Interface
- Software Solution MODBUS/HART mapping
- Ready-made Example of FF Interface
- Summary
20
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
FF Interface Solution – Block DiagramX2
Fieldbus
IEC61158-2 H1Fieldbus Foundation
Digital Unit
Micro Controller M16C
Fieldbus ControllerUFC100
MAU
Medium Attachment Unit
Protection
FBK
I2C memory interface
Jumper
configurable IO
DI/DO/AI/AO
6.3VPower Output
3.15VPower Output
Serial Interface
M16C Progamming
Interface
X1User
Interface
21
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Low Power Design – Intrinsic safety
- FOUNDATION fieldbus is able to provide power over bus
- 2- or 4-wire designs are possible
- The available bus power depends on different conditions (devices, cable, …)
- Lower total power consumption:Less development efforts regarding intrinsic safeLess effort for bus or power cablingLess hardware cost (cheaper components, design without galvanic isolation)
22
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Fieldbus Kit FBK2 - Example of FF Interface- Easy FF integration of existing field devices
with HART- or serial interface
- Compact size makes it ideally suited for installation in most existing device housings
- Pre-certified for hazardous areas (ATEX certificate)
- Connection to field device via: UART, I²C or SPI
- Programmable AI/AO and DI/DO
- Ready-made templates allow quick customization to HART commands
23
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Structure
- Introduction – Motivation
- Requirements on Field Devices Integration
- Hardware Solutions for FF Interface
- Software Solution MODBUS/HART mapping
- Ready-made Example of FF Interface
- Summary
24
© 2008 Fieldbus Foundation
2008 FFIMC - Automation 2008-Mumbai
Summary
- Any traditional field devices can become a FF field device
- A ready-made FF interface can reduce the development and test efforts
- Software adaptation for device specific commands will be still necessary
- Pre-Certified FF interface hardware is available