이 내용은 고객님의 설정 언어로 확인할 수 없습니다

이 내용은 다른 사용 가능한 언어로 표시됩니다. 고객님께서 사용하시는 브라우저에 텍스트 번역에 도움이되는 기능이 포함되어 있을 수 있습니다.

Cannot connect to USRP 2974

Updated Nov 24, 2020

Reported In

Hardware

  • USRP-2974

Software

  • LabVIEW Communications System Design Software
  • LabVIEW Communications System Design Suite

Issue Details

I am trying to connect to my USRP 2974 and it does not show up in MAX. How do I connect the USRP 2974 to my computer?

Solution

The USRP 2974 will not appear in MAX. The device can be added to LabVIEW Communications projects through the SystemDesigner. Instructions for this is located on page 6 of the USRP 2974 Getting Started Guide. If you are not able to add your device according to the instructions in the Getting Started Guide, follow the steps below to troubleshoot.
  1. First confirm that the version of your software supports USRP 2974. The USRP 2974 is only supported in LabVIEW Communications System Design Suite 2.0 and later. It is not supported in LabVIEW. For drivers, the NI-USRP 17.2 driver is the first version to add support for the USRP 2974. Please check driver readme to ensure that your version of the NI-USRP driver supports the USRP 2974 and is compatible with the version of LabVIEW Communications you're using. 
  2. Since the USRP 2974 has a Real-Time Controller built in, you will have to go through the process of provisioning the USRP device for Real-Time use with LabVIEW Communications. Instructions for this process is contained in the tutorial "Provisioning a Real-Time Controller or USRP Stand-Alone Device for LabVIEW Communications".
  3. Try connecting to the device through a router. If you must connect the device directly to your computer through ethernet, you will have to bring down the eth1 interface in order to add the device in SystemDesigner. Instructions on how to implement this workaround can be found in the known issues list for the NI USRP Driver.
  4. Try to ping your device's IP address. To find the IP address of your device, follow instructions on page 8 of the USRP 2974 Getting Started Guide. If you can ping the IP address than it means that your physical connection is good but maybe something is blocking specific traffic from the USRP to your computer or from your computer to the USRP. In this case you might want to try normal network troubleshooting like disabling your firewall. To check the ports that NI software and hardware needs to operate, please refer to the whitepaper "Configuring Software and Hardware Firewalls to Support National Instruments Products"
  5. If you are using LabVIEW Communications System Design Suite 2.0 or 2.1, and getting "The Network Systems manager failed to initialize." while discovering the remote hardware target as shown below.
Ensure the services below are running. If either one of the services cannot be found, reinstall LabVIEW Comms 2.0 or 2.1.
  • NI Systems Management Service
  • NI Skyline Database
  • RabbitMQ
If these services are running and the error still present, change both NI Systems Management Service and NI Skyline Database services startup type as "Automatic (Delayed Start)". Then restart PC.
  1. If you are using NXG 3.0 or later version. And you got "Error-NI Systems Management Server is not installed or running on the machine". You will only find NI SystemLink Service Manager. Make sure the the status in NI MAX is "local and remote".


After following the steps above, you can confirm whether or not the USRP 2974 is properly connected by running the "USRP-2974 Single-Device Streaming" example in LabVIEW Communications. If you still have trouble connecting to your device, please contact NI Support. 
 

Additional Information

If you are affected by Known Issue 712296 when directly connecting USRP 2974 to your computer, it is possible to have a script run at startup to disable the eth1 interface automatically. To implement this, please follow the Tutorial: Installing Startup Scripts on NI Linux Real-Time.

The Linux command to disable the eth1 interface is "ifconfig eth1 down" which allows the communication to go to eth0 instead.