EDD Registrations will be accepted provided the device (device type, device revision) is already Compliance Registered.


  • A manufacturer must submit a device and EDD for registration simultaneously (effective September 1, 2017). 
  • Devices are tested first, if it meets the requirements for registration the EDD is processed .


EDD Revisions will be accepted for Registration in the HART EDD Library provided that a EDD for that device type and device revision is already registered.


  • Updates made to EDDs must comply with HART EDD compatibility rules. 
  • Any revision that would indicate a firmware change to the device will fail EDD registration. The device revision number must increase.  The device must be tested and registered before the EDD is re-submitted.




What needs to be submitted?


Purchase Order 

Payment is accepted via purchase order or credit card authorization. 

Each EDD submission must include payment for the fee.


EDD Source Files

There must be only one *.ddl source file.  

Additional source (*.dd, *.h) and image files (*.jpg, *gif, *.png) may be included.


How do I create EDD Source Files?


Configuration File 

Devices.cfg must have the entry for the Manufacturer and Device Type number. This allows the Tokenizer to resolve the device type symbol in your DD to an integer.


How do I create a Devices.cfg file?


Readme


This is a text file that holds at least the identifying data for the DD. This should be a text file consisting of at least the following 5 lines of information:


  • Manufacturer ID number (hexadecimal)
  • Expanded Device type number (hexadecimal)
  • Device revision (hexadecimal)
  • DD revision (hexadecimal)
  • DD Release date (yymmdd)

Include any special information or device status that FieldComm Group needs to know in order to register your Device Description.   
  • If there are changes required to the Standard DDs, the manufacturer must document the changes and request approval via Support Ticket in advance of the EDD submission.  
  • All deviations from standards must have an approved supportive document (Ticket#, CR#, AR# or Policy #) which was approved prior to the submission date. This includes REDEFINE of standard variables or commands, ADD enumerations or bit enumerations, and including Universal Commands or Common Practice Commands which are defined by HART Protocol Specifications but have not been released in the Standard DD library. 
  • The submitted source shall not produce any errors when built by the Tokenizer, else this will cause the test campaign to fail, resulting in the invoicing of the testing services fee. 
  • Errors produced by host simulator software must be resolved prior to submitting the EDD for testing at FieldComm Group, else this will cause the test campaign to fail, resulting in the invoicing of the testing services fee. 



HART EDD Exhibit
This is an Excel document which records the information necessary for registration. The template is included in the HART EDD Registration Kit.  Always use the latest version of the registration kit. 


SDC Test Logs
Please place the following log files in a zip file named "devtypeDevRevDDRev_SDC.zip" within a folder named "SDC", this folder is within the submission zip file:

  • sdcOut.txt
  • sdcLog.txt
  • sdcErr.txt
  • wsdcOut.txt
  • wsdcLog.txt
  • wsdcErr.txt

How are the SDC test logs generated?


DD Host Test Directories
(Optional) Each host manufacturer may require test files that will allow them to test your EDD for proper operation and compatibility with their host device.  Please segregate these test files into separate directories so that the FieldComm Group can forward your Encoded DD (Tokenized DD file) along with the appropriate test files for operational testing. Some examples of hosts which accept test files include 475 handheld, AMS, PDM, PRM, Fieldmate, EHiDTM.

Please place the event capture log files in a zip file named "devtypeDevRevDDRev_Host X.zip" within a folder named "Host X", where "Host X" is the name of the system.

How can I test my EDD on a host system during product development?

Submission File Structure

It is important to follow this file structure to prevent delays in the processing of your request. 

The file name structure should follow the example, where "devtype" is the Expanded Device Type Code of this device, "DevRev" is the device revision of this device, and "DDRev" is the EDD revision of this device.  The developer should use a prefix of "devtypeDevRev" for the source files. Please see the example below. 
 

Example of EDD zip file

 


The EDD zip file "devtypeDevRevDDRev.zip" is included as an attachment to the support ticket belonging to the request for registration. Please see the example below.




EDD_ticket_attachment.png

Example of a Registration Submission Zip File


If your attachments exceed 15 MB, please submit your ticket with the Purchase Order attached and request an upload link in the ticket Description.
 




What is the process?

 

A manufacturer develops the EDD and submits it for registration by opening a ticket and specifying HART EDD Registration is being requested.  Please put the expanded device type and model name in the subject line of the ticket.

 

Our technical staff reviews the submitted files for completeness, then schedules the complete code audit.  FieldComm Group reviews the source code for compliance to the specifications and builds (Tokenizes) the encoded files and symbols files. The final stage is operational verification, the encoded files are sent to host manufacturers to confirm interoperability. 



If there are no issues found, the EDD is registered and published in the product registry.