黑龙江佳木斯射频子板1-250MHZTX无线系统VERT2450如何安装招商_钻头_云商网产品信息
您好, 欢迎来到云商网!
黑龙江佳木斯射频子板1-250MHZTX无线系统VERT2450如何安装招商
产品价格：
请联系咨询
发布时间：
行业类别：
郑重提示：
发布企业：
发布 IP ：
详细介绍 ()
润创工业科技有限公司为您提供佳木斯射频子板1-250MHZTX无线系统VERT2450如何安装招商。产品简介:详细信息 USRP N210包括：- USRP N210主机一台。- 2条SMA头 - 以太缆一条 - USRP N210系列提供高带宽，大动态范围处理能力。这款USRP N210是专为高要求的通信应用和快速发展所的。产品内部包括一个Xilinx的Spartan3A-DSP3400 FPGA，100 MSPS的双通道ADC，400 MSPS的双通道DAC以及通过千兆以太网将数据传输到主处理器。模块化的设计允许USRP N210在从直流至6 GHz频率范围工作，同时通过扩展端口可以将多个USRP N210系列同步以组成MIMO系统。GPDSO选件模块为多个USRP N200设备提供误差在0.01 ppm范围内GPS参考时钟。USRP的N210能把高达50MHz的射频带宽传输给主机。用户可以在FPGA架构内或者上的32位RISC软核中实现自定义功能。USRP N210比USRP N200提供一个更大容量的FPGA在要求额外的逻辑的应用、和DSP的资源。该FPGA能够处理上下行各100MHz的射频_。可以通过千兆以太网更新FPGA固件。1、黑龙江佳木斯射频子板1-250MHzTx 无线系统VERT2450 如何安装热门搜索:无线电平台LP0410【河北德科机械设备有限公司】2015价值机械品牌★★工业产品推荐★★机械行业产品★★消费者品牌★★2015年工业品先进单位★★拨打电话请告诉我产品订货号，热线：【】2、黑龙江佳木斯射频子板1-250MHzTx 无线系统VERT2450 如何安装多种型号图片
型号:JX166534通用软件无线电平台LP0410
型号:JX166506射频子板1-250MHzTx
型号:JX166504通用软件无线电平台USRPN210
【黑龙江佳木斯射频子板1-250MHzTx 无线系统VERT2450 如何安装一共有★★30★★多种型号以上只显示1-3种型号，如没有合适您的产品请咨询 河北润创科技开发有限公司】3、黑龙江佳木斯射频子板1-250MHzTx 无线系统VERT2450 如何安装多种型号内容型号:JX166534通用软件无线电平台LP0410详细信息 LPMHz到1 GHz的对数周期的PCB定向，增益为5-6dBi。可与任何工作在400 MHz 至 1 GHz频率范围内的子板配套。提供SMA接口，但需要自己将其焊接上去。栏目页面:/product/3611.html来源网址:/chanpin/xx-166534.html型号:JX166506射频子板1-250MHzTx详细信息 BasicTx子板是一个低成本的射频发射子板，工作频率为1 250MHz。该产品采用两个宽带，从而为USRP双通道DAC输出提供两个50-ohm SMA接口。当所需输出的频率超出USRP DAC所承受的范围时（100 MHz或200 MHz），BasicTX的宽带宽处理能力能让USRP在Subsampling模式下工作的带宽。BasicTX的每路输出既可以是独立的也可以合并成完整的I/Q_。值得注意的是在使用subsamling模式下要采用适当的滤波处理。典型应用包括发射子板连同外置的射频前端，直接发射通过带通的基带_或者定制的子板开发。栏目页面:/product/3611.html来源网址:/chanpin/xx-166506.html型号:JX166504通用软件无线电平台USRPN210详细信息 USRP N210包括：- USRP N210主机一台。- 2条SMA头线缆 - 以太网线缆一条 - 电源USRP N210系列提供高带宽，大动态范围处理能力。这款USRP N210是专为高要求的通信应用和快速发展所设计的。产品内部包括一个Xilinx的Spartan3A-DSP3400 FPGA，100 MSPS的双通道ADC，400 MSPS的双通道DAC以及通过千兆以太网将数据传输到主处理器。模块化的设计允许USRP N210在从直流至6 GHz频率范围工作，同时通过扩展端口可以将多个USRP N210系列同步以组成MIMO系统。GPDSO选件模块为多个USRP N200设备提供误差在0.01 ppm范围内GPS参考时钟。USRP的N210能把高达50MHz的射频带宽传输给主机。用户可以在FPGA架构内或者主板上的32位RISC软核中实现自定义功能。USRP N210比USRP N200提供一个更大容量的FPGA在要求额外的逻辑的应用、内存和DSP的资源。该FPGA能够处理上下行各100MHz的射频_。可以通过千兆以太网更新FPGA固件。栏目页面:/product/3611.html来源网址:/chanpin/xx-166504.html联系方式:刘经理电话:QQ:温馨提示：
润联为您提供详细的产品价格、产品图片等产品介绍信息，您可以直接联系厂家获取产品的具体资料，联系时请说明是在润联看到的，并告知型号
&&&& 联系我们时请一定说明是在云商网上看到的此信息，谢谢！
&&&& 联系电话：，欢迎您的来电咨询！
&&&& 本页网址：
&&&& 推荐关键词：
缓存时间： 12:26:44
免责声明：“黑龙江佳木斯射频子板1-250MHZTX无线系统VERT2450如何安装招商”信息由相关发布企业发布，云商网对此不对信息真伪提供担保。
风险防范建议：合作之前请先详细阅读本站。云商网保留删除上述展示信息的权利；我们欢迎您举报不实信息，共同建立诚信网上环境。
本站图片和信息均为用户自行发布，用户上传发布的图片或文章如侵犯了您的合法权益，请与我们联系，我们将及时处理，共同维护诚信公平网络环境！
Copyright & 2010
&公安机关备案号：<font color="#
缓存时间： 12:28:03在&UHD&下使用&USRP2&和&N&系列
将映像文件装入 SD
卡中(仅对 USRP2)
谨慎使用命令 usrp2_card_burner.py。如若指向错误的设备节点，可能会重写硬盘。请确认 --dev= 指向 SD 卡。
提示! 尽管理论上 USRP2 可以使用第三方 SD
卡。但是有些类型的 SD 卡不能同 CPLD 进行交互：
该卡可能是 SDHC，它不支持同 CPLD 的交互。
该卡有意外的时间特性。
鉴于上面的这些因数，建议使用随机的 SD
/share/uhd/utils/usrp2_card_burner_gui.py
cd /share/uhd/utils
./usrp2_card_burner.py --dev=/dev/sd --fpga=
./usrp2_card_burner.py --dev=/dev/sd --fw=
使用选项 --list 可获取可能的原始设备清单。list 将会剔除容量太大无法装入 SD
卡的磁盘扇区和设备。Linux, Mac OS X, 和 Windows 都具有该 --list 选项。
windows 烧卡工具
/share/uhd/utils/usrp2_card_burner_gui.py
将映像文件装入板上闪存中 (仅对 USRP-N 系列)
系列产品可以通过网络进行重新编程来更新或更改固件（firmware）和 FPGA
映像（images）。但每当在更新映像（images）过程中，总是在系统重新启动（power
cycling）之前对 FPGA
和固件两者的映像烧结。这便可确保设备一旦被重启，其映像文件与之配套。
的网络烧卡工具
/share/uhd/utils/usrp_n2xx_net_burner_gui.py
cd /share/uhd/utils
./usrp_n2xx_net_burner.py --addr=
./usrp_n2xx_net_burner.py --addr=
Windows 的网络烧卡工具
/share/uhd/utils/usrp_n2xx_net_burner_gui.py
设备的恢复 - Device recovery
and bricking
载入有问题的映像文件可能会招致设备处于无法工作的状态。幸运的是，USRP-N
系列可以启用安全（只读）映像模式。如若启用安全映像模式，用户便可试图再次装入映像文件。
壳体内的按钮（S2)便是安全模式按钮。在上电启动过程中按下该按钮便可启动安全映像模式。持续按住该按钮直到前面板的
LED 从闪烁到稳定（blink and remain
在安全模式中，USRP-N 设备的 IP
地址总是 192.168.10.2 。
配置网络 - Setup
networking
仅支持千兆级以太网，所以其无法同 10/100 Mbps
接口直接相互工作。尽管如此，10/100 Mbps 接口还是可以通过一个千兆级的以太网交换机间接同
USRP2 相连接。
配置主机接口
- Setup the host interface
的通过千兆级以太网的通信是基于 IP/UDP 层。其缺省 IP 地址为
192.168.10.2。这样只需配置计算机侧一个静态 IP
地址便可使其相互通信。推荐使用 IP 地址 192.168.10.1 和子网掩码
255.255.255.0.
备注：在使用 UHD 情况下，如若 USRP2
的 IP 地址没有被指定，应用软件便会使用 UDP
广播的数据包来定位 USRP2。存在这样一些情况，防火墙软件会阻碍 UDP
广播的数据包。在此建议更改或取消防火墙相关功用。
单口多机化 - Multiple devices per
为最大化数据处理能力，建议一个以太网接口配置一台
USRP2 设备。尽管如此，通过千兆级的交换机也可以同多台设备相互连接。无论哪种情况，每个以太网接口单元都必须有自己的子网，其相关的
USRP2 的地址应当处于其子网范围内。例如：
USRP2 设备 0 的配置:
以太网接口 IPv4 地址:
192.168.10.1
以太网接口子网掩码: 255.255.255.0
USRP2 设备的 IPv4 地址:
192.168.10.2
USRP2 设备 1 的配置:
以太网接口 IPv4
192.168.20.1
以太网接口子网掩码: 255.255.255.0
USRP2 设备的 IPv4
192.168.20.2
更改 USRP 的 IP 地址 - Change
the USRP2's IP address
基于下面可能的原因需要对 USRP2 的 IP
地址进行更改：
满足特定的网络配置要求
在同一宿主计算下使用多台 USRP2
使用（用户）熟知的 IP 地址（以防遗忘）
方法 1: 更改 USRP2 IP
地址的先决条件是必须清楚其正在使用的地址，网络也必须如上所述地被恰当的配置成功。然后运行下面的命令：
cd /share/uhd/utils
./usrp_burn_mb_eeprom
--args= --key=ip-addr --val=192.168.10.3
(仅适用于 Linux): 此方法假定在对设备现在使用的 IP 地址不清楚的情况下。它使用以太网的原始数据包短接（bypass）
IP/UDP 协议层而直接同 USRP2
通信。如下运行命令：
cd /share/uhd/utils sudo
./usrp2_recovery.py
--ifc=eth0 --new-ip=192.168.10.3
通信问题 - Communication
首次构建一个开发平台时，碰到各种各样的 USRP
通信问题是不足为奇的。下面便是一些简化的问题和诊断的建议。
防火墙 - Firewall issues
在 没有配置设备的
IP 地址的情况下，设备查询机制便会通过各个以太网接口广播 UDP
数据包来试图建立相互间的通信。众多防火墙会阻碍对这些广播信息的反馈。如若（如此，只能）禁止系统的防火墙功能、或明晰需确认的设备的 IP
地址。在此情况下的建议是：要么关闭防火墙、要么建立一个规则为端口号为 49152 的 UDP
的数据源建立通道。
“Ping” 设备 - Ping the
响应 icmp echo 。 成功的 ping
意味着设备已经被成功地启动，也意味着希望的 IP 地址被成功的配置。
ping 192.168.10.2
监视串口 - Monitor the serial
serial port to get debug verbose from the embedded microcontroller.
The microcontroller prints useful information about IP addresses,
MAC addresses, control packets, fast-path settings, and
bootloading. Use a standard USB to 3.3v-level serial converter at
230400 baud. Connect GND to the converter ground, and connect TXD
to the converter receive. The RXD pin can be left unconnected as
this is only a one-way communication.
Serial port located on the rear edge
Serial port located on the left side
监视主网流量 - Monitor the
host network traffic
Use wireshark
to monitor packets sent to and received from the
赋予设备地址 - Addressing the
单一设备的配置 - Single device
configuration
single-device configuration, the USRP device must have a unique
IPv4 address on the host computer. The USRP can be identified
through its IPv4 address, resolvable hostname, or by other means.
See the application notes on . Use this
addressing scheme with the single_usrp interface.
device address string representation for a USRP2 with IPv4 address
192.168.10.2 addr=192.168.10.2
多台设备的配置 - Multiple
device configuration
multi-device configuration, each USRP device must have a unique
IPv4 address on the host computer. The device address parameter
keys must be suffixed with the device index. Each parameter key
should be of the format . Use this addressing scheme with the
multi_usrp interface.
The order in which
devices are indexed corresponds to the indexing of the transmit and
receive channels.
The key indexing
provides the same granularity of device identification as in the
single device case.
device address string representation for 2 USRP2s with IPv4
addresses 192.168.10.2 and 192.168.20.2
addr0=192.168.10.2,
addr1=192.168.20.2
使用 MIMO 电缆 - Using the MIMO
cable allows two USRP devices to share reference clocks, time
synchronization, and the ethernet interface.
共享网络模式 - Shared
ethernet mode
shared ethernet mode, only one device in the configuration can be
attached to the ethernet. This device will be referred to as the
master, and the other device, the slave.
master provides reference clock and time synchronization to the
passing between the host and the slave is routed over the MIMO
master and slave must have different IPv4 addresses in the same
master and slave may be used individually or in a multi-device
configuration.
clocking is optional, and should only be supplied to the master
of slave and master may be switched with the "mimo_mode" device
address (see dual ethernet mode).
device address string representation for 2 USRP2s with IPv4
addresses 192.168.10.2 (master) and 192.168.10.3
-- Multi-device example
addr0=192.168.10.2,
addr1=192.168.10.3
-- Two single devices example
addr=192.168.10.2
addr=192.168.10.3
双网模式 - Dual ethernet
ethernet mode, both devices in the configuration must be attached
to the ethernet. One of the devices in the configuration will be
configured to provide synchronization. This device will be referred
to as the master, and the other device, the slave.
master provides reference clock and time synchronization to the
devices require the special device address argument "mimo_mode"
master and slave must have different IPv4 addresses in different
master and slave may be used individually or in a multi-device
configuration.
clocking is optional, and should only be supplied to the master
device address string representation for 2 USRP2s with IPv4
addresses 192.168.10.2 (master) and 192.168.20.2
-- Multi-device example
addr0=192.168.10.2, mimo_mode0=master,
addr1=192.168.20.2, mimo_mode1=slave
-- Two single devices example
addr=192.168.10.2,
mimo_mode=master
addr=192.168.20.2,
mimo_mode=slave
硬件配置注解 - Hardware setup
前面板指示灯 - Front panel
on the front panel can be useful in debugging hardware and software
issues. The LEDs reveal the following about the state of the
transmitting
mimo cable link
firmware loaded
reference lock
CPLD loaded
参考时钟 -
external 10MHz reference clock, square wave will offer the best
phase noise performance, but sinusoid is acceptable. The reference
clock requires the following power level:
PPS - Pulse Per
PPS signal for timestamp synchronization requires a square wave
signal with the following amplitude:
PPS input with the following app:
device address arguments (optional if only one USRP is on your
/share/uhd/examples
./test_pps_input
内部 GPS 伺服时钟 - Internal
Please see
the GPSDO application note for information on configuring and using
the internal GPSDO.
Installation
instructions:
the daughterboard.
jumper on the motherboard from 1-2 to 2-3 in order to switch from
external 10 MHz Ref Clock to GPSDO’s 10 MHz Ref
GPSDO module in place with the screws provided. The screws are
treated to avoid loosening with vibration.
the GPSDO power cable to J509 on the motherboard, and then to
connector D on the GPSDO module
an SMB to SMA cable between connectors B and J506
an SMB to SMA cable between connectors C and J507 (CLK
the serial cable between connectors A and J312 (RS232-3) on the
motherboard. If J312 on your USRP isn’t a keyed connector, please
ensure to connect pin1 (TX) of connector A to pin3 (RX) on
the washer and nut from the MMCX to SMA-Bulkhead cable. Connect it
to connector E and then insert SMA-Bulkhead connector through the
hole in the rear panel. Tighten nut to fasten in
the daughterboard pushing all the cables
underneath.
the following commands:
cd /share/uhd/utils
./usrp_burn_mb_eeprom --args=
--key=gpsdo --val=internal
instructions:
the jumper setting, disconnect the cables, and unscrew the GPSDO
unit. Then run the following commands:
cd /share/uhd/utils
./usrp_burn_mb_eeprom --args=
--key=gpsdo --val=none
The GPSDO is
capable of supplying a 3V for active GPS antennas or supporting
passive antennas
杂类 - Miscellaneous
可选传感单元 - Available
following sensors are available for the USRP2/N-Series
they can be queried through the
mimo_locked - clock reference locked
over the MIMO cable
ref_locked - clock reference locked
(internal/external)
- GPS epoch seconds (available when GPSDO
installed)
gps_locked - GPS lock
多接收链路 - Multiple RX
two complete DDC chains in the FPGA. In the single channel case,
only one chain is ever used. To receive from both channels, the
user must set the RX subdevice specification. This hardware has
only one daughterboard slot, which has been aptly named slot
following example, a TVRX2 is installed. Channel 0 is sourced from
subdevice RX1, channel 1 is sourced from subdevice
usrp-&set_rx_subdev_spec("0:RX1
from:/usrp2uhdmanual
已投稿到：
以上网友发言只代表其个人观点，不代表新浪网的观点或立场。NI-USRP 14.0 Known Issues List - National Instruments
NI-USRP 14.0 Known Issues List
This document contains the NI-USRP known issues that were discovered before and since the release of NI-USRP 14.0.
Not every issue known to NI
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 /kb/ and enter the KnowledgeBase number in the search field to locate the specific document.
Reported Version - The earliest version of NI-USRP in which the issue was reported. If you discover the issue appears in an earlier version of NI-USRP 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
Known Issue
You cannot use RIO aliases to identify NI 294x/295x devices in the NI-USRP API.
You can create a RIO alias in NI MAX for NI 294x/295x devices connected using the MXI Express interface. RIO aliases are usable when you open a LabVIEW FPGA reference to these devices but they are not usable from the NI-USRP API in the device names input in the niUSRP Open Rx Session VI and the niUSRP Open Tx Session VI.
Workaround: Use the standard RIO name, such as "rio0", in the device names input of the niUSRP Open Rx Session VI and the niUSRP Open Tx Session VI.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 09/23/14
After you run a NI-USRP VI which commits an existing niUSRP Tx session, opening a second niUSRP session occasionally takes more than 60 seconds.
Running a VI which commits settings to an existing Tx session, such as niUSRP Configure Signal.vi, may delay the opening of another niUSRP session (using niUSRP Open Rx Session.vi or niUSRP Open Tx Session.vi).
Workaround: Call niUSRP Open.vi on all of the sessions that you want to open before calling any other niUSRP VI.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
Tx sessions may underflow after you start an Rx session with NI 294x/295x devices connected using MXI Express cables.
If you start an Rx session with an outstanding Tx session already streaming, the Tx session may underflow if both sessions are on NI 294x/295x devices connected using MXI Express cables.
Workaround: Start the Rx and Tx sessions before you start streaming.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
An LO locking error occurs on channel one on your NI 294x/295x devices.
When you query an attribute from the NI-USRP driver before you configure any parameters, an LO locking error occurs on channel one on your NI 294x/295x devices.
Workaround: Set the Enabled Channels property before you query any attribute and immediately after opening a session.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
Error -61083 and corrupted data can occur when you use clocks derived from the data clocks.
The data clock of the NI 294x/295x 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.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
The NI-USRP Configuration Utility may incorrectly report that an image update is needed for NI USRP-292x/293x devices already in use.
If an NI 292x/293x 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.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
NI 292x/293x devices may not return an error if an external reference signal is missing.
When an NI 292x/293x 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.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
The niUSRP Find Devices VI will occasionally return incorrect information when a session is open to a USRP device.
When running the niUSRP Find Devices VI while a session is open to a USRP device connected to the system, it will occasionally return incorrect information.
Workaround: Ensure all sessions are closed when you run the niUSRP Find Devices VI.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
Alternating use of NI 293x/292x devices connected with MIMO cables in LabVIEW 32-bit and LabVIEW 64-bit can cause the USRP devices to appear disconnected from the system.
This issue may occur when you run applications on multiple NI 293x/292x devices connected with MIMO cables, alternating between LabVIEW 32-bit and LabVIEW 64-bit. The devices appear to be disconnected from your system. This is due to improper releasing of the USRP resources.
Workaround: Close both LabVIEW instances and cycle power to the USRP devices.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
Configuring the Rx Reference Level on NI 294x/295x devices results in an incorrect reference level setting.
When you configure the Rx reference level, as demonstrated in the Simple NI-USRP Streaming Sample Project, using the Configure Signal (Level) VI, the niUsrpRio Configuration IDL may report the following error: Error - occurred at niUsrpRio Config v1 Host.lvlib:Calculate Gain Setting.vi: "Specified reference level or output power exceeds the characterized capabilities of the device." In other cases, no error is reported, but the resulting reference level may be incorrect. In this case, the "Coerced Vertical Range [Vpp]" returned by the Configure Signal (Level) VI may be off by 7 dB to 20 dB and the niUsrpRio Configuration IDL will program the hardware gain incorrectly by the same factor.
Workaround: 1) Use Configure Signal (Gain).vi and set a gain of 0 dB to 30 dB. Do not configure the Rx reference level. 2) Install NI-USRP 14.0 and run \LabVIEW Targets\FPGA\USRP\niusrprio_tools.llb\Update Device Correction Data.vi. This VI will correct the Rx gain correction data in persistent storage on the device to correct the problem. You need only to run this VI once per device.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
Two channel acquisition (Rx) on a single NI 294x/295x device is not aligned.
When you configure a single device for a multi-channel acquisition (Rx), if you use a Time Start Trigger (niUSRP Configure Trigger.vi) the time must be set on both channels of the device using niUSRP Set Time.vi. If the "apply timestamp" parameter is set to "Now" there may be a misalignment between the channels. Set the "apply timestamp" parameter to "Next Timebase Edge".
Workaround: Set the "apply timestamp" parameter of the niUSRP Set Time.vi to "Next Timebase Edge" for a single-device, multi-channel acquisition with a Time Start Trigger.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
NI-USRP may return incorrect or empty GPS NMEA strings.
If you repeatedly query the GPS Sentence GGA and GPS Sentence RMC properties from the NI-USRP driver, the driver may return an incorrect or empty string.
Workaround: Query the property again if it returns an empty or obviously incorrect string. Alternately, always query the attributes in this order:
GPS Time (seconds)
GPS Sentence RMC
GPS Sentence GGA
GPS Lock Status
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 09/23/14
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.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 09/23/14
Error - "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.
If you set Timebase Clock Source to PpsIn and do not provide a timebase clock source to PPS IN, the USRP device will revert back to its internal timebase clock source. This may result in error - "A stream command was issued in the past."
Workaround: Provide a timebase clock source to the PPS IN port.
Reported Version: 14.0
  
Resolved Version: N/A
  
Added: 09/23/14
"A stream command was issued in the past" or "Packet had timestamp that was late (or too early)" errors can occur with MIMO synchronization.
In an Rx session, the error message reads "A stream command was issued in the past." In a Tx session, the error message reads "Packet had timestamp that was late (or too early)." This issue occurs only when all of the following conditions are met:
The slave device has a GPSDO.
The niUSRP Set Time VI is called only on the master.
The timestamp is applied immediately.
Workaround: Avoid this error by implementing any of the following solutions:
Add a one-second wait anywhere after you open a Tx or Rx session but before the niUSRP Initiate VI.
Configure the niUSRP Set Time VI to apply the timestamp at the next timebase edge.
Call the niUSRP Set Time VI on both channels.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 05/07/14
The NI-USRP help does not contain an AUX I/O front panel connector pin-out diagram for the NI 294x/295x devices.
Workaround: Refer to /manual/page_usrp_x3x0.html#x3x0_hw_gpio. The AUX I/O lines in LabVIEW FPGA correspond to the Data[xx] lines in the Pin Mapping section.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 05/19/14
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:
": 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.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 05/07/14
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:
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.
You call the niUSRP Set Time VI after you call the niUSRP Initiate VI when receiving.
Workaround: 
Refer to the Data Streaming Performance Tips topic in the NI-USRP Help for more information about improving streaming performance over Ethernet.
Do not call the niUSRP Set Time VI after calling the niUSRP Initiate VI.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 05/19/14
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.
Reported Version: 1.0
  
Resolved Version: N/A
  
Added: 05/19/14
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.
Reported Version: 1.0
  
Resolved Version: N/A
  
Added: 05/19/14
There is a large transient time at the beginning of a Tx session or Rx session when you use the NI R.
There is a ~110 μs to 130 μs transient at the beginning of a Tx session or Rx session when you use the NI R 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.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 05/07/14
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.
Workaround: Design your application to discard the first 24 samples and 130 μs of transient data.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 05/07/14
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 incorrectly return a value of 1 in the fractional seconds element of the USRP Timestamp 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.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 05/07/14
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.
Reported Version: 1.3
  
Resolved Version: N/A
  
Added: 05/07/14
Opening an FPGA reference fails with error -63150 on NI 294x/295x devices.
The Open FPGA VI Reference and Open Dynamic Bitfile Reference nodes fail with error -61350 on NI 294x/295x 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.
Reported Version: 1.0
  
Resolved Version: N/A
  
Added: 05/07/14
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.
Reported Version: 1.1
  
Resolved Version: N/A
  
Added: 09/23/14
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
Reported Version: 1.1
  
Resolved Version: N/A
  
Added: 05/07/14
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.
Reported Version: 1.1
  
Resolved Version: N/A
  
Added: 05/10/12
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 - 2.2 GHz.
NI- GHz - 2.5 GHz; 4.9 GHz - 4.9 GHz.
Reported Version: 1.0
  
Resolved Version: N/A
  
Added: 09/16/11
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.
Reported Version: 1.0
  
Resolved Version: N/A
  
Added: 09/16/11
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.
Reported Version: 1.0
  
Resolved Version: N/A
  
Added: 09/16/11
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
to contact us. Also contact us if you find a workaround for an issue that is not listed in the document.
书签收藏和分享
本网站使用cookies来为您提供更好的浏览体验。
