Device Revisions

1

Device Revisions Management Best Practices -

Is DD the problem or the solution?

Jonas Berge, Director, Applied

Technology

Emerson Process Management

Photography & Video Recording Policy

Photography and audio/video recording is not permitted in any

sessions or in the exhibition areas without press credentials or

written permission from the Emerson Exchange Board of Directors.

Inquiries should be directed to:

2

Inquiries should be directed to:

EmersonExchange@Emerson.com

Thank you.

Presenters

� Jonas Berge

3

Introduction

� Keeping the system up to date with new types and

versions of devices is a challenge in most plants– 4-20 mA/HART

– WirelessHART

– FOUNDATION fieldbus

– PROFIBUS

� The role of Device Description (DD) files in interoperability

and compatibility often misunderstood

4

and compatibility often misunderstood– How to manage DD in projects

– How to keep the system up to date with intelligent devices

� Relevant to:– Users of Emerson devices on Emerson systems

– Emerson devices on third-party systems

– Third-party devices on Emerson systems benefit alike

Topics Covered

� Device Integration and Compatibility

� Basics

� Versioning and File Names

� Troubleshooting

� System Files

� Poor Hosts

� Project Execution Considerations

5

� Project Execution Considerations

� Plant Operations & Maintenance

� Training for Competency

6

Device Integration and Compatibility

Devices get better and better,

how does the system keep up?

Intelligent Digital Devices Require Software Integration

Eight-channel two-wire

temperature transmitter Intelligent two-wire on/off valve

7

Fully integrated gas

chromatograph

Intrinsically safe intelligent two-

wire inventory tank gauging

system

Electric actuators / Motor

Operated Valve (MOV)

Plant Challenge: Device Revisions

� It is not a problem with DD file, it is a DEVICE “problem”:– Manufacturers constantly release new revisions of devices with

new features

� 4-20 mA (HART), FOUNDATION fieldbus, PROFIBUS,

and WirelessHART devices periodically have new

versions

� 4-20 mA devices use HART for configuration and

8

� 4-20 mA devices use HART for configuration and

calibration– Therefore device revision is a challenge for 4-20 mA devices too

Ver 1 Ver 2 Ver 3 Ver 4

Solution: The IEC 61804-3 (EDDL) Device Integration Technology

� The EDDL file is in the computer

� There is no EDDL in the device– There is no such thing as an “EDDL device” or “non-EDDL device”

� The EDDL file describes the device so the computer

knows how to talk to the device– EDDL is a device integration technology

� All systems use the same EDDL file for the device

9

� All systems use the same EDDL file for the device

� There is no need to upgrade the system software version

to match the device version

Backwards and Forwards Compatibility Provided by EDDL

� Backwards compatible:– Thanks to EDDL, new software and handhelds work with old

devices

� Forward compatible:– Thanks to EDDL, software and handhelds will work with future

devices without software upgrade

10

Rev 1 Rev 2 Rev 3 Rev 4

Old

Devices

Future

Devices

Pre-loaded EDDL files for old devices Load EDDL files for new devices in the future

Forward CompatibilityBackwards Compatibility

New

System

How EDDL Works

� The EDDL file is made by the device manufacturer

� The EDDL file lets the system know the features of

each device

� EDDL files keep the system up to date with new

devices

� New system and handhelds have EDDL files pre-

loaded

EDDL file

DEV_REV

= 1

11

loaded

� Load EDDL files for new devices in the future

� Any system or handheld works with any device type

� All devices can be managed from the same software

EDDL file

•Transmit

•Receive

•Display

DEV_REV

= 2

DEV_REV

= 3

Same Technology, Same Procedures

� Keep systems up to date and compatible with new

devices by loading the DD file for the device onto system

� EDDL works the same way for HART, WirelessHART,

FOUNDATION fieldbus, and PROFIBUS– Know one, and you know them all

� 4-20 mA devices use HART for configuration and

calibration; need EDDL to be commissioned

12

calibration; need EDDL to be commissioned

New Skills Required

� EDDL files are downloaded from the Internet and loaded

on the system– In 1996 this was totally new

� In the past, people in general were not as used to using

software, downloading files from the Internet, and

synchronizing with devices– Everyday MP3 players, digital cameras, smart phones, and tablets

13

– Everyday MP3 players, digital cameras, smart phones, and tablets

have now changed this

� Software, downloading files, and synchronizing with smart

devices is becoming second nature

14

Device Revision Management Basics

In a nutshell...

Device Revision Management is Simple

� If a new revision of a device is received, obtain the EDDL

file for that device revision and load on the system

� For instance, if a revision 7 device arrives in the plant, get

a DD file for device revision 7

� That is all you need to know– The rest of this workshop is just details

15

Common Misunderstanding

Wrong

� “What is the DD revision

of the device?”– This is not right because the

device does not know about

DD files

– The DD is not inside the

device

Right

� “What is the device

revision of the device”

� “What device revision is

this DD file used for?”

16

device

System and Handheld Update

� Download EDDL file:– Device manufacturer site

– Bus organization (HCF, FF, PI) site

– System supplier site• Together with system files

– Automatic update

� Small– Via email even on low bandwidth connection

17

– Via email even on low bandwidth connection

� Copy and paste– Document, not software

– Add device wizard

475 Easy Update

� The field communicator is ahead in usability

� Utility software updates communicator with its device

support files– No search for files on multiple websites

� Makes 4-20 mA/HART devices easy to use– Systems that don’t use HART don't need EDDL files

18

Guardian Automatic System Update- DeltaV/AMS v12

� DeltaV and AMS Device Manager automatically

download new DD files from the Guardian server

� The system is automatically kept up to date, ready

for new device types and versions as they come to

the plant– No need to search for files

� Upgrade to DeltaV/AMS v12

19

� Upgrade to DeltaV/AMS v12

Manual File

Transfer or

Network

Connection

EDDL Files for All Devices Managed The Same Way

� EDDL files are loaded the same way for 4-20 mA (HART)

and Fieldbus devices

EDDL File

4-20 mA (HART Device)

Fieldbus Device

20

� System is kept up to date with HART, FOUNDATION

fieldbus, PROFIBUS, and WirelessHART devices the

same way

� 4-20 mA devices use HART and therefore need EDDL file

to be loaded

Fieldbus DeviceHART

Fieldbus

21

Versioning and File Names

Keeping the system evergreen

The Problem:- Device Versions Get Better

� A new revision device has new features– New function blocks

– New parameters (setup, diagnostics, monitoring)

– New options (units, sensor types, etc.)

� The system must know the features of every revision of

every device

22

DEV_REV = 1

Device (HART, FF, PROFIBUS, WirelessHART)

AITB

DEV_REV = 2 AI PIDTB

Plugged Impulse Line

DEV_REV = 3 AI PIDMass

FlowTB

Auto Tuning

mmH2O @ 4 degC

Version Management (for Device)

� Problem: A new revision

device has new features– New function

– New diagnostics

– New options

� Solution: Therefore a new

EDDL file is required to

describe those new device

features– Old files are not removed

23

DEV_REV = 1

DEV_REV = 2

DEV_REV = 3

Corresponds To:

Device (HART, FF, PROFIBUS, WirelessHART)

Corresponds To:

Corresponds To:

EDDL file

DEV_REV = 1

DEV_REV = 2

DEV_REV = 3

Version Management (for EDDL file)

� New EDDL released even if there is no change in device

revision– For example to improve the EDDL file

• Easier to use wizards

• More intuitive menus

• Better graphics

• Conditionals

• Clearer help text

24

• Clearer help text

� When there is a new DD file for the same device revision,

this is when we get a new “DD revision”

DEV_REV

= 1

DEV_REV

= 2

Works With

Device (HART, FF, PROFIBUS, WirelessHART) EDDL File

Works With

DEV_REV = 1

DD_REV = 1

0101.sym

DEV_REV = 1

DD_REV = 2

0102.sym

DEV_REV = 2

DD_REV = 1

0201.sym

Recap: DD Revision is Different from Device Revision

Device Revision

� Version of the device

� Incremented when

firmware is improved with

new features– New blocks

– New features

DD Revision

� Version of the user

interface, the file itself

� Incremented when the

user interface is improved

with new features– Better graphics

25

– New features

– New diagnostics– Better graphics

– Smarter wizards

– More helpful conditionals

– More intuitive menus

(HART, FF, PROFIBUS, WirelessHART)

Device Revision is What Matters

� The Device Revision for the EDDL file must match the

device revision of the actual device– Otherwise the system cannot work with the new device

� This applies to 4-20 mA (with HART), FOUNDATION

fieldbus, PROFIBUS, and WirelessHART alike

� The system does not care much about the DD revision of

the device

26

the device– The system usually picks the latest available DD file for the device

Understanding EDDL File Names

� The DD file names consist of:– Device revision

– DD file revision

� Hexadecimal

� Old files not removed when new files are loaded

� The system automatically picks the correct EDDL file for

the device to be displayed

27

the device to be displayed

0701.sym

07 = Device Revision 7

01 = DD File Revision 1

1703.sym

17 = Device Revision 23 (17 in hexadecimal is 23 in decimal)

03 = DD File Revision 3

Device Library and Add Device Wizard

� Lists all supported device

types and revisions– That is, all the EDDL files

loaded on the system

� Plain text model numbers

and descriptions

� Organized by manufacturer

28

� Organized by manufacturer

and protocol

Plug-‘n’-Play

� System automatically picks

the correct EDDL file– No manual configuration

29

(HART, FF, PROFIBUS, WirelessHART)

•Manufacturer ID

•Device Type

•Device RevisionREAD

30

Poor Host

Early days of DD

DD/EDDL Support in Systems

� All systems support DD

� In the past, not all systems supported wizards (methods)

and conditionals– Some systems required “simplified” DD to work

� Enhanced menus and graphics was not introduced until

2006– Compliant systems must now implement full support

31

– Compliant systems must now implement full support

Device

Definition

Business

Logic

User Interface

Description

•Blocks

•Parameters

•Wizards

•Conditionals

•Menus

•Graphics

EDDL

Modified CFF

� Most systems just ignore unsupported features in the CFF

file– Can use CFF from the device supplier as-is

� Some systems reject CFF file with unsupported content– System manufacturer edits the CFF file to make the system accept

it

– The original CFF file from the device manufacturer does not work

32

33

System Files

Host System Interoperability

Device Files vs. System Files

Device Files

� Standard– IEC 61804-3

– Used by all systems

� Created by device

manufacturer

� This is the DD files

System Files

� Non-standard– Unique to each system

� Created by system

manufacturer

� Other files

� Support system

34

� This is the DD files

� Supports device

functionality

� Download from bus

organization site or device

manufacturer site

� Support system

functionality– System graphics (before

EDDL)

– Alarm management

– Default settings

– etc.

� Download from system

manufacturer site– May also include DD as a

single package

Downloading Device Files from The Internet

Device Files:

www.fieldbus.org

35

System Files:

deltav.com

Field Communicator Files:

fieldcommunicator.com

Downloading System Files From the Internet

36

37

Project Execution Considerations

System Implementation

Protocol` Manufacturer Model Description Device

Revision

HART Yokogawa YTA320 Temperature 3

HART Metso VG800 Valve Guard 6

FF CSI 9210 Machinery Health

Transmitter

3

FF Rotork FF01 Mk2 Electric Actuator 2

WirelessHART Rosemount 3051S Pressure 1

WirelessHART Siemens TF280 Temperature 1

PROFIBUS-DP Siemens MM440 Drive 2

38

� Confirm device revision to be used

� Create checklist of all device types for all protocols:– 4-20 mA (HART), Fieldbus, Profibus, WirelessHART

� Load DD for all devices: used and unused– Unexpected devices may show up at site

PROFIBUS-DP Siemens MM440 Drive 2

Integration and Factory Acceptance Test (FAT)

� Interoperability test one device of each type for all

protocols– Will reveal if DD or system files for device are missing

� Minimize surprises at site

39

Commissioning

� A system or handheld needs the correct DD

and system files to be loaded in order for it to

configure and calibrate a device before

commissioning– This applies to 4-20 mA (HART), Fieldbus, Profibus,

and WirelessHART

� The system will prompt if DD or system file for

40

� The system will prompt if DD or system file for

the device is missing

� The system will prompt if configured device

revision is different from actual device

41

Plant Operations & Maintenance

Device Replacement

� Make sure DD and system files for the new device is

loaded– Needed for configuration and calibration before commissioning

– This applies to 4-20 mA (HART), Fieldbus, Profibus, and

WirelessHART

� There is no need to remove the old DD files

42

DEV_REV = 2

DEV_REV = 1

02xx(HART, FF, PROFIBUS, WirelessHART)

Training for Competency

� EDDL is where systems and devices meet

� Training is a critical success factor for any

project– EDDL must be part of the training

� Customized for role:– Instrument technicians

– System administrators EDDL

System

43

Devices

� Customized for the systems and portables

used

44

Device Revision Troubleshooting

EDDL files do not fail

DD File Missing

� The system or handheld field communicator will prompt if

a DD file is missing

� The prompt will specify which DD file the system or

handheld needs

� Without the DD the 4-20 mA (HART), Fieldbus, Profibus,

or WirelessHART device cannot be configured and

calibrated before commissioning

45

calibrated before commissioning

� Use semi-automated field communicator DD file update

software

Proprietary System File Missing

� The system will prompt if the proprietary system file such

as a “template” is missing

� Newer systems don’t have this problem– Upgrade to a version which automatically generate templates and

other proprietary files

46

Unable to Interpret CFF

� The system will prompt if it is unable to interpret the CFF

file

� Obtain modified CFF from system supplier

� Newer systems don’t have this problem– Upgrade to a version which has passed HPR

47

Device Revision Mismatch

� This error appears when Device Revision for the tag place

holder created in the system database is different from the

Device Revision of the actual device connected

� A device with device revision 02 requires:– a DD file for Device Revision 02xx

– A system database tag place holder created for a device with

Device Revision 2

48

� A 4-20 mA controller does not care about device revision

but handheld and configuration software do

� Use automated system DD file update

DEV_REV = 2DEV_REV = 3

Device Not Detected

� EDDL files are not required to detect the presence of a

device– If a device is not detected, it is not a problem with EDDL

� A gateway can join a WirelessHART device to the network

without using EDDL– Provided the network ID and join key have been set

– If device refuse to join, it is not because of EDDL file

49

– Software or a handheld field communicator requires DD files in

order to configure the network ID, join key, and update period in

the device before it can be detected by the gateway

50

Solution and Results

Solution

� Incorporate device revision management as part of the

project training program

� Upgrade existing systems to latest version to benefit from

improved device revision handling

� Manage DD files during project execution

� Invest in automated system DD file updates

� Use the device revision management life-cycle application

51

� Use the device revision management life-cycle application

guide

Business Results Achieved

� Project-phase device commissioning delays due to device

revision issues can be reduced once system engineers

understand device revision management– Ensuring on-time plant startup

• Avoiding project delay penalties

� Less operational-phase device replacement down-time

can be achieved once instrument technicians and system

52

can be achieved once instrument technicians and system

administrators understand device revision management– Greater availability

� The full features and diagnostics of devices can be

accessed once systems are kept up to date– Optimal operation and lower maintenance cost

Summary

� Device revisions are the “problem”, DD is the solution

� Device revision affect all protocols

� Study revision management further

� Exercise device revision management– Project execution

– System administration

� Automate device revision management

53

� Automate device revision management

� Reduce project delays (commissioning)

� Greater availability (device replacement)

Comments Questions

! ?

Where To Get More Information

� ‘Device Revision and Lifecycle Management Guide’ can

be found on the EDDL Intelligent Device Management

(IDM) microsite:– www.eddl.org

– FREE download

54