Overview

DeviceInfo files are text-based files comprised of extracted metadata from the EDD and are output from the generator as JSON and XML file formats.  


The following procedure applies to HART FDI Device Packages built with the FDI-IDE 1.4 or later. 

 

How to remove DeviceInfo files from a build

If the FDI Package project ever built the DeviceInfo files, they will reside in the local EDD directory (C:\HCF\DDL\Library\mmmmmm\dddd\ ).  


By deleting the JSON and XML DeviceInfo files and re-creating the package in the FDI-IDE using the Project > Create Package menu option (or the zip icon on the tool bar), the resulting FDI Device Package will not include any DeviceInfo files and the catalog.xml will remove the references to these files. 

 

How to create FDI Packages WITHOUT DeviceInfo Files

 

To tokenize the source and not trigger the DeviceInfoGenerator, use the first “Tokenize” option in the Ant Script shown below.  



 

Next, using the Project > Create Package menu option (or the zip icon on the tool bar), build the package. The resulting FDI Device Package will not include any DeviceInfo files. 


 

 



How to create an FDI Package WITH DeviceInfo files

When the time comes to include DeviceInfo files in the FDI Device Package, the following steps will allow the developer to do so. 


By default, the Tokenize.FDI.xml Ant Script includes a call to DeviceInfoGenerator and the DeviceInfo files are added as protocol specific attachments in the FDI Package.

 

Manually configuring an Ant build will allow the user to Tokenize and Generate DeviceInfo files that match the EDD,

and the steps must be done in this order. 


1.    Right-click on the Tokenize.FDI.xml file in the Navigator window of the FDI-IDE. Select Run As.

2.    Select 2 Ant Build... from this context menu.

3.    In the Edit Configuration dialog window, select the first two targets (Tokenize [Model Name...], Generate Device Info: [Model Name...] )

4.    If needed, you can re-order the script using the Order... menu.

5.    Click Run to execute the custom script.


 


Similarly, if the script steps in #3 above are selected as Tokenize [Model Name...] and then 1_Create Package [default], this will execute the same way as above with the additional step of building the FDI Device Package. 

 


The resulting catalog.xml includes DeviceInfo files as entries in ListOfCommunicationProfileSupportFile section.


<ListOfCommunicationProfileSupportFiles>
<CommunicationProfileSupportFile>rId1</CommunicationProfileSupportFile>
<CommunicationProfileSupportFile>rId2</CommunicationProfileSupportFile>
</ListOfCommunicationProfileSupportFiles>