Each issue appears as a row in the table and includes the following fields:
| ID | Known Issue | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 682721 Return | When changing the Host Data Type in a NI-USRP session in between acquisitions, an overflow is falsely reported. When acquiring with the NI-USRP API, changing the Host Data Type property after aborting an acquisition and then running another acquisition in the same session results in the false report of an overflow on the first packet. Workaround: To avoid the error, close your session and open a new session before changing the Host Data Type. To ignore the error for the first packet only, run niUSRP Clear Error and then continue acquiring.
| |||||||||||||||||||
| 681935 Return | When using the 2945/2955 Sample Project, aliases appear in the data path after the frequency shift occurs on the FPGA. The DSP in the NI-USRP Simple Streaming with USRP-2945/2955 Sample Project may fail to filter out signal aliases when a user-specified frequency shift is used. Workaround: Upgrade to NI-USRP 17.1 or later and generate a new sample project or do not use a user-specified frequency shift.
| |||||||||||||||||||
| 679121 Return | When using the 2945/2955 Sample Project, each digital data value is scaled to half of the correct value. The DSP in the NI-USRP Simple Streaming with USRP-2945/2955 Sample Project does not correctly scale the power by a factor of 2, resulting in digital data values with magnitudes half that of the correct I/Q values. Workaround: Upgrade to NI-USRP 17.1 or later and generate a new sample project or scale the data up by a factor of 2 on the Host or on the FPGA after the fractional decimator.
| |||||||||||||||||||
| 641880 Return | When using the USRP-2945/2955 device and the USRP RIO sample project, LO sharing may cause the RF frequency to be inaccurate. When using the USRP-2945/2955 and the USRP RIO sample project, configuring the device for LO sharing to RF 0 from RF 1 may cause RF 0 to tune to an incorrect RF frequency resulting in an apparent phase shift. If RF 0 is configured for Import and RF 1 is configured for Shared and Export, RF 0 may not be tuned to the correct frequency. Workaround: After configuration, use the Get LO Frequency TwinRX VI (Config Instrument Design Library (IDL)) to get the LO frequencies of the exporting channel. Then use the Configure LO TwinRX VI (Config IDL) to manually set the LO frequencies of the importing channels to the coerced frequency of the exporting channel.
| |||||||||||||||||||
| 626202 Return | When opening multiple new streaming sessions using the NI-USRP API to the same device, you may receive an error. When opening a streaming session, a DMA channel is reserved. If you try to open more sessions than there are DMA channels, you will receive the following error: "Trying to allocate more DMA channels than are available." This affects the transceiver USRP RIO devices when connected using PCIe. Workaround: Implement one of the following solutions:
| |||||||||||||||||||
| 624459 Return | In LabVIEW Communications 2.0, bitfile cannot be built using DRAM after installing NI-USRP. After installing NI-USRP in LabVIEW Communication 2.0, projects containing DRAM can no longer be compiled. Workaround: Contact NI technical support.
| |||||||||||||||||||
| 617872 Return | Continuous streaming performance of USRP RIO devices degrades when connected over PCIe and using NI-USRP API. Users of the USRP RIO API are not affected. Applications using the USRP RIO API involving the Application Frameworks, Sample Projects, and LabVIEW FPGA all use the USRP RIO API and thus are not affected. Nominal rates with NI-USRP 16.1 are the following:
Workaround: Implement one of the following solutions:
| |||||||||||||||||||
| 614923 Return | LabVIEW may crash when using USRP-2945/2955 and the NI-USRP API if configure frequency is called with a command time too far in the future. When using the USRP-2945/2955 with the NI-USRP API, LabVIEW will crash if there is an attempt to configure the frequency on a channel that has not yet been configured. This crash will only occur if the command time has been set more than 10 seconds in future and if an acquisition on another channel is already in progress. Workaround: Implement one of the following solutions:
| |||||||||||||||||||
| 610228 Return | On the USRP-2945/2955, a second harmonic LO spur may be observed when sharing LOs. On the USRP-2945/2955, if a channel's LO source is set to companion during an acquisition, there may be a spur observed in the received signal of that channel at twice the center frequency of the original channel settings. Workaround: Before setting an LO source to companion, tune the LO to a frequency such that the spur will not be near the new frequency of interest, or abort acquisition before attempting to change the LO source.
| |||||||||||||||||||
| 600668 Return | Rx transients when using the USRP-2944/2954 devices. Transients are observed on the received data when doing finite acquisitions using the USRP-2944/2954 devices. These transients are hardware-specific and have been observed to be around 20 ms to 50 ms in duration. Workaround: Throw away the initial transient samples after a finite acquisition.
| |||||||||||||||||||
| 595649 Return | When using LabVIEW Communications 2.0, the Rx Custom Sample Type and Size example is broken. The Rx Custom Sample Type and Size example is broken in LabVIEW Communications 2.0. Workaround: Change the broken property nodes from Active Channel to All Active Channel. Alternatively, you can save the project, close LabVIEW Communications 2.0, and reopen the project.
| |||||||||||||||||||
| 586927 Return | Subsequent configurations of the LO frequency require a delay to allow the clock to settle. Configuring the LO can require some transient time to settle. Data that was fetched or written during this settling period will be corrupted. This affects the niUSRP Configure Signal VI on the host side, as well as Configure Rx VI and Configure LO VI for USRP RIO sessions. Due to the race condition nature of the issue, the problem may not present itself in every application depending on parallel tasks running in the VI. Workaround: Place a delay on the order of 20 ms to 50 ms following configurations to the LO. These numbers were experimentally found, and may differ depending on the hardware or application.
| |||||||||||||||||||
| 562870 Return | NI-USRP Configuration Utility seems to hang when updating the image of a USRP. When updating an image on a USRP, the NI-USRP Configuration Utility seems to hang, and the application must be forced to close. Workaround: Updating the image can take up to 20 minutes, during which time the utility currently seems to hang. Please wait at least 20 minutes when attempting to update the image.
| |||||||||||||||||||
| 542084 Return | Invalid samples received after retuning the LO on a USRP-2944/2954 device. When retuning the receiver side of a USRP-2944/2954 device from a frequency above 1.5 GHz to a frequency below 1.5 GHz, the received signal takes around 200 ms to stabilize. Workaround: Either wait 200 ms between retuning the device and acquiring samples or discard the samples acquired during that period.
| |||||||||||||||||||
| 540599 Return | When you open an NI-USRP API session to a device that is already being used as a LabVIEW FPGA device with the niUsrpRio Configuration Instrument Design Library, errors result from the existing session. If you attempt to use the NI-USRP API to open a session to anUSRP RIO device when it is already being used as LabVIEW FPGA device, for example through a NI-USRP Simple Streaming sample project, your action can cause the session to terminate with an error. When you open an NI-USRP session to a device, the custom LV FPGA image on the device will be replaced with a default FPGA image that works with the NI-USRP driver, which will invalidate an open LV FPGA session open to that device. Workaround: Using both driver APIs (NI-USRP and the niUsrpRIO Configuration Instrument Design Library in the LabVIEW FPGA environment) simultaneously to configure the same device is not a supported use case.
| |||||||||||||||||||
| 539338 Return | The status of the USRP RIO Local Oscillator (LO) lock may be true even when the LO has not been configured. The LO lock status may be true even before you configure the LO frequency. The LO lock status is indeterminate before you configure any frequency. Workaround: Do not check the LO Locked status before you configure the frequency, because the status is indeterminate until the LO is configured. It is valid to check the status only after a frequency configuration is made.
| |||||||||||||||||||
| 532349 Return | Timed commands do not work with the USRP-2900/2901 device. Timed commands are currently not supported with the USRP-2900/2901 device. Workaround: N/A
| |||||||||||||||||||
| 528194 Return | Incorrect frequency coercion can result when you set the LO frequency to a non-default value on an USRP-2900/2901 device. If you set the LO frequency to a non-default value, an incorrect carrier frequency coercion can result if the absolute difference (offset) between the carrier frequency and the LO frequency is greater than half the data clock rate. For example, setting a LO frequency to 2 GHz and configuring a carrier frequency of 2.02 GHz or 20 MHz offset will result in incorrect carrier frequency coercion if the data clock rate is 32 MHz (which permits only 16 MHz offset). The maximum allowed offset is also limited by the maximum configurable DSP frequency and thus can be lower than the data clock rate/2 limit. Workaround: Set the Data Clock Rate to a value higher than twice the maximum offset that you intend to use. However, the Data Clock Rate has a maximum limit too. Or Do not use the LO frequency property node and instead use only the carrier frequency property, which will automatically set the LO frequency to a value appropriate to achieve the requested carrier frequency.
| |||||||||||||||||||
| 527016 Return | Setting the LO Frequency property node to the default value of -1 results in wrong carrier frequency coercion on the USRP-2901 device. When you set the LO Frequency property node to the default value of -1 and then set the carrier frequency, a wrong carrier frequency configuration may result on the USRP-2901 device. Workaround: Set the LO frequency property in the context of an active channel. For example, using the niusrp property node, first set the active channel and then set the LO frequency property below it.
| |||||||||||||||||||
| 519572 Return | Changing the I/Q rate can cause discontinuity in the time reported by the device. A change in I/Q rate value can cause a discontinuity in the time reported by the USRP-2900/2901 device. Change in the I/Q rate can cause an automatic change in the data clock rate, which influences the time maintained by the device. Workaround: Set the data clock rate property to a fixed value for e.g. 32M or 48M explicitly if you intend to change the I/Q rate in an application and rely on the time-stamps from the device to be continuous. Setting the the data clock rate however will restrict the I/Q rates that can be achieved. Another workaround is to explicitly set the time after making a change to the I/Q rate. You can use the niUSRP Set Time VI to do this. For example, read the time from the device using the niUSRP Get Time VI before changing the I/Q rate and set the time to that value after you change the I/Q rate using the niUSRP Set Time VI.
| |||||||||||||||||||
| 518489 Return | Repeatedly aborting and then initiating an NI-USRP session occasionally causes a packet timeout error with USRP-2900/2901 devices. Repeatedly initiating and aborting your NI-USRP session when using an USRP-2900/2901 device will occasionally result in a timeout error -1074118650. Workaround: Catch the error, then close and reconfigure your session.
| |||||||||||||||||||
| 488044 Return | Error -61083 and corrupted data can occur when you use clocks derived from the data clocks. The data clock of the USRP RIO is generated outside of the FPGA . You must configure the data clock before it is used by any FPGA logic, otherwise logic running from the derived clock could execute while the data clock configures, resulting in undefined behavior. The ability to derive clocks from the data clock has been disabled in NI-USRP 14.0. Workaround: Create derived clocks from the 40 MHz onboard clock instead of the data clocks. Because the onboard clock is not phase-locked to the data clock, you must add and test logic to ensure the clocks perform as intended.
| |||||||||||||||||||
| 487251 Return | The NI-USRP Configuration Utility may incorrectly report that an image update is needed for USRP-2920/2921/2922/2930/2932 devices already in use. If an USRP-2920/2921/2922/2930/2932 device is already in use, the NI-USRP Configuration Utility normally does not display the device. In some cases, the utility may show the device but display UPDATE NEEDED in the Image Status column. If the device is in use by another process or system, the FPGA/Firmware update may not be required. Refresh the devices list to verify that the device is visible and requires image updating. Workaround: Ensure that a device is not in use by another application or system before updating the FPGA and Firmware images with the NI-USRP Configuration Utility.
| |||||||||||||||||||
| 487061 Return | USRP-2920/2921/2922/2930/2932 devices may not return an error if an external reference signal is missing. When an USRP-2920/2921/2922/2930/2932 device is configured to use REF IN as the reference frequency source, but a reference signal is not applied on the REF IN port, the device may not generate an error in LabVIEW. Workaround: Provide a reference frequency source to the REF IN port.
| |||||||||||||||||||
| 469466 Return | Errors occur when you use multiple devices on different buses in a single session. When you use the NI-USRP API to open a session to multiple devices on different buses, for example one with Ethernet and one with PCI Express, various errors occur during execution after opening the session. The errors vary depending on whether the session is Rx or Tx. Workaround: Use devices only on a single bus in a single session.
| |||||||||||||||||||
| 467209 Return |
Error -107411864 "A stream command was issued in the past" occurs when you set Timebase Clock Source to PpsIn and do not provide a timebase clock source to the PPS IN port. Workaround: Provide a timebase clock source to the PPS IN port.
| |||||||||||||||||||
| 460810 Return | Runtime errors occur when you open one session to multiple devices and another session to a subset of those devices. The order in which you call the Open Tx Session VI and the Open Rx Session VI affects which error appears. For example, if you call the Open Tx Session VI with the names of device A and device B and then you call the Open Rx Session VI with the name of device A, the Write Tx Data VI returns the following error: "niUSRP Write Tx Data (2D CDB).vi. A runtime or configuration error occurred. Code: 1440 Details: RuntimeError: fifo ctrl timed out looking for acks" If you call the Open Rx Session VI with the names of device A and device B and then you call the Open Tx Session VI with the name of device A, the Fetch Rx Data VI returns the following error: "1074118650: Timeout exceeded before packet received or sent. Not all samples may have been received or sent. Consider increasing timeout." Workaround: Open an Rx and Tx session to the same list of devices. You can disable the unused channel in the session where you added it.
| |||||||||||||||||||
| 460704 Return | Out-of-sequence errors occur when you use NI-USRP over an Ethernet connection. The driver may report out-of-sequence errors in either of the following scenarios:
Workaround:
| |||||||||||||||||||
| 460113 Return | Hibernation is not supported for the USRP RIO devices over PCI Express. USRP RIO devices do not support hibernation when connected over PCI Express. When resuming from hibernation, USRP-294x/295x devices may not work. Workaround: Cycle power to the USRP RIO devices and the host machine.
| |||||||||||||||||||
| 460109 Return | Sleep is not supported for the USRP RIO devices over PCI Express.USRP RIO devices do not support sleep when connected over PCI Express. When resuming from sleep, USRP RIO devices may not work or the host machine may become unstable. Workaround: Cycle power to the USRP RIO devices and the host machine.
| |||||||||||||||||||
| 458782 Return | There is a large transient time at the beginning of a Tx session or Rx session when you use the USRP-2943/2953. There is a ~110 μs to 130 μs transient at the beginning of a Tx session or Rx session when you use the USRP-2943/2953 devices. Workaround: For Tx or Rx, pad the waveforms with sufficient 0 samples to cover the transient time and then throw out these 0 samples.
| |||||||||||||||||||
| 458163 Return |
When you use NI-USRP and the USRP RIO devices, 24 samples of the previous acquisition are present at the beginning of a new acquisition. Workaround: Design your application to discard the first 24 samples and 130 μs of transient data.
| |||||||||||||||||||
| 456625 Return | The niUSRP Fetch Rx Data VIs do not respect "channel list" control. The niUSRP Fetch Rx Data VI always returns data for all of the channels specified in the Enabled Channels property. You cannot enable multiple channels and then fetch data only from a single channel at a time. Workaround: Enable only the channels that you want to fetch data from at the same time.
| |||||||||||||||||||
| 442853 Return | Opening an FPGA reference fails with error -63150 on USRP RIO devices. The Open FPGA VI Reference and Open Dynamic Bitfile Reference nodes fail with error -61350 on USRP RIO devices if the FPGA image stored in the flash of the device is bad. Workaround: Update the FPGA image stored in the flash of the device with a known good image by running\vi.lib\LabVIEW Targets\FPGA\USRP\niusrprio_tools.llb\Write Bitfile to Flash.vi. The default FPGA image is stored at \NI-USRP\images\usrp_x310_fpga_HGS.lvbitx. Cycle power to the device and the host after you update the FPGA image of the device.
| |||||||||||||||||||
| 360108 Return | The niUSRP Write Tx Data VI sometimes ignores timeout if end of data? is TRUE. If you call the niUSRP Write Tx Data VI with end of data? set to TRUE, the driver might ignore the timeout. If you configured the device to start generating at a time that is later than the timeout, the driver will wait for the device to start generating, even if the wait time exceeds the timeout. Workaround: Do not set Start Trigger times that are further in the future than you want to wait.
| |||||||||||||||||||
| 349079 Return | Streaming performance for multi-device sessions is sometimes low. NI-USRP sessions configured to control multiple devices exhibit lower than expected streaming performance. The streaming rate for multi-device sessions should be approximately half that of single device sessions, but actual performance is less than half. For multi-device sessions, it is sometimes not possible to stream at high I/Q rates. Workaround: N/A
| |||||||||||||||||||
| 340767 Return | NI-USRP Configuration Utility fails to reset after you upgrade the firmware or FPGA. The utility reports that it was unable to reset the device after a firmware or FPGA upgrade. The upgrade was successful, but the reset action did not complete. Workaround: Unplug and replug the device to manually power cycle the device and complete the reset action.
| |||||||||||||||||||
| 310810 Return | NI-USRP returns one of the following errors during Tx: "Packet loss between host and device." or "Packet loss within a burst." A continuous Tx operation that uses a high I/Q sampling rate and a small waveform size per write creates a very large number of underflows. The underflows cause the operation to eventually error out with one of the packet loss errors. When one of these errors occurs, a packet has actually been dropped between the host and the device. Workaround: Implement one or more of the following changes: -Use a larger write size in each write call. -Use a smaller I/Q sampling rate, if possible. -Use a finite Tx operation that provides all the data in a single write call and sets the end of data? input of the write VI to TRUE, if possible.
| |||||||||||||||||||
| 295724 Return | Transients exist for both Tx and Rx. For I/Q sampling rates that are divisible by 2, transients may appear in the first 20 or so samples for both Rx and Tx. Workaround: For Tx, pad the end of each generated waveform with zeros to eliminate the transient samples at the beginning of the subsequent waveform generation. For Rx, acquire sufficient extra data before the expected beginning of the packet and discard the first 20 samples.
|
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.
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.