NI-FGEN 2024 Q3 Bug Fixes

Overview

The following items are notable issues fixed between the release of NI-FGEN 2023 Q4 and NI-FGEN 2024 Q3, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI-FGEN.

Bug Number

Legacy ID

Description

Details

1622796

Detailed help for NI-FGEN API is not available in LabVIEW from context help or right-click context menu

Workaround:

The detailed help can be accessed from the "Help" menu by clicking on the "NI Signal Generators Help..." option.

Reported Version:

NI-FGEN 21.3

Resolved Version:

NI-FGEN 21.8

Added:

Oct 20, 2021

1881242

NI Linux Real-Time PXIe Controller Unexpectedly Reboots When Using NI-FGEN 21.3

When running any NI-FGEN API calls on an NI Linux Real-Time PXIe controller, the NI Linux Real-Time system stops responding and reboots.

This issue affects NI Linux Real-Time systems that support SMAP, including but not limited to the PXIe-8861 and the PXIe-8840QC, when using NI-FGEN devices that use the NI-DAQmx-based waveform generators such as PXIe-5422 and PXIe-5421.

Workaround:

Edit the /boot/runmode/bootimage.cfg file on the NI Linux RT system, add "nosmap" to the "set otherbootargs" line, and reboot. Note that this disables SMAP for the system.

Reported Version:

NI-FGEN 21.3

Resolved Version:

NI-FGEN 21.8

Added:

Apr 18, 2022

1861805

No device names appear when initializing a session with NI-FGEN on Linux Desktop

When selecting a resource name with niFGEN Initialize.vi in LabVIEW on Linux Desktop, the drop-down menu for selecting resources appears empty and you cannot select a device that is in your system.


Workaround:

Manually enter the resource name for the device you want to use. Use the Hardware Configuration Utility or NI System Configuration software to retrieve the resource name for any devices in the system.

Reported Version:

NI-FGEN 21.8

Resolved Version:

NI-FGEN 2023 Q1

Added:

Apr 19, 2022

2061458

Using the niFgen_WriteP2PEndpointI16 or niFgen Write P2P Endpoint I16 function causes a hang on SMAP-capable Linux systems

Using the niFgen_WriteP2PEndpointI16 C function or the niFgen Write P2P Endpoint I16 LabVIEW VI causes a hang on SMAP-capable Linux systems.

This is a function used "to write initial data from the host to the endpoint before starting generation to avoid an underflow at start." It is only relevant to applications using Peer-to-Peer (P2P) streaming, usually in tandem with a FlexRIO device.



Workaround:

Disable SMAP on Linux. (refer to External Link- How can I enable/disable SMAP)

Reported Version:

NI-FGEN 21.8

Resolved Version:

NI-FGEN 2023 Q1

Added:

Aug 3, 2022

2242367

Reading device temperature sometimes generates an exception

Using the NI-FGEN API to read the device temperature sometimes generates an exception.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-FGEN 2023 Q1

Resolved Version:

NI-FGEN 2023 Q1

Added:

Feb 6, 2023

2477227

Simulated PXIe-5413/23/33 instruments can cause an access violation when calling Export Attribute Configuration Buffer/File

Calling niFgen_ExportAttributeConfigurationBuffer or niFgen_ExportAttributeConfigurationFile (or the equivalent in another programming language) when using a simulated instrument session on an NI PXIe-5413, PXIe-5423, or PXIe-5433 instrument can sometimes cause an access violation.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-FGEN 2023 Q3

Resolved Version:

NI-FGEN 2023 Q4

Added:

N/A

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

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).