Source Code Submissions

FieldComm Group will build all possible EDD encoded formats from a submitted project. If a developer does not want an EDD to be built and distributed in parallel to the FDI Device Package, additional steps must be taken to ensure the project will exclude the EDD from the build process.  

Only the latest EDD Revision will be available in the Repository for a given Device Type + Device Revision combination.  In other words, an EDD Revision will replace the prior EDD registration for a given Device Type + Device Revision. Ex.  0302.fm8 will replace 0301.fm8

FDI Device Package revisions will be added to the Repository without replacing previously registered revisions of that product. This means that a version 02.00.00. FDIX file will not replace a 01.00.00 FDIX file in the Repository.

Building All Encoded Formats From Single Source

It is possible to build an EDD (*.fm8) encoded file format using the FDI Package IDE, however, developers must take the time to correctly prepare the source files. New features added to FDI Device Packages will not be built into the EDD (*.fm8) and will trigger syntax errors. Developers can use pre-processor directives to maintain a single set of source files for their product.

To build an EDD (*.fm8) with Tokenizer version 8, wrap the PLUGIN, BLOB and/or TEMPLATE items with a __TOKVER__ pre-processor directive. An example is shown below:

This code will include the PLUGIN item only for Tokenizer version 10 or greater, Tokenizer version 10 is what will build the FDI (*.fma) file format. 

Each pre-processor directive should only wrap around a single item, including multiple items may cause errors when Tokenizing the source. 

As other items are added to the Device Description Language, additional wraps may be required to build an EDD (*.fm8) encoded file in parallel to the FDI (*.fma) encoded file.

Building FDI Device Package (FMA) Encoded Format Only

The EDD source code submitted to be used in an FDI Device Package will be registered and will replace your previous registered EDD (*.fms/*fm6/*fm8) (see notes above).  

If the developer wishes to preserve the previously registered EDD for the submitted Device Revision, the developer must implement a syntax error in the EDD source that applies to Tokenizer Version 5, 6 or 8.  

The following is an example for this syntax error:

#if __TOKVER__ < 1000  /* fma only */

     ,  /* insert a comma as shown to create syntax error */


Using this method, this Device Revision will preserve the original EDD (*.fm8) while implementing an FDI Device Package at a higher DD_REVISION. This is made possible because these two formats (EDD and FDI) are different and stored separately in the Repository.