LabVIEW Communications 1.1 to 2.0 Migration Guide for General Projects

Publish Date: Sep 17, 2018 | 0 Ratings | 0.00 out of 5 | Print | Submit your review

Overview

This guide provides information and guidance for migrating existing LabVIEW Communications 1.1 applications to LabVIEW Communications 2.0 for General Projects. If you prefer to migrate over an existing application, this guide addresses known issues that may arise in the process. It is recommended to start with a new project in 2.0 and duplicate the original project in the newer version.

For an overview of new features and changes in LabVIEW Communications 2.0, see the New Features and Changes topic online.

Table of Contents

  1. How to Use This Guide
  2. General Projects
  3. Next Steps
  4. Revisions and Feedback 
  5. Additional Resources

1. How to Use This Guide

This document covers LabVIEW Communications 1.1 to 2.0 Migration Guide for General Projects. 

The guide is made up five documents covering the following topics: 

 

Each section discusses the required steps to migrate that specific type of project. For example, if you would like to migrate a USRP streaming project, you should navigate to the USRP Projects section for guidance. If your project does not fall into the first three categories listed above, you should navigate to the General Projects section. Each section is meant to be self-contained and used independently of the others, so redundant information may be included in multiple sections.

Note: Always back up a copy of the original project before attempting any migration efforts.

 

Back to Top

2. General Projects

This section describes the necessary changes needed if you want to reuse a general project that was created based on projects in LabVIEW Communications 2.0. For details specific to USRP or the Application Frameworks, refer to those sections.


This section includes the following parts:

  • FPGA
  • Host
  • Hardware

FPGA

Projects Containing Multiple FPGA Targets

It is generally recommended that project migration should be limited to a single target at a time to reduce complexity and to make migration efforts easier. If a project does contain multiple targets, there may be issues if the same resource name is shared between these targets. For example, top-level VIs, subVIs, or common resource names that are shared between targets. To address this, remove all but one of the targets, migrate, and, if necessary, add the additional targets back into the newer project. Additionally, any broken VIs must be fixed by manually selecting the correct FPGA resources.

579x Sample Clock

Projects using 579x targets will have broken VIs that reference the “Sample Clock”. This clock has been renamed to the “Data Clock” and must be reconfigured.

For additional details, or information on migrating one of the NI-579xR streaming projects, see the FlexRIO Projects topic.

Reconfigure Xixlinx IP

Xilinx IP needs to be reconfigured due to the new Vivado version used in LabVIEW Communications 2.0.


To find the affected files and make the necessary updates, follow these steps:

  1. Open the FPGA top-level you wish to migrate.
  2. Wait until type propagation has occurred.
  3. Once the document finishes loading, you will see in the list of errors the affected files, as shown in Figure 107.

Figure 107: Example error list showing affected files for Xilinx IP Core reconfiguration

  1. Double-click on the errors as shown in Figure 107. This will open the affected document.
  2.  Select the affected Xilinx IP block, and click Configure Xilinx IP Core in the right-hand rail as shown in Figure 108.
  3. Wait for the “Re-customize IP“ dialog to appear.
  4. Inside the “Re-customize IP“ dialog, leave the settings untouched and click OK as shown in Figure 109.
  5. Wait until the warning “Not Ready“ as shown in Figure 110, has disappeared.
  6. Repeat steps 2 through 6 until all Errors in the FPGA top-level have disappeared.


Figure 108: How to reconfigure a Xilinx IP Core (1)



Figure 109: How to reconfigure a Xilinx IP Core (2)

 

Figure 110: "Not Ready" warning because Xilinx tool is processing the IP in the background


Host


FPGA Resources


The FIFO resource names in the Host VIs which interface with DMA FIFOs must be updated. In LabVIEW Communications 2.0, the FIFO resource contains additional prefixes for the FPGA resource file name along with the FIFO name itself. For example, in the USRP Streaming projects, “Rx Stream 0” becomes “USRP Resources.grsc\Rx Stream 0.” Because of this, all FIFO node instances (Start/Stop, Configure, and Read/Write), along with any FPGA reference terminals, must be updated.


If the host is not updated correctly, runtime errors can occur after migrating over a previous project. These errors may persist even after a recompile in the newer version. A typical error is shown in Figure 111.


Figure 111: Typical Error if Host Not Updated

Note: The bitfile may need to be recompiled in version 2.0 to make use of any changes in resource files that may have been added during migration of the project. This must be done prior to any host-side changes that reference that bitfile.


To update FPGA refnums, complete the following steps:

Note: If the application uses FPGA terminals, or constants, then they may need to be updated to the latest bitfile.

1. Select the FPGA reference and click Configure in the right-hand rail.


Figure 112: Configure Dialog in Right-Hand Rail

  1. In the “FPGA Interface Dynamic Refnum Configuration“ dialog, click Import bitfile and browse to your recently compiled bitfile.

    Note: The default location will be in the <project directory>\Builds folder. However, this, along with the file name, will vary based on the configuration of the build spec used during compile


Figure 113: Import Bitfile

  1. (Optional) With the “FPGA Interface Dynamic Refnum Configuration“ dialog still open, remove all unused resources by clicking the X symbol on the right side. This will not affect functionality but may make it easier to view used resources at a later time.
  2. Click OK in the “FPGA Interface Dynamic Refnum“ dialog.


To update DMA FIFO nodes, complete the following steps:

  1. Select the affected DMA FIFO node.
  2. In the right-hand rail is a drop-down selection for available FIFO names referenced by the bitfile being used. Select the appropriate resource as shown in Figure 114.


Figure 114: Select Appropriate Resource

USRP API

Several changes have been made to the USRP API. For a list of these changes, and needed adjustments, see the Host API section under the USRP Projects topic.

Hardware


USRP 40 MHz

The USRP RIO 40 MHz target will be deprecated in future versions of LabVIEW Communications. Previous projects built for these targets will still be usable in version 2.0 but you should consider migration efforts in future designs. Please see the USRP Projects topic for instructions on how to update to the latest USRP targets. 

 

Back to Top

3. Next Steps

Continue onto other sections of the LabVIEW Communications 1.1 to 2.0 Migration Guide for: 

The LabVIEW Communications product documentation provides detailed information in addition to the tasks discussed in this guide. Hardware manuals also contain valuable information about the features and performance characteristics of NI RIO devices.


The main NI support page, ni.com/support, provides quick access to manuals, KnowledgeBase documents, tutorials, example code, community forums, technical support, and customer service.

Formal Training

In addition to online content, in-product Guided Help and examples, you can also obtain LabVIEW Communications instructor-led training from NI. For details, visit ni.com/training/communications or consult with your NI sales representative.

NI Alliance Partners and Services

NI partners can help you with the design, integration, and deployment of your application. The NI Alliance Partner Network is a program of more than 700 independent, third-party companies worldwide that provide engineers with complete solutions and high-quality products based on graphical system design.

Finally, you can count on NI field engineers to discuss how to solve your particular application using the NI platform.


Back to Top

4. Revisions and Feedback 

NI strives to provide high-quality content and welcomes your comments. Please send feedback for future revisions of the guide to your local NI support team.


If there are areas you believe need clarification, submit your question to the LabVIEW Communications System Design Suite Discussion Forum, where the applications, support, and R&D engineers can answer it for the benefit of all readers.

 

Revision

Date

Change Summary

1.0

8/1/2016

Initial release alongside LabVIEW Communications 2.0

 

Back to Top

5. Additional Resources

 

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit