Acceptance Policy

There are two entry points for HART EDD Registration requests. The first entry point is to include the EDD with a Device submission. The second entry point is for a minor update to an existing EDD. Both methods are discussed below.


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

  • A new EDD Registration for a Device that is currently HART-Registered (i.e. appears in the Product Registry) is not required to be submitted with a device hardware sample.
  • A manufacturer developing a new Device or a Device Revision mustsubmit it with a corresponding EDD (effective September 1, 2017).  
    • Devices and their corresponding EDD are tested in parallel whenever possible.  
    • Registration is granted when both the Device and EDD have met the requirements of registration.
  • A manufacturer developing a new Device or a Device Revision will be required to include an FDI Device Package starting on December 31, 2020.  

EDD Revisions will be accepted provided that an EDD for that device type and that 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. In this case:
    • The device revision number must increase.  
    • The device revision must be tested and pass conformance testing.


Purchase Order Requirements

Each submission must include payment for the appropriate fees.  Additional Testing Services may be required if inspection of modified standardized HART code is required, this may include labels and/or help strings which are redefined after import from the HART Standard DD Library. 


If a quotation is required, please request a quotation in your ticket. Payment is accepted via purchase order or credit card authorization.  After the Purchase Order or other payment method is accepted by FieldComm Group, a test date can be scheduled for the campaign. 


The fees will be invoiced after the conclusion of the test campaign, the ticket number will be your reference number on the invoice.

How do I submit a Device + EDD/FDI Package Registration?

Please open a test campaign request via the Support Portal ticket system


Choose Product Registration, then HART Device (location), and specify if this is a New Device, Device Revision, Private Label/Rebranding, or Wireless Product.  See Figure 1 below. 

The ticket should include the Model Name and Device Type Code for the product you wish to submit for testing. The ticket must have a Purchase Order and EDD Source and Documentation attached.


Fig 1. How to classify your product test campaign request


Purchase Order 

Please see the "Purchase Order" section above.


EDD Source and Documentation

FieldComm Group will generate a companion ticket to track the EDD test campaign activities. There is no need to create a separate ticket for this portion of the product test campaign.

Please follow the instructions below under the "Prepare Your EDD Submission" section, please submit to the companion ticket created for you. 


How do I submit an EDD Revision?

Please open a test campaign request via the Support Portal ticket system


Choose Product Registration, then HART EDD, and specify either EDD Revision (this is most common) or Private Label/Rebranding EDD Revision.  See Figure 2 below.  

The ticket should include the Model Name and Device Type Code for the EDD Revision you wish to submit for testing. The ticket must have a Purchase Order and EDD Source and Documentation attached.


Fig 2. How to classify your HART EDD test campaign request



Purchase Order 

Please see the "Purchase Order" section above.

 

EDD Source and Documentation

Please follow the instructions below under the "Prepare Your EDD Submission" section.


Prepare Your EDD Submission

An  EDD Submission Template is included in the HART EDD Registration Kit.  This template contains the directories to use to create your Submission Zip file. The Submission Zip file should be named after your ticket number, this is to establish the audit trail of your submission.   


Zip files larger than 20MB must be uploaded to ShareFile, please use the ticket number as the zip file name. An upload link is provided in the HART EDD Registration Kit.


Source Files (Required)

There must be only one *.ddl source file.  Additional source (*.dd, *.h) and image files (*.jpg, *gif, *.png) may be included. See Figure 3 below for an example.

A template is included in the HART EDD Registration Kit, see EDD Submission Template\Source Files\.


Fig 3. Example set of EDD Source Files


How do I create EDD Source Files?


Configuration File (Required) 

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.

A template is included in the HART EDD Registration Kit, see EDD Submission Template\Source Files\.


How do I create a Devices.cfg file?


Readme (Required)

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) (i.e. the date you have given to this source submission)
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. 
  • EDDs without support for the maintenance_root_menu and/or offline_root_menu must submit a statement in the Readme.txt that these menus are not supported per WG PD10013. FDI Device Packages must include all root menus.
  • The submitted source shall not produce any errors when built by the current version of 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.  
  • Errors discovered after the test campaign has concluded that result in source code changes must be submitted as a new DD Revision as a new and separate submission.
A template ReadMe.txt file is included in the HART EDD Registration Kit, see EDD Submission Template\Source Files\.

HART EDD Exhibit (Required)
This is an Excel document which records the information necessary for registration.
The template is included in the HART EDD Registration Kit, see EDD Submission Template\Product Documentation\. 

Host Interoperability Logs (SDC Test Logs or RRTE Logs)
SDC-625 logs must be captured using the latest released version of the application (4.2.0), which is a component of the HART DD-IDE. Support for the HART DD-IDE will expire on September 17, 2020. Please place the following log files 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
A template is included in the HART EDD Registration Kit, see EDD Submission Template\SDC Test Logs\.


RRTE Logs must be captured using the latest released version of the FDI Package IDE. RRTE Logs will become mandatory after December 31, 2020. Please include all log files from C:\ProgramData\FDI\Logs in the submission zip file.

o    AuditTrail.log

o    DefaultLogger.log

o    DMS.log

o    HARTModemDriver.log

o    FdiContainer.log

o    FDIOPCUACLIENT.log.txt

o    InformationModelServer.log

o    ReferenceHost.log

o    Trace.log



Host Application Test Logs (optional)
This is not a requirement for FieldComm Group registration.


Each host manufacturer may require test files that will allow them to test your EDD for proper operation and compatibility with their host application.  Some examples of hosts that accept test files include the 475 handheld, AMS, PDM, PRM, Fieldmate, and EHiDTM.  FieldComm Group recommends pre-testing your EDD on all targeted host applications, then use the Registered encoded files to capture your Host Test Logs to provide to the host representatives. This will allow for the best representative logs of your product to be captured and distributed for further testing. 

Please segregate these test files into separate directories so that the FieldComm Group can forward it to the appropriate host application representatives for operational testing.  

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. 
A template is included in the HART EDD Registration Kit, see EDD Submission Template\Host Application Test Logs (optional)\.

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