EDDL Highlights Explained
The characteristics that make EDDL ideal for device integration:
- Robustness
- Security
- International standardization
- Full utilization of host features
- Externally accessible information
- Single universal solution
- Different devices
- Different protocols
- Different tools
- Different tasks
- Investment protection
- Consistent display of devices
- No version conflicts
- Easy integration and removal
- No licensing
- Full support of device functionality
- Interoperability testing
Text based
EDDL is a text file, not a software, and hence independent of operating system.
Moreover, it does not execute. This makes a system based on EDDL not just easy
to setup, but also easy to manage and maintain current in the long-term. This
makes EDDL secure, robust, and applicable to portable tools which are not PC-based,
such as handheld communicators and calibrators. Moreover, it enables EDDL to
avoid device version conflicts, makes integration and removal easier, and protects
the investment.
Independent of communications protocol
EDDL is applicable to different communication protocols and is independent of the underlying communication hierarchy. This makes it possible to integrate data from HART, WirelessHART, Foundation fieldbus, and PROFIBUS devices in the same tool.
Robust
EDDL is not software and therefore has no tightly coupled procedure calls that could fail. If the EDDL declaration is faulty the host will report this just like a web browser reports there is an error on an HTML page.
Secure
EDDL is not software and thus malicious code cannot get embedded. Complex procedures are scripted as text which is interpreted rather than executed.
International standard
IEC 61804-3 ensures compatibility between manufacturers. Due process ensures backward compatibility as new versions of the standard are developed.
Externally accessible information
EDDL is not a display program and therefore the device information and the meta-information about the device information is also made available to other applications, for example through OPC-DA or OPC-UA.
Full utilization of host features
EDDL does not require code for parameter reconciliation, offline parameterization, save, or printing. Thus functions built into EDDL-hosts can be used with all devices.
Single universal solution
EDDL was created to support the broad spectrum of devices, protocols, tools, and diverse tasks encountered in a plant.
Different Devices
EDDL displays simple text as well as rich graphics and thus applies to simple temperature transmitters, sophisticated valve positioners, variable speed drives, and bus health transmitters alike.
 |
 |
 |
 |
 |
Variable Speed Drive |
Radar Level Transmitter |
Machinery Health Transmitter |
Valve Positioner |
Pressure Transmitter |
Different Protocols
EDDL declares commands and parameter locations and is used for devices communicating HART, WirelessHART, Foundation fieldbus, and PROFIBUS as well as for OPC-UA software.
Different Tools
EDDL is not software and therefore works on embedded field communicators and web servers as well as sophisticated client software and OPC servers.
|  |
 |
 |
 |
Device Management Software |
Handheld Field Communicator |
Device Management Software |
Configuration & Diagnostics Software |
Configuration & Diagnositcs Software |
Different Tasks
EDDL describes function blocks, device parameters, calibration procedures, menu structures, and presentation of diagnostics results and thus applies to control strategy building, commissioning, operation, and maintenance tasks. EDDL handles all life cycle aspects.
Investment protection
EDDL is not software and therefore not made obsolete by operating system changes, upgrades, or service packs. This makes a system based on EDDL not just easy to setup, but also easy to manage and maintain current in the long-term.
Cross-platform Compatibility
EDDL is not software and therefore not made obsolete by device management software changes, versions, or service packs. This makes a system based on EDDL not just easy to setup, but also easy to manage and maintain current in the long-term.
Consistent display of devices
An EDDL browser renders consistent displays with consistent mode of operations for the technician based on descriptions of each device. A gauge displaying a value looks the same for all device types from any manufacturer. Any bar-graph looks the same. Any trend chart looks the same and has the same tools for zoom etc. Buttons to OK, cancel, or apply changes as well as print, search, or get help are for any device. Messages from a shared dictionary ensure consistent interaction.
HART |
HART |
Wireless |
HART |
Fieldbus |
|---|---|---|---|---|
 |
 |
 |
 |
 |
Pressure |
Output Current |
Battery Voltage |
Temperature |
Actuator Pressure |
No version conflicts
EDDL is not software and therefore adding support for a new device does not conflict with support for existing devices. Integrating a new device is as simple as copying a text document. This makes a system based on EDDL not just easy to setup, but also easy to manage and maintain current in the long-term.
Easy integration and removal
EDDL is not software and therefore does not require installation, high-level access privileges or un-installation for upgrade. Removing EDDL is not necessary but is as simple as deleting a text document. This makes a system based on EDDL not just easy to setup, but also easy to manage and maintain current in the long-term.
No licensing
EDDL is not software and therefore there is no need to manage licenses. This makes a system based on EDDL not just easy to setup, but also easy to manage and maintain current in the long-term.
Full support of device functionality
EDDL describes procedures such as calibration and complex setup and presents waveform graphics, continuous trend charts, table grids, and images. Persistent storage is provided for test results. All functionality in even the most sophisticated device can thus be made available to the technician.
Testing
EDDL files are tested together with the device as part of the protocol interoperability registration process.
Conclusion
EDDL meet user requirements such as NAMUR NE 105. Most of the user requirements are met simply because EDDL is a declarative technology avoiding issues associated with software drivers.