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
- Specified VM install not found
- Reference Run-Time Environment
- Communication Servers
- Device Package Conformance Test Tool (DPCTT)
- FDI Signing Tool
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
Explanation: Your installer may have issues. Please make sure to completely uninstall the previous version of the FDI-IDE and use an official release installer for this tool.
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.
If there are more warnings about "Latin-1 encoded string found", you may need to update the individual file properties. Right-click on the source files (.dd, .ddl, .h) and change the encoding to UTF-8. See below
Specified VM install not found
Issue: When tokenizing a Debug version of the HART EDD, eclipse gives an error Specified VM install not found. This error occurred in FDI-IDE 1.5.0.
Explanation: IDE settings have not been persisted, or were not properly configured.
Solution: Open the eclipse settings for the Tokenizer Ant Script. Go to the JRE tab and select Runtime JRE: Run in the same JRE as the workspace (first option). Click Apply.
Try to run this Ant Script again, the error should be resolved.
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.
After upgrading to a new version of the FDI IDE (and RRTE) packages no longer load that worked previously.
This can occur if any of the following are true:
- The prior version of the FDI IDE was not completely uninstalled, and files removed from C:\ProgramData\FDI and C:\Program Files (x86)\FDI
- The pre-requisites were not properly upgraded
- The License Key has expired
You may need to contact Tech Support to retrieve your License Key.
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|
Device Package Conformance Test Tool (DPCTT)
This is the CTT used to check the syntax and structure of the overall FDI Package.
No package is assigned
Issue: User starts a new test campaign and encounters an error message "No package is assigned. Please add the package you want to test."
Explanation: There was no FDI Package configured to test.
Solution: Go to the Campaign menu > Assign Package and then browse to the FDI Package (.FDIX) that is on your local machine.
Campaign has an invalid signature
FDI-IDE version 1.4.2 CTT is opened and a test campaign is started. Test campaign immediately stops with an error "Campaign has an invalid signature: NoStructureSignature".
- Uninstall and delete old FDI-IDE files, re-install the software.
- Uninstall and delete old FDI-IDE files, upgrade to the latest version of the FDI-IDE.
Test Case P_2_2_001 Failed
Test case P_2_2_001 failed, with error "No Digital Signatures found" "the package... does not contain a signature".
Explanation: All unsigned packages fail this test case.
The FDI Package (.FDIX) has not been signed with an appropriate digital code signing certificate using the FDI Signing Tool. There are two digital signatures expected: ProofOfOrigin and ProofOfApproval.
See this article for more details about signatures: FDI Package Signature Processing
Solution: Review the article: How to Sign an FDI Device Package and obtain the FDI Signing Tool utility (free to FieldComm Group Members).
When the FDI Package is registered with FieldComm Group, we apply the first digital signature (ProofOfApproval), then the same file is signed by the vendor (ProofOfOrigin). At this point, the FDI Package can be tested against P_2_2_001 and P_2_2_002 for the appropriate signatures. Both test cases should pass.
FDI Signing Tool
Signature Failed with Unhandled Exception
Issue: FDI Signing Tool reports the file is signed but includes a message below similar to this:
Unhandled Exception: System.UnauthorizedAccessException: Access to the path 'C:\...\*.fdix' is denied.
Explanation: The FDI Package was set to Read-Only permissions, or the folder it is saved in was set to Read-Only.
Solution: Check the files and folders access rights for your user account on the PC using the FDI Signing Tool.