This support article will provide information about common problems and questions reported by users of the FDI Package IDE. There are three main topics: IDE, RRTE, and CTT. Each topic will contain specific troubleshooting tips and Q&A. For HART Tokenizer errors and warnings, please refer to Troubleshoot the HART Tokenizer.
TABLE OF CONTENTS
- FDI Package IDE
- Pre-Requisite Installations
- Build Output shows BUILD FAILED but an encoded file was produced, what failed?
- Cannot set FDI Perspective
- FDI Perspective Windows are Missing
- FDI "Outline" of the Source is Blank
- ISA100 "Legacy Tokenizer"
- FF Tokenizer Installation is Missing, Reported as Malicious Software
- How to set the FDI-IDE to open, process and save files in UTF-8 for multi-byte language support
- Reference Run-Time Environment
- Communication Servers
FDI Package IDE
This topic includes the development environment, tokenizers, and DeviceInfo.
There are specific versions of Java SE and eclipse which were used to develop the IDE, the user guide contains the version information for these tools. If users install other versions of Java and/or eclipse, there may be issues because they have not been fully regression tested with the latest release of the IDE.
Eclipse Error Message: Java was started but returned exit code=13.
This error occurs because your Eclipse version is 64-bit. You should download and install 64-bit JRE. Please see http://go.fieldcommgroup.org/fdi-ide-documentation for the current Java SE version to install.
Build Output shows BUILD FAILED but an encoded file was produced, what failed?
The build output lines of interest are:
[exec] Completed with: 0 Errors, 0 Warnings, 0 Informational
C:\....\Tokenize.DD.fm8.xml:23: exec returned: 1
The Tokenizer XML file is created when you setup an FDI project in the IDE, this error message is pointing to line 23 of this XML file. If you open this XML, you will see line 23 pertains to the DeviceInfoGenerator:
To see why the DeviceInfoGenerator failed, you must open the built *.json file in the DeviceInfoBrowser tool (C:\Program Files (x86)\FDI\HART DeviceInfoBrowser). The DeviceInfoBrowser shows more information about what failed.
Inspection of the XML may show: <>pv-units-type See List of EDDErrors.
Cannot set FDI Perspective
FDI Perspective Windows are Missing
If you close a window in the IDE you can reset the perspective.
FDI "Outline" of the Source is Blank
After tokenizing the source successfully, the Outline window appears blank.
The file associations may be incorrect, Eclipse has defaulted to using the wrong editor for .DDL files. You can change this setting in the Eclipse "Preferences" menu.
Open the General > Editors > File Associations menu. Select the *.ddl File Type in the top window. In the bottom window, select the "EDDL Editor" and click the "Default" button to make this editor be your default for .DDL files.
Click OK to save this setting.
ISA100 "Legacy Tokenizer"
Problem: Using the FDI-IDE with an "ISA100" license and not able to re-produce the *.ff5/*.sy5 device descriptions because the FDI Project settings GUI does not show the options for "Legacy Tokenizer".
The solution is to change the Interface Type to "H1" and then run the Tokenizer.DD.ff5.xml as your Ant Script.
First, open the Device Type tab within the FDI Project settings. Click on "Add interface..." and select Foundation Fieldbus: H1.
Expand the "Legacy Tokenizer" section within the Device Type tab. Enable the "FF Tokenizer ff5" option.
Complete the remaining settings for the project and Save the changes. The Communication Profile should now be [foundation_h1] (A).
Next, right-click on the Tokenize.DD.ff5.xml file (B) and select Run As.../2 Ant Build...
Here is the menu:
FF Tokenizer Installation is Missing, Reported as Malicious Software
Issue: After FDI-IDE 1.5.0 installation without any error, the FF tokenizers were not deployed in "C:\FF\TOK". This issue is documented as Bugzilla 3509 - Tok and Pretok executables should be signed.
Solution: FCG will provide a patch containing signed exe files so that Microsoft Windows does not perceive them as malicious. Next minor release of the tools will include signed exe's files, etc.
How to set the FDI-IDE to open, process and save files in UTF-8 for multi-byte language support
Issue: After FDI-IDE 1.5.0 installation, two-byte characters previously rendered properly. Now they are not showing properly (see example below).
Explanation: IDE settings have not been persisted, language encoding is CP1252 instead of UTF-8.
Solution: Change the settings in eclipse to UTF-8.
Open the IDE workspace. Go to the Windows menu > Preferences. Open the 'General' section > 'Editors' > 'Text Editors' > 'Spelling'. Change Encoding to 'Other: UTF-8'. Apply and save changes.
Open the 'General' section > 'Content Types' > 'Text'. For 'Dictionary File Editor' and 'EDDL Editor' change Default Encoding to 'UTF-8'. Apply and save changes.
Next, go to the 'Workspace' section. Change the Text file encoding to 'Other: UTF-8'. Apply and save changes.
Reload the source file containing multi-byte characters and verify they render as expected. You may need to replace the corrupted files with the original sources if you are importing this project from a previous development environment.
Reference Run-Time Environment
This topic includes the RRTE, DMS, communication clients, Communication Logger, Device Simulator, Package Repository.
The RRTE will only load a single instance of an FDI Device Package. If the package was previously loaded and was not fully closed, the RRTE may show an error.
The FDI-IDE and RRTE do not include all possible Communication Servers for the various FDI communication protocols. Please see the User Guide provided in the Documentation support article.
If you see an error like the ones below, you may need to install and/or acquire a license for the Communication Server.
Error Message: ifakPN driver has no valid license!
List of EDDErrors
If there are errors detected by the DeviceInfo generator, they are described in the Browser User Manual. A list is included here for quick reference.
|EDDError Code||Error Description|
|no-errors||No errors were detected|
|negative-pv-index||A symbol name was not found on the Process Valuelist|
|cmd-3-resp-short||An odd number of VARIABLES on a Command 3 response is expected|
|pv-units-type||Process Value units must be of type enumerated|
|pv-value-type||Process Values must be of type float|
|pv-units-missing||No Process Value units code was found|
|pv-value-missing||No Process Value was found|