About EDDL
Technical Resources
Standards Groups

EDDL FAQ

Q: It looks like EDDL works like a printer driver in Windows. Is that a good analogy?

A: No. A printer driver is a software program. An EDD is a text based description of the field device and its properties. A better analogy would be to say that EDDL works like web pages and web browsers on the Internet.

Q: Does EDDL support parameter reconciliation for all devices, or is it optional only available for some devices?

A: EDDL is a declarative technology, not a software program. It describes field device parameters and data. The host can use this to compare data in any device against data stored in an external database without special code programmed by the device manufacturer. Thus a host can support parameter reconciliation for all devices.

Q: Does EDDL support offline configuration and save for all devices, or is it optional only available for some devices?

A: EDDL is a declarative technology, not a software program. The host does not rely on any code from the device manufacturer to enable data to be saved or retrieved to and from an external database. Thus a host can support offline configuration and save for all devices.

Q: Does EDDL support configuration printing for all devices, or is it optional only available for some devices?

A: EDDL is a declarative technology, not a software program. The host does not rely on any code from the device manufacturer to enable data to be displayed or printed. EDDL describes the data and how it should be displayed. Thus a host can render displays and print-outs for all devices.

Q: Does EDDL support help text for all devices, or is it optional only available for some devices?

A: EDDL is a declarative technology, not a software program. The host does not rely on for example the Windows help system. EDDL describes the data including labels and help text. Thus a host can display help for all devices.

Q: How robust is the architecture of EDDL? Is it program components that can experience procedure call problems and crash?

A: EDDL is a declarative technology. There are no program components with procedure calls that could fail. An EDDL device support file is very much like an HTML web page and the host is very much like an HTML web browser that renders a display based on the declaration. If the declaration is faulty the host will report this just like a web browser reports there is an error on the page.

Q: How does EDDL address cyber security when device support files are downloaded from the Internet? Is it based on EXE, DLL, OCX program files that could contain malicious code?

A: EDDL is a declarative technology. It is compressed text documents with method scripts which are interpreted, not executed programs. Thus malicious code cannot be embedded.

Q: Can EDDL be used to provide externally accessible information, or does it only display values on the screen?

A: EDDL is a declarative technology, not a display program. The host can use the information about the data to present the data as well as making it available through to other applications, for example through an OPC-UA server configured using the attributes declared by EDDL.

Q: Is EDDL only intended to display data in computer workstations or will it support handheld communicators as well?

A: Because EDDL is a declarative technology, not a software program, it is platform independent supporting software and sophisticated device management systems on Windows workstations as well as embedded devices such as handheld field communicators and blind gateways having web server interface. Data servers such as for OPC also utilize EDDL to build name space etc. Thus EDDL provides a single universal solution.

Q: Is EDDL only working with HART protocol devices, or with devices using other protocols as well?

A: EDDL theoretically works with any bus or Ethernet protocol. So far it is being used with devices communicating HART, FOUNDATION fieldbus, and PROFIBUS.

Q: EDDL only works for simple instruments like temperature transmitters, showing diagnostics as brief text messages, right?

A: No. EDDL applies to simple as well as sophisticated devices including valve positioners and variable speed drives. Performance analysis results can be displayed graphically, for example in plots such as valve signature and step response.

Q: How will future versions of Windows and its regular service packs affect the compatibility of EDDL?

A: Because EDDL is a declarative technology, and not an executable program, it is platform independent not affected by changes in operating system. Therefore the investment in the system is protected.

Q: Do I need to complement EDDL with FDT/DTM?

A: No. EDDL handles all aspects of the device and system life cycle from configuration and commissioning to advanced diagnostics and performance analysis. It need not be complemented.

Q: Devices from different vendors must be displayed consistently. Does EDDL technology help to ensure that?

A: EDDL gives the device vendor complete freedom to define the content on device pages to give access to all device functionality. But, since EDDL is a declarative technology, the style (look & feel) comes from the host. This ensures that colors are used consistently and that buttons and other controls function uniformly for all devices on the system.

Q: Over the life time of the system there will be many versions of devices used as failed devices are replaced. How does EDDL prevent conflicts between different versions of a device?

A: Each version of each device type from every vendor has its own dedicated EDDL file. The addition of a new device or version simply means the addition of a file without removing or overwriting existing files. Thus a new version does not conflict with an old.

Q: Does EDDL meet the requirements of NAMUR NE 105?

A: Yes. Most of those requirements are met simply because EDDL is a declarative technology avoiding problems associated with hardware drivers.

Q: Will I have to constantly upgrade my EDDL host software when I buy new devices in the future?

A: No. Frequent host upgrades can be avoided because when a new type of device or a new version of a device is added, a corresponding EDDL file is copied into the host. As long as the EDDL specification does not evolve drastically there is no need to upgrade the software to take advantage of he new device. Because EDDL is a committee standard, changes should be infrequent.

Q: Can new devices be added to the EDDL host without expert knowledge and privileges?

A: Yes. Because EDDL is a declarative technology, not a software program, adding support for a new devices is as easy as copying a file. There is no need to uninstall old program components or to install new program components. No registry entries are made and therefore no special privileges are required. There are no shared DLLs and thus version conflicts are avoided. There will be no problems due to components refusing to uninstall.

Q: What will EDDL for a device cost?

A: The intention is that EDDL files are an integral part of the whole product at no additional cost. Devices are charged differently depending on the level of sophistication of the embedded diagnostics. Hosts may charge differently depending on the level of graphics sophistication chosen. The EDDL file is expected to be free.

Q: Does EDDL completely eliminate proprietary software applications and plug-ins?

A: Maybe not completely. The EDDL deals with devices on an individual basis. Functions that span multiple devices, such as batch runs of partial stroke testing for multiple devices may not be covered by EDDL.

Q: Are EDDL files registered, and how?

A: Yes. EDD files are registered together with the device as part of the device interoperability registration process.

Q: What is the difference between DD, DDL, EDD, EDDL, and "enhanced EDDL"?

A: In simple terms DD, DDL, EDD, EDDL are all the same. DD is the original name. DD and EDD refers to the file itself while DDL and EDDL refers to the language used to write the file. Enhanced EDDL refers to the waveform graphics, continuous trend charts, table grids, and images as well as better menu structures, methods, and persistent data storage which was added in 2006.