View this email in your browser

The ABCs of EDDs 


All devices submitted for product registration require an FDI Device Package along with the EDD. While FDI Device Packages incorporate an EDD within the package, EDDs are also registered separately for those systems that do not support FDI-based device integration today. A single source code project can manage and produce both file formats. For devices submitted for registration, the EDD is inspected first to determine if any protocol compliance issues might impact the actual device test.  

When developing and maintaining HART EDDs, all EDDs start by importing common code from the HART Standard DD Library. This code is part of the FDI Package IDE tool set for developers.

 Here are three keys to a successful EDD test campaign: 



The HART EDD Standard Library was developed by project group members who are experts in EDD technology. Along with the standard EDD code, developers use a companion document  – Using the HART Standard Library (FCG AG10101). The latest version is published with the FDI Package IDE. Read this document carefully and follow the rules for developing your EDD. Device type and manufacturer labels are pre-registered, make sure you are using those exact strings. If you don't have an assigned device type for your product, please contact support to request it today. 



The HART EDD Test Specification (FCG TS20019) is the basis for conformance testing and is available with the FDI Package IDE. All HART EDDs are subject to the rules defined in the document. Much of these rules depend on verifying your EDD against the rules outlined in the latest application guide, using the HART Standard DD (FCG AG10101). If you have developed according to the latest library, the test cases should be much easier to run to verify the implementation. While EDD testing is a manual process today, FieldComm Group is developing additional automated tools that will greatly help speed up this verification process. Stay tuned for future announcements!  



The Reference Run-time Environment (RRTE) is included in the FDI Package IDE. This application allows you to inspect your EDD. When loading your EDD, make sure to test with a physical device connected and also run the same EDD in simulation mode. Oftentimes, differences seen between the two can indicate a compliance issue with the EDD properly matching the device. Make sure to traverse all menus to verify that data can be read from the device.  


When loading the FDI Package, make sure to exercise the transfer/download to device menus in a variety of initial device states. Remember that these menus are there to assist an end user in properly configuring a device. Devices, especially multivariable devices, may have different configurations and it's important the transfer can handle devices that are not necessarily in a base/factory state.