Archived: NI-FGEN 2.9 and 2.9.1 Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Overview



This document contains the NI-FGEN 2.9 and 2.9.1 known issues that were discovered before and since the release of NI-FGEN 2.9 and 2.9.1. Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that can be encountered.

Each issue appears as a row in the table and includes the following fields:

  • Issue ID - The number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.  "N/A" indicates that there is no ID assigned to the issue.
  • Issue Title (in italics) - Describes the issue in one sentence or less.
  • Problem Description - A few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you may want more information on an issue. If you would like more information on an issue, contact NI and reference the ID number given in the document.
  • Workaround - Possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, visit www.ni.com/kb/ and enter the KnowledgeBase number in the search field to locate the specific document.
  • Reported Version - The earliest version of NI-FGEN in which the issue was reported. If you discover the issue appears in an earlier version of NI-FGEN than is reported in this field, report the discrepancy to NI to have the field updated.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).

Known Issues by Severity

314690"Error Loading ivi_support_c.dll" results when using some modular instruments on a real-time system with LabVIEW RT 8.6.1.
317520Unable to build an installer from the LabVIEW executable
251164A protocol violation error occurs when using an NI PXIe-1075 chassis
192435NI-FGEN devices are unable to start after installing NI-FGEN 2.7 or later on top of NI-DAQmx 7.0 or 7.1
N/AInstallation interrupted by security dialog boxes
N/ABack button not working in the NI Signal Generators Help
N/ATable of contents not locating in the NI Signal Generators Help
350624In the device documentation, the MAX "Configure" button is inaccurately labeled with its former name, "Properties."

 

IDKnown Issue
314690

"Error Loading ivi_support_c.dll" results when using some modular instruments on a real-time system with LabVIEW RT 8.6.1.
"Error Loading ivi_support_c.dll" results when using some modular instruments on a real-time system with LabVIEW RT 8.6.1. A self-test, self-calibration, or device reset from Measurement & Automation Explorer (MAX) results in error –50251:"The specified component is not available. The component was not loaded."
The following additional related errors may occur:
Deploying a VI using my device results in the following error:
"LabVIEW: Failed to load shared library niFgen_*.*."
Connecting a monitor to the real time controller results in the following error:
"Error loading ivi_support_c.dll."

Workaround: Visit ni.com/kb and search for 5PJF6E77 for information about how to work around this error.

Reported Version: Unknown  Resolved Version: 2.9.1  Added: 10/24/2011
317520

Unable to build an installer from the LabVIEW executable
The following error results when trying to build an installer for an NI-FGEN 2.9 executable in LabVIEW:
**************
*** Error: Windows SDK function returned an error. (Error code -12) The system cannot find the path specified.
**********
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
**************
Done building deployment

Workaround: Visit ni.com/kb and search for 5QJ95VUS for information about how to work around this error.

Reported Version: Unknown  Resolved Version: 2.9.1  Added: 10/24/2011
251164

A protocol violation error occurs when using an NI PXIe-1075 chassis
When routing triggers across segments on the NI PXIe-1075 chassis, a protocol violation error may occur. The NI PXIe-1075 has three bus segments: slots 1 through 6, slots 7 through 12, and slots 13 through 18. If the devices are located in different segments, this issue may occur. Some features, such as NI-TClk, when used for synchronization applications, internally route triggers.

Workaround: Visit ni.com/kb and search for 5FTGSP0O for information about how to work around this error.

Reported Version: 2.8  Resolved Version: N/A  Added: 10/24/2011
192435

NI-FGEN devices are unable to start after installing NI-FGEN 2.7 or later in addition to NI-DAQmx 7.0 or 7.1
After installing NI-FGEN 2.7 or later on a system with NI-DAQmx 7.0 or 7.1 already installed, NI-FGEN may return an error about NI-FGEN devices unable to start.

Workaround: After installing NI-FGEN 2.7 or later, reboot, and then repair NI-FGEN using the Microsoft Windows Control Panel.

Reported Version: 2.7  Resolved Version: N/A  Added: 10/24/2011
N/A

Installation interrupted by security dialog boxes
When you run setup.exe to install the software from the DVD, you are prompted to choose whether you want to always trust software from National Instruments. If you do not select this option, your installation may be interrupted by one or more Microsoft Windows security dialog boxes. However, if you run the installer in silent mode from the command line, you do not receive this prompt, and the installer automatically installs NI's Software Publisher Certificate to your Windows Trusted Publisher Store. If you do not want to make this change to your Windows Trusted Publisher Store, do not choose this installation method.

Workaround: N/A

Reported Version: 2.4.5  Resolved Version: N/A  Added: 10/24/2011
N/A

Back button not working in the NI Signal Generators Help
If you click a topic link in the NI-FGEN C Function Reference section of the NI Signal Generators Help, you cannot use the Back button in the HTML Help window toolbar to return to the original topic.

Workaround: N/A

Reported Version: 2.7  Resolved Version: 14.0  Added: 10/24/2011
N/A

Table of contents not locating in the NI Signal Generators Help
When linking to a topic in the NI Signal Generators Help from the LabVIEW context help or opening the help file from a VI within LabVIEW, the NI Signal Generators Help launches and the relevant topic displays, but the location of the topic might not be highlighted in the table of contents.

Workaround: N/A

Reported Version: 2.7  Resolved Version: N/A  Added: 10/24/2011
350624
In the device documentation, including the Getting Started Guide and Help file, the MAX "Configure" button is inaccurately labeled with its former name, "Properties."

Workaround: When the documentation instructs you to select the "Properties" button, you should select the "Configure" button.

Reported Version: 2.9.1  Resolved Version: N/A  Added: 08/09/2012

Contacting NI

Contact NI regarding this document or issues in the document. If you contact NI in regards to a specific issue, reference the ID number given in the document. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting NI). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also contact us if you find a workaround for an issue that is not listed in the document.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).