Post on 28-Nov-2015
transcript
Fieldbus Foundation™Freedom to choose. Power to integrate
New NAMUR Recommendations
Sven Seintsch
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Prepared by: NAMUR-Working group 2.6 „Feldbus“
Part 1NAMUR Recommendation „NE 105“Specifications for Integrating Fieldbus Devicesin Engineering Tools for Field Devices
Part 2NAMUR Recommendation „NE 107“Requirements regarding self-monitoring anddiagnosis in field instrumentation
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
• Introduction• Scope of the NAMUR Recommendation• Long-Term Viability of the Device Integration• User Interface Specification and Style Guide• Functional Specifications for Device
Connections and Interfaces for Device DataProcessing
• Certification• Result
NAMUR Recommendation „NE 105“Specifications for Integrating Fieldbus Devicesin Engineering Tools for Field Devices
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Introduce of the NAMUR Recommendation
Field buses and field devices that are suitable for usein the chemical industry are commercially available.From a user’s perspective, one has to summarize thedevice integration specifications, despite thestandardization of buses and the permanent progressmade in establishing data transfer rules.
The main focus lies on life cycle management:• Make sure that complex Automation systems can be
maintained without undue effort over a productionplant’s life cycle
• a view to adopting version update frequencies that donot impede technological progress
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Existing Integration methods forField devices
Engineering- , Configuration- or Maintainace- tool
GSDInterpreter
(E)DDInterpreter
HCF DDInterpreter
ASCII Datei
(E)DD HCFDD
GSD
FDT-Container
DeviceDTM
DeviceDTM
Descriptions Data: Software driver:
+ Operating system independent + implementation of complex functions
+ unified User interface - depend on Operating system
- Complex functions different to implement - Device specific user interface
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Objective of the NAMURRecommendation
• This NAMUR Recommendation lays out thespecifications for uniform user interfaces, thefunctionality of device connections and forconfiguration tool interfaces for the processing ofdevice data.
• The goal is to be able to efficiently and safelyoperate, parameterise and manage the data ofdevices from various manufacturers with auniform tool.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Long-Term Viability of Device Integration
Investment Safety
Investments must be safeguarded by a clear and stable interfacebetween the application and operating system.
Specifications:• New field device with a new device description No operating system updates required
• New version of the operating system No change of device description required
• New version of the device integration tool
No change of operating system or device description required
The Device integration just as one part of the automation system shouldnot decrease the live cycle of the complete system
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Version Conflicts
Long-Term Viability of DeviceIntegration
Device descriptions must be upward and downwardcompatible for integration.
Device DescriptionConfiguration Tool
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
User Interface Specifications &Style Guide
• Integration of Devices Integration of DevicesA standard procedure for the integration of newdevices must be established. It must be compatiblewith all modes of communication (HART, FF, DP,PA, etc.).
• User GuidanceUniform user guidance must be provided for everycomponent regardless of the manufacturer or typeof device. Key features must be made available in aclearly defined manner.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
User Interface Specifications
Representation of devices• Operating concepts and the user interface employed
to configure and diagnose field devices must sharea uniform structure.
• A difference must be made between standardfeatures and parameters (e.g. measurement limitsettings) of various device types (e.g. measurementtransmitters) and manufacturer specific featuresand parameters (e.g. extended diagnostic features).
• Display methods used for standard parameterscomponents as well as the grouping of standardparameters and nomenclature must be determineduniformly for al manufactures.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Functional Specifications for DeviceConnections and Interfaces for DeviceData Processing
• Device DescriptionsEach field device may only have one device description, whichshould work without requiring changes to every tool (acrossmanufactures)
• Licensing of Device DescriptionsThe device description and the device form a functional unit.The device description is an integral component of the deviceand therefore cannot be licensed separately.
• Cross-Platform CompatibilityDevice descriptions must be compatible with all versions ofthe computer’s operating system.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Functional Specifications for DeviceConnections and Interfaces for DeviceData Processing
• Full Support of Device FunctionalityDevice descriptions should allow one to access all of thedevice’s parameters and features. One should also considerusing graphical images (shell curves, characteristic curves,etc.) to simplify operation.
• Standardized Data FilingInconsistencies between sets of parameters, which often occurin various systems (control systems, device parameterisationtools, asset management systems, etc.) should be avoided byadopting a uniform data structure and filing strategy, with acentral storage space.
• Storing of parameter datasets by name and version number
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Certification
• User interfaceCompliance with established user guidance anddevice mapping criteria must be ensured.(Certification process)
• FunctionalityA mechanism must be devised to ensure thatsystem and field device suppliers can guaranteethat their products work. The mechanism shouldcomply with manufacturer-independent certificationstandards that ensure interoperability and cross-version compatibility.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Result
• The existing integration methods do not matchcomplete the recommendations in the NE 105.
• Future device technology with higher functionality and faster version changes in the device technology or IT World will cause a non containable situation, if the presented requirements are not solved.
• Manufactures/Foundations are called to react with proper moves, otherwise the user acceptance of the technology is endangered.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Requirements regarding self-monitoring anddiagnosis in field instrumentation
NAMUR Recommendation „NE 107“
Part 2
• Diagnose
• History
• Experience
• Result
• User requirements
(Author: Dr. Zobel)
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
• Process technology ↔ automotivetechnology
Who needs whichDiagnostic Information ?
• Information to Operator/Driver:• All information needed for save driving• No needless information• As soon as possible
DiagnosisInformation
Operator/Driver
Process Plant/automobile
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Who needs whichDiagnostic Information ?
work shop diagnosis tool: 773 Diagnostic codes !
• Information to work shop laborer:• As detailed as possible• includes proposals for solution
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
A Beginning: Diagnostic structureNAMUR 64
Organization into 3 status signals:• Failure:
– Due to a malfunction at the field equipment or atits periphery the output signal is invalid.
• Function control:– On the field equipment one works, the measuring
signal is temporarily invalid therefore.• Maintenance Required:
– The measuring signal is still valid, but the wearsupply will shortly be exhausted.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Status byte in the Fieldbustechnique(256 Stati)
00Hex bis 1FHex Messwert „BAD“
40Hex bis 59Hex Messwert „UNCERTAIN“
60Hex bis 63Hex Messwert „UNCERTAIN“
64Hex bis 67Hex Messwert „UNCERTAIN“
80Hex bis A7Hex Messwert GOOD (NON CASCADE)
C0Hex bis E7Hex Messwert GOOD (CASCADE)
Positioner:Additional information by checkback bits
84hex
Failure
Maintenance
Funktion control
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Diagnostic transmission withFoundation Fieldbus
TransducerBlock
ResourceBlock
BlockError
BlockError
Status information visualized,acyclic readable
Analog InputBlock
AbnormalActive
Maske
BADActive
No Yes
BlockError
Status information visualized,cyclic readable
StatusByte
Classify statusInformation !
Switch !
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
– No manufacturer-spreading classification ofdiagnostic massages
– Classification of diagnosis messages according toNAMUR 64 only device-specifically
– High developing costs (driver, alarm system)
– Announcement of the status signals over colorchanges
• → good acceptance in factory
– Differentiated diagnosis:• → possible with Fieldbus
Result: Diagnostics with Fieldbus
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
– Application specific: error messages not to bedisabled(Pressure measuring cell overpressure, measuringtube empty, …)
– Reporting gush with start-up
– Not all messages are classifiable:Measuring tube not completely filled, to high solidpart, electronics temperature too highly, …
– DCS or vendor specific diagnostic not useable formulti vendor plants
Result: Diagnostics with Fieldbus
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
• Standardization of all diagnostic messages into fourstatus signals
- 4. Status signal “Out of Specification”- Fine partitioning of the 4 status signals possible
• Allocation of the diagnostic messages to the statussignals must take place in the field instrument→ Independence from DCS !
• Suppression of individual diagnostic messages in theequipment
• Diagnostics must take place in real time!
• interoperability for all devices• independent from the technical transmission (PA / FF / Hart / ..)
User Requirements
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
User RequirementsNE 107
Requirements regarding self-monitoring anddiagnosis in field instrumentation
Cyclic diagnosis from the Device
• structured: failuremaintenance requestfunction controlout of specification (New)
• reliable• internal• just in time
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
failure
• Def.: “Ausfall” (F = failure)
Due to a malfunction at the field equipmentor at its periphery the output signal isinvalid.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
maintenance request
• Def.: “Wartungsbedarf”(M = maintenance request)
The measuring signal is still valid, but thewear supply will shortly be exhausted.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
check
• Def.: “Funktionskontrolle”(C = check)
On the field equipment one works, theMeasuring signal is therefore temporarilyinvalid.
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
out of specification
• Def.: “außerhalb der Spezifikation”(S = out of specification)
The Device is used out of it´s spez. Rangeor
– Deviation cursed by internal Problemsor
– Process characteristics
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
- better planning of maintenanceno needless maintenance
- more confidence into the measured valueless examination
- longer time between service checks
Profit
2005 General AssemblyVienna, Austria
Copyright Fieldbus Foundation, February 2005
Thank you
for your attention