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.
Each issue appears as a row in the table and includes the following fields:
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 466351 |
"A stream command was issued in the past" or "Packet had timestamp that was late (or too early)" errors can occur with MIMO synchronization.
| |||||
| 465821 | The NI-USRP help does not contain an AUX I/O front panel connect pin-out diagram for the NI USRP-294x/295x devices. The documentation does not contain a pin-out diagram for the AUX I/O connector. Workaround: Refer to http://files.ettus.com/uhd_docs/manual/html/gpio_api.html for a pin-out diagram for the NI 294x/295x AUX I/O connector.
| |||||
| 460810 | 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<ERR>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."
| |||||
| 460704 | 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: 1) High network traffic or high streaming rates are occurring over Ethernet. Some network cards collate network packets out-of-order in these situations, and the NI-USRP driver reports errors in this case. For example, the Intel 82579LM network controller chipset is known to exhibit this behavior with the NI-USRP driver. 2) You call the niUSRP Set Time VI after you call the niUSRP Initiate VI when receiving. Workaround: 1) Refer to the Data Streaming Performance Tips topic in the NI-USRP Help for more information about improving streaming performance over Ethernet. 2) Do not call the niUSRP Set Time VI after calling the niUSRP Initiate VI.
| |||||
| 460113 | Hibernation is not supported for the NI 294x/295x devices over PCI Express. NI 294x/295x devices do not support hibernation when connected over PCI Express. When resuming from hibernation, NI 294x/295x devices may not work. Workaround: Cycle power to the NI 294x/295x devices and the host machine.
| |||||
| 460109 | Sleep is not supported for the NI 294x/295x devices over PCI Express. NI 294x/295x devices do not support sleep when connected over PCI Express. When resuming from sleep, NI 294x/295x devices may not work or the host machine may become unstable. Workaround: Cycle power to the NI 294x/295x devices and the host machine.
| |||||
| 458782 | There is a large transient time at the beginning of a Tx session or Rx session when you use the NI 2943R/2953R. There is a ~110-130 μs transient at the beginning of a Tx session or Rx session using the NI 2943R/2953R 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 | When you use NI-USRP and the NI 294x/295x devices, 24 samples of the previous acquisition are present at the beginning of a new acquisition. When you configure an Rx session, the first set of data retrieved from a fetch call will contain invalid data. Twenty-four samples and about 130 μs of transient data are left over from the previous Rx acquisition.This issue is present only when you use the NI-USRP API and the NI 294x/295x devices. Workaround: Design your application to discard the first 24 samples and 130 μs of transient data.
| |||||
| 456805 | The niUSRP Get Time VI returns a fractional seconds value of 1. If you use the niUSRP Get Time VI with the when input set to previous timebase edge, the VI may return a value of 1 in the fractional seconds output. This output is incorrect and should be taken to mean 0. Workaround: Interpret a value of 1 in the fractional seconds output as a value of 0.
| |||||
| 456625 | 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.
| |||||
| 456268 | If a corrupt image exists on the flash of the NI USRP-294xR/295xR device, the NI-USRP Configuration Utility might crash and the PC might also crash.
The behavior of the device when a corrupt image exists on its flash is undefined and can cause software or system crashes. Exercise extreme caution when writing an image other than the one shipped with the driver to the flash of a device.
| |||||
| 360108 | 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 | 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 | 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 cycle power to the device and complete the reset action.
| |||||
| 311843 | NI-USRP incorrectly coerces carrier frequency for the NI 292x. If you set the carrier frequency to a value that is out of range for the NI 292x, NI-USRP does not coerce the carrier frequency to a value within range of the NI 292x. Workaround: Set the carrier frequency to a value within range of your device. Select values within the following ranges: NI 2920: 50 MHz to 2.2 GHz. NI 2921: 2.4 GHz to 2.5 GHz; 4.9 GHz to 4.9 GHz.
| |||||
| 310810 | 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:
| |||||
| 295724 | Transients exist for both Tx and Rx. For I/Q sampling rates that are divisible by two, 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.