NI-RFSG 15.0, 15.0.2, and 15.0.3 Known Issues

Overview

This document contains the NI-RFSG 15.0, 15.0.2, and 15.0.3 known issues that were discovered before and since the release of NI-RFSG 15.0.3. 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-RFSG in which the issue was reported. If you discover the issue appears in an earlier version of NI-RFSG 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

ID Known Issue
412582

A few of the final samples are not generated on the NI 5673/5673E when using finite generation in Arb Waveform Generation mode or Script Generation mode

When running a finite generation on the NI 5673/5673E, you may not observe the few last samples prior to the end of the generation. This behavior occurs because those samples are not moved all the way through the digital filter on the arbitrary waveform generator. The number of missing samples varies based on the configured I/Q rates.

Workaround: If using Script Generation mode, generate an idle waveform (a waveform that uses 0 as the samples) prior to the end Script instruction.
Reported Version: 14.5    Resolved Version: N/A    Added: 02/16/2015
518027

The NI 5654 standard (not fast tuning) hardware model processes every other trigger when frequency is below 250 MHz and triggers are sent exactly 1 ms apart

When using RF list mode and you set the frequency to lower than 250 MHz, NI-RFSG misses every other trigger if triggers are sent exactly 1 ms apart.

Workaround: If you require 1 ms switching, use the NI 5654 fast tuning hardware option; or if the frequency is set lower than 250 MHz, set the time between triggers to be at least 1.04 ms apart for the standard tuning hardware model.
Reported Version: 14.5    Resolved Version: N/A    Added: 03/05/2015
516385

The NI 5654 remains powered off after the system returns from sleep mode

If a system containing an NI 5654 or NI 5696 is put into sleep or hibernation mode, the NI 5654 or NI 5696 remain powered off when the system returns to operation.

Workaround: In Measurement & Automation Explorer (MAX), reset the devices that are not powered on.

Reported Version: 14.5    Resolved Version: N/A    Added: 02/20/2015
515169

The returned temperature on the NI 5654 is far off from the ambient temperature

When reading temperature from the NI 5654 during RF list mode execution, the temperature returned may be far off from the ambient temperature. For example, NI-RFSG might return the temperature as -201.75 degrees Celsius, when the  ambient temperature is 35 degrees Celsius. This behavior can also cause the RF output to be inaccurate, as the thermal correction applied uses this incorrect temperature. To avoid an incorrect reading, do not run MAX while the device is operating in RF list mode, as this operation mode causes multiple calls to read temperature on the device.

Workaround: Reset the device in MAX if the returned temperature is an extremely high or low value.

Reported Version: 14.5    Resolved Version: N/A    Added: 02/27/2015
514199

Power is inaccurate if the ALC Control property is changed during generation

If the NI 5654 with NI 5696 system device is in a generating state and you change the frequency or power and then change the ALC Control property or the NIRFSG_ATTR_ALC_CONTROL attribute, the power of the generated signal may be inaccurate.

Workaround: Call the niRFSG Wait Until Settled VI or the niRFSG_WaitUntilSettled function after changing frequency or power without interruption before changing the ALC Control property or the NIRFSG_ATTR_ALC_CONTROL attribute.

Reported Version: 14.5    Resolved Version: N/A    Added: 02/16/2015
516773

RF output on the NI 5654 takes longer than usual when using FM wideband modulation

The RF output from the NI 5654 is delayed by up to 10 ms after a frequency change when you enable FM wideband modulation. This happens when you abort and reinitiate the session as well as when you make frequency changes dynamically.

Workaround: N/A

Reported Version: 14.5    Resolved Version: N/A    Added: 02/24/2015
509261

Unleveled warning returns only on first check of the generation status

When an unleveled condition occurs on the NI 5654 with NI 5696 system device in RF list mode, a warning returns on only the first call to the niRFSG Check Generation Status VI or the niRFSG_CheckGenerationStatus function in a particular step of the list. Subsequent calls to this status on the same step in the list do not return the warning even though the device may be in the unleveled state.

Workaround: N/A

Reported Version: 14.5    Resolved Version: N/A    Added: 02/16/2015
498840

Resource name control does not display all devices on first click

After installing NI-RFSG, the resource name control in some LabVIEW VIs does not display all devices when you first select the drop-down list. On subsequent clicks, the device list appears correctly. This issue occurs each time you restart  LabVIEW.

Workaround: Click away from the resource name control, then click the drop-down list again to select your device.

Reported Version: 14.5    Resolved Version: N/A    Added: 02/16/2015
479360

An error occurs when changing the Reference Clock rate for the NI 5654

When the NI 5654 is locked to an external reference and the time between changing the frequency of this reference and changing the value of the Reference Clock rate or committing the session to use an external Reference Clock in NI-RFSG is less than 150 ms, the NI-RFSG session returns an error indicating that the Reference Clock used is not the rate specified.

Workaround: Wait 150 ms after changing the external clock value before changing the value on the NI 5654.

Reported Version: 14.5    Resolved Version: N/A    Added: 02/20/2015
516193

The remote test panel for Phar Lap does not work for the NI 5653

When trying to use the test panels for the NI 5653 on a Phar Lap ETS system, the test panel returns an error, and you cannot control the device.

Workaround: N/A

Reported Version: 14.5    Resolved Version: N/A    Added: 02/18/2015
486930

The niRFSG Error Message VI takes longer than expected

Reporting of errors and warnings from the niRFSG Error Message VI or the niRFSG_error_message function takes tens of milliseconds.

Other VIs that implicitly call the niRFSG Error Message VI may be impacted as well.

Workaround: N/A
Reported Version: 14.5    Resolved Version: N/A    Added: 02/16/2015
510356

Installing the NI-RFSG run-time engine may cause devices to not be shown in MAX

If the NI-RFSG 14.5 runtime is installed after MAX version 14.0 or earlier, the chassis and devices may not appear in the MAX configuration tree.

Workaround: Install the full version of NI-RFSG 14.5 or another product that installs MAX 14.5.

Reported Version: 14.5    Resolved Version: N/A    Added: 02/16/2015
482979

Device association of the NI 5654 with the NI 5696 is lost if you rename the device to the same name as another device

If you rename the NI 5654 or NI 5696 to the same name as an existing device in MAX, the association of the devices is lost.

Workaround: Reassociate the device with the NI 5696 amplitude extender module after renaming the device in MAX.

Reported Version: 14.5    Resolved Version: N/A    Added: 02/16/2015
515837

The NI 5654 device name persists for other devices inserted into the same slot

When you insert another device in a chassis slot that was previously occupied by a NI 5654 that was renamed and then removed from the system, the new device keeps the same name that the NI 5654 held. The new device should have a unique name when installed in the system for the first time. Instead, the previous NI 5654 name persists for other devices placed in the same slot.

Workaround: N/A

Reported Version: 14.5    Resolved Version: N/A    Added: 02/16/2015
329131

RF list mode does not work correctly when using both a Start Trigger and an external source for the Configuration List Step Trigger 

If you use a Start Trigger and an external source for the Configuration List Step Trigger, the device proceeds through the Configuration List Step Triggers before the Start Trigger.

Workaround: To use a Start Trigger to advance a configuration list, use the Timer Event Interval property or NIRFSG_ATTR_TIMER_EVENT_INTERVAL attribute instead of a Configuration List Step Trigger. Another workaround includes not sending the the Configuration List Step Triggers before the Start Trigger.

Reported Version: 1.8    Resolved Version: N/A    Added: 03/14/2014
492490

NI-RFSG 14.0 does not install LabVIEW Run-Time Engine 2013 SP1

NI-RFSG 14.0 does not install LabVIEW Run-Time Engine 2013 SP1, which is required for VST support. If you have LabVIEW 2013, LabVIEW 2014, or LabVIEW Run-Time Engine 2013 installed, this issue does not affect you. If you are using the VST Sample Projects, this issue does not affect you. This issue affects most non-LabVIEW users or users who are working in LabVIEW 2012 SP1 or earlier with the newest version of NI-RFSG.

Workaround: Download and install LabVIEW Run-Time Engine 2013 SP1. You can download LabVIEW Run-Time Engine 2013 SP1 from ni.com/downloads.

Reported Version: 14.0    Resolved Version: N/A    Added: 09/15/2014
425439

When NI-RFSA and NI-RFSG both export a signal to the same external trigger line on a National Instruments vector signal transceiver (VST), LabVIEW does not return an error

You can export two different signals to the same external trigger line on a VST, for example, NI-RFSG exports a Marker Event to PFI0, and NI-RFSA exports a Start Trigger to PFI0. However, LabVIEW does not return an error when this occurs, so only the last item configured within either driver exports its signal.

Workaround: Avoid exporting signals from both drivers to the same external trigger line.

Reported Version: 1.9.5    Resolved Version: N/A    Added: 02/25/2014
483724

Alignment of multiple NI PXIe-5673 devices using NI-TClk is off by 25 ns

When using NI-TClk to synchronize signals from NI PXIe-5673 devices driven by different controllers, the RF signals may be off in their alignment by 25 ns.

Workaround: N/A

Reported Version: 14.0    Resolved Version: N/A    Added: 08/18/2014
385430

niVST Self-Calibrate.vi cannot be found

When using the NI PXIe-5644R or NI PXIe-5645R and upgrading to NI-RFSG 1.9 or when using the NI PXIe-5646R and upgrading to NI-RFSG 1.9.7, niVST Self-Calibrate.vi is missing because it has been moved and renamed. Replace the missing VI with the Self-Calibrate VI located on the NI VST Calibration palette or at <LabVIEW>\instr.lib\niVST\Calibration\SelfCal\Self-Calibrate.vi for your device.

Workaround: Replace existing calls to niVST Self-Calibrate.vi with a call to Self-Calibrate.vi.

Reported Version: 1.9    Resolved Version: N/A    Added: 04/04/2013
258290
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 return. 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, you may run into this issue.  Some features, such as RF list mode or NI-TClk when used for synchronization or MIMO applications, internally route triggers. 

Workaround: Visit ni.com/kb and search for 5FTGSP0O for more information about working around this issue.

Reported Version: 1.6    Resolved Version: N/A    Added: 11/24/2010
435537

Error -1074118136 occurs when exporting an event at a low I/Q rate

If you configure the driver to export an event when using an NI 5673E at a low I/Q rate, or if you configure the driver to export an event and enable the Compensate for Filter Group Delay property when using an NI 5672 at a low I/Q rate, you may receive the following error message:

The AWG reported the following error:
Event delay is outside of the legal range. Change the value of the delay, and/or verify that the units are correct.
Device:5450
Property: Started Event Delay Value
Requested Value: 0.0
Minimum Value: -59.521484e-6
Maximum Value: -34.524536e-6
Property: Started Event Delay Units
Requested Value: Seconds
Status Code: -200345

Workaround: If using an NI 5673E, increase the I/Q rate. If using an NI 5672, you can increase the I/Q rate or disable the Compensate for Filter Group Delay property.

Reported Version: 1.9.6    Resolved Version: N/A    Added: 01/16/2014
392126

The niVST Calibration.lvlib:Self-Calibrate.vi leaks memory when loading and unloading

When using the Self-Calibrate.vi from the NI VST Calibration palette to self-calibrate the NI PXIe-5644R, NI PXIe-5645R, or NI PXIe-5646R, a memory leak may occur when loading and unloading the VI repeatedly.

Workaround: Keep the Self-Calibrate VI in memory. For example, in your top-level VI, create a "dummy" subVI that includes one instance of the Self-Calibrate VI to keep the Self-Calibrate VI loaded in memory.

For applications that optimize memory usage where it is not acceptable to keep the Self-Calibrate VI in memory, you can minimize the memory leak by keeping a Timed Loop in memory. A memory leak will still exist, but it will be considerably smaller.

Reported Version: 1.9    Resolved Version: N/A    Added: 04/04/2013
150413 Signal generates at the NI PXIe-5450 CLK OUT connector when Reference Clock export is disabled

First setting the Reference Clock Export Output property to Clkout or NIRFSG_ATTR_REF_CLOCK_EXPORT_OUTPUT attribute to NIRFSG_VAL_REF_OUT_STR and then changing the Reference Clock Export Output property to Do Not Export Signal or NIRFSG_ATTR_REF_CLOCK_EXPORT_OUTPUT attribute to NIRFSG_ATTR_DO_NOT_EXPORT_STR still causes a signal to generate on the CLK OUT front panel connector.

Workaround: N/A

Reported Version: 1.4    Resolved Version: N/A    Added: 09/01/2011
248779 NI PXIe-5650/5651/5652 takes 10 ms to hit target power level when switching to the divide by 16 path

When switching to the divide by 16 path (any frequency between 100 MHz to 200 MHz) on the NI PXIe-5650/5651/5652, the output power behaves oddly. If you target 0 dBm on the device, the power starts off at approximately -25 dBm, but then overshoots to 10 dBm until it finally settles at approximately 0 dBm.

Workaround: N/A

Reported Version: N/A    Resolved Version: N/A    Added: 09/01/2011
389317

The niRFSG Self Calibrate Range VI execution time is greater than expected when using the NI PXIe-5644R, NI PXIe-5645R, and NI PXIe-5646R

In some instances, calling the niRFSG Self Calibrate Range VI or the niRFSG_SelfCalibrateRange function takes much longer than expected because of device settling, which can occur each time the device is reconfigured. When the VI or function executes, the RF IN and RF OUT connectors are configured twice. The connectors are configured once before and after execution where RF IN and RF OUT are reconfigured to their original states. Extended execution time is most noticeable when you repeatedly call the Self Calibrate Range VI or function for a single point, varying the frequency slightly for each call.

Workaround: Perform either of the following options as a workaround.

  • Call the niRFSG Self Calibrate Range VI or niRFSG_SelfCalibrateRange function only once for the entire frequency range so that device settling is minimized.
  • Configure and commit both NI-RFSA and NI-RFSG sessions to the desired frequency prior to calling the niRFSG Self Calibrate Range VI or niRFSG_SelfCalibrateRange function to minimize the call time.
Reported Version: 1.9    Resolved Version: N/A    Added: 02/18/2013
411948

Error –373104 occurs when a hyphen character is used in a configuration list name

When creating a configuration list in NI-RFSG on a VST, using hyphens in the configuration list name results in error -373104, "the specified configuration list name is invalid".

Workaround: Avoid using hyphen characters in configuration list names.

Reported Version: 1.9    Resolved Version: N/A    Added: 02/25/2014
387023

Error is not always reported when using duplicate names for NI-RFSG devices

NI-RFSG sometimes fails to report an error when you specify the same name in MAX for two different NI-RFSG devices.

Workaround: Perform either of the following options as a workaround.

  • Close and then reopen LabVIEW.
  • Use a unique name for each NI-RFSG device.
Reported Version: 1.9    Resolved Version: N/A    Added: 03/21/2013
364860

A deadlock can occur when creating two peer-to-peer streams between two devices in opposite directions concurrently

Workaround: To avoid the deadlock, serialize the calls to the niP2P Create Peer to Peer Stream VIs.

Reported Version: 1.9    Resolved Version: N/A    Added: 04/05/2013
371227

The test panel does not launch in MAX

Installing NI-RFSG Runtime 1.9 or later on a system with NI-RFSG 1.8 installed causes the MAX test panel to fail to launch.

Workaround: Install the NI-RFSG Soft Front Panel 1.9.5 from ni.com/updates.

Reported Version: 1.9    Resolved Version: N/A    Added: 02/18/2013
386372

Some devices do not appear in the device control of NI-RFSG Express VI dialog boxes

NI-RFSG Express VIs are not currently supported for the NI 5644R/5645R/5646R or the NI 5654/5654 with NI 5696.

Workaround: N/A

Reported Version: 1.9    Resolved Version: N/A    Added: 04/04/2013
480525

Windows 8.0 to Windows 8.1 upgrade issue

Upgrading the version of Windows on a system with NI-RFSG installed may result in the loss of device names, the loss of device configuration, and/or devices appearing disconnected. For more information about how to resolve this issue, visit ni.com/info and enter the Info Code excrxm.

Workaround: N/A

Reported Version: 14.0    Resolved Version: N/A    Added: 07/01/2014
389561

Uninstalling NI-RFSG leaves an empty folder in the Start menu

After you uninstall NI-RFSG 1.9 or later, an empty NI-RFSG item is stored under the National Instruments folder in the Start menu location at Start»All Programs»National Instruments.

Workaround: Manually delete the empty NI-RFSG folder.

Reported Version: 1.9    Resolved Version: N/A    Added: 02/18/2013
192893 Table of contents not locating

When linking to a topic in the NI RF Signal Generators Help from the LabVIEW context help or opening the help file from a VI within LabVIEW, the NI RF 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: 1.6    Resolved Version: N/A    Added: 08/03/2010
238196 Warning about active content

Microsoft Windows security feature that asks users whether or not to allow active content on their computer when launching certain pages from the driver media.

Workaround: Select Yes when the active content warning appears.

Reported Version: 1.7    Resolved Version: N/A    Added: 08/26/2011


Related Topics:

 

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